TDM Portal - Masking Service war file cannot load properly
search cancel

TDM Portal - Masking Service war file cannot load properly


Article ID: 241208


Updated On:


CA Test Data Manager (Data Finder / Grid Tools)


We just patch our TDM Portal server from version 4.10.12 to 4.10.17, but now the Masking Service won't start properly because the Masking Service WAR file cannot be loaded properly.


Release : 4.10

Component : Web Portal - Data Masking


The issue is due to a defect that was introduced in TDMWeb- This release of TDM Portal has been pulled, to help limit the exposure to this introduced defect.

The problem occurs because TDMWeb- updated the wrong table in the gtrep database. When TDMWeb- runs the migration process the schema_version table is updated with V4.10.0.03, however, this update should have been made to the schema_version_masking table. 

So when running an upgrade from to a newer release, the migration process causes the Masking Service to throw the following error:

Application run failed org.flywaydb.core.api.FlywayException: Validate failed: Detected failed migration to version (add mask sample value col fix audit)

To resolve this,

  1. Connect to the gtrep database with the utility of your choice.
  2. Check the schema_version table and the schema_version_masking table.
  3. Insert the line containing V4.10.0.03 from the schema_version table into the schema_versionMasking table:
    • INSERT INTO gterp.schema_version_masking
      SELECT * FROM gtrep.schema_version
      WHERE installed_rank =26;
  4. Change the installed_rank to be the next number in the sequence for the schema_version_masking table
  5. Modify the success column from 0 to 1
  6. Remove the line containing V4.10.0.03 from the schema_version table:
    • DELETE FROM gtrep.schema_version
      WHERE installed_rank=26;
  7. Stop the TDM Portal service
  8. Clear the Portal logs
  9. Restart the Portal service

If you are running TDM and need to upgrade, please take the following steps:

  1. Stop the Portal services 
  2. Backup the TDM Portal files and gtrep database
  3. Clear the Portal logs
  4. Modify the schema_version table and remove the line containing the entry added by TDM
  5. Upgrade Portal to the latest release
  6. Restart the services, and allow the migration to fail
  7. Stop the Portal service, clear the portal logs
  8. Modify the schema_version_masking table - success column, and change the 0 value to 1
  9. Restart the Portal service.