Real-Time Load Plan (LOAD_PLAN_ON_DEMAND Or LOAD_PLAN_REALTIME_GLOBAL Or LOAD_PLAN_REALTIME_PROJECT) Showing Running Status In Analytics Administration Application But Not Actually Running When It Should
Last updated on JULY 10, 2018
Applies to:Primavera Analytics Cloud Service - Version 18.5 and later
Information in this document applies to any platform.
The realtime load plans (LOAD_PLAN_REALTIME_PROJECT or LOAD_PLAN_REALTIME_GLOBAL or LOAD_PLAN_ON_DEMAND) have potential to reflect a "running" load plan that is not tied to an actual hierarchical session.
This causes two issues:
- The load plan will never run when changes are made in P6 EPPM extended schema to trigger the real-time ETL.
- The Analytics Administration Application will display the real-time load plan in a running state even though the load plan is not actually running, preventing the load plan from being restarted within the UI.
If a real-time load plan is reliant on connection to a running hierarchical session, the load plan logic must be updated to restart itself if the actual hierarchical session is not running. Without this the load plan will be in an unstable state where it reflects as running in the Analytics Admin UI but not really running in additional to preventing a restart from within the UI resulting in a need to log an SR and engage cloud operations.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms