Patch Name: PHSS_30324 Patch Description: s700_800 11.X OV ITO7.1X Perf Agent Tru64 A.07.21 Creation Date: 04/03/05 Post Date: 04/03/11 Hardware Platforms - OS Releases: s700: 11.00 11.11 s800: 11.00 11.11 Products: OpenView Operations 7.1 Filesets: OVOPC-CLT.OVOPC-OSF-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,v=HP OVOPC-CLT.OVOPC-OSF-CLT,fr=A.07.10,fa=HP-UX_B.11.11_32/64,v=HP Automatic Reboot?: No Status: General Release Critical: Yes PHSS_30324: CORRUPTION coda_Time is corrupt; shows up as an opcmona abort. PHSS_29556: ABORT Coda aborts when retrieving data records that are missing some string (UTF8) values. Records may be missing values if a SPI client fails to submit values for all metrics. Some SPIs do not always submit a value for the UTF8 fields. This problem can occur on all of the supported Unix and Windows platforms. Category Tags: defect_repair general_release critical halts_system corruption Path Name: /hp-ux_patches/s700_800/11.X/PHSS_30324 Symptoms: PHSS_30324: Change Request: 8606318909 Problem with codautil tool and EXSPIDATA datasource. Change Request: 8606326670 Coda creating corrupt log and giving false values for GBL_CPU_TOTAL_TIME. Change Request: B555022787 Coda may not log data when the log files are rolled at midnight Saturday. Change Request: R555025249 coda_Time is corrupt; shows up as an opcmona abort. Change Request: B555020276 Coda reports BYDSK_UTIL > 100 on tru64 agent. Change Request: 8606349341 Coda values low for GBL_CPU_TOTAL_TIME or GBL_CPU_IDLE_TIME. PHSS_29556: Change Request: B555016055 I18N: Korean characters display errors in reports for Exchange SPI on Windows 2000. Change Request: B555016493 opcmona aborts on unhandled exception thrown in libcodaaccess. Change Request: R555023258 Performance problem if Coda accumulates many unresolved instances. Change Request: R555023771 Unhandled exception when calling codautil - data is not available for IIS reports. Defect Description: PHSS_30324: Resolution: Change Request: R555025249 Date/time values can become corrupted in multi-threaded applications bacause Coda is using non-thread safe system calls. The most obvious symtom shows up as an opcmona abort. Coda now uses thread safe system calls, thereby providing correct date/time values. Change Request: B555022787 Due to improper handling of the Coda logs when they are shut down for the log file roll at Midnight on Saturday, the metrics that are logged at 23:55 may not get reported correctly and show a gap in the data. The code was modified to correctly handle the log file roll at Midnight on Saturday to report the metrics that are logged at 23:55. This solves the problem of the missing data for that time period. Change Request: 8606318909 When running codautil with the -dumpds option, not all of the data for the specified datasource may be listed. The following error message may be displayed: Unable to get requested raw data (16) This occurs when one or more of the datasource objects don't have any data to report for the last interval. Codautil has been modified to check for the existence of a datasource object and report the name of the object if the object can't be found in the last logged interval. It then continues the processing of any remaining object(s). Change Request: 8606326670 The CPU may spike anywhere from 20,000 to 60,000% on terminal servers with W2k SP3 and nodes running W2k IIS servers as well. These spikes occurred during system reboot/restart when Coda was attempting to log its data. The code was modified to indicate that there is a gap in the data prior to deleting a corrupted coda log. The missing data is now reported correctly. Change Request: B555020276 On Tru64 agents, Coda may report greater than 100% disk utilization. The utilization for each disk is now reported correctly. Change Request: 8606349341 The 'Availability Report' from OV Reporter shows less than 100% uptime for a Tru64 system although the system had been up all the time. Processor block time for IO operation is included in the calculations. PHSS_29556: Resolution: Change Request: B555016055 Korean characters are not correctly displayed in Exchange SPI reports. Errors are shown in the character strings. This problem can occur on all of the supported Unix and Windows platforms. The non-ASCII data is now handled correctly by the DDF code. The string processing no longer assumes the data in ASCII. Change Request: B555016493 An unhandled "uninitialized DateTime" exception (fatal error) in libcodaaccess caused opcmona to abort. The DateTime field in question is now properly initialized to prevent a fatal error from occurring. Change Request: R555023258 Internally, Coda maintains a list of unresolved object instances. An entry is added to this list every time data for a new instance is submitted by the SPIs. When a client requests data from Coda, the list of unresolved instances must be "unified". The algorithm used to do this is very slow. As the list of unresolved instances grows, the response time of Coda quickly becomes unacceptable. To correct this problem, the unresolved instances are "unified" before allowing new data to be submitted. This will cause a minor delay for some submit requests, but will prevent the huge delays currently seen when the list of unresolved instances is large. Change Request: R555023771 Coda aborts when retrieving data records that are missing some string (UTF8) values. Records may be missing values if a SPI client fails to submit values for all metrics. Some SPIs do not always submit a value for the UTF8 fields. This problem can occur on all of the supported Unix and Windows platforms. The code now detects missing string (UTF8) values and handles them appropriately. Enhancement: No SR: B555020276 B555022787 R555025249 8606318909 8606349341 8606326670 B555016055 B555016493 R555023258 R555023771 Patch Files: OVOPC-CLT.OVOPC-OSF-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64, v=HP: OVOPC-CLT.OVOPC-OSF-CLT,fr=A.07.10,fa=HP-UX_B.11.11_32/64, v=HP: /var/opt/OV/share/databases/OpC/mgd_node/vendor/dec/alpha/ unix/A.07.10/RPC_DCE_TCP/perf_pkg.Z /var/opt/OV/share/databases/OpC/mgd_node/vendor/dec/alpha/ unix/A.07.10/RPC_DCE_TCP/perf_version /var/opt/OV/share/databases/OpC/mgd_node/vendor/dec/alpha/ unix/A.07.10/RPC_NCS/perf_pkg.Z /var/opt/OV/share/databases/OpC/mgd_node/vendor/dec/alpha/ unix/A.07.10/RPC_NCS/perf_version /var/opt/OV/share/databases/OpC/mgd_node/vendor/dec/alpha/ unix51A+/A.07.10/RPC_DCE_TCP/perf_pkg.Z /var/opt/OV/share/databases/OpC/mgd_node/vendor/dec/alpha/ unix51A+/A.07.10/RPC_DCE_TCP/perf_version what(1) Output: OVOPC-CLT.OVOPC-OSF-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64, v=HP: /var/opt/OV/share/databases/OpC/mgd_node/vendor/dec/alpha/ unix/A.07.10/RPC_DCE_TCP/perf_pkg.Z: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/dec/alpha/ unix/A.07.10/RPC_DCE_TCP/perf_version: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/dec/alpha/ unix/A.07.10/RPC_NCS/perf_pkg.Z: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/dec/alpha/ unix/A.07.10/RPC_NCS/perf_version: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/dec/alpha/ unix51A+/A.07.10/RPC_DCE_TCP/perf_pkg.Z: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/dec/alpha/ unix51A+/A.07.10/RPC_DCE_TCP/perf_version: None cksum(1) Output: OVOPC-CLT.OVOPC-OSF-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64, v=HP: 445233478 1033965 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/dec/alpha/unix/A.07.10/RPC_DCE_TCP/perf_pkg.Z 4059024341 8 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/dec/alpha/unix/A.07.10/RPC_DCE_TCP/ perf_version 445233478 1033965 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/dec/alpha/unix/A.07.10/RPC_NCS/perf_pkg.Z 4059024341 8 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/dec/alpha/unix/A.07.10/RPC_NCS/perf_version 445233478 1033965 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/dec/alpha/unix51A+/A.07.10/RPC_DCE_TCP/ perf_pkg.Z 4059024341 8 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/dec/alpha/unix51A+/A.07.10/RPC_DCE_TCP/ perf_version Patch Conflicts: None Patch Dependencies: s700: 11.00 11.11: PHSS_28950 s800: 11.00 11.11: PHSS_28950 Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_29556 Equivalent Patches: ITOSOL_00290: sparcSOL: 2.7 2.8 2.9 OVOW_00081: intelNT: 4.00 4.01 intelWIN2000: 1.00 Patch Package Size: 2910 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_30324 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHSS_30324.depot By default swinstall will archive the original software in /var/adm/sw/save/PHSS_30324. If you do not wish to retain a copy of the original software, include the patch_save_files option in the swinstall command above: -x patch_save_files=false WARNING: If patch_save_files is false when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. For future reference, the contents of the PHSS_30324.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHSS_30324.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_30324.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: BEFORE LOADING THIS PATCH... (A) Patch Installation Instructions ------------------------------- (A1) Install the patch, following the standard installation instructions. For backing up the system before installing a patch, you may use opc_backup(1m) NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM ADDRESSED BY THIS PATCH IS DISTRIBUTED (either from the VPO Administrator's GUI or from command line using inst.sh) WHILE RUNNING SWINSTALL. NOTE: This patch must be installed on the VPO Management Server system, NOT on an VPO Managed Node directly. Changes will take effect on managed nodes by means of VPO Software Distribution (using 'Force Update' if there is already an agent installed on the managed node). See chapter 2 of the VPO Administrator's Reference manual for more information. NOTE: The VPO Agent consists of several components that are patched individually. This patch updates only the Event/Action component. Therefore the software distribution will tell, that the agent software is updated to A.07.10, not to A.07.12. Also the version of the ITOAgent bundle will still be A.07.10. You can verify the installed version of the components on the agent system using opcragt -agent_version. For example: opcragt -agent_version hpbbln8 Node hpbbln8.bbn.hp.com: OPC_INSTALLED_VERSION = A.07.22 PERF_INSTALLED_VERSION = A.07.21 COMM_INSTALLED_VERSION = 2.6.4.0 Done. NOTE: Before installing new agents, please check which version of OVO agent is installed on the managed node. If installed version is lower than A.07.20, than make sure that old agents are deinstalled from the managed node. Also make sure that after old agents are deinstalled, neither /usr/opt/OV nor var/opt/OV directories exists on the managed node. These two directories must be removed prior to the new agent installation. (B) Patch Deinstallation Instructions --------------------------------- (B1) To deinstall the patch PHSS_30324 run swremove: NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM ADDRESSED BY THIS PATCH IS DISTRIBUTED (either from the ITO Administrator's GUI or from command line using inst.sh) WHILE RUNNING SWREMOVE. # swremove PHSS_30324