Siebel Server Does Not Come Up After Successful Profile Deployment Due to SRBroker Termination - [DataDirect][ODBC lib] Specified driver could not be loaded
(Doc ID 2835062.1)
Last updated on JANUARY 21, 2022
Applies to:
Siebel CRM - Version 21.12 and laterInformation in this document applies to any platform.
Symptoms
After successfully deploying a Siebel Server profile the Siebel Server does not come up as expected. The environment has been setup for IBM DB2 Database Server v11.1.
SRBroker is known a required component and it is getting terminated with the following error found in the Siebel Enterprise log file found siebsrvr/enterprises/<enterprise_name>/<siebel_server_name>/log directory:
In the SRBroker log file found on the same log directory the following errors can be found:
ServerLog LstnObjInherit 3 0000000261e86ed2:0 2022-01-19 22:09:06 Inherited listening object for port 49156
ServerLog LstnObjPrivCreate 3 0000000261e86ed2:0 2022-01-19 22:09:06 Created port 49165 for Server Request Broker
DBCLog DBCLogError 1 0000000261e86ed2:0 2022-01-19 22:09:06 [DataDirect][ODBC lib] Specified driver could not be loaded
GenericLog GenericError 1 0000000261e86ed2:0 2022-01-19 22:09:06 (srbthrd.cpp (4106) err=2097168 sys=0) SBL-SRM-00016: Unable to initialize the Database environment -- Unable to connect to DB (data ops)
GenericLog GenericError 1 0000000261e86ed2:0 2022-01-19 22:09:06 (srbmtsrv.cpp (86) err=2097168 sys=0) SBL-SRM-00016: Unable to initialize the Database environment -- Unable to connect to DB (data ops)
SrbLayerLog Error 1 0000000261e86ed2:0 2022-01-19 22:09:06 Main Init fails
GenericLog GenericError 1 0000000261e86ed2:0 2022-01-19 22:09:06 (smimtsrv.cpp (1236) err=2097168 sys=0) SBL-SRM-00016: Unable to initialize the Database environment -- Unable to connect to DB (data ops)
SmiLayerLog Error 1 0000000261e86ed2:0 2022-01-19 22:09:06 Terminate process due to unrecoverable error: 2097168. (Main Thread)
STEPS
The issue can be reproduced at will with the following steps:
1. Create and Deploy the Siebel Enterprise profile
2. Create and Deploy the Siebel Server profile
3. Verify the Siebel Server Enterprise log file
4. The above mentioned SRBroker termination can be verified
Changes
New installation using IBM DB2 Database Server v11.1
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 |