PRIMECLUSTER Wizard for Oracle Configuration and Administration Guide 4.2 - Linux for Itanium -

3.2.1.1 Oracle must be stopped

If Oracle must be stopped, change the settings as follows:

1. Monitoring disruption

   # hvoradisable -a <userApplication>

   
   

2. Oracle stop

   # su - <Oracle user>
   $ sqlplus /nolog
   SQL> connect / as sysdba
   SQL> shutdown immediate

3. Confirmation of stop monitoring
   Confirm stop monitoring was normally done.
   (Refer to note of "4.1 hvoradisable - Discontinue Monitoring Resources".)

4. Setup change
   Change Oracle settings such as initialized parameters and data files.

5. Oracle startup

   # su - <Oracle use>
   $ sqlplus /nolog
   SQL> connect / as sysdba
   SQL> startup

6. Monitoring restart

   # hvoraenable -a <userApplication>

7. Confirmation of restart monitoring
   Confirm restart monitoring was normally done.
   (Refer to note of "4.2 hvoraenable - Restart Monitoring Resources".)

If there are Oracle-dependent resources, the procedure with the monitoring disruption command might not work. When Oracle resources are stopped with the monitoring disruption command then Oracle is stopped manually, the Oracle-dependent resource might fail.

You need to check the status of the Oracle-dependent resource when you stop Oracle manually.