Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by SubinCheruvath, 1 year ago
Unable to resolve 'AuditDB'. Resolved '' ; remaining name 'AuditDB'
javax.naming.NameNotFoundException: Unable to resolve 'AuditDB'. Resolved ''; remaining name 'AuditDB' at oracle.security.audit.ajl.loader.OracleRepository.<init>(OracleRepository.java:84) at oracle.security.audit.ajl.loader.JDBCLogWriter.reinit(JDBCLogWriter.java:59) at oracle.security.audit.ajl.loader.JDBCLogWriter.write(JDBCLogWriter.java:104) at oracle.security.audit.ajl.loader.AuditLoader.readMessages(AuditLoader.java:488) at oracle.security.audit.service.AuditLoaderManager.readMessages(AuditLoaderManager.java:209) at oracle.security.audit.service.AuditLoaderManager$Runner.run(AuditLoaderManager.java:284)Caused by: javax.naming.NameNotFoundException: Unable to resolve 'AuditDB'. Resolved ''; remaining name 'AuditDB' at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139) at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252) at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182) at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206) at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254) at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412) at javax.naming.InitialContext.lookup(InitialContext.java:392) at oracle.security.audit.ajl.loader.OracleRepository.<init>(OracleRepository.java:74) ... 5 more