README VERSION : 1.1 README CREATION DATE : 2012-09-20 PATCH-ID : PVCO_03960 PATCH NAME : VRTSvcsea 5.1 SP1RP2 BASE PACKAGE NAME : Veritas High Availability Enterprise Agents by Symantec BASE PACKAGE VERSION : VRTSvcsea 5.1SP1 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : hpux1131 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER PATCH CRITICALITY : OPTIONAL HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : NO PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer the release notes for installation instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer the release notes for un-installation instructions. SPECIAL INSTRUCTIONS: --------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- 2724835 (2724829) Provide online monitoring (PRON) IMF support for Sybase agent SUMMARY OF KNOWN ISSUES: ----------------------------------------- KNOWN ISSUES : -------------- FIXED INCIDENTS: ---------------- PATCH ID:PVCO_03960 * INCIDENT NO:2724835 TRACKING ID:2724829 SYMPTOM: Only traditional monitor method is available for Sybase agent DESCRIPTION: Provide online monitoring (PRON) IMF support for Sybase agent. The IMF Mode value for Sybase resources can be set to 2 for 5.1SP1RP3 release on Linux, Solaris and AIX platform. For HP platform the online monitoring (PRON)IMF support is available for Sybase agent from 5.1SP1RP2 release. IMF support is not enabled by-default in these RP releases. RESOLUTION: Symantec has updated the Sybase and SybaseBk agents to provide online monitoring (PRON) IMF support. User should set the IMF attribute and set the Mode to 2 (PRON support) only.IMFRegList is added to the Sybase type definition. During enabling IMF, user should ensure that the type definition is updated and IMFRegList is correctly set. For in-depth monitoring DetailMonitor attribute should be used. LevelTwoMonitorFrequency attribute is not used in the RP releases. As a result, when IMF is enabled and DetailMonitor is also enabled for Sybase resource, the actual detail monitor will happen at a frequency (DetailMonitor attribute value * IMF MonitorFreq) INCIDENTS FROM OLD PATCHES: --------------------------- Patch Id::PVCO_03934 * Incident no::2271882 Tracking ID ::2381846 Symptom::MonitorMethod attribute does not reflect IMF value without setting Listener attribute on Netlsnr Resource. Description::The default value of Netlsnr attribute was set for traditional monitoring but was not set for AMF. Resolution::Default value for Listener attribute of Netlsnr is set to LISTENER for all types of monitoring. * Incident no::2318334 Tracking ID ::2318310 Symptom::Oracle agents use /usr/lib in LD_PRELOAD before Oracle libraries. Description::Customer was asked by Oracle CC for using Oracle Library path before /usr/lib Resolution::Changed the order of libraries mentioned in LD_PRELOAD environment variable. * Incident no::2403782 Tracking ID ::2403714 Symptom::On the Linux platform, if the values of the VCS Sybase agent attributes "SApswd" and "UPword" begin with the string "VCSSY:", then Sybase resources fail to come online. Description::Sybase agent scripts use an incorrect path for the "cat" command on the Linux platform. As a result, the operation to bring a Sybase resource online fails, and the following message appears as part of the command output: Can't exec "/usr/bin/cat": No such file or directory at /opt/VRTSagents/ha/bin/Sybase/online line 244. Use of uninitialized value $encrypted_passwd in substitution (s///) at /opt/VRTSagents/ha/bin/Sybase/online line 245 Resolution::Symantec has modified the Sybase and SybaseBk agent code to remove the use of the "cat" command. Instead, the agents use Perl's built-in functionality to read the required password information from a file to execute agent operations. * Incident no::2417846 Tracking ID ::2220749 Symptom::Cluster Manager(Java Console) does not encrypt DBAPword attribute of the Oracle agent. Description::Tags Empty Resolution::Cluster Manager(Java Console) is modified to encrypt DBAPword attribute of the Oracle agent. * Incident no::2367721 Tracking ID ::2427112 Symptom::Virtual fire drill fails for owner check when output format of id command differs between the node where resource is online and on the node where the check is performed. Description::Virtual fire drill matches the output of id command with the output of same command on the system where the resource is in online state. For example, some fields in this output differ when SELinux is enabled. Resolution::Symantec has modified the check to only verify the uid and gid instead of complete output of the id command. * Incident no::2424812 Tracking ID ::2424805 Symptom::When the Oracle owner uses CSH shell, Oracle agent fails after an upgrade to version 5.0MP4RP1(for Linux) or 5.0MP3RP5(for other unices). Description::When an user does not specify the EnvFile attribute or does not set the LD_LIBRARY_PATH variable in the specified EnvFile, the Oracle startup operation fails. During the startup operation the agent uses the setenv command to set the LD_LIBRARY_PATH environment variable to the list of library paths consisting of user-specified and pre-defined values. User-defined values are listed before pre-defined values. If the user-specified value is not available in the EnvFile, the agent sets the user-specified value to NULL. However, the setenv command does not accept NULL as the first value in the list of library paths and hence the agent fails. Resolution::Symantec has modified the Oracle agent code and moved the user-specified values at the end of the library path list. * Incident no::2511385 Tracking ID ::2511378 Symptom::The Sybase agent declares a resource online before the Sybase database can complete its recovery. The following message also appears in the engine logs: "recovery state is UNKNOWN- online script terminating" Description::When the Sybase agent runs the 'sybase dataserver start' command, the data server takes some time to initialize and start accepting the 'isql' connection requests. The Sybase agent attempts an 'isql' connection after 10 seconds of issuing the start command. If the 'isql' connection request is unsuccessful, the ONLINE script of the Sybase agent terminates without waiting for the database recovery, and logs the above error message. Resolution::Symantec has modified the ONLINE script of the Sybase agent to wait in loop till the Sybase dataserver accepts an 'isql' connection. As a result, the agent declares the resource online, only after the database completes recovery.