OID 11g oid1 Shows As Down in EM FMW Control Console. WLS Admin Server Log Shows: Caused by: javax.management.MBeanException: ODL-52501: Unable to get OPMN connection for instance 'asinst_1'; check that the instance name is valid and that OPMN is running.

(Doc ID 2387972.1)

Last updated on APRIL 19, 2018

Applies to:

Oracle Internet Directory - Version 11.1.1 and later
Information in this document applies to any platform.

Symptoms

Oracle Internet Directory (OID) component (e.g., oid1) status is showing as down (red arrow) in Enterprise Manager (EM) Fusion Middleware (FMW) Control console.

The WebLogic (WLS) Admin Server diagnostic log shows:

Caused by: java.lang.Exception: query setup failed for secure target WLS MBean [oracle.logging:type=LogQuery,name=ProxyLogQuery,Location=AdminServer], Search Criteria [From Time: 2018-01-04T02:38:23.990 -0500, To Time: 2018-01-04T03:38:23.990 -0500, Selected Message Types [INCIDENT_ERROR:ERROR:WARNING:NOTIFICATION:TRACE:UNKNOWN:]], maxMessagesToFetch: 1000], Target List [/Farm_IDMDomain/asinst_1/oid1,oracle_ldap][oracle.as.management.mbeans.register:instance=asinst_1,Location=AdminServer,EMTargetType=oracle_ldap,name=/asinst_1/oid1,component=oid1,type=SystemComponent]
  at oracle.sysman.core.model.logmgmt.mas.MASLogProvider.getLogMessages(MASLogProvider.java:781)
  at oracle.sysman.core.model.logmgmt.mas.MASLogViewer.getLogMessages(MASLogViewer.java:402)
  at oracle.sysman.core.model.logmgmt.msgs.LogProviderRunner.doLogMessagesSearch(LogProviderRunner.java:133)
  ... 2 more
Caused by: javax.management.MBeanException: ODL-52501: Unable to get OPMN connection for instance 'asinst_1'; check that the instance name is valid and that OPMN is running.

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms