Weblogic 12.2.1.3.0 Developer - 无法使用管理控制台创建数据源

Question

I have been trying to create a DataSource on my development machine using Weblogic 12.2.1.3.0 developer install using the admin console and I am getting an exception that I have not encountered before. I have verified that all of the connection information is correct and I can connect to the Oracle Database (v12.1.2) using SQL Developer and an IDE connection but the Weblogic server is not cooperating. This is the exception that I am getting:

I have also tried creating a DataSource when the EAR file is deployed using descriptors and the DS is created and deployed but the connection pool for the DS cannot be created and the only exception that I am seeing is this:

Connection test failed with the following exception: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection for datasource 'StipDS'. The DBMS driver exception was: null

Anyone have any ideas? Oracle has not been much help at all so far.

Answer 1

check your jdbc connection url, i guess something is missing there. make sure the jdbc driver is present inside lib folder.

Answer 2

I was facing the same issue and able to resolve by replacing the ojdbc6.jar with ojdbc6-2.0.jar from "C:\\Oracle\\Middleware\\wlserver_10.3\\server\\lib"

Downloaded the jar file from https://jar-download.com/?search_box=ojdbc6++jar

Error log:

Caused By: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: null
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:283)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1310)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1227)
    at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:250)
    at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1329)

Answer 3

i suggest reverting any network changes that might have taken place. example DNS change in the resolve.conf file