Configuring databases for global coordination of transactions
If your message flow interacts with a database, and you want to globally coordinate the updates made to the database with other actions within the message flow, configure your databases for globally coordinated transactions.
About this task
If you restart a database while the integration node is still running, you must also restart the integration node. The integration node cannot detect that the database has stopped, and WebSphere® MQ therefore retains its old connections to the database. When the database starts again, the integration node tries, and fails, to use these connections.
Configuring IBM Db2 for global coordination of transactions
Before you begin
You must complete these steps for databases that you connect to with an ODBC or a JDBC connection.
You must have database administrator (DBA) privileges to perform the following tasks.
About this task
Procedure
Results
What to do next
Configuring Oracle for global coordination of transactions
Before you begin
You must complete these steps for databases that you connect to with an ODBC connection only.
You must have database administrator (DBA) privileges to perform the following tasks.
About this task
Procedure
Results
What to do next
Configuring Sybase for global coordination of transactions
Before you begin
You must complete these steps for databases that you connect to with an ODBC connection only.
You must have database administrator (DBA) privileges to perform the following tasks.
Procedure
dtm_tm_role
.