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 » General Discussion » Unable to Connecting broker with Default Database

Post new topic  Reply to topic
 Unable to Connecting broker with Default Database « View previous topic :: View next topic » 
Author Message
Kup1228
PostPosted: Mon Aug 31, 2009 5:07 am    Post subject: Unable to Connecting broker with Default Database Reply with quote

Newbie

Joined: 28 Aug 2009
Posts: 1
Hi All,

Please help me.

When i trying to creating broker with default configuration wizard or mqsi command console that time i am getting problem.

Enviornment: DB29.1,MQ7.0,MB6.1


Log details:


Aug 31, 2009 4:02:55 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO:
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Mon Aug 31 16:02:55 IST 2009]

Aug 31, 2009 4:02:55 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO: Checking for the Default Configuration
Aug 31, 2009 4:02:55 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO: The above task succeeded

Collected output from task >
Stdout: [MQSI 6.1.0.3
C:\Program Files\IBM\MQSI\6.1

BIP8071I: Successful command completion.]

Stderr: []
Aug 31, 2009 4:02:57 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO:
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Mon Aug 31 16:02:57 IST 2009]

Aug 31, 2009 4:02:57 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO: Checking for the Default Configuration
Aug 31, 2009 4:02:57 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO: The above task succeeded

Collected output from task >
Stdout: [MQSI 6.1.0.3
C:\Program Files\IBM\MQSI\6.1

BIP8071I: Successful command completion.]

Stderr: []
Aug 31, 2009 4:03:19 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO:
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Mon Aug 31 16:03:19 IST 2009]

Aug 31, 2009 4:03:19 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO: Verifying that the default queue manager [WBRK61_DEFAULT_QUEUE_MANAGER] does not already exist.
Aug 31, 2009 4:03:19 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO: The above task succeeded

Collected output from task >
Stdout: [QMNAME(QM_Kuppil6318_G09) STATUS(Running)]

Stderr: []
Aug 31, 2009 4:03:21 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO:
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Mon Aug 31 16:03:21 IST 2009]

Aug 31, 2009 4:03:21 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO: Verifying that the default broker [WBRK61_DEFAULT_BROKER] does not already exist.
Aug 31, 2009 4:03:21 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
SEVERE: The default broker already exists.

Collected output from task >
Stdout: [MQSI 6.1.0.3
C:\Program Files\IBM\MQSI\6.1

BIP2393E: Database error: ODBC return code '-1' from data source ''DEFBKD61''.
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 ''IM002''; Native Error Code '0'; Error Text ''[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified''.
The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code '0' SQL Error Text ''[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified''
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.]

Stderr: []
Aug 31, 2009 4:03:39 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO:
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Mon Aug 31 16:03:39 IST 2009]

Aug 31, 2009 4:03:39 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO: Verifying that the default broker [WBRK61_DEFAULT_BROKER] does not already exist.
Aug 31, 2009 4:03:40 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
SEVERE: The default broker already exists.

Collected output from task >
Stdout: [MQSI 6.1.0.3
C:\Program Files\IBM\MQSI\6.1

BIP2393E: Database error: ODBC return code '-1' from data source ''DEFBKD61''.
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 ''IM002''; Native Error Code '0'; Error Text ''[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified''.
The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code '0' SQL Error Text ''[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified''
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.]

Stderr: []
Aug 31, 2009 4:03:47 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO:
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Mon Aug 31 16:03:47 IST 2009]

Aug 31, 2009 4:03:47 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
INFO: Verifying that the default broker [WBRK61_DEFAULT_BROKER] does not already exist.
Aug 31, 2009 4:03:47 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction
SEVERE: The default broker already exists.

Collected output from task >
Stdout: [MQSI 6.1.0.3
C:\Program Files\IBM\MQSI\6.1

BIP2393E: Database error: ODBC return code '-1' from The broker received an error when executing a database operation.data source ''DEFBKD61''.
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 ''IM002''; Native Error Code '0'; Error Text ''[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified''.
The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code '0' SQL Error Text ''[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified''
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.]

Stderr: []
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Aug 31, 2009 5:14 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
So you got this problem, you looked at the error messages and you did what to resolve them? Aside from posting the entire log here?

It also looks a bit like you've been repeatedly running and running the wizard in the hope it will work if you keep trying enough. Some clearing up might help.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Ratan
PostPosted: Tue Sep 01, 2009 1:51 am    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245
Create the database and ODBC datasource
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
ranganathan
PostPosted: Tue Sep 01, 2009 2:55 am    Post subject: Reply with quote

Centurion

Joined: 03 Jul 2008
Posts: 104
Kup1228 wrote:
trying to creating broker with default configuration wizard
.

From Infocenter
Quote:


Before you run the Default Configuration wizard:

* Windows platform You must have Administrator privileges on Windows, and your user ID must be a local ID (not a domain ID).
* A database must be available, and your user ID must be authorized to create databases:
o Linux platform On Linux on x86, install DB2® Enterprise Server.
o Windows platform On Windows, install either DB2 Enterprise Server or the ODBC Drivers for Cloudscape® (to use the embedded Derby database).



Did you face any issues in the above steps ?!

I suppose you have already created a broker

Quote:
SEVERE: The default broker already exists


Fix the Datasource issue and try again...
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 » General Discussion » Unable to Connecting broker with Default Database
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.