Author |
Message
|
CT |
Posted: Sun Jun 11, 2006 10:04 pm Post subject: Unable to create broker using 64 bit ODBC driver |
|
|
Newbie
Joined: 05 Apr 2002 Posts: 3
|
I'm upgrading from MQSI 2.1 to WBIMB Ver 6 running on:
·AIX 5.3 ML 4 64 bit kernel
·DB2 8.1 FP 11
·MQ 5.3 CSD 12
·WBIMB 6 CSD 1
Everything works fine if I use Db2 and ODBC 32 bit
I'm trying now to run WBIMB on 64 bit but all my trials were failed.
The procedure I followed to switch to WBIMB 64 bit is:
1. upgrade db2 instance to 64 bit by the command db2iupdt –w 64
2. configure ODBCINI64 to point to a copy of odbc64.ini after configuring that copy by my new DSN (Now we have old 32 bit DSN in ODBCINI and the new 64 bit DSN in ODBCINI64)
3. execute the .profile
4. I decided to create a new broker using an existing database, but I got the following 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 ''[DataDirect][ODBC lib] 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 ''[DataDirect][ODBC lib] 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 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.
*****************************
5.It seems it doesn’t look up for that DSN in ODBCINI64 (My guess it only lookup in ODBCINI)
6.I changed the ODBCINI to poing the same file as ODBCINI64
7.I retried to create the broker, I got a different error:
*********************************
AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager running.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
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.
***********************************
8. Here is the DSN definition for the above error:
Driver=/usr/opt/db2_08_01/lib64/libdb2.a
Description=Broker DB2 ODBC Database
Database=AX2D
9.I found in another IBM document that the library used in DSN definiton is different than what I’m using, I updated it and retried but got the same error
Driver=/opt/IBM/mqsi/6.0/lib/libdb2Wrapper64.so
#Driver=/usr/opt/db2_08_01/lib64/libdb2.a
Description=Broker DB2 ODBC Database
Database=AX2D
Has anyone faced this issue?  |
|
Back to top |
|
 |
nvogt |
Posted: Mon Jun 12, 2006 12:44 am Post subject: |
|
|
Novice
Joined: 27 Apr 2006 Posts: 11 Location: Aachen, Germany
|
The Broker can only be created by using an 32-bit ODBC Connection, because of the broker is an 32-bit executable |
|
Back to top |
|
 |
CT |
Posted: Mon Jun 12, 2006 6:34 am Post subject: |
|
|
Newbie
Joined: 05 Apr 2002 Posts: 3
|
Quote: |
The Broker can only be created by using an 32-bit ODBC Connection, because of the broker is an 32-bit executable |
Does this means that I have to have DB2 instance running in 32 bit mode?
I assumed the answer yes, I converted the DB2 instance to run in 32 bit mode.
I created the broker successfully but when I tried to create a 64bit execution group it gave the following error:
[1]BIP2391E: DB2 wrapper (64-bit) could not load the DB2 implementation library using library locations '/usr/opt/db2_08_01/lib64/libdb2.a(shr_64.o)', 'libdb2.a(shr_64.o)', or the location specified by the MQSI_64BIT_DB2_LIBRARY_NAME environment variable. DB2 will not be accessible in this process. : AX2D.daed6dc8-0b01-0000-0080-c44d4d0f83bc: /build/S600_P/src/bipodbc/wrapper/ImbDB2Wrapper.cpp: 603: ImbDB2Wrapper.o(loadAppropriateDB2Library): :
Jun 12 16:58:20 mwupgrd1 user:err|error WebSphere Broker v6001[815328]: (AX2D.Test64)[1]BIP2221E: Invalid installation set up. : AX2D.daed6dc8-0b01-0000-0080-c44d4d0f83bc: /build/S600_P/src/DataFlowEngine/ImbResource.cpp: 1438: ImbPersistentResource::startDatabase: ComIbmMQConnectionManager: ComIbmMQConnectionManager
Jun 12 16:58:20 mwupgrd1 user:err|error WebSphere Broker v6001[815328]: (AX2D.Test64)[1]BIP2321E: Database error: ODBC return code '-1'. : AX2D.daed6dc8-0b01-0000-0080-c44d4d0f83bc: /build/S600_P/src/DataFlowEngine/ImbOdbc.cpp: 227: ImbOdbcHandle::checkRcInner: :
Jun 12 16:58:20 mwupgrd1 user:err|error WebSphere Broker v6001[815328]: (AX2D.Test64)[1]BIP2322E: Database error: SQL State 'IM004'; Native Error Code '0'; Error Text '[DataDirect][ODBC lib] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed'. : AX2D.daed6dc8-0b01-0000-0080-c44d4d0f83bc: /build/S600_P/src/DataFlowEngine/ImbOdbc.cpp: 355: ImbOdbcHandle::checkRcInner: :
The DSN definition in ODBCINI64 is:
[AX2D]
Driver=/opt/IBM/mqsi/6.0/lib/libdb2Wrapper64.so
Description=Broker DB2 ODBC Database
Database=AX2D
By the way I made a one more try by using the following DSN definition:
[AX2D]
Driver=/usr/opt/db2_08_01/lib64/libdb2.a
Description=Broker DB2 ODBC Database
Database=AX2D
It gave the error "driver can't be loaded"
Is there any valid reason for these errors? |
|
Back to top |
|
 |
nvogt |
Posted: Tue Jun 13, 2006 3:23 am Post subject: |
|
|
Novice
Joined: 27 Apr 2006 Posts: 11 Location: Aachen, Germany
|
I don't know about DB2 because we are using an ORACLE 10g 64-bit Datatabase. But you have 2 config-Files for ODBC connections
1.) /var/mqsi/odbc/.odbc.ini for 32-bit connection config
2.) /var/mqsi/odbc/.odbc64.ini for 64-bit connection config.
it is also an environment variable.
ODBCINI64=/var/mqsi/odbc/odbc64.ini
ODBCINI=/var/mqsi/odbc/.odbc.ini
Best Regards
Norbert |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Jun 13, 2006 3:50 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
And did you make sure the access rights for the broker user are the same on the 64 bit executable DB directories than on the 32 bit ones?
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
xzhou |
Posted: Fri Apr 11, 2008 11:33 am Post subject: can 32 bit Oracle ODBC driver talk to 64 bit oracle db? |
|
|
Apprentice
Joined: 11 Apr 2008 Posts: 32
|
Hi
I have a question, I understand the core component is 32 bit in the message broker v6.0, we use ORACLE 10gr2 64-bit Datatabase in our case, both message broker and oracle run on Solaris 10 (SPARC), can I use 32 bit Oracle ODBC driver from Borker (which comes with IBM distribution) to connect to oracle instance (64 bit) ?
Thanks in advance!
Xiaoming |
|
Back to top |
|
 |
ghoshly |
Posted: Tue May 20, 2008 3:25 am Post subject: |
|
|
Partisan
Joined: 10 Jan 2008 Posts: 333
|
I had also faced this same kind of problem.
If the problem is still not solved then please try the following.
1. Create another environment variable named as MQSI_LIBPATH64
2. Put the path to the directory within your DB2 instance where all the library files for DB2 64bit are stored. (e.g. <DB2 Instance directory>/lib64)
3. Change the odbc64.ini as
[AX2D]
Driver=libdb2Wrapper64.so
Description=Broker DB2 ODBC Database
Database=AX2D
4. Execute the .profile and try |
|
Back to top |
|
 |
|