Time Slicing Sync performance / filling TEMP space on Temp LOBS in Oracle

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

After upgrade to 16.4.1, when a large Oracle customer is running Time Slicing Sync, it fills up the TEMP tablespace with temporaryLobs and leads to other jobs being stuck & them having to restart BG. The job is taking over 35 minutes

We have addressed part of the issue in DE191176 on 16.4.2.

STEPS TO REPRODUCE:

1. Have a very large amount of Calendar Exceptions, on each resource
2. Run Time Slicing & Time Slicing Sync on a test system with Oracle

Expected Results: The Time Slicing Sync to run consistently. 

Actual Results: Time Slicing Sync runs for 30+ min and TEMP tablespace eventually starts running out

Environment

Clarity 16.4.1, 16.4.2

Oracle Only

Cause

DE207767

Resolution

In Review by Engineering