ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Cannot create broker on 6.1 BIP2321E

Post new topic  Reply to topic
 Cannot create broker on 6.1 BIP2321E « View previous topic :: View next topic » 
Author Message
kevinobyrne
PostPosted: Tue May 20, 2008 4:08 am    Post subject: Cannot create broker on 6.1 BIP2321E Reply with quote

Voyager

Joined: 17 Jul 2007
Posts: 83
Location: Ireland

Hi All,
I originally had WMB 6.0 installed but I uninstalled it and installed 6.1, and now I'm trying to create a new broker. (Unix)

The command I'm running is:
mqsicreatebroker ESBUAT_BRKR -i mqbrk0 -a password1 -q ESBUAT -n broker_u -u mqbrk0 -p password2

The full error details:
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.
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.
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. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration.
BIP2322E: Database error: SQL State ''82''; Native Error Code '0'; Error Text ''523 80''.
The error has the following diagnostic information: SQL State ''82'' SQL Native Error Code '0' SQL Error Text ''523 80''
This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying 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 with the broker.
- Check that the database is running.
- On Windows check that an ODBC connection has been created.
- On systems which use $ODBCINI check that the file pointed to by $ODBCINI has been correctly updated.
- Check that the userid and password pair specified for ODBC connect on the mqsicreate or mqsichangebroker command are capable of being used to connect to the database using an ODBC connection.
- Check that the database has a adequate number of database connections available for use.


I have already created the QM and CM. The database is an oracle10 db running on a different machine. I have set up my .odbc.ini and tnsnames.ora and I can connect to broker_u using sqlplus. The database username and password are correct and have permission to create tables . Originally there was an mqbrk0 schema in the database, which was deleted, and a new one was created with no tables. I have run mqsi_setupdatabase.

I've read through all of the threads that mention anything like this here but I can't find any suggestions that work. It's extremely frustrating that the database error is "Database error: SQL State ''82''; Native Error Code '0'; Error Text ''523 80''.", there's not much to take from that.

Does anyone have any suggestions or solutions? I'm ready to provide any more information, thanks.
Back to top
View user's profile Send private message
kevinobyrne
PostPosted: Tue May 20, 2008 4:49 am    Post subject: Reply with quote

Voyager

Joined: 17 Jul 2007
Posts: 83
Location: Ireland

My .odbc.ini was incorrect
the

[ODBC]
...
InstallDir=....

was set to the directory in 6.0 (which no longer existed) instead of 6.1

Unfortunately I've still got a problem:

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.
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.
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. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely to 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 '0'; Error Text ''[DataDirect][ODBC lib] Specified driver could not be loaded''.
The error has the following diagnostic information: SQL State ''IM003'' SQL Native Error Code '0' SQL Error Text ''[DataDirect][ODBC lib] Specified driver could not be loaded''

This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying 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 with the broker.
- Check that the database is running.
- On Windows check that an ODBC connection has been created.
- On systems which use $ODBCINI check that the file pointed to by $ODBCINI has been correctly updated.
- Check that the userid and password pair specified for ODBC connect on the mqsicreate or mqsichangebroker command are capable of being used to connect to the database using an ODBC connection.
- Check that the database has a adequate number of database connections available for use.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Cannot create broker on 6.1 BIP2321E
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.