High Availability Guide : Administering and configuring HotStandby : Administering HotStandby with ADMIN COMMANDs (HotStandby API) : Shutting off HotStandby operations
  
Shutting off HotStandby operations
You might want to shut off HotStandby operations temporarily in the Primary server, for example, if you are taking the Secondary server out of service to upgrade it and the Primary does not have enough disk space to store the transaction logs that accumulates while the Secondary is out of service.
About this task
(See Running out of space for transaction logs for more details.)
To shut off HotStandby at the Primary server:
Procedure
1 Disconnect the servers (if they are currently connected).
2 Set the Primary server to STANDALONE state, using the following sequence of commands:
ADMIN COMMAND 'hotstandby disconnect'; -- if servers are
                                          connected
ADMIN COMMAND 'hotstandby set standalone';
The Primary server continues to operate as a non-HotStandby server.
Note After you have stopped storing transaction logs to send to the Secondary, you can no longer have the Primary and Secondary servers catch up merely by connecting them again. Instead, you must synchronize the servers manually when you resume HotStandby operations.
What to do next
If you want to permanently stop using the server as a HotStandby server, see Changing a HotStandby server to a non-HotStandby server.
See also
Administering HotStandby with ADMIN COMMANDs (HotStandby API)