HP Performance Insight

Version 5.30, Release Notes

for the Windows®, HP-UX, Linux, and Solaris operating system

07 November 2007

This document provides an overview of Performance Insight (PI) for version 5.30. The release notes contain important information not included in the manuals.

NOTE: The Release Notes on the PI 5.30 DVD may not contain the latest information. To check for recent updates or to verify that you are using the most recent edition, go to the following web site: http://ovweb.external.hp.com/lpe/doc_serv/


In This Version
Installation Notes
Software Requirements
Documentation Updates
Known Problems, Limitations, and Workarounds
Support
Legal Notices


In This Version

The PI 5.30 release includes new features along with the features introduced in PI 5.20.
To display details about each release, click the links. To hide details, click again.

Features in PI 5.30 Release

Features in PI 5.20 Release (Released in July 2007)

For detailed information about the above features, refer to the HP OpenView Performance Insight Administration Guide.


Installation Notes

Installation and upgrade requirements, as well as instructions for installing PI on Oracle and Sybase databases are documented in the following product manuals provided in Adobe Acrobat (.pdf) format:

Review the Installation and Upgrade guides prior to installing the product.

NOTE: You must install all operating system patches before you install your Oracle or Sybase database or PI. For a complete list of operating system patches, see the Software Requirements section.

Prerequisites for PI Installation

NOTE: When you install or upgrade PI from a path, it must not contain a blank space in any of the folder names. For example, if you have a folder by the name my space in the following path: /my space/DVDROM; you cannot install or upgrade from this path.

Before installing PI, make sure that Oracle binaries permissions are set correctly so that other users can access and execute the Oracle binaries like sqlplus.
Following is the detailed instruction given in the Oracle 10.2.0.3 Patch install notes to achieve this.

Running changePerm.sh Script on an Oracle Database Server Home

Oracle recommends using the most restrictive file permissions possible for your given implementation.

Perform these optional steps only after considering all security ramifications and only if you need to share this installation:

During patch set installation, all new files and directories are created with restricted access, by default. Users or third party applications with a different group identifier from that of the database, which try to access client-side utilities or libraries in the database home, will see permission errors when trying to access these files or directories.

To change the permissions, follow these steps:

  1. Change to the install directory by using the following command:
    $ cd $ORACLE_HOME/install
  2. Run changePerm.sh and specify the patched server Oracle home location, before accessing client-side utilities or libraries in the database home.

Post-Installation and Upgrade Activities

  1. UNIX only: Change the owner of systems.xml file to trendadm user. By default, root user is the owner. To change the ownership, type the following at the command line:
    chown trendadm:trendadm {DPIPE_HOME}/data/systems.xml
    In this instance, DPIPE_HOME is the directory into which you installed PI.

  2. After you install or upgrade PI, run the Perl module encode generator (enc2xs) to ensure that all the Perl scripts run successfully. To run enc2xs:
  3. If you are upgrading PI from an earlier version to PI 5.30, you must disable SHS. To disable SHS, follow these steps:
    1. Open the following file using a text editor:
      <installation_directory>\data\config.prp
      In this instance, <installation_directory> is the directory into which you installed PI.
    2. Add the following lines in the config.prp file:
      SelfHealing.QueryMinMaxTaPeriods=false
      SelfHealing.QueryPropertyTable=false
      SelfHealing.QueryDataTable=false
      SelfHealing.CollectionInterval=20

      You must overwrite if the above lines already exist.
    3. Restart the OVPI HTTP Server process.
    4. Stop SHS service if it is running.

Software Requirements

This section describes the software requirements for PI 5.30 release.

Supported Operating Systems and Database Management Systems

The following table shows the operating systems, the database management systems, and the PI components that the configurations support:

Operating Systems - Architecture Oracle 10g Enterprise Edition R2 Sybase Adaptive Server Enterprise 15 PI Components
HP-UX 11.11 / 11.23 - PA-RISC
HP-UX 11.23 / 11.31 - Itanium
Oracle 10G R2 Version 10.2.0.3

Sybase 15.0.2

