See information about the latest product version
Configuring databases for global coordination of transactions
If your message flow interacts with a user database, and you want to globally coordinate the updates made to the database with other actions within the message flow, configure your databases for global coordination.
If you restart a user database while the broker is still running, you must also restart the broker. The broker cannot detect that the database has stopped, and WebSphere® MQ therefore retains its old connections to the database. When the database starts again, the broker tries, and fails, to use these connections.
Configuring DB2 for global coordination of transactions
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.
Configuring Oracle for global coordination of transactions
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.
Configuring Sybase for global coordination of transactions
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.