Clarity

New to Clarity/PPM inner workings but we have a time slice job running against this table where it sets SLICE_STATUS to 0,1,2,3 or 4.

We believe it might be related to changes to reporting added for Jaspersoft (Moving away from Biz Objects)

There are 17 million records in this table.

The main  update we see running is   (Calling other procedures?)

UPDATE PRTimeentry

   SET SLICE_STATUS = :"SYS_B_0"

   WHERE SLICE_STATUS = :v0

   ADD ROWNUM <= :"SYS_B_1"

We are out of ideas.   Oracle DB tuning had no suggestions.  It is only updating about 1000 records a minute.  Indexes won't have any help we are told as there are nulls in SLICE_STATUS.    We were told maybe a Bitmap index might help but I think something else is going on here we are not aware of.

Hi Paul

I checked and it looks like you are on PPM 14.2 in our system. This sometimes happens when a SQL trace is enabled, which slows down the Timeslicing job.
In that case please try the following.

1.       Stop services.
2.       Modify your properties.xml:

From:
traceEnabled="true"

To:
traceEnabled="false"

If you have the traceJDBCEnabled option, set it to false as well.

3.       Save, and repeat for all servers in cluster.

4.       Once done, start back the services. Ensure the job is no longer running on database side and kick it off again, see if that helps.

Hope this helps -Nika

We applied the solution above with Paul and his team, on their Support case on Monday and the issue was resolved.