DataPump Import Of APPS FND_LOBS Fails With ORA-07445 [kupfxReadLob] Errors
(Doc ID 2110230.1)
Last updated on AUGUST 01, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata 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
1. The Datapump import into 12.1.0.2 fails and the alert log shows the following errors
The import command is similar to:
impdp "'/ as sysdba'" tables=APPLSYS.FND_LOBS directory=<directory_name> dumpfile=<dump_name> logfile=<log_name>
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x7D] [PC:0x31A5C87, kupfxReadLob()+327] [flags: 0x0, count: 1]
Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_dw00_4917.trc (incident=132291):
ORA-07445: exception encountered: core dump [kupfxReadLob()+327] [SIGSEGV] [ADDR:0x7D] [PC:0x31A5C87] [Address not mapped to object] []
impdp "'/ as sysdba'" tables=APPLSYS.FND_LOBS directory=<directory_name> dumpfile=<dump_name> logfile=<log_name>
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x7D] [PC:0x31A5C87, kupfxReadLob()+327] [flags: 0x0, count: 1]
Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_dw00_4917.trc (incident=132291):
ORA-07445: exception encountered: core dump [kupfxReadLob()+327] [SIGSEGV] [ADDR:0x7D] [PC:0x31A5C87] [Address not mapped to object] []
2. There may be a failing SQL in the incident trace file
2016-01-13 10:48:08.522
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x3, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=<sql_id>) -----
BEGIN
SYS.KUPW$WORKER.MAIN('SYS_IMPORT_TABLE_03', 'SYS', 0);
END;
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0x1bbf749f0 860 package body SYS.KUPF$FILE_INT
0x1bbf749f0 910 package body SYS.KUPF$FILE_INT
0x1c2a45cf8 7149 package body SYS.KUPF$FILE
0x1bbc2a810 4484 package body SYS.KUPW$WORKER
0x1bbc2a810 12063 package body SYS.KUPW$WORKER
0x1bbc2a810 2081 package body SYS.KUPW$WORKER
0x1b9c60520 2 anonymous block
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x3, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=<sql_id>) -----
BEGIN
SYS.KUPW$WORKER.MAIN('SYS_IMPORT_TABLE_03', 'SYS', 0);
END;
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0x1bbf749f0 860 package body SYS.KUPF$FILE_INT
0x1bbf749f0 910 package body SYS.KUPF$FILE_INT
0x1c2a45cf8 7149 package body SYS.KUPF$FILE
0x1bbc2a810 4484 package body SYS.KUPW$WORKER
0x1bbc2a810 12063 package body SYS.KUPW$WORKER
0x1bbc2a810 2081 package body SYS.KUPW$WORKER
0x1b9c60520 2 anonymous block
3. The failing functions and the call stack is similar to
... kupfxReadLob spefcmpa spefmccallstd pextproc peftrusted psdexsp rpiswu2 kxe_push_env_internal_pp_ kkx_push_env_for_ICD_for_new_session psdextp pefccal ...
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 |