Basic Elementsthe day before yesterday finally successfully to the user to export the entire database, and today the user also told the export data can not be imported, first asked the user what error, to my answer is a ' job ' SYSTEM. " Sys_import_full_03 "Because of fatal error in XXXX elapsed 0 03:01:06 Stop", no other hints, the amount of information is too little, this processing is quite troublesome. Problem Analysis
Step One: First or add tracking informationstill have to rely on their own, fortunately we will point tracking skills, specific ways to see my previous post how to diagnose Oracle data pump-on how to add diagnostic information to the pump, come on, look at the results after the tracking orcl_dm00_10856.trc, the bit of the error prompt The following:Kupm:13:38:03.378:log message received from worker dg,kupc$c_1_20141208103757,kupc$a_1_103800203000000,mcp,510, Ykupm:13:38:03.378: "Zlhis" was imported. " Check-in price "576.4 KB 20817 lineskupm:13:38:03.378: ****out DISPATCH, request type=3031, response type =2041* * * 2014-12-08 13:38:04.392kupm:13:38:04.392:client Count Is:1kupm:13:38:04.392:in check_workers ...kupm:13:38:04.392:live worker Count Is:1kupm:13:38:04.392:in Set_longopskupm:13:38:04.392:work so far is:107805.74195098876953125kupm:13:38:04.392:checking for Resumable waitskupm:13:39:05.435:client Count Is:1* * * 2014-12-08 13:39:05.435kupm:13:39:05.435:in check_workers ...kupm:13:39:05.435:live worker Count is:0kupm:13:39:05.435:worker ID is:kupm:13:39:05.435:worker Error is:0kupm: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:1kupm: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 = 1Kupm:13:39:05.435:log message received from MCPkupm:13:39:05.435: Job "SYSTEM". " Sys_import_full_03 "due to fatal error Monday December 8 13:39:05 elapsed 0 03:01:06 Stopkupm:13:39:05.498:in Respond_to_startkupm:13:39:05.498:in check_workers ...kupm:13:39:05.498:live worker Count is:0kupm:13:39:05.498:worker ID is:kupm:13:39:05.498:worker Error is:0The results are very disappointing and there are no valuable error hints. Step Two: View the alert log belowthis time to look at the alert log, perhaps inside can give some hints, open the log did find very valuable information, as follows:Tue Dec 02:00:00Closing Scheduler WindowClosing Resource Manager Plan via scheduler windowclearing Resource Manager plan via parameterTue Dec 02:00:12Exception [Type:access_violation, Unable_to_read] [addr:0x0] [pc:0x14575b408, Kpodpals () +5174]error:unable to normalize symbol name of 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<-0000000077c991af<- 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<-pfrinstr_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\orcl\trace\orcl_dw00_5304.trc (incident=8636):ORA-07445: Unexpected error: Core dump [Kpodpals () +5174] [access_violation] [addr:0x0] [pc:0x14575b408] [Unable_to_read] []Incident Details IN:D:\APP\ADMINISTRATOR\DIAG\RDBMS\ORCL\ORCL\INCIDENT\INCDIR_8636\ORCL_DW00_5304_I8636.TRC Use Adrci or support Workbench to the incident.See Note 411.1 at My Oracle support for error and packaging details.Tue Dec 02:00:17dumping diagnostic data in directory=[cdmp_20141209020017], requested by (Instance=1, osid=5304 (DW00)), summary=[ INCIDENT=8636].Tue Dec 02:00:19Sweep [inc][8636]: CompletedSweep [inc2][8636]: CompletedTue Dec 02:00:55with this information, further log analysis I will not be described here, because there is no value information, we are here to seize ORA-07445 [Kpodpals () +5174], this core error, General 99% is a bug caused by Oracle, With Oracle's official information, a document was found: 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, April, 2010 9:21:43
Copyright (c) 2003, 2005, 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/table
Processing Object Type Table_export/table/table_data
Ora-39014:one or more workers has prematurely exited.
Ora-39029:worker 1 with process name "DW01" prematurely terminated
Ora-31672:worker process DW01 died unexpectedly.
The Job "SYSTEM". Sys_import_full_01 "stopped due to fatal error at 09:23:32cause
This is addressed in Bug 9626756. A no-name column "<space>" is included in the table definition.
The imported table is defined as:CREATE TABLE A_table
(
ID number,
"Varchar2",--"" 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 and then exclude the table during import with:exclude=table:\ "in (' a_table ') \"The reason is that there is a table of the field is a space, Pit daddy Ah, actually have so create a table, next we will query the system whether there really exists such a table. resolution Process
Step one: Query table fields
through the door of the SQL statement, a query is sure to have a blank field, the table name is Tx_ medical treatment project, the table is not our system with the table, is due to the previous channel to do the system switch, save the user old system data table, really killed people ah. Step two: Exclude table re-importThere are two ways to solve this, 1. In the formal library to adjust or rebuild the table, 2. Import the time exclusion problem table, after communication decided to use the second method, exclude the tableIMPDP system/xxxxx directory=dp full=y dumpfile=wzyfull20141205b_01.dmp logfile=impdp1209.log trace=4a0300 Exclude=table:\ "in \ (\ ' Zlhis. Tx_ medical program \ ' \ ' \ ", 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 a long wait of 3 hours, the data was successfully imported. key points of knowledgeData Pump Log tracking: Generates a trace log file by adding the trace parameter when exporting the importORA-7445 [kpodpals]: Bug 9626756. A table containing a field with no name, all spaces
IMPDP terminated ORA-7445 [kpodpals] due to fatal error
