My Oracle Support Banner

Slow Runtimes For History Related ODI ETL Steps After Disabling History For All Projects In P6 EPPM (Doc ID 2463861.1)

Last updated on DECEMBER 13, 2018

Applies to:

Primavera Analytics Cloud Service - Version 17.11.0.0 and later
Primavera Analytics - Version 17.11.0.0 and later
Primavera Data Warehouse - Version 17.11.0.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
-----------------------
P6 EPPM activity (daily) history was once enabled for 800+ projects within P6 EPPM but recently disabled / turned off for all P6 EPPM projects.

After disabling history for all P6 EPPM projects, the following steps of the Data Warehouse ETL show high runtimes:

For example, the ETL log file shows the following runtime duration of these steps which match the runtime duration when history *was* enabled:
...
[DONE] Load assignment spread history, duration = 3995 seconds (1.1 hours)
[DONE] PROC_LOAD_ASSIGNMENT_SPREAD_HISTORY
[DONE] Load activity spread history, duration = 6051 seconds (1.7 hours)
[DONE] PROC_LOAD_ACTIVITY_SPREAD_HISTORY
[DONE] After loading package SCD, duration = 6089 seconds (1.7 hours)
[DONE] PROC_AFTER_LOADING_PKG_SCD
...


EXPECTED BEHAVIOR
-----------------------
When history is disabled (after once being enabled) for all P6 EPPM, the three noted steps should show improved runtime duration since history is no longer being captured. In fact, the procedures which are executed should be skipped over if no projects are configured for the associated history level which would require it's execution.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

  1. Turn on (Activity daily) history level for all P6 EPPM projects. Note, this is done on the projects page within P6 (web)
  2. Execute consecutive ETLs and note the ETL duration of the three noted steps
  3. Turn off history level for all P6 EPPM projects. Note, this is done on the projects page within P6 (web)
  4. Execute an ETL and note the runtime matches the runtime when history was enabled.


BUSINESS IMPACT
-----------------------
When history is no longer enabled for P6 EPPM projects, steps which are relative to history capture should be skipped over which will improve the overall runtime of the ETL.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.