Update Readiness Tool ends with errors: Invalid Non-Primary Key Indexes

book

Article ID: 184652

calendar_today

Updated On:

Products

Data Loss Prevention Enforce

Issue/Introduction

During preparing customers DLP environment to the upgrade from DLP 15.0 to 15.5 MP1 URT ends with Index Definition Validation errors: Invalid Non-Primary Key Indexes.

Start: Index Definition Validation - 2019-07-19 11:26:35 
Invalid Non-Primary Key Indexes 
------------------------------ ------------------------------ 
Table Name Index Name 
------------------------------ ------------------------------ 
DATAUSER NLS_DU_FN_CZECH 
DATAUSER NLS_DU_LN_CZECH 
INCIDENTSTATUS NLS_IST_ISN_CZECH 
MESSAGE NLS_M_EFN_CZECH 
MESSAGE NLS_M_FO_CZECH 
MESSAGE NLS_M_MSB_CZECH 
MESSAGEORIGINATOR NLS_MO_EMN_CZECH 
MESSAGEORIGINATOR NLS_MO_EUN_CZECH 
MESSAGEORIGINATOR NLS_MO_NSI_CZECH 
POLICY NLS_P_PNM_CZECH 
SCANASSIGNMENT NLS_SA_SAN_CZECH 
End : Index Definition Validation - elapsed 33.98s - FAILED (11 errors) 

Cause

URT returns "Invalid Non-Primary Key Indexes" errors when it is launched on Enforce server with installed additional Language Pack.
Installation of Language Pack creates locale specific indexes in DB which are not included to URT script.

In exampled case issue was caused by installed Czech Language Pack.

Resolution

These errors does not affect upgrade process and can be completely ignored.

But running of migrator will fail due to these "Invalid Non-Primary Key Indexes" errors as URT script is included into the list of scripts in default configuration of migrator.

To exclude of URT script from default configuration:

  1. Navigate to the folder with unpacked migrator files ..\Protect\Migrator
  2. Open configuration file EnforceServerMigration.xml with for example Notepad++
  3. Comment line with ID="UpgradeReadinessTool" using '<!--' at the beginig and '-->' at the end of commented line and save changes.

Example:

<!--   <MigrationActionReference:ActionReference FilePath="EnforceMigration.xml" ID="UpgradeReadinessTool"/>  -->

After that migrator can be launched.