| Author |
Message
|
| yaakovd_new |
 Posted: Thu Mar 18, 2004 5:28 am Post subject: Solved! Strange rumtime problem in WMQI |
 |
|
Apprentice
Joined: 03 Feb 2004
Posts: 25
Location: Israel
|
Hi.
I'll appreciate any help with that problem.
I've finished the development on NT include testing end-to-end.
Now we've tried to switch the broker from NT to AIX.
Configuration: WMQI 2.1 SP5 on AIX, MQ 5.3 SP6 , DB2 8.1, Configuration Manager on NT.
Mainfarme - MQ 5.3 with Natural adaptor.
All MQ CCSID - 1208
DB2 tables also created with Unicode (Broker. application DB, CfgManager).
First of all - is there any known problem with DB2 and Unicode ???
Flow 1.
receives XML message from online client,
generates:
a. XML audit message (using XML parser)
b. MRM message to Mainframe
c. Create a record in application DB (DB2).
Flow 1 is working properly.
The MRM message successfully processed on Mainframe side and the responce arrives on replyQ on AIX.
Flow 2.
receives XML audit message and generates other XML using MRM parser.
Flow faled generate output message, but when I change the output parser to XML in working properly.
I've gote the following error:
| Code: |
- <DatabaseException>
<File>/build/S210_P/src/DataFlowEngine/ImbOdbc.cpp</File>
<Line>154</Line>
<Function>ImbOdbcHandle::checkRcInner</Function>
<Type /> <Name /> <Label />
<Text>Root SQL exception</Text>
<Catalog>WMQIv210</Catalog>
<Severity>3</Severity>
<Number>2321</Number>
- <DatabaseException>
<File>/build/S210_P/src/DataFlowEngine/ImbOdbc.cpp</File>
<Line>255</Line>
<Function>ImbOdbcHandle::checkRcInner</Function>
<Type /> <Name /> <Label />
<Text>Child SQL exception</Text>
<Catalog>WMQIv210</Catalog>
<Severity>3</Severity>
<Number>2322</Number>
- <Insert> <Type>5</Type> <Text>08001</Text> </Insert>
- <Insert> <Type>2</Type> <Text>-1224</Text> </Insert>
- <Insert>
<Type>5</Type>
<Text>[IBM][CLI Driver] SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032</Text>
</Insert>
</DatabaseException> </DatabaseException>
|
Flow 3
1. Parce the Mainframe response
2. Get and delete record from DB2
3. Generate XML response to online client.
I've got the following error in MQSI log during processing the message:
| Code: |
Mar 17 18:41:40 rs31 WMQIv210[35950]: (RS31ND.INTENA)[3873]BIP2232E: Error detec
ted whilst handling a previous error in node 'IEC_TENA_DH_FromNaturalREP_FL.IEC_
INF_ErrorReplyXML_SFL.RevertReplyToQ'. : RS31ND.1bedab59-fb00-0000-0080-a75abe7f
e60f: /build/S210_P/src/DataFlowEngine/ImbDataFlowNode.cpp: 369: ImbDataFlowNode
::logExceptionList: ComIbmComputeNode: 7bbb9bf2-fa00-0000-0080-a75abe7fe60f.a25c
769d-f900-0000-0080-995db73969a9
Mar 17 18:41:40 rs31 WMQIv210[35950]: (RS31ND.INTENA)[3873]BIP2230E: Error detec
ted whilst processing a message in node 'IEC_TENA_DH_FromNaturalREP_FL.IEC_INF_G
etReplyQ_SFL.GetReplyToQ'. : RS31ND.1bedab59-fb00-0000-0080-a75abe7fe60f: /build
/S210_P/src/DataFlowEngine/ImbComputeNode.cpp: 453: ImbComputeNode::evaluate: Co
mIbmComputeNode: 4b8e989d-f900-0000-0080-995db73969a9.a25c769d-f900-0000-0080-99
5db73969a9
Mar 17 18:41:40 rs31 WMQIv210[35950]: (RS31ND.INTENA)[3873]BIP5902W: An error oc
curred in parser 'Root' whilst parsing the field named 'MRM' on behalf of node
'IEC_TENA_DH_FromNaturalREP_FL.TENA.HOURS.REP.DH'. The data being parsed was '4d
442020000000020000000000000002ffffffff0000000000000311000003234d5153545220202000
00000400000001c3e2d840d4c6c8e34040404040404040baee8655a4e25547414d5120525333314e
442020202020204057036f2001ec010000000054454e412e484f5552532e5245502e444820202020
202020202020202020202020202020202020202020202020202020525333314e4420202020202020
202020202020202020202020202020202020202020202020202020202020202020202074617a3871
20202020202020170ee5e3c1d4c9c5c34bc3c9c3e2e3f7ee865596fefb0001000000000000000020
20202020202020202020202020202020202020202020202020202020202020000000014349435354
3720204d434254202020202020202020202020202020203230303430333137313834343539383720
202020000000000000000000000000000000000000000000000000000000010000000000000000ff
ffffffd4c3c2d9f0f0f0f1d7d4d5f040404040d4d5d4d8c5d9d7f4c3f0f040404
Mar 17 18:41:40 rs31 WMQIv210[35950]: (RS31ND.INTENA)[3873]BIP2321E: Database er
ror: ODBC return code '-1'. : RS31ND.1bedab59-fb00-0000-0080-a75abe7fe60f: /buil
d/S210_P/src/DataFlowEngine/ImbOdbc.cpp: 154: ImbOdbcHandle::checkRcInner: :
Mar 17 18:41:40 rs31 WMQIv210[35950]: (RS31ND.INTENA)[3873]BIP2322E: Database er
ror: SQL State '08001'; Native Error Code '-1224'; Error Text '[IBM][CLI Driver]
SQL1224N A database agent could not be started to service a request, or was te
rminated as a result of a database system shutdown or a force command. SQLSTATE
=55032: RS31ND.1bedab59-fb00-0000-0080-a75abe7fe60f: /build/S210_P/src/DataFlowE
ngine/ImbOdbc.cpp: 255: ImbOdbcHandle::checkRcInner: :
Mar 17 18:41:40 rs31 WMQIv210[35950]: (RS31ND.INTENA)[3873]BIP2232E: Error detec
ted whilst handling a previous error in node 'IEC_TENA_DH_FromNaturalREP_FL.IEC_
INF_ErrorReplyXML_SFL.UnableGenerateReply'. : RS31ND.1bedab59-fb00-0000-0080-a75
abe7fe60f: /build/S210_P/src/DataFlowEngine/ImbDataFlowNode.cpp: 369: ImbDataFlo
wNode::logExceptionList: ComIbmComputeNode: 7bbb9bf2-fa00-0000-0080-a75abe7fe60f
.618aaeea-f900-0000-0080-995db73969a9
Mar 17 18:41:40 rs31 WMQIv210[35950]: (RS31ND.INTENA)[3873]BIP2230E: Error detec
ted whilst processing a message in node 'IEC_TENA_DH_FromNaturalREP_FL.IEC_INF_E
rrorReplyXML_SFL.RevertReplyToQ'. : RS31ND.1bedab59-fb00-0000-0080-a75abe7fe60f:
/build/S210_P/src/DataFlowEngine/ImbDataFlowNode.cpp: 536: ImbDataFlowNode::cre
ateExceptionList: ComIbmComputeNode: 7bbb9bf2-fa00-0000-0080-a75abe7fe60f.a25c76
9d-f900-0000-0080-995db73969a9
Mar 17 18:41:40 rs31 WMQIv210[35950]: (RS31ND.INTENA)[3873]BIP2321E: Database er
ror: ODBC return code '-1'. : RS31ND.1bedab59-fb00-0000-0080-a75abe7fe60f: /buil
d/S210_P/src/DataFlowEngine/ImbOdbc.cpp: 154: ImbOdbcHandle::checkRcInner: :
Mar 17 18:41:40 rs31 WMQIv210[35950]: (RS31ND.INTENA)[3873]BIP2322E: Database er
ror: SQL State '08001'; Native Error Code '-1224'; Error Text '[IBM][CLI Driver]
SQL1224N A database agent could not be started to service a request, or was te
rminated as a result of a database system shutdown or a force command. SQLSTATE
=55032: RS31ND.1bedab59-fb00-0000-0080-a75abe7fe60f: /build/S210_P/src/DataFlowE
ngine/ImbOdbc.cpp: 255: ImbOdbcHandle::checkRcInner: :
|
and in ODBC trace
| Code: |
HENV 0x00000000
HDBC 0x3b0728b8
HSTMT 0x00000000
WCHAR * 0x3b573854 (NYI)
SDWORD * 0x3b573b00 (-1224)
WCHAR * 0x3b573860 [ 184] "[IBM][CLI Driver] SQL
1224N A database agent could not be started to service a request, or was termin
ated as a result of a database system shutdown or a force command. SQLSTATE=550
32"
SWORD 512
SWORD * 0x3b573adc (184)
ppid=35440:pid= 5402:c16 EXIT SQLError with return code 0 (SQL_SUCCESS)
HENV 0x00000000
HDBC 0x3b0728b8
HSTMT 0x00000000
UCHAR * 0x3b573af8 (NYI)
SDWORD * 0x3b573b00 (-1224)
UCHAR * 0x3aad5e08 [ 184] "[IBM][CLI Driver] SQL
1224N A database agent could not be started to service a request, or was termin
ated as a result of a database system shutdown or a force command. SQLSTATE=550
32"
SWORD 1024
SWORD * 0x3b573adc (184)
ppid=35440:pid= 5402:c16 ENTER SQLError
HENV 0x00000000
HDBC 0x3b0728b8
HSTMT 0x00000000
UCHAR * 0x3b573af8 (NYI)
SDWORD * 0x3b573b00
UCHAR * 0x3aad5e08
SWORD 1024
SWORD * 0x3b573adc
ppid=35440:pid= 5402:c16 ENTER SQLErrorW
HENV 0x00000000
HDBC 0x3b0728b8
HSTMT 0x00000000
WCHAR * 0x3b573854 (NYI)
SDWORD * 0x3b573b00
WCHAR * 0x3b573860
SWORD 512
SWORD * 0x3b573adc
ppid=35440:pid= 5402:c16 EXIT SQLErrorW with return code 100 (SQL_NO_DA
TA_FOUND)
HENV 0x00000000
HDBC 0x3b0728b8
HSTMT 0x00000000
WCHAR * 0x3b573854 (NYI)
SDWORD * 0x3b573b00
WCHAR * 0x3b573860
SWORD 512
SWORD * 0x3b573adc
ppid=35440:pid= 5402:c16 EXIT SQLError with return code 100 (SQL_NO_DAT
A_FOUND)
HENV 0x00000000
HDBC 0x3b0728b8
HSTMT 0x00000000
UCHAR * 0x3b573af8 (NYI)
SDWORD * 0x3b573b00
UCHAR * 0x3aad5e08
SWORD 1024
SWORD * 0x3b573adc
ppid=35440:pid= 5402:c16 ENTER SQLFreeConnect
HDBC 0x3b0728b8
ppid=35440:pid= 5402:c16 EXIT SQLFreeConnect with return code 0 (SQL_SU
CCESS)
HDBC 0x3b0728b8
|
Sorry for huge message  [/code]
_________________
_________________
Best regards.
Yaakov Dolgov
E-Business Solutions Consultant
IBM Global Services, Israel
preiger.yaakov@il.ibm.com
Last edited by yaakovd_new on Tue Mar 23, 2004 10:16 pm; edited 1 time in total |
|
| Back to top |
|
 |
