4 Upgrading an Oracle Audit Vault Collection Agent

This chapter describes the procedure to upgrade an Oracle Audit Vault collection agent installation from release 10.2.2.1.0 or lower to release 10.2.3.0.0. This chapter covers the following topics:

Back Up and Recovery of Oracle Audit Vault Collection Agent Files
Upgrade Requirements
Upgrade Procedure
Performing a Silent Upgrade Installation Using a Response File
Post Upgrade Information

4.1 Back Up and Recovery of Oracle Audit Vault Collection Agent Files

Oracle Audit Vault collection agent upgrade installation does not have the ability to be rolled back, therefore you should take precautions to backup the files before you perform the upgrade until you have tested the upgrade installation.

Back Up Oracle Audit Vault Collection Agent Home

Because the upgrade installation will update files in the Oracle Audit Vault collection agent home, you should back up or copy these files to another directory until the upgrade installation has been tested.

Abandon the Upgrade

If the upgrade installation is not successful, to abandon the upgrade, copy (Restore) the Oracle Audit Vault collection agent home files back.

4.2 Upgrade Requirements

Note:

On the Solaris Operating System (SPARC 64-bit) platform before performing an upgrade operation from Oracle Audit Vault collection agent release 10.2.2.1.0 to release 10.2.3.0.0, you must set the write permissions for the $ORACLE_HOME/jre folder as follows; otherwise, a write permission error is returned for the ../jre/../ files during the upgrade.

chmod -R u+w jre

The only requirement for upgrading your Oracle Audit Vault collection agents to release 10.2.3.0.0 is that you must have already upgraded the associated Oracle Audit Vault Server (Audit Vault Server) for these collection agents to release 10.2.3.0.0. This is essential to maintain compatibility between these Oracle Audit Vault collection agents with the most current version of the associated Audit Vault Server. In other words, you cannot upgrade an Oracle Audit Vault collection agent to release 10.2.3.0.0 without first upgrading its associated Audit Vault Server to this release because the Oracle Audit Vault collection agent would not be compatible nor would it work with the older associated release 10.2.2.1.0 or lower Audit Vault Server.

The rule of thumb is that an older, installed Oracle Audit Vault collection agent will always work with the most current installed release of the Audit Vault Server that is either of the same release or higher; this is called upward compatibility of the older Oracle Audit Vault collection agent with the newer Audit Vault Server. For example, a release 10.2.2.1.0 Oracle Audit Vault collection agent would be compatible with a release 10.2.3.0.0 Audit Vault Server.

However, on the contrary, a release 10.2.3.0.0 Oracle Audit Vault collection agent would not be compatible nor would it work with a release 10.2.2.1.0 or lower Audit Vault Server. For example, neither an upgraded release 10.2.3.0.0 Oracle Audit Vault collection agent nor a fresh installation of a release 10.2.3.0.0 Oracle Audit Vault collection agent would be compatible with a release 10.2.2.1.0 or lower Oracle Audit Vault Server.

4.3 Upgrade Procedure

To upgrade to Oracle Audit Vault collection agent release 10.2.3, you must follow this sequence of steps to shut down Oracle Audit Vault components, perform the upgrade, then start up Oracle Audit Vault components:

Step 1: Ensure the NLS_LANG Environment Variable Is Not Set

Note:
This step is not necessary if the October 2007 or later Oracle CPU has been applied to Oracle Audit Vault collection agent release 10.2.2.1 or lower.
Step 2: Stop All Collectors Running Within the Context of the Collection Agent You Are Upgrading
Step 3: Stop the Collection Agent You Are Upgrading
Step 4: Stop the Agent OC4J That Houses the Collection Agent You Are Upgrading
Step 5: Perform the Upgrade to Oracle Audit Vault Collection Agent Release 10.2.3.0.0 in the Oracle Audit Vault Collection Agent Home
Step 6: Start the Upgraded Collection Agent
Step 7: Start the Collectors That Run in the Upgraded Collection Agent
Step 8: Monitor the Oracle Audit Vault System

Details of each of these steps follows.

Step 1: Ensure the NLS_LANG Environment Variable Is Not Set

The NLS_LANG environment variable must not be set.

Step 2: Stop All Collectors Running Within the Context of the Collection Agent You Are Upgrading

You must stop all collectors associated with the Oracle Audit Vault collection agent being upgraded.

From the Audit Vault Server home with ORACLE_HOME, ORACLE_SID, and PATH environment variables properly set for the Audit Vault Server home, use the following command syntax to stop each collector.

avctl stop_collector -collname collector-name -srcname source-name

Step 3: Stop the Collection Agent You Are Upgrading

You must stop the collection agent associated with the Oracle Audit Vault collection agent being upgraded.

From the Audit Vault Server home with ORACLE_HOME, ORACLE_SID, and PATH environment variables properly set for the Audit Vault Server home, use the following command syntax to stop each collection agent.

avctl stop_agent -agentname agent-name

