HP Operations Smart Plug-in for Oracle Application Server

for HP Operations Manager for Windows

Release Notes

Software version: 5.10/ December 2007

This document provides an overview of the changes made to the HP Operations Smart Plug-in for Oracle Application Server (Oracle AS SPI) for HP Operations Manager for Windows 8.00. It contains important information not included in the manuals or in online help.

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

NOTE: To reduce clutter, this document collapses certain blocks of text under special links. Click the link to expand the collapsed text.

Collapsed text example

Important: Collapsed text does not print. To print this document, first scan through it, expanding the text of interest before you print. Alternatively, click the Show all or Hide all button to toggle between showing or hiding all collapsible text.

In This Version

The following new features are supported in this version:

Documentation Updates

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

To check for recent updates or to verify that you are using the most recent edition, go to the following web site:

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 web site:

Installation Notes

Installation instructions for installing WBS SPI, are documented in the HP Operations Smart Plug-in for Oracle Application Server Configuration Guide provided in Adobe Acrobat (.pdf) format. The document file is included on the product's DVD media as:

\Documentation\SPI Guides\Oracle_AppServer_Config.pdf

Software and Hardware Requirements

Before installing the Oracle AS SPI, make sure that your system meets the following minimum requirements:

NOTE: Support on Windows X64 nodes is available only on DCE Agents in 32 bit emulation mode.

Enhancements and Fixes

To display details about each software enhancement or fix, click the reference number link to go to the HP Online Software Support web site. The first time you click a link, you must enter your HP passport information. To set up your passport profile, go to:



QXCR1000382131: OASSPI log file template does not work

QXCR1000456111: OAS discovery run the oracle scripts as superuser

Known Problems, Limitations, and Workarounds

The following problems are known in the current software release. To display details about each problem (including workaround information), click the problem text. To hide details, click again.

Problems and Workarounds

Support for HP-UX 11.31 IA not available for the DCE agent managed nodes
Problem: Support for HP-UX 11.31 IA is not available in OASSPI for the DCE agent managed nodes.
Cause: The instrumentation folders OASSPI Discovery and SPI for OracleAS are not present at the required location.

On the OVO for Windows 7.50 system, copy the OASSPI Discovery and SPI for OracleAS folders from C:\Program Files\HP OpenView\Data\shared\Instrumentation\HPUX\B.11.31 PA to C:\Program Files\HP OpenView\Data\shared\Instrumentation\HPUX\B.11.31 IA.

On the HPOM for Windows 8.00 system, copy the OASSPI Discovery and SPI for OracleAS folders from C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software\Data\shared\Instrumentation\HPUX\B.11.31 PA to C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software\Data\shared\Instrumentation\HPUX\B.11.31 IA.

Discovery, Discover OracleAS, and (or) Configure OASSPI tool hangs
Problem: The Discovery policy, the Discover OracleAS tool, and (or) the Configure OASSPI tool hangs.
Cause: When you run any of these components the configuration file is locked so that the file cannot be overwritten. If you select STOP in the Console Status window or these components are stopped while running because of any other reason (for example, a failover), the lock is not removed from the configuration file. When you start any of these components again, the component waits for the lock to be removed before it can continue.

Remove the lock directory on the management server: <OvOWShareInstallDir>\SPI-Share\wasspi\oas\conf\SiteConfig.lock

where <OvOWShareInstallDir> is typically (for HPOM for Windows 8.00) C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software\shared.

The locking mechanism automatically deletes the lock directory after two hours.

Tracing stops or the collector hangs when tracing is on
Problem: If tracing is enabled, when the first 20 MB trace file limit is reached, tracing either stops or the collector hangs and stops monitoring the web application servers.
Workaround: Enable tracing for a short duration of time (for example, 5-6 hours) because the 20 MB limit of the trace file is reached in approximately 7 hours.
Discover OracleAS or Configure OASSPI tool may misplace the SPI configuration file on a managed node
Problem: If multiple managed nodes are selected when running the Discover OracleAS or Configure OASSPI tool, or if the Discover OracleAS and Configure OASSPI tools are run at the same time, the SPI may report errors for one or more selected managed nodes because the SPI configuration file for one or more managed nodes are misplaced.
Workaround: Run the Configure OASSPI tool for each managed node that is reporting errors (run the tool on each managed node one at a time).
The output file created by Self-Healing Info tool is hidden
Problem: When the Self-Healing Info tool is run on a Windows managed node, the output file may be hidden.

If you do not see the file, do the following on the managed node:

  1. Open Windows Explorer.
  2. From the Tools menu, select Folder Options.
  3. Click on the View tab.
  4. Under Hidden files and folders, select Show hidden files and folders.
On a Solaris managed node, the ddflog and dsilog processes hang
Problem: On a Solaris managed node, the ddflog and dsilog processes hang. The error message
WASSPI-1: Unable to create the lock file /var/opt/OV/wasspi/oas/datalog/ddflog.lck. File already exists. is reported and running the command ps –l shows that the ddflog_coda and ddflog or dsilog processes are hung.

On each Solaris managed node on which the problem occurs, do the following:

  1. In the /var/opt/OV/wasspi/oas/conf/SPIConfig file, set the DATA_LOGGING_EXECUTABLE_NAME
    property after the “#--------- Dynamic definitions -----------“ entry. DATA_LOGGING_EXECUTABLE_NAME explicitly sets the data logging program that is used (normally, the collector automatically determines the data logging program to use).
  2. If you are running OVPA, set the property to the following value:

    If you are running CODA, set the property to the following value:

  3. Kill the hung ddflog_coda and ddflog or dsilog processes. Example excerpt from the SPIConfig file after setting the property:

    #--------- Dynamic definitions -----------

SPI's configuration log on a managed node grows without being managed for size
Problem: Information is appended to …/oas/log/config.log file whenever the SPI's configuration is run (either manually or when the discovery process finds a change that requires configure to run such as a Oracle Application server being added or removed). Unless there are frequent changes to the environment requiring reconfiguration, this should not be a problem.
Workaround: Manually delete the file if it gets too large.
Error message appears for managed nodes running Red Hat Linux 4

For a managed node running Red Hat Linux 4 or SuSe Linux 9.1or 9.2, both discovery and metric threshold monitor alarming or one of them is not functioning and the following error message is found in the SPI error log:
*** glibc detected *** double free or corruption: 0x0937d008 ***

Workaround: On the OVO agent, set the MALLOC_CHECK_ environment variable to 0 (zero) and restart the agent.
The uninstallation process does not uninstall Oracle AS SPI completely
Problem: In a cluster environment, the uninstallation process may not remove the SPI for Oracle Application Server tool group, policy group, and some policies.
Workaround: Manually delete the tool group, policy group and policies from the management server console.


Documentation Errata

The default path for <AgentDir> on Windows managed node is documented as <drive>\Program Files\HP OpenView\Data in the Online Help and Configuration Guide. This is the default path for <AgentDir> on HTTPS managed nodes (Windows) for HPOM for Windows 8.00.

On DCE managed nodes (Windows) the default path is :

<AgentDir> = C:\Program Files\HP OpenView\Installed Packages\{790C06B4-844E-11D2-972B-080009EF8C2A}


You can visit the HP Software Support web site at:

This web site provides contact information and details about the products, services, and support that HP 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:

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

Legal Notices

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

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

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

The information contained herein is subject to change without notice.