After an BusinessConnect Interior Server restart, batched transactions are stuck in BC_SCHEDULED_TASK table
Article ID: KB0082149
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect EDI Protocol Powered by Instream | 6.X |
Description
After the interior server restart, some outbound X12 batches get "stuck" in BC and are not sent out to the trading partner. The transactions are in "RUNNING" state but will not get transmitted because the batch time has passed.
Issue/Introduction
After an BusinessConnect Interior Server restart, batched transactions remain stuck in BC_SCHEDULED_TASK table and are not transmitted even though the time when the transaction was supposed to go out has passed.
Environment
All platforms
Resolution
In order to get the TASKID of the transactions whose batch time has passed, run the following sample query :
<<<
SELECT TASKID FROM [TIBCO_BCPROD].[dbo].[BC_SCHEDULED_TASK]
WHERE STATUS='RUNNING' AND
NEXTSTARTTIME < current_timestamp;
>>>
This will give you one or more TASKID's
Take one TASKID at a time and in the BC_SCHEDULED_TASK table, run a query and update the STATUS to PENDING and NEXTSTARTTIME to current_time + 5 minutes (say) and re-trigger the transaction.
A sample query would be like this (this is for Microsoft SQL Server):
<<<
<<<
SELECT TASKID FROM [TIBCO_BCPROD].[dbo].[BC_SCHEDULED_TASK]
WHERE STATUS='RUNNING' AND
NEXTSTARTTIME < current_timestamp;
>>>
This will give you one or more TASKID's
Take one TASKID at a time and in the BC_SCHEDULED_TASK table, run a query and update the STATUS to PENDING and NEXTSTARTTIME to current_time + 5 minutes (say) and re-trigger the transaction.
A sample query would be like this (this is for Microsoft SQL Server):
<<<
UPDATE [TIBCO_BCPROD].[dbo].[BC_SCHEDULED_TASK]
SET STATUS = 'PENDING'
,NEXTSTARTTIME = '2017-12-07 14:00:00.000'
WHERE TASKID = 'D1A7F71D-1C52-49E2-8792-93110E494F3F'
>>>
This will cause the BC batch poller to restart the job and send the batch out at the next batch polling cycle.
Feedback
Yes
No
Powered by
