Siebel System Admin, Install and Upgrade (MOSC)

MOSC Banner

Siebel Server is not coming up after IP2017 install and completing the DB upgrade

edited Apr 16, 2018 5:36AM in Siebel System Admin, Install and Upgrade (MOSC) 7 commentsAnswered

Hi Team,

We have done upgrade from 8.1.1.11 to IP2017. We have completed the upgrep +upgphys including IRM.

After that we have recreated services for gateway and siebel server using siebctl command. Now when we try to start siebel server it is not coming up. when i enter list_server all it shows like below

started at Mon Oct  9 14:12:11 2017, pid: 14659 (Service process is not running), autostart: no

And the Siebsrvr.log shows something like

ameServerLayerLog Info 3 0000000259db3943:0 2017-10-09 14:12:09 -153250096: CSSNSClient::CSSNSClient() successfully initialized, m_bNewLocking: False

NameServerLayerLog Debug 5 0000000259db3943:0 2017-10-09 14:12:09 -153250096:   CSSNSClient::Lock(), lockTime:0.003000, m_nLocks:1, m_tid:-153250096

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

SBL Sys Admin Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center