Product: TIBCO Spotfire®
Oracle error, "OALL8 is in an inconsistent state, DATABASE_ERROR" causing a communication error with the Spotfire database.
"OALL8 is in an inconsistent state" is a generic exception that occurs in the Oracle JDBC driver 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 the exact details on what caused the inconsistency. The exception no longer occurs in Oracle JDBC driver as of version 11.2.
Communication issues with the Spotfire database may result in failure to log in, failure to access the library, failure to perform an LDAP synchronization among other symptoms (all of which require a connection to the Spotfire database). For example, when trying to access the TIBCO Spotfire Web Player, you may see the following error:
An Internal Error has occurred. Failed to load group membership associations from database Error: An Internal Error has occurred. Failed to load group membership associations from database
All symptoms will be caused by the following errors as logged in the server.log file:
ERROR 2014-09-04T02:33:08,692+0100 [*LibraryChangeMonitor*] im.element.LibraryStorageChangeMonitor: Failed to check for changes to items of type 'spotfire.datasource' com.spotfire.ws.im.IMException: Failed to get elements of type spotfire.datasource ... Caused by: com.spotfire.ws.library.StorageException: java.sql.SQLException: OALL8 is in an inconsistent state, DATABASE_ERRORand:
ERROR 2014-09-04T02:05:08,696+0100 [*LibraryChangeMonitor*] im.element.LibraryStorageChangeMonitor: Failed to check for changes to items of type 'spotfire.datasource' com.spotfire.ws.im.IMException: Failed to get elements of type spotfire.datasource ... Caused by: com.spotfire.ws.library.StorageException: java.sql.SQLException: Protocol violation, DATABASE_ERROR
"OALL8 is in an inconsistent state" is a generic exception that occurs in the Oracle JDBC driver 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 the exact details on what caused the inconsistency. Upgrade the Oracle JDBC driver to version 11.2 or later. External: Oracle JDBC Driver download:
External: External forum discussion of this issue:
Comments
0 comments
Article is closed for comments.