Hi,
Either you are connecting via connection manager or by a floating DBSERVERNAME.
Both is not compatible.
Connection manager needs to have distinguished names of the connected engines and, for automatic failover
a HA_ALIAS declaration, which points to the network based connection.
You could also have a setup where a server name is shared and the IP is migrated from one server to another,
and then the listener is activated, when the primary instance is losts.
This would be done without connection manager (manually or with support of an external tool like keepalived).
But this behaviour is not compatible with connection manager.
So what would be the purpose of the common DBSERVER name in a connection manager ruled environment ?
Best,
Original Message:
Sent: 6/26/2024 10:05:00 AM
From: Dennis Melnikov
Subject: Duplicate DBSERVERALIAS
Hi,
The Admin's Guide declares,
Each database server across all of your associated networks must have a unique database server name.
Nevertheless, our primary and RSS are sharing the same name in DBSERVERALIASES.
What is a risk of having duplicate dbserver names?
BTW, online.log is filled with messages,
Registration of Connection Manager %s is rejected because its name is not unique.
What a chance is it results from duplicate names?
------------------------------
Sincerely,
Dennis
------------------------------