| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Co Ordinated Transaction error |
« View previous topic :: View next topic » |
| Author |
Message
|
| gmmqnet |
 Posted: Thu Feb 12, 2004 7:23 pm Post subject: Co Ordinated Transaction error |
 |
|
Novice
Joined: 12 Feb 2004
Posts: 18
|
Hello,
I have been trying ot deploy the message flows for WBIFN.I have been able to successfully deploy them on the test machine and now have been trying to deploy them on the production machine and have been getting this error in the db2diag.log continously.
2004-02-13-11.10.38.431436 Instance:udb2adm1 Node:000
PID:26448(DataFlowEngine) Appid:
oper_system_services sqlocshr2 Probe:200
0000 0018 ....
2004-02-13-11.10.38.591387 Instance:udb2adm1 Node:000
PID:26448(DataFlowEngine) Appid:
oper_system_services sqlocshr2 Probe:200
pSetHdl 303b 8000 303b 8000 0001 0000 0192 0037 0;..0;.........7
0004 0000 ....
2004-02-13-11.10.38.824238 Instance:udb2adm1 Node:000
PID:26448(DataFlowEngine) Appid:
XA DTP Support sqlxa_open Probe:101
DIA4701E Database "DNIRTDB" could not be opened for distributed transaction
processing.
String Title: XA Interface SQLCA PID:26448 Node:000
---------------------------
my qm.ini read like this for the XA resource stanza.
XAResourceManager:
Name=DB2 DNIRTDB
SwitchFile=/usr/opt/wmqi/sample/xatm/db2swit
XAOpenString=DNIRTDB,udb2adm1,udb2adm1
ThreadOfControl=PROCESS
---------------------------
instance name for db2 -udb2adm1 and the user id - udb2adm1
---------------------------
For WBIFN there are 10 main flows out of these I can deploy 4 msg flows -any of them -with the transaction co ordination set on in the check box.But if I have to put another msg with the co ordinated transaction set and then deployed it will give start giving me error on the db2diag and this is what I get from the syslog.
Feb 12 14:45:29 wbifn_p WMQIv210[31284]: (MQWPBRK.default)[4113]BIP2628E: Exception condition detected on input node 'DNI_TIMER_3420.DniTimer.Trigger.GenerateMessage.DniCTP1'. : MQWPBRK.98136b86-fa00-0000-0080-ca3a991dec68: /build/S210_BP/src/DataFlowEngine/PluginInterface/ImbCniNode.cpp: 728: ImbCniNode::dispatcher: ComIbmCniNode: 5e3b4f8e-f500-0000-0080-e933d76678bd.40a84c8e-f500-0000-0080-e933d76678bd.beda4b8e-f500-0000-0080-e933d76678bd.43464a8e-f500-0000-0080-e933d76678bd
Feb 12 14:45:29 wbifn_p WMQIv210[31284]: (MQWPBRK.default)[4113]BIP2230E: Error detected whilst processing a message in node 'DNI_TIMER_3420.DniTimer.Trigger.AddCategoryValue.DniAVN1'. : MQWPBRK.98136b86-fa00-0000-0080-ca3a991dec68: : 1087: : ComIbmCniNode: 5e3b4f8e-f500-0000-0080-e933d76678bd.40a84c8e-f500-0000-0080-e933d76678bd.4ec14d8d-f500-0000-0080-e933d76678bd.6ca4c6f0-ef00-0000-0080-cf2ea7585306
Feb 12 14:45:29 wbifn_p WMQIv210[31284]: (MQWPBRK.default)[4113]BIP5009E: XML Parsing Errors have occurred. : MQWPBRK.98136b86-fa00-0000-0080-ca3a991dec68: : 339: : :
Feb 12 14:45:29 wbifn_p WMQIv210[31284]: (MQWPBRK.default)[4113]BIP5004E: XML parsing error (Invalid document structure) encountered on line 1 column 1 while parsing element XML. : MQWPBRK.98136b86-fa00-0000-0080-ca3a991dec68: /build/S210_BP/src/MTI/MTIforBroker/GenXmlParser2/XmlBrokerAsgardParser.cpp: 728: XmlBrokerAsgardParser::error: :
Feb 12 14:45:33 wbifn_p WMQIv210[31284]: (MQWPBRK.default)[4370]BIP2633W: Warning when starting transaction coordinated by MQSeries; MQBEGIN failed: MQCC=1; MQRC=2122; node 'DNI_N_EVENT_3420.DniNEvent.Input'. : MQWPBRK.98136b86-fa00-0000-0080-ca3a991dec68: /build/S210_BP/src/DataFlowEngine/ImbMqInputNode.cpp: 780: ImbMqInputNode::readQueue: ComIbmMQInputNode: 21281242-ef00-0000-0080-aa3c7759a610.89550f42-ef00-0000-0080-aa3c7759a610
Feb 12 14:45:33 wbifn_p WMQIv210[31284]: (MQWPBRK.default)[3856]BIP2633W: Warning when starting transaction coordinated by MQSeries; MQBEGIN failed: MQCC=1; MQRC=2122; node 'DNI_SAMPLE_3420.DniSample.SampleInputQueue'. : MQWPBRK.98136b86-fa00-0000-0080-ca3a991dec68: /build/S210_BP/src/DataFlowEngine/ImbMqInputNode.cpp: 780: ImbMqInputNode::readQueue: ComIbmMQInputNode: 883b325c-ef00-0000-0080-b9088e287155.647c803c-ef00-0000-0080-b9088e287155
-------------------------------------------------------
Any help in this matter will be welcome.
GM |
|
| Back to top |
|
 |
| bolek |
| Posted: Fri Feb 13, 2004 12:11 am Post subject: Re: Co Ordinated Transaction error |
|
|
Apprentice
Joined: 25 Jul 2002
Posts: 35
Location: Germany
|
Hi,
which platform do you use ?
I think you have two problems:
1. XML parsing error in DNI_TIMER - you need an APAR from WMQI to use Timer service ( I think it is PQ73602 ).
2. DB2 switch file is not compatible with your DB2 release ( see /usr/opt/wmqi/sample/xatm/readme for more details how to use the switch file ).
Anyway, contact WBI FN Service  |
|
| Back to top |
|
|
| gmmqnet |
| Posted: Mon Feb 16, 2004 12:00 am Post subject: |
|
|
Novice
Joined: 12 Feb 2004
Posts: 18
|
Bolek,
First of all thanks for the reply and here are my replies to your queries,
which platform do you use ?
Ans .AIX ,where the broker is running and WIN2K for config mgr.
I think you have two problems:
1. XML parsing error in DNI_TIMER - you need an APAR from WMQI to use Timer service ( I think it is PQ73602 ).
2. DB2 switch file is not compatible with your DB2 release ( see /usr/opt/wmqi/sample/xatm/readme for more details how to use the switch file ).
Anyway, contact WBI FN Service
As for you suggestion that I should need an APAR or for that matter need to change the db2swit file ,here is my reply.I have thing running on the test set up with all the same configuration without any change.That is the reason I find it all the more surprising that it is not working on the production machine.Any suggestion that you can offer in this matter would be of immense help .
GM |
|
| Back to top |
|
|
| bolek |
| Posted: Mon Feb 16, 2004 5:02 am Post subject: |
|
|
Apprentice
Joined: 25 Jul 2002
Posts: 35
Location: Germany
|
I can bet that you have some differences between your systems
1. Timer service can't run without the APAR ( APAR is included in CSD06 ). BTW, Timer is optional service and you do not need to deploy Timer flow if you do not need them.
2. There is a number of possible reasons why XA does not work. Could you post SQLCODE(s) from db2diag.log ? If you find SQL1224N, check whether DB2 is started with EXTSHM=ON ( see http://www-306.ibm.com/software/data/db2/udb/ad/db2irfp4/db2ir266.htm for more details ).
Anyway I could suggest to contact IBM Service. |
|
| Back to top |
|
|
| gmmqnet |
| Posted: Fri Feb 27, 2004 1:02 am Post subject: Problem sorted |
|
|
Novice
Joined: 12 Feb 2004
Posts: 18
|
I have resolved the error that I had been receiving in this case .The solution that I have used is to export the db2instance in the broker user profile.Stop the Broker and Q Mgr and then the db2 isntance.The follow up with the starting the db2 instance and Q Mgr and then the broker.
Thanks for you help .
 |
|
| 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
|
|
|
|
