Troubleshooting
Problem
Attempts to run confirmShipment does not move order status does not move to Shipped status in IBM Sterling Order Management.
Symptom
Order remains in the previous Packed status. This is an intermittent issue and does not occur all the time.
Cause
DB2 parameter DB2LOCK_TO_RB is not set to STATEMENT
Diagnosing The Problem
From the logs, it can be observed that the orderlines for which the status has to be changed to Shipped, the query to insert the status change takes place:
INSERT INTO YFS_ORDER_RELEASE_STATUS(ORDER_RELEASE_STATUS_KEY,ORDER_RELEASE_KEY,ORDER_LINE_KEY,ORDER_HEADER_KEY,STATUS,STATUS_DATE,STATUS_QUANTITY,PIPELINE_KEY,ORDER_LINE_SCHEDULE_KEY,TOTAL_QUANTITY,EXPECTED_SHIPMENT_DATE,CHAINED_TO_ORDER_LINE_KEY,CHAINED_TO_ORDER_HEADER_KEY,CREATETS,MODIFYTS,CREATEUSERID,MODIFYUSERID,CREATEPROGID,MODIFYPROGID,LOCKID) values ( 'XXX','XXX','XXX','XXX','3700','XXX',XXX,'XXX','XXX',XXX,'XXX',' ',' ','XXX','XXX','XXX','XXX','XXX','XXX',XXX )
However, subsequently the log would show that querying the YFS_ORDER_RELEASE_STATUS returns status of 3350.500 which was the previous state. Hence, the Order status does not get updated.
Resolving The Problem
If Hot Sku is enabled, DB2LOCK_TO_RB must be set to STATEMENT. This registry variable specifies whether lock timeouts cause an entire transaction or only the current statement to be rolled back. If DB2LOCK_TO_RB is set to STATEMENT, locked timeouts cause only the current statement to be rolled back. Any other setting results in transaction rollback.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22000759