Oracle DB Client on Windows OS Is Bypassing the Siebel Crash Handler and Resulting in Multiple Crashes on orageneric kpedbgGetCallStack()
(Doc ID 1368167.1)
Last updated on SEPTEMBER 30, 2021
Applies to:Siebel CRM - Version 17.0 [IP2017] and later
Microsoft Windows x64 (64-bit)
How to generate the correct callstack for crashing Siebel process?
Siebel application on the Windows platform using the Oracle Database Client version might encounter the following issues:
- After a crash has occurred, there are no crash.txt and FDR file created. (In normal circumstances the FDR is generated by the built in Siebel signal handler when a crash occurs)
- All crashes always have the same call stack in the crash.txt as shown below:
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