|
This note is for Tibco Administrator version 5.6 connecting to an Oracle 10 (?) database.
One day I could not deploy anymore via AppManage and I could not log in into the Tibco Administrator browser frontend either. Upon the first deployment I found the following error message in the Tibco Administrator log file ($TIBCO_DIR/tra/domain/$TIBCO_DOMAIN_NAME/logs/Administrator.log):
2011 Jul 01 11:28:30:148 GMT +2 Error [Pool] AESDKJ-0000 [Thread-44] java.sql.SQLException: ORA-01502: index
'ADM.ADPRODUCT_PK' or partition of such index is in unusable state
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
....
2011 Jul 01 11:28:30:149 GMT +2 Error [DBEntityStore] AESDKJ-0000 [Thread-44] Getting attributes with SQL: SELECT *
FROM AdProduct WHERE mID='......'
I tried restarting Tibco Administrator. After restarting I tried to deploy again but I got more serious errors:
2011 Jul 04 07:43:31:635 GMT +2 Error [DBEntityStore] AESDKJ-0000 [http-8080-Processor24] [CREATE TABLE SQL}:
CREATE TABLE AdInputStreams(unique_id VARCHAR2(1500) NOT NULL PRIMARY KEY,Stream BLOB )
2011 Jul 04 07:43:31:637 GMT +2 Error [Pool] AESDKJ-0000 [http-8080-Processor24] java.sql.SQLException: ORA-00955:
name is already used by an existing object
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
....
When trying to log into the browser frontend in I got the following error message in the Tibco Administrator log file:
2011 Jul 04 08:32:59:242 GMT +2 Error [DBEntityStore] AESDKJ-0000 [main] [CREATE TABLE SQL}:CREATE TABLE
AdInputStreams(unique_id VARCHAR2(1500) NOT NULL PRIMARY KEY,Stream BLOB )
2011 Jul 04 08:32:59:245 GMT +2 Error [Pool] AESDKJ-0000 [main] java.sql.SQLException: ORA-00955: name is
already used by an existing object
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
....
So I emailed the database team. They replied that the problems started after they had moved the indexes to another tablespace. Something had gone wrong in compiling the indexes which caused the error messages. After recompiling Tibco Administrator ran OK.
|