DTM Administration and Troubleshooting

DTM administration includes using transactions and threads of control, querying systransactions, executing external transactions. Troubleshooting DTM includes recovering from a system failure, heuristically completing transactions, and using configuration options to track transaction issues.

• Transactions and Threads of Control
  SAP ASE provides native support for the “suspend” and “join” semantics used by X/Open XA-compliant transaction managers such as Encina and TUXEDO. Transactions may be shared among different threads of execution, or may have no associated thread at all.
• Getting Information About Distributed Transactions
  systransactions stores information about all server transactions, and identifies each transaction and maintains information about the state of the transaction and its associated threads.
• Executing External Transactions
  The transaction manager executes external transactions.
• Crash Recovery Procedures for Distributed Transactions
  During crash recovery, SAP ASE must resolve distributed transactions that it discovers in the prepared state.
• Heuristically Completing Transactions
  SAP ASE includes the dbcc complete_xact command to facilitate heuristic completion of transactions.
• Troubleshooting for Transactions Coordinated by External Transaction Managers
  If a transaction is coordinated by an external transaction manager using X/Open XA protocol or through Adpative Server transaction coodination services of another SAP ASE, then DDL commands are not allowed within the transaction. This behavior applies even if the database option ddl in tran is enabled.