This article describes the steps necessary to resolve the "ORA-00001: unique constraint (SYS.SQLLOG$_PKEY) violated" error in TIBCO Administator.
Environment: ===========
Oracle Database Oracle 11.2.0.1
Symptoms: ========
Administrator.log contains the following error message:
2011 Dec 27 21:49:10:760 GMT +0 Error [Pool] AESDKJ-0000 [Thread-13] java.sql.SQLException: [tibcosoftwareinc][Oracle JDBC Driver][Oracle]ORA-00001: unique constraint (SYS.SQLLOG$_PKEY) violated at tibcosoftwareinc.jdbc.base.BaseExceptions.createException(Unknown Source) at tibcosoftwareinc.jdbc.base.BaseExceptions.getException(Unknown Source) at tibcosoftwareinc.jdbc.oracle.OracleImplStatement.execute(Unknown Source) at tibcosoftwareinc.jdbc.base.BaseStatement.commonExecute(Unknown Source) at tibcosoftwareinc.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source) at tibcosoftwareinc.jdbc.base.BaseStatement.executeQuery(Unknown Source) at com.tibco.pof.entitystore.db.DBEntityResultSet.<init>(DBEntityResultSet.java:50) at com.tibco.pof.entitystore.db.DBEntityStore.a(DBEntityStore.java:934) at com.tibco.pof.entitystore.db.DBEntityStore.getEntityInputStreamHelper(DBEntityStore.java:1220) at com.tibco.pof.entitystore.db.DBEntityStore.getEntityInputStreamByID(DBEntityStore.java:1190) at com.tibco.pof.entitystore.AbstractEntityStore.getEntityInputStreamByURI(AbstractEntityStore.java:1038) at com.tibco.pof.notification.impl.EntityNotificationImpl.getEntity(EntityNotificationImpl.java:117) at com.tibco.pof.entity.impl.AbstractEntityCache.setCachedEntityByURI(AbstractEntityCache.java:210) at com.tibco.pof.entity.impl.AbstractEntityCache.a(AbstractEntityCache.java:497) at com.tibco.pof.entity.impl.AbstractEntityCache.onTransactionNotification(AbstractEntityCache.java:444) at com.tibco.pof.entitystore.AbstractEntityStore$UpdateCachesHandler.walk(AbstractEntityStore.java:231) at com.tibco.pof.entitystore.AbstractEntityStore.walkNotifiableCaches(AbstractEntityStore.java:265) at com.tibco.pof.entitystore.AbstractEntityStore.walkNotifiableCaches(AbstractEntityStore.java:272) at com.tibco.pof.entitystore.AbstractEntityStore.callCaches(AbstractEntityStore.java:122) at com.tibco.pof.entitystore.AtomicTransactionNotifierImpl.onTransactionNotification(AtomicTransactionNotifierImpl.java:46) at com.tibco.pof.entitystore.rvtransactionnotifier.RVTransactionNotifier.onMsg(RVTransactionNotifier.java:261) at com.tibco.tibrv.TibrvEvent.invoke(TibrvEvent.java:160) at com.tibco.tibrv.TibrvImplQueueC.natDispatch(Native Method) at com.tibco.tibrv.TibrvImplQueueC.dispatch(TibrvImplQueueC.java:44) at com.tibco.tibrv.TibrvQueue.dispatch(TibrvQueue.java:301) at com.tibco.pof.entitystore.rvtransactionnotifier.RVTransactionNotifier.run(RVTransactionNotifier.java:187) at java.lang.Thread.run(Thread.java:595) 2011 Dec 27 21:49:10:761 GMT +0 Error [DBEntityStore] AESDKJ-0000 [Thread-13] Getting attributes with SQL: SELECT * FROM AdFileContent WHERE mID='-2b598925_134817f63bf_-7ffc0a4a3954'
Cause: =====
This issue happens due to the following Oracle defect:
************************************************************************ 9900025 ORA-1 on (SYS.SQLLOG$_PKEY) from SPM automatic plan capture ************************************************************************
Resolution: ==========
1). Apply Oracle 11.2.0.3 patch set to the database server used by TIBCO Administrator.