Siebel Server Service Fails To Start With Errcode=5001 followed by "SBL-SCM-00008: Batch read operation failed" Error after OS update
(Doc ID 2975242.1)
Last updated on NOVEMBER 03, 2023
Applies to:
Siebel CRM - Version 17.0 [IP2017] and laterGeneric Linux
Symptoms
Outage in Siebel environments after updating the OS to newer version, in this particular case to Red Hat 8.8 release, on all Siebel machines.
After OS update the Siebel Server service is failing to start and this behavior is observed in all Siebel environments (DEV, Test, and higher).
The issue can be reproduced at will with the following steps:
1. Stop Siebel Services
2. Update OS to Red Hat ES 8.8 and Kernel version 4.18.0-477.15.1.el8_8.x86_64 or newer version
3. Restart Siebel machines
4. Start Siebel services
5. Siebel Server service is failing to start due to error: SBL-SCM-00008: Batch read operation failed
In order to gather detailed logging the following steps can be applied on affected Siebel Server machine:
1. source the siebenv.sh script in new putty session
2. export the log events environment variable using command:
export SIEBEL_LOG_EVENTS=5
3. trace the "start_server all" instruction using command:
strace -v -f -s 8192 -o strace.txt start_server all
4. Review the strace output along with SiebSrvr logs generated and search for the following errors.
In SiebSrvr.log search for errcode=5001 and SBL-SCM-00008 error.
ScmLayerLog Debug 5 <date> Keyname: [/enterprises/<enterprise_name>/servers/<server_name>/component groups/echannel/components/<component_alias_name>/events/SessMgr/handlers/EventLog]
ScmLayerLog Debug 5 <date> Keyname: [/enterprises/<enterprise_name>/component groups/echannel/components/<component_alias_name>/events/SessMgr/handlers/EventLog]
ScmLayerLog Debug 5 <date> Keyname: [/enterprises/<enterprise_name>/servers/<server_name>/events/SessMgr/handlers/EventLog]
NameServerLayerLog Debug 5 <date> CSSNSClient::Lock(), lockTime:0.000000, m_nLocks:1, m_tid:701544192
GenericLog GenericError 1 <date> Key (/enterprises/<enterprise_name>/servers/<server_name>/events/trigger level): errcode=5001
GenericLog GenericError 1 <date> (scmnsclnt.cpp (352) err=2555912 sys=0) SBL-SCM-00008: Batch read operation failed
GenericLog GenericError 1 <date> (scfutil.cpp (381) err=2555912 sys=0) SBL-SCM-00008: Batch read operation failed
ScfLayerLog Error 1 <date> Error countered after reading 1 components. Last component read is <component_alias_name>
In strace output search for CSSNSClient::Lock() function followed by errcode=5001 and SBL-SCM-00008.
607892 write(7, "tDebug\t1\t0000000264f04694:0\<date>\tKeyname: [/enterprises/<enterprise_name>/servers/<server_name>/events/<component_alias_name>/events/trigger level]\n
NameServerLayerLog\tDebug\t1\t0000000264f04694:0\<date>\t701544192: CSSNSClient::Lock(), lockTime:0.000000, m_nLocks:1,
. . .
607892 write(7, "GenericLog\tGenericError\t1\t0000000264f04694:0\<date>\tKey (/enterprises/<enterprise_name>/servers/<server_name>/events/<component_alias_name>/events/trigger level): errcode=5001\n\n", 159 <unfinished ...>
. . .
607892 write(7, "GenericLog\tGenericError\t1\t0000000264f04694:0\t2023-08-31 10:39:11\t(scmnsclnt.cpp (352) err=2555912 sys=0) SBL-SCM-00008: Batch read operation failed\n", 148 <unfinished ...>
If the OS is rollback to previous version the Siebel Service become functional again.
Changes
Update Red Hat to 8.8 release.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |