Impdp terminate ORA-7445 due to fatal errors [kpodpals]

Impdp terminate ORA-7445 due to fatal errors [kpodpals]

Basic Elements
The day before yesterday, I finally successfully exported all the data to the user. Today, the user told me that the exported data cannot be imported. First, I asked the user what error message is displayed, the answer is a 'job "SYSTEM ". "SYS_IMPORT_FULL_03" was stopped at xxxx elapsed 0 03:01:06 due to a fatal error. There were no other prompts and the amount of information was too small. This was quite troublesome to handle.

Problem Analysis

Step 1: First add the tracking information
We still have to rely on ourselves. Fortunately, we will learn tracking skills. For details, refer to my previous article on How to Diagnose Oracle Data Pump-How to add diagnostic information to the Data Pump. Come on, check the tracking result orcl_dm00_10856.trc. The error prompt is as follows:
KUPM: 13: 38: 03.378: Log message received ed from worker DG, KUPC $ C_1_20141208103757, KUPC $ a_0000103800203000000, MCP, 510, Y
KUPM: 13: 38: 03.378: .. Imported "ZLHIS". "health check package pricing" 576.4 KB 20817 rows
KUPM: 13: 38: 03.378: *** out dispatch, request type = 3031, response type = 2041
* ** 13:38:04. 392
KUPM: 13: 38: 04.392: Client count is: 1
KUPM: 13: 38: 04.392: In check_workers...
KUPM: 13: 38: 04.392: Live worker count is: 1
KUPM: 13: 38: 04.392: In set_longops
KUPM: 13: 38: 04.392: Work so far is: 107805.74195098876953125
KUPM: 13: 38: 04.392: Checking for resumable waits
KUPM: 13: 39: 05.435: Client count is: 1
* ** 13:39:05. 435
KUPM: 13: 39: 05.435: In check_workers...
KUPM: 13: 39: 05.435: Live worker count is: 0
KUPM: 13: 39: 05.435: worker id is:
KUPM: 13: 39: 05.435: Worker error is: 0
KUPM: 13: 39: 05.435: Exited main loop...
KUPM: 13: 39: 05.435: Returned to MAIN
KUPV: 13: 39: 05.435: Update request for job: SYSTEM. SYS_IMPORT_FULL_03, func: 1
KUPM: 13: 39: 05.435: Entered state: STOPPING
KUPM: 13: 39: 05.435: keeping master because job is restartable
KUPM: 13: 39: 05.435: Final job_info_flags = 1
KUPM: 13: 39: 05.435: Log message received ed from MCP
KUPM: 13: 39: 05.435: Job "SYSTEM". "SYS_IMPORT_FULL_03" ended at 13:39:05, January 1, December 8, 2014 elapsed 0, due to a fatal error.
KUPM: 13: 39: 05.498: In RESPOND_TO_START
KUPM: 13: 39: 05.498: In check_workers...
KUPM: 13: 39: 05.498: Live worker count is: 0
KUPM: 13: 39: 05.498: worker id is:
KUPM: 13: 39: 05.498: Worker error is: 0
The results were very disappointing and there were no valuable error messages.
Step 2: View alert logs
At this time, I want to view the alert Log. Maybe there are some tips in it. When I open the log, I find very valuable information, as shown below:
Tue Dec 09 02:00:00 2014
Closing scheduler window
Closing Resource Manager plan via scheduler window
Clearing Resource Manager plan via parameter
Tue Dec 09 02:00:12 2014
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR: 0x0] [PC: 0x14575B408, kpodpals () + 5174]
ERROR: Unable to normalize symbol name for the following short stack (at offset 213 ):
DbgexProcessError () + 200 <-dbgeExecuteForError () + 65 <-dbgePostErrorKGE () + 2269 <-dbkePostKGE_kgsf () + 77 <-kgeade () + 562 <-kgerelv () + 151 <-kgerev () + 45 <-kgerec5 () + 60 <-sss_xcpt_EvalFilterEx () + 1862 <-sss_xcpt_EvalFilter () + 174 <-. 1.4_5 + 59 <-0000000077C985A8 <-0000000077CA9D0D <-000077c991af <-0000000077CD1278 <-kpodpals () + 5174 <-kpodpp () + 4946 <-opiodr () + 1631 <-kpoodr () + 699 <-xupirtrc () + 2833 <-upirtrc () + 117 <-kpurcsc () + 150 <-kpudpxp_ctxPrepare () + 19418 <-OCIDirPathPrepare () + 11 <-kupd_initDirPath () + 1048 <-kupdls () + 2863 <-spefcifa () + 3937 <-spefmccallstd () + 532 <-pextproc () + 47 <-PGOSF493_peftrusted () + 134 <-psdexsp () + 297 <-rpiswu2 () + 3039 <-psdextp () + 951 <-pefccal () + 785 <-pefcal () + 225 <-pevm_FCAL () + 164 <-pfr1__fcal () + 69 <-pfrrun_no_tool () + 77 <-pfrrun () + 1241 <-plsql_run () + 903 <-peicnt () + 328 <-kkxexe () + 616 <-opiexe () + 20959 <-kpoal8 () + 2397 <-opiodr () + 1631 <-kpoodr () + 699 <-xupirtrc () + 2833 <-upirtrc () + 117 <-kpurcsc () + 150 <-kpuexec () + 10984
Errors in file D: \ APP \ ADMINISTRATOR \ diag \ rdbms \ orcl \ trace \ orcl_dw00_5304.trc (incident = 8636 ):
ORA-07445: Exception error: core dump [kpodpals () + 5174] [ACCESS_VIOLATION] [ADDR: 0x0] [PC: 0x14575B408] [UNABLE_TO_READ] []
Incident details in: D: \ APP \ ADMINISTRATOR \ diag \ rdbms \ orcl \ incident \ incdir_8636 \ orcl_dw00_5304_i8636.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Tue Dec 09 02:00:17 2014
Dumping diagnostic data in directory = [cdmp_20141209020017], requested by (instance = 1, osid = 5304 (DW00), summary = [incident = 8636].
Tue Dec 09 02:00:19 2014
Sweep [inc] [8636]: completed
Sweep [inc2] [8636]: completed
Tue Dec 09 02:00:55 2014

With this information, further log analysis I here will not be described, because there is no value information, we here to seize the ORA-07445 [kpodpals () + 5174] Don't put, this kind of core error is generally caused by Oracle BUG 99%. The official Oracle information shows a document:
ORA-7445 [kpodpals] During DataPump Import (Document ID 1096837.1)
SYMPTOMS

You perform a DataPump import and this breaks with errors:
#> Impdp system/password directory = dpu dumpfile = a_table.dmp table_exists_action = replace
Import: Release 10.2.0.1.0-Production on Wednesday, 21 minutes l, 2010 9:21:43
Copyright (c) 2003,200 5, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0-Production
With the Partitioning, OLAP and Data Mining options
Master table "SYSTEM". "SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "SYSTEM". "SYS_IMPORT_FULL_01": system/********* directory = dpu
Dumpfile = a_table.dmp table_exists_action = replace
Processing object type TABLE_EXPORT/TABLE
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW01" prematurely terminated
ORA-31672: Worker process DW01 died unexpectedly.
Job "SYSTEM". "SYS_IMPORT_FULL_01" stopped due to fatal error at 09:23:32
CAUSE

This is addressed in Bug 9626756. A no-name column "<space>" is already ded in the table definition.
The imported table is defined:
Create table a_table
(
Id number,
"" Varchar2 (10), -- "" means "<one space>"
Text varchar2 (10)
);
SOLUTION

1. Don't use columns like "<space>" in the source database

-OR-

2. If a table has such columns, then exclude the table during import:
Exclude = table: \ "IN ('A _ table ')\"

The reason is that the fields in the table are spaces, so we can find out whether such a table exists in our system.

Solution Process

Step 1: Query table fields

Through the on-site SQL statement, there is indeed a blank field in the query. The table name is the TX _ medical project. This table is not included in our system. It was because the system was switched during the previous channel, the table that stores the user's old system data is really killing people.
Step 2: import the table again
There are two ways to solve the problem: 1. Adjust or recreate the table in the official database, 2. Exclude the problem table during import, and use the second method after communication.
Impdp system/xxxxx DIRECTORY = dp full = y DUMPFILE = wzyfull20141205b_01.dmp logfile = impdp1209.log trace = 4a0300 exclude = TABLE: \ "IN \ (\ 'zlhis. TX _ medical project \ '\) \ ", SCHEMA: \" IN \ (\ 'sys \', \ 'System \ ', \ 'outln \', \ 'mgmt _ VIEW \ ', \ 'flows _ FILES \', \ 'mdsys \ ', \ 'ordsys \', \ 'exfsys \ ', \ 'dbsnmp \', \ 'wmsys \ ', \ 'wksys \', \ 'wk _ TEST \ ', \ 'ctxsys \', \ 'Anonymous \ ', \ 'sysman \', \ 'xdb \ ', \ 'wkproxy \', \ 'ordplugins \ ', \ 'flows _ 030000 \', \ 'owbsys \ ', \ 'si _ INFORMTN_SCHEMA \', \ 'olapsys \ ', \ 'Scott \', \ 'oracle _ OCM \'\)\"
After more than three hours of waiting, the data is successfully imported.
Key knowledge points
Data Pump log tracking: You can add trace parameters during export and import to generate a trace log file.
ORA-7445 [kpodpals]: Bug 9626756. A table contains a word with no name but Spaces

Oracle Import and Export expdp IMPDP details

Solution to Oracle 10g expdp export error ORA-4031

Oracle 10gr2 rac expdp error UDE-00008 ORA-31626

Use of expdp/impdp to back up databases in Oracle

Oracle backup recovery (expdp/impdp)

Problems and Solutions of impdp ORA-39002, ORA-39166 and ORA-39164