Recovering from a Failed Delivery

If any failure occurs during Workspace publish, then all committed transactions are rolled back automatically, including the Workspace merge. If rollback also fails, then the Workspace Administrator should manually initiate a Revert operation followed by a Deliver/Rebase operation again.

The WORKSPACE_STATUS (LOV type) includes the following LOV values to indicate failure status:

• Publish Failed. This status appears when rollback of publish fails during the Deliver operation.

• Rebase Failed. This status appears when rollback of publish fails during the Rebase operation.

Reasons for a Workspace publish failure during a Deliver/Rebase operation include the application crashes, the database goes down or the database connection is lost. For example, if the database connection is lost, then the Deliver/Rebase operation may terminate abruptly or erroneously leaving the Integration Workspace in an incomplete state. In such a case, the Integration Workspace may end up in an Edit in Progress, Publish Failed, or Rebase Failed status. The failed Deliver operation would have generated a new version on the Integration Workspace, which is a bad version and needs a manual rollback. In this incomplete state, no other operation is allowed on the Integration Workspace except Revert. A Workspace Administrator must manually initiate a Workspace Revert operation on the Integration Workspace to roll back the incomplete Deliver/Rebase operation. This will revert the Integration Workspace back to a proper state. Thereafter, you may try to perform the Deliver/Rebase operation again.