Datapump Import Fails On Import Of Trigger With ORA-06502: PL/SQL: numeric or value error
(Doc ID 1628926.1)
Last updated on MAY 17, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
DataPump import (impdp) fails with messages like below at the end of the import log:
...
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TRIGGER
ORA-39082: Object type TRIGGER:"<SCHEMA_NAME>"."<TRIGGER_NAME>" created with compilation warnings
ORA-39082: Object type TRIGGER:"<SCHEMA_NAME>"."<TRIGGER_NAME>" created with compilation warnings
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS [TRIGGER:"<SCHEMA_NAME>"."<TRIGGER_NAME>"]
ORA-06502: PL/SQL: numeric or value error
LPX-00217: invalid character 0 (U+0000)
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 9001
----- PL/SQL Call Stack -----
object line object
handle number name
0x150511958 20462 package body SYS.KUPW$WORKER
0x150511958 9028 package body SYS.KUPW$WORKER
0x150511958 16665 package body SYS.KUPW$WORKER
0x150511958 3956 package body SYS.KUPW$WORKER
0x150511958 9725 package body SYS.KUPW$WORKER
0x150511958 1775 package body SYS.KUPW$WORKER
0x13f979be8 2 anonymous block
ORA-39097: Data Pump job encountered unexpected error -1427
ORA-39065: unexpected master process exception in DISPATCH
ORA-01427: single-row subquery returns more than one row
Job "<LOGIN_SCHEMA>"."SYS_IMPORT_FULL_01" stopped due to fatal error at 12:06:55
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TRIGGER
ORA-39082: Object type TRIGGER:"<SCHEMA_NAME>"."<TRIGGER_NAME>" created with compilation warnings
ORA-39082: Object type TRIGGER:"<SCHEMA_NAME>"."<TRIGGER_NAME>" created with compilation warnings
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS [TRIGGER:"<SCHEMA_NAME>"."<TRIGGER_NAME>"]
ORA-06502: PL/SQL: numeric or value error
LPX-00217: invalid character 0 (U+0000)
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 9001
----- PL/SQL Call Stack -----
object line object
handle number name
0x150511958 20462 package body SYS.KUPW$WORKER
0x150511958 9028 package body SYS.KUPW$WORKER
0x150511958 16665 package body SYS.KUPW$WORKER
0x150511958 3956 package body SYS.KUPW$WORKER
0x150511958 9725 package body SYS.KUPW$WORKER
0x150511958 1775 package body SYS.KUPW$WORKER
0x13f979be8 2 anonymous block
ORA-39097: Data Pump job encountered unexpected error -1427
ORA-39065: unexpected master process exception in DISPATCH
ORA-01427: single-row subquery returns more than one row
Job "<LOGIN_SCHEMA>"."SYS_IMPORT_FULL_01" stopped due to fatal error at 12:06:55
The relevant tracefile shows:
...
kwqberlst rqan->lagno_kwqiia 4
KUPW:22:45:17.735: 1: ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS [TRIGGER:"<SCHEMA_NAME>"."<TRIGGER_NAME>"]
ORA-06502: PL/SQL: numeric or value error
LPX-00217: invalid character 0 (U+0000)
KUPW:22:45:17.735: 1: ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 9001
KUPW:22:45:17.735: 1: ----- PL/SQL Call Stack -----
object line object
handle number name
0x643ba42b8 20462 package body SYS.KUPW$WORKER
0x643ba42b8 9028 package body SYS.KUPW$WORKER
0x643ba42b8 16665 package body SYS.KUPW$WORKER
0x643ba42b8 3956 package body SYS.KUPW$WORKER
0x643ba42b8 9725 package body SYS.KUPW$WORKER
0x643ba42b8 1775 package body SYS.KUPW$WORKER
0x63f46d798 2 anonymous block
KUPW:22:45:17.735: 1: Setting v_fatal_msg_sent to true
*** 2014-01-23 22:45:18.085
KUPW:22:45:18.085: 1: In procedure EXIT
KUPW:22:45:18.085: 1: DBMS_LOB.FREETEMPORARY called.
KUPW:22:45:18.087: 1: DBMS_LOB.FREETEMPORARY returned.
KUPW:22:45:18.088: 1: Returning after sending fatal ms
kwqberlst rqan->lagno_kwqiia 4
KUPW:22:45:17.735: 1: ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS [TRIGGER:"<SCHEMA_NAME>"."<TRIGGER_NAME>"]
ORA-06502: PL/SQL: numeric or value error
LPX-00217: invalid character 0 (U+0000)
KUPW:22:45:17.735: 1: ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 9001
KUPW:22:45:17.735: 1: ----- PL/SQL Call Stack -----
object line object
handle number name
0x643ba42b8 20462 package body SYS.KUPW$WORKER
0x643ba42b8 9028 package body SYS.KUPW$WORKER
0x643ba42b8 16665 package body SYS.KUPW$WORKER
0x643ba42b8 3956 package body SYS.KUPW$WORKER
0x643ba42b8 9725 package body SYS.KUPW$WORKER
0x643ba42b8 1775 package body SYS.KUPW$WORKER
0x63f46d798 2 anonymous block
KUPW:22:45:17.735: 1: Setting v_fatal_msg_sent to true
*** 2014-01-23 22:45:18.085
KUPW:22:45:18.085: 1: In procedure EXIT
KUPW:22:45:18.085: 1: DBMS_LOB.FREETEMPORARY called.
KUPW:22:45:18.087: 1: DBMS_LOB.FREETEMPORARY returned.
KUPW:22:45:18.088: 1: Returning after sending fatal ms
Changes
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 |