My Oracle Support Banner

Oracle client or above on Windows is bypassing Siebel crash handler (Doc ID 1368167.1)

Last updated on FEBRUARY 05, 2019

Applies to:

Siebel CRM - Version 8.1.1 [21112] and later
Siebel System Software - Version 8.1.1 [21112] and later
Microsoft Windows (32-bit)


Customers running Siebel version 8.1 on the Windows platform and are using the Oracle database client version or above might encounter one of the following two behaviors:

  1. After a crash has occurred, there was no crash.txt and fdr file created.
  2. For each different crash always the same call stack as described below can be observed in the crash.txt:


kernel32 +0x3fbae = RaiseException() +0x58
orageneric11 +0x8650b1 = skgesigOSCrash() +0x43
orageneric11 +0x4b7316 = kpedbgGetCallStack() +0x200
orageneric11 +0x864fc3 = skge_sign_fr() +0x2a9
kernel32 +0x9febe = UnhandledExceptionFilter() +0x135
MSVCR71 +0xc456 = XcptFilter() +0x15f
MSVCR71 +0x957c = endthreadex() +0xb7
kernel32 +0x4d0e9 = BaseThreadInitThunk() +0x12
ntdll +0x416c3 = RtlInitializeExceptionChain() +0x63
ntdll +0x41696 = RtlInitializeExceptionChain() +0x36

The orageneric11.dll has the version: orageneric11.dll, or higher
This call stack pattern is misleading and does not represent the actual situation on the process stack that has caused the crash. 




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

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