Вячеслав ЛюбомудровПо запросу больше похоже на Bug 18373054 : EXPDP GETS SLOWER WITH EVERY ORACLE TEXT INDEX REBUILD.
точно!
я как раз поставил чаще перестройку индексов и было это не сильно давно
проверил запросом
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
-- Affected Domain Index(es)
select s.obj#,o.owner,o.object_name,count(s.secobj#) "ORPHAND SECOBJ"
from sys.secobj$ s,dba_objects o, dba_objects o2
where s.obj#=o.object_id
and o2.object_name is null
and s.secobj#=o2.object_id (+)
group by s.obj#,o.owner,o.object_name
order by s.obj#,o.owner,o.object_name;
OBJ# OWNER OBJECT_NAME ORPHAND SECOBJ
---------- ------------ ----------------------- --------------
3646279 U1 TEST_IDX 2173300
у меня ORPHAND SECOBJ=129848
авторUsually, this query should not return any rows. Due to this bug, each Domain Index rebuild activity will increase the output of column "ORPHAND SECOBJ" by 4.
NOTE:
The larger the number returned by "ORPHAND SECOBJ" the slower the Data Pump Export will get when exporting Domain Indexes.
The bug is fixed in 12.2 (Future Release).
Solution
If it is known that your database maintains a number of Domain Indexes, it is recommended to execute the above query each time before executing Data Pump Export.
To solve the issue, use any of below alternatives:
Apply interim patch 18373054, if available for your platform and Oracle version.
To check for conflicting patches, please use the MOS Patch Planner Tool
Please refer to
Note 1317012.1 - How To Use MOS Patch Planner To Check And Request The Conflict Patches?
If no patch exists for your version, please contact Oracle Support for a backport request.
- OR -
As possible workaround, you can:
Drop and re-create the affected Domain Index(es).
Note that rebuilding the Domain Index(es) will not fix the problem
- OR -
Manually delete the redundant entries in secobj$.
If it is related to performance you can also try creating an index on secobj# of secobj$.
проблемных индекса всего 4 - соответственно лечить просто
