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 FEBRUARY 24, 2025

Applies to:

Siebel CRM - Version 17.0 [IP2017] and later
Microsoft Windows x64 (64-bit)

Goal

This is also applicable to Siebel IP2013, IP2014, IP2015 and IP2016

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:

- CALL STACK -
kernel RaiseException()
orageneric11 skgesigOSCrash()
orageneric11 kpedbgGetCallStack()
orageneric11 skge_sign_fr()
kernel32 UnhandledExceptionFilter()
MSVCR XcptFilter()
MSVCR endthreadex()
kernel BaseThreadInitThunk()
ntdll RtlInitializeExceptionChain()
ntdll RtlInitializeExceptionChain()

- CALL STACK -
kernel32 RaiseException()
orageneric12 skgesigOSCrash()
orageneric12 kpedbgGetCallStack()
orageneric12 skge_sign_fr()
kernel32 UnhandledExceptionFilter()
MSVCR71 XcptFilter()
MSVCR71 endthreadex()
kernel32 BaseThreadInitThunk()
ntdll RtlInitializeExceptionChain()
ntdll RtlInitializeExceptionChain()

- CALL STACK -
kernel32 RaiseException()
orageneric19 skgesigOSCrash()
orageneric19 kpedbgGetCallStack()
orageneric19 skge_sign_fr()
kernel32 UnhandledExceptionFilter()
MSVCR71 XcptFilter()
MSVCR71 endthreadex()
kernel32 BaseThreadInitThunk()
ntdll RtlInitializeExceptionChain()
ntdll RtlInitializeExceptionChain()

Note

The above call stack are showing different orageneric dll version depending on the DB client version:

For Oracle DB client 11.x the dll version would be orageneric11.dll
For Oracle DB client 12.x the dll version would be orageneric12.dll
For Oracle DB client 19.x the dll version would be orageneric19.dll

Solution

	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

Goal

Solution

References

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

Oracle DB Client on Windows OS Is Bypassing the Siebel Crash Handler and Resulting in Multiple Crashes on orageneric kpedbgGetCallStack() (Doc ID 1368167.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!