| Author |
Message
|
| kpvin |
 Posted: Wed Mar 03, 2004 12:45 am Post subject: Problems with message flow deployment in WBIMB |
 |
|
Novice
Joined: 02 Jan 2004
Posts: 17
|
Hi,
I have WBIMB 5.0 installed talking to Oracle Database. WebSphere MQ 5.3 I had created all the required MQ Objects with respect to Message Flow.
I had successfully deployed message flow (execution group:db2admin). Message Flow Debug shows the message insertion in to the DataInsert node and MQOutput node. When I query database (Oracle) with select cmd for nos of rows inserted [select count(*) from table;] its giving the nos of rows inserted. But when I query for inserted data [select * from table;] its showing blank records in the table.
Could anyone help me in solving this problem please.
Thanks in advance. |
|
| Back to top |
|
 |
| wooda |
| Posted: Wed Mar 03, 2004 2:50 am Post subject: |
|
|
Master
Joined: 21 Nov 2003
Posts: 265
Location: UK
|
hi rekha -
Please supply a trace of your message tree ${Root} before the DataInsert node and also details of the mappings you have used in the datainsert node. |
|
| Back to top |
|
|
| Deeko |
| Posted: Wed Mar 03, 2004 3:30 am Post subject: |
|
|
Acolyte
Joined: 16 May 2001
Posts: 72
Location: Edinburgh, UK
|
Rekha,
I have a problem similar to this with UDB. Basically it is as if the broker wasn't committing the DB updates due to a failure in the flow. Try doing a 'select * from table with ur' (or whatever the oracle equivalent is for uncommitted read). If that shows the records then there may be something similarly wrong with your messageflow.
My problem is that it's reporting that I have invalid EQSL in my compute node. This is a bit strange as the flow was working OK and it suddenly stopped working. A redeploy of the same code fixes the problem for a while.
I have a PMR open for this but I'm having problems replicating it due to another problem with security failures (using mqsisetdbparms).
For info the failure I have in my event log is:
| Quote: |
BIP2599E: The ESQL deployed to the node 'MJI_IA_Logger_1.Insert . Update
IA Record' is invalid.
The message could not be processed because the ESQL deployed
to the node is invalid. Examine previous error me
ssages for details of the problem.
Correct the logic of the ESQL program and re-deploy the
message flow.
|
Regards,
Derek. |
|
| Back to top |
|
|
| Paul D |
| Posted: Tue Mar 09, 2004 8:06 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
Derek,
We meet again. We must be doing the same testing on the same platforms. I have the same problem with mqsisetdbparms (AIX broker). I'm getting the same ESQL error with UDB. I'm trying a simple SQL statement like this to test:
| Code: |
| SET InputLocalEnvironment.tabledata[] = (SELECT ITEM C.tabname FROM Database.syscat.tables as C); |
Of which it works when pointing to the Broker DB and using the mqsi ID (i.e. no mqsisetdbparms in effect). I get the:
| Code: |
BIP2322E: Database error: SQL State '08001'; Native Error Code '-30082'; Error Text
'[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with security reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTAT
E=08001 |
error the first time through, then get the ESQL error you get other times after that. I've also got a case open in this. Did you get any resolution back on this yet?
_________________
Thanks!!!
Paul D |
|
| Back to top |
|
|
| Deeko |
| Posted: Tue Mar 09, 2004 12:16 pm Post subject: |
|
|
Acolyte
Joined: 16 May 2001
Posts: 72
Location: Edinburgh, UK
|
Hi Paul,
Yeah....I'm going through the lengthy process of making sure all our WMQI 2.1 resources function OK on WBIMB 5.0.2! Some of the new features make our life easier so I've been trying to utilise them as well (with varying degrees of success I may add).
I raised a PMR for a related issue to this where my deployed ESQL suddenly became corrupt and a redeploy fixed it. However, it became really hard to replicate the problem as I was using mqsisetdbparms on my Win NT test box to override the userid/password for DB2Connect and it stopped working. IBM have confirmed that there are problems with mqsisetdbparms in CSD2 which will be fixed in CSD3 and they've supplied me with the fix (for Windows only). Apparently there's problems with the broker picking up values from the registry (I should maybe try it on our new AIX test broker but I've not got round to it yet).
I haven't tried this yet but will do so tomorrow (it's 20:15 in the UK and I'm at home)....if it works I'll email it to you!  I'll keep you updated!
Regards,
Derek. |
|
| Back to top |
|
|
| Paul D |
| Posted: Tue Mar 09, 2004 12:39 pm Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
Derek,
I just got word back from IBM. They told me that passwords 12 and longer has issues, certainly on AIX, and maybe other UNIX platforms. I actually got mine shortened to 8 so I'm ok with this issue now. My message flow is working repeatedly without issue so it appears the ESQL error and the User ID/Password error were all caused by this same issue. Good luck with the rest of your testing.
- Paul
_________________
Thanks!!!
Paul D |
|
| Back to top |
|
|
| Deeko |
| Posted: Tue Mar 09, 2004 1:08 pm Post subject: |
|
|
Acolyte
Joined: 16 May 2001
Posts: 72
Location: Edinburgh, UK
|
Eep! My password was only ever 6 chars! Oh well, see what happens when I install the fix!!!
Regards,
Derek. |
|
| Back to top |
|
|
| BineBlue |
| Posted: Thu Apr 01, 2004 1:35 pm Post subject: |
|
|
Novice
Joined: 12 Nov 2003
Posts: 17
|
Hi guys,
that is a very interesting discussion, I am working with WBI MB V5.0 and CSD03 and try to connect to a Oracle Database. As you guys,I made a simple flow with a SELECT COUNT(*) statement and get in my trace the same Error, you get : ESQL deployed to the node is invalid
After I mad a redeploy it works for a while and then I allways get a connection Error, it says my dirver is invalid.
If would be nice, if you inform me, if you get the problem fixed.
Thanks
Sabine |
|
| Back to top |
|
|
| Paul D |
| Posted: Fri Apr 02, 2004 6:04 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
All I can add is that my issue was a password length problem. I think you want to open a case with IBM on your problem. I was using DB2 and not oracle in my case also. Good Luck!
_________________
Thanks!!!
Paul D |
|
| Back to top |
|
|
| Deeko |
| Posted: Fri Apr 02, 2004 7:40 am Post subject: |
|
|
Acolyte
Joined: 16 May 2001
Posts: 72
Location: Edinburgh, UK
|
I think my problem was also related to the password length and mqsisetdbparms. I've not had any bother with Oracle as of yet!
Regards,
Derek. |
|
| Back to top |
|
|
|
|
