| Author |
Message
|
| abs_cal |
 Posted: Tue Aug 23, 2005 2:34 pm Post subject: BIP2599E: The ESQL deployed in node is invalid |
 |
|
Acolyte
Joined: 18 Aug 2005
Posts: 62
|
RecoverableException BIP2599E: The ESQL deployed to the node 'RivFlow.Compute' is invalid. This errors are getting using mqsichangetrace.
I have created one DSN for user DB in DB2 as local database. I have added this DSN in compute Node. In compute node i will suppose to access one table. Because of this DSN, control doesn't enter into the compute node and throwing the above error.
My WBIMB is installed as Plugin with WSAD.
Anybody has any solutions for this. Earlier I did so many times db access using DSN but i never find this kind of error.
It may happen that i am working in BROKER with different userid/passwd. How do i give access to this user for Db call from compute node.
Thanks |
|
| Back to top |
|
 |
| vennela |
| Posted: Tue Aug 23, 2005 3:01 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Try posting in WMQI/WBIMB forum next time. |
|
| Back to top |
|
|
| abs_cal |
| Posted: Tue Aug 23, 2005 3:02 pm Post subject: Userid and Passwd set during DB call from Coputenode |
|
|
Acolyte
Joined: 18 Aug 2005
Posts: 62
|
I am logged in with my own userid/passwd but DB needs to have different Userid/passwd during DB call from Compute Node.
how this can be set during DB2 call inside compute node?
Thankx |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Tue Aug 23, 2005 8:51 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
mqsisetdbparms BrokerName -n DataSourceName [ -u DataSourceUserId ] -p DataSourcePassword
I guess u have set the DSN for the database already....
But your error seems to be the one when the compute node references the wrong ESQL module....Go to the Compute node properties and check if the "ESQL Module" mentioned is correct. |
|
| Back to top |
|
|
| deeps1281 |
| Posted: Wed Aug 31, 2005 11:28 pm Post subject: |
|
|
Apprentice
Joined: 31 Aug 2005
Posts: 29
|
Hi
Please let me know if you have resolved your problem |
|
| Back to top |
|
|
| maxis |
| Posted: Fri Nov 11, 2005 3:22 am Post subject: bipv500 |
|
|
Centurion
Joined: 25 Jun 2002
Posts: 144
|
On wbi-mb 5, successfully compiled, deployed and tested on windows xp (both config mgr and broker on the same m/c). When I moved the same, code message flow and respective esql, to test m/c (broker on unix) its giving
| Code: |
| The ESQL deployed to the node is invalid |
Later tried with bar file .. still the same error 
any suggestion .... |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Fri Nov 11, 2005 3:31 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
ESQL deployed is invalid means that the compute node is referencing the wrong compute module(Code).......
Right click the compute Node--> Properties--> ESQL Module--> Browse--> Select your module
Hope it works.
Regards. |
|
| Back to top |
|
|
| maxis |
| Posted: Fri Nov 11, 2005 4:11 am Post subject: |
|
|
Centurion
Joined: 25 Jun 2002
Posts: 144
|
| its working in development environment ... when its moved, as it is, to test environment its giving problem ... |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Fri Nov 11, 2005 8:58 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
U mean you have moved only the Bar file to the Test environment.....??
Are you using the same directory structure in Dev and Test.....if the directory in test is longer than Dev then the ESQL file might not be getting deployed....Import the files in Test and Create the Bar there and Deploy....see if any Errors or warnings are being thrown.
Regards. |
|
| Back to top |
|
|
| mayur2378 |
| Posted: Sun Nov 13, 2005 8:59 am Post subject: |
|
|
Apprentice
Joined: 26 May 2004
Posts: 47
|
Do u use the same DSN in DEV as in TEST ?
Seems like there is a problem with the DSN that ur using. |
|
| Back to top |
|
|
| sknrt1 |
| Posted: Tue Nov 15, 2005 7:58 am Post subject: |
|
|
Apprentice
Joined: 22 Jan 2003
Posts: 39
Location: USA
|
If you are still seeing the error "The ESQL deployed to the node is invalid", sometimes its misleading.
ie: the actual error would have been different
So, try deploying your code again and run a msg through, look at the errors for the first msg only, becoz from the second msg onwards, u will get above error.
I have had this problem, though the problem was related to DSN configuration.
Refer to the topic posted earlier, which explains, about this broker behaviour
http://www.mqseries.net/phpBB2/viewtopic.php?t=17703&highlight=esql+deployed+node+invalid |
|
| Back to top |
|
|
| rajesh.palled |
| Posted: Wed Nov 16, 2005 1:58 am Post subject: |
|
|
Apprentice
Joined: 16 Feb 2004
Posts: 30
Location: New Jersey
|
I too faces this problem many times and sometime i was having ESQL error which WBIMB editor doesnt show up when you compile. SO you can have a quick look at the ESQL.
One more thing is you may have to import the database files to the project file in WBIMB toolkit. Go to Data Persective and specify the Database Connection name, Database Name, userid/pwd, Driver. After that you can see your database table in Data Perspective panel of WBI MB Toolkit. You can right click & import the table definition to your project. Then deploy & try to your flows again.
Another possibility would be when you move from one environment to another environment you may have give the set the DB user id password to the broker so that broker can access those tables without any problems.
Let me know if you have solved this issue or not.
Thanks
Rajesh |
|
| Back to top |
|
|
|
|
