| Author |
Message
|
| BrokerBeginner |
 Posted: Fri Jul 11, 2014 2:17 pm Post subject: IBM DB2 with MB7 |
 |
|
Newbie
Joined: 11 Jul 2014
Posts: 4
|
Hi Guys ,
I am a complete newbie to MB . Looking for some of your expertise here.
Was trying out a proof of concept with the Database node . I have Oracle 11.2 edition installed on my system and the Broker version running is MB 7.0 .
After I have created a system DSN called ORACLEDBDSN , the test connection works fine in the ODBC System Administrator Window . However , I get the following error when I use the mqsicvp command .
mqsicvp MB7BROKER -n ORACLEDBDSN
BIP2393E: Database error: ODBC return code '-1' from data source ''ORACLEDBDSN'' using ODBC driver manager ''odbc32.dll''.
The broker received an error when processing 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 problems are an incorrect data source, or table names. Correct either the database or the broker configuration.
BIP2322E: Database error: SQL State ''IM014''; Native Error Code '0'; Error Text ''[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application''.
The error has the following diagnostic information: SQL State ''IM014'' SQL Native Error Code '0' SQL Error Text ''[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application''
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.
- Check that the database has an adequate number of database connections available 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 DB2 64bit ODBC driver (DSNAO64C) is in the STEPLIB.
- Use mqsisetdbparms to set the password to the correct value and try again.
C:\Program Files (x86)\IBM\MQSI\7.0>
Any pointers will be greatly appreciated . Thanks in advance . |
|
| Back to top |
|
 |
| BrokerBeginner |
| Posted: Sat Jul 12, 2014 9:53 am Post subject: |
|
|
Newbie
Joined: 11 Jul 2014
Posts: 4
|
Also just some additional information :
Version of broker - 7.0.0.1
Version of Oracle - 11.2
I am doing POC's on my Windows XP - 64 bit OS .
I read the below in the sample provided with the toolkit -
Setting up the Database
On Windows®:
Windows provides only 32-bit support. Follow the instructions in Connecting to a database from Windows systems.
Is this why I am getting the error posted earlier . |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Jul 12, 2014 10:51 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Windows XP is .... well ancient.
Can't you really try something a little more recent for your learning? You will run into far fewer problems like this.
If you really have to use XP then revert to the 32nit version but honestly, IMHO XP is like putting Lipstick on a Pig. Underneath, there is still a Pig.
Search this site for posts mentioning 'odbc64'. These may resolve your problem but honestly, it is time to move to a newer OS and at the very least patch your broker to 7.0.0.6.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| ganesh |
| Posted: Mon Jul 14, 2014 5:44 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| Quote: |
The specified DSN contains an architecture mismatch between the Driver and Application''.
|
You are trying to create a 64 bit dsn for a 32 bit broker. |
|
| Back to top |
|
|
| BrokerBeginner |
| Posted: Mon Jul 14, 2014 8:40 pm Post subject: |
|
|
Newbie
Joined: 11 Jul 2014
Posts: 4
|
| smdavies99 wrote: |
Windows XP is .... well ancient.
Can't you really try something a little more recent for your learning? You will run into far fewer problems like this.
If you really have to use XP then revert to the 32nit version but honestly, IMHO XP is like putting Lipstick on a Pig. Underneath, there is still a Pig.
Search this site for posts mentioning 'odbc64'. These may resolve your problem but honestly, it is time to move to a newer OS and at the very least patch your broker to 7.0.0.6. |
First of all , would like to thank you for replying .
Would like to apologize for giving incorrect info - My OS is Windows 7 . |
|
| Back to top |
|
|
| BrokerBeginner |
| Posted: Mon Jul 14, 2014 8:43 pm Post subject: |
|
|
Newbie
Joined: 11 Jul 2014
Posts: 4
|
| ganesh wrote: |
| Quote: |
The specified DSN contains an architecture mismatch between the Driver and Application''.
|
You are trying to create a 64 bit dsn for a 32 bit broker. |
Hi Ganesh ,
Thank you for pointing it out .
Will do some digging on this and request for help if needed. |
|
| Back to top |
|
|
|
|
