Products | Versions |
---|---|
TIBCO Administrator | - |
Not Applicable | - |
Description:
While saving Global Variable changes or deploying an application through the TIBCO Administrator, the following exception is thrown.
*****************************************
ORA-00942: table or view does not exist.
*****************************************
Symptoms:
========
After saving the Global Variable changes or after deploying a new or existing application through the TIBCO Administrator the following error is displayed by TIBCO Administrator and also in the Administrator.log file.
******************************************************************************************************
Caused by: java.sql.SQLException: ORA-00942: table or view does not exist
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:111)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:330)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:287)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:744)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:206)
at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:800)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1038)
at oracle.jdbc.driver.T4CStatement.executeMaybeDescribe(T4CStatement.java:840)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1133)
at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1273)
at com.tibco.pof.entitystore.db.UriQueryEntityIterator.(UriQueryEntityIterator.java:33)
... 22 more
*********************************************************************************************************
Cause:
=====
1). The required table may be absent in the domain's Database. Follow the steps in Resolution 1 to resolve this issue.
2). This is a rare scenario in which the table was actually present but the above error was still being thrown by Administrator. It could also be caused due to an ORACLE server "Bug 9577583 - False ORA-942 or other errors when multiple schemas have identical object names". Follow the steps in Resolution 2 to resolve this issue.