To check why the issue might be occurring, start by reviewing the following:
1. Open JobQueueInfo, look at the DBQueue section, take note of the DBQueue task that is in a 'Is reset' state. Click on the View menu and select System journal from the list.
Here we should see warnings like the one below:
"Resetting DBQueue tasks {0} because processes {1} related to objects on these tasks are still running in JobQueue"
Double-click on the warning. This will present the reason why this particular DBQueue task is in a 'Is reset' state.
2. Check the table QBMDBQueueCurrent, and look for the column SlotNumber.
Use the following query within SQL Management Studio, e.g.:
select * from QBMDBQueueCurrent
- If SlotNumber is -1, then the DBQueue task was reset due to a synchronization that is running for an affected target system.
Check the Job queue to confirm if any synchronization jobs are present and currently processing or frozen.
- If SlotNumber is -3, then the DBqueue task was reset due to a pending job in
QBMElementAffectedByJobIf -3 is the case, look in the table
QBMElementAffectedByJob and confirm what
UID_Job is listed, then check if that job is in the Job queue (select the running process in the Job queue, then the UID_Job value will be visible in the
Process step pane):
3. For issues where a reindex table DBQueue task is getting reset, check the
UID_Parameter and
UID_SubParameter values for
QBMDBQueueCurrent as these may provide a clue as to what is affected. For example, if the
UID_Task is
QBM-K-CommonReindexTable the UID_Parameter will provide the name of the table where it is failing.