How to use Oracle Clusterware to protect a single instance database
In Oracle 10g it is possible to use the Oracle Clustersoftware to protect single instance databases as well as cluster databases.
There is a new set of code samples on OTN and a brilliant white paper by the authors Philip Newlan and Roland Knapp, which shows how to protect a Single Instance Oracle Database with Oracle Clusterware.
It is packed into a .zip file and contains the white paper plus a number of little perl scripts:
- a script to start / stop / check the Oracle Listener in a cold failover configuration.
- a script for start / stop / check the Oracle Instance in a cold failover configuration.
- a script for start / stop / check the Oracle ASM Instance in a cold failover configuration
The white paper covers three different case studies:
(here is an excerpt from the white paper)
- Case 1 No Oracle Software installed on either node
- Case 2 Oracle with datafiles installed into a local instance of ASM
- Case 3 Oracle with datafiles installed onto a local filesystem
The ‘ending case’ configuration for each of these is as follows:
- Case 1 Oracle Clusterware installed onto both nodes, Clustered ASM installed onto both nodes in the cluster, Single Instance Database Home on each node. In this case Oracle Clusterware automatically protects the ASM instance (by default). This section discusses scripts to protect the single Instance database.
- Case 2 Oracle Clusterware installed onto both nodes, ASM instance ready to be started on new node. New database home on 2nd node, . This paper discusses scripts to protect the Listener, ASM and single Instance database. In this case the
ASM instance is non-clustered.
- Case 3 Oracle Clusterware installed onto both nodes, OCFS 2 installed as a
common shared filesystem for the datafiles. Local Oracle Homes on each node. This paper discusses scripts to protect the listener and single Instance database.