Siebel Server Fail to Start after Database upgrade (Doc ID 1965096.1)

Last updated on JULY 07, 2016

Applies to:

Siebel CRM - Version 8.0 SIA [20405] and later
Information in this document applies to any platform.
**** Checked for relevance on 07-Jul-2016 ****

Symptoms

On : 8.0 SIA [20405] version, System Admin

When attempting to start Siebel servers after DB upgrade
the following error occurs.

ERROR
-----------------------
GenericLog GenericError 1 0000000854c580f6:0 2015-01-25 22:08:23 (scisvc.cpp (502) err=852188 sys=0) SBL-OSD-00220: Internal: pthread_mutex_trylock () failed with err
or. (0)^M
SmiLayerLog Error 1 0000000854c580f6:0 2015-01-25 22:08:28 Error 852188 in smiMainThread::GetSciSyncLatch()^M

Enterprise log shows below error:

GenericLog GenericError 1 0000379854c5207a:0 2015-01-25 19:20:18 (schedule.cpp (1073) err=1376409 sys=0) SBL-SMI-00153: SRProc    NOT READY    Component is not ready.
GenericLog GenericError 1 0000379854c5207a:0 2015-01-25 19:20:18 (schedule.cpp (944) err=1376408 sys=0) SBL-SMI-00152: TIMEOUT    Component initialization for priority level 1 timed out after 300 s.



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1- shutdown the application 8.0 (siebel servers + gateway server) +databse 10g,
2- left the 10 g database as it is for rollback scenario
3- took a clone from production database (10g) on new database servers,
4- upgraded the database to 11.2.0.3 and then we changed the tnsnames.ora on all siebel servers to point on the new database servers
5- Changed the SADMIN password on the database to match the same passowrd configured on the preprod enterprise server
6- verified the connection from siebel servers to the database servers by the below command using the below command:
odbcsql /s esia811_DSN /u sadmin /p <sadmin pwd>
7- startup the gateway and then the rest of the servers

the gateway service started however, the rest of the servers started partially (not all processes) and then it went like below:

(Service process is not running ), autostart: no



Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms