ADMN-202046 When Starting OC4J_Security After Restoring the Metadata Repository Database (Doc ID 453650.1)

Last updated on SEPTEMBER 06, 2016

Applies to:

Oracle Fusion Middleware - Version: 10.1.2.0.2 and later    [Release: AS10gR2 and later]
Information in this document applies to any platform.
Oracle Application Server 10g Enterprise Edition - Version: 10.1.2.0.0 to 10.1.2.3.0
***Checked for relevance on 06-Mar-2012***

Symptoms

After restoring an old Metadata Repository database backup, HTTP Server and OID start successfully but OC4J_Security fails to start. The following error is produced by DCM:

ADMN-202046
The OracleAS Repository API threw an exception when obtaining the connect string to the Metadata
Repository
Resolution:
Check the exception thrown by the Repository API for resolution information.
Some common causes of this problem are as follows:
OID is not running or unavailable
the ias.properties file is misconfigured with incorrect OID connection information
OID permissions are incorrectly defined
Base Exception:
oracle.ias.repository.schema.SchemaException
Unable to establish connection to the Oracle Internet Directory Server ldap://ldapdb.hostname.com:3060/. Base Exception : javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
oracle.ias.repository.schema.SchemaException: Unable to establish connection to the Oracle Internet Directory Server ldap://ldapdb.hostname.com:3060/. Base Exception : javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]

Changes

The data from a Metadata Repository database backup (generated by using backup_restore.sh)  has been restored to MR, but the associated configuration files were not restored. 

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