Patch Name: PHSS_30323 Patch Description: s700_800 11.X OV ITO7.1X Perf Agent Windows A.07.21 Creation Date: 04/03/05 Post Date: 04/03/09 Hardware Platforms - OS Releases: s700: 11.00 11.11 s800: 11.00 11.11 Products: OpenView Operations 7.1 Filesets: OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,v=HP OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.11_32/64,v=HP Automatic Reboot?: No Status: General Release Critical: Yes PHSS_30323: CORRUPTION coda_Time is corrupt; shows up as an opcmona abort. Category Tags: defect_repair general_release critical corruption Path Name: /hp-ux_patches/s700_800/11.X/PHSS_30323 Symptoms: PHSS_30323: Change Request: 8606323549 WIN: Not able to see more than 10 CPUs from Graphs 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: 8606318909 Problem with codautil tool and EXSPIDATA datasource. Change Request: R555025249 coda_Time is corrupt; shows up as an opcmona abort. PHSS_29540: 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. 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. PHSS_28822: Change Request: B552002462 Errors in EXSPI Mailbox Reports due to improper handling of the DDF data. Change Request: B552002781 When attempting to run Coda on a Windows NT managed node, errors occurred when trying to access a Microsoft library, causing Coda to fail. Change Request: B555015875 coda_SubmitObservation fails after a new metric was added to an object. Change Request: R555017084 The physical memory for MDC systems whose memory is higher than 2 GB is not reported in service Reporter correctly, the value found in the Reporter table is around 2 GB. Change Request: R555017222 64 bit counters have negative values if populated from 32 bit fields that wrap. Change Request: R555017754 Various memory and swap metrics on Windows 2000 systems with more than 2 GBytes of physical memory and/or pagefile (swap space) memory were incorrect and reporting bad values. Change Request: R555019316 Enhance codautil to allow users to view the last set of logged values. Change Request: R555019330 Gbl_Mem_Phys should be MBytes, not KBytes. Change Request: R555020973 Provide a faster mechanism for creating a partial list of instances. Change Request: R555020974 Improve KMdataMatrix memory management for sparse data. Change Request: R555021901 On Windows, GetDriveType() behaves differently for redirected drives. When this API is called with a drive letter that actually points to a remote network drive, it has been found that it causes a file access attempt, and consequently a network logon, which, in turn, causes an account lockout of the global HP ITO account. Microsoft has agreed to update the MSDN documentation accordingly. Defect Description: PHSS_30323: Resolution: Change Request: 8606323549 On Windows systems with more that 10 processors, not all of the CPU data gets reported. Coda will now correctly report all of the CPU data for all of the processors on the system. 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. PHSS_29540: Resolution: 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. 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. PHSS_28822: Resolution: Change Request: B552002462 The errors in the Exchange SPI Mailbox Reports were due to improper handling of the DDF data in Coda. This has since been corrected so that only the valid data is returned to Reporter. Change Request: B552002781 Coda no longer depends on the msvcp60.dll and will work correctly on a Windows NT managed node. Change Request: B555015875 New metrics can now be added to an existing DDF object after data has been submitted. Change Request: R555017084 Coda now uses an extended function that Microsoft has provided for Windows 2000 that supports systems with greater than 2GBytes of physical memory and/or pagefile (swap space) memory. The correct values are now being reported. Change Request: R555017222 Coda now handles a 32 bit wrap in a 64 bit field, thereby showing the correct values for any affected metric. Change Request: R555017754 Coda now uses an extended function that Microsoft has provided for Windows 2000 that supports systems with greater than 2GBytes of physical memory and/or pagefile (swap space) memory. The correct values are now being reported. Change Request: R555019316 The codautil tool has been enhanced to allow any user to view the object model (through the use of the -obj option) for all of the SPIs that that have been deployed and are running on their nodes. In addition, the -dumpds option (the datasource name is required) will report all of the data for the specified datasource for the last logged interval. The command formats are: codautil -obj codautil -dumpds Change Request: R555019330 GBL_MEM_PHYS is now reported in MBytes. Change Request: R555020973 Added attributes to keep track of last instance visited in the instance list. These attributes are used to speed sequential access to list elements. Change Request: R555020974 Extensive modifications to minimize memory used to store dataMatrix on server and client. Change Request: R555021901 The code has been updated to first determine whether or not a redirected (or substituted) drive has been used. If this is the case, it will simply use the resolved network drive. Enhancement: No SR: 8606323549 B555022787 R555025249 8606318909 8606326670 B555016055 B555016493 R555023258 R555023771 B555015875 R555017754 R555017084 R555020973 R555020974 R555019330 B552002781 R555021901 R555019316 B552002462 R555017222 Patch Files: OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64, v=HP: OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.11_32/64, v=HP: /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.07.10/RPC_DCE_TCP/perf_pkg.Z what(1) Output: OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64, v=HP: /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/ A.07.10/RPC_DCE_TCP/perf_pkg.Z: None cksum(1) Output: OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64, v=HP: 3560002319 252631 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/ms/intel/nt/A.07.10/RPC_DCE_TCP/perf_pkg.Z Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_29540 PHSS_28822 Equivalent Patches: ITOSOL_00289: sparcSOL: 2.7 2.8 2.9 Patch Package Size: 280 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_30323 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHSS_30323.depot By default swinstall will archive the original software in /var/adm/sw/save/PHSS_30323. 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_30323.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHSS_30323.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_30323.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 OVO Administrator's GUI or from command line using inst.sh) WHILE RUNNING SWINSTALL. NOTE: This patch must be installed on the OVO Management Server system, NOT on an OVO Managed Node directly. Changes will take effect on managed nodes by means of OVO Software Distribution (using 'Force Update' if there is already an agent installed on the managed node). See chapter 2 of the OVO Administrator's Reference manual for more information. (B) Patch Deinstallation Instructions --------------------------------- (B1) To deinstall the patch PHSS_30323 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_30323