All
Solaris 9 / 10 - Sun SPARC Oracle 10G R2 Version 10.2.0.3

Sybase 15.0.2

All
Windows XP (32-bit) Not applicable

Not applicable

PI Client and Web Access Server
Windows 2003 Standard and Enterprise Edition (32-bit x86) Oracle 10G R2 Version 10.2.0.3

Sybase 15.0.2

All
Red Hat Enterprise Edition Linux version 4 - 32 bit x86 Oracle 10G R2 Version 10.2.0.3 Sybase 15.0.2 All

Operating System Patch Information for PI 5.30

HPUX 11.23 (PA and IA)

The patches required for HPUX 11.23 (PA and IA) are:

HPUX 11.31 (IA)

The patch required for HPUX 11.31 (IA) is:
QPKBASE(B.11.31.0709.312a) Quality Pack Depot for 11i v3, September 2007

Solaris 9

The patches required for Solaris 9 are:

Solaris 10

The patches required for Solaris 10 are:

Windows 2003 Standard and Enterprise Edition

The patch required for Windows 2003 Standard and Enterprise Edition is:
Windows2003: Service Pack1 (SP1)

Linux (RHEL4)

The patch required for Linux (RHEL4) is:
Update 3

Database Patch information for PI 5.30

Oracle

The patch required for Oracle is:

Oracle for OpenView (OfO)

Before installing PI 5.3 on your OfO instance, you must install the Oracle Critical Patch Update - October 2007.

For information on how to get this patch, go to the website, http://saw.cce.hp.com/km/saw/view.do?docId=emr_na-c00727143


Documentation Updates

The first page of this release notes document contains the following identifying information:

In addition to the release notes, the PI documentation set includes the following guides:


Known Problems, Limitations, and Workarounds

This section describes known problems, limitations, and workarounds for PI 5.30 release.

Security Bulletin

Problem: PI 5.30 contains Java version JDK 1.4.2_13. There are security vulnerabilities detected in this version of JDK.
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102997-1
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102995-1
Workaround: You must update the java version to JDK 1.4.2_15 to resolve this security issue. The PI 5.30 DVD contains JDK1.4.2_15.
To install JDK 1.4.2_15, follow these steps:

  1. Log on to the local system.
  2. Stop the trendtimer and wait for all PI processes to halt.
  3. To install the package, do one of the following depending on your operating system:

Installation

Problem: After you upgrade PI from 5.1 SP9 or 5.1.2 or 5.20 version to PI 5.30 version, the initial Management Console is blank with status bar displayed.
Workaround: When you upgrade PI, the upgrade process does not remove the .ovpi folder that contains the preferences.ini and defaults.ini files. The .ovpi folder is present in the directory into which you install PI. You must back up the .ovpi folder and save the folder with a different name. For example, you can rename .ovpi to .ovpi.bak. The PI 5.3 applications re-create .ovpi, preferences.ini, and defaults.ini files when you start them. Before you upgrade PI, you must save the customizations and manually reapply the same after upgrade.

Problem: On HP-UX PA-RISC or HP-UX Itanium, installation of Sybase fails when the Installer is launched from a mounted DVD on HPUX.
Solution: Run the following command to mount the DVD:
mkdir /dvdrom
mount -F cdfs -o rr /dev/dsk/dvd_devicename /dvdrom


Here, dvd_devicename is the name of the DVD-ROM device. On an HP_UX system, the dvd_devicename will apear simillar to the following:
/dev/dsk/c1t2d0

Problem: On Windows platform, the PI installer might fail to start the OVPI HTTP Server. Also, when you try to start the OVPI HTTP Server using the Windows Services administrative tool, the following error message appears:
The OVPI HTTP Server service on Local Computer started and then stopped.
Workaround: This problem occurs if the entry for System32\wbem is missing from the Path entry of the server system variables. To solve this problem, follow these steps:

  1. On the Windows taskbar, click Start, point to Settings, and select Control Panel. The Control Panel window opens.
  2. Double-click System. The System Properties dialog box opens.
  3. Click the Advanced tab, and click the Environment Variables button.
  4. In the System Variables list, select the Path entry and click Edit button.
  5. In the Variable value box, append a semicolon(;) at the end of the existing values and add the following entry:
    C:\Windows\System32;C:\Windows;C:\Windows\system32\wbem;
  6. Click OK.
  7. Restart the OVPI HTTP Server.

