Upgrading the VCS agent for Oracle


Upgrading the VCS agent for Oracle
Prev	Installing and removing the agent for Oracle	Next

The agent binaries for Cluster Server agent for Oracle are part of VRTSvcsea fileset. The VRTSvcsea fileset is already upgraded if you chose to upgrade to VCS 7.3 on a cluster which has a previous version of Cluster Server agent for Oracle installed.

Before you upgrade the agent, make sure you meet the prerequisites to upgrade the Cluster Server agent for Oracle.

Warning:

The agent fileset VRTSvcsea includes the VCS agents for Oracle, Sybase, and DB2. So, the procedure to upgrade the VCS agent for Oracle upgrades all the other agents also. Make sure that you have also met the upgrade prerequisites for the other agents that are part of the VRTSvcsea fileset.

If you had installed Cluster Server agent for Oracle that supported VCS 5.0MP3, 5.1, 5.1SP1, 5.1SP1RP1, 6.0, 6.0.1, or 6.0.3 on your VCS cluster, you can now upgrade the agents for use with VCS 7.3.

To upgrade VCS agent for Oracle to use with VCS 7.3

Save the VCS configuration and stop the VCS engine.
```
# haconf -dump -makero
# hastop -all -force
```
On all nodes on which the Oracle agent was installed, do the following:
- Remove the earlier version of the VCS agent for Oracle.
  - For VCS 5.1, 5.1SP1, 5.1SP1RP1, 6.0, 6.0.1, 6.0.3:
    
    # installp -u VRTSvcsea
  - For VCS 5.0 or 5.0MP3:
    
    # installp -u VRTSvcsor.rte
  - For VCS 5.0 or 5.0MP3:
    
    You must also remove the VRTScsocw fileset.
    
    # installp -u VRTScsocw.rte
- Delete the file /etc/VRTSvcs/conf/config/OracleTypes.cf.
- Install the VCS 7.3 agent for Oracle.
Make sure that you have copied the OracleTypes.cf file from the /etc/VRTSagents/ha/conf/Oracle directory to /etc/VRTSvcs/conf/config directory.
Make sure to update the newly copied OracleTypes.cf file with all the type-level changes that you had made to the older OracleTypes.cf file.

For example, if you had changed the value of the MonitorInterval attribute from the default 60 to 120 seconds, the OracleTypes.cf file gets updated. You must apply these type-level changes manually to the newly copied OracleTypes.cf file.
If you use ASM for database storage, then make sure that you have copied the file OracleASMTypes.cf from the directory /etc/VRTSagents/ha/conf/OracleASM to /etc/VRTSvcs/conf/config directory.
Make sure to update the newly copied OracleASMTypes.cf file with all the type-level changes that you had made to the older OracleASMTypes.cf file.
If you had enabled detail monitoring for the Oracle agent in the previous version, set the value of the LevelTwoMonitorFreq attribute to the same value of that of the DetailMonitor attribute.

Note:

The DetailMonitor attribute is deprecated in VCS 6.0 and later.
From a node in the cluster, edit your configuration file /etc/VRTSvcs/conf/config/main.cf.
Replace all resources of type Sqlnet with resources of type Netlsnr.
Verify the configuration.
```
# hacf -verify config
```
Start VCS on local node first.
Start VCS on other nodes.

Prev	Up	Next
Installing the VCS agent for Oracle software	Home	Disabling the Cluster Server agent for Oracle