Author |
Message
|
Chander Mohan |
Posted: Tue Feb 20, 2007 7:24 am Post subject: Getting error while creating Broker |
|
|
Novice
Joined: 16 Feb 2007 Posts: 22
|
Hi,
I am using MQ 5.3 , Message broker toolkit 5.0.6 and IBM DB2 8.1.
I loged on as cmmqm and while installing DB2 and WMBI i assigned cmmqm id and now id(cmmqm) is part of mqm,administrator,db2admin, and 5 groups of broker.I created System DSN and associate database BRKDB with DSN.
I created two database in DB2 for broker(BRKDB) configmgr(CONFMGDB) .
I created configmgr (mqsicreateconfigmgr -i cmmqm -a mqm -q CONF_QM -n CONFMGDB -u cmmqm -p mqm)
While giving this command to create broker(mqsicreatebroker WBRK_BROKER -i cmmqm -a mqm -q WBRK_QM -n BRKDB -u cmmqm -p mqm) I am getting error enclosing below.
BIP2321E , BIP2322E , BIP8040E
Please help me  |
|
Back to top |
|
 |
vennela |
Posted: Tue Feb 20, 2007 7:33 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Posting the detailed error message would help |
|
Back to top |
|
 |
Chander Mohan |
Posted: Tue Feb 20, 2007 10:26 am Post subject: |
|
|
Novice
Joined: 16 Feb 2007 Posts: 22
|
Here i am enclosing an error.
BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. T
he ODBC return code was '-1'. See the following messages for information obtaine
d from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely t
o be such things as incorrect datasource or table names. Then correct either the
database or message broker configuration.
BIP2322E: Database error: SQL State 'IM002'; Native Error Code '0'; Error Text '
[Microsoft][ODBC Driver Manager] Data source name not found and no default drive
r specified'.
The error has the following diagnostic information: SQL State 'I
M002' SQL Native Error Code '0' SQL Error Text '[Microsoft][ODBC
Driver Manager] Data source name not found and no default driver specified'
This message may be accompanied by other messages describing the effect on the m
essage broker itself. Use the reason identified in this message with the accomp
anying messages to determine the cause of the error.
BIP8040E: Unable to connect to the database.
The database cannot be accessed with the userid and password that were specified
when the broker was created.
Check that the database is running, that an ODBC connection has been created and
that the userid and password pair specified for ODBC connect on the mqsicreate
command are capable of being used to connect to the database using an ODBC conne
ction. Also ensure that the database has a adequate number of database connectio
ns available for use. |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Feb 20, 2007 10:28 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You need to GRANT ALL for the broker user.
Being in db2admin doesn't automatically give you all priviledges to all databases. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Chander Mohan |
Posted: Tue Feb 20, 2007 10:34 am Post subject: |
|
|
Novice
Joined: 16 Feb 2007 Posts: 22
|
Could u elborate bit more how i can give this permission.
Thanks in advance |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Feb 20, 2007 10:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I'm sure it's clearly spelled out in the Info Center where it talks about connecting to databases. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Feb 21, 2007 12:36 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Chander Mohan wrote: |
Could u elborate bit more how i can give this permission. |
Make friends with your DB2 DBA, and show him the section in the Info Center. It's a database thing rather than an MQ one. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|