Siebel Application Crashes With Error SBL-OSD-02011 segment violation (SIGSEGV) When High Number Of Concurrent Locks Are Made on Siebel File System (sfs) in OCI File Storage Service (FSS) (Doc ID 2908036.1)

Last updated on JUNE 25, 2024

Applies to:

Symptoms

After increasing the user load in Production environment for Siebel Application, Siebel processes for components like Application Object Manager, EAI, Workflow or other batch components has started crashing.

The issue can be reproduced at will with the following steps:

1. Start Siebel Server service;

2. Allow end users to login in Siebel Application;

3. The crash will occur during peak hours.

The first evidence of the problem is SBL-OSD-02011 error that is reported continuously for all Siebel components in EnterpriseServerName.SiebelServerName.log:

The size of core file generated for crashed process is below 1.8 GB. No fdr or crash.txt file is generated.

The corresponding function key sequence extracted from call stack of core files is:

The behavior is reported for Siebel Application that is running in OKE cluster (OKE - Container Engine for Kubernetes) and Siebel File System (sfs) on OCI File Storage Service (FSS) is mounted as NFSv3, without -nolock option.

Cause

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