PRIMECLUSTER Wizard for Oracle 4.6 Configuration and Administration Guide

3.2.1 Oracle database Setting Change

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

Note

Oracle database must be stopped depending on the settings. For details, refer to the Oracle Database manual.

3.2.1.1 Oracle database must be stopped

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

1. Maintenance mode / Monitoring disruption

   # /opt/SMAW/SMAWRrms/bin/hvutil -m on <userApplication> (Maintenance mode)
   # /opt/FJSVclora/sbin/hvoradisable -a <userApplication>  (Monitoring disruption)

2. Confirmation of maintenance mode and stop of monitoring

   Confirm that changing into maintenance mode and stop of monitoring have been successfully done.

   (Refer to note of "4.1 hvoradisable - Discontinue Monitoring Resources".)

3. Enable Oracle Restart settings

   Enable Oracle Restart settings if necessary.
   (Refer to "3.2 Oracle database Maintenance".)

4. Oracle database stop

   # su - <Oracle user>
   $ sqlplus /nolog
   SQL> CONNECT / AS SYSDBA
   SQL> SHUTDOWN IMMEDIATE

5. Setup change

   Change Oracle database settings such as initialized parameters and data files.

6. Oracle database startup

   # su - <Oracle user>
   $ sqlplus /nolog
   SQL> CONNECT / AS SYSDBA
   SQL> STARTUP

7. PDB startup(for the database using the multitenant architecture)

   # su - <Oracle user>
   $ sqlplus /nolog
   SQL> CONNECT / AS SYSDBA
   SQL> ALTER PLUGGABLE DATABASE ALL OPEN;

8. Disable Oracle Restart settings

   If "3. Enable Oracle Restart settings" is executed, disable Oracle Restart settings.
   (Refer to "3.2 Oracle database Maintenance".)

9. Monitoring restart / Maintenance mode stop

   # /opt/FJSVclora/sbin/hvoraenable -a <userApplication>(Monitoring restart)
   # /opt/SMAW/SMAWRrms/bin/hvutil -m off <userApplication> (Maintenance mode stop)

10. Confirmation of restart of monitoring and maintenance mode

    Confirm that restart of monitoring and changing out of maintenance mode has been successfully done.
    (Refer to note of "4.2 hvoraenable - Restart Monitoring Resources".)

11. Restart userApplication

    When the Oracle instance, listener, or ASM is stopped and started manually, restart the userApplication including Oracle resources.

    # hvutil -f <userApplication>
    # hvswitch <userApplication> <SysNode>