| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| need help! - broker DB name got messed up in compute node |
« View previous topic :: View next topic » |
| Author |
Message
|
| pcelari |
 Posted: Wed Mar 26, 2008 10:56 am Post subject: need help! - broker DB name got messed up in compute node |
 |
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
I created a ROUTING_TABLE in my broker database MQSIBKDB which contains queue names for routing based on service name contained in incoming messages.
In the compute node, I populate the destination list based on a query to the database table. In the compute node properties, I specified database as MQSIBKDB. But when the flow hit the query command, I got the exception:
[IBM][CLI Driver][DB2/LINUX390] SQL0204N "WMBADM.ROUTING_TABLE" is an undefined name. SQLSTATE=42704
why does my database name got replaced with the username under which the broker is running?
Can an expert please point out what I missed?
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
 |
| JosephGramig |
| Posted: Wed Mar 26, 2008 11:47 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
It used the Service ID for the table schema. Try explicitly specifying the schema.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| sunny_30 |
| Posted: Wed Mar 26, 2008 3:22 pm Post subject: |
|
|
Master
Joined: 03 Oct 2005
Posts: 258
|
| Quote: |
| "I" created a ROUTING_TABLE |
Looks like 'you' were not WMBADM when the ROUTING_TABLE was created.
From ESQL try
| Quote: |
| MQSIBKDB."your-id".ROUTING_TABLE |
|
|
| Back to top |
|
|
| pcelari |
| Posted: Thu Mar 27, 2008 7:28 am Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
thanks for pointing that out, it did the trick.
Yes, I created the table as db2inst1. After I recreated the table as WMBADM, it works.
many thanks for the insight!
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| 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
|
|
|
|
