ORA-7445 [kqlvld] Raised in Alert Log Using Datapump Export (expdp) on 10.2 (Doc ID 752165.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.1.0.6 [Release 11.1]
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.4 [Release 10.2]
Information in this document applies to any platform.
*** Checked for relevance on 28-AUG-2013 ***


Symptoms

The following symptoms have been attributed to this issue :-

a) Schema based EXPDP fails with any of below symptoms :-


Export: Release 10.2.0.4.0 - 64bit Production on Wednesday, 15 October, 2008 15:59:59

Copyright (c) 2003, 2007, Oracle. All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit
Production With the Partitioning, OLAP, Data Mining and Real Application
Testing options
ORA-31626: job does not exist
ORA-31637: cannot create job SYS_EXPORT_SCHEMA_01 for user ONR_DM
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 1201
ORA-39062: error creating master process DM00
ORA-31649: Master process DM00 violated startup proto .


or


Export: Release 10.2.0.4.0 - 64bit Production on Tuesday, 28 October, 2008 9:46:35

Copyright (c) 2003, 2007, Oracle. All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit
Production With the Partitioning, Oracle Label Security, OLAP, Data Mining Scoring Engine
and Real Application Testing options

UDE-00008: operation generated ORACLE error 22303
OCI-22303: type "SYS"."KU$_STATUS1020" not found



b) At same time that EXPDP fails at session level following error is seen in alert log :-

ORA-07445: exception encountered: core dump [kqlvld()+11125] [SIGSEGV]
[Address not mapped to object] [0x000000038] [] []

Arguments may differ but KQLVLD should be reported

c) ORA-07445 traces reported :-


Current SQL statement for this session:
SELECT /*+ cursor_sharing_exact */ count(*) FROM "SYS"."KUPC$DATAPUMP_QUETAB"
TAB, SYS.DUAL WHERE tab.corrid='MCP' OR tab.corrid=' '
----- PL/SQL Call Stack -----
object line object
handle number name
0x91119140 49 package body SYS.DBMS_RULEADM_INTERNAL
0x92a6f4a0 178 package body SYS.DBMS_RULE_ADM
0x91367270 2834 package body SYS.DBMS_PRVTAQIS
0x91367270 2771 package body SYS.DBMS_PRVTAQIS
0x91367270 1041 package body SYS.DBMS_PRVTAQIS
0x91395f30 5708 package body SYS.DBMS_AQADM_SYS
0x92a08600 229 package body SYS.KUPC$QUE_INT
0x92a08600 1415 package body SYS.KUPC$QUE_INT
0x94ba53c8 1 anonymous block
0x949a9558 102 package body SYS.KUPC$QUEUE_INT
0x84146cc8 612 package body SYS.KUPM$MCP
0x91303968 2 anonymous block



This may vary depending on the EXPDP action being taken

d) The call stack trace will be similar to :-

kqlvld <- kglgob <- kwraidp <- kwravlc <- opicbk <- opikpr <- opiodr <- rpidrus <- skgmstack
<- rpidru <- rpiswu2 <- kprball <- kwrapfs <- kwracrl <- kwrxcrl <- spefcmpa <- spefmccallstd
<- pextproc <- peftrusted <- psdexsp <- rpiswu2 <- psdextp <- pefccal <- pefcal <- pevm_FCAL
<- pfrinstr_FCAL <- pfrrun_no_tool <- pfrrun <- plsql_run <- peicnt <- kkxexe <- opiexe <- opipls
<- opiodr <- rpidrus <- skgmstack <- rpidru <- rpiswu2 <- rpidrv <- psddr0 <- psdnal <- pevm_EXIM
<- pfrinstr_EXIM <- pfrrun_no_tool <- pfrrun <- plsql_run <- peicnt <- kkxexe <- opiexe <- kpoal8
<- opiodr <- kpoodr <- upirtrc <- kpurcsc <- kpuexecv8 <- kpuexec <- OCIStmtExecute <- kupprdp
<- opirip <- opidrv <- sou2o <- opimai_real <- main <- libc_start_main <- start

The key function for this article to be considered is 'kqlvld', if this is not seen in the stack the note is unlikely to provide a resolution.

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