Clarity: During an upgrade, the database installation fails while applying processes/proj_man_appr.xml

Document ID : KB000022817
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Error 'could not insert a NULL value into BPM_DEF_ASSIGNEES.PRINCIPAL_ID' when XOgging Clarity Content Add-ins (just the processes) if your default language is set to something other than English

During a Clarity upgrade, when trying to upgrade the database schema from NSA, the installation fails.

The following error sequence can be found on the admin.log:

M/DD/YY HH:mm XX (admin) Error occurred: com.niku.nsa.service.ExecutableException: Content Pack Installation - XOG Install failed Failure occurred while applying processes/proj_man_appr.xml
M/DD/YY HH:mm XX (admin) Check C:\Clarity\META-INF\content\xog\clarityContent\processes/proj_man_appr_out.xml for errors

And the following error can be found in the proj_man_appr_out.xml file mentioned above:

   <ErrorInformation>   
     <Severity>FATAL</Severity>   
     <Description>Problem while inserting/updating processes</Description>   
     <Exception><![CDATA[   
java.sql.SQLException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into ("NIKU"."BPM_DEF_ASSIGNEES"."PRINCIPAL_ID")  

Solution:

WORKAROUND:

The installation tries to XOG several processes, looking for terms such as 'Project Manager'. If the Language for the Clarity admin user is not English, it does not find such a value, so attempts to insert a NULL, which is not permitted and throws the error that you have encountered.

Use the following steps to resolve this issue:

  1. Restore the database to its previous version from backup.

  2. Restore the Clarity files to its previous version from backup.

  3. Start the old Clarity services.

  4. Log into Clarity as admin, go to Account Settings, under Personal, change the Language to English, and SAVE.

  5. Stop all Clarity services.

  6. Retry the upgrade.

STATUS/RESOLUTION:

This issue has been documented and is assigned to development for review. If you are experiencing this problem and the workaround above does not significantly help, please contact CA Clarity Technical Support.

Keywords: CLARITYKB, CLRT-21964, clarity12open.