ORA-07445:[DBKTWRITENFY()+75] [SIGSEGV] REPORTED IN ALERT LOG (Doc ID 2041064.1)

Last updated on SEPTEMBER 11, 2023

Applies to:

Symptoms

The following symptoms have been attributed to this issue :-

a) The following error or similar is seen in the alert log :-

ORA-07445: exception encountered: core dump [dbktWriteNfy()+75] [SIGSEGV] [ADDR:0x7FFFEDC51FE8] [PC:0xCC129CB] [Address not mapped to object] []

b) The incident context dump will be similar to :-

----- Incident Context Dump -----
Address: 0x7fd750737678
Incident ID: 72670
Problem Key: ORA 7445 [dbktWriteNfy]
Error: ORA-7445 [dbktWriteNfy] [SIGSEGV] [ADDR:0x7FFFEDC51FE8] [PC:0xCC129CB] 
[Address not mapped to object] [] [] [] [] [] [] []
[00]: dbgexExplicitEndInc [diag_dde]
[01]: dbgeEndDDEInvocationImpl [diag_dde]
[02]: dbgeEndDDEInvocation [diag_dde]
[03]: ssexhd []
[04]: sslsshandler []<-- Signaling
[05]: __sighandler []
[06]: dbktWriteNfy []
[07]: dbgtfdFileWrite [diag_uts]
[08]: dbgtfdFileAccessCbk [diag_uts]
[09]: dbgtfPutStr [diag_uts]
[10]: dbktPri []
[11]: ksdwrf [VOS]
[12]: ktgAvlDumpTree []

And many more calls to 'ktgAvlDumpTree' will be seen in the stack

c) The database is likely to be using 'inmemory' parameters e.g. :- 

show parameter inmemory 

inmemory_clause_default                     string
inmemory_force                              string                           DEFAULT
inmemory_max_populate_servers               integer                          100
inmemory_query                              string                           ENABLE
inmemory_size                               big integer                      350G
inmemory_trickle_repopulate_servers_percent integer                          50
optimizer_inmemory_aware                    boolean                          TRUE

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.