Unable to resolve 'jdbc.OPSSDBDS'. Resolved 'jdbc'; remaining name 'OPSSDBDS' (Doc ID 2262711.1)

Last updated on JANUARY 15, 2020

Applies to:

Symptoms

While trying to access the OIM console, getting a 404 error.
The OIM log shows error:

[2017-05-03T00:10:01.261-04:00] [<SERVERNAME>] [WARNING] [JPS-04155] [oracle.jps.authorization] [tid: Policy change scanner] [userId: <WLS Kernel>] [ecid: <ECID>] [APP: wsm-pm] Scanning of application policy failed. Reason {0}[[
oracle.security.jps.service.policystore.PolicyStoreException: JPS-10702: The datasource jdbc/OPSSDBDS is not found.
    at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.getDataSourceAndSubject(JpsDBDataManager.java:1463)
    at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.getEMFAndSubject(JpsDBDataManager.java:1173)
    at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.init(JpsDBDataManager.java:951)
    at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.getApplicationNames(JpsDBDataManager.java:6428)
................
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.OPSSDBDS'. Resolved 'jdbc'; remaining name 'OPSSDBDS'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1148)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:258)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
................

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.