Clarity

Hello All,

I'm upgrading my UAT site from 13.2 to 14.3 and is happing the following error during the execute of CLEANUP_CLARITY_FOR_DWH.xml script.

The upgrade stopped after that error.

The error started at line 52996 of install.log attached.

Please, could someone help me ?

Thanks.

Error:

2/23/16 5:49 PM (ExecTask) Process - post-upgrade: CLEANUP_CLARITY_FOR_DWH.xml

2/23/16 5:50 PM (ExecTask) com.ca.clarity.jdbc.oraclebase.ddc: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-00001: unique constraint (NIKU.CMN_AUDITS_PK) violated

2/23/16 5:50 PM (ExecTask) ORA-06512: at "NIKU.T_TASK_PPRTASK", line 265

2/23/16 5:50 PM (ExecTask) ORA-04088: error during execution of trigger 'NIKU.T_TASK_PPRTASK'

2/23/16 5:50 PM (ExecTask) ORA-06512: at line 4

2/23/16 5:50 PM (ExecTask)

Hi Maurico,

The error you mentioned is second, i looked at the install log and the first error reported was

2/23/16 3:15 PM (ExecTask) Executing Ant script: /clarity/clarity/upgrade/13.3.0/infrastructure/postupgrade/osf.xml

2/23/16 3:16 PM (ExecTask) com.niku.union.persistence.PersistenceException: Invalid trigger

So roll back to 13.2, run the dbcompile to ensure all the database objects are in compiled stated.

The triggers which are invalid are the audit trggers, so you would want to disable the audit trail before the upgrade. We discussed the same in this thread 14.2 Upgrade Error.

Let me know how it goes.

Regards

Suman Pramanik

Hello Surma,

I did the rollback to 13.2, I verified all database objects were compiled, but It happened the same error.

Thanks.

HI Maurico,

You pre check results says you have possible schema customization and check install files are updated, can you remove the customization in database objects and disable the audit as I mentioned the other thread 14.2 Upgrade Error.

And then run the upgrade

Regards

Suman Pramanik

Possible schema customization(s) have been found. Any customization to the system is the responsibility of the customer to maintain and are not supported by CA Technologies. To upgrade successfully, all customizations must be reviewed, changed or removed as needed before the upgrade. After a successful upgrade the customizations may be added back to the system. The possible customizations found are listed in file check-logs/database_customization_indexes.txt, check-logs/database_customization_tables.txt and check-logs/database_customization_constraints.txt. Customizations of any type are not supported by CA Technologies.

Hello Suma,

I found the problem, I did one import data dump from PRD to HML.

But the sequences stayed with lower value than audit table, for example. I fix it and the installation worked fine.

Thanks for you help.

Great, yes during back up this is the most common issue i have seen. Glad to hear but please remove any schema customization before any upgrade