resourcepool.ResourceDeadException: 0: Could not connect to 'oracle.jdbc.OracleDriver'. The returned message is: ORA-01017: invalid username/password; logon denied It is likely that the login or password is not valid. It is also possible that something else is invalid in the configuration or that the database is not available.

Oracle Community | Ramya PS | 3 years ago
  1. 0

    Web logic server changed to ADMIN mode

    Oracle Community | 3 years ago | Ramya PS
    resourcepool.ResourceDeadException: 0: Could not connect to 'oracle.jdbc.OracleDriver'. The returned message is: ORA-01017: invalid username/password; logon denied It is likely that the login or password is not valid. It is also possible that something else is invalid in the configuration or that the database is not available.
  2. 0

    Please help : Unable to Start the Weblogic Server..!!

    Oracle Community | 5 years ago | 851913
    resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could n ot create pool connection. The DBMS driver exception was: IO Error: The Network Adapter could not establish the connection
  3. 0

    BI presentation services login error

    Oracle Community | 4 years ago | 7688438
    resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could n ot create pool connection. The DBMS driver exception was: IO Error: The Network Adapter could not establish the connection
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Error while starting Weblogic Server in SOA Suite

    Oracle Community | 2 years ago | 973086
    resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could n ot create pool connection. The DBMS driver exception was: ORA-28001: the passwor d has expired

    Root Cause Analysis

    1. resourcepool.ResourceDeadException

      0: Could not connect to 'oracle.jdbc.OracleDriver'. The returned message is: ORA-01017: invalid username/password; logon denied It is likely that the login or password is not valid. It is also possible that something else is invalid in the configuration or that the database is not available.

      at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException()
    2. weblogic.jdbc.common
      RmiDataSource.getConnection
      1. weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:250)
      2. weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:352)
      3. weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:369)
      3 frames