README VERSION : 1.1 README CREATION DATE : 2014-04-03 PATCH-ID : VRTSvcsea-6.0.500.000 PATCH NAME : VRTSvcsea 6.0.500.000 BASE PACKAGE NAME : VRTSvcsea BASE PACKAGE VERSION : 6.0.100.000 SUPERSEDED PATCHES : 6.0.300.000 REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : rhel5_x86_64 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER PATCH CRITICALITY : CRITICAL HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : NO REQUIRE APPLICATION DOWNTIME : YES PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to Install Guide for install instructions and Release Notes for other information. PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Install Guide for uninstall instructions and Release Notes for other information. SPECIAL INSTALL INSTRUCTIONS: ----------------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:VRTSvcsea-6.0.500.000 3343071 (3233895) Error message does not specify the source directory for the missing detailed monitoring script of the Db2udb agent. 3359151 (3240209) During the Oracle online operation, due to an incorrect pattern match, the Oracle agent unnecessarily tries to back up the database. 3384343 (1919203) Add Health check monitoring for Oracle Agent. 3415165 (3409593) The ASMDG agent shows offline before volumes are released and service group fail-over will be delayed because volumes won't stop. PATCH ID:6.0.300.000 2930163 (3013962) Added support for DB2 Version 10.1 in DB2 agent. 3002840 (3013940) If DB2 is installed in NON-MPP mode and UseDB2Start attribute is set to 0, db2start command is used to start the DB2 process instead of db2gcf command. SUMMARY OF KNOWN ISSUES: ----------------------------------------- NONE KNOWN ISSUES : -------------- NONE FIXED INCIDENTS: ---------------- PATCH ID:VRTSvcsea-6.0.500.000 * INCIDENT NO:3343071 TRACKING ID:3233895 SYMPTOM: During the in-depth monitoring cycle of the Db2udb Agent, the following error message appears in the VCS engine logs: Db2udb:db2udb1:monitor:Custom monitor script /opt/VRTSagents/ha/bin/Db2udb/monitor_custom_db2inst1_0 does not exist. From the error message, users cannot determine the source from where the missing script needs to be copied. DESCRIPTION: As a prerequisite for in-depth monitoring of the Db2udb instances, you must manually copy the monitor_custom_db2inst1_0script from the /etc/VRTSagents/ha/conf/Db2udb/sample_db2udb directory, to the Db2udb Agent directory. If you fail to copy the script then the agent displays the above error message. RESOLUTION: The error message was modified to indicate the source directory from where you must copy the monitor_custom_db2inst1_0 script to the Db2udb agent directory. * INCIDENT NO:3359151 TRACKING ID:3240209 SYMPTOM: During an Oracle online operation, the Oracle Agent repeatedly tries to back up the Oracle database, and fails. The following error message appears in the engine log: ORA-01531: a database already open by the instance DESCRIPTION: While bringing an Oracle database instance online, the Oracle agent tries to determine if last database backup was failed. The agent uses a pattern match on known error string codes to determine if the previous backup failed. The known error code strings include: ORA-00299; ORA-01108; ORA-01113; ORA-01143; ORA-01151; ORA-01153; ORA-16139; 16175; ORA-19681; ORA-38749; ORA-51204; ORA-51221; ORA-51226; ORA-51230; ORA- 10873 In a rare case, the agent may incorrectly determine a pattern match and unnecessarily start a database backup. As the backup is unnecessary, the backup fails, and the error message appears. RESOLUTION: The Oracle agent is modified to accurately determine a previous backup failure, and back up the database only when required. * INCIDENT NO:3384343 TRACKING ID:1919203 SYMPTOM: Unable to detect the health check status of Oracle database on upgrading the current version to next version. DESCRIPTION: Oracle health check binaries built by linking Oracle libraries from specific version of Oracle did not work as expected with the next version of Oracle. This change in behavior was observed during the minor release of Oracle 11g. RESOLUTION: 1) The Oracle health check binaries are built on the target VCS nodes where Oracle is installed. 2) If the Oracle version is upgraded, then Oracle health check binaries can be re-built using the build_oraapi.sh script shipped in the Oracle agent directory. From VCS version 6.0.5 onwards, you can use the build_oraapi.sh script to generate the executables that are required for Oracle health check monitoring. Symantec ships the build_oraapi.sh script along with the VCS agent for Oracle in the Oracle agent's directory, /opt/VRTSagents/ha/bin/Oracle/ For more details, please refer to following link: http://www.symantec.com/docs/TECH214888 * INCIDENT NO:3415165 TRACKING ID:3409593 SYMPTOM: When the ASMDG resource completes offline, the ASM volume has not yet been released. Therefore the volumes will not stop, and VCS has to run the clean entry point to stop the volumes. The clean operation mostly succeeds after multiple attempts. DESCRIPTION: While trying to make the service group containing the Listener, Oracle and the ASMDG resources offline, the resources successfully go offline. However, while trying to make the volume resource offline, it states that the volume is still open or mounted and clean entry point was called and the volume resource went offline subsequently. Next, when the diskgroup resource was made offline it reported an error stating that Some volumes in the disk group are in use and the clean is called and fails the first time and when it is called the next time it goes through successfully. RESOLUTION: The ASMDG agent delays the exit of the offline entry point when it detects the device (any one of the volume) to be busy. PATCH ID:6.0.300.000 * INCIDENT NO:2930163 TRACKING ID:3013962 SYMPTOM: In a DB2 10.1 setup, if you bring a DB2 resource online, the DB2 agent reports a resource fault. DESCRIPTION: In DB2 Version 10.1, the DB2 PID file is hidden. As a result, when you bring a DB2 resource online, the agent fails to detect the hidden PID file, and incorrectly reports a resource fault. RESOLUTION: The code has been modified, so that DB2 agent can detect the hidden PID file. * INCIDENT NO:3002840 TRACKING ID:3013940 SYMPTOM: When you try to bring a DB2 resource online, the DB2 agent fires the "db2 start" command in the non-MPP mode. If you have set the value of UseDB2start attribute to 0, and if you have not specified the virtual hostname in the db2nodes.cfg file, the command fails, and displays the following error message: "A communication error occurred during START or STOP DATABASE MANAGER processing. SQL1032N No start database manager command was issued.SQLSTATE=57019" DESCRIPTION: The "db2 start" command fails for want of the virtual hostname. RESOLUTION: Symantec has modified the DB2 agent to use the "db2gcf" command instead of the "db2 start" command. This command automatically updates the db2nodes.cfg file with the virtual hostname of the physical machine where the command is fired. INCIDENTS FROM OLD PATCHES: --------------------------- NONE