The Gantt view is not displaying tasks (the Gantt is blank) for one or more projects and the Clarity app-ca.logs shows an error referencing 'ORA-01400: cannot insert NULL into' (example below)
com.niku.union.persistence.PersistenceException: SQL error code: 1400 Error message: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into ("XXXXX"."TEMP_WBS"."PAR_SEQ")
insert into TEMP_WBS( cacheid, projectid, taskid, origwbssequence, origwbslevel, wbssequence, wbslevel, par_seq, nnb_seq, prrefprojectid,visible )
( select ?, projectid, taskid, origwbssequence, origwbslevel, wbssequence, wbslevel, par_seq, nnb_seq, prrefprojectid, case when wbslevel= 1 then 1 else 0 end from TEMP_WBS_GLOBAL )
Note: If you click 'Show All' on the filter section in the Gantt, an error message displays in a popup window with a similar message of that referenced above.
TEMP_WBS and TEMP_WBS_GLOBAL in the error are two temporary tables that the Gantt View uses to load task data from Work Breakdown Structure (WBS) table named PRTASK. Sometimes, PRTASK.WBS_PARSEQ is NULL and can cause TEMP_WBS_GLOBAL.PAR_SEQ to be also NULL. This will lead to the above error because TEMP_WBS. PAR_SEQ must not be NULL.
Note: PRTASK.WBS_PARSEQ is a system-maintained field and is not configurable by the user.
Component: Clarity Project Management
Regenerate the PRTASK.WBS_PARSEQ value using one of the options below:
Option 1: Open the problem Project in a scheduler (Open Workbench (OWB) or Microsoft Project (MSP), then save it back without changing anything. In most instances, the WBS_PARSEQ is rewritten with a valid number during the save back to the CA PPM application.
1. Execute the following SQL query to display details of tasks containing a null value on the column WBS_PARSEQ.
(Clarity SaaS Customers, please contact Broadcom support for assistance with this option).
AND PRTASK.PRPROJECTID =<Project internal id in terms of 5 million number>
AND WBS_PARSEQ is NULL
2. Remove the identified tasks from the Clarity UI and recreate the tasks.
In another case reported, the task came from a project created from a template.
Delete one task and re-added it back to the template.
Afterwards, the project's tasks become 'Open For Time Entry' in the timesheets.