PRIMECLUSTER Wizard for Oracle 4.2 Configuration and Administration Guide

3.2.1 Oracle Setting Change

You can change Oracle settings such as initialized parameters and data files using the procedures described below.

Note

Oracle must be stopped depending on the settings. For details, see the Oracle manual.

3.2.1.1 Oracle must be stopped

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

1. Maintenance mode / Monitoring disruption

   # hvutil -m on <userApplication> (Maintenance mode)
   # hvoradisable -a <userApplication> (Monitoring disruption)

2. Oracle stop

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

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

4. Oracle startup

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

5. Monitoring restart / Maintenance mode stop

   # hvoraenable -a <userApplication> (Monitoring restart)
   # hvutil -m off <userApplication> (Maintenance mode stop)

Note

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.