Your Data Guard environment has two remote physical standby databases.
Client applications use the local naming method to define connectivity to the primary database instance.
Which will automatically redirect clients to the new primary database in case of a switchover or failover?
Create a database service on the standby databases; automate the start of the service after a role change,
and modify the connection description on the clients to use that service.
Configure a PRIMARY role service on the Primary and Standby and modify the Client connect descriptor to
include both Primary and the Standby.
Set the DB_NAME parameter identically on all databases; modify the connection descriptor on the clients to
use DB_NAME to connect to the primary database instance.
Set the LOCAL_LISTENER parameter for all the database instances, to register services with the default
listener on the primary database host.
Example of error:
”TNS: could not resolve the connect identifier specified”
A connection to a database or other service was requested using a connect identifier, and the connect identifier
specified could not be resolved into a connect descriptor using one of the naming methods configured.
– Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.
– If you are using local naming (TNSNAMES.ORA file):
– Make sure that “TNSNAMES” is listed as one of the values of the NAMES.DIRECTORY_PATH
parameter in the Oracle Net profile (SQLNET.ORA)
– Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.
– Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched