Last updated on MARCH 02, 2017
Applies to:Siebel System Software - Version 18.104.22.168  to 22.214.171.124 SIA [Release V7 to V8]
z*OBSOLETE: Microsoft Windows Server 2003
Version: 126.96.36.199 
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server
This document was previously published as Siebel SR 38-3155416955.
***Checked for relevance on 27-Feb-2013***
We have recently clustered our Gateway server. The resource resides on a shared disk between two servers LONSEBLGW01(primary node) and LONSEBLGW02 (secondary node).
The installation was successful and we are able to failover without any problems.
However when the cluster is moved to the secondary node and Siebel servers are re-started they do not recognise the Gateway server. I strongly suspect that this is because pre-cluster the Gateway was only on LONSEBLGW01 and this is when all of the Siebel servers were installed. These Siebel servers obviously still reference the physical machine LONSEBLGW01 and this explains why they work when the primary node is active.
I've looked at SR#38-1031389997 and I think we have the same issue. Only this SR doesn't explain what was changed to point to the virtual cluster ip address. Can you let me know where this setting is?
Nb I have changed the Gateway Server params in the siebel.cfg files to point to the cluster.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms