Tuesday, 12 October 2010

Each OMS Startup Adds the Error "Integration Class not found" in the emoms Logfiles

Applies to:

Enterprise Manager Grid Control - Version: 10.2.0.5 and later   [Release: 10.2 and later ]
Information in this document applies to any platform.

Symptoms

Each time 10.2.0.5 OMS is restarted, the following errors are logged in $OMS_HOME/sysman/log/emoms.trc file:

<Timestamp> [Orion Launcher] ERROR app.ContextInitializer contextInitialized.453 - Integration Class not found: oracle.sysman.test.pp.common.intg.ProvTestIntg
<Timestamp> [Orion Launcher] ERROR app.ContextInitializer contextInitialized.453 - Integration Class not found: oracle.sysman.pp.paf.sample.ui.intg.PAFDemoIntegration


 

Cause

This is due to an internal bug: "error in emoms.trc:oracle.sysman.pp.paf.sample.ui.intg.pafdemointegration".  The bug is fixed in Grid Control 11.1.

Solution

These error messages can be safely ignored. They are due to some misconfigured integration class XML files, but do not prevent the Provisioning Framework to work as expected.

Workaround

1. Backup and edit $OMS_HOME/j2ee/OC4J_EM/applications/em/em/WEB-INF/config/empp_intg.xml.
Remove the line:

<integration name="provtest" class="oracle.sysman.test.pp.common.intg.ProvTestIntg"/>


2. Backup and edit $OMS_HOME/j2ee/OC4J_EM/applications/em/em/WEB-INF/config/demo_intg.xml.
Remove the line:

<integration name="demo.ui"
class="oracle.sysman.pp.paf.sample.ui.intg.PAFDemoIntegration"/>


3. Bounce the OMS.

No comments: