Cannot start components after upgrade from 14.3 to 14.4
search cancel

Cannot start components after upgrade from 14.3 to 14.4


Article ID: 263353


Updated On:


CA Identity Suite


Client performing Vaap upgrade from 14.3 to 14.4 and components are not starting. This is a machine with all components together


Caused by: Error : 904, Position : 41, Sql = ALTER TABLE QRTZ_JOB_DETAILS DROP COLUMN IS_VOLATILE, OriginalSql = ALTER TABLE QRTZ_JOB_DETAILS DROP COLUMN IS_VOLATILE, Error Msg = ORA-00904: "IS_VOLATILE": invalid identifier

        at oracle.jdbc.driver.T4CTTIoer11.processError(
        ... 44 more

2023-01-31 16:48:29,684 INFO  [ims.Main] (ServerService Thread Pool -- 107) ---- CA IAM Server shutdown Initiated. ----
2023-01-31 16:48:29,694 WARN  [] (ServerService Thread Pool -- 107) Attempting to shutdown long running events if any.
2023-01-31 16:48:29,786 ERROR [] (ServerService Thread Pool -- 107) MSC000001: Failed to start service jboss.deployment.subunit."iam_im.ear"."user_console.war".undertow-deployment: org.jboss.msc.service.StartException in service jboss.deployment.subunit."iam_im.ear"."user_console.war".undertow-deployment: java.lang.ExceptionInInitializerError



Release : 14.4


During the configuration of the Oracle databases in the Vaap console it was pointed to coincident oracle users/schemas where it should have different users. IM/IG's Workpoint Database was conflicting with IP's Workpoint Database for example.


Reviewed the problematic environment where the IG is not starting.

Working on SQL developer to connect to DB Schemas  noticed on Pre-Production where the problem exists and compared with Development where works fine. Please notice the presence of QRTZ_ tables in working side and the tables are missing in not working side.

Also we noticed that having eurekify db and reportdb pointing to Oracle schema sdb. It's recommended to have each one a separated Oracle user schema.