UpdateReadinessTool fails with mutliple errors related to tables, indexes, foreign keys and constraints when upgrading from a Beta release of the DLP product
search cancel

UpdateReadinessTool fails with mutliple errors related to tables, indexes, foreign keys and constraints when upgrading from a Beta release of the DLP product

book

Article ID: 415338

calendar_today

Updated On:

Products

Data Loss Prevention Data Loss Prevention Enforce

Issue/Introduction

When planning an upgrade to a new DLP release it is obligatory to execute the UpdateReadinessTool (URT) to verify whether the database is ready for the process which allows to resolve any potential issues beforehand. However when running the URT when planning to upgrade from a Beta release of the product to the GA release (General Availability) you may run into errors in the Table Definition, Index Definition, Foreign Key, Miscellaneous Object, Check Constraint Validation steps of the tool. 

The validation errors should be similar to those below. 

Start: Table Definition Validation - 2025-10-21 11:16:48
    Missing Tables
    DISCOVERSCHEDULE
    LIVEUPDATETRIGGER
    LOGDIAGNOSTICCONFIG
    LOGDIAGNOSTICCONFIGFILE
    LOGDIAGNOSTICLOGGER
    LOGDIAGNOSTICPACKAGE
    ROLEINCIDENTSTATUSMAPPING
    SCHEDULE
    Missing Columns
    DEPLOYMENTAGENT.AGENTNAME
    DEPLOYMENTAGENT.LIVEUPDATETRIGGERID
    DEPLOYMENTAGENT.SCHEDULEDATE
    DEPLOYMENTAGENT.UPGRADESTATUS
    DEPLOYMENTAGENT.UPGRADESTATUSMESSAGE
    PROTECTUSER.ISAPIUSER
    Invalid Columns
    AGENTDEPLOYMENTGROUP.AGENTSCOMPLETEDUPGRADECOUNT
    AGENTDEPLOYMENTGROUP.AGENTSFAILEDUPGRADECOUNT
    AGENTDEPLOYMENTGROUP.AGENTSPENDINGUPGRADECOUNT
    AGENTDEPLOYMENTGROUP.AGENTUPGRADESTATUS
    AGENTDEPLOYMENTGROUP.LASTTARGETEDAGENTSCOUNT
    AGENTDEPLOYMENTGROUP.LASTTARGETEDUPGRADEVERSION
    AGENTDEPLOYMENTGROUP.UPGRADESTARTDATE
    AGENTDEPLOYMENTGROUP.UPGRADEENDDATE
    DEPLOYMENTAGENT.AGENTUPGRADEREPORTEDSTATUS
    DEPLOYMENTAGENT.AGENTDEPLOYMENTGROUPID
    DEPLOYMENTAGENT.UPGRADESTATUSEXTENDEDVALUE
End  : Table Definition Validation - elapsed 2.24s - FAILED (14 errors, 11 warnings)
Start: Index Definition Validation - 2025-10-21 11:16:51
    Missing Primary Key Indexes
    ------------------------------ ------------------------------
    Table Name               Index Name             
    ------------------------------ ------------------------------
    DISCOVERSCHEDULE           SYS_C00397185
    LIVEUPDATETRIGGER           SYS_C00556788
    LOGDIAGNOSTICCONFIG        SYS_C00298602
    LOGDIAGNOSTICCONFIGFILE       SYS_C00087265
    LOGDIAGNOSTICLOGGER        SYS_C00531927
    LOGDIAGNOSTICPACKAGE       SYS_C00950012
    ROLEINCIDENTSTATUSMAPPING       ROLEINCIDENTSTATUSMAPPING_PK
    SCHEDULE               SYS_C00839810
    Missing non-Primary Key Unique Indexes
    ------------------------------ ------------------------------
    Table Name               Index Name             
    ------------------------------ ------------------------------
    LOGDIAGNOSTICCONFIG        LOGDIAGNOSTICCONFIG_U1
    LOGDIAGNOSTICCONFIGFILE       LOGDIAGNOSTICCONFIGFILE_U1
    Missing Non-Unique Indexes
    ------------------------------ ------------------------------
    Table Name               Index Name             
    ------------------------------ ------------------------------
    DEPLOYMENTAGENT           DEPLOYMENTAGENT_AGENTNAME_IDX
    DEPLOYMENTAGENT           DEPLOYMENTAGENT_FK3
    DISCOVERSCHEDULE           SCANASSIGNMENT_DS_FK1
    DISCOVERSCHEDULE           SCHEDULE_FK1
    LIVEUPDATETRIGGER           LIVEUPDATETRIGGER_FK1
    LIVEUPDATETRIGGER           LIVEUPDATETRIGGER_FK2
    LOGDIAGNOSTICCONFIGFILE       LOGDIAGNOSTICCONFIGFILE_FK1
    LOGDIAGNOSTICLOGGER        LOGDIAGNOSTICLOGGER_FK1
    LOGDIAGNOSTICPACKAGE       LOGDIAGNOSTICPACKAGE_FK1
    ROLEINCIDENTSTATUSMAPPING       ROLEINCIDENTSTATUSMAPPING_FK1
    ROLEINCIDENTSTATUSMAPPING       ROLEINCIDENTSTATUSMAPPING_FK2
    Invalid Non-Unique Indexes
    ------------------------------ ------------------------------
    Table Name               Index Name             
    ------------------------------ ------------------------------
    DEPLOYMENTAGENT           DEPLOYMENTAGENT_FK1
    DEPLOYMENTAGENT           DEPLOYMENTAGENT_FK2
