Header Ads

SIP-20881: ERROR: The batch job did not start because a batch job is already running on table [Table Name] Informatica MDM

SIP-20881: ERROR: The batch job did not start because a batch job is already running on table<Table_Name>

The above error appears while running a Batch Job/Batch Group in MDM.


Reason:

There is a lock on the corresponding Base Object in the C_REPOS_APPLIED_LOCK table in Database.
In order to accommodate multi-threading,MDM make use of batch locks on dependent objects rather than row level locks as in previous versions.If there is a match path between Parent Base Object and Child Base Object,a batch lock is put on the parent Base Object when MDM runs the load or merge batch job.This will stop another child Base Object from running load or megre job in parallel.Likewise,MDM puts a batch lock on child Base Object while running a Parent Base Object.

Steps to Fix:

1)Load or Merge jobs should be run in series if there is a match path existing between Parent and Child Base Objects.

2)If the error still appears,delete the  record in C_REPOS_APPLIED_LOCK table.

2 comments:

Powered by Blogger.