After Siebel Monthly Update Installation, The Gateway Cluster Registry Service on Gateway Primary Node Does Not Start. Error QuorumCnxManager$Listener$ListenerHandler@1093] - Exception while listening is Displayed While Starting Up Zookeeper Manually
(Doc ID 2872542.1)
Last updated on JULY 08, 2024
Applies to:
Siebel CRM - Version 22.1 and laterInformation in this document applies to any platform.
Symptoms
The Siebel environment was updated from version 20.5 to 22.1 successfully. No installation errors were encountered.
This is the structure of the Siebel environment:
1. Siebel Cloud Gateway Cluster with three Siebel Gateway nodes (service and registry)
2. Four Siebel Application Servers
3. Two Application Interface (AI) Servers
After the monthly update 22.1 installation, all Siebel modules are up and running, except Gateway registry in primary node.
The following steps can be executed in order to reproduce the behavior:
The details to install a monthly update can be read in Siebel Bookshelf 22.1 > Installation Guide > Roadmap: Installing Siebel CRM in an Update Installation Case (Existing Installation of Siebel CRM 17.x or later)
1. Update all Siebel Application interface (AI) to version 22.1.
2. Update SES to 22.1, including the three Gateways servers .
3. Start up the Siebel system and the Gateway registry service in primary node goes down.
Changes
Siebel monthly update 22.1 was installed on top of version 20.5.
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 |