Frank Davis' Blog: OBIEE ONE

Just came across this one today.  This appears to be only in v7.9.6.2 as I have not seen before.  Here is the snippet of error message from DAC:

2011-05-12 08:43:50.358 INFORMATICA TASK:SILOS:@DAC_SIL_PositionDimension_FULL_TD_CMD:(Source : FULL Target : FULL) has started.

ANOMALY INFO::: Error while executing : INFORMATICA TASK:SILOS:@DAC_SIL_PositionDimension_FULL_TD_CMD:(Source : FULL Target : FULL)
MESSAGE:::
Irrecoverable Error
Request to start workflow : ‘@DAC_SIL_PositionDimension_FULL_TD_CMD’ has completed with error code 2
Error Message : The specified task name, workflow name, or folder name does not exist.

Pretty much it could not find the workflow as the full command for the task is defined in DAC metadata (OOTB) as ‘@DAC_SIL_PositionDimension_FULL_TD_CMD’.  In my most recent experience, with v7.9.6.1, this particular SIL task has the full command set as ‘SIL_PositionDimension_Full’.  So what is this ‘@DAC_’ value?  Well they were introduced recently to be utlized more and are DAC parameters.  Mostly you see them as a way to do parameter nesting.  This is the first time I have seen used in this way instead of the actual Informatica workflow names.

The cause for this DAC parameter not being substituted with its value? I searched around and got this from Oracle “COMMANDS FOR FULL AND INCREMENTAL SHOULD ALLOW DB SPECIFIC TEXTS”.  So I guess the task commands utilizing these DAC params are not properly passing and replacing those DAC params with their values.

Resolution: Use cumulative Patch 10052370.  Looking at the v7.9.6.2 release notes, this is a mandatory patch for the DAC for this release of OBIA.  Unfortunately, they do not go into great details for this bug.

UPDATE: PATCH ABOVE HAS BEEN DEPRECATED BY ORACLE AND YOU WILL BE REDIRECTED TO USE PATCH 13551596.