Step 4: Stop the Agent OC4J That Houses the Collection Agent You Are Upgrading

You must stop the agent OC4J associated with the Oracle Audit Vault collection agent you are upgrading. There is one agent OC4J associated with each collection agent.

From the Oracle Audit Vault collection agent home with ORACLE_HOME, ORACLE_SID, PATH, LD_LIBRARY_PATH (for Linux x86, Linux x86-64, and Solaris SPARC_64), SHLIB_PATH (for HP-UX PA RISC and HP Itanium), or LIBPATH (for AIX) environment variables properly set for the Oracle Audit Vault collection agent home, use the following command syntax to stop the agent OC4J.

avctl stop_oc4j

Step 5: Perform the Upgrade to Oracle Audit Vault Collection Agent Release 10.2.3.0.0 in the Oracle Audit Vault Collection Agent Home

Perform the following steps to perform the upgrade to Oracle Audit Vault collection agent release 10.2.3.0.0 in the Oracle Audit Vault collection agent home:

Locate the Oracle Audit Vault collection agent release 10.2.3 media and mount the media.
Start Oracle Universal Installer (OUI) from the directory where the runInstaller program is located.
```
cd directory-containing-Oracle-Audit-Vault-Agent-Installation-Files
./runInstaller
```
On the Oracle Audit Vault Agent Installation Select Installation Type window, when the installer detects an upgradable release, it automatically selects the Upgrade Existing Audit Vault Agent Home option and displays the upgradeable home path specifications. If there is more than one upgradable path to upgrade, review the path names, and select the path specification to upgrade. Then click Next.
The Summary Page screen is displayed. Check the space requirements. Note that 33 MB of space is required to install Patch Set 1 along, which includes 27 MB of temporary space. Next, review each of the items that are about to be installed. Click Install.
The Configuration Assistant screen appears and proceeds to apply Oracle Audit Vault collection agent one-off patches and then the Oracle Audit Vault Upgrade Assistant runs some AVCA scripts to continue the release 10.2.3 upgrade installation.
On the End of Installation screen, you should see a message indicating a successful installation. Click Exit to exit the Oracle Universal Installer. Then on the Exit confirmation screen for the prompt "Do you really want to exit?", click Yes to confirm the exit operation.

Step 6: Start the Upgraded Collection Agent

avctl start_agent -agentname agent-name

Step 7: Start the Collectors That Run in the Upgraded Collection Agent

From the Audit Vault Server home with ORACLE_HOME, ORACLE_SID, PATH, LD_LIBRARY_PATH (for Linux x86, Linux x86-64, and Solaris SPARC_64), SHLIB_PATH (for HP Itanium), or LIBPATH (for AIX) environment variables properly set for the Audit Vault Server home, use the following command syntax to start each collector that runs in the upgraded collection agent.

avctl start_collector -collname collector-name -srcname source-name

Step 8: Monitor the Oracle Audit Vault System

This step is a reminder to monitor the Oracle Audit Vault system to ensure all Oracle Audit Vault components are running and the system is operational. See the Oracle Audit Vault Administrator's Guide for more information.

4.4 Performing a Silent Upgrade Installation Using a Response File

Follow these brief steps to perform a silent upgrade installation using a response file:

Make sure all prerequisites are met for the installation of Oracle Audit Vault collection agent.
Prepare the Oracle Audit Vault collection agent response file. A template response file can be found at AV-agent-installer-location/response/upgrade_avagent.rsp on Linux and UNIX-based systems at the Oracle Audit Vault collection agent installation media and at AV-agent-installer-location\response\upgrade_avagent.rsp on Microsoft Windows systems at the Oracle Audit Vault collection agent installation media.

Prepare the response file by entering values in the first part of the response file for all parameters, then save the file. Do not edit any values in the second part of the response file.
Invoke Oracle Universal Installer using the following options:

For Linux and UNIX-based systems:
```
./runInstaller -silent -responseFile Path-of-response-file
```
For Microsoft Windows systems:
```
setup.exe -silent -responseFile Path-of-response-file
```
In this example:

Path of response file identifies the full path of the response file.

-silent runs Oracle Universal Installer in silent mode and suppresses the Welcome window.

For more information about these options, see Section 1.2.2. For general information about these options and about how to complete an installation using these response files, see the platform specific Oracle Database installation guides and Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide for Linux and "Installing Oracle Products" in Oracle Universal Installer and OPatch User's Guide for more information about installing and using response files.

4.5 Post Upgrade Information

Note that after performing an Oracle Audit Vault collection agent upgrade, because the upgrade is an inplace upgrade, the original directory structure is still in use. This means the ORACLE_HOME, ORACLE_SID, PATH, LD_LIBRARY_PATH (for Linux x86, Linux x86-64, and Solaris SPARC_64), SHLIB_PATH (for HP-UX PA RISC and HP Itanium), or LIBPATH (for AIX) environment variables are the same as they were before the upgrade.

See Section 3.4 for any additional post upgrade installation tasks.