After installing Oracle Application Server 10.2.0.2, with corresponding OID, Grid Control 10.2.0.5 gave me the obove mentioned error, and the the item OID a ‘metric collection error’.
To fix the metric collection error downloaded and applied Patch 5686191 on top of OID product.This is a sql-script to run against the OID-repository. Unpublished bug according to note 764088.1
Shutdown the DAS:
~/media/5686191> opmnctl stopproc process-type=OC4J_SECURITY
~/media/5686191> /software/oracle/product/10.2/infra/OPatch/opatch apply
Oracle Interim Patch Installer version 1.0.0.0.52
Copyright (c) 2005 Oracle Corporation. All Rights Reserved..
We recommend you refer to the OPatch documentation under
OPatch/docs for usage reference. We also recommend using
the latest OPatch version. For the latest OPatch version
and other support related issues, please refer to document
293369.1 which is viewable from metalink.oracle.com
Oracle Home = /software/oracle/product/10.2/infra
Location of Oracle Universal Installer components = /software/oracle/product/10.2/infra/oui
Location of OraInstaller.jar = “/software/oracle/product/10.2/infra/oui/jlib”
Oracle Universal Installer shared library = /software/oracle/product/10.2/infra/oui/lib/linux/liboraInstaller.so
Location of Oracle Inventory Pointer = /etc/oraInst.loc
Location of Oracle Inventory = /software/oracle/product/10.2/infra/inventory
Path to Java = /software/oracle/product/10.2/infra/jre/1.4.2/bin/java
Log file = /software/oracle/product/10.2/infra/.patch_storage/<patch ID>/*.log
Backing up comps.xml …
OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Please shut down Oracle instances running out of this ORACLE_HOME
(Oracle Home = /software/oracle/product/10.2/infra)
Is this system ready for updating?
Please respond Y|N >
~/media/5686191> Y
Patching…
Updating inventory…
Backing up comps.xml …
OPatch succeeded.
Is the script there?
ls -al /software/oracle/product/10.2/infra/ldap/admin/oidtdip.sql
Run this script as the owner of the repository, in this case mostlikely ODS.
Start the DAS:
~/media/5686191> opmnctl startproc process-type=OC4J_SECURITY
opmnctl: starting opmn managed processes…
It may take a while before the management repository will update the change.
Did this resolve your problem?
I have come across the same issue and patching does not appear to have resolved the issue.