| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AIX MQ5.3 WBIMB5.0 CreateBroker Problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| smallred |
 Posted: Thu Jan 27, 2005 2:47 am Post subject: AIX MQ5.3 WBIMB5.0 CreateBroker Problem |
 |
|
Newbie
Joined: 27 Jan 2005
Posts: 4
Location: china
|
hi,
We have a problem creating a broker in AIX env.
MQSeries 5.3(CSD08) and WBIMB(CSD04) DB2 8.1(FIX5)
we get are BIP 2321E, BIP 2322E and BIP8040E 
Scenario
AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager running.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
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 'IM003'; Native Error Code '80'; Error Text
'Specified driver could not be loaded'.
The error has the following diagnostic information: SQL State 'I
M003' SQL Native Error Code '80' SQL Error Text 'Specified driver
could not be loaded'
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.
the role,username and password is correct,what can i do?
thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Jan 27, 2005 5:21 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Have you confirmed that the datasource in question works properly?
Have you confirmed that you are using the right ODBC driver for WBIMB?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| smallred |
| Posted: Fri Jan 28, 2005 10:33 pm Post subject: |
|
|
Newbie
Joined: 27 Jan 2005
Posts: 4
Location: china
|
| my DB2 is 64bit,i migrate db2 instance to 32 bits, it work correctly. |
|
| Back to top |
|
|
| GYR |
| Posted: Mon Jan 31, 2005 2:25 pm Post subject: |
|
|
Acolyte
Joined: 23 Jan 2002
Posts: 72
|
|
| 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
|
|
|
|
