Siebel Servers Failing To Start With Error "SBL-SCM-00018: Could not open connection to Siebel Gateway configuration store" When Primary Gateway Node is Down with Gateway Native Clustering (Doc ID 2905206.1)

Last updated on APRIL 19, 2024

Applies to:

Symptoms

Siebel servers are failing to start when primary gateway node is down .

It is 5 node gateway clustering deployed with 20+ siebel servers where gateway nodes are distributed across multiple data centers DC1 (Gateway1 + Gateway2), DC2 (Gateway3 + Gateway4) and DC3 (Gateway5). While performing DR activity that is shutdown DC1 (Gateway1 + Gateway2) and bring up DC2(Gateway3 + Gateway4) & DC3(Gateway5), Siebel servers are failing to start and it keep trying to connect Gateway1 instead of retrying available node. Also all metafiles in gateway & Siebel servers still updated with Gateway1 information though this node (both registry & cgw) are down.

Ideally siebel server should try to connect another available node but this is not happening. Also metafile is still having Gateway1 reference which is causing this behavior.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1) Siebel Enterprise deployed with 5 node Gateway cluster + 20+ Siebel servers + 4 AI servers

2) Stop complete enterprise

3) Bring up Gateway3, Gateway4 & gateway5 out of 5 nodes which is fine to maintain zookeeper quorum

4) Start Siebel servers, servers are failing to start and trying to connect Gateway1.

5) metafile is also updated with Gateway1 information, where this node completely down

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.