Unable To Start SOA After Database Was Cloned Due To MDS-01330 Error
Last updated on DECEMBER 01, 2016
Applies to:Oracle SOA Suite - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Deployment
Unable to start SOA after database was cloned.
Cloned the database from the existing 18.104.22.168 SOA installation.
After the clone, performed the following on the TEST database:
1. re-created the SOA schema tablespaces
2. re-created the non-prod SOA db users
3. exported the prod SOA db users
4. imported the dmp file to the TEST SOA db users.
The node manager and admin server would start fine.
However, the SOA server does not start. The log file shows these:
<Apr 14, 2014 11:25:29 AM MDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "mds-soa": ORA-28000: the account is locked.>
<Apr 14, 2014 11:25:30 AM MDT> <Error> <oracle.mds> <BEA-000000> <
oracle.mds.lcm.exception.MDSLCMException: MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "soa-infra-store" is invalid.
MDS-01376: Unable to get database connection from data source "mds-soa" configured with JNDI name "jdbc/mds/MDS_LocalTxDataSource".
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: ORA-28000: the account is locked
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