Search Engine: Elastic

Article ID: 122306, created on Jul 9, 2014, last review on Jul 9, 2014

  • Applies to:
  • Business Automation 5.5


Sales or Resource Upgrade order may stuck in "Provisioning" status. The Order may have one of the provisioning items failed.

To locate failed item and its ID one may open: Home > Operations > Orders > SOxxx/UGxxx > Provisioning Items > Line ID

In Home > Operations > Tasks > All Events >

There is a failed event of type "Creation Completed" or "Upgrade Completed" with parameter "OrderItemID=Line ID" with the following content:

Status  Failed
Start Time      09-04-2014 18:07:27
End Time        01-01-1970 02:00:00
Redo Counter    1
Execution Failed: ODBC code #40P01: ERROR: deadlock detected
Process 22898 waits for ShareLock on transaction 567516164; blocked by process 22899.
Process 22899 waits for ShareLock on transaction 567516174; blocked by process 22927.
Process 22927 waits for ShareLock on tuple (2753,22) of relation 40498 of database 40386; blocked by process 22898.;
Error while executing the query
Transaction ID  0

In BM.log one may find that the deadlock occurred on Accounts table. What is the reason of the deadlock?


The issue can be caused by an internal issue PBA-56243. It raises when certain account is trying to launch several Sales / Upgrade orders at the same time.

The issue will be fixed in one of the future versions of PBA-E.


As a workaround, Provider is suggested to resubmit corresponding failed event:

In Home > Operations > Tasks > All Events > Failed Event > "Resubmit" button.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF