| Author |
Message
|
| yonny |
 Posted: Tue Dec 14, 2004 4:34 pm Post subject: Mqsicreatebroker problem (after trying almost everything) |
 |
|
Apprentice
Joined: 08 Jul 2001
Posts: 49
Location: Santo Domingo
|
Hello, before I decided to post this question I tried every suggestion found on this forum, without luck.
My enviroment is:
AIX 5200-04, DB2 Version 8.2 (Version 8.1 FixPak 7)
Business Integration Message Broker Fix Pack 04.
And my problem is the following command not working:
mqsicreatebroker BROKERA -i db2inst1 -a ****** -q QMBROKER -n BKDB
I am receiving some errors which have been seen several times on these forums:
BIP2322E: Database error: SQL State 'IM003'; Native Error Code '80'; Error Text 'Specified driver could not be loaded'.
...
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.
The command mqsi_setupdatabase db2 /usr/opt/db2_08_01 created this link: /var/wmqi/lib/libdb2.a to /usr/opt/db2_08_01/lib/libdb2.a
which is also a link pointing to /usr/opt/db2_08_01/lib64/libdb2.a
I'll post my odbc.ini file and the errors returned by the odbc trace in a separate note.
Thanks,
Yonny |
|
| Back to top |
|
 |
| yonny |
| Posted: Tue Dec 14, 2004 4:45 pm Post subject: |
|
|
Apprentice
Joined: 08 Jul 2001
Posts: 49
Location: Santo Domingo
|
My .odbc.ini file:
[ODBC Data Sources]
MQSIBKDB=IBM DB2 ODBC Driver
MYDB=IBM DB2 ODBC Driver
BKDB=IBM DB2 ODBC Driver
ORACLEDB=DataDirect 410 Oracle 8 Driver
SYBASEDB=DataDirect 410 Sybase ASE Driver
[BKDB]
Driver=/u/db2inst1/sqllib/lib/libdb2.a
Description=ODBC para DB Broker
Database=BKDB
[ODBC]
Trace=1
TraceFile=/var/wmqi/odbc/odbctrace.out
TraceDll=/usr/opt/wmqi/merant/lib/odbctrac.so
InstallDir=/usr/opt/wmqi/merant
and the error captured by the odbc trace:
...
ppid=315646:pid 59004:1 EXIT SQLAllocConnect with return code 0 (SQL_SUCCESS)
HENV 0x2003ae48
HDBC * 0x2003d278 ( 0x2005a958)
ppid=315646:pid 59004:1 ENTER SQLSetConnectOption
HDBC 0x2005a958
UWORD 102
UDWORD 0
ppid=315646:pid 59004:1 EXIT SQLSetConnectOption with return code 0 (SQL_SUCCE
SS)
HDBC 0x2005a958
UWORD 102
UDWORD 0
ppid=315646:pid 59004:1 ENTER SQLConnect
HDBC 0x2005a958
UCHAR * 0x2ff20818 [ -3] "BKDB"
SWORD -3
UCHAR * 0x2ff20798 [ -3] "db2inst1"
SWORD -3
UCHAR * 0x2ff20670 [ -3] "******"
SWORD -3
ppid=315646:pid 59004:1 ENTER SQLConnectW
HDBC 0x2005a958
WCHAR * 0x2003d358 [ -3] "BKDB"
SWORD -3
WCHAR * 0x2003d378 [ -3] "db2inst1"
SWORD -3
WCHAR * 0x2ff205e0 [ -3] "******"
SWORD -3
ppid=315646:pid 59004:1 EXIT SQLConnectW with return code -1 (SQL_ERROR)
HDBC 0x2005a958
WCHAR * 0x2003d358 [ -3] "BKDB"
SWORD -3
WCHAR * 0x2003d378 [ -3] "db2inst1"
SWORD -3
WCHAR * 0x2ff205e0 [ -3] "****/≥P ╙x ╙¿ ╙x"
SWORD -3
ppid=315646:pid 59004:1 EXIT SQLConnect with return code -1 (SQL_ERROR)
HDBC 0x2005a958
UCHAR * 0x2ff20818 [ -3] "BKDB"
SWORD -3
UCHAR * 0x2ff20798 [ -3] "db2inst1"
SWORD -3
UCHAR * 0x2ff20670 [ -3] "****≡¬8┤ ╙¿ ╙x/≥╙▌q0"
SWORD -3
ppid=315646:pid 59004:1 ENTER SQLError
HENV 0x00000000
HDBC 0x2005a958
HSTMT 0x00000000
...
Any help will be appreciated. If you need further information please let me know. Another clues may be:
- After installing FixPack 7 for BD2 I had to migrate db2 instance to 64 bits.
- The aix box has a completely new installation, I mean that all the products (aix, db2, mq and the message broker) were installed since monday.
- I have had experience installing this set of products several times before, but always with MQSI 2.1 and without 64 bits versions. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Dec 14, 2004 4:47 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| yonny wrote: |
| - After installing FixPack 7 for BD2 I had to migrate db2 instance to 64 bits. |
I don't think 64 bit DB2 is supported by broker....
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Dec 14, 2004 11:46 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
From IBM website.
| Quote: |
Support for 64-bit databases (DB2 and Oracle)
The Broker is a 32-bit application and interacts with 32-bit database libraries. In these Broker environments, our statement of support for databases refers to the database client.
The Broker supports connecting to a 32-bit database client which connects to a 64-bit server. The Broker does not support connecting to a 64-bit database client. This restriction is imposed by both the Broker and the DataDirect drivers.
Oracle 9i installs both 64-bit and 32-bit libraries, with the 64-bit libraries as the default. For example, the 64-bit libraries are installed in the ${ORACLE_HOME}/lib directory and the 32-bit libraries are installed in the /lib32 directory. The customer must configure the Broker environment to use the 32-bit libraries (using mqsi_setupdatabase).
|
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| fschofer |
| Posted: Wed Dec 15, 2004 12:11 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi,
correct the parameter:
Driver=/u/db2inst1/sqllib/lib/libdb2.a (which points to nowhere)
to
Driver= /usr/opt/db2_08_01/lib/libdb2.a
in
[BKDB]
Driver=/u/db2inst1/sqllib/lib/libdb2.a
Description=ODBC para DB Broker
Database=BKDB
Greetings
Frank |
|
| Back to top |
|
|
| yonny |
| Posted: Thu Dec 16, 2004 12:43 pm Post subject: |
|
|
Apprentice
Joined: 08 Jul 2001
Posts: 49
Location: Santo Domingo
|
| Thank you all. I tried your suggestions but they did not work. I am working with the broker running on Win2k until I have time to reinstall a 32bit version of DB2 in the AIX box. |
|
| Back to top |
|
|
|
|
