3 Critical Reasons Batch Execution Failed to Trigger a Data Load in FDMEE

Batch Execution is the most efficient way to trigger data loads in FDMEE, reducing the extra time you would’ve spent otherwise on manually running the loads. It’s a straightforward approach to defining the Batch Execution based on the execution mode you’ve selected (Parallel or Serial). The execution with batch is a straightforward process however it becomes a little tricky when Batch Execution fails and the logs do not provide much help sometimes. While there could be numerous reasons why the Batch Execution failed, I’m listing the most tricky scenario that I came across and spent hours troubleshooting only to find that the solution was pretty simple and the easiest one.

Batch Execution Issue Explained

So I came across this issue where I triggered the Batch from FDMEE that executes 3 Data Loads in a serial manner. Let’s say I have a batch that runs the load for location X and location Y and when it’s triggered it should ideally perform the load in those locations only once but it triggered the load 3 times for both locations.

The other batch I had did not trigger the loads at all. So two batches were having two different issues and it stopped working abruptly. The batch Definition was verified and it includes only one data load rule. Also, the event scripts – beforebatch.py and afterbatch.py scripts were already modified as per the environment and requirements. However, when I clicked the Execute Batch option, it did not trigger the loads and the Batch failed.

So the batch was failing repeatedly and below was the error I found in the log file.

I tried troubleshooting this error by clicking “Unlock all Locations” from Application Settings but it did not help.

After hours of troubleshooting, I figured out that you need to place the file in the folder from where the batch could pick up the file.

Let me put all the details using a detailed example of my case.

My batch name was “abc”. I had three locations for which I was trying to load the data. Let’s name these locations L1, L2, and L3. Whenever I was triggering the batch using the Execute Batch option under Batch Execution inside FDMEE, it failed and showed a red cross. Sometimes, it showed a green tick as well but did not trigger any load. The logs had the above error which I posted and a few times, I did not see any error in the logs. It was just the information. Then I performed the below troubleshooting steps that fixed the issue.

1.) Create an abc folder inside the FDMEEApps\inbox folder. The batch folder needs to be created manually sometimes when the batch doesn’t trigger the load automatically because FDMEE fails to recognize the batch folder definition by itself.

2.) You may create one more folder where all the individual locations folders are created and that’s where you keep the files required for the load. In my case, I created a folder called “IncomingBatch” and all the respective location folders were present inside this folder.

3.) Instead of putting the file that needs to be loaded in the IncomingBatch folder, place it in the respective location folder and then execute the batch. In my case, I placed it inside the IncomingBatch folder and respective locations folder as well which confused FDMEE and caused the batch to fail.

Pretty straight isn’t it? But little tricky as you don’t know why it keeps showing that same error when your load file is literally everywhere.

Hope it helps..!!!

To work efficiently with batches in FDMEE, read the official Oracle documentation – Working with Batch Definitions.

Also, Read another post on how you can troubleshoot common errors when you migrate the FDMEE Mappings across the environments. FDMEE Mapping Migration Issues.