| bolek |
| Posted: Fri Mar 19, 2004 2:15 am Post subject: |
|
|
Apprentice
Joined: 25 Jul 2002
Posts: 35
Location: Germany
|
Hi,
I think you have two problems:
1. SQL1224N - for answer just go to www.ibm.com and enter "SQL1224N" in search bar 
Basically, you have to use EXTSHM=ON before starting DB2 and the broker and use IP loopback for your datasources.
2. BIP5902W - it seems that the message you try to parse includes some EBCDIC parts from mainframe and therefore can't be parsed by MRM parser correctly - you have to check your program logic... |
|
| Back to top |
|
|
| yaakovd_new |
| Posted: Mon Mar 22, 2004 5:49 am Post subject: |
|
|
Apprentice
Joined: 03 Feb 2004
Posts: 25
Location: Israel
|
Hi,
Thanks for your reply. I've set the EXTSHM=ON and one of MRM-s is working now.
1. I've eliminated EBCDIC issue using channel conversion on sender channel from Mainframe. Currently I recieve the message in readable format MQSTR + CCID 1208 etc.
2. I've removed the DB2 accsess in compute node.
My current flow looks as following - input node with simple MRM parser, where each character is an element (repited till end of stream); Compute node with OutRoot = InputRoot; MQ Output node.
And I still get the same error. 
Is there any known issues with:
1. The message length is 32 K ?
2. Broker DB (DB2) was created with CCID 1208 ?
Thanks for any help.
_________________
_________________
Best regards.
Yaakov Dolgov
E-Business Solutions Consultant
IBM Global Services, Israel
preiger.yaakov@il.ibm.com |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Mar 22, 2004 6:52 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| yaakovd_new wrote: |
1. I've eliminated EBCDIC issue using channel conversion on sender channel from Mainframe. Currently I recieve the message in readable format MQSTR + CCID 1208 etc.
|
Better to set Conversion on the MQInputNode.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| yaakovd_new |
| Posted: Mon Mar 22, 2004 10:57 pm Post subject: |
|
|
Apprentice
Joined: 03 Feb 2004
Posts: 25
Location: Israel
|
| Quote: |
| Better to set Conversion on the MQInputNode. |
Currently it is not an issue - I just tried to eliminate all possible problems.
Looks like I have a proble during access to broker DB.
| Quote: |
| [IBM][CLI Driver] SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032 |
in ODBC trace and MQSI log ...
_________________
_________________
Best regards.
Yaakov Dolgov
E-Business Solutions Consultant
IBM Global Services, Israel
preiger.yaakov@il.ibm.com |
|
| Back to top |
|
|
| pakya |
| Posted: Mon Mar 22, 2004 11:05 pm Post subject: Re: Urgent! Strange rumtime problem in WMQI |
|
|
Novice
Joined: 22 Mar 2004
Posts: 14
|
Please check the DSN which you have created using IBM DB2 Driver . Delete The DSN Configuration & recreated it The Problem will be solved  |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Mar 22, 2004 11:34 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Yaakov,
This could also mean that you are having serious Database problems. Check whether your database is available or not. Try to logon using DB2 command window.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| yaakovd_new |
| Posted: Tue Mar 23, 2004 3:23 am Post subject: |
|
|
Apprentice
Joined: 03 Feb 2004
Posts: 25
Location: Israel
|
Thanks,
What is really - output parsing and insert into application DB2 table alwyas working properly.
Input MRM-s are not working.
When I just add DB source to compute node (without real select) - the operation failed.
And allways the same error.
| Quote: |
*********************
**** dbdiag.log ****
*********************
2004-03-23-10.58.30.590049 Instance:db2 Node:000
PID:39744(DataFlowEngine) Appid:
oper_system_services sqlocshr2 Probe:200
0000 0018 ....
2004-03-23-10.58.30.727007 Instance:db2 Node:000
PID:39744(DataFlowEngine) Appid:
oper_system_services sqlocshr2 Probe:200
pSetHdl 303b 8000 303b 8000 0001 0000 0002 0045 0;..0;.........E
0004 0000 .... |
| Quote: |
Mar 22 12:39:41 rs31 WMQIv210[23958]: (RS31ND.TENA)[3114]BIP2322E: Database erro
r: SQL State '08001'; Native Error Code '-1224'; Error Text '[IBM][CLI Driver] S
QL1224N A database agent could not be started to service a request, or was term
inated as a result of a database system shutdown or a force command. SQLSTATE=5
5032: RS31ND.c557175d-fb00-0000-0080-a75abe7fe60f: /build/S210_P/src/DataFlowEng
ine/ImbOdbc.cpp: 255: ImbOdbcHandle::checkRcInner: :
Mar 22 12:39:42 rs31 WMQIv210[23958]: (RS31ND.TENA)[3114]BIP2232E: Error detecte
d whilst handling a previous error in node 'IEC_TENA_DH_FromNaturalREP_FL.IEC_IN
F_ErrorReplyXML_SFL.UnableGenerateReply'. : RS31ND.c557175d-fb00-0000-0080-a75ab
e7fe60f: /build/S210_P/src/DataFlowEngine/ImbDataFlowNode.cpp: 369: ImbDataFlowN
ode::logExceptionList: ComIbmComputeNode: 7bbb9bf2-fa00-0000-0080-a75abe7fe60f.6
18aaeea-f900-0000-0080-995db73969a9
Mar 22 12:39:42 rs31 WMQIv210[23958]: (RS31ND.TENA)[3114]BIP2230E: Error detecte
d whilst processing a message in node 'IEC_TENA_DH_FromNaturalREP_FL.IEC_INF_Err
orReplyXML_SFL.RevertReplyToQ'. : RS31ND.c557175d-fb00-0000-0080-a75abe7fe60f: /
build/S210_P/src/DataFlowEngine/ImbDataFlowNode.cpp: 536: ImbDataFlowNode::creat
eExceptionList: ComIbmComputeNode: 7bbb9bf2-fa00-0000-0080-a75abe7fe60f.a25c769d
-f900-0000-0080-995db73969a9
Mar 22 12:39:42 rs31 WMQIv210[23958]: (RS31ND.TENA)[3114]BIP2321E: Database erro
r: ODBC return code '-1'. : RS31ND.c557175d-fb00-0000-0080-a75abe7fe60f: /build/
S210_P/src/DataFlowEngine/ImbOdbc.cpp: 154: ImbOdbcHandle::checkRcInner: :
Mar 22 12:39:42 rs31 WMQIv210[23958]: (RS31ND.TENA)[3114]BIP2322E: Database erro
r: SQL State '08001'; Native Error Code '-1224'; Error Text '[IBM][CLI Driver] S
QL1224N A database agent could not be started to service a request, or was term
inated as a result of a database system shutdown or a force command. SQLSTATE=5
5032: RS31ND.c557175d-fb00-0000-0080-a75abe7fe60f: /build/S210_P/src/DataFlowEng
ine/ImbOdbc.cpp: 255: ImbOdbcHandle::checkRcInner: :
|
[/code]
_________________
_________________
Best regards.
Yaakov Dolgov
E-Business Solutions Consultant
IBM Global Services, Israel
preiger.yaakov@il.ibm.com |
|
| Back to top |
|
|
| mpuetz |
| Posted: Tue Mar 23, 2004 5:12 am Post subject: |
|
|
Centurion
Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services
|
Hi,
there is a limitation on AIX DB2 for the number
of direct connections to the database: You
can't have more than 8 direct connections to DB2
on AIX. Your broker may have already used up
the number of direct connections and fails to
open another one which would result in an
1224N code as well.
The default catalogization gives you direct connections.
There is a workaround where you catalog
your db2 instance as a TCPIP node and
catalog your database through that TCPIP node.
That way the broker connects DB2 using TCPIP
mode, which can handle an arbitrary number
of connections.
To check whether this is the case just enter
db2 list applications
as DB2 instance user and count the number of connections
to your database.
Anyway the above workaround is officially recommended
for broker installations on AIX.
_________________
Mathias Puetz
IBM/Central WebSphere Services
WebSphere Business Integration Specialist |
|
| Back to top |
|
|
| yaakovd_new |
| Posted: Tue Mar 23, 2004 10:15 pm Post subject: |
|
|
Apprentice
Joined: 03 Feb 2004
Posts: 25
Location: Israel
|
| mpuetz wrote: |
The default catalogization gives you direct connections.
There is a workaround where you catalog
your db2 instance as a TCPIP ... |
O-o-o !!! of course !!!
It was just mistake in our configuration procedure...
It is working now. Thanks!!!
_________________
_________________
Best regards.
Yaakov Dolgov
E-Business Solutions Consultant
IBM Global Services, Israel
preiger.yaakov@il.ibm.com |
|
| Back to top |
|
|
| fitzcaraldo |
| Posted: Tue Mar 30, 2004 3:17 pm Post subject: |
|
|
Voyager
Joined: 05 May 2003
Posts: 98
|
This is very interesting.
We had the same problem and this TCP/Local change has also fixed it.
But it raises a number of questions.
Is the 8 connection limit per Execution Group or broker wide?
And why does the broker need to access the database at runtime anyway? I have always assumed that all the required information is retrieved by the broker from the database at deployment time - why then it is going back to the database at runtime?
Any ideas? |
|
| Back to top |
|
|
| mpuetz |
| Posted: Mon Apr 05, 2004 2:43 pm Post subject: |
|
|
Centurion
Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services
|
Hi,
I believe the limitation is database wide, DB2 does not support more
than 8 direct connection on AIX in 32 bit mode.
The broker accesses the broker database all the time, not just
at startup time or after a deploy. The broker does some caching,
but it doesn't cache everything.
_________________
Mathias Puetz
IBM/Central WebSphere Services
WebSphere Business Integration Specialist |
|
| Back to top |
|
|
|
|
