This document provides an overview of OpenView Performance Insight (OVPI) for version 5.20. The release notes contain important information not included in the manuals.
NOTE: The Release Notes on the OVPI 5.20 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
The following features are introduced in OVPI 5.20 release.
Ability to log the datasource information, which helps to uniquely identify the collected data based on datasource.
Ability to process collected data using Perl scripts, before loading it to the database.
For detailed information about the above features, refer to the HP OpenView Performance Insight Administration Guide (OVPI_admin_guide.pdf)
Installation and upgrade requirements, as well as instructions for installing OVPI 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 OVPI. For a complete list of operating system patches, refer to Software Requirements section.
Before installing OVPI, 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.
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.
Perform the following steps to change the permissions:
Change to the install directory by using the following command:
$ cd
$ORACLE_HOME/install
Run changePerm.sh and specify the patched server
Oracle home location, before accessing client-side utilities or libraries in the
database home.
This section describes the software requirements for OVPI 5.20 release.
The following table shows the operating systems, the database management
systems, and the OVPI components that the configurations support:
| Operating Systems | Database Management Systems | OVPI Components |
|
HP-UX 11.11 |
Oracle 10G R2 Version 10.2.0.3 Sybase 15.0.1 |
All components except LTR for Sybase databases |
| Solaris 9 and 10 |
Oracle 10G R2 Version 10.2.0.3 Sybase 15.0.1 |
All components except LTR for Sybase databases |
| Windows 2003 Standard and Enterprise Edition |
Oracle 10G R2 Version 10.2.0.3 Sybase 15.0.1 |
All components except LTR for Sybase databases |
| Windows XP | None | OVPI Client and Web Access Server |
| Red Hat Enterprise Edition Linux version 4 |
Oracle 10G R2 Version 10.2.0.3 Sybase 15.0.1 |
All components except LTR for Sybase databases |
HP-UX 11.11
The patches required for HP-UX 11.11 are:
HP-UX 11.23 (PA)
The patches required for HP-UX 11.23 (PA) are:
Solaris 9
The patch required for Solaris 9 is:
Solaris 10
The patch required for Solaris 10 is:
Windows 2003 Standard and Enterprise Edition
The patch required for Windows 2003 Standard and Enterprise Edition is:
Linux (RHEL4)
The patch required for Linux (RHEL4) is:
Oracle
The patch required for Oracle is:
Sybase
The patches required for Sybase on respective Operating Systems are:
The Sybase patches are delivered along with the OVPI Software. You can find the patches under the following directory in the OVPI 5.20 DVD:
$CDROM/Data/sybase/esd3/
You can find the Installation instructions in the README.html file.
In addition to this release notes, the OVPI documentation set includes the following guides:
This section describes known problems, limitations, and workarounds for OVPI 5.20 release.
Problem: After you upgrade OVPI from 5.1 SP6 to 5.20, the initial Management Console is blank with status bar.
Workaround: When you upgrade OVPI from version 5.1 to 5.2, 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 OVPI. 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 OVPI 5.2 applications re-create .ovpi, preferences.ini, and defaults.ini files when you start them.
Problem: If you try to install or upgrade OVPI from a path
that contains a blank space in any of the folder names, the OVPI installation or
upgrade fails.
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.
Workaround: None.
Problem: On Oracle installations, following errors are recorded:
.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 Oracle patch 3748430 on top of Oracle 10.2.0.3.
Problem: When OVPI runs on Sybase databases, you might find the following error in the trend.log file.
deadlock situation encountered
Solution: This is the Sybase locking issue. Install the following latest Sybase patches for the Operating System that you are using:
The Sybase patches are delivered along with the OVPI Software. You can find the patches under the following directory in the OVPI 5.20 DVD:
$CDROM/Data/sybase/esd3/
You can find the Installation instructions in the README.html file.
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 can not exceed 16K. To workaround 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: SHS 2 STAR Collector does not work on Linux. SHS 2.6 is currently not supported on Linux platform.
Problem: On HP-UX platform, OVPI running on Simplified Chinese locale; WAS pages show unrecognizable characters in the date string.
Workaround: None.
Problem: On Oracle databases, trend_sum command shows 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: This error does not affect the functionality of trend_sum. You can ignore this error.
Problem: trendpm hangs while synchronizing upload tables and keys table.
Workaround: This happens when the SGA size slow. 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.
Problem: Reports can be viewed without logging in to the Viewer application.
Workaround: None.
Problem: The OVPI Management Console on Simplified Chinese locale shows incorrect date format for OVPI build date.
Workaround: None.
Problem: On HP-UX platform, when you use Remote X display to view the OVPI Management Console, your session might disconnect from the OVPI server.
Workaround: Create another Remote X display session to
connect to the OVPI server.
If this problem occurs frequently with the
Remote X terminal server you are using, you may consider an alternate method to
access the OVPI Management Console.
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.
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. OVPI is designed to discard duplicate records before inserting them into the database.
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.
The PATH in OVPI is not localised. Therefore, non-english characters are not supported in PATH.
Limitation: You cannot create OVPI Users with user names that begin or end with Simplified Chinese characters.
OVPI username/passwords are not localised.
Limitation: The installation of Report Packs fails if the Installation PATH contains Simplified Chinese characters.
The PATH in OVPI is not localised. Therefore, non-english characters are not supported in PATH.
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 OpenView 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
©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.