Protecting a single instance database using ASM and oracle Clusterware has been made simpler in 11g.
I did follow the instructions from Philip Newlan Paper "Using Oracle Clusterware to Protect A Single Instance Oracle Database 11g" and produced a step by step list of implementing this procedure on an existing cluster on Linux.
This is the report I've produced: Protecting a single instance with Oracle Clusterware 11g
This is a summary of the implementation steps:
1. Create a single instance on one of the nodes of an existing Oracle Cluster
2. Add a new virtual IP’s to /etc/hosts
3. Add to listener.ora a new Listener on both nodes
4. Add to tnsnames.ora the new listener on both nodes
5. Setup Management Scripts on $CRS_HOME/crs/public On Both Nodes
6. Create and register “resource group” rg1 for the instance to protect
7. Create and register the resource rg1.vip
8. Change the new resource vip permissions to root
9. Check the new vip by starting it
10. Test the application Listener
11. Create and register resource rg1.listener
12. Prepare the database to be registered as a cluster resource of the rg1 group
13. Create and register resource rg1.db_protsing for the protsing database
14. Test relocating the group
15. Create and register resource rg1.head that contros startup order of rg1 resources
16. Check that the resources on the group start
17. Test planned failover
18. Test unplanned failover
19. Test failover on node crash