Integration of PI and Network Node Manager(NNM)

Problem: If you try to install NNM 7.51 on a system which already has PI version 5.20 or 5.30, the installation of NNM 7.51 fails.
Workaround: This problem occurs because NNM 7.51 tries to install an older version of OvPerl package. To solve this problem, do either of the following:

Product Upgrade

Problem: Upgrading Sybase or Oracle fails when trendtimer is running.
Workaround: Stop the trendtimer and wait for all PI processes to halt before you upgrade Sybase or Oracle.

Problem: If PI is unused for a long time, trend_sum creates unnecessary partitions in the database.
Workaround: To solve this problem, see the eCare document number OV-EN023678.

Problem: On UNIX platform, the ovpi_run_sql command occasionally fails after upgrading to PI 5.30.
Workaround: To solve this problem, you must manually edit the ovpi_odbc.ini file. For more information, see the eCare document number OV-EN023669.

Uninstalling Sybase

Problem: On some platforms (Linux, HP-UX IA, HP-UX PA RISC), the uninstall program option is not available for Sybase Adaptive Server 15.0.2.
Workaround: To uninstall Sybase Adaptive Server 15.0.2, run the following commands:

$JAVA_HOME/bin/java -classpath
$SYBASE/uninstall/ASESuite/uninstall.jar:$SYBASE/uninstall/ASESuite/ismp.jar -Dtemp.dir=/var/tmp
-Dis.jvm.home=$JAVA_HOME -Dis.jvm.temp=1
-Dis.launcher.file=$SYBASE/uninstall/ASESuite/uninstall -Xms20m
-Xmx60m run

Where:
$JAVA_HOME is the JRE 1.4.X directory.
$SYBASE is the location where you installed Adaptive Server Enterprise version 15.0.2.

Database Management Systems

Problem: The following error message is recorded in the Oracle alert log file:
ORA-28674: cannot reference transient index-organized table
Workaround: This is an Oracle problem. To solve this problem, follow these steps:

  1. Log into SQLPlus client as sys user.
  2. Run the following command:
    alter system set recyclebin='off' scope=both;

Data Collection and Discovery

Problem: When you create a Collection with Row Processing using the Collection Wizard, the following error may appear: DPM_COLLECTABLE_TABLE_REGISTRATION_FAILED. The detailed error message that appears is: Implicit conversion from VARCHAR to TEXT is not allowed.
Workaround: This problem occurs only with the Sybase as backend database. With the Sybase database, .pl file created cannot exceed 16K. To work around this problem, either limit the number of metrics used to create a Collection or you can manually change the generated Perl script to limit the Perl script size to less than 16K.

Problem: On Solaris platform, if you uninstall HPlwdce package, the pa_discovery fails and the following error message appears:
ld.so.1: pa_discovery: fatal: libdce.so: open failed: No such file or directory Killed
Workaround: Reinstall the HPlwdce package.

PROBLEM: If the SourceDisposition directive for ee_collect is set to "delete", the entire source directory specified by the SourceDirectory directive is removed.

WORKAROUND: Use specific and unique source directory for all the files belonging to a collection. Do not use this directory for storing any other important information. Alternately you can use the SourceDisposition directives "keep" or "move".

Command Line

Problem: On Oracle databases installed on RedHat Linux platform, the trend_sum command might show the following error:
TSUM_MIDDLEWARE_ERROR,Middleware error: Unexpected exception : SqlState: null java.sql.SQLException: No more data to read from socket, ErrorCode: 17410
Workaround:
None. You can ignore this error. This is an Oracle problem, and does not affect the functionality of trend_sum. The trend_sum processes the rows during the next run.

Problem: On Sybase databases, the ovpi_bulk_copy command fails.
Workaround: To solve this problem, do one of the following depending on your operating system:

Problem: In a PI system running on Oracle database, trend_sum logs the following error:
.ovpiStandard,05:30,trend_sum,,ERROR,28762,23864,DEFAULT_SQL_MSG,java.sql.SQLException: ORA-00001:
unique constraint (SYS.I_I
NDPART_BOPART$) violated
ORA-06512: at "SYS.DBMS_UTILITY", line 478
ORA-06512: at "DSI_DPIPE.ADD_PARTITION_P", line 250
ORA-06512: at "DSI_DPIPE.SRDEVRES_SWITOSHDEVRES_SWI_P", line 478
ORA-06512: at line 1
. [trace: oracle.jdbc.dbaccess.DBError.throwSqlException() DBError.java:134]

Workaround: Apply the following Oracle patch on top of Oracle 10.2.0.3:

Problem: trendpm hangs while synchronizing upload tables and keys table.
Workaround: This happens when the SGA size is too low. Increase the Oracle SGA size.

Problem: db_delete_data is not working for custom collection table. That is, db_delete_data is not deleting the data in the custom collection table as per the retention profile.
Workaround: This defect is due to a bug in Oracle 10.2.0.3 which causes low end partition split failure. Apply the Oracle patch #3748430 to fix this problem.

Management Console

Problem: On HP-UX platform, when you use Remote X display to view the PI Management Console, your session might disconnect from the PI server.
Workaround: Create another Remote X display session to connect to the PI server.
If this problem occurs frequently with the Remote X terminal server you are using, you may consider an alternate method to access the PI Management Console.

Objects deletion

Problem: On the Edit Exclusion List GUI, under Device category, interfaces are also visible.
Workaround: This does not affect the functionality of Edit Exclusion List GUI and you can choose either device or interface to delete from Exclusion list from Device Category.

Performance Graphs - Row counts

Limitation: On the Performance Snapin, in the Row Counts Performance Graphs, the values displayed as Rows Collected will not always reflect the number of Rows saved in the database. This is because in certain instances the collectors will retrieve data records that represent duplicate information from the performance agents running on polled nodes. PI is designed to discard duplicate records before inserting them into the database.

Documentation

Problem:The PI Administration Guide mentions that the ta_period column can be updated using the Perl script generated by the collection wizard. However, this information is incorrect. The collection wizard can only generate a Perl script that can modify the metrics collected from the agent.
Workaround: If you want to modify the ta_period or derive the ta_period column from the collected metrics, you must manually create a Perl script. For more information about manually creating a Perl script, see Chapter 8 Managing Polling Policies of the HP OpenView Performance Insight Administration Guide

Localization

Problem: On non-English locales, the display strings appear in English.
Workaround: None. This problem does not affect the functionality of PI.

Problem: PI error messages are not localized.
Workaround: None. This problem does not affect the functionality of PI.

Problem: On non-English locale PI website, some of the link destinations in a tabbed report do not work after the tabbed report element is used a few times.
Workaround: Reload the report in the browser or use the Report Builder.

Problem: On non-English locales, some label names of the Certificate Manager tool are not translated correctly.
Workaround: None. This does not affect the functionality of PI.

Limitation: When you create a Report with Simplified Chinese characters, and deploy the report file to a directory with Simplified Chinese characters, the directory name and the file name are changed to unknown string. Non-English characters are not supported in PATH.

Limitation: You cannot create PI Users with user names that begin or end with Simplified Chinese characters. PI username or passwords are not localized.

Limitation: The installation of Report Packs fails if the Installation PATH contains Simplified Chinese characters. Non-English characters are not supported in PATH.


Support

You can visit the HP Support web site at:
www.hp.com/go/hpsoftwaresupport

This web site provides contact information and details about the products, services, and support that HP Software offers.

HP Software online software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to do the following:

NOTE: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to the following URL:
http://support.openview.hp.com/new_access_levels.jsp

To register for an HP Passport ID, go to the following URL:
http://www.managementsoftware.hp.com/passport-registration.html


Legal Notices

©Copyright 2007 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.