Issues with Import Processing within the FDMEE/ODI Environment
I have recently come across issue’s with a client regarding imported processes within FDMEE that show up with green check marks but when selected, there are Red x’s being displayed of failed processes within the import, imported process showing as they are still being ran, of which, wasn’t the case, as they were failed jobs and a workaround in order to avoid auto duplicated imports that fail. Due to these types of issues, I have learned that:
A. For running job’s that are in fact failed jobs:
First verify that the job is either really running or in fact has failed by navigating to the Data management tab > Process Details and locating the Process ID of the Running Job.
Once you have located the running job, under the ODI Session Number column, select the ODI Session number associated with the same process Id that’s showing as running and download and open the log file. Log file will look something like the below image:
As you can see by the above image, this was in fact a failed session that ended in an error state but still shows up as a running job. See below:
If you would like to clean out your system of all stale sessions, you may do so by performing the following steps:
From the Operator Navigator toolbar menu, select Clean Stale Sessions.
In Topology Navigator, from the Physical Architecture accordion, select an Agent, right-click and select Clen Stale Sessions.
The Clean Stale Sessions Dialog specify the criteria for cleaning stale sessions:
From the list, select the Agents that will clean their stale sessions.
Select Clean all Agents if you want all Agents to clean their stale sessions.
From the list, select the Work Repositories you want to clean.
Select Clean all Work Repositories you want to clean stale sessions in all Work Repositories.
Click Clean to start the cleaning process. See below of what the open window would look like:
B. For imported processes within FDMEE that show up with green check marks but when selected, there are red x’s being displayed of failed processes:
For such instances, there isn’t much you can do.
Such issue’s occur when there’s an interference with the communication between the ODI server and the database server.
C. For avoiding FDMEE from auto producing a secondary import, after the first import has been executed, try the following workaround:
Note:This would be ideal until a permanent fix has been deployed.
From the Data Management > Data Load Workbench > select the desired Location (bottom left of screen) > select Import > (Execution Mode Option window will appear) File Name (click the SELECT button) and you can either select a File that's already been uploaded or select to UPLOAD the file. For the Mode section, this is where you’re going to select the Offline option, by selecting the Offline option, it will bypass FDMEE to auto-generate. See screenshot below.
For additional information pertaining to paragraphs A & B, see the below links:
http://docs.oracle.com/cd/E28271_01/integrate.1111/e12643/running_execution.htm