ORA-7445 [kskqmkact()+468] Reported While Running DataPump Import (IMPDP) (Doc ID 2060506.1)

Last updated on JULY 25, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Information in this document applies to any platform.

Symptoms

During full database DataPump import, the alert log reports error

ORA-07445: exception encountered: core dump [kskqmkact()+468] [SIGSEGV] [ADDR:0xAA8] [PC:0x100A81554] [Address not mapped to object] []


The full database DataPump import is clear from earlier alert log entries:

Mon Sep 21 18:16:27 2015
DW01 started with pid=61, OS id=15991, wid=2, job SYSTEM.SYS_IMPORT_FULL_01
Mon Sep 21 18:16:27 2015
............
DW3H started with pid=189, OS id=16116, wid=126, job SYSTEM.SYS_IMPORT_FULL_01
Mon Sep 21 18:16:30 2015
DW3I started with pid=190, OS id=16117, wid=127, job SYSTEM.SYS_IMPORT_FULL_01
Mon Sep 21 18:16:30 2015
DW3J started with pid=191, OS id=16118, wid=128, job SYSTEM.SYS_IMPORT_FULL_01
...........
Mon Sep 21 21:46:07 2015
Completed checkpoint up to RBA [0x17.2.10], SCN: 7700361
Mon Sep 21 22:00:00 2015
Setting Resource Manager plan SCHEDULER[0x32CA]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Mon Sep 21 22:00:00 2015
Starting background process VKRM
Mon Sep 21 22:00:00 2015
VKRM started with pid=202, OS id=12441
Mon Sep 21 22:00:02 2015
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0xAA8] [PC:0x100A81554, kskqmkact()+468] [flags: 0x0, count: 1]
Errors in file /oracle/db/tech_st/diag/rdbms/ebsdb/ebsdb1/trace/ebsdb1_dw00_28784.trc  (incident=360457):
ORA-07445: exception encountered: core dump [kskqmkact()+468] [SIGSEGV] [ADDR:0xAA8] [PC:0x100A81554] [Address not mapped to object] []
Incident details in: /oracle/db/tech_st/diag/rdbms/ebsdb/ebsdb1/incident/incdir_360457/ebsdb1_dw00_28784_i360457.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Mon Sep 21 22:00:02 2015
Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"


The accompanying trace file shows characteristics like:

----- Current SQL Statement for this session (sql_id=...) -----
CREATE INDEX .... parallel 128;

----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
 object      line  object
 handle    number  name
1ccfc80eb0      1321  package body SYS.DBMS_SQL
1c9a393478     18857  package body SYS.KUPW$WORKER
1c9a393478     18051  package body SYS.KUPW$WORKER
1c9a393478     17667  package body SYS.KUPW$WORKER
1c9a393478      4058  package body SYS.KUPW$WORKER
1c9a393478     10450  package body SYS.KUPW$WORKER
1c9a393478      1824  package body SYS.KUPW$WORKER
1c8f31de10         2  anonymous block

----- Call Stack Trace -----
... kskqmkact kxfxqOnOrderQueue opiexe opiosq0 opiall0 opikpr opiodr rpidrus skgmstack rpidru rpiswu2 kprball kkxspap pevm_icd_call_common pfrinstr_ICAL 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

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms