3.2.2 Patch Application

This section discusses how to apply PSR by In-place upgrade in Oracle Database 11g R2/12c R1 or previous version of Oracle Database 11g R1.

Start userApplication (Operating node)
Start userApplication that includes the Oracle instance and listener resources if it is stopped.
Maintenance mode (Operating node)
Start maintenance mode for userApplication on the operating node.
Example
If you start maintenance mode for all userApplication, execute the following command.
```
# /opt/SMAW/SMAWRrms/bin/hvutil -M on
```
Confirm that state of userApplication has become "Maintenance" on all nodes.
Monitoring disruption of Oracle resource (All nodes)
Stop monitoring the Oracle instance and listener resources by executing the "hvoradisable" command on all nodes.
Example
If you stop monitoring all the Oracle resources on a local node, execute the following command.
```
# /opt/FJSVclora/sbin/hvoradisable -a
```
Confirm that states of the Oracle instance and listener resources have become "Warning" on all nodes.
Information
In standby operation, applying Oracle PSR (Patch Set Release) on the standby node without stopping monitoring Oracle resources might cause problems because Oracle database is monitored on the standby node. Therefore it is necessary to stop monitoring them on the standby node.

Oracle database stop (if necessary)

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

Patch application
Apply patches according to the placement of the Oracle Database software.
See
For further details, refer to the Oracle Database manual.

Oracle database startup (if stopped)

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

PDB startup (for the database using the multitenant architecture. and if stopped)

# su - <Oracle user>
$ sqlplus /nolog
SQL> connect / as sysdba
SQL> alter pluggable database all open;

Restart Oracle resource monitoring (All nodes)
Restart monitoring the Oracle instance and listener resources again using the hvoraenable command on all nodes.
Example
If you restart monitoring all the Oracle resources on a local node, execute the following command.
```
# /opt/FJSVclora/sbin/hvoraenable -a
```
Confirm that states of the Oracle instance and listener resources have become the previous state ("Online" or "Offline") from "Warning" on all nodes.
Stop maintenance mode (Operating node)
Stop maintenance mode of userApplication on the operating node.
Example
If you stop maintenance mode for all userApplication, execute the following command.
```
# /opt/SMAW/SMAWRrms/bin/hvutil -M off
```
Confirm that state of userApplication has become the previous state ("Online", "Standby" or "Offline") from "Maintenance" on all nodes.

3.2.2.2 Patch Application by Out-of-place upgrade (Standby Operation, Single-Node Cluster Operation)

This section discusses how to apply PSR by Out-of-place upgrade in standby operation or single-node cluster operation of Oracle Database 11g R2/12c R1.

Note

Upgrade to local disk if the Oracle Database software is located on local disk.
Upgrade to shared disk if the Oracle Database software is located on shared disk.
Changing the placement (local disk, shared disk) of the Oracle Database software at the upgrade does not support.

Start userApplication (Operating node)
Start userApplication that includes the Oracle instance and listener resources if it is stopped.
Maintenance mode (Operating node)
Start maintenance mode for userApplication on the operating node.
Example
If you start maintenance mode for all userApplication, execute the following command.
```
# /opt/SMAW/SMAWRrms/bin/hvutil -M on
```
Confirm that state of userApplication has become "Maintenance" on all nodes.
Monitoring disruption of Oracle resource (All nodes)
Stop monitoring the Oracle instance and listener resources by executing the "hvoradisable" command on all nodes.
Example
If you stop monitoring all the Oracle resources on a local node, execute the following command.
```
# /opt/FJSVclora/sbin/hvoradisable -a
```
Confirm that states of the Oracle instance and listener resources have become "Warning" on all nodes.
Information
In standby operation, applying Oracle PSR (Patch Set Release) on the standby node without stopping monitoring Oracle resources might cause problems because Oracle database is monitored on the standby node. Therefore it is necessary to stop monitoring them on the standby node.
Stop Oracle database-dependent resources (Operating node)
If there are Oracle database-dependent resources, stop them manually before stopping Oracle database.
Applying PSR, and upgrade of database
1. Applying PSR
  - In the case that the Oracle Database software is located on local disk
    Execute the Out-of-place upgrade on all nodes. For information on how to execute the Out-of-place upgrade, refer to the Oracle Database manual.
  - In the case that the Oracle Database software is located on shared disk
    Execute the Out-of-place upgrade on the operating node. For information on how to execute the Out-of-place upgrade, refer to the Oracle Database manual.
  Note
  - Select "Install database software only" on the "Select Installation Option" screen.
  - For details, refer to the Oracle Database manual.
2. Upgrade of database (Operating node)
  Execute dbua (Database Upgrade Assistant) on the operating node, and upgrade the database.
  Note
  - Execute "<New ORACLE_HOME>/bin/dbua".
  - For details, refer to the Oracle Database manual.
3. Move the SPFILE to the shared disk (Operating node)
  Move the SPFILE (server parameter file) to the shared disk when it is newly generated on a local disk after the upgrade of the database is executed. Afterwards, specify SPFILE path to PFILE (the initialization parameter file "<New ORACLE_HOME>/dbs/init<SID>.ora") or make a symbolic link file to SPFILE.
  Note
  If Oracle Database Software is located in shared disk, this step is not necessary.
  See
  For details, see "2.2.6 Oracle database Creation and Setting".
PRIMECLUSTER Wizard for Oracle Settings
1. Login profile Setting Change (All nodes)
  Open Oracle user's login profile with editor (e.g. vi), and change the setting of the ORACLE_BASE and ORACLE_HOME environment variable to new path. Execute this procedure on all nodes.
  Example
  Before changes
```
ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
```
  After changes
```
ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_2
```
  See
  For details, see "2.2.2 Oracle Database Software Installation and Configuration".
2. Transfer PFILE to standby nodes (Operating node, Standby node)
  Create tar archive file from "<New ORACLE_HOME>/dbs" on the operating node.
  Example
```
# su - oracle
$ tar cfpvP /tmp/dbs.tar <New ORACLE_HOME>/dbs
```
  After that, transfer the archive file from the operating node to the standby node by FTP, and expand it.
  Example
```
# su - oracle
$ tar xfpvP /tmp/dbs.tar
```
  Note
  - If Oracle Database Software is located in shared disk, this step is not necessary.
  - This step is not necessary for single-node cluster operation.
  - Do not use the cloracpy command of PRIMECLUSTER Wizard for Oracle on this step.
  - Set the access privilege of files which are expanded on the standby node same as the files on operating node.
  See
  For details, see "2.2.6 Oracle database Creation and Setting".
3. The allocation of Oracle Net Services configuration file
  Copy the Oracle Net Services configuration file from under the <Old ORACLE_HOME> to under the <New ORACLE_HOME>. Execute this procedure on all nodes
  - In the case that the Oracle Database software is located on local disk
    Execute this procedure on all nodes
  - In the case that the Oracle Database software is located on shared disk
    Execute this procedure on the operating node
  Example
```
$ cp -p <Old ORACLE_HOME>/network/admin/*.ora <New ORACLE_HOME>/network/admin/
```
  Note
  - Edit "<New ORACLE_HOME>/network/admin/*.ora" file when there are parameters depending on ORACLE_BASE and ORACLE_HOME in the Oracle Net Services configuration file after copy.
  - Do not use the cloracpy command of PRIMECLUSTER Wizard for Oracle on this step.
Confirming Oracle database Startup (Operating node)
Confirm that Oracle instance and Listener started. If not, start up them manually. Start PDBs manually for the database using the multitenant architecture.
Note
- The Oracle instance should start in the state of OPEN.
- Confirm the process of the listener is as "<New ORACLE_HOME>/bin/tnslsnr".
  If the process of the listener is as "<Old ORACLE_HOME>/bin/tnslsnr", stop it and start as "<New ORACLE_HOME>/bin/tnslsnr".
Start resources dependent on Oracle database (Operating node)
If resources that are dependent on Oracle database had been stopped on step 4, start them manually.
Restart Oracle resource monitoring (All nodes)
Restart monitoring the Oracle instance and listener resources again using the hvoraenable command on all nodes
Example
If you restart monitoring all the Oracle resources on a local node, execute the following command.
```
# /opt/FJSVclora/sbin/hvoraenable -a
```
Confirm that states of the Oracle instance and listener resources have become the previous state ("Online" or "Offline") from "Warning" on all nodes.
Stop maintenance mode (Operating node)
Stop maintenance mode of userApplication on the operating node.
Example
If you stop maintenance mode for all userApplication, execute the following command.
```
# /opt/SMAW/SMAWRrms/bin/hvutil -M off
```
Confirm that state of userApplication has become the previous state ("Online", "Standby" or "Offline") from "Maintenance" on all nodes.
Confirming of switch to the standby node
Confirm the switch of userApplication to the standby node, and the correct start.
Note
- This step is not necessary for single-node cluster operation.
- Confirm step 6 when you cannot correctly start userApplication on the standby node.
Restart service
Switch userApplication to the operating node if necessary, and restart service.

3.2.2.3 Patch Application by Out-of-place upgrade (Scalable Operation with Oracle RAC)

This section discusses how to apply PSR by Out-of-place upgrade in scalable operation with Oracle RAC of Oracle Database 11g R2/12c R1.

Stopping userApplication (All nodes)
Stop userApplication on all nodes to be Offline.
Note
If the Oracle Clusterware resource and the Oracle RAC instance resource are registered in different userApplication, stop userApplications in the following order.
1. userApplication including Oracle RAC instance resource
2. userApplication including Oracle Clusterware
Stopping RMS (All nodes)
Stop RMS on all nodes.
Applying PSR, and upgrade of database (All nodes or any one of them)
To upgrade, execute the following procedure. For details, refer to the Oracle Database manual.
1. Upgrade of Grid Infrastructure Software
2. Upgrade of Oracle Database Software (Oracle RAC)
3. Upgrade of Oracle Database
Changing the login profile setting (All nodes)
Open Oracle user's login profile with editor (e.g. vi), and change the setting of the ORACLE_BASE and ORACLE_HOME environment variable to new path. Execute this procedure on all nodes.
Example
Before changes
```
ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
```
After changes
```
ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_2
```
Setting automatic startup
1. Setting automatic startup of Oracle Clusterware (All nodes)
  Set up automatic startup of Oracle Clusterware. For details about setting, see "2.3.2 Oracle Database Software Installation and Configuration".
2. Disabling automatic startup of Oracle RAC instance (any one of the nodes)
  Confirm that automatic startup of Oracle RAC instance is disabled.
  Example
```
# su - oracle
$ srvctl config database -d <DB_NAME>
    :
Management policy: automatic
    :
$
```
  In the above example, "automatic" means that automatic startup is not disabled. Refer to the following example to disable automatic startup.
  Example
```
$ srvctl modify database -d <DB_NAME> -y manual
```
Changing the Oracle resource settings
1. Starting Oracle Clusterware (All nodes)
  If Oracle Cluserware is not started, start it on all nodes.
  See
  For details about starting Oracle Clusterware, refer to the Oracle Database manual.
2. Changing the Oracle resource settings (Any one of nodes)
  Start userApplication Configuration Wizard and change the setting of Oracle resource in all nodes. Set the new path after Out-of-place upgrade to all of the following settings.
  - Oracle Clusterware resource
    Grid home (GridHome)
  - Oracle RAC instance resource
    Oracle home (OracleHome)
    Grid home (GridHome)
  - Oracle RAC listener resource
    Grid home (GridHome)
  See
  For details about the procedures for changing the Oracle resource settings, see "2.3.4 userApplication with Oracle Clusterware", "2.3.5 userApplication with Oracle RAC Instances and Listeners" and "B.2 Change Resource Settings".
3. Confirming the settings (All nodes)
  To confirm the settings of Oracle RAC instance or listener resource, execute clorainfo command.
  Example
```
# /opt/FJSVclora/bin/clorainfo -c
```
  To confirm the settings of Oracle Clusterware, execute grep command and find them in the configuration file.
  Example
```
# grep Clusterware /usr/opt/reliant/etc/hvgdconfig | grep GridHome
  Oracle1_Clusterware GridHome /u01/app/11.2.0.3/grid
  Oracle2_Clusterware GridHome /u01/app/11.2.0.3/grid
#
```
Starting RMS (All nodes)
Start RMS on all nodes.
Starting userApplication (All nodes)
Start userApplication on all nodes, and confirm to be Online and Offline.
Also, confirm that Oracle Clusterware, Oracle RAC instance and Oracle RAC listener resource become Online and Offline following the starting and stopping of userApplication.
Restart service
If RMS and userApplication run correctly, restart service.