| Author |
Message
|
| Kjell |
 Posted: Wed Dec 01, 2004 3:07 am Post subject: ODBC Data sources |
 |
|
Acolyte
Joined: 26 Feb 2002
Posts: 73
|
Hi
We have installed 2 brokers in the same machine , an AIX.
One broker for the development environment, and one for the test environment.
We have developed a flow that inserts records into an Oracle DB, via a Database node. For both brokers (dev + test) we want to use the same Oracle instance and the same schema. So, we have ONE datasource name that we use in this node.
Our problem is that it works perfectly from the DEV broker, but from the TEST one it does not work. We get an error , like "sql error in creating object" or similar.
Does anyone recognise this problem? Is it at all possible to use the same datasource from 2 different brokers, or do we need to create 2 Datasources, and thus remeber to change the property on the bar file when we move from dev to test? |
|
| Back to top |
|
 |
| rajmq |
| Posted: Wed Dec 01, 2004 6:34 am Post subject: |
|
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
Hi Jell,
My First Question,
Why do you need two broker for access single db??
You can achive this using the single broker !!
What is the sql error details ??..did you enabled the trace ?? or post sys log error's
Cheers,
RJ |
|
| Back to top |
|
|
| JT |
| Posted: Wed Dec 01, 2004 6:41 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
Shouldn't be a problem as we do something very similar. We have multiple brokers (Solaris) running simultaneously on the same server. Each broker contains the same message flows that are accessing the same Data Source (Oracle). We do this to load-balance the messages in the development environment.
What happens if you shutdown the DEV broker so that the TEST broker is the only one running. Does it work?
What is the exact error message? |
|
| Back to top |
|
|
| Kjell |
| Posted: Fri Dec 03, 2004 12:51 am Post subject: |
|
|
Acolyte
Joined: 26 Feb 2002
Posts: 73
|
The error message is obtained from the Exception list in the message, when I run the Flow debugger. It says "The ESQL code generated is invalid", pointing at the database node as to where the SQL stmt is. I do not remember the exact error numbers and so on, since I am on an other assignment at the moment. When I go thru the code step by step the debugger stops at the SQL Insert stmt and backs out.
I will try to shut down the DEV broker and run the TEST only, next time I am working on the task (it will be in 2 weeks). |
|
| Back to top |
|
|
| Kjell |
| Posted: Thu Dec 09, 2004 2:50 am Post subject: |
|
|
Acolyte
Joined: 26 Feb 2002
Posts: 73
|
I get the following error message:
BIP2599: "The ESQL deployed to the node is invalid"
How can the code be "valid" in DEV , but "invalid" in TEST?
Anyone? |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Dec 09, 2004 9:51 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| How can the code be "valid" in DEV , but "invalid" in TEST? |
Different CSD levels?
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Kjell |
| Posted: Thu Dec 09, 2004 11:38 pm Post subject: |
|
|
Acolyte
Joined: 26 Feb 2002
Posts: 73
|
No,
Both DEV and TEST are on the same machine, create in the same WBIMB installation. |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Dec 09, 2004 11:42 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
I am using the same DSN for 2 brokers on Windows platform and it's working very well.
_________________
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 |
|
|
| JT |
| Posted: Fri Dec 10, 2004 11:39 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
If you're deploying the exact same code to both brokers, then it sounds like an environmental discrepancy.
For instance, verify that the same database id & password were assigned, via mqsisetdbparms, to the data source for each of the brokers. |
|
| Back to top |
|
|
| Kjell |
| Posted: Mon Dec 13, 2004 11:23 am Post subject: |
|
|
Acolyte
Joined: 26 Feb 2002
Posts: 73
|
Solved
I had forgotten to stop the broker before doing the mqsisetdbparms.
All OK now. |
|
| Back to top |
|
|
|
|
