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

Source: Internet
Author: User
Tags table definition

Impdp terminate ORA-7445 [kpodpals], impdpkpodpals due to fatal errors
It was difficult to successfully export all the data to the user the day before yesterday. Today, the user told me that the exported data could not be imported. First, ask the user for any error message, 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, you still have to add the tracking information on your own. Fortunately, we will learn the tracking skills, for details, see my previous post "How to Diagnose Oracle Data Pump"-How to add diagnostic information to the Data Pump. Let's take a look at the tracking result "orcl_dm00_10856.trc". The error message is located at: KUPM: 13: 38: 03.378: Log message received ed from worker DG, KUPC $ c_000020141208103757, KUPC $ a_0000103800203000000, MCP, 510, YKUPM: 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_longopsKUPM: 13: 38: 04.392: Work so far is: 107805.74195098876953125 KUPM: 13: 38: 04.392: Checking for resumable waitsKUPM: 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 I S: 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 MAINKUPV: 13: 39: 05.435: Update request for job: SYSTEM. SYS_IMPORT_FULL_03, func: 1 KUPM: 13: 39: 05.435: Entered state: STOPPINGKUPM: 13: 39: 05.435: keeping master because job is restartableKUPM: 13: 39: 05.435: final job_info_flags = 1 KUPM: 13: 39: 05.435: Log message r Eceived from MCPKUPM: 13: 39: 05.435: Job "SYSTEM ". "SYS_IMPORT_FULL_03" ended KUPM: 13: 39: 2014: In RESPOND_TO_STARTKUPM: 13: 39: 05.498: In check_workers at 13:39:05 on Monday, 05.498 due to a fatal error... 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 results are very disappointing, and there are no valuable error messages. Step 2: Check the alert Log. If you want to view the alert Log, you may be prompted to open the log and find valuable information, as shown below: tue Dec 09 02:00:00 2014 Closing scheduler windowClosing Resource Manager plan via scheduler windowClearing Resource Manager plan via parameterTue 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.trcUse 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]: completedSweep [inc2] [8636]: completedTue Dec 09 02:00:55 2014 with this information, further log analysis I will not describe here, because there is no value information, we here to seize the ORA-07445 [kpodpals () + 5174] Don't put, this core error, general 99% is caused by Oracle BUG, through Oracle official information, really found 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 = replaceImport: Release 10.2.0.1.0-Production on Wednesday, 21 2.16l, 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 as: 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 with: exclude = table: \ "IN ('A _ table') \" is because the fields IN the TABLE are spaces, if you have created a table like this, we will query 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: There are two ways to re-import the exclusive table: 1. adjust or recreate the table in the official database. the second method is adopted after communication. The Partition TABLE 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 \', \ 'anonus US \ ', \ '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 point Data Pump log tracking: by adding trace parameters while exporting the import, generate a trace log file ORA-7445 [kpodpals]: Bug 9626756. A table contains a field with no name but spaces.

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.