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 » WMB V60 and DB2 odbc error - please help

Post new topic  Reply to topic
 WMB V60 and DB2 odbc error - please help « View previous topic :: View next topic » 
Author Message
emileke
PostPosted: Wed Aug 01, 2007 6:26 am    Post subject: WMB V60 and DB2 odbc error - please help Reply with quote

Centurion

Joined: 19 Aug 2001
Posts: 110
Location: South Africa

mqsilist -a BROKERDEV
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 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 connection. Also ensure that the database has a adequate number of database connections available for use.
_________________
Emile M Kearns
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Aug 01, 2007 6:30 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

So have you checked you're using the right userid and password as indicated by the message text?

WHat other diagnostic activities have you perfomed? There's no pint us suggesting things which have already not helped.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Aug 01, 2007 6:31 am    Post subject: Re: WMB V60 and DB2 odbc error - please help Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

emileke wrote:
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 connection.

_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
emileke
PostPosted: Wed Aug 01, 2007 7:28 am    Post subject: Reply with quote

Centurion

Joined: 19 Aug 2001
Posts: 110
Location: South Africa

The userid and password can definately access the database, I do a db2 connect and it is succesful
_________________
Emile M Kearns
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Aug 01, 2007 7:30 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Did they change?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Aug 01, 2007 7:30 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

emileke wrote:
The userid and password can definately access the database, I do a db2 connect and it is succesful


Then you need to explore some of the other possible causes listed in the error message.

Having first assured yourself the userid you think is in use is indeed the one that's in use!
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
emileke
PostPosted: Wed Aug 01, 2007 7:45 am    Post subject: Reply with quote

Centurion

Joined: 19 Aug 2001
Posts: 110
Location: South Africa

What are steps to following when u think the service id password changed?
I can start the broker but when I tried issuing a "mqsilist -a BROKERNAME" and "mqsideletebroker -b BROKERNAME", then I get this error. It is a band new installation and I only started a month ago and I reckon that the service id password expired and was given a new one. I tried issuing"mqsichangebroker" to change the servicce userid and password and this was successful, not quite sure what to do next.
_________________
Emile M Kearns
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Aug 01, 2007 7:50 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

You need to also change the database password, likely.

mqsichangebroker -p
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
emileke
PostPosted: Wed Aug 01, 2007 8:00 am    Post subject: Reply with quote

Centurion

Joined: 19 Aug 2001
Posts: 110
Location: South Africa

Ok, thanks, I forgot to that.

One thing I neglected to say is that we run a 64 bit AIX machine and somehow my gut feeling says to me that the environment settings ain't correct but I not sure what it should be. The LIBPATH, etc.
_________________
Emile M Kearns
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Aug 01, 2007 8:20 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

You need to go through the section in the Info Center on configuring databases with a fine toothed comb, and check everything against what you've got set up.

There isn't really an easier way.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
emileke
PostPosted: Wed Aug 01, 2007 8:40 am    Post subject: Reply with quote

Centurion

Joined: 19 Aug 2001
Posts: 110
Location: South Africa

One last question, the -p option, would that be the same as the service id or would I have to check with the DBA's to ascertain the dbuser and dbpasswd that they used?
Thanks for the pointers
_________________
Emile M Kearns
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Aug 01, 2007 8:41 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

well, it might not be "-p". But yes, the password needed for the database.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Aug 01, 2007 2:49 pm    Post subject: Reply with quote

Grand High Poobah

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

And to be even more specific:

use mqsiservice to display the userid used by the broker to access its DB.
The password you need to update is the password for that user.

You may also ask your unix admin to set up "service accounts" i.e. the password never expires... The downside to this is that they will not allow you to login to the box with that userid you will have to su to it (security).
The advantage => no more password troubles for the broker / db, MQ, etc...

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
emileke
PostPosted: Thu Aug 02, 2007 4:08 am    Post subject: Reply with quote

Centurion

Joined: 19 Aug 2001
Posts: 110
Location: South Africa

SOLVED.

The LIBPATH was not set correctly.
_________________
Emile M Kearns
Back to top
View user's profile Send private message
emileke
PostPosted: Thu Aug 02, 2007 4:10 am    Post subject: WMB V60 and DB2 odbc error - please help -SOLVED Reply with quote

Centurion

Joined: 19 Aug 2001
Posts: 110
Location: South Africa

Solved
_________________
Emile M Kearns
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 » WMB V60 and DB2 odbc error - please help
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.