Hello there,
We have just upgrade Appian from 20.2 to 21.2 in Linux, standalone server.
Apparently the upgrade was going well but when we started Tomcat we saw the following error:
2021-07-22 10:06:56,796 [localhost-startStop-1] ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (BMCOMS.USR_USERNAME_UC) violated
2021-07-22 10:06:56,820 [localhost-startStop-1] ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (BMCOMS.USR_USERNAME_UC) violated
2021-07-22 10:06:56,829 [localhost-startStop-1] ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (BMCOMS.USR_USERNAME_UC) violated
2021-07-22 10:06:56,964 [localhost-startStop-1] ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (BMCOMS.USR_USERNAME_UC) violated
2021-07-22 10:06:56,992 [localhost-startStop-1] INFO com.appiancorp.process.engine.MigrateUserWithoutUuidRequest - Determining usernames without UUIDs (ad hoc users)2021-07-22 10:06:56,999 [localhost-startStop-1] INFO com.appiancorp.process.engine.MigrateUserWithoutUuidRequest - execution has ad hoc username: 2021-07-22 10:06:56,999 [localhost-startStop-1] INFO com.appiancorp.process.engine.MigrateUserWithoutUuidRequest - execution has 1 ad hoc usernames, to be created in a deactivated state in Personalization engine.2021-07-22 10:06:57,015 [localhost-startStop-1] INFO com.appiancorp.process.engine.MigrateUserWithoutUuidRequest - Determined there were 1 total usernames without UUIDs (ad hoc usernames), will recreate these users in deactivated state with UUIDs.2021-07-22 10:06:57,097 [localhost-startStop-1] ERROR org.hibernate.util.JDBCExceptionReporter - ORA-01400: cannot insert NULL into ("BMCOMS"."USR"."USERNAME")
2021-07-22 10:06:56,992 [localhost-startStop-1] INFO com.appiancorp.process.engine.MigrateUserWithoutUuidRequest - Determining usernames without UUIDs (ad hoc users)
2021-07-22 10:06:56,999 [localhost-startStop-1] INFO com.appiancorp.process.engine.MigrateUserWithoutUuidRequest - execution has ad hoc username:
2021-07-22 10:06:56,999 [localhost-startStop-1] INFO com.appiancorp.process.engine.MigrateUserWithoutUuidRequest - execution has 1 ad hoc usernames, to be created in a deactivated state in Personalization engine.
2021-07-22 10:06:57,015 [localhost-startStop-1] INFO com.appiancorp.process.engine.MigrateUserWithoutUuidRequest - Determined there were 1 total usernames without UUIDs (ad hoc usernames), will recreate these users in deactivated state with UUIDs.
2021-07-22 10:06:57,097 [localhost-startStop-1] ERROR org.hibernate.util.JDBCExceptionReporter - ORA-01400: cannot insert NULL into ("BMCOMS"."USR"."USERNAME")
2021-07-22 10:06:57,099 [localhost-startStop-1] ERROR org.hibernate.util.JDBCExceptionReporter - ORA-01400: cannot insert NULL into ("BMCOMS"."USR"."USERNAME")
2021-07-22 10:06:57,101 [localhost-startStop-1] FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: A fatal error occurred when importing system packages: Could not import system package successfully. Will retry upon restart: /apps/appian/deployment/web.war/WEB-INF/bundled-apps/system.zipcom.appiancorp.suiteapi.common.exceptions.AppianException: A fatal error occurred when importing system packages: Could not import system package successfully. Will retry upon restart: /apps/appian/deployment/web.war/WEB-INF/bundled-apps/system.zip (APNX-1-4262-001) at com.appiancorp.suiteapi.common.exceptions.AppianRuntimeException.<init>(AppianRuntimeException.java:45) at com.appiancorp.common.config.FatalConfigurationException.<init>(FatalConfigurationException.java:23)
2021-07-22 10:06:57,101 [localhost-startStop-1] FATAL com.appiancorp.common.web.StartupHaltingServletContextListener - Halting JVM startup: A fatal error occurred when importing system packages: Could not import system package successfully. Will retry upon restart: /apps/appian/deployment/web.war/WEB-INF/bundled-apps/system.zip
com.appiancorp.suiteapi.common.exceptions.AppianException: A fatal error occurred when importing system packages: Could not import system package successfully. Will retry upon restart: /apps/appian/deployment/web.war/WEB-INF/bundled-apps/system.zip (APNX-1-4262-001)
at com.appiancorp.suiteapi.common.exceptions.AppianRuntimeException.<init>(AppianRuntimeException.java:45)
at com.appiancorp.common.config.FatalConfigurationException.<init>(FatalConfigurationException.java:23)
It looks like there is a problem with a table of users in Oracle in the primary schema, possibly a problem with a user with a null value that was allowed in Appian 20.2 but not in Appian 21.2
I guess the only way is to raise a ticket with Appian but we would appreciate if it is a known problem that can be easily fixed.
Thanks a lot!
Discussion posts and replies are publicly visible
Since the primary schema is directly used by the base product. As you already mentioned, the best and the safest course of action is to get support from Appian via support case.
Thanks Raghuvaran, Appian has recognized this as a bug in the product and it has been solved in the latest hotfix of Appian 21.2
We have experiencing this exact same issue, we've installed the latest hotfix 21.2.595.0. We are in the progress of migrating our DEV and TEST environment.
The only way we got Tomcat to start was to disable / re-enable the DB Null constraint before/after startup, however this resulted in multiple blank user records created in the DB. We will need a proper fix to this to progress any further with our version upgrade from 20.2 to 21.2.
We solved it by restarting Tomcat multiple times, as suggested by Appian Support. They recognized it as a problem in Appian and they mentioned they were going to implement a fix for it.
I've raised a support case since.
We rebuilt the migration environment with new installs and attempted to start Tomcat, with exact snapshot of our current Dev / Test environment on 20.2, Tomcat continued to fail startup with the same result (retried 5 times). Our current workaround is to disable the USR username null constraint during startup, and once tomcat is up, we re-enable the constraints, then remove the null username records that Tomcat repeatedly inserted into the USR table. This method just allows us to have the DEV / TEST environment up and running so we can perform application testing on 21.2, we won't be able to do this for our Production migration from 20.2 to 21.2 in 3 weeks time. Hopefully support will be able to identify the issue and have a fix ready in time.
2021-10-28 02:50:22,744 [Appian Work Item - 1838 - groups : CreateUserRequest] ERROR org.hibernate.util.JDBCExceptionReporter - ORA-01400: cannot insert NULL into ("TEST_APPIAN"."USR"."USERNAME")