Shulou(Shulou.com)06/01 Report--

Problem description

When the colleague response database is exported using the data pump, it is exported to UDE-31623, ORA-31623 and ORA-06512, roughly as follows:

The alarm log information is roughly as follows:

Treatment process

(1) in the first step, I thought it was caused by insufficient streams pool size or insufficient allocation of sga. After query, I found that sga allocated 64g and streams pool size = 256m. Therefore, the problem of insufficient memory allocation was eliminated.

(2) in the second step, according to the MOS document (document ID 1907256.1), the reasons such as object invalidation are excluded.

(3) in the third step, when troubleshooting the dba_datapump_jobs view, I found that there were more than 340 terminated tasks. I was surprised by the number of failed tasks, because normally there would not be so many terminated tasks in this view, so I tried to clean up these failed tasks:

SELECT o.status

O.object_id

O.object_type

O.owner | |'. | | object_name "OWNER.OBJECT"

FROM dba_objects o, dba_datapump_jobs j

WHERE o.owner = j.owner_name

AND o.object_name = j.job_name

AND j.job_name NOT LIKE 'BIN$%'

ORDER BY 4, 2

According to the queried objects, we use drop table XXX purge to delete them one by one, or we can delete them in batches through scripts. after all the terminated objects are deleted, we try to export the data pump again and are pleasantly surprised to find that it can be exported normally.

Summary

Thus it can be seen that the reason for this failure is that there are too many terminated objects in the dba_datapump_jobs. After we delete them, the problem can be solved.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.