After Upgrading To 18c Seeing Several ORA-07445: exception encountered: core dump [kkqctdrvJPPD()+3108] Core Dumps
(Doc ID 2538301.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 18.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
- After upgrading to 18c, seeing several core dumps in the alert.log:
ORA-07445: exception encountered: core dump [kkqctdrvJPPD()+3108] [SIGSEGV] [ADDR:0x28] [PC:0x1131AD1A4] [Address not mapped to object]
----- Current SQL Statement for this session (sql_id=f5y6pgqbcjp8p) -----
SELECT NUM||':'||l))...
.......
ORDER BY NUM, IDX_OR_TAB DESC)
[TOC00005]
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
4458c4f58 12 procedure SYS.DBMS_FEATURE_PARTITION_SYSTEM
443a02fd0 1 anonymous block
3e8c52328 1721 package body SYS.DBMS_SQL.EXECUTE
44812ad78 312 package body SYS.DBMS_FEATURE_USAGE_INTERNAL.COMPUTE_FEATURE_USAGE
44812ad78 522 package body SYS.DBMS_FEATURE_USAGE_INTERNAL.SAMPLE_FEATURE_USAGE
44812ad78 694 package body SYS.DBMS_FEATURE_USAGE_INTERNAL.SAMPLE_DB_FEATURE_USAGE
44812ad78 791 package body SYS.DBMS_FEATURE_USAGE_INTERNAL.EXEC_DB_USAGE_SAMPLING
4039832e8 1 anonymous block
[TOC00005-END]
[TOC00004-END]
ksedst dbkedDefDump ksedmp ssexhd sslsshandler
sighndlr call_user_handler sigacthandler kkqctdrvJPPD kkqjpdctr
qksqbApplyToQbcLoc qksqbApplyToQbcLoc qksqbApplyToQbcLoc qksqbApplyToQbcLoc qksqbApplyToQbcLoc
qksqbApplyToQbcLoc qksqbApplyToQbcLoc qksqbApplyToQbcLoc qksqbApplyToQbcLoc qksqbApplyToQbcLoc
qksqbApplyToQbcLoc qksqbApplyToQbcLoc qksqbApplyToQbcLoc qksqbApplyToQbcLoc qksqbApplyToQbcLoc
qksqbApplyToQbcLoc qksqbApplyToQbcLoc qksqbApplyToQbc kkqctdrvTD kkqjpddrv
kkqdrv kkqctdrvIT apadrv opitca kksFullTypeCheck
rpiswu2 kksLoadChild kxsGetRuntimeLock kksfbc kkspbd0
kksParseCursor opiosq0 opipls opiodr rpidrus
skgmstack rpidru rpiswu2 rpidrv psddr0
Changes
Upgraded databases from 12c to 18c, since then multiple core dumps are generated for all upgraded databases running on same server.
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 |