README VERSION : 1.1 README CREATION DATE : 2013-01-18 PATCH-ID : 6.0.300.000 PATCH NAME : VRTSvcsea 6.0.300.000 BASE PACKAGE NAME : VRTSvcsea BASE PACKAGE VERSION : 6.0.100.000 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sol11_sparc (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 Release Notes for install instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Release Notes for uninstall instructions SPECIAL INSTRUCTIONS: --------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:6.0.300.000 2930163 (3013962) DB2 Agent support for DB2 Version 10.1. 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: ----------------------------------------- KNOWN ISSUES : -------------- FIXED INCIDENTS: ---------------- PATCH ID:6.0.300.000 * INCIDENT NO:2930163 TRACKING ID:3013962 SYMPTOM: In a DB2 10.1 setup, if you try to 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 try to bring a DB2 resource online, the Agent fails to detect the hidden PID file, and incorrectly reports a resource fault. RESOLUTION: Symantec has modified the DB2 agent to 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