How To Manage Tuxedo XA Transactions Between Multiple Databases When Partial Rollbacks,Stored Procedures,Triggers, And Registering Events Involved? (Doc ID 2191496.1)

Last updated on OCTOBER 14, 2016

Applies to:

Oracle Tuxedo - Version 11.1.1.3.0 and later
Information in this document applies to any platform.

Goal

1. Question #1:
  From a tuxedo service user invokes a procedure in Sybase, that performs a series of business validations and if successful, it completes by inserting a movement in the database.
  The transaction management is in TUXEDO.
  If a validation error occurs, user is required to do a partial rollback and then continue with the transaction to register an event in another database table.
  How do users proceed, in order to manage from one single TUXEDO service, and the transaction is nested, in regards to the ROLLBACK and COMMIT?.

2. Question #2:
  From a TUXEDO service, user ends up running a Store Procedure of another data base, which is associated with TRIGGERS.
  How do users efficiently handle the transaction in this case?
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms