HP OpenView Performance Insight

for the HP-UX 11.23 operating system

5.1.2 Release Notes

9 March 2006

This document provides an overview of the changes made to HP OpenView Performance Insight (OVPI) for the version 5.1.2 release. The Release Notes contain important information not included in the manuals.

NOTE: Because updated release notes and documentation are posted to the support website on a regular basis, HP strongly recommends that you check the website for newer versions before you use the release notes or documentation shipped on the OVPI documentation CD. To access the website, see Documentation Updates.

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

In This Version

OVPI version 5.1.2 is a new release. It supports only the Itanium platform (HP-UX 11i v2 native) and Oracle (64 bit). OVPI 5.1.2 includes all fixes and enhancements through 5.1 Service Pack 3, including:

HP OpenView Self-Healing Services

HP OpenView Self-Healing Services is a combination of people, process and technology created to enable faster problem resolution. For the customer this means significant time savings and reduced downtime, resulting in maximization of ROI. Self-Healing Services is a collection of software run both at HP and the customer site which detects, collects, analyzes and reports on HP OpenView management software faults. Self-Healing Services automates several steps that were previously manual: fault detection, data collection, data transport, incident analysis, notification and reporting. For the customer this eliminates manual/iterative processes and reduces time consuming and mundane activities. Consult the Self-Healing Services website at http://support.openview.hp.com/self_healing.jsp to verify that support is available on your platform.

Snapshot Graphic User Interface

The new snapshot graphic user interface replaces the deferred node interface in the OVPI 5.1 Web Access Server application. This new interface will improve performance and provide a robust mechanism for selecting nodes and interfaces. It also allows you to save deferred selections as groups.

To select particular nodes and interfaces:

  1. Select the Snapshot report that you want to view.

    The Select Deferred Node Mechanism page opens.

  2. Select the Select nodes and interfaces individually option.

    The Available Report Items page opens. It displays all the nodes and interfaces available.

  3. Select the nodes and interfaces you want to use by selecting a check box next to a specific item. Note that you can also locate and select items by doing the following:
  4. After you have selected all the nodes and interfaces that you want, click Next.

    The Selected Items Summary page opens.

  5. Review the list of items.

    If you want to save the items you have selected as a group, do the following:

    1. Select the Save this search for future use checkbox.
    2. In the Name box, type a name for the group.

      If you type a name that already exists, the name is appended with a number, which increments depending on how many occurrences there are of that group name. For example, if you type "ABCCo" and that name already exists, the group name becomes "ABCCo_1".

    3. In the Description box, type a description for the group. A description is optional.

    To select this group for use in a Snapshot report, select the Select a group of nodes and interface option from the Select Deferred Node Mechanism page.

    NOTE: You can create groups of nodes and interfaces using the Web Access Server; however, to delete or edit these groups, you must use Group Manager, which is available from the Management Console application.

  6. Click Submit in the Selected Items Summary page to display the report with data for the selected nodes and interfaces.

Selecting Colors for Multi-Node Graphs

In previous versions of OVPI, users could control the colors of statistics rendered in single-node graphs but not multi-node graphs, whose statistics used randomly-assigned colors. This posed a problem when the result produced a white graph line on a white background, for example. Report Builder now allows you to select colors for statistics in multi-node graphs using a color map file.

color.prp File

A new file, color.prp, has been added to the $OVPI_HOME/data directory. The file contains, by default, a list of 20 colors in RGB (#FFEEDD) format. The OVPI administrator can change this list by adding or removing color entries.

Multi-node graphs initially utilize the color.prp file to assign colors to the statistics rendered in the graph. For example, the first four colors in the color.prp file could be red, green, blue, and orange, and the first four statistics rendered in the graph will display using these colors. Once the report is saved, the colors are saved within the report file on a per element basis. Therefore, each graph will have its unique color settings, and once saved, the report will utilize the saved colors rather than the values set in the color.prp file.

NOTE: Adding more colors to the color.prp file could affect the loading performance of reports. Once a report is saved, these colors are added to the report file; having a large number of colors may slow the rendering process because these colors are replicated for each graph element in the report.

Using the color.prp File

The Report Builder now contains a new property, "Color Map," for a multi-node graph displayed in the Elements level of the Components tree. Right clicking on the Color Map property opens the Color Map dialog box. The dialog box initially contains the 20 colors from the color.prp file. To change a color, right-click on the color and select a new color from the resulting color palette. Use the buttons in the Color Map dialog box to change the order of the color list, or to add and delete colors from the list.

The Color Map property also contains a Size property, an editable parameter that lets you set the number of colors in the color map. The default is 20, based on the number of color entries in the color.prp file. If you increase the value of the size property beyond the number of available colors in the color.prp file, a random color will be used for each new color entry.

Creating CrossTabs in Reports

With this version of OVPI, you can now create CrossTabs in a report. A CrossTab presents summarized user-defined data in a grid format. A simple example is shown below:

                    Bill    Fred    Joe    TOTAL
Apples         1       2         4        7
Bananas      3       2         0        5
Oranges      2       2         1        5
TOTAL        6        6         5        17

A CrossTab has the following components: rows, columns, and summary fields. In the example above, “Apples” is a row, and “Bill” is a column.  Summary fields are at the intersection of rows and columns.  Each value represents a summary, such as the sum, the maximum, the average, the count and so on, of the records that meet the row and column criteria.  In the example above, the intersection of "Bill" and "Apples" is 1.  This is the number of apples that Bill ate.

At the end of each row is a total for that row.  In the example, the total represents all of the fruit types eaten by Bill, Fred, and Joe.  In this case, there were 7 apples eaten.  At the bottom of each column is a total for the column.  In this example, this represents all of the fruit that each person ate.  In this case, Bill ate 6 pieces of fruit.  Finally, at the intersection of the Total column and the Total row is the grand total.  In this case, this represents the total number of fruits eaten by all of the people, which is 17.  This is a very simple example; however, CrossTabs can be a powerful way to present and summarize information.  If you add multiple row and column fields to group on, CrossTabs can become quite complex.

Creating a CrossTab

To create a CrossTab in a report:

  1. Run Report Builder.
  2. Open a report or create a new report.
  3. On the Report Builder toolbar, click the CrossTab icon.
  4. Do one of the following:

    The Element Name and Description window opens.

  5. Supplying this information is optional. To enter a name and description, go to step 6; otherwise, click Next and go to step 7.
  6. To enter a name and a description for the CrossTab, do the following:
    1. In the Name box, enter a name for the element. (This becomes the element’s Name property in the report’s Properties list.)
    2. In the Description box, enter a description of the element. (This becomes the element’s Description property in the report’s Properties list.)
    3. Click Next.

    The Select a Data Source window opens.

  7. Expand the data source folders and select one of the following options that best suits your requirements:

    Depending on the type of table you selected, one of the following will happen:

  8. Do the following:
    1. Specify if the table you selected from the Select a Data Source window is time-based by clicking Yes or No.
    2. Do one of the following:
      • If you selected No, click Next.
      • If you selected Yes, the Enter the Time Column's Name window opens; select the name of the time column from the list, and click Next. Go to Step 10.
  9. In the text area, type an SQL statement that will define the data for the table, and then click Next. Go to step 15.
  10. Select the statistics that will represent the rows in your CrossTab

    Do the following:

    1. To select a statistic, do either of the following:
      • Double-click a statistic in the Choose from box.
      • Select a statistic in the Choose from box, and click the right arrow button.

      To remove a statistic from the Selected statistics box, double-click the statistic in the Selected statistics box, or select the statistic in the Selected statistics box, and click the left arrow button.

    2. Click Next.
  11. To select the statistics that will represent the columns in your CrossTab, do the following:
    1. To select a statistic, do either of the following:
      • Double-click a statistic in the Choose from box.
      • Select a statistic in the Choose from box, and click the right arrow button.

      To remove a statistic from the Selected statistics box, double-click the statistic in the Selected statistics box, or select the statistic in the Selected statistics box, and click the left arrow button.

    2. Click Next.
  12. To select the aggregations for your CrossTab, do the following:
    1. Click Add. The Add Aggregation Field dialog box opens.
    2. Do the following:
      1. In the Field list, click a field.
      2. In the Aggregation list, click an aggregation.
      3. In the Display Name box, type the display name you want for the aggregation.
      4. Click OK.

      You can also do either of the following:

      • To remove an aggregation, select the aggregation, and click Delete.
      • To edit an aggregation, select the aggregation, and click Modify.
    3. Click Next.
  13. To select nodes and interfaces:
    1. Do one of the following:
      • Click Next to select data from all nodes and interfaces (Use All
      • Click Use Selected Nodes/Interfaces to select specific nodes and interfaces.

        To select specific nodes and interfaces, do the following:

      1. Expand a node’s folder to display its interfaces.
      2. To select a node or an interface, do one of the following:
        • Double-click a node or an interface in the Choose from box.
        • Select a node or an interface in the Choose from box, and click the right arrow button.
    2. Click Next.

    Note: If you select a node, all of its interfaces are automatically selected.

    To remove a node or an interface:

    The Set a Relative The Set Time Period window opens.

  14. To select a time period:

    Do one of the following:

    The Add Titles window opens.

  15. Do the following:
    1. Select a Title check box. Enter a title in the text area. A title can have up to three lines.
    2. Click Next.

    The Summary window opens.

  16. Click Finish.

The CrossTab appears in the Report window, and the CrossTab element and its attributes appear in the components tree as follows:

    Rows -- The list of rows that you selected
    Columns -- The list of columns that you selected
    Aggregations -- The list of columns that will be aggregated in the CrossTab
    Title Area

As with other elements, each of the CrossTabs attributes has additional properties that you can change. When you click on an attribute, its properties display in the properties list portion of Report Builder's components window. Additionally, if you right-click on the Rows, Columns, or Aggregation attribute in the components tree, you can select an option (Change Rows, Change Columns, or Change Aggregations) from a menu to change the rows, columns, or aggregations.   

Following is an example of a CrossTab. In this example, row 1 is dsi_target_name, row 2 is dsi_table_key, column1 is ta_period, and the aggregation is the sum of TOTIfInOctets.

03-22-2005 00:00:00

03-23-2005 00:00:00








3000 (row grand total)





5000 (row grand total)



8000 (row grand total)




500 (row grand total)





8000 (row grand total)



8500 (row grand total)


6000 (column grand total)

10500 (column grand total)

16500 (grand total)

Applying Rules to a CrossTab

You can apply a rule to any of the following fields in a CrossTab: the aggregation summarization (highlighted in yellow in the CrossTab example above) the column grand total (gray in the above example), the row grand total (green in the above example), and the grand total (red in the above example). 

To apply a rule:

  1. Start the Rule wizard by doing either of the following:

    The Rule Name and Description Window opens.

  2. Do either of the following:

    The Apply Rule to the Selected Field window opens.

  3. Select the fields in the CrossTab to which you want to apply the rule.
    1. Do either of the following:
      • Select a field in the Choose from box, and click the right arrow button.
      • Double-click a field in the Choose From box.
    2. Click Next.

    If you need to remove a selected field, do either of the following:

    The Add Rule Clauses window opens.

  4. Add rule clauses.
    1. Click the New button. A clause row is added.
    2. Click the Operator box, select an operator, and then press the TAB key.
    3. Type a value in the Value box, and then press the TAB key.
    4. Type a label for the clause in the Clause Label box, and then press the TAB key.
    5. Select one of the following options from the Set box to indicate what will occur when a rule is satisfied:
      • Background. Displays a color behind the field’s data. When a rule is satisfied, the field can be highlighted with red.
      • Image. Displays an image instead of the field’s data. When a rule is satisfied, an image of a check mark can display.
      • Text. Displays user-specified text instead of the field's data. When a rule is satisfied, the text “Full” can display.

      Note: Even though Statistic appears as an option, you cannot use this option for a CrossTab.

    6. Click the To box, then do one of the following depending on the option you selected in the Set box:
      • Background. Select a color from the Select a Color dialog box.
      • Image. Locate an image using the Open dialog box.
      • Text. Type the text you want to display in the To box.

      Note: Even though Statistic appears as an option, you cannot use this option for a CrossTab.

    7. Repeat steps a through f to add additional clauses.
    8. To delete a clause from the list, select the clause, and then click Delete.
    9. To rearrange the order in which the clauses will be evaluated, select the clause, and then do one of the following:
      • Click the up arrow to move the clause up in the list.
      • Click the down arrow to move the clause down in the list.
    10. Click Next.

    The Summary window opens.

  5. Review the rule summary, and click Finish to create the rule.

See Chapter 6 in the "Guide to Building and Viewing Reports" for information about creating rules.

Drilling Down in a CrossTab

Drilling down in a CrossTab is different from drilling down in a table.  You can only use columns that are in the RowFields list as drilldown source columns.  This is because the CrossTab does not have a one-to-one mapping from the computed fields to the rows of the underlying data table.  When the CrossTab is viewed using the Web Access Server, drilldown icons will appear in the same way as those do for tables.

Creating Report Links to CrossTabs

As with drilldowns, report links will work differently for CrossTabs than for tables.  You can only use columns that are in the RowFields and the ColumnFields lists as link output statistics.  Additionally, links originating from other report elements may not use data from fields in the CrossTab element like tables and graphs can.

Documentation Updates

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

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

NOTE: The install instructions in the 5.1.2 Installation guide is applicable to OVPI 5.x versions too.

The Installation Guide and the Release Notes is updated following the OVPI Documentation CD shipment. To check for recent updates or to verify that you are using the most recent edition, visit the following URL:


  1. In the Product list, click the product name.
  2. In the Version list, click the version number.
  3. In the OS list, click the OS type.
  4. In the document list, click the document title.
  5. To retrieve the document, click Open or Download.

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:


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 or you can contact HP Support representative.

Installation Notes

Installation requirements, as well as instructions for installing OVPI are documented in the Performance Insight Installation and Upgrade Guide for Oracle Databases provided in Adobe Acrobat (.pdf) format. The guide contains the preparations and requirements necessary for installing OVPI for Oracle databases.

Review the release notes prior to installing the product. For OVPI documentation information, refer to Documentation Updates section.

NOTE: You must install all operating system patches before you install your Oracle database or OVPI. For a complete list of patches required by your operating system, refer to Software Requirements section.

Software Requirements

This section describes the software requirements for OVPI 5.1.2.

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 11i V2 (B.11.23) (Itanium) Oracle All

Operating System Patch Information

Before installing OVPI, make sure that your HP-UX operating system is at the correct patch level. Use the following command to determine which patches have been installed.

/usr/sbin/swlist -l product | fgrep PH

The minimum patch bundle level required for OVPI 5.1.2 is the HP-UX 11.23 patch bundle for Itanuim (IA), BUNDLE11i B.11.23.0409.3. This was released in September 2004. A later version of the patch can also be used.

If you plan to install OVPI Web Access Server on an HP-UX 11.23 system, you must install the PHSS_34201 (s700_800, 11.23 Aries cumulative patch) patch. This patch provides defect fixes and performance updates for OVPI Web Access Server. To download the patch, go to the following URL:

NOTE: The following HP-UX patches may cause OVPI installation to fail. Additional information and workaround is documented in the Known Problems, Limitations, and Workarounds section.

Enhancements and Fixes

The following items are improvements to OVPI.

QXCR1000299175: OVPI stores write community strings in encrypted format in the database. As part of this enhancement, only OVPI Administrator will be able to view and change these community strings. The OVPI Administration Console is also enhanced to accept new write community strings as password fields. A form has been added in the Object manager to update the system generated community profile names to user preferred names. It is highly recommended to use this form to change system generated community profile names to more user readable profile names.

QXCR1000282606: OVPI performs history collection from OVPA/EPC agents. The pa_collect utility of OVPI is responsible for this history collection and needs to know the start time and end time of collection. Initially, the default start time of the collection is Yesterday at Midnight. Thereafter, pa_collect stores the last timestamp of collected data in the OVPI database in the lastPoll column of the history table, so that the next time it is run, pa_collect can use this lastPoll value as the start time of collection. However, if the database is down, pa_collect cannot update the OVPI database. As a result, while the database is down pa_collect runs and collects data from the same start time (the last time it collected data) to the current time. This results in duplicate data being cached in files under the COLLECT_HOME directory. The enhancement allows pa_collect to track its last collection time whenever the database is down and stores that data in a flat file called CollectDef file . This allows pa_collect to collect only incremental data (cached in files under COLLECT_HOME directory) whenever the OVPI database is down.

QXCR1000218022: As part of this enhancement, users can display the entire query period in a graph rather than the period constrained by the returned query or max rows. For example, if a query specifies data from 12 Noon to 12 Midnight, but data is only returned for the period from 5 PM to 12 midnight, the graph shows the full queried time period but shows no data for the unreported period from 12 Noon through 4 PM.

To implement this optional behavior, users must change the following property to "true" in order for the enhancement to work. This property is located in the /OVPI/data/config.prp file.

graph.entire.query.period = true

Leaving this property as "false" renders the graph as before where the start and end of the graph are constrained to the results of the query rather than the constraints of the query itself.


The OVPI issues listed below are now resolved.

Command Line Utilities

QXCR1000216645: Scheduling reports using command line throws Null Pointer Exception


QXCR1000196434: Need to provide template script/documentation to create dsi_dpipe user and table.

Data Collection and Summarization

QXCR1000190149: Generation of bcpg rules should be more efficient.
QXCR1000208816: "trend_sum -f file.sum" command fails to create and execute the stored sum procedure.
QXCR1000196522 and QXCR1000113133: The trendcopy command copies a table to the destination database without copying the data records.
QXCR1000026634: Use of type discovery with viewname containing spaces fails snmpv2dis.
QXCR1000027243: Trendcopy failed due to schema change.
QXCR1000029561: trend_proc -f takes input file without the proper file format.
QXCR1000029563: trend_proc raises DEF_ERROR when debug level is 4.
QXCR1000029594: Trendtimer does not log error messages when offset is invalid.
QXCR1000029595: The argument MONTH accepts an invalid entry.
QXCR1000031052: Index "Identifier is too long" error from r2d procedure.
QXCR1000050087: The number of rows does not match the hour of day summarization.
QXCR1000050532: The trend_sum baseline forecast slows down over time.
QXCR1000086350: Datapipes are not cleaned up when tables are removed.
QXCR1000188687: trendcopy hangs during copy from Sybase to Oracle.
QXCR1000191363: trendcopy 50SP1 fails to copy raw tables on Solaris platform.
QXCR1000193328: BCP Gateway fails for IRifEntry_Duplex_Datapipe.
QXCR1000194032: trendcopy hung during the copy of SDGTW_GATEWAY_LOC during the copy.
QXCR1000196590: pa_discovery does not work with just -t option specified.
QXCR1000197888: trend_sum forecasting are inaccurate.
QXCR1000205488: Indexmaint is running on upload and keys tables.
QXCR1000205910: The R2D procedures are not dropping indexes correctly.
QXCR1000207225: The trend_sum procedures hang for DR and IR summaries.
QXCR1000212142: There is a bcp_gateway memory problem.
QXCR1000213563: ovpi_run_sql does not use the correct Oracle home directory ($ORACLE_HOME), so report pack installations fail.
QXCR1000214806: The update worktable bcpg rule is incorrectly generated in OVPI 5.0 for Oracle only.
QXCR1000216513: ovpi_run_sql fails if arguments are very long.
QXCR1000217868: Datapipe manager doesn't allow a number data type with a precision other than 10.
QXCR1000220063: The bcp_gateway produces errors when locking the upload table.
QXCR1000220282: SNMP error messages should be clearer.
QXCR1000223584: trend_sum fails to run the procedure and aborts.
QXCR1000224683: snmpv2dis is missing from a remote poller installation.
QXCR1000228509: On Oracle, collections fail for complex foreign key conditions.
QXCR1000230966: trend_export options are ignored in an .ini file.
QXCR1000232323: OVPI version 5.0 and 5.1 versions of the Action Poller are slower than 4.6 version.
QXCR1000233734: OVPI 4.6 Service Pack 4's R2D generator produces bad procedures.
QXCR1000235895: When using trendcopy with Oracle, it displays errors when you attempt to copy only data for certain hours of the day and days of the week.
QXCR1000236313: The R2D procedures are not dropping indexes on upload tables.
QXCR1000236532: Occasionally, trendtimer will not start as a service because of an invalid file handle.
QXCR1000238667: ee_collect leaves files in the tmp directory.
QXCR1000049708: Running indexmaint with an improper command-line argument now shows the default "usage" listing of arguments instead of returning an error message.
QXCR1000157015: collection_manager now creates new installed datapipes as necessary.
QXCR1000220087:On Oracle, when uploading huge files, bcp_gateway fails and returns an error. Oracle is running out of maximum cursors per session.
Workaround: OPEN_CURSORS parameter in the "init.ora" specifies the maximum number of open cursors (handles to private SQL areas) a session can have at once. It is important to set the value of OPEN_CURSORS high enough to prevent the application from running out of open cursors.
To set your OPEN_CURSOR value to a higher one, do the following in SQLPLUS:

  1. SQL> show parameter OPEN_CURSORS;

    Displays the current value of max open cursors possible per session.

  2. To alter this value to a higher value:
    SQL> ALTER SYSTEM SET OPEN_CURSORS = <<value >> {scope=spfile};

    Value can range from 1 to 4294967295
    {} => optionally specify the scope.

  3. Restart ORACLE database.

NOTE: Changing this parameter does not effect performance in any way but Oracle will now need a little more memory to store the cursors.
QXCR1000239152: mw_collect now recognizes the community string in the parameter "ELEMENT".
QXCR1000241601: dip_manager code has been changed to export all groups without errors and exceptions.
QXCR1000245722: trendcopy no longer fails to copy OVPA History tables because a number check has been added which has fixed the problem.
QXCR1000279248: Creating a file using the datatype smalldatetime resulted in an error when datapipe_manager attempts to create the table. The datatype is now properly supported.
QXCR1000280608: Node manager created new device names if names differed in capitalization. Now, names that differ only by the case of their text are treated as identical names.
QXCR1000282616: After a successful run of mw_collect all the appropriate files are deleted; this avoids any problems during later runs of mw_collect..
QXCR1000283517: Trendcopy's error handling mechanism no longer prints or logs the same error message multiple times, preventing trend.log from growing until it fills up the filesystem.
QXCR1000284467: The OVPI utility datapipe_manager has been modified to delete views/tables properly so that no error messages are received.
QXCR1000284618: The OVPI collection mechanism has been changed to delete .instance files at the end of each collection cycle.
QXCR1000285524: dpipe_pa is spawned from the trendadm shell and no longer resets the environment for each child collector.
QXCR1000288772: A problem that caused Threshold processing to inserted a value too large for a column now rounds to a shorter number.
QXCR1000289013: The utility pa_discovery has been modified so that it displays data sources correctly when the type of data is "DSI" data.
QXCR1000293214: If the RPC agent fails on a particular machine, dpipe_pa utility now continues processing even if an attempt to collect data from a node fails.
QXCR1000295665: If there are multiple logs with the same OVPA class, pa_collect doesn’t get all the data records and only keeps the last data record. To fix this issue, data sources now handle multiple log files.
QXCR1000300186: A database query change has improved response times for Trendpms device resource collections.
QXCR1000300237: A problem causing the ovis_datapipe to not be recognized has been fixed.
QXCR1000301136: If duplicate rows are collected from an agent, trendpm now filters out one of the duplicate rows instead of deleting both.
QXCR1000305709: trend_sum no longer runs slowly if some devices become inactive.

Web Access Server

QXCR1000233353: The report scheduler needs a modified pick list. See "Snapshot Graphic User Interface" for details.
QXCR1000202453 and QXCR1000205885 I18N: Japanese Data included in downloaded file is broken
QXCR1000217184 : Event deletion is not working for "system" schedule.
QXCR1000215994: WAS does not open when secure port is 443.
QXCR1000027065: Expanded drilldowns with multiple wildcards breaks query.
QXCR1000027354: Changing max rows in webpage causes time ranges to change.
QXCR1000027678: When a large node group is created the query on KV_IRDevports fails.
QXCR1000210657: The line colors in a graph differ between Report Builder and the Web Access Server.
QXCR1000215408: Table names not in uppercase on Oracle for deferred node group evaluations.
QXCR1000216256: The deferred node selection feature in OVPI 5.0 does not work.
QXCR1000221772: There are problems when searching for nodes in snapshot reports.
QXCR1000222974: If you run 2 Near Real Time Snapshot reports back-to-back, the second report times out after 10 minutes.
QXCR1000227296: The search feature does not work for snapshot reports when you search from a non-first page.
QXCR1000228213: When using the deferred node wizard, some database connections are not closed.
QXCR1000237944: There is a discrepancy between actual data and how that data is rendered in a report.
QXCR1000239044: The Web Access Server fails to send email.
QXCR1000241847: Report link relations display incorrectly.
QXCR1000243071: Report data is not displayed in chronological order.
QXCR1000243269: When you view reports in Report Builder or the Web Access Server using an Oracle database, the maximum cursor open error is displayed. No report data is displayed after this error displays.
QXCM1000245736: If the Oracle database system goes down, OVPI will not reestablish its connection to the database.
QXCR1000241607: In Interface Reporting Near Real Time Snapshot report, selecting an interface whose InterfaceName contains a colon (:) no longer causes the Selected Items Summary screen to truncate the InterfaceName after the colon.
QXCR1000245253: Opening a static report in Builder no longer displays the dsi_table_key twice in the legends.
QXCR1000285975: Displaying a bandwidth report which has multiple nodes and multiple statistics selected now displays correctly, even when one of the statistics is missing.
QXCR1000291339: Opening a static report in Builder no longer displays incorrect x-axis time scale information.
QXCR1000292763: Red bars that highlight 'holes' in data now appear correctly.
QXCR1000294537: Changing the Application Server port number now correctly updates the Systems.xml file, allowing other applications like piadmin and builder to log in to AppServer.
QXCR1000295847: When using the Web Access Server (WAS) to view a report, selecting "Download - PDF" now correctly displays a PDF that accurately represent the view of the report as displayed in the WAS.
QXCR1000300121: When creating a new report in builder, specifying a combobox element now works correctly when the combobox width is resized.
QXCR1000300889: When enabling SSL and disabling non-secure connections, the Update Node form now loads correctly load into the management console.
QXCR1000301059: German umlaut characters now correctly appear in scheduled reports.
QXCR1000301085: Custom reports that have values where x1>x2 or y1>y2 now display correctly in the pdf.
QXCR1000302369: MultiNode/MultiStatistic plot and scatter graphs with missing data now correctly display.

Report Builder/Viewer

QXCR1000201461: The snapshot feature is unusable for a large number of nodes. See "Snapshot Graphic User Interface" for details.
QXCR1000219599: There needs to be a new method to find nodes in reports. See "Snapshot Graphic User Interface" for details.

QXCR1000202453 and QXCR1000205885 I18N: Japanese and traditional Chinese symbols do not appear in the label component of .PDF and .CSV formatted files generated from an OVPI report.
QXCR1000027678: When a large node group is created the query on KV_IRDevports fails.
QXCR1000086940: Node selection is ignored using overlay reports.
QXCR1000210657: The line colors in a graph differ between Report Builder and the Web Access Server.
QXCR1000215503: White graph lines on white background do not display.
QXCR1000223571: The x-axis annotation font size does not work when you graph by node.
QXCR1000224982: The $N$ variables are not consistent in a graph's legend.
QXCR1000230883: Monthly graphs can display incorrectly since hole graphing was introduced.
QXCR1000232748: Legend and graph elements do not match when one column is missing data.
QXCR1000235257: The hole style interpolation is not working.
QXCR1000236460: When you display a by-time graph with multiple selected statistics, the database columns are incorrectly assigned to the graph's statistics if the first row has SQL-NULL values in it.
QXCR1000237944: There is a discrepancy between actual data and how that data is rendered in a report.
QXCR1000243212: When you print a report from Report Builder or Report Viewer, all of the report is not printed.
QXCR1000243269: When you view reports in Report Builder or the Web Access Server using an Oracle database, the maximum cursor open error is displayed. No report data is displayed after this error displays.
QXCR1000243292: The graph legend does not match the data in a graph.
QXCR1000193627: Specifying a link-source from a combo-box where the destination is a table now works correctly.
QXCR1000195163: Adding a custom statistic no longer causes GOS parameters to not appear.
QXCR1000196241: Changing the Overlay Data Table no longer results in change of table name under Data.
QXCR1000290772: Problems with URL addresses that previously caused Builder to not open reports in a web browser have been fixed.
QXCR1000299221: Graphs in .rep files are now displayed correctly because a time stamp issue that resulted in erroneous information has been fixed.

Management Console

QXCR1000191266: piadmin GUI would not all a selection of SNMP Ports > 9999.
QXCR1000216486 : Using Object Manager to export a file after aborting an export causes a Java exception.
QXCR1000216471 : "Set Max Rows" option is not working from Table manager in piadmin.
QXCR1000215472: Selecting a report while doing undeploy is not working properly.
QXCR1000215721: Exporting links when links does not contain a directory causing empty directory.
QXCR1000214909: Problem in deleting report for other user in catalog manager (piadmin).
QXCR1000218823 and QXCR1000215514: Exception in Catalog Manager on Cyclic report links.
QXCR1000218821 : Window resize issue in catalog manager.
QXCR1000201479: There is a problem when trying to switch servers in the Management Console.
QXCR1000202414: There is a problem creating groups in the Management Console.
QXCR1000215544: The multiple sorted selection in the Management Console selects incorrect objects.
QXCR1000235948: When you edit a managed node, the status (available/unavailable) shown in the combo-box is different
from the current status.
QXCR1000236043: When you import nodes using node_manager, node manager has problems reading a CSV file.
QXCR1000191983: In an OVPI Oracle system, when the Management Console - Table Manager is launched it now allows you to save a property table definition.
QXCR1000226013: Adding an empty Hi-Lo pair in collection no longer produces an error.
QXCR1000279746: The rediscovery of flagged interfaces are defined in the polling policies based on the custom groups discovery process. The query based on the group definition was wrong and has been corrected.


QXCR1000225543: There is a problem with the threshold Perl script.

Known Problems, Limitations, and Workarounds

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

Installing OVPI 5.1.2

QXCR1000310465: When you install OVPI 5.1.2 on HP-UX 11.23, the installation may fail with the following error:
/usr/lib/hpux32/dld.so: Unsatisfied data symbol ,__libCsup_mutex_context' in load module “/usr/lib/hpux32/libstd.so.1'."

This occurs when the following patches are installed on the HP-UX system.

Workaround: Uninstall the patches mentioned above and then install OVPI. To uninstall the patches, use the following command at the command line:

swremove < patch_name >

Installing Report Packs

When you install Report Packs from the RNS CD, the installation may fail. The following error will be logged in the trend.log file:
ORA-08120: Need to create SYS.IND_ONLINE$ table in order to (re)build index

Workaround: Run the following script and then reinstall the Report Packs:

Installing Oracle on HP-UX 11.23

When you attempt to install Oracle on HP-UX 11.23, Oracle will not install. 

You will see the following:

$ runInstaller
Starting Oracle Universal Installer...
Checking installer requirements...
Checking operating system version: must be B.11.00 or B.11.11. Actual

Failed <<
Exiting Oracle Universal Installer, log for this session can be found at .......

You will also see the same result if you use the -ignoreSysPrereq option with the runInstaller command.

This occurs because the oraparam.ini file does not check for HP-UX B.11.23.

Workaround: Edit the oraparam.ini file by adding the version number to the HP-UX parameter. For example, the HPUX parameter in the file should appear as follows after you edit it:


Installing CiscoCDR_Datapipe


Network Node Manager (NNM) Integration with OVPI 5.1.2


Please visit the HP OpenView web site at:


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:


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:

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:


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


Legal Notices

©Copyright 2006 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.