You can disable a secondary connection to the primary database server to cause the secondary server to close the connection to its primary server, leaving the connection closed. This places a secondary database in an offline mode in which it can continue tracking and providing read-only database access while not receiving further journals from the primary database.
Use the Reconnect command to attempt to re-establish a connection to the primary server. For details, see "Reconnecting a Secondary Database", later in this chapter.
To disable a secondary database connection to the primary server
Select the secondary database in the database view pane whose connection you want to disable.
Select the Disable Primary Connection command in the Secondary menu. (This command is enabled only when the secondary database is connected to the primary server.)
The connection to the primary server from the selected secondary database is then disabled, the value of the State attribute in the operational state details changes to disconnected, the Disable Primary Connection menu command is disabled, and the Reconnect menu command is enabled.
When you disconnect a secondary database, only a subset of details for that secondary database are available for display on the primary system.
You can also use the Disable Primary Connection command to clear and re-establish a disrupted network link. In the event that a connection becomes disrupted because of a problem in the network path, use the Disable Primary Connection command to drop the failed connection and the Reconnect command to attempt to establish a fresh network connection.
For details, see "Disabling a Connection to the Primary Database", in the previous section.