ORA 7445 [kktget2] when insert in a view
(Doc ID 2874944.1)
Last updated on JULY 21, 2023
Applies to:
Gen 2 Exadata Cloud at Customer - Version All Versions and laterInformation in this document applies to any platform.
-->Upgraded database from 12.1.0.2 to 19.10 and converted to a PDB and put it inside CDB
-->This query works fine in 12.1.0.2
--> This schema has no triggers, don't have a missing trigger
Symptoms
Next error is affecting when customer try to insert in a view:
ORA-07445: exception encountered: core dump [kktget2()+6719] [SIGSEGV] [ADDR:0x0] [PC:0x25FA65F] [Address not mapped to object] []
The incident trc file shows:
----- Call Stack Trace -----
ksedst1()+95 < ksedst()+58 < dbkedDefDump()+2344 < ksedmp()+577 < ssexhd()+2859 < sslssSynchHdlr()+40 < sslsshandler()+94 < __sighandler() < kktget2()+6719 < kxtivwt()+204 < kkqvmCheckValidSVM( < kkqvmTrMrg()+10051 < kkqvmTrMrg()+9802 < kkqvmTrMrg()+9802 < kkqvmdrv2()+925 < kkqdrv()+2278 < opiSem()+4321 < opiDeferredSem()+43 < opitca()+478 < kksFullTypeCheck()+ < rpiswu2()+2004 < kksLoadChild()+7742 < kxsGetRuntimeLock() < kksfbc()+19053 < kkspsc0()+1575 < kksParseCursor()+11 < opiosq0()+2310 < kpooprx()+387 < kpoal8()+830 < opiodr()+1202 < ttcpip()+1255 < opitsk()+1900 < opiino()+936 < opiodr()+1202 < opidrv()+1094 < ...
...
[05]: __sighandler []
[06]: kktget2 []<-- Signaling
[07]: kxtivwt [SQL_Execution]
[08]: kkqvmCheckValidSVM [SQL_VMerge]
[09]: kkqvmTrMrg [SQL_VMerge]
[10]: kkqvmTrMrg [SQL_VMerge]
[11]: kkqvmTrMrg [SQL_VMerge]
[12]: kkqvmdrv2 [SQL_VMerge]
[13]: kkqdrv [SQL_Transform]
[14]: opiSem [OPI]
[15]: opiDeferredSem [OPI]
[16]: opitca [OPI]
[17]: kksFullTypeCheck [cursor]
[18]: rpiswu2 [RPI]
[19]: kksLoadChild [cursor]
[20]: kxsGetRuntimeLock [cursor]
[21]: kksfbc [cursor]
[22]: kkspsc0 [cursor]
[23]: kksParseCursor [cursor]
...
Changes
-->Error occurs after upgrading from 12.1.0.2 to 19.10 and converting to a PDB
-->Database parameters stayed the same as well as memory allocations when migrating into a CDB. We did reset all hidden parameters as oracle recommends during upgrade to 19c
-->This query works fine in 12.1.0.2
-->Existed for a very long time. "Technically" new since it was converted to a PDB, using XMLFILE method.
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 |