I have found during some administrative tasks it is easier to have your system in single NODE configuration. An example of this, would be physical changes the database structure that due not include binary upgrades such as a CPU patch. It is easier to startup, shutdown, and restrict access thorough single stand alone system, rather then a RAC environment with several active nodes. I realize that most of you are quite verse in the user of the SRVCTL utility to administrate the instances and database. However, I would like to show the use of starting up the database in single node from within the database and using SRVCTL just to verify the status.
1. Logon to one node as sysdba.
mylinux1>$ sqlplus ‘/ as sysdba’
SQL*Plus: Release 10.2.0.4.0 – Production on Thu Sep 3 18:47:59 2009
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 – Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options
SQL>
2. Execute the following SQL “select inst_id, instance_name, instance_role, host_name from gv$instance;†and as you can see we are attached to a two node RAC.
SQL> select inst_id, instance_name, instance_role, host_name from gv$instance;
INST_ID INSTANCE_NAME INSTANCE_ROLE HOST_NAME
———- ————– —————– ——————
1 node1 PRIMARY_INSTANCE mylinux1
2 node2 PRIMARY_INSTANCE mylinux2
SQL>
3. Exit out of SQL*PLUS and use the SRVCTL utility to obtain the current RAC status. The utility SRVCTL verifies what we saw in the data dictionary view of GV$INSTANCE.
mylinux1>$ srvctl status database -d orcl
Instance node1 is running on node mylinux1
Instance node2 is running on node mylinux2
4. Due to the fact that we have two instance running, we will use the SRVCTL utility to shutdown the database.
mylinux1>$ srvctl stop database -d orcl
5. Again use the SRVCTL utility to view the status of your Instances and the results are displayed that both instance are shutdown.
srvctl status database -d orcl
Instance node1 is not running on node mylinux1
Instance node2 is not running on node mylinux2
mylinux1>$
6. Now you do have a choice here: 1. You could startup the database and a single instance with the SRVCTL utility or 2. You could logon to SQL*PLUS like a non-RAC system and startup the instance and database. We will logon to SQL*PLUS as sysdba and issue the startup command.
mylinux1>$ sqlplus ‘/ as sysdba’
SQL*Plus: Release 10.2.0.4.0 – Production on Thu Sep 3 19:02:13 2009
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 1795162112 bytes
Fixed Size 1262332 bytes
Variable Size 587205892 bytes
Database Buffers 1191182336 bytes
Redo Buffers 15511552 bytes
Database mounted.
Database opened.
SQL>
7. Execute the following SQL “select inst_id, instance_name, instance_role, host_name from gv$instance;†to display the results of starting the database from NODE1.
SQL> select inst_id, instance_name, instance_role, host_name from gv$instance;
INST_ID INSTANCE_NAME INSTANCE_ROLE HOST_NAME
———- ————– —————– ——————
1 node1 PRIMARY_INSTANCE mylinux1
SQL>
8. You can verify these results with the SRVCTL utility.
mylinux1>$ srvctl status database -d orcl
Instance node1 is running on node mylinux1
Instance node2 is not running on node mylinux2
mylinux1>$
9. Your system is now executing in a SINGLE NODE fashion and you can began your administrative tasks.
Larry Catt OCP 9i, 10g
oracle@allcompute.com
www.allcompute.com