Siebel Server Down and Not Coming Up When Gateway Shifts Node In Cluster Environment.
SymptomsOne of Siebel server was not getting failover to other node if gateway was getting failover.
Below were scenarios observed in Customer's environment.
For Scenario1:
Gateway and Siebel Server1 is running on Node1
Siebel Server2 is running on Node2
Customer is able to start both siebel servers and fail over is happening properly.
For Scenario2:
Gateway and Siebel Server2 is running on Node2
Siebel Server1 is running on Node1
Customer is able to start both Siebel servers but fail over for siebel server2 is not happening.
So problem was with Siebel server2 when gateway is running on Node2
Cause
There were separate data sources in each cluster node for each server i.e. for Siebel Server1, Siebel Server2 and for Gateway Server. In case of second scenario, Siebel Server2 was not coming up giving below error: (listener.cpp (172) err=2555922 sys=0) SBL-SCM-00018: Could not open connection to Siebel Gateway configuration store
On further investigation Siebel servers service entry showed incorrect gateway server entry for second siebel server.
Solution
Updating registry for second siebel server 'service entry' with proper gateway entry followed by reboot of cluster box solved the issue.
Related Posts
No comments :