Resource Anonymize PII job does not rebuild indexes on failure leaving them in unusable state

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

If Anonymize (PII) job fails upon table update it does not re-enable the indexes back and leaves them in unusable state which prevents users from doing multiple actions in Clarity including project create and update

STEPS TO REPRODUCE:

1. In Clarity on Oracle database, run Resource Anonymize PII job for a single resource
2. Whilst the job is running make sure one of the tables 'PAC_MNT_PROJECTS','PAC_MNT_RESOURCES', 'PPA_WIP','CMN_AUDITS is locked for update to make it fail with an error ORA-00054 resource busy

Expected Results: The Anonymize Personally Identifiable Information (PII) job fails and the indexes that were disabled and set to unusable by COP_PII_ANONYMIZE_SP to be rebuilt and enabled

Actual Results: The Anonymize Personally Identifiable Information (PII) job fails and the indexes that were disabled and set to unusable by COP_PII_ANONYMIZE_SP are still in unusable state. Actions in Clarity UI, as example, creating/updating project fail with errors such as :  

Caused by: java.sql.SQLException: ORA-01502: index 'NIKU.PAC_MNT_PROJECTS_U1' or partition of such index is in unusable state

Environment

Clarity 16.1.x, 16.2.x

Cause

DE154962

Resolution

This is DE154962, in review by Engineering

Workaround: Engage DBA to manually rebuild the indexes (requires downtime), example syntax:

ALTER INDEX CLARITY.PPA_WIP_U1 REBUILD