Slow Managed Server Startup After 'Invalid MDS configuration specified in: "OWSM_TargetRepos"' Error
(Doc ID 2240461.1)
Last updated on AUGUST 12, 2024
Applies to:
Oracle SOA Suite - Version 12.2.1.1.0 and laterInformation in this document applies to any platform.
Symptoms
At managed server startup, there is an issue when deploying OWSM
[2017-03-01T13:12:37.041-08:00] [SOA3UAT_soa3_server1] [WARNING] [] [oracle.mds] [tid: [STANDBY].ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: OracleSystemUser] [ecid: aa5007b3-e9d6-4726-a39a-754e855227a4-0000000a,0] [APP: wsm-pm] [partition-name: DOMAIN] [tenant-name: GLOBAL] MDS-01367: Failed to create PConfig. Invalid MDS configuration specified in: "OWSM_TargetRepos" [[
oracle.mds.persistence.MDSIOException: MDS-00929: unable to look up name "jdbc/mds/owsm" in JNDI context
javax.naming.NameNotFoundException: Unable to resolve 'jdbc.mds.owsm'. Resolved 'jdbc.mds'; remaining name 'owsm'
at oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl.inititializeDataSoureForNonMT(JNDIConnectionManagerImpl.java:416)
at oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl.initializeDataSources(JNDIConnectionManagerImpl.java:380)
at oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl.init(JNDIConnectionManagerImpl.java:211)
at oracle.mds.internal.persistence.db.ConnectionManagerFactory.createConnectionManager(ConnectionManagerFactory.java:72)
.
.
.
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.mds.owsm'. Resolved 'jdbc.mds'; remaining name 'owsm'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1292)
oracle.mds.persistence.MDSIOException: MDS-00929: unable to look up name "jdbc/mds/owsm" in JNDI context
javax.naming.NameNotFoundException: Unable to resolve 'jdbc.mds.owsm'. Resolved 'jdbc.mds'; remaining name 'owsm'
at oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl.inititializeDataSoureForNonMT(JNDIConnectionManagerImpl.java:416)
at oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl.initializeDataSources(JNDIConnectionManagerImpl.java:380)
at oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl.init(JNDIConnectionManagerImpl.java:211)
at oracle.mds.internal.persistence.db.ConnectionManagerFactory.createConnectionManager(ConnectionManagerFactory.java:72)
.
.
.
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.mds.owsm'. Resolved 'jdbc.mds'; remaining name 'owsm'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1292)
This causes a slow server startup, due to subsequent frequent WSM-02311 and WSM-02302 errors because OWSM has not been correctly deployed.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |