Anonymize Personally Identifiable Information (PII) job failure

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

When a resource to be anonymized is part of MUX conversations the Anonymize Personally Identifiable Information (PII) job fails with the following error:

Couldn't execute SQL: EXEC COP_PII_ANONYMIZE_SP 0,0,'1','0',362

The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.

bg-dwh.log file shows the following:
ERROR 2024-02-14 13:33:28,337 [Dispatch 14 02 2024 Anonymize Personally Identifiable Information (PII) : bg@myserver (tenant=clarity)] dwh.event (clarity:admin:19834338__79C26DE8-E7B6-42AA-8F9A-30321034FD66:14 02 2024 Anonymize Personally Identifiable Information (PII)) ETL Job Failed. Log details below: 
2024/02/14 13:33:28 - PPM Tables (M) - ERROR (version 9.1.0.0-324, build 9.1.0.0-324 from 2020-09-07 05.09.05 by buildguy) : An error occurred executing this job entry : 
2024/02/14 13:33:28 - PPM Tables (M) - Couldn't execute SQL: EXEC COP_PII_ANONYMIZE_SP 0,0,'1','0',362
2024/02/14 13:33:28 - PPM Tables (M) - 
2024/02/14 13:33:28 - PPM Tables (M) - The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
null

Environment

Clarity 16.0.X, 16.1.X

Cause

This is caused by DE78310

Resolution

This is fixed in 16.2.0

For prior releases, please use the attached SP