Shulou(Shulou.com)05/31 Report--

This article mainly shows you the "impdp import error report ORA-04030 how to do", the content is easy to understand, clear, hope to help you solve doubts, the following let the editor lead you to study and learn "impdp import error report ORA-04030 how to do" this article.

Phenomenon description: five large tables are exported with impdp from the source side, and the remap_tablespace is used to import these five tables on the destination side, and an error is reported when importing to the statistics.

System: Linux 6.5

Environment: 11.2.0.4

The import error is as follows:

Processing object type TABLE_EXPORT/TABLE/COMMENTProcessing object type TABLE_EXPORT/TABLE/INDEX/INDEXProcessing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINTProcessing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICSProcessing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICSORA-39014: One or more workers have prematurely exited.ORA-39029: worker 1 with process name "DW00" prematurely terminatedORA-31671: Worker process DW00 had an unhandled exception.ORA-04030: out of process memory when trying to allocate 16048 bytes (session heap,kuxLpxAlloc) ORA-06512: at "SYS.KUPW$WORKER" Line 1887ORA-06512: at line 2ORA-39097: Data Pump job encountered unexpected error-1427ORA-39065: unexpected master process exception in MAINORA-01427: single-row subquery returns more than one rowJob "SYS". "SYS_IMPORT_TABLE_02" stopped due to fatal error at Mon Sep 17 16:59:07 2018 elapsed 0 01:10:01

Analysis:

According to the error report, it is caused by insufficient memory, but when analyzing memory and sga, no obvious errors are found, and the system memory is sufficient. Check MOS and find that this article is consistent with my error report. (document ID 1516766.1)

As described in this document, during the data pump import of a database containing large partition tables and many subpartitions, ORA-04030 is reported to have caused the import to fail. In version 11.2.x, a large amount of database statistics for these objects compressed the XML processing during import. This has been identified as Bug:14841775. In version 12.1, the way database statistics are exported and imported has been redesigned, so memory resource issues will no longer occur.

Resolve:

1. Use EXCLUDE = STATISTICS to perform the import that does not include statistics, and regenerate the statistics after importing objects.

2. If possible, upgrade the database to version 12.1

The first method for error resolution is to use the import that does not include statistics, and then re-collect statistics after the import.

The above is all the contents of the article "what to do about impdp Import error report ORA-04030". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

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.