EXPDP ORA-39126 ORA-01422 ORA-06512 Errors and sys.metaxsl$ table/view corruption can lead Datapump Exports to Fail
(Doc ID 1948299.1)
Last updated on FEBRUARY 13, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and laterInformation in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data .Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Symptoms
1. The following errors are reported in the datapump export log
Export: Release 11.2.0.4.0 - Production on Tue Nov 18 11:57:06 2014
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Password:
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
Starting "SYSTEM"."SYS_EXPORT_TABLE_01": system/******** parfile=test_table_expdp.par
Estimate in progress using BLOCKS method...
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.CONFIGURE_METADATA_UNLOAD [ESTIMATE_PHASE]
ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 9724
----- PL/SQL Call Stack -----
object line object
handle number name
0x111f9038d0 21988 package body SYS.KUPW$WORKER
0x111f9038d0 9751 package body SYS.KUPW$WORKER
0x111f9038d0 7485 package body SYS.KUPW$WORKER
0x111f9038d0 14673 package body SYS.KUPW$WORKER
0x111f9038d0 2734 package body SYS.KUPW$WORKER
0x111f9038d0 10431 package body SYS.KUPW$WORKER
0x111f9038d0 1824 package body SYS.KUPW$WORKER
0x111f90ae70 2 anonymous block
2. There may be a failing SQL in the DW trace file
SELECT script FROM sys.metaxsl$ WHERE xmltag=:1 AND transform=:2 AND model=:3
3. The failing functions and the call stack is similar to
skdstdst <- ksedst1 <- ksedst <- dbkedDefDump <- ksedmp <- dbkdaKsdActDriver <- dbgdaExecuteAction <- dbgdaRunAction <- dbgdRunActions <- dbgdProcessEventAct <- ions <- dbgdChkEventKgErr <- dbkdChkEventRdbmsEr <- ksfpec <- dbgePostErrorKGE <- dbkePostKGE_kgsf <- kgeselv <- ksesecl0 <- rpiswu2 <- rpidrv <- psddr0 <- psdnal <- pevm_EXIM <- pfrinstr_EXIM <- pfrrun_no_tool <- pfrrun <- plsql_run <- peicnt <- kkxexe <- opiexe <- kpoal8 <- opiodr <- kpoodr <- upirtrc <- kpurcsc <- kpuexec <- OCIStmtExecute <- kupprwp <- ksvrdp <- opirip <- opidrv <- sou2o <- opimai_real <- ssthrdmain <- main <- libc_start_main <- start
Changes
The database might have been upgraded from previous release or patchset to 11.2.0.4
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |