HP OpenView Performance Insight

5.1 Release Notes

14 March 2005

This document provides an overview of the changes made to HP OpenView Performance Insight (OVPI) for the version 5.1 release. It contains important information not included in the manuals. 
 

NOTE: Because updated release notes and documentation are posted to the support website on a regular basis, the release notes available from the website are likely to be more current than the release notes included on the OVPI CD. HP strongly recommends that you check for an update to these release notes on the support website before you use the release notes shipped on the CD. To access the website, see Support.

In This Version
Oracle Installation Notes
Installation Notes
Software Requirements
Enhancements and Fixes
Known Problems, Limitations, and Workarounds
Documentation Errors
Support
Legal Notices

In This Version

This section describes the new and changed features of the software for OVPI version 5.1.

Installation

OVPI now provides installation support for:

• Linux operating systems

  You can install the OVPI Client on the following Linux platforms: Red Hat Enterprise Linux 2.1, Red Hat Enterprise Linux 3, and SuSE Linux Enterprise Server 8.

• Remote Oracle databases

  You can install OVPI and use an existing remote Oracle 9.2.0.5 database, keeping the database on a system separate from the OVPI installation. For installation details, refer to Chapter 3 of the Performance Insight Installation Guide. 

• 32-bit/64-bit Oracle database support

  OVPI supports Oracle on 32-bit and 64-bit UNIX systems, and on 32-bit Windows systems.

Internationalization

OVPI supports internationalization. You can install OVPI on any language version of the supported operating systems. Database support is internationalized for Oracle only. Sybase database systems must use English-based systems and do not support localized data.

Localization

OVPI is localized only for the following languages: Japanese, Korean, Simplified Chinese, and Traditional Chinese.

Management Console

You can use the Management Console’s Catalog Manager application to create report links (formerly referred to as contextual launch) from deployed reports to other reports, URLs, and applications. Additionally, you can manage its Link and Report and Uniform Resource Locator (URL) catalogs. These catalogs reside on the Web Access Server. They contain the following:

• Link. This catalog contains any links that you created in any of the deployed reports in the catalog. You can create a link from any deployed report to any of the following: report, third-party application, or URL.

  A report link takes specific information from the source report, uses it as the input for a report parameter (in the case of a report to report link) or to an argument (in the case of a report to application or URL link), and then displays the report, application, or URL with the specified information when a user opens the link in the report. Thus, you can connect reports, URLs, and applications together to create navigation paths building an intelligent and customer-specific flow of information.

• Report and URL. This catalog contains the following:
  1. Deployed reports. You deploy reports to this catalog to make them available for users to view using the Web Access Server. You place reports in the Report and URL catalog using the Report Deployment wizard.
  2. Deployed URLs. Deploying a URL in the Report and URL catalog is useful when you want to access a particular URL frequently.

     After you deploy a URL, you can select it from the catalog of URLs rather than having to type its information each time you want to create a link to that URL. Additionally, you can also access the URL while using the Web Access Server application.

     To view a deployed URL using the Web Access Server application, click the Catalog link, open the folder to which you deployed the URL, and then click the URL. The specified website displays in your current browser window or in a new browser window, depending on how you have configured the viewing settings for the Web Access Server. 

Refer to Chapter 12 in the Performance Insight Administration Guide for more information about Catalog Manager. Links are launched by users when they view reports using the Web Access Server, Report Viewer, or Report Builder.

Package Manager

Package Manager has the following new directive:

report_link:<name_of_tlg_file>

This directive allows the deployment of a .tlg file. The .tlg file contains link group information. You can view links in this file using Catalog Manager, which is available from the Management Console. Refer to the install.pkg chapter in the Performance Insight Reference Guide for details.

Report Builder

Following are the new features for Report Builder:

• Handling missing data for graphs

  Occasionally, there is no data available for a graph. For example, this can happen when polling cycles are missed or network errors occur. You can decide how to graph missing data by setting a graph's hole properties after you create it. For details, refer to Chapter 4 in the Performance Insight Guide to Building and Viewing Reports.

• Multiple sources supported for element drilldown

  After you create the elements for a report, you will probably want to link them. You create links between elements in order to display more detailed information about a selected item. For example, you might link a table to multiple graphs; the graphs will display more detail about a selected item in the table. This detailed information is referred to as a drilldown. In previous versions of OVPI, you could only link a single element to one or more destination elements. In OVPI 5.1, you can now link multiple elements to the same destination element. For example, you can link multiple combination boxes to a single table.

  Refer to Chapter 5 in the Performance Insight Guide to Building and Viewing Reports for more information about linking elements in a report.

• Drilldown operators

  When you link elements using Report Builder's link wizard, you can specify any of the following operators to link the element's statistics: =, >, >=, <, <=, and <>. You will be able to choose these operators from the Create Link Constraints window in the link wizard. Refer to Chapter 5 in the Performance Insight Guide to Building and Viewing Reports for more information about linking elements in a report.

• Rule satisfaction methods

  In addition to displaying an image or a background color when a rule is satisfied, you can now specify that another statistic or text display. For details, refer to Chapter 6 in the Performance Insight Guide to Building and Viewing Reports.

• Substitution variable

  The !{X} variable is now available for graph legends. This is a substitution variable where X represents the alias of one of the selected statistics in the graph. Thus, you can display values stored in the database. For example, to display a managed object and its description, where the alias Description is the value of the description stored in the database, you would use the following:

  $M$ !{Description}

  Refer to Chapter 4 in the Performance Insight Guide to Building and Viewing Reports for more information about using variables in graph legends.

• Generic graphing

  You can create graphs that contain data from generic or non-OVPI tables using Report Builder's graph wizard. You will be able to choose generic data from the Select a Data Source window in the graph wizard. Refer to Chapter 3 in the Performance Insight Guide to Building and Viewing Reports for more information about creating graphs in reports.

• Report links (formerly referred to as contextual launch)

  A report can now contain a link to another report, a URL, or an application. When viewing a report, you can launch any of the links it contains. A link takes specific information from a source report, uses it as the input for a specific statistic (in the case of a report to report link) or to an argument (in the case of a report to application or URL link), and then displays the report, application, or URL with the specified information when you open the link.

  When the cursor is placed over a link, it changes from an arrow to a hand. Also, depending on the type of element used for the link, the following occurs:

  • Elements that are the destination of a report link are surrounded by a blue boundary.

  • Text in a label or in a table column is underlined.

  Refer to Chapters 3, 10, and 11 in the Performance Insight Guide to Building and Viewing Reports for more information about opening report links using Report Builder, Report Viewer, and the Web Access Server applications. Note that report links are created using the Catalog Manager application; refer to the Performance Insight Administration Guide for details.

• Performance Insight Guide to Building and Viewing Reports has a new chapter, Appendix B, "Using TrueType Fonts in PDF Files".

Web Access Server

Following are the new features for the Web Access Server:

• Emailing generated reports in PDF format

  When you schedule a report for generation and select PDF for the format of the generated report, you can choose to email the generated PDF file to other users. For details, refer to Chapter 7 in the Performance Insight Guide to Building and Viewing Reports.

• URL deployment

  You can deploy a URL to the Web Access Server’s catalog in order to quickly access a website that you use frequently. For example, if your company has more than one Web Access Server system, you may want to deploy a URL for a particular report that you view frequently on one of those systems. For details, refer to Chapter 11 in the Performance Insight Guide to Building and Viewing Reports.

• Diagnostic information

  The Administration link has a Diagnostic page that shows information about the Web Access Server and the database connections. For details, refer to Chapter 13 in the Performance Insight Administration Guide.

• Report links (formerly referred to as contextual launch)

  A report can now contain a link to another report, a URL, or an application. When viewing a report, you can launch any of the links it contains. A link takes specific information from a source report, uses it as the input for a specific statistic (in the case of a report to report link) or to an argument (in the case of a report to application or URL link), and then displays the report, application, or URL with the specified information when you open the link. A link is treated just like a URL; it will display using the same method that your browser uses to display URLs. For example, if your browser underlines URLs, any links in the report will be underlined.

   

  ---

  NOTE: You cannot open report to application links using the Web Access Server. You must use Report Builder or Report Viewer to open these kinds of links. Additionally, the application must reside on the system from which you run Report Builder or Report Viewer to successfully invoke the application linked to the report.
   

  ---

  Report links are created using the Catalog Manager application; refer to the Performance Insight Administration Guide for details.

SNMPv3 Support

OVPI will now collect data from SNMPv3 nodes; however, OVPI will not be able to discover those nodes. In order to collect data from these nodes, you will have to do the following:

1. Install SNMP Research's SNMP Security Pack product.

2. Add the SNMPv3 nodes using node_manager.

3. Set up specific community string profiles for the nodes.

Refer to Chapter 2 of the Performance Insight Administration Guide for the detailed procedure.

Miscellaneous

In OVPI 5.1, the default look and feel reflects that of the native operating system. If for any reason this is not the case, you may need to remove the .ovpi directory from your home directory.

OVPI 4.6 Upgrade - Obsolete Programs

OVPI 4.6 users upgrading to OVPI 5.1 should review the following table, which lists programs that were removed during the OVPI 5.0 release and that are obsolete. 

Oracle Installation Notes

When installing Oracle 9.2.0.5, or when using an existing remote Oracle 9.2.0.5 database, you are instructed to download and apply the Oracle 9.2.0.5 patch set, available from www.oracle.com, as part of the database installation. Note that you must do the following to ensure subsequent successful installation of OVPI:

• Edit root.sh (HP-UX only)
• Install System Table (SYS.IND_ONLINE$)

These procedures are documented in Chapter 3 in the Performance Insight Installation Guide, in addition to several other steps needed to install Oracle properly in order for it to work with OVPI. Refer to Chapter 3 for the complete Oracle installation procedure.

Edit root.sh

On HP-UX only, during the patch set install, you are prompted to run root.sh. Before doing so, you must edit the root.sh script. Change the following lines:

CHMODF="/bin/chmod -f"
CHMODRF="/bin/chmod -fR"

to

CHMODF="/bin/chmod "
CHMODRF="/bin/chmod -R"

Install SYS.IND_ONLINE$

Due to a defect in the Oracle 9.2.0.5 patch installation, you must perform the following steps after installing the patch set and before installing OVPI. Otherwise, OVPI will display an error regarding Oracle’s missing system table, IND_ONLINE$.

Assuming that the database and the listener program are not running, and that your password is manager, perform the following steps:

1. Depending on your operating system, do one of the following:

• Windows
  1. From the Control Panel window, double-click the Administrative Tools icon. The Administrative Tools window opens.
  2. Double-click the Services icon. The Services window opens.
  3. Select and start the listener program and the database server.
• UNIX
  1. From the command prompt, start the listener program by typing:

      >lsnrctl start

2. Log on as sysdba using SQL*PLUS by typing:

>sqlplus/nolog
SQL>connect sys/manager as sysdba

3. Start the database by typing:

   SQL>shutdown
   SQL>startup migrate

4. Run SQL scripts by typing:

   SQL>@?/rdbms/admin/catpatch.sql
   SQL>@?/rdbms/admin/catcio.sql

5. Shutdown and then start the database by typing:

   SQL>shutdown
   SQL>startup

6. Exit SQL*Plus by typing:

   SQL>exit

Before you install OVPI, make sure that the instance for the Oracle listener program created for OVPI is running.

Installation Notes

Installation requirements, as well as instructions for installing OVPI are documented in the Performance Insight Installation Guide provided in Adobe Acrobat (.pdf) format. Specifically, Chapter 2 of the Performance Insight Installation Guide contains the preparations and requirements necessary for installing OVPI.

The OVPI guides are available on the OVPI installation CD. After you unzip the 5.1 tar file to your system, you can find them in the top level Documentation folder of the kit, or in the docs folder of the OVPI installation directory following product installation.  (See Support for additional information about accessing OVPI documentation, as well as Open View products, services, and support.)

NOTE: You must install all operating system patches before you install your database (Sybase or Oracle) or OVPI. For a complete list of patches required by your operating system, contact your operating system representative.

Required Patches for Running Java

OVPI also includes Java 1.4.2_02. Java will automatically load onto your system during the installation, but it will most likely not run properly until you download the patches required for your operating system. Refer to Chapter 2 in the Performance Insight Installation Guide for more information about the Java patches that you will need to install.

Required HP-UX Operating System Patches

If you plan to install the Database Schema and Performance Manager components on an HP-UX system, you need to install specific HP-UX patches. Refer to Chapter 2 in the Performance Insight Installation Guide for the list of patches that you must install.

Linux OVPI Client Installs

You must install a Linux Red Hat system with the db3 module (rpm), before you can install OVPI 5.1 clients on it.

Network Node Manager (NNM) Integration with OVPI 5.1

You can install OVPI 5.1 on a system that is already running Network Node Manager (NNM). HP recommends upgrading to NNM 7.5 (or greater) before installing OVPI; otherwise the OVPI MIB Browser and Collection Wizard tools will not be functional. Note that installing OVPI 5.1 with a version prior to NNM 6.4 is not supported.

Installing with NNM 7.5

When you install OVPI 5.1 on a system that is already running NNM 7.5, OVPI shares components with NNM that enable the OVPI MIB Browser and Collection Wizard tools to function.  The NNM 7.5 processes do not need to be stopped before installing OVPI.

On Windows systems, expect to see ERROR and WARNING messages during installation. The Windows installer displays this message:

failed to copy the file, msvcr70.dll, into the OVPI “bin” directory

msiexec failed with exit status: 1603

The “Warning” tab displays one or both of these warning messages:

Higher version of package might have been installed. Failed to install packageHPOvXpl-02.50.100-WinNT4.0-release.msi:{C9C24CC5-23CE-4B55-8BC0-6D5785924842}

Higher version of package might have been installed. Failed to install packageHPOvJxpl-02.50.100-WinNT4.0-release.msi:{48C97C18-5AFA-40FE-B51D-A4EECBE02808}

You can ignore all these messages. For more information, see QXCR1000218248 and QXCR1000218491, later in these Release Notes.

Installing with NNM 6.4 up to NNM 7.5

Before installing OVPI, you must completely stop all NNM processes; otherwise, errors may occur during installation. 

1. To stop NNM processes, do one of the following:

• Windows

  From the Start button on the Windows task bar, point to Programs, point to HP OpenView, point to Network Node Manager Admin, and select NNM Services - Stop.

• UNIX

  At the command prompt,  type:
  ovstop -c

2. Verify that the NNM processes have stopped by doing one of the following:

• Windows

  From the Start button on the Windows task bar, point to Programs, point to HP OpenView, point to Network Node Manager Admin, and select NNM Services - Status.      

• UNIX

  At the command prompt,  type:
  ovstatus -c

3. On Windows systems only, close the Services window; otherwise, the OVPI Services will fail to be installed. (Refer to QXCR1000218777, later in these Release Notes, should you need a workaround.)
4. Install OVPI 5.1. 

On Windows systems, expect to see the ERROR and WARNING messages described in the previous section,  "Installing with NNM 7.5."  You can ignore these messages.

Software Requirements

This section describes the software requirements for OVPI 5.1.

Supported Operating Systems and Database Management Systems

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	Sybase 11.9.2.5 ESD 1, Oracle 9.2.0.5	All
Red Hat Enterprise Linux 2.1 Red Hat Enterprise Linux 3 SuSE Linux Enterprise Server 8	None	OVPI Client
Solaris 8	Sybase 11.9.2.5 ESD 1, Oracle 9.2.0.5	All
Solaris 9	Oracle 9.2.0.5	All
Windows 2000 Server and Advanced Server with Service Pack 4 and later	Sybase 11.9.2.5 ESD 1, Oracle 9.2.0.5	All
Windows 2003 Standard and Enterprise	Oracle 9.2.0.5	All
Windows XP	None	OVPI Client and Web Access Server

Enhancements and Fixes

The following items (identified by error tracking number) are fixed in the current software release.

Back End

• QXCR1000027520: The dip_manager command's export_all option does not function correctly.
• QXCR1000029523: Filesystem filled to 100% without notification or warning.
• QXCR1000030540: The ksi_managed_node_d_tr trigger raises wrong error.
• QXCR1000030682: A locking problem causes records to be stuck in upload tables.
• QXCR1000030786: There is a trendpm issue related to the database procedure lock.
• QXCR1000031110: Raw2Rate and Copy procedures do not perform database space check prior to data processing.
• QXCR1000031294: On Oracle mw_collect should not mandate that the category name must be case-sensitive.
• QXCR1000030707: When multiple instances of trendcopy are running simultaneously, a core dump may occur.
• QXCR1000048020: The trendcopy command does not copy property tables that don't have a corresponding data table.
• QXCR1000049664: It is possible for R2D to introduce dsi_locks error on an upload table, because R2d does not have enough error checking prior to the dsi_locks_p call.
• QXCR1000050118: On a Sybase system, baseline summarization on a daily table is not working with ta_period as the by-variable.
• QXCR1000050131: The ta_samples computation is wrong in Sybase for weekly summarization.
• QXCR1000050152: The ta_samples for day_of_week summarization does not match in 5.0 Sybase and Oracle systems.
• QXCR1000050295: disk_stats can execute on a different system from the server it monitors.
• QXCR1000050296: disk_stats improperly handles table_space spread over the multiple disks.
• QXCR1000050396: The number of rows does not match in 5.0 Sybase and Oracle for day_of_week.
• QXCR1000050409: The trendcopy utility and others get the incorrect database vendor for a system.
• QXCR1000050549: The fields ta_samples and total_samples are incorrectly updated for weekly summarization for the hysterisis time period.
• QXCR1000050527: OVPA data does not get collected, because the .bcpg files do not get processed.
• QXCR1000050528: There is an issue with raw-to-delta regeneration on non-English systems.
• QXCR1000086041: pa_discovery and dpipe_pa display an error when OVO 8 agents are installed on the same system.
• QXCR1000086400: The indexmaint command should delete the primary key on Sybase when executed in force mode.
• QXCR1000088687: r2dupdate generates errors during the installation of 5.0 SP1.
• QXCR1000088693: The 5.0 SP1 log messages for Windows are different from UNIX.
• QXCR1000088695: The Service Pack installer should use the $TREND_LOG variable.
• QXCR1000090125: mw_collect is not able to resolve a derived group.
• QXCR1000090371: Hourly trendsum fails when a column with same name exists in the data table and property table.
• QXCR1000090594: The Action Poller and its related graphical user interface need to be ported to Oracle.
• QXCR1000113133 - Trendcopy core dumps when the time zone of the system on which it is run is ahead of GMT and the destination data table is empty.
• QXCR1000177879: A bcp_gateway truncation error occurs when uploading float numbers longer than 16 digits.
• QXCR1000177991: r2d skips the processing of data for the first dsi_key_id in a property table.
• QXCR1000190736: The bcp_gateway is slow to upload ifdescr collections.
• QXCR1000200121: When the service pack is installed, trendsum has to regenerate the

  procedure; however, it is also resummarizing the entire source table.

Form Deployment Wizard

• QXCR1000030619: The wizard shows that the form's deployment was successful even when the deployment fails.

Management Console

• QXCR1000028664: When you type the following command, no help is displayed:

  piadmin -help 

• QXCR1000030045: The word "synchronization" is spelled incorrectly twice.
• QXCR1000050482: You cannot change the port number using the database connect wizard.
• QXCR1000087403: Grouping does not work. When you attempt to create a enumerated group, Group Manager does not load the elements from the selected table into the user interface; it simply loads the contents of the table into the user's interface's navigation frame.

Report Builder

• QXCR1000027328: Time period settings are lost when the report is saved and then reloaded.
• QXCR1000047891: When you use a separate y-axis for an overlay's dataset, the autoscale functionality for the overlay's y-axis uses the max of the first dataset to determine the max y-axis value of the overlay y-axis. It should be using the max of the overlay dataset to determine this.
• QXCR1000049668: When the font for text in a table is set to Sans Serif, the text font property displays Arial. If you change the font back to Sans Serif, it reverts back to Arial when you click on another property.
• QXCR1000085492: Dual y-axis overlays do not work.
• QXCR1000087784: Megabyte values with a trailing 'T' are displayed Terabytes instead of 'M' in a graph.
• QXCR1000091442: When you select Font Type in Table Column Properties, Title Line 1, 2 or 3 in graphs or tables, or Label Boxes, the font always defaults to Arial immediately after any other font is selected; however, the font appears correctly in the graph and XML file.
• QXCR1000192435: When a report with a tabbed area and you right-click on the Tab level in the components tree, the pop-up menu that should display does not.
• QXCR1000195137:  The x-axis does not use the graph.prp file to display the x-axis time format.

Web Access Server

• QXCR1000027319: If you add a text label to a report and change its background color within the text label, the background color is not seen when the report is viewed.
• QXCR1000027493: The edit parameter icon is still available after the Allow Element Editing option is unchecked.
• QXCR1000027599: OVPI is still operational on port 80 after SSL is enabled.
• QXCR1000050166: When a "group by" is specified for a report element and the underlying table is a managed category table, the query does not work.
• QXCR1000050201: Whenever "ovpi_httpd stop" is run when there is an open session, an exception is dumped to the website.log file.
• QXCR1000050203: Users are still allowed to log on after the grace period expires.
• QXCR1000050495: When creating a schedule, the Drill down depth option does not allow values greater than 999 or negative values like -1.
• QXCR1000088332: A scheduled snapshot report shows all devices rather than those that were selected.
• QXCR1000158553: Reports with property parameters cause the scheduler to lose track of which parameter it should configure during scheduling.
• QXCR1000196078: The threshold policy results in Jrun opening files, which do not get closed; this causes OVPI to become unstable.

Documentation

• QXCR1000204890:  There is a  Missing Option in Reference Guide.
• QXCR1000203115:  OVPI_reference_guide document for pa_discovery is not updated for trace level. 
• QXCR1000205213:  Documentation does not state the -c option  for group/userimport.

Known Problems, Limitations, and Workarounds

This section describes known problems, limitations, and workarounds for OVPI 5.1, identified by error tracking number.

Installation and Upgrade

The following are known problems and limitations:

• QXCR1000195652: OVPI is limited to installing the components or database on systems with fully qualified hostnames of 32 characters or less. Hostnames of longer length will cause the installation to fail with the following error message:

  POST_INIT_P fails to run at install, hostname value too big for column

• QXCR1000215564: The OVPI installation program reports non-fatal errors when you try to load MIBs. This is because the packages downloaded from the package warehouse have circular dependencies and cannot be installed. As a result, the MIB Browser does not function on Linux.
• If you are installing OVPI on a Compaq system, stop any Compaq Insight Manager services before you install OVPI.
• If an HP OpenView Operations Agent or an HP OpenView Performance Agent (version 4 or later) is on the system, stop the agent before you begin the OVPI installation.
• QXCR1000029245: There is a serious problem on WIN2K & WIN2003 with installing from depots that sit in a directory that includes blanks in the pathname.

  Workaround: Place the set of installation files in a folder that does not have any space in the path. For example, you cannot run OVPI's setup.exe when it is located in a folder called OVPI install; rename the folder to OVPIinstall to run the executable.

  Note that you should not install OVPI using an executable that has been placed on the Desktop, because the Desktop folder has spaces in the path.

• QXCR10000213918: A problem occurs when using a raw device to create tablespaces during installation of OVPI on Sybase on a UNIX system. From the Sybase User and Device Creation window, display the Advanced  OVPI Configuration window. After choosing the device file from the Datafile column, if you move immediately to the "Transaction Log" tab (for setting the raw device for the Transaction Log), the raw device lists gets corrupted.

  Workaround: After choosing the raw device from the Datafile column, double-click on the corresponding Size column.

• QXCR1000213791: When OVPI is installed on a UNIX box set up in Trusted Mode, no OVPI environment variables get set. This is because trendadm does not have read permission over the file /etc/trend.conf.
• QXCR1000218248: After installing OVPI on a system with NNM, the Windows installer gives a misleading error message:

  failed to copy the file, msvcr70.dll, into the OVPI “bin” directory

  Workaround: Ignore this error message; the file does get copied into the correct location.

• QXCR1000218491: When installing or upgrading OVPI with NNM or another OpenView product that shares the HPOvXpl or HPOvJxpl packages, you will see a warning symbol during “configuring software settings”. After installation is complete, ERROR and WARNING messages display in the Details window.

  The "Error" tab will display the following message:

  msiexec failed with exit status: 1603
  
  The “Warning” tab will display one or both of the following warning messages:
  
  Higher version of package might have been installed. Failed to install packageHPOvXpl-02.50.100-WinNT4.0-release.msi:{C9C24CC5-23CE-4B55-8BC0-6D5785924842}
  
  Higher version of package might have been installed. Failed to install packageHPOvJxpl-02.50.100-WinNT4.0-release.msi:{48C97C18-5AFA-40FE-B51D-A4EECBE02808}

  Workaround: Ignore these messages.

• QXCR1000218777: On Windows systems, if the Services window is open during an installation or upgrade, one or both of the OVPI services ("OVPI HTTP Server" or "OVPI Timer") may fail to initialize. After a reboot, the services will not be listed in the Services window.

  Workaround: After you reboot the Windows system, run the following command to install the OVPI Timer:

  trendtimer -i 

  Run the following command to install the OVPI HTTP Server (be careful to use the surrounding quotes):

  DPIPE_HOME\jrun\bin\jrunsvc -install piweb "OVPI HTTP Server" "OVPI HTTP Server"
   

• QXCR1000218753:  The OVPI installer may give a “NumberFormatException” error during full upgrade from 5.0 to 5.1 on Solaris 5.9 when disk suite partitions are in use on Solaris raw devices. OVPI does not support installation on disk suite partitions on Solaris raw devices.

  Workaround: You can ignore the error message, proceed with the installation, and choose to install on other supported disk devices.

• QXCR1000211179: When upgrading from OVPI 5.0 to 5.1 using Windows 2003 Enterprise Edition with an Oracle database, the upgrade produces the error message:
  
  Failed to extract <DPIPE_HOME>\jrun\bin\jrunsvcmsg.dll
  
  This error usually occurs because the WMI (Windows Management Instrumentation) is trying to monitor the jrun service and has locked the jrunsvcmsg.dll file. (The process that has the file locked is C:\WINDOWS\system32\wbem\wmiprvse.exe.)

  Workaround: Stop the WMI service to release the lock on the file, and start the OVPI upgrade.

• QXCR1000221038: Occasionally, the OVPI Windows installer will fail to add C:\Program Files\HP OpenView\bin to the system PATH. The MIB Browser will give the following error when run:

  The dynamic link library ovJavaNative.dll could not be found in the specified path.

  Workaround: Edit the Windows system PATH and add C:\Program Files\HP OpenView\bin .
   

Localization and I18N

The following is a known limitation:

• The only localized data that OVPI supports for Sybase is in English. If you want to use localized data, you must use Oracle instead of Sybase.

Management Console

The following are known problems and limitations:

• QXCR1000204291/QXCR1000210953: On UNIX systems, using Management Console's Catalog Manager to open a new Report to Application Link and then browsing to the destination application results in the Open window displaying applications of type .exe. You cannot change the file type using the "Filter" tab. (This problem reflects Java bug #4710726.)

  Workaround: The laf (look and feel) is using Motif. Use the Edit -> Options menu item ("Display" tab) to change the look and feel to Windows or Metal, exit and restart OVPI.  You can also use the piadmin command (piadmin -laf) from the command prompt.

• QXCR1000201612: Using Management Console's Object Manager to locate a specific object through the Find dialog box does not always find the requested object.  For performance reasons, OVPI does not completely fill out the tree branches displayed in the Object/Property Management window. The Find option searches objects only in the currently populated Objects tree display. There is no workaround.
• QXCR1000207078: When using Report to Report link creation or Report to URL link creation, the Summary window displays the word "null" in the Link Index field. Ignore this, because it does not affect the functioning of the link.
• QXCR1000214650: When using any of the Catalog Manager report link wizards, the Link Group selection window is displayed, even if you have started the wizard by right-clicking the Link folder in the Links catalog.
• QXCR1000215096: When using the Catalog Manager to select a report in the report to URL link wizard, selecting one report enables the "next" button; selecting another report then disables the "next" button. This keeps occurring for every alternative report selection.
•  QXCR1000208357: When using the Catalog Manager, the Report to Application link browser does not list the contents of the $DPIPE_HOME/bin directory. However, for other directories it works as expected.

  Workaround: Type in the path and name of the application to which to link.

Report Builder

The following are known problems and limitations:

• In Report Builder, rules do not work when the table is a target of a link.
• QXCR1000215104: On UNIX platforms only, after adding a constraint to a report, the constraint is not reflected in the report.  Using Builder, create a new report, insert a table, and then add a constraint. After clicking OK and entering a target name, the table becomes blank. After entering the target name a second time, data appears in the table.
• QXCR1000207276: The File Save and Open dialog boxes on Windows Server 2003 give non-standard icons (and no office pane on the left). On other Windows platforms, the standard Windows icons do display, and the office pane does display on the left. The reason for this difference is because Sun has changed the look of the file dialogs between Java 1.4.1 and 1.4.2, but did not include icons for Windows 2003.
• QXCR1000202445: When using the Report Builder, Japanese characters get changed to white rectangles after setting FONT NAME property.

  Workaround: Simply change the font property to a font that supports multi-byte languages, like "sansserif.***" and "serif.***".

• QXCR1000202208: In the Report Builder, using drill-downs from a .SREP file doesn't work. When the same .SREP file is deployed to the web site, the drill downs work as expected.

System/Network Administration

The following is a known problem:

• QXCR1000207035: When using Management Console to add a remote database that is in a different domain than the client, hostname information downloaded from the remote server may not include the domain details that allow connection to the remote database.

  Workaround: To include the details, right-click on the system using the Management Console System/Network Administration window and select the Properties menu item. Add the domain name to the Hostname attribute in the "WAS" or "Database Properties" tabs (or both), apply, and restart the application.

Web Access Server

The following are known problems and limitations:

• If you are using Internet Explorer under Windows XP Service Pack 2 to view the Web Access Server, the Web Access Server's dialog boxes may not open because Service Pack 2 blocks pop-up windows on Internet Explorer by default. To change the settings of the pop-up blocker, go to the following web site and follow the instructions to enable the display of pop-up windows:

  http://www.microsoft.com/windowsxp/using/web/sp2_popupblocker.mspx

• When a user account is configured to access a database other than the default database, and that user changes information on the User Profile page, the Web Access Server reassigns the default database to the user.
• QXCR1000205885/QXCR1000202453: Japanese and traditional Chinese symbols do not appear in PDF files generated from an OVPI report.

  Workaround: Configure OVPI to use TrueType fonts in PDF files. For information, see Appendix B in the Performance Insight Guide to Building and Viewing Reports.

• Certain pathnames and data fields accessed through the Web Access Server Administration tab must contain only ASCII text.

Log File Location (Service Configuration -> Web Access Server): When using the Web Access Server Settings Page to specify the Log File Location, the pathname must contain only ASCII text. For example, you could not enter Chinese characters in the path name.

SSL Certificate Identifying Data (Service Configuration -> SSL Service): When using the SSL Service Configuration Page to specify Certificate Identifying Data, you must enter only ASCII text characters in the data fields. Otherwise, an error dialog box will alert you that you have entered nonASCII text.  

Deployed Items locations (Deployed Items -> Deployed Items): When using the Deployed Items Page to enter the Generated Reports Location, the Deployed Items Location, and the Image Cache Location, you must enter only ASCII text.

• QXCR1000207500: PDF rendering ignores font formatting and simply uses Times Roman.
• QXCR1000205939/QXCR1000205934: When downloading a report element -- table or graph -- from the web, where the element contains multi-byte characters (for example, Simplified Chinese), the element and its data are downloaded as a CSV (comma separated value) file, which is UTF-8 encoded. To properly view this file, your file viewer must support UTF-8 encoded documents. Additionally, filenames are only supported in the US ASCII character set.

  Workaround: You must rename the file manually during the download Save As operation. When downloading the file, change the file extension from .csv to .txt. This forces the viewer to ask how to parse the file. Choose a comma delimiter and UTF-8 encoding, and the file can then be viewed correctly.

Back End

The following is a known problem:

• QXCR1000209751: The trend_discover "help" parameter (-H) is not working.

Documentation Errors

The following errors and omissions occur in the documentation.

Performance Insight Installation Guide

• In Chapter 8 on page 221, a step is missing from the Prerequisite Tasks Checklist. In the checklist, a new list item should occur before the current number 10:

  Verify that the OVPI Timer and OVPI HTTP Server processes are stopped and that all OVPI-related processes have completed before you run the upgrade wizard. See "Stopping the OVPI Timer and OVPI HTTP Server."

  Immediately after the checklist, this new section should appear:

  Stopping the OVPI Timer and OVPI HTTP Server

  To stop the OVPI Timer and OVPI HTTP Server processes and verify that all OVPI-related processes have completed before you run the upgrade, do the following:

  • Windows

    From the Services window, right-click OVPI Timer and select Stop from the menu.

    From the Services window, right-click OVPI HTTP Server and select Stop from the menu.

  • HP-UX
    Type the following commands:

    /sbin/init.d/ovpi_timer stop
    /sbin/init.d/ovpi_httpd stop

  • Solaris
    Type the following commands:

    /etc/init.d/ovpi_timer stop
    /etc/init.d/ovpi_httpd stop

• In Chapter 2 on page 25 ("Internationalization and Localization"), the statement "OVPI supports full internationalization" should read "OVPI supports internationalization."
• In Chapter 2 on page 38 ("Addressable Memory Limits"), the limits for Oracle are omitted. Table 9 should appear as follows:

  Table 9   Addressable Memory Limits

  Operating System	Database
  	Sybase	Oracle (for 32-bit)	Oracle (for 64-bit)
  HP-UX	1 GB	1 GB (max for kernel parameter SHMMAX) 1.75 GB (total Shared Global Area (SGA) for all Oracle instances)	Limited to the size that the operating system can handle.
  Solaris	4 GB	2 GB	Limited to the size that the operating system can handle.
  Windows	2 GB	2 GB	N/A

• In Chapter 3 on page 82, step 7 should include a "shutdown" command. The step should appear as follows:

  
  7.  Start the database by typing:

       SQL>shutdown
     SQL>startup migrate

• In Chapter 3 on page 86, Table 1 is missing a parameter. The table should include the following parameter:
   

  Parameter	Recommended Value
  COMPATIBLE	9.2.0

   

Performance Insight Administration Guide

• In Chapter 2 on page 44, the documentation states "The SNMP Security Pack product has been integrated with OVPI to provide SNMPv3 support."
  
  This statement implies that SNMP Security Pack is installed when you install OVPI; however, this is not the case. SNMP Security Pack is a product from SNMP Research. You must contact SNMP Research to purchase this product.
• In Chapter 12 on page 343, Figure 17 does not show the Build this URL as a relative URL check box, nor does the subsequent text explain this option.
  
  Select the Build this URL as a relative URL check box when you want to link to a page on the current server. When you select this option, you will note that the Protocol, Host, and Port boxes in the Add the URL window become unavailable.
• In Chapter 12 on page 350, the Edit Report Link dialog box is shown. This dialog box is now called the Report Link Properties dialog box.
• The following changes have been made to the Report Link Properties dialog box:

  • The "General" tab, in addition to displaying the link's display name and description, displays the Link Type (URL, Report, Application), the source report, and, if applicable, the destination report.

  • The "Element Links" tab was removed.

  • The "Base" tab was added; it is identical to the Add the URL window in the Report to URL wizard. See page 343 for details.

  • The "Parameters" tab was added; it is identical to the Create Link Index window in the Report to URL wizard. See page 344 for details.

   

Support

Please visit the HP OpenView web site at:

http://www.managementsoftware.hp.com/

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

You can also go directly to the support web site at:

http://support.openview.hp.com/

HP OpenView 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 valuable support customer, you can benefit by being able to:

• Search for knowledge documents of interest
• Submit and track progress on support cases
• Manage a support contract
• Look up HP support contacts
• Review information about available services
• Enter discussions with other software customers
• Research and register for software training

NOTE: Most of the support areas require that you register as an HP Passport user and log 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/access_level.jsp

To register for an HP Passport ID, go to the following URL:

https://passport.hp.com/hpp2/newuser.do

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

• HP OpenView Performance Insight Administration Guide

• HP OpenView Performance Insight Guide to Building and Viewing Reports

• HP OpenView Performance Insight Installation Guide

• HP OpenView Performance Insight Reference Guide

To view release notes and other documentation, go to the support web site at:

http://support.openview.hp.com/

Do the following:

1. Click Product manuals under "Using our products."
   The Product manuals search window opens. It is located at:

   http://ovweb.external.hp.com/lpe/doc_serv/

2. In the Product list, click Performance Insight.
3. In the Version list, click 5.1.
4. In the OS list, click the operating system used.
5. Select the Product manual title, and then click Open or Download.

In addition to customizing existing reports and learning how to create your own reports, you also might want to explore advanced features that allow you to integrate OVPI with other systems and import data from other sources. Procedures for using these more advanced features are found in the following guide: Performance Insight TEEL Reference Guide. You can obtain this guide by attending OVPI customer training. For information, go to:

http://www.hp.com/education/courses/u7380s.html

or call your HP sales representative.

NOTE: To view files in PDF format (*.pdf), Adobe Acrobat Reader must be installed on your system. To download Adobe Acrobat Reader, go to the following URL:

http://www.adobe.com

Legal Notices

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

The information contained herein is subject to change without notice.

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.