End  : Index Definition Validation - elapsed 22.83s - FAILED (10 errors, 13 warnings)
Start: Foreign Key Validation - 2025-10-21 11:17:13
    Missing Foreign Keys
    DEPLOYMENTAGENT_FK3: DEPLOYMENTAGENT(LIVEUPDATETRIGGERID) REFERENCES LIVEUPDATETRIGGER(LIVEUPDATETRIGGERID)
    LIVEUPDATETRIGGER_FK1: LIVEUPDATETRIGGER(LASTMODIFIEDBYID) REFERENCES PROTECTUSER(USERID)
    LIVEUPDATETRIGGER_FK2: LIVEUPDATETRIGGER(AGENTDEPLOYMENTGROUPID) REFERENCES AGENTDEPLOYMENTGROUP(AGENTDEPLOYMENTGROUPID)
    LOGDIAGNOSTICCONFIGFILE_FK1: LOGDIAGNOSTICCONFIGFILE(LOGDIAGNOSTICCONFIGID) REFERENCES LOGDIAGNOSTICCONFIG(LOGDIAGNOSTICCONFIGID)
    LOGDIAGNOSTICLOGGER_FK1: LOGDIAGNOSTICLOGGER(LOGDIAGNOSTICCONFIGFILEID) REFERENCES LOGDIAGNOSTICCONFIGFILE(LOGDIAGNOSTICCONFIGFILEID)
    LOGDIAGNOSTICPACKAGE_FK1: LOGDIAGNOSTICPACKAGE(LOGDIAGNOSTICCONFIGFILEID) REFERENCES LOGDIAGNOSTICCONFIGFILE(LOGDIAGNOSTICCONFIGFILEID)
    SCANASSIGNMENT_DS_FK1: DISCOVERSCHEDULE(SCANASSIGNMENTID) REFERENCES SCANASSIGNMENT(SCANASSIGNMENTID)
    SCHEDULE_FK1: DISCOVERSCHEDULE(SCHEDULEID) REFERENCES SCHEDULE(SCHEDULEID)
    ROLEINCIDENTSTATUSMAPPING_FK1: ROLEINCIDENTSTATUSMAPPING(ROLEID) REFERENCES ROLE(ROLEID)
    ROLEINCIDENTSTATUSMAPPING_FK2: ROLEINCIDENTSTATUSMAPPING(INCIDENTSTATUSID) REFERENCES INCIDENTSTATUS(INCIDENTSTATUSID)
End  : Foreign Key Validation - elapsed 2.61s - FAILED (10 errors, 0 warnings)
Start: Trigger Validation - 2025-10-21 11:17:16
End  : Trigger Validation - elapsed .11s - PASSED
Start: Miscellaneous Object Validation - 2025-10-21 11:17:16
    Missing objects
    Object Type     object Name
    ------------------- ----------------------------------------
    PROCEDURE        ADD_DIAGNOSTIC_LOG_CONFIG
    SEQUENCE        SEQ_DISCOVERSCHEDULE
    SEQUENCE        SEQ_LIVEUPDATETRIGGER
    SEQUENCE        SEQ_LOGDIAGNOSTICCONFIG
    SEQUENCE        SEQ_LOGDIAGNOSTICCONFIGFILE
    SEQUENCE        SEQ_LOGDIAGNOSTICLOGGER
    SEQUENCE        SEQ_LOGDIAGNOSTICPACKAGE
    SEQUENCE        SEQ_SCHEDULE
End  : Miscellaneous Object Validation - elapsed .03s - FAILED (8 errors, 0 warnings)
Start: Invalid Object Validation - 2025-10-21 11:17:16
End  : Invalid Object Validation - elapsed 2.34s - PASSED
Start: Tablespace Validation - 2025-10-21 11:17:19
End  : Tablespace Validation - elapsed .03s - PASSED
Start: Check Constraint Validation - 2025-10-21 11:17:19
    Mismatched or Missing Check Constraints
    Table Name                     Master Check Constraint Definition
    ---------------------------------------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    DATAIDENTIFIER                 IDENTIFIERTYPE IN ('SYSTEM','CUSTOM', 'MODIFIED', 'DANGLINGREF','INTERNAL')
    LOGDIAGNOSTICCONFIG              TARGETSERVER IN ('ENFORCE','MONITOR','ENFORCE_AND_MONITOR')
    LOGDIAGNOSTICLOGGER              LOGLEVEL IN ('TRACE','DEBUG','INFO','WARN','ERROR','FATAL')
    LOGDIAGNOSTICPACKAGE             LOGLEVEL IN ('FINEST','FINER','FINE','CONFIG','INFO','WARNING','SEVERE')
    PROTECTUSER                  ISAPIUSER IN (0,1)
End  : Check Constraint Validation - elapsed .19s - FAILED (5 errors)

Environment

25.1 Beta

Cause

The Beta update process is a special scenario and requires an additional parameter for the URT tool.

Resolution

In case of upgrading from a Beta to GA release execute the URT tool with the "--beta" parameter as described in the document below:

Running the Update Readiness Tool at the Command Line

 

--beta Use this parameter if you are running the URT on a system that currently has a beta version of Symantec Data Loss Prevention installed.
This parameter specifies that the URT is being run on a system with a beta version of the Symantec Data Loss Prevention schema. By default, the URT validates the schema against version 25.1. Because the beta version includes schema differences from the version 25.1 release, the URT requires this parameter to correctly identify and validate the beta schema.

 

For example:

"C:\Program Files\AdoptOpenJRE\<JRE version>\bin\java" UpdateReadinessTool --beta

Powered by Wolken Software