Starting and Stopping Grid Infrastructure on a Standalone GI Installation

Starting and Stopping Grid Infrastructure on a Standalone GI Installation

To start and stop Grid Infrastructure services for a standalone installation, there are slightly different commands. Using same commands as RAC to start and stop the GI resources would return errors as follows

[root@~]$ /u01/app/11203/grid/bin/crsctl stop crs CRS-4013: This command is not supported in a single-node configuration. CRS-4000: Command Stop failed, or completed with errors. [root@ ~]$ /u01/app/11203/grid/bin/crsctl stop cluster -all CRS-4013: This command is not supported in a single-node configuration. CRS-4000: Command Stop failed, or completed with errors.

Let’s see how to start and stop the services. First, check status of currently running services

grid ~]$ crsctl stat res -t -------------------------------------------------------------------------------- NAME           TARGET  STATE        SERVER                   STATE_DETAILS -------------------------------------------------------------------------------- Local Resources -------------------------------------------------------------------------------- ora.LISTENER.lsnr                ONLINE  ONLINE       dbserver01 ora.ORADATA.dg                ONLINE  ONLINE       dbserver01 ora.ORAFRA.dg                ONLINE  ONLINE       dbserver01 ora.ORAREDO.dg                ONLINE  ONLINE       dbserver01 ora.asm                ONLINE  ONLINE       dbserver01             Started ora.ons                OFFLINE OFFLINE      dbserver01 -------------------------------------------------------------------------------- Cluster Resources -------------------------------------------------------------------------------- ora.myproddb.myservice.svc       1        ONLINE  ONLINE       dbserver01 ora.myproddb.db       1        ONLINE  ONLINE       dbserver01             Open ora.cssd       1        ONLINE  ONLINE       dbserver01 ora.diskmon       1        OFFLINE OFFLINE ora.evmd       1        ONLINE  ONLINE       dbserver01

Stopping Grid Infrastructure and HAS (High Availability Service)

To stop all services (including database services running from database home registered with this Grid Infrastructure), use following command. After stopping all resources, we will also stop High Availability Service (has).

grid ~]$ crsctl stop res -all CRS-2500: Cannot stop resource 'ora.diskmon' as it is not running CRS-2500: Cannot stop resource 'ora.ons' as it is not running CRS-2673: Attempting to stop 'ora.evmd' on 'dbserver01' CRS-2673: Attempting to stop 'ora.ORADATA.dg' on 'dbserver01' CRS-2673: Attempting to stop 'ora.ORAFRA.dg' on 'dbserver01' CRS-2673: Attempting to stop 'ora.ORAREDO.dg' on 'dbserver01' CRS-2673: Attempting to stop 'ora.myproddb.myservice.svc' on 'dbserver01' CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'dbserver01' CRS-2677: Stop of 'ora.myproddb.myservice.svc' on 'dbserver01' succeeded CRS-2673: Attempting to stop 'ora.myproddb.db' on 'dbserver01' CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'dbserver01' succeeded CRS-2677: Stop of 'ora.evmd' on 'dbserver01' succeeded CRS-2677: Stop of 'ora.myproddb.db' on 'dbserver01' succeeded CRS-2677: Stop of 'ora.ORADATA.dg' on 'dbserver01' succeeded CRS-2677: Stop of 'ora.ORAREDO.dg' on 'dbserver01' succeeded CRS-2677: Stop of 'ora.ORAFRA.dg' on 'dbserver01' succeeded CRS-2673: Attempting to stop 'ora.asm' on 'dbserver01' CRS-2677: Stop of 'ora.asm' on 'dbserver01' succeeded CRS-2673: Attempting to stop 'ora.cssd' on 'dbserver01' CRS-2677: Stop of 'ora.cssd' on 'dbserver01' succeeded CRS-4000: Command Stop failed, or completed with errors. grid ~]$ crsctl stop has CRS-4133: Oracle High Availability Services has been stopped.

Stopping Grid Infrastructure and HAS (High Availability Service)

grid ~]$ crsctl start has CRS-4123: Oracle High Availability Services has been started. grid ~]$ crsctl start res -all CRS-5702: Resource 'ora.evmd' is already running on 'dbserver01' CRS-2501: Resource 'ora.ons' is disabled CRS-2672: Attempting to start 'ora.LISTENER.lsnr' on 'dbserver01' CRS-2672: Attempting to start 'ora.cssd' on ' dbserver 01' CRS-2672: Attempting to start 'ora.diskmon' on 'dbserver01' CRS-2676: Start of 'ora.diskmon' on 'dbserver01' succeeded CRS-2676: Start of 'ora.LISTENER.lsnr' on 'dbserver01' succeeded CRS-2676: Start of 'ora.cssd' on 'dbserver01' succeeded CRS-2672: Attempting to start 'ora.asm' on 'dbserver01' CRS-2676: Start of 'ora.asm' on 'dbserver01' succeeded CRS-2672: Attempting to start 'ora.ORADATA.dg' on 'dbserver01' CRS-2672: Attempting to start 'ora.ORAFRA.dg' on 'dbserver01' CRS-2672: Attempting to start 'ora.ORAREDO.dg' on 'dbserver01' CRS-2676: Start of 'ora.ORADATA.dg' on 'dbserver01' succeeded CRS-2676: Start of 'ora.ORAFRA.dg' on 'dbserver01' succeeded CRS-2676: Start of 'ora.ORAREDO.dg' on 'dbserver01' succeeded CRS-2672: Attempting to start 'ora.myproddb.db' on 'dbserver01' CRS-2676: Start of 'ora.myproddb.db' on 'dbserver01' succeeded CRS-2672: Attempting to start 'ora.myproddb.myservice.svc' on 'dbserver01' CRS-2676: Start of 'ora.myproddb.myservice.svc' on 'dbserver01' succeeded

Stopping and Starting a single Grid Infrastructure Resource

A single resources, such as Listener can be stopped and started as follows.

grid~]$ crsctl stop res ora.LISTENER.lsnr CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'dbserver01' CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'dbserver01' succeeded grid ~]$ crsctl start res ora.LISTENER.lsnr CRS-2672: Attempting to start 'ora.LISTENER.lsnr' on 'dbserver01' CRS-2676: Start of 'ora.LISTENER.lsnr' on 'dbserver01' succeeded