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 » WebSphere Message Broker (ACE) Support » Failed to create a broker with 64bit DB2

Post new topic  Reply to topic
 Failed to create a broker with 64bit DB2 « View previous topic :: View next topic » 
Author Message
Knotic
PostPosted: Wed Nov 08, 2006 12:18 am    Post subject: Failed to create a broker with 64bit DB2 Reply with quote

Newbie

Joined: 07 Nov 2006
Posts: 2
I cann't create the broker with 64bit DB2. I'm quiet sure that I already tried everything in the info center.

System Environment:
Broker Server
AIX 5.3 ML2
WebSphere Message Broker V6.0.2.0
WebSphere MQ V6.0.1.1
DB2 Client V8.2 (64bit Instance)
IBM SDK 1.4.2

DB2 Server
AIX 5.3 ML2
DB2 UDB V8.2 (64bit Instance)
IBM SDK 1.4.2

I can connect to DB2 Server from broker server's DB2 client with the user name and password specify in mqsicreatebroker command. I created the broker on 32bit DB2 database successfully.

mqsicreatebroker <BROKER_NAME> -i <BROKER_USERNAME> -a <PASSWORD> -q <QM_NAME> -n <DB2_ALIAS> -u <DB2_USER> -p <DB2_PWD>

The command above failed with the following log
----------------------------Error Log----------------------------
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.
----------------------------Error Log----------------------------



Below are the exported variable before run the command
----------------------------Exported ENV----------------------------
export ODBCINI=/var/mqsi/odbc/.odbc.ini
export ODBCINI64=/var/mqsi/odbc/odbc64.ini
export LIBPATH=/home/db2inst1/sqllib/lib32:$LIBPATH
export MQSI_LIBPATH64=/home/db2inst1/sqllib/lib64
export EXTSHM=ON
----------------------------Exported ENV----------------------------



Below is odbc64.ini file
----------------------------ODBC64.INI----------------------------
[ODBC Data Sources]
BRK_DB64=IBM DB2 ODBC Driver

[BRK_DB64]
#Driver=/usr/IBM/mqsi/lib/libdb2Wrapper64.so
Driver=/home/db2inst1/sqllib/lib/libdb2.a
Description=BRK_DB64 DB2 ODBC Database
Database=BRK_DB64

[ODBC]
Trace=1
TraceFile=/usr/IBM/mqsi/merant/odbc64trace.out
TraceDll=/usr/IBM/mqsi/merant/lib/odbctrac.so
InstallDir=/usr/IBM/mqsi/merant
UseCursorLib=0
IANAAppCodePage=4
----------------------------ODBC64.INI----------------------------


Have anybody here create the broker with 64bit DB2 database successfully? It would be great if you can give a hint to do it.
Back to top
View user's profile Send private message MSN Messenger
jefflowrey
PostPosted: Wed Nov 08, 2006 3:38 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
If you are using a 64-bit DB2 instance, ensure that you add <DB2 instance directory>/sqllib/lib32 to the start of the library search path environment variable. If you are using a 64-bit Oracle instance, ensure that you add $ORACLE_HOME/lib32 to the start of the library search path environment variable. If you are using 64-bit execution groups, ensure that you set the environment variable MQSI_LIBPATH64 to include the regular 64-bit database libraries.

Notice that this section ins marked as a recent change in the InfoCenter. It seems, in general, that documentation on database connectivity with v6 is under heavy revision. So if you get stuck on something, make sure to re-check the Info Center as it may have changed since the last time you looked.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Knotic
PostPosted: Wed Nov 08, 2006 7:20 pm    Post subject: Reply with quote

Newbie

Joined: 07 Nov 2006
Posts: 2
Thanks for yo suggestion, jefflowrey

I had already add <DB2 instance directory>/sqllib/lib32 to the library search path as you can see from below.

----------------------------Exported ENV----------------------------
export ODBCINI=/var/mqsi/odbc/.odbc.ini
export ODBCINI64=/var/mqsi/odbc/odbc64.ini
export LIBPATH=/home/db2inst1/sqllib/lib32:$LIBPATH
export MQSI_LIBPATH64=/home/db2inst1/sqllib/lib64
export EXTSHM=ON
----------------------------Exported ENV----------------------------

Any suggestion?
Back to top
View user's profile Send private message MSN Messenger
martinb
PostPosted: Thu Nov 09, 2006 4:11 am    Post subject: Reply with quote

Master

Joined: 09 Nov 2006
Posts: 210
Location: UK
Looks like your odbc64.ini file is incorrect, when using a 64bit instance you need to have the driver configured to libdb2Wrapper64.so.

Validate the path to libdb2Wrapper64.so and ensure it is either quoted in full
in the odbc64.ini file or the path is added to LIBPATH

---------------ODBC64.INI------------------

[BRK_DB64]
Driver=<Path>/libdb2Wrapper64.so
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 » WebSphere Message Broker (ACE) Support » Failed to create a broker with 64bit DB2
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.