We are facing Synchronization error in our running application , in this application we are extracting data from source system and load in our database , extraction and loading is multiinstance job . due to this error
it not triggered other job .
Error Log :-
J8IcaSrc.61.T1: Synchronization error Resource = J8IcaSrc.61.InvoiceReceivableFile.ToInvoiceRcvbleFile, CurWave = 7, LastWave = 6, Expected 6
Synchronization error Resource
Moderators: chulett, rschirm, roy
Synchronization error Resource
Arun Verma
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Reset the job, which will also reset the wave numbers, and this problem should go away.
DataStage works with the concept of "resources" (in the RT_STATUS hashed files in the Repository, which is viewed by the Status view and Monitor view in Director, and by "show performance statistics" in Designer (version 5.2 and later)). Simplistically, a resource is something that is going to consume CPU resources, maybe a job, maybe an active stage.
Wave numbers are used to maintain synchronization internally, including when an aborted job is being reset. Wave numbers are visible in detail of status events in Director, but are not otherwise documented.
It looks like something has caused the wave numbers not to be correct in your case. Resetting the job should force them to be synchronized again.
DataStage works with the concept of "resources" (in the RT_STATUS hashed files in the Repository, which is viewed by the Status view and Monitor view in Director, and by "show performance statistics" in Designer (version 5.2 and later)). Simplistically, a resource is something that is going to consume CPU resources, maybe a job, maybe an active stage.
Wave numbers are used to maintain synchronization internally, including when an aborted job is being reset. Wave numbers are visible in detail of status events in Director, but are not otherwise documented.
It looks like something has caused the wave numbers not to be correct in your case. Resetting the job should force them to be synchronized again.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.