Correlating the Transaction ID

Installable cloud operations perform all database operations in transactions. Each transaction is assigned with a unique transaction ID. An existing transaction ID will become invalid if any of the following cases occur:

  • When the relevant session ID becomes invalid;

  • At the execution of Connect, Disconnect, Commit, or Rollback.

When the Connect, Disconnect, Commit or Rollback is executed, the response body will contain the new transaction ID. When the Commit or Rollback is executed but has failed, the response body will still contain the old transaction ID, which means that the old transaction is still valid.

It is necessary to catch the proper “transactionid” from the server response on Connect/Disconnect/Commit/Rollback, and then attach it to the subsequent requests. That is, correlating the transaction ID in the script for successful replay.