PPM Gantt Does Not Load

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Sequence numbers keep incrementing when changes are done on the MUX Task timeline or PPM Gantt. When the PRWBSSEQUENCE and WBS_NNBSEQ fields exceed 32,000 value, duplicates occur and the task timeline or PPM Gantt can not be loaded any longer
Depending on the size of the project/number of tasks and how often it is modified it will be easier to hit this scenario.

Steps to Reproduce:

1. Create a project in MUX and add a few tasks
2. Look at SELECT prid, prname, PRWBSLEVEL, PRWBSSEQUENCE, WBS_PARSEQ, WBS_NNBSEQ FROM prtask WHERE PRPROJECTID = 5009014
   5018000 aaa 2 3 2 4
   5018001 bbb 1 1 -1 2
   5018002 cccc 1 2 -1 5
   5018003 ddd 2 4 2 5
3. Open the PPM Gantt or Tasks timeline and drag and drop tasks up and down. Notice the same query values.
   5018000 aaa 2 26 17 27
   5018001 bbb 2 27 17 28
   5018002 cccc 2 28 17 29
   5018003 ddd 1 17 -1 29
4. When the PRWBSSEQUENCE value reaches 32100 create a few tasks via postman using the task with that value as parent
5. Notice duplicates are created in the DB
6. Open the project in PPM Gantt

Expected results: The PPM Gantt loads the project Gantt

Actual results: Gantt does not load

 

app-ca.log file shows the following error:

Error at log files:
ERROR 2024-09-13 04:21:52,434 [http-nio-1623-exec-234] service.WBSService (clarity:myuser:mysession:odata.WBSService.loadFast) (ead56154-583a-4498-9863-166038dd9cc5) 
com.niku.union.persistence.PersistenceException: 
SQL error code: 1
Error message: ORA-00001: unique constraint (myclarity.TEMP_WBS_GLOBAL_PK) violated

Executed:
 insert into TEMP_WBS_GLOBAL( taskid, projectid, wbssequence, wbslevel, origwbslevel,origwbssequence, par_seq, nnb_seq, origpartask, orignnbtask )
           (
            SELECT task.prid, task.prprojectid, task.prwbssequence, task.prwbslevel, task.prwbslevel, task.prwbssequence, task.wbs_parseq, task.wbs_nnbseq
                   , PARENTTASK.PRID, NNBTASK.PRID
              FROM PRTASK TASK
                   LEFT OUTER JOIN PRTASK PARENTTASK ON PARENTTASK.PRWBSSEQUENCE = TASK.WBS_PARSEQ AND PARENTTASK.PRPROJECTID = TASK.PRPROJECTID
                   LEFT OUTER JOIN PRTASK NNBTASK ON NNBTASK.PRWBSSEQUENCE = TASK.WBS_NNBSEQ AND NNBTASK.PRPROJECTID = TASK.PRPROJECTID
             WHERE TASK.PRPROJECTID = ?
            )

Environment

This issue has been observed in: Clarity 16.2.1, 16.2.2, 16.2.3, 16.3.0.

Cause

DE156013

Resolution

This issue has been fixed in Clarity 16.3.1.

Workaround: Open the project in Open Workbench (OWB) and save. Sequences will be reset.