| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Database Transaction Troubles |
« View previous topic :: View next topic » |
| Author |
Message
|
| KingMoonMan |
 Posted: Fri Jan 31, 2003 12:11 pm Post subject: Database Transaction Troubles |
 |
|
Newbie
Joined: 31 Jan 2003
Posts: 5
|
I'm having two problems that I hope someone can help me with. We are running MQSI v2.1 CSD03. Our broker database is DB2 v7.1, and the database we attempt to update from MQSI compute nodes is a seperate mainframe DB2 v6.1. We have configured our MQSeries (5.2) service to act as a XA resource manager as recommended in the System Administration Guide chapter 12, and Developing Solutions in WebSphere MQ Integrator chaper 9 books.
When we deploy a flow with coordinated transactions on (a full normal deploy), the messages pass through the flow successfully, but are never committed. Eventually the mainframe times the connection out and the updates are rolled back. The messages pass through the flow, end up on the output queues, and they are not rolled back. We tried setting the commit interval and count to non-default settings, but that didn’t seem to have an impact.
We did not compile a DB2SWIT.dll file, but instead relied on the one sent with the product. Also, we only configured the tp_mon_name setting on the broker database.
The second issue occurs when we attempt to work around the first issue. We have a flow with an input node, a compute, and an output node. The compute node performs a select, an update, and an insert. When more than one message arrives on the input queue nearly simultaneously (10-20) a few will succeed, but the rest will fail with a "Database error: SQL State 'HY010'; Native Error Code '-99999'; Error Text '[IBM][CLI Driver] CLI0125E Function sequence error. SQLSTATE=HY010'". We are not running this flow as part of a coordinated transaction and have the node set to Commit. If single messages are placed on the queue the update works fine. We attempted to increase the additional instances property, to no avail.
In both scenarios we have the input queue defined as transactional. If anyone could provide me any assistance it would be greatly appreciated! |
|
| Back to top |
|
 |
| philip.baker |
| Posted: Tue Feb 04, 2003 10:43 am Post subject: |
|
|
Voyager
Joined: 21 Mar 2002
Posts: 77
Location: Baker Systems Consulting, Inc. - Tampa
|
KingMoon,
Not too sure about your first issue. You may want to somehow confirm that the XA activity is working before going up to the Mainframe DB.
But for the second issue, to resolve certain DB locking issues, run db2set DB2_RR_TO_RS=YES from the db2 command line. This is for the broker database on a Windows environment.
_________________
Regards,
Phil |
|
| Back to top |
|
|
| KingMoonMan |
| Posted: Tue Mar 11, 2003 8:54 am Post subject: Database Transaction Troubles [Solved] |
|
|
Newbie
Joined: 31 Jan 2003
Posts: 5
|
In case others find similar errors with their implementation, the following items fixed our problems.
The function sequence errors were negated by setting a Windows 2000 enviromental variable to be MQSI_DB2_ALWAYS_PREPARE=YES. Turning on our DB2 Connect concentrator solved the problem with commits and coordinated transactions. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
