Stopping Recovery Appliance Services

You must stop the Recovery Appliance services, Oracle Database File System, Oracle Database, and the cluster services.

To stop the Recovery Appliance services:

1. Disable the keystore as part of appliance shutdown. If the keystore is not created, skip this step.

   If a keystore is created, this is required to stop the HSM wallet for copy to cloud encryption.

   Before appliance shutdown, run:

   [root@myhost ~]# racli disable keystore
   [root@myhost ~]# racli status keystore
          Node: zdlra41
   Wallet Type: HSM
        Status: Closed
          Node: zdlra42
   Wallet Type: HSM
        Status: Closed

2. Log in as oracle to either Recovery Appliance compute server.

3. Open a SQL connection to Oracle Database as the rasys user:

   $ sqlplus rasys

4. Check the status of the services:

   SQL> SELECT state FROM ra_server;
   
   STATE
   ------------
   ON

5. Shut down Recovery Appliance services:

   SQL> exec dbms_ra.shutdown;
   

6. Disconnect from Oracle Database:

   SQL> exit

7. If Oracle Secure Backup is configured:

   1. Switch to the root user.

   2. Check the current status of Oracle Secure Backup:

      # $GRID_HOME/bin/crsctl status res osbadmin
        NAME=osbadmin
        TYPE=cluster_resource
        TARGET=ONLINE
        STATE=ONLINE on example01adm04

   3. If Oracle Secure Backup is online, then stop it:

      # $GRID_HOME/bin/crsctl stop res osbadmin

   4. Switch back to the oracle user.

8. Check the status of Oracle Database:

   $ srvctl status database -d zdlra5
   Instance zdlra51 is running on node radb07
   Instance zdlra52 is running on node radb08

9. Stop Oracle Database:

   $ srvctl stop database -d zdlra5

10. Verify that Oracle Database is stopped:

    $ srvctl status database -d zdlra5
    Instance zdlra51 is not running on node radb07
    Instance zdlra52 is not running on node radb08

11. Switch to the root user.

12. Stop the Oracle Clusterware stack on all nodes in the cluster:

    # $GRID_HOME/bin/crsctl stop cluster -all
    CRS-2673: Attempting to stop 'ora.crsd' on 'zdlradb07'
    CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on
    'zdlradb07'
    CRS-2673: Attempting to stop 'ora.LISTENER_SCAN2.lsnr' on 'zdlradb07'
    CRS-2673: Attempting to stop 'ora.LISTENER_SCAN1.lsnr' on 'zdlradb07'
         .
         .
         .
    #

    If the command fails, reenter it with the -f option.

13. On each compute server, run the following command to stop the Oracle Cluster Ready Services (CRS):

    # $GRID_HOME/bin/crsctl stop crs
    CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'radb08'
    CRS-2673: Attempting to stop 'ora.crf' on 'radb08'
    CRS-2673: Attempting to stop 'ora.mdnsd' on 'radb08'
         .
         .
         .
    CRS-2677: Stop of 'ora.crf' on 'radb08' succeeded
    CRS-2677: Stop of 'ora.mdnsd' on 'radb08' succeeded
    CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'radb08' has completed
    CRS-4133: Oracle High Availability Services has been stopped.
    

14. Shut down or reboot the hardware as required, in the following order:

    1. Compute servers

    2. Storage servers

    3. Rack and switches