Clarity Upgrade fails at .../postupgrade/osf.xml (Invalid Trigger)

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

While upgrading Clarity, it fails:

install.log file shows the following:
2/15/22 10:48 AM (ExecTask) Upgrade audit triggers.
2/15/22 10:48 AM (ExecTask) Starting upgrade AuditTriggers
2/15/22 10:48 AM (ExecTask) log4j:WARN No such property [maxFileSize] in org.apache.log4j.net.SyslogAppender.
2/15/22 10:48 AM (ExecTask) log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.net.SyslogAppender.
2/15/22 10:48 AM (ExecTask) log4j:WARN No such property [append] in org.apache.log4j.net.SyslogAppender.
2/15/22 10:48 AM (ExecTask) processing object: project
2/15/22 10:48 AM (ExecTask) com.niku.dbtools.ant.ExecutableException: /app/clarity/upgrade/16.0.0/component/postupgrade/osf.xml:32: Java returned: 1

And prior to the specific error, the key of the failure:

2/15/22 10:45 AM (ExecTask) Command: compile
2/15/22 10:45 AM (ExecTask) Compiling the database....
2/15/22 10:45 AM (ExecTask)  Following object(s) are invalid:
2/15/22 10:45 AM (ExecTask)   DWH_LKP_Z_TEST_V
2/15/22 10:45 AM (ExecTask)   ODF_AUD_5001860_FCT

Cause

Invalid objects/views and audit-related functions are causing the upgrade failure

Resolution

Ensure auditing is disabled prior to the upgrade:
Disable auditing prior to upgrade

Ensure there is no invalid objects/views on the DB prior to the upgrade
Drop any Auditing related invalid function