Running a migration a second time after rolling back from a successful upgrade fails with unhandled user-defined exception

Products

• Data Loss Prevention
• Data Loss Prevention Enforce
• Data Loss Prevention Discover Suite
• Data Loss Prevention Core Package
• Data Loss Prevention Enterprise Suite
• Data Loss Prevention Plus Suite

Issue/Introduction

After migrating the Enforce server to the latest version successfully, then for testing purposes after a roll back to the previous version and second migration attempt there is a failure with the following error in the Migrator log: 

SQLPlus standard output end
Apr 18, 2024 9:33:28 AM com.symantec.dlp.migrationcommon.MigrationActionsExecutor executeMigrationActions
SEVERE: Failed to execute migration actions. Please refer to the log file for details
com.symantec.dlp.migrationcommon.MigrationException: Failed to run migration action "DatabaseUpdate"
	at com.symantec.dlp.migrationcommon.MigrationActionsExecutor.runMigrationAction(MigrationActionsExecutor.java:72)
	at com.symantec.dlp.migrationcommon.MigrationActionsExecutor.executeMigrationActions(MigrationActionsExecutor.java:118)
	at com.symantec.dlp.migrationcommon.MigrationUtility.runMigrationUtility(MigrationUtility.java:183)
	at com.symantec.dlp.migrationcommon.MigrationUtility.runMigrationUtility(MigrationUtility.java:109)
	at com.symantec.dlp.migrationcommon.MigrationUtility.runMigrationUtility(MigrationUtility.java:119)
	at com.symantec.dlp.enforceservermigrationutility.EnforceServerMigrationUtility.runMigration(EnforceServerMigrationUtility.java:37)
Caused by: com.symantec.dlp.migrationcommon.MigrationException: java.lang.Exception: SQLPlus error: BEGIN
*
ERROR at line 1:
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "PROTECT.UPGRADER_CENTRAL", line 533
ORA-02291: integrity constraint (PROTECT.DATAIDENTIFIERPATTERN_FK1) violated -
parent key not found
ORA-06512: at "PROTECT.UPGRADER_CENTRAL", line 443
ORA-06512: at "PROTECT.UPGRADESCHEMA_DI_MIGRATION", line 1141
ORA-06512: at line 1063

Environment

16.x

Cause

A rollback is not expected when the result of the migration is successful, attempting another migration will fail because the installer files specifically the following were not replaced: 

D:\Program Files\Symantec\DataLossPrevention\EnforceServer\16.x\Protect\Migrator\sql\add_di_regex_pattern.sql
D:\Program Files\Symantec\DataLossPrevention\EnforceServer\16.x\Protect\Migrator\sql\update_di_prepost_valid_characters.sql

These files are modified during the migration so when a second migration is performed results in an unhandled user-defined exception.

Resolution

When performing a rollback on a successful upgrade, you must do the following:

1. Follow the steps in Reverting the Enforce Server to a Previous Release (16.1 - techdocs.broadcom.com)

2. Delete the Migrator folder content and then unzip a fresh Update_Readiness_Tool.zip file to that folder again, for detailed steps please see Preparing to Run the Update Readiness Tool (16.1 - techdocs.broadcom.com). before running the migration a second time. 

Windows: c:\Program Files\Symantec\DataLossPrevention\EnforceServer\16.x\Protect\Migrator\
Linux: /opt/Symantec/DataLossPrevention/EnforceServer/16.x/Protect/Migrator/