• Why You should attend Oracle OpenWorld
  • Data Guard Architecture
  • Understand Oracle Real Application Cluster
  • Understand the Power of Oracle RMAN - Page 47
  • Migrate Non-ASM Database to ASM Using RMAN
  • Modifying the VIP Address or VIP Hostname in RAC
  • Duplicate RAC Database Using RMAN
  • "OALL8 is in an inconsistent state" is a generic exception that occurs in JDBC 10.1, 10.2, and 11.1. It indicates that an internal inconsistency has been detected in the JDBC connection but it does not provide information on what caused the inconsistency.

    OALL8 is in an inconsistent state.
    java.sql.SQLException: OALL8 is in an inconsistent state.
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
    at oracle.jdbc.driver.T4C8Oall.init(T4C8Oall.java:325)
    at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:170)
    at oracle.jdbc.driver.T4CPreparedStatement.execute_for_describe(T4CPreparedStatement.java:503)
    at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:1029)
    at oracle.jdbc.driver.T4CPreparedStatement.execute_maybe_describe(T4CPreparedStatement.java:535)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1126)
    at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3001)
    at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3043)
    at oracle_jdbc_driver_T4CPreparedStatement_Proxy.executeQuery()
    at com.agile.pc.cmserver.util.ClusterLock.acquireClusterLock(ClusterLock.java:61)
    at com.agile.pc.cmserver.notification.NotifyTask.run(NotifyTask.java:413)
    at java.util.TimerThread.mainLoop(Timer.java:512)
    at java.util.TimerThread.run(Timer.java:462)
    <2013-02-27 22:59:37,734> <NotifyTask:ERROR> notification task exception


    You may also see a "Protocol Violation error, the thin driver throws this exception when it reads something from the RDBMS that it did not expect. This means that the protocol engine in the Thin driver and the protocol engine in the RDBMS are out of synch. There is no way to recover from this error. The connection is dead and You should try to close it, but that will probably fail too.

    If you are able to reproduce the error, please file a TAR with Oracle Global Support by specifying the exact version numbers of the JDBC driver and the RDBMS.

    Protocol violation
    java.sql.SQLException: Protocol violation
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:175)
    at oracle.jdbc.driver.DatabaseError.check_error(DatabaseError.java:898)
    at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:656)
    at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:185)
    at oracle.jdbc.driver.T4CPreparedStatement.execute_for_describe(T4CPreparedStatement.java:503)
    at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:1029)
    at oracle.jdbc.driver.T4CPreparedStatement.execute_maybe_describeT4CPreparedStatement.
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1126)
    at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3001)
    at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3043)
    at oracle_jdbc_driver_T4CPreparedStatement_Proxy.executeQuery()
    at com.agile.pc.cmserver.util.ClusterLock.acquireClusterLock(ClusterLock.java:61)
    at com.agile.pc.cmserver.notification.NotifyTask.run(NotifyTask.java:199)
    at java.util.TimerThread.mainLoop(Timer.java:512)
    at java.util.TimerThread.run(Timer.java:462)

    Possible Solution: It is very hard to troubleshoot and the simplest solution is to upgrade your JDBC Driver.

    This exception no longer occurs in JDBC 11.2.

    Other scenarios & Reference
    1. Oracle Transportation Management (OTM) - Version 5.5.04.02 to 5.5.06.03
    If you are facing the issue with OTM then check below metalink note for Cause and Solution
    java.sql.SQLException: OALL8 is in an inconsistent state [ID 754144.1]

    2. Master Note: Understanding the "OALL8 is in an Inconsistent State" Exception [ID 944692.1]
    Regards
    Satishbabu Gunukula, Oracle ACE
    http://www.oracleracexpert.com
    1. We are offering website service & website design Contact us.....

      Voip Telephone Systems

      Reply Delete
    Sunnyvale, California, United States
    Satishbabu Gunukula has over 24+ years of experience in various roles as Technical Lead, Project Lead, Project Manager, and Sr.Database Architect. He has experience on wide range of products such as Databases, Cloud , Data Analytics, Replication , EPM , PLM and Business Apps, software development lifecycle and Systems administration using various technologies. He has extensive experience in high availability Solutions various platforms. He has implemented many business critical systems for fortune 500, 1000 companies. He has done his Master degree in Computer Applications(MCA). He has published several articles and presentations, Technical review of Books with Packt publishing.

    Helful and want to say thanks?

    Oracle ACE Award