Oracle Restart

Grid Infrastructure is also available for installation on a stand-alone server and consists of the following:
1. Managed by the Oracle High Availability Serviced daemon OHASD
2. During the installation steps choose configure the Oracle GI for standalone Server
3. This will create OLR as there is no OCR in non-clustered environment
4. OLR location is
5. Database and Database Listeners needed to added to OLR for Oracle Restart using srvctl
6. Grid Infrastructure for a standalone server is a combination of a Clusterware subset known as Oracle Restart and ASM
7. It is started by init using the /etc/init.d/ohasd script and starts the ohasd.bin executable as root.
8. Linux /etc/inittab entry
    h1:35:respawn:/etc/init.d/init.ohasd run >/dev/null 2>&1

Benefits of using Oracle Restart:
1. Automatic resource startup at boot time without using shell scripts or the Oracle supplied dbstart and dbshut scripts in Oracle Home.
2. Resources are started in the correct sequence based on dependencies in the OLR.
3. Resources are also monitored by ohasd for availability and may be restarted in place if they fail.
4. Role managed services for Data Guard.
5. Consistency of command line interfaced tools using crsctl and srvctl as is done with clusters.
6. Adding the standby database to oracle restart
srvctl add database -d PS -o /u01/app/oracle/ps/11.2.0.3 -r PHYSICAL_STANDBY -s MOUNT -p '+DATA_PS/PS/spfilePS.ora' -t IMMEDIATE -a 'DATA_PS','FRA_PS'
[oracle@node1:~]$ srvctl config database -d PS
Database unique name: PS
Database name:
Oracle home: /u01/app/oracle/ps/11.2.0.3
Oracle user: oracle
Spfile: /u01/app/oracle/ps/11.2.0.3/dbs/spfilePS.ora
Domain:
Start options: mount
Stop options: immediate
Database role: PHYSICAL_STANDBY
Management policy: AUTOMATIC
Database instance: PS
Disk Groups: DATA_PS,FRA_PS
Services:
[oracle@node1:~]$
7. Adding Disk Group to create dependency with database restart and disk groups in above command is particularly important as Oracle Restart will attempt to start the database even before confirming the disks are mounted.
8. Adding the listener if it is same as ASM listener and uses the different oracle home
srvctl add listener -o /u01/app/oracle/ps/11.2.0.3
Managing the Oracle Restart
1. crsctl start has – to manually start the Oracle Restart stack when running disabled or after manually stopping it
2. crsctl stop has [-f] – to manually stop the Oracle Restart stack. The -f option
3. crsctl enable has – to enable the stack for automatic startup at server reboot
4. crsctl disable has – to disable the stack for automatic startup at server reboot
5. crsctl config has - to display the configuration of Oracle Restart
6. crsctl check has – to check the current status of Restart
Some of the crsctl commands used for clusters may also be used for Oracle Restart
crsctl stat res -t – to check the status of the resources
crsctl start res – to start individual resources
crsctl stop res – to stop individual resources