Single 10g Instance to RAC - without ASM migration

Question

Is it possible to comment the following steps to convert existing 10.1.0.5 single instance database to RAC? We're using OCFS2 and it is not possible to perform ASM migration.
1. Copy the existing $ORACLE_HOME/dbs/init<SID1>.ora to
$ORACLE_HOME/dbs/init<db_name>.ora. Add the following parameters to
$ORACLE_HOME/dbs/init<db_name>.ora:
*.cluster_database = TRUE
*.cluster_database_instances = 2
     *.undo_management=AUTO (Add if you don't have it )
<SID1>.undo_tablespace=undotbs (undo tablespace which already exists)
     <SID1>.instance_name=RAC1
     <SID1>.instance_number=1
     <SID1>.thread=1
<SID1>.local_listener=LISTENER_RAC1
where LISTENER_RAC1 is an entry in the tnsnames.ora file like:
LISTENER_RAC1 =
(ADDRESS = (PROTOCOL = TCP)(HOST = <node1>)(PORT = 1521))
Keep only one line in $ORACLE_HOME/dbs/init<SID1>.ora:
ifile=$ORACLE_HOME/dbs/init<db_name>.ora
You could also create a common spfile from this pfile and add a line
like spfile=$ORACLE_HOME/dbs/spfile<db_name>.ora in each init<SIDn>.ora
file. For more details about how to do this, please refer to Note 136327.1.
2. Open your database and run $ORACLE_HOME/rdbms/admin/catclust.sql to create
cluster database specific views within the existing instance.
3. Recreate control file if you defined maxinstances to be 1 when you created
the single instance database.
To check your current setting of maxinstances, run the following command
while the database is mounted or open and connected as a user with DBA
privileges:
% sqlplus /nolog
SQL> connect / as sysdba
SQL> startup mount
SQL> alter database backup controlfile to trace;
The trace file is located in udump directory. Check the maxinstance value
in the CREATE CONTROLFILE statement. Please refer to Note 118931.1
Recreating the Controlfile in RAC and OPS
4. Add instance specific parameters in the init<db_name>.ora for the second
instance on the second node and set appropriate values for it:
     *** Names may need to be modified
     <SID2>.instance_name=RAC2
     <SID2>.instance_number=2
     <SID2>.local_listener=LISTENER_RAC2
     <SID2>.thread=2
     <SID2>.undo_tablespace=UNDOTBS2
<SID2>.cluster_database = TRUE
<SID2>.cluster_database_instances = 2
where LISTENER_RAC2 is an entry in the tnsnames.ora file like:
LISTENER_RAC2 =
(ADDRESS = (PROTOCOL = TCP)(HOST = <node2>)(PORT = 1521))
5. From the first instance, mount the database and run the following command:
     *** Path names, file names, and sizes will need to be modified
alter database
add logfile thread 2
group 3 ('/dev/RAC/redo2_01_100.dbf') size 100M,
group 4 ('/dev/RAC/redo2_02_100.dbf') size 100M;
alter database enable public thread 2;
6. Create a second Undo Tablespace from the existing instance:
     *** Path names, file names, and sizes will need to be modified
CREATE UNDO TABLESPACE UNDOTBS2 DATAFILE
     '/dev/RAC/undotbs_02_210.dbf' SIZE 200M ;
7. Set ORACLE_SID and ORACLE_HOME environment variables on the second node.
8. Start the second Instance.

Answer 1

In order not to affect the current home on node1, another user oracle2 is created which belong to racinstall group. On node2, which doesn’t have any oracle home installed, CRS will be installed so that node2 will become the primary node.
Been looking into this CRS for sometime as the installation has failed due to OCFS2 kernel panic upon running root.sh on the second node. Performed the cleanup as described Doc ID: Note:239998.1 (10g RAC: How to Clean Up After a Failed CRS Install), but now, the installation is failing and giving the error “ File not found /ClusterCRS/install/rootadd”. This message didn’t appear the first attempt which could indicate that the cleanup described in the note was not sufficient.