ORA-07445 [lxinitc] Errors Occur From Datapump Import (Doc ID 1958257.1)

Last updated on JANUARY 16, 2015

Applies to:

Oracle Database - Standard Edition - Version 11.2.0.3 to 12.1.0.2 [Release 11.2 to 12.1]
Information in this document applies to any platform.

Symptoms

1.  The Datapump import fails with fatal error:

Import: Release 11.2.0.3.0 - Production on Thu Nov 6 12:47:02 2014
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
;;;
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SYS"."SYS_IMPORT_FULL_02" successfully loaded/unloaded
Starting "SYS"."SYS_IMPORT_FULL_02": /******** AS SYSDBA REMAP_SCHEMA=live3:test3 DIRECTORY=DATA_PUMP_DIR TABLE_EXISTS_ACTION=append DUMPFILE=ctlgrp.dmp LOGFILE=test3_ctlgrp_imp.log
Processing object type TABLE_EXPORT/TABLE/TABLE
Table "TEST3"."CTLGRP" exists. Data will be appended to existing table but all dependent metadata will be skipped due to table_exists_action of append
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Job "SYS"."SYS_IMPORT_FULL_02" stopped due to fatal error at Thu Nov 6 12:48:40 2014 elapsed 0 00:01:31

2.  The following errors are reported in the alert log:

DW00 started with pid=26, OS id=5288, wid=1, job TEST3.SYS_IMPORT_FULL_01
ORA-07445: exception encountered: core dump [lxinitc()+46] [SIGSEGV] [ADDR:0x4C] [PC:0x25C6B9E] [Address not mapped to object] []

3.  There may be a failing SQL in the DW trace file:

----- Current SQL Statement for this session (sql_id=06w0gb6dx4yhm) -----
INSERT /*+ SYS_DL_CURSOR */ INTO RELATIONAL("TST09"."CTLGRP" NOT XMLTYPE) ("ITMCLS","ITMCOD","CTLGRP","CTLDAT","FIFODT","QASTAT","EXPDAT","STPDAT","NONRLS","CTRL_DATE","CTRL_USER","MACHID","TEAMID","PRODAT","RRNUMB","PONUMB","VNDCOD","VNDLOT","RECV_DATE","RESERV","POTENCY","EMPTY_DATE","PARENT_CTLGRP") VALUES (NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL)
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
 object      line  object
 handle    number  name
0x1cd995618        58  package body SYS.KUPD$DATA_INT
0x1dd7c4818      3401  package body SYS.KUPD$DATA
0x1dd2a0ba8     15332  package body SYS.KUPW$WORKER
0x1dd2a0ba8      4426  package body SYS.KUPW$WORKER
0x1dd2a0ba8      9739  package body SYS.KUPW$WORKER
0x1dd2a0ba8      1775  package body SYS.KUPW$WORKER
0x1cdf5bd98         2  anonymous block

4.  The failing functions and the call stack is similar to:

skdstdst <- ksedst1 <- ksedst <- dbkedDefDump <- ksedmp   <- ssexhd <- sighandler <- lxinitc <- ldxlxi <- ldxsen <- evadds <- evaopn2 <- evacat <- expepr <- evaand <- expepr <- evaor <- expepr <- qesltcValidateCheck <- Constraints <- inschk <- Constraints <- klaevc <- klarpp <- klaprs <- kpodpls <- opiodr <- kpoodr <- upirtrc <- kpurcsc <- kpudpxls_intCtxLoad <- Stream <- kpudpxls_ctxLoadStr <- eam <- OCIDirPathLoadStrea <- kupdls_rdData <- kupdls <- spefcifa <- spefmccallstd <- pextproc <- peftrusted <- psdexsp <- rpiswu2 <- psdextp <- pefccal <- pefcal <- pevm_FCAL <- pfrinstr_FCAL <- 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

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