Description:
We can have orders in START status when restarting Tomcat or when Tomcat goes down. We can find orders in START status with no plan. These orders do not resume after a Tomcat restart. We will see order related information in tables ORDERS,ORDER_DETAILS and sometimes in OMS_ROUTER_TBL.

• com.tibco.af.oms.webservice.idempotency=true (ConfigValues_OMS.xml)

- It is possible for order to remain in START state with data in ORDERS/ORDER_DETAILS table and no entry in OMS_ROUTER_TBL. In such cases, the order can be recovered by resubmitting such orders.

- It is possible for order to remain in START state with entries in ORDERS,ORDER_DETAILS and OMS_ROUTER_TBL table.  We have JIRA AF-5128: Order recovery doesn't happen if routing of order to Orchestrator fails and order stays in START state for this (Fix version: Ruby). Orders can be recovered through resubmission by removing the corresponding entry in OMS_ROUTER_TBL. No need to restart Tomcat.
 

• com.tibco.af.oms.webservice.idempotency=false (ConfigValues_OMS.xml)

 - We will have to delete the corresponding entries in ORDERS,ORDER_DETAILS and OMS_ROUTER_TBL. No need to restart Tomcat. Resubmit the order.
  -- using orderid
 
  DELETE FROM OMS_ROUTER_TBL
  WHERE orderid='%%ORDER_ID%%';
 
  delete from order_details
  where orderid='%%ORDER_ID%%';
 
  delete from orders
  where orderid='%%ORDER_ID%%';
 
  commit;
 
  -- using order ref
 
  DELETE FROM OMS_ROUTER_TBL
  WHERE orderid=( select orderid from orders where orderref='%%ORDER_REF%%');
 
  delete from order_details
  where orderid=( select orderid from orders where orderref='%%ORDER_REF%%');
 
  delete from orders
  where orderid=( select orderid from orders where orderref='%%ORDER_REF%%');
 
  commit;

How to resubmit orders in START status.