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 » Unable to create broker (SOLVED)

Post new topic  Reply to topic
 Unable to create broker (SOLVED) « View previous topic :: View next topic » 
Author Message
venkat126
PostPosted: Sun Sep 19, 2010 9:19 am    Post subject: Unable to create broker (SOLVED) Reply with quote

Novice

Joined: 23 Aug 2010
Posts: 22

WMB v6.1
I created a new config manager in zlinux. I’m trying to create a new broker and corresponding queue manager. The broker database was created on a remote system. It’s a DB2 database.

Assuming broker name is BRK1, its QM name is BRK1QM, its DB name is BRK1DB.

I added the following info to the odbc64.ini file.

[BRK1DB]
DRIVER=libdb2Wrapper.so
Description=DB2DB DB2 ODBC Database
Database=BRK1DB

I connected to the remote db2 box from my DB2 Client and checked for the BRK1DB database. It does exist. Yet, I get the following error when I run the mqsicreatebroker command.

ediwmb@ediwtxqa1:/> mqsicreatebroker BRK1DB -i <un> -a <pw> -q BRK1QM -n BRK1DB -u <un> -p <pw>

AMQ8110: WebSphere MQ queue manager already exists.
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.
BIP2393E: Database error: ODBC return code '-1' from data source ''BRKCDBQ''.

The broker received an error when executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database about this error.

Use the following messages to determine the cause of the error. Typical causes are incorrect data source or table names. Correct either the database or the broker configuration.

BIP2322E: Database error: SQL State ''08001''; Native Error Code '-1013'; Error Text ''[IBM][CLI Driver] SQL1013N The database alias name or database name "BRKCDBQ" could not be found. SQLSTATE=42705 ''.

The error has the following diagnostic information: SQL State ''08001'' SQL Native Error Code '-1013' SQL Error Text ''[IBM][CLI Driver] SQL1013N The database alias name or database name "BRKCDBQ" could not be found. SQLSTATE=42705 ''

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 specified user Id and password pair.

- Check that the database is running.

- On Windows, check that an ODBC connection has been created.

- On systems that use $ODBCINI, check that the file pointed to by $ODBCINI has been correctly updated.

- Use mqsichangebroker brokername -a xxx to set the password to the correct value and try again.

Use mqsichangeconfigmgr configmgr -a xxx to set the password to the correct value and try again.

- Check that the database has an adequate number of database connections available for use.


Is there any step that I’m missing here?
In case anyone is about to suggest mqsisetdbparms, I already tried executing this step, but obviously, it said, object not found (I'm guessing because the broker wasn't created).


Last edited by venkat126 on Mon Sep 20, 2010 9:23 am; edited 1 time in total
Back to top
View user's profile Send private message
mvarghese
PostPosted: Sun Sep 19, 2010 9:45 am    Post subject: Reply with quote

Centurion

Joined: 27 Sep 2006
Posts: 141

seems like u mention wrong "DRIVER=libdb2Wrapper " directory location.
Correct with right driver location, u can find out from the db2 client u installed on Broker server.
_________________
Jain Varghese
Back to top
View user's profile Send private message
venkat126
PostPosted: Mon Sep 20, 2010 7:52 am    Post subject: Reply with quote

Novice

Joined: 23 Aug 2010
Posts: 22

mvarghese wrote:
seems like u mention wrong "DRIVER=libdb2Wrapper " directory location.
Correct with right driver location, u can find out from the db2 client u installed on Broker server.


I have two other brokers and broker databases setup with the exact same configuration on the same system. I created the new stanza in the odbc64.ini file with reference to the stanzas for the existing brokers.
Back to top
View user's profile Send private message
venkat126
PostPosted: Mon Sep 20, 2010 8:03 am    Post subject: Reply with quote

Novice

Joined: 23 Aug 2010
Posts: 22

I also added "BRK1DB=IBM DB2 ODBC Driver" to the "List of Data Sources Stanza". Even that didn't help.
I wish to point out that other broker databases in my environment have not been listed in the "List of Data Sources Stanza".
Back to top
View user's profile Send private message
mqjeff
PostPosted: Mon Sep 20, 2010 8:11 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Did you catalog the remote database into the local DB2 client instance?
Back to top
View user's profile Send private message
venkat126
PostPosted: Mon Sep 20, 2010 9:19 am    Post subject: Reply with quote

Novice

Joined: 23 Aug 2010
Posts: 22

mqjeff wrote:
Did you catalog the remote database into the local DB2 client instance?


Thanks a ton mqjeff. That was it! I gave your suggestion to my DBA and that solved the issue. I was able to create my broker.

Thanks again.
Back to top
View user's profile Send private message
venkat126
PostPosted: Mon Sep 20, 2010 9:24 am    Post subject: Reply with quote

Novice

Joined: 23 Aug 2010
Posts: 22

I just added (SOLVED) to the title of my first post. Is that sufficient or do I have to do anything else to mark this question resolved?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Sep 20, 2010 9:29 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

venkat126 wrote:
I just added (SOLVED) to the title of my first post. Is that sufficient or do I have to do anything else to mark this question resolved?

That's fine
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Unable to create broker (SOLVED)
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.