java.sql.SQLException: ORA-02396: exceeded maximum idle time, please connect again

Super User | Andrey Dmitriev | 3 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    [Sqoop-dev] [jira] [Created] (SQOOP-1329) JDBC connection to Oracle timeout after data import but before hive metadata import - Grokbase

    grokbase.com | 2 years ago
    java.sql.SQLException: ORA-02396: exceeded maximum idle time, please connect again
  2. 0

    Sqoop JDBC connection timeout after import but before hive import

    Super User | 3 years ago | Andrey Dmitriev
    java.sql.SQLException: ORA-02396: exceeded maximum idle time, please connect again
  3. 0

    Sqoop JDBC connection timeout after import but before hive import

    Stack Overflow | 3 years ago | Andrey Dmitriev
    java.sql.SQLException: ORA-02396: exceeded maximum idle time, please connect again
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Persistance, clés composées et clés étrangères

    developpez.net | 1 year ago
    java.sql.SQLException: ORA-00957: nom de colonne en double Error Code: 957
  6. 0

    How to resolve the StaleConnectionException in WebSphere Application Server? - dWAnswers

    ibm.com | 8 months ago
    java.sql.SQLException: ORA-02396: exceeded maximum idle time, please connect again DSRA0010E: SQL State = 61000, Error Code = 2,396

    4 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.sql.SQLException

      ORA-02396: exceeded maximum idle time, please connect again

      at oracle.jdbc.driver.T4CTTIoer.processError()
    2. Oracle jdbc
      T4CTTIoer.processError
      1. oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
      2. oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)
      2 frames