* * * READ ME * * *
         * * * Veritas Cluster Server Agents 5.0 MP3 RP4 * * *
                         * * * P-patch 1 * * *
                         Patch Date: 2010-10-04


This document provides the following information:

   * PATCH NAME
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
Veritas Cluster Server Agents 5.0 MP3 RP4 P-patch 1


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSvcsdb


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Storage Foundation for DB2 5.0 MP3 RP4


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Solaris SPARC 8
Solaris SPARC 9
Solaris SPARC 10


INCIDENTS FIXED BY THE PATCH
----------------------------
This patch fixes the following Symantec incidents:

   * 2116529                                                            

     SYMPTOM: A DB2 resource on a Veritas Cluster Server (VCS) node     
     generates excessive log messages. Consequently, the engine log file 
     engine_A.log is flooded with log messages.                         

     DESCRIPTION: For a DB2 resource on a VCS node, the monitor entry   
     function reads a PID file located at db2inst1/sqllib/ctrl. In the  
     PID file, if there is an empty line below the PID, then the "kill  
     -0" command generates an error and it fails to return the          
     appropriate exit status. As a result, for every monitor cycle, an  
     error is logged in the engine log and the inappropriate exit status
     returned by "kill -0" causes the monitor function to miss detection
     of a failed DB2 Connect instance.                                  

     RESOLUTION: Symantec has modified the DB2 agent so that it does not
     issue the kill command for empty lines in the PID file. The agent  
     now parses the PID file, validates the PID, and then issues the    
     kill command, if applicable. This modification prevents excessive  
     log messages in the engine log file engine_A.log.                  


INSTALLATION PRE-REQUISITES
---------------------------
The VRTSvcsdb package from 5.0 MP3 (Patch ID: 123672-03) must be present 
before installing this patch.


INSTALLING THE PATCH
--------------------
To install the patch:

1. Stop the Db2udb agent:
   # haagent -stop Db2udb -force -sys <system_name> 

2. Install the patch:
   # patchadd 141285-06

3. After the installation completes, verify that the patch is installed 
   on the systems. On each system type:
   # showrev -p | grep 141285-06

   The information displayed after the patch is installed resembles the 
   following:
   Patch: 141285-06
   Obsoletes: 141285-05
   Requires: 123672-03
   Incompatibles:
   Packages: VRTSvcsdb

4. Start the Db2udb agent:
   # haagent -start Db2udb -sys <system_name>


REMOVING THE PATCH
------------------
To remove the patch:

1. Stop the Db2udb agent:
   # haagent -stop Db2udb -force -sys <system_name>

2. Remove the patch:
   # patchrm 141285-06

3. After the removal completes, verify that the patch has been removed 
   from all the systems in the cluster. On each system type:
   # showrev -p | grep 141285-06

   No information is displayed after the patch is removed.

4. Start the Db2udb agent:
   # haagent -start Db2udb -sys <system_name>