ETL Fails Then Automatically Restarts And Executes Successfully (Showing An OK Status) But Log File Shows Failure (And What Looks To Be Reference To The First ETL Failure)

(Doc ID 2401447.1)

Last updated on MAY 21, 2018

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
The scheduled ETL shows as failed, but then immediately after the failure a new ETL is kicked off and shows a status of OK.  However, the subsequent ETL displays a log file with a failure which makes it appear as if the subsequent ETL execution did not run successfully.

Example log for a P6 Datasource generated from the secondary run:

...
Load plan [LOAD_PLAN_DAILY] started, instance id = 5389
  rootStep_caseWhen
  [RUNNING] Load dimension and fact tables
  Pre-ETL Tasks for Textura
  Pre-ETL Tasks
[RUNNING] P6 Daily
  [DONE] Status daily run start, duration = 1 seconds
  [DONE] STATUS_DAILY_RUN_START
  [RUNNING] Case Data Source Type
  SQL scripts after loading part 1
  SQL scripts after loading part 2
  [DONE] Security Staging Updates, duration = 13 seconds
  [DONE] P6_INIT_W_PROJECT_SECURITY_SS_PHYSICAL
  [DONE] For scheduled interval projects, duration = 288 seconds
  [DONE] RUNNER_SCHEDULED_P6
  [DONE] P6_SCHEDULED_W_ACTIVITYCODE_DS_PHYSICAL
  [DONE] P6_SCHEDULED_W_ACTIVITYCODETYPE_DS_PHYSICAL
  [DONE] P6_SCHEDULED_W_ACTIVITY_D_PHYSICAL
  [DONE] P6_SCHEDULED_W_ACTIVITY_NOTE_D_PHYSICAL
  [DONE] P6_SCHEDULED_W_ACTIVITY_RISK_DS_PHYSICAL
  [DONE] P6_SCHEDULED_W_ACTIVITY_STEP_D_PHYSICAL
  [DONE] P6_SCHEDULED_W_ASSIGNMENT_D_PHYSICAL
  [DONE] P6_SCHEDULED_W_PROJECT_D_PHYSICAL
  [DONE] P6_SCHEDULED_W_PROJECT_NOTE_D_PHYSICAL
  [DONE] P6_SCHEDULED_W_RISK_D_PHYSICAL
  [DONE] P6_SCHEDULED_W_WBS_NOTE_D_PHYSICAL
  [DONE] P6_SCHEDULED_W_REFDELETE_S_PHYSICAL
  [DONE] P6_SCHEDULED_W_RESOURCE_ASSIGNMENT_D_PHYSICAL
  [DONE] P6_SCHEDULED_W_ACTIVITYCODEASSIGNMENT_DS_PHYSICAL
  [DONE] P6_SCHEDULED_W_ACTIVITY_EXPENSE_D_PHYSICAL
  [DONE] P6_SCHEDULED_W_P6_CBS_HIERARCHY_DS_PHYSICAL
  [DONE] P6_SCHEDULED_W_PROJECTCODEASSIGNMENT_DS_PHYSICAL
  [DONE] P6_SCHEDULED_W_WBS_D_PHYSICAL
  [DONE] P6_SCHEDULED_W_WBS_HIERARCHY_DS_PHYSICAL
  [DONE] SPREAD_INCREMENT_LOAD
  [DONE] P6_SCHEDULED_W_ACTIVITY_SPREAD_F_PHYSICAL
  [DONE] P6_SCHEDULED_W_RESOURCE_ASSIGNMENT_SPREAD_F
  [DONE] P6_SCHEDULED_W_ASSIGNMENT_SPREAD_F_PHYSICAL
  [DONE] SPREAD_FULL_LOAD
[ERROR]Load plan [LOAD_PLAN_DAILY] completed, duration = 416 seconds
-- End --

EXPECTED BEHAVIOR
For the ETL to complete successfully and generate a log file which either a) shows what the cause of failure is or b) shows a log file from the consecutive execution with better detail to the successful run.

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

  1. Login to the Analytics Administration Application
  2. Schedule the ETL to run at a scheduled interval time of your choosing.
  3. When the ETL executes at the defined interval, if it fails, note that a new ETL is automatically executed.
  4. The new ETL executes successfully but when clicking the View Log link, it generates a log file which shows an ETL failure (which appears to be the log from the first run)

 

Cause

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