Stopping and Restarting Oracle Restart for Maintenance Operations

When several components in an Oracle home are managed by Oracle Restart, you can stop Oracle Restart and the components managed by Oracle Restart in the Oracle home. You can also disable Oracle Restart so that it is not restarted if the node reboots. You might need to do this when you are performing maintenance that includes the Oracle home, such as installing a patch. When the maintenance operation is complete, you can enable and restart Oracle Restart, and you can restart the components managed by Oracle Restart in the Oracle home.

Use both the SRVCTL utility and the CRSCTL utility for the stop and start operations:

The stop home SRVCTL command stops all of the components that are managed by Oracle Restart in the specified Oracle home. The start home SRVCTL command starts these components. The Oracle home can be an Oracle Database home or an Oracle Grid Infrastructure home.

When you use the home object, a state file, specified in the -s option, tracks the state of each component. The stop and status commands create the state file. The start command uses the state file to identify the components to restart.

In addition, you can check the status of the components managed by Oracle Restart using the status home command.
The stop CRSCTL command stops Oracle Restart, and the disable CRSCTL command ensures that the components managed by Oracle Restart do not restart automatically. The enable CRSCTL command enables automatic restart and the start CRSCTL command restarts Oracle Restart.

To stop and start the components in an Oracle home while installing a patch:

Prepare to run SRVCTL as described in "Preparing to Run SRVCTL".
Use the SRVCTL utility to stop the components managed by Oracle Restart in an Oracle home:
```
srvctl stop home -o oracle_home -s state_file [-t stop_options] [-f]
```
where oracle_home is the complete path of the Oracle home and state_file is the complete path to the state file. State information for the Oracle home is recorded in the specified state file. Make a note of the state file location because it must be specified in Step 7.

Before stopping the components in an Oracle Grid Infrastructure home, ensure that you first stop the components in a dependent Oracle Database home.
If you are patching an Oracle Grid Infrastructure home, then disable and stop Oracle Restart. Otherwise, go to Step 4.

To disable and stop Oracle Restart, use the CRSCTL utility to run the following commands:
```
crsctl disable has

crsctl stop has
```
Perform the maintenance operation.
Use the CRSCTL utility to enable automatic restart of the components managed by Oracle Restart:
```
crsctl enable has
```
Use the CRSCTL utility to start Oracle Restart:
```
crsctl start has
```
Use the SRVCTL utility to start the components that were stopped in Step 2:
```
srvctl start home -o oracle_home -s state_file
```
The state file must match the state file specified in Step 2.
Optionally, use the SRVCTL utility to check the status of the components managed by Oracle Restart in the Oracle home:
```
srvctl status home -o oracle_home -s state_file
```

Example 4-25 Stopping Components Managed by Oracle Restart in an Oracle Home

srvctl stop home -o /u01/app/oracle/product/11.2.0/dbhome_1 -s /usr1/or_state

Example 4-26 Starting Components Managed by Oracle Restart in an Oracle Home

srvctl start home -o /u01/app/oracle/product/11.2.0/dbhome_1 -s /usr1/or_state

Example 4-27 Displaying the Status of Components Managed by Oracle Restart in an Oracle Home

srvctl status home -o /u01/app/oracle/product/11.2.0/dbhome_1 -s /usr1/or_state