ORA-7445 [nstimexp()+32] With Patch 6918493 Applied

(Doc ID 869894.1)

Last updated on SEPTEMBER 01, 2014

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 09-Apr-2013***


When running frequent errors like the following are raised:

ORA-07445: exception encountered: core dump [nstimexp()+28] [SIGSEGV] [ADDR:0x58] [PC:0x1083E88FC] [Address not mapped to object] []

This issue was suspected to be a case of <bug:6918493> as described in eg. <note:789111.1>, however after applying <patch:6918493> the error persists although the offset may have changed slightly:

ORA-07445: exception encountered: core dump [nstimexp()+32] [SIGSEGV] [ADDR:0x58] [PC:0x1083E8B20] [Address not mapped to object] []

Note the "+28" changed to "+32" - this is because the code for the nstimexp() function was modified by <patch:6918493>.

The call stack will still be something like:

... nstimexp ltmdvp sslsstehdlr __sighndlr call_user_handler ... kscnfy ksmdpg opidcl ...

We see opidcl() on the stack - this function is called when we find a session where the client disappeared, ie. this is the Dead Connection Detection (DCD) that does what it is supposed to do.

Also note that we call the signal handler and then fail in nstimexp()


Product (Component) Oracle Net Services (SQL*Net)
Range of versions believed to be affected Versions BELOW 12.1
Versions confirmed as being affected
Platforms affected Generic (all / most platforms affected)


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