Upgrading from 3.6.1 to 3.6.2.5 can fail on the form_permission table

Upgrading from 3.6.1 to 3.6.2.5 the schema upgrade of igops failed with the following errors:


MS SQL:
liquibase: IacOpsChangeLog.xml: IacOpsTables362.xml::4200::SYSTEM: Change Set IacOpsTables362.xml::4200::SYSTEM failed. Error: ALTER TABLE only allows columns to be added that can contain nulls, or have a DEFAULT definition specified, or the column being added is an identity or timestamp column, or alternatively if none of the previous conditions are satisfied the table must be empty to allow addition of this column. Column 'FORM_SET_ID' cannot be added to non-empty table 'FORM_PERMISSION' because it does not satisfy these conditions. [Failed SQL: ALTER TABLE [FORM_PERMISSION] ADD [FORM_SET_ID] NVARCHAR(255) NOT NULL]

PostgreSQL:
Unexpected error running Liquibase: ERROR: column "form_set_id" contains null values [Failed SQL: ALTER TABLE public.FORM_PERMISSION ADD FORM_SET_ID VARCHAR(255) NOT NULL]

SEVERE liquibase: IacOpsTables362.xml::4200::SYSTEM: ERROR: column "form_set_id" contains null values [Failed SQL: ALTER TABLE public.FORM_PERMISSION ADD FORM_SET_ID VARCHAR(255) NOT NULL]
liquibase.exception.MigrationFailedException: Migration failed for change set IacOpsTables362.xml::4200::SYSTEM:
Reason: liquibase.exception.DatabaseException: ERROR: column "form_set_id" contains null values [Failed SQL: ALTER TABLE public.FORM_PERMISSION ADD FORM_SET_ID VARCHAR(255) NOT NULL]

With 3.6.2, the definition of the form_permission and form_application tables were changed, and the upgrade process is not handling the case of upgrading from 3.6.1 to 3.6.x correctly with these two (2) tables.

The work-around is to truncate these two (2) tables before upgrading.  Or if the problem is seen during the install, then truncate the two (2) tables and then run db-init from the idgov/bin directory.

Defect# 357171 Upgrading from 3.6.1 to 3.6.2.5 can fail on the form_permission table
This defect will be fixed in a future release.