| Author |
Message
|
| alvinlimtc |
 Posted: Thu Dec 22, 2005 2:28 am Post subject: Error creating broker on HP-UX |
 |
|
Apprentice
Joined: 22 Dec 2005
Posts: 29
Location: Singapore
|
Hi,
Am using the following :
OS : HP-UX 11.11 (64-bit)
DB2 : v8.1 Fix Pak 2
Message Broker : v5
MQ : v5.3 CSD 11
I am getting this error when creating a broker :
> mqsicreatebroker WBIMB_BROKER –i wbimb –a ****** –q WBIMB.QM.BRK –n WBIMBBRK –u wbimb –p *******
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.
/usr/lib/dld.sl: Bad magic number for shared library: /opt/db2inst1/sqllib/lib/libdb2.sl
/usr/lib/dld.sl: Exec format 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 'IM003'; Native Error Code '80'; Error Text 'Specified driver could not be loaded'.
The error has the following diagnostic information: SQL State 'IM003' SQL Native Error Code '80' SQL Error Text '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.
This is the .odbc.ini file :
[ODBC Data Sources]
WBIMBBRK=IBM DB2 ODBC Driver
MYDB=IBM DB2 ODBC Driver
ORACLEDB=DataDirect 410 Oracle 8 Driver
SYBASEDB=DataDirect 410 Sybase TDS Driver
[WBIMBBRK]
Driver=/opt/db2inst1/sqllib/lib/libdb2.sl
Description=WBIMBBRK DB2 ODBC Database
Database=WBIMBBRK
[MYDB]
Driver=/u/db2inst1/sqllib/lib/libdb2.sl
Description=MYDB DB2 ODBC Database
Database=MYDB
[ORACLEDB]
Driver=/opt/wmqi/merant/lib/UKor818.sl
Description=Oracle
WorkArounds=536870912
WorkArounds2=2
Description=Oracle8
ServerName=YourServerName
EnableDescribeParam=1
OptimizePrepare=1
[SYBASEDB]
Driver=/opt/wmqi/merant/lib/UKase18.sl
Description=Sybase12
Database=SYBASEDB
WorkstationID=id
ServerName=YourServerName
EnableDescribeParam=1
OptimizePrepare=1
SelectMethod=0
NetworkAddress=10.30.14.72,5000
SelectUserName=1
[ODBC]
Trace=0
TraceFile=/var/mqsi/odbc/odbctrace.out
TraceDll=/opt/mqsi/merant/lib/odbctrac.sl
InstallDir=/opt/mqsi/merant
I have done everything in as suggested in the manuals, ie:
- already run the mqsi_setupdatabase script
- source the db2profile by adding the line '. ~db2inst1/sqllib/db2profile' at the end of profile.hpux and verified that can connect to the DB2 table
- authorised the DB2 table
From the looks of the message, it cannot resolve the libdb2.sl library. But what do i have to do to correct this?
Thanks. |
|
| Back to top |
|
 |
| jsware |
| Posted: Thu Dec 22, 2005 5:03 am Post subject: Re: Error creating broker on HP-UX |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
| alvinlimtc wrote: |
/usr/lib/dld.sl: Bad magic number for shared library: /opt/db2inst1/sqllib/lib/libdb2.sl
/usr/lib/dld.sl: Exec format error
|
I am not an HPUX person, but according to HP's documentation at http://docs.hp.com/en/B2355-90697/dld.sl.5.html dld.sl is the dynamic loader which (if the same as AIX) will dynamically load shared libraries through the O/S calls such as dlopen etc.
Looks from this that the DB2 installation on your machine is corrupted in some fashion. Check with your DBAs regarding this. I read that the dld.sl shared library is complaining that the magic number (a kind of check digit I guess) for the libdb2.sl shared library is not correct.
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
|
| alvinlimtc |
| Posted: Fri Dec 23, 2005 1:27 am Post subject: |
|
|
Apprentice
Joined: 22 Dec 2005
Posts: 29
Location: Singapore
|
Thanks for the reply. We did a re-installation of the DB2 today and still the error persists. We even tried creating a different instance.
Wondering if anyone has done a Message Broker installation on HP-UX?
Any advise would be appreciated as we are at our wits end trying to figure this out.
Thanks. |
|
| Back to top |
|
|
| EddieA |
| Posted: Fri Dec 23, 2005 9:27 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Are you mixing 64 and 32 bit versions of DB2.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| JT |
| Posted: Fri Dec 23, 2005 9:48 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
DB2 : v8.1 Fix Pak 2
Message Broker : v5
MQ : v5.3 CSD 11 |
.......also, you didn't specify that a Fixpack was applied to MB v5 as you did the other technologies. Did you, what is it ? |
|
| Back to top |
|
|
| alexey |
| Posted: Sun Dec 25, 2005 8:58 am Post subject: |
|
|
Acolyte
Joined: 18 Dec 2003
Posts: 62
Location: Israel
|
| Check if your 64 bit drivers are listed in LIB_PATH. |
|
| Back to top |
|
|
| alvinlimtc |
| Posted: Tue Dec 27, 2005 7:39 pm Post subject: |
|
|
Apprentice
Joined: 22 Dec 2005
Posts: 29
Location: Singapore
|
I am using the 64-bit database.
I do not have a LIB_PATH, just an SHLIB_PATH. I use the default libraries as specified in the db2profile.
Is there any particular library I should include?
Also, with the wbimb userid I created, I am able to do this :
> db2 connect to WBIMBBRK
Thanks. |
|
| Back to top |
|
|
| alvinlimtc |
| Posted: Tue Dec 27, 2005 7:44 pm Post subject: |
|
|
Apprentice
Joined: 22 Dec 2005
Posts: 29
Location: Singapore
|
also, just to add, I tried without any Fix Pack for Message Broker. I also tried with the latest Fix Pack, ie Fix Pack 6.
Problem still persists.
Thanks. |
|
| Back to top |
|
|
| insanemorgoth |
| Posted: Wed Dec 28, 2005 8:51 am Post subject: Error creating broker on HP-UX |
|
|
Newbie
Joined: 13 Dec 2005
Posts: 7
|
I believe we had similar issues on AIX so this might help : -->
try running the mqsisetupdatabase command before you create the actual database. and run the profiles of each user , so that all the correct environment variables are exported. |
|
| Back to top |
|
|
| alvinlimtc |
| Posted: Wed Jan 04, 2006 8:40 am Post subject: |
|
|
Apprentice
Joined: 22 Dec 2005
Posts: 29
Location: Singapore
|
Just wanted to share that this problem has been resolved. It turns out that the ODBC driver shipped with DB2 does not support 64-bit instances. Hence, I had to create a 32-bit DB2 instance and I was able to proceed.
Thanks for all the help rendered. |
|
| Back to top |
|
|
|
|
