To bring the secondary server back online, connect the primary server with the secondary server. For more information, see Connecting HotStandby servers.
After you bring a secondary server online, it might need to catchup with changes made to the primary server. While the primary server is in PRIMARY ALONE state, the primary server writes transactions and data to the transaction log. When the secondary server is connected to the primary server again, the pending changes on the primary server are written from the transaction log to the secondary server for synchronization. While the changes are written to the secondary server, the secondary server is in SECONDARY ALONE state and the primary server is in PRIMARY ALONE state. If you run the command ADMIN COMMAND 'hsb status connect', the return message indicates whether the servers are performing catchup.
Note If the primary server was set to the STANDALONE state by using the commandhotstandby set standalone, the full database must be copied from the primary server to the secondary server before the secondary server can be switched to SECONDARY ACTIVE state. For more information, see Synchronizing primary and secondary servers.
After the secondary server finishes processing the pending changes, the primary and secondary server states are automatically changed to PRIMARY ACTIVE and SECONDARY ACTIVE respectively.