TIBCO Spotfire Server will not start due to 'Database consistency verification failed' error message about ROUTING_RULES_UC2 in Catalina.log

TIBCO Spotfire Server will not start due to 'Database consistency verification failed' error message about ROUTING_RULES_UC2 in Catalina.log

Upgrading from TIBCO Spotfire Server 7.14 or lower to TIBCO Spotfire Server 10.0 or higher might show the following error in catalina.log. As a result the TIBCO Spotfire Server would not start up:

22-Feb-2020 10:10:35.819 SEVERE [main] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class [com.spotfire.server.lifecycle.SpotfireServerInitializer]     org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'lifecycleManager' defined in class path resource [applicationContext.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.spotfire.server.LifecycleManager]: Constructor threw exception; nested exception is com.spotfire.server.ServerInitializationException: TIBCO Spotfire Server will not be started. Database consistency verification failed. Errors found: Unexpected index for table ROUTING_RULES: OracleDatabaseIndex[   name: ROUTING_RULES_UC2   uniqueness: UNIQUE   Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.spotfire.server.LifecycleManager]: Constructor threw exception; nested exception is com.spotfire.server.ServerInitializationException: TIBCO Spotfire Server will not be started. Database consistency verification failed. Errors found: Unexpected index for table ROUTING_RULES: OracleDatabaseIndex[   name: ROUTING_RULES_UC2   uniqueness: UNIQUE In TIBCO Spotfire 10.0 and higher versions, the index "ROUTING_RULES_UC2"  has been removed from the database. If this error is seen, it means that this constraint still exists in the upgraded database. To resolve, ensure the database has been upgraded correctly per the instructions in Upgrading Spotfire (Example provided for version 10.3. Use the documentation for your version). If the database has already been upgraded, then have the database administrator manually drop this index from the database so the database consistency check succeeds.

Note: Before making any changes to the database, take a backup of the current database.

Another scenario where this may be see is if the database user has access to another Spotfire database too. See KB 000033135 TIBCO Spotfire Server does not start with "Unexpected constraint for table GROUP_MEMBERS" error for more details. Doc: Upgrading Spotfire

• https://docs.tibco.com/pub/spotfire_server/10.3.8/doc/html/TIB_sfire_server_tsas_admin_help/GUID-7C929C7D-3809-4FA4-855E-9487AE91BA1C.html

KB: 000033135 TIBCO Spotfire Server does not start with "Unexpected constraint for table GROUP_MEMBERS" error

• https://support.tibco.com/s/article/TIBCO-Spotfire-Server-does-not-start-with-Unexpected-constraint-for-table-GROUP-MEMBERS-error