| Author |
Message
|
| chbushan |
 Posted: Wed Feb 27, 2013 12:28 pm Post subject: WMB V 7.0.0.2 connecting to SQL Server 2008 |
 |
|
Novice
Joined: 18 Jan 2005
Posts: 11
Location: United States
|
I'm trying to connect broker to sql server 2008 using ODBC connection.
I did go through most of the posts here but still not able to resolve the problem.
I'm using windows XP to connect to remote SQL Server.
I created System DSN and then executed the mqsisetdbparams.
But I see the below issue after executing mqsicvp.
I tried checking ODBC.INI files and other logs.
Please help me what can I check to fix this problem.
Thanks for for your help.
MQSI 7.0.0.2
C:\Program Files\IBM\MQSI\7.0
C:\Program Files\IBM\MQSI\7.0>mqsicvp MB7BROKER -n dsn::MYDSN
BIP2393E: Database error: ODBC return code '-1' from data source ''dsn::MYDSN''
using ODBC driver manager ''odbc32.dll''.
The broker received an error when processing a database operation. The ODBC retu
rn code was '-1'. See the following messages for information obtained from the d
atabase about this error.
Use the following messages to determine the cause of the error. Typical problems
are an incorrect data source, or table names. Correct either the database or th
e 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 m
essage broker itself. Use the reason identified in this message with the accomp
anying 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.
- Check that the database has an adequate number of database connections availa
ble for use.
- 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.
- On z/OS check the BIPDSNAO member of the component's dataset, and check the D
B2 64bit ODBC driver (DSNAO64C) is in the STEPLIB.
- Use mqsisetdbparms to set the password to the correct value and try again.
C:\Program Files\IBM\MQSI\7.0> |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Feb 27, 2013 12:58 pm Post subject: Re: WMB V 7.0.0.2 connecting to SQL Server 2008 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| chbushan wrote: |
| I created System DSN |
When you test that through Windows does it work?
Also 7.0.0.2 is below the recommended level. You should be on 7.0.0.3 at least; there are a lot of fixes you're missing and one of them could help you here.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mgk |
| Posted: Wed Feb 27, 2013 2:11 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
| Quote: |
| mqsicvp MB7BROKER -n dsn::MYDSN |
Unless you DSN really is called "dsn::MYDSN", try using
| Code: |
| mqsicvp MB7BROKER -n MYDSN |
Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| chbushan |
| Posted: Wed Feb 27, 2013 2:47 pm Post subject: |
|
|
Novice
Joined: 18 Jan 2005
Posts: 11
Location: United States
|
No Luck...
MQSI 7.0.0.2
C:\Program Files\IBM\MQSI\7.0
C:\Program Files\IBM\MQSI\7.0>mqsicvp MB7BROKER -n MYDSN
BIP8272E: Datasource 'MYDSN' has not been associated with broker 'MB7BROKER'.
This invocation of the mqsicvp command requires that the datasource name has bee
n associated with the broker, using the mqsisetdbparms command.
Check that this datasource has been associated with the broker.
C:\Program Files\IBM\MQSI\7.0> |
|
| Back to top |
|
|
| mgk |
| Posted: Wed Feb 27, 2013 3:44 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
This sounds like you have not run the mqsisetdbparms command to set the user id and password. Also you can pass these parameters directly to the mqsicvp command as well...
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
|
|
