The connect string that the Primary uses to connect to the Secondary server is specified using the HotStandby.Connect parameter.

You can view current connect settings in the Primary and Secondary nodes by issuing the command:

If the connection between the Primary and Secondary servers is broken or not yet established, you must issue the following command at the Primary or Secondary node:

For example, after performing a netcopy, you normally connect the servers. Since there is no automatic connect mechanism in the HotStandby servers, your high availability control application must issue the command when the connection between the servers is broken.

After issuing this command, a confirmation message is displayed if the connection between the Primary and Secondary servers is successful. If the Primary and Secondary are connected, but the transaction log is not yet fully copied at the Secondary, the Primary server returns the following message: Started the process of connecting the servers.

If the state of the Primary server was PRIMARY UNCERTAIN or PRIMARY ALONE when you issued the command, and if the connection is successful, the state of the Primary server changes to PRIMARY ACTIVE. If unsuccessful, the state remains PRIMARY UNCERTAIN or PRIMARY ALONE.

For more information about querying the connect status at Primary and Secondary servers, see Displaying connect status information. For more information about reconnecting an application to the Primary server, see Reconnecting to primary servers from applications.