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 » Broker Unable to connect DB

Post new topic  Reply to topic
 Broker Unable to connect DB « View previous topic :: View next topic » 
Author Message
dashsatya
PostPosted: Wed Jun 13, 2007 5:28 am    Post subject: Broker Unable to connect DB Reply with quote

Novice

Joined: 24 Mar 2006
Posts: 17
Location: INDIA
Hi

I have message broker running on solaris and the DB Oracle is running on Windows server. Previously i had installed oracle client on solaris and had configured the tnsnames.ora file properly to access the Oracle Database on windows server so the things were running properly.

The oracle client have been uninstalled by the unix administrator and the oracle server is installed on some different directory of the same box. I have configured again the tnsname.ora file under the new installation to access the Oracle database running on windows server. i could able to connect manually to the DB by using sqlplus <user id >/<passwd> @ <Database name>.
(The user id and passwd is the user id and passwd provided with -u <userid > and -p< passwd >at the time of broker creation ).

But when ever i tried to stop the broker or issuing the command mqsilist <broker name > the following error i got.








mqsistop -i REGTEST2_BK
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.

BIP8071I: Successful command completion.



-------------------------------------------------------------------


mqsilist REGTEST2_BK
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.




any help in this regard will be highly appereciated.

Thanks in advance.
Back to top
View user's profile Send private message AIM Address
jefflowrey
PostPosted: Wed Jun 13, 2007 5:32 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
You need to redo all the setup for connecting to a database from Broker. Or get the unix administrator to establish symbolic links from the NEW client installation to the same location as the OLD client installation.

The fact that your unix administrator did this major change to your broker environment without working with you so that you were properly prepared and knew exactly what changes you needed to make to support it is a very bad thing.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
dashsatya
PostPosted: Thu Jun 14, 2007 4:12 am    Post subject: Reply with quote

Novice

Joined: 24 Mar 2006
Posts: 17
Location: INDIA
Hi Jeff
Thanks a lot for your valuable suggestion.

I have created a soft link of the newly installed oracle home to the old oracle home directory. still i am facing the same problem.
The oracle installation is done in this box with some different userid (a user id different from broker service user id).

Is it required to install the oracle with the broker service user id ?? or is the brioker service user id should be having some special privelege ......??
Back to top
View user's profile Send private message AIM Address
jefflowrey
PostPosted: Thu Jun 14, 2007 6:50 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
I was guessing that the softlinks would work, I guess not.

You need to basically redo everything that you did the first time you set up Broker to connect to this database.
_________________
I am *not* the model of the modern major general.
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 » Broker Unable to connect DB
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.