| Author |
Message
|
| prk |
 Posted: Fri Jan 18, 2008 7:02 am Post subject: Broker creation error with Message Broker 6.1 |
 |
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
Environment is Windows XP where I have the Message Broker 6.1 runtime and the toolkit installed. Have an oracle client on the XP and the actual database is on the UNIX server. I ran the mqsiprofile and am also able to connect to the database from the same command window using sqlplus. But when I try to create the broker I get a database error.
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 ''IM002''; Native Error Code '0'; Error Text
''[Microsoft][ODBC Driver Manager] Data source name not found and no default dr
iver specified''.
The error has the following diagnostic information: SQL State ''
IM002'' SQL Native Error Code '0' SQL Error Text ''[Microsoft][OD
BC 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 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 hasbeen 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.
Any ideas how this issue can be resolved ? |
|
| Back to top |
|
 |
| leo> |
| Posted: Fri Jan 18, 2008 7:06 am Post subject: |
|
|
Apprentice
Joined: 06 Oct 2004
Posts: 42
|
Have you created the ODBC reference for the broker database? You would need to register the broker database under system dsn..
_________________
IBM Certified System Administrator - Websphere MQ V5.3 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jan 18, 2008 7:06 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You didn't specify the right ODBC driver when you created the ODBC DSN, or you specified the wrong name for the ODBC DSN on mqsicreatebroker.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 18, 2008 7:09 am Post subject: Re: Broker creation error with Message Broker 6.1 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| prk wrote: |
| Any ideas how this issue can be resolved ? |
Well,
| prk wrote: |
- 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 hasbeen 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.
|
What were the results of your check?
Also
| prk wrote: |
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''.
|
I'd recheck the ODBC name supplied to the broker and the ODBC itself as a first move.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| prk |
| Posted: Fri Jan 18, 2008 7:15 am Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
| The Broker database is defined in the tnsnames.ora file on the Windows XP machine. I can do sqlplus into the database with the same username and password that I am providing to create the Broker. I also ran the mqsiprofile. How can I check the ODBC DSN ? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jan 18, 2008 7:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
tnsnames.ora is not sufficient.
You must also create an ODBC data source. As per the documentation.
Your windows System Administrator or DBA can help you create an ODBC data source.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| prk |
| Posted: Fri Jan 18, 2008 8:38 am Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
| Thanks Jefflowrey, I created the ODBC data source and its working now. Thanks for your help. |
|
| Back to top |
|
|
|
|
