| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem installing WMQI 2.1 + DB2 8.1 on Solaris 8 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Cliff |
 Posted: Tue Nov 11, 2003 4:42 am Post subject: Problem installing WMQI 2.1 + DB2 8.1 on Solaris 8 |
 |
|
Centurion
Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire
|
Hello all.
I had a problem at a client's site yesterday installing WMQI 2.1 on a Solaris 8 box which already had DB2 8.1 installed - the package bind to the DB2 client failed, so I could not create a broker:
$
$ db2 create database BRKxxx
DB20000I The CREATE DATABASE command completed successfully.
$ db2 connect to BRKxxx
Database Connection Information
Database server = DB2/SUN 8.1.3
SQL authorization ID = MQSIxxx
Local database alias = BRKxxx
$ db2 bind /export/home/db2inst1/sqllib/bnd/@db2cli.lst grant public CLIPKG 5
LINE MESSAGES FOR db2cli.lst
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
LINE MESSAGES FOR db2clist.bnd
------ --------------------------------------------------------------------
235 SQL0440N No authorized routine named "POSSTR" of type
"FUNCTION" having compatible arguments was found.
SQLSTATE=42884
LINE MESSAGES FOR db2cli.lst
------ --------------------------------------------------------------------
SQL0091N Binding was ended with "0" errors and "1" warnings.
$
$
$
$
$ mqsicreatebroker BRKxxx -i mqsixxx -a <pwd> -q BRKxxx -n BRKxxx -u mqsixxx -p <pwd>
Abort
$
$
$
$
$ db2 connect reset
DB20000I The SQL command completed successfully.
$
$
$
$
$ mqsicreatebroker BRKxxx -i mqsixxx -a <pwd> -q BRKxxx -n BRKxxx -u mqsixxx -p <pwd>
Abort
$
Names changed to protect the guilty, of course.... So, I know this is not a supported combination, but can anyone tell me whether this can be expected to work (the client would prefer to stick with DB2 8.1 if possible because of other software on the box) and if so how, whether I really need to uninstall DB2 and install version 7.2, or whether I've missed something else?
Other info: MQSeries 5.3 (yes, I know that's not supported either!) and I am not a DB2 DBA. Nor indeed a Solaris administrator.
Any help gratefully received. Many thanks -
Cliff |
|
| Back to top |
|
 |
| kirani |
| Posted: Tue Nov 11, 2003 8:52 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
What WMQI CSD level you have installed on this server? MQ 5.3 is supported with WMQI 2.1.
_________________
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 |
|
|
| Cliff |
| Posted: Wed Nov 12, 2003 1:36 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire
|
Hi, Kiran. Glad to see you spotted the deliberate mistake re MQ 5.3......
CSD level for WMQI 2.1 is 4, freshly downloaded and installed.
Kind regards -
Cliff |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Nov 12, 2003 1:41 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
I think DB2 8.1 is not officially supported by IBM with WMQI 2.1
_________________
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 |
|
|
| Cliff |
| Posted: Fri Nov 14, 2003 1:49 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire
|
Kiran, you're right, it's not officialy supported but the best information I can get (if I heard it right) is that the broker process is unchanged between versions 2.1 and 5.2, so if it works for 5.2 it'll work for 2.1.
There is a known problem + workaround with DB2 7.2 and WMQI 2.1 which I am advised also applies to DB2 8.1. So, this is the process I'll follow when I return to the client site on Monday:
The fix for this incompatibility in Unicode support between the Merant Driver Manager and the DB2 ODBC driver is described for DB2 7.2 at http://www-1.ibm.com/support/docview.wss?uid=swg21042663 and the fix is the same for DB2 8.1. It involves using the 2nd version of the ODBC driver which ships with the product.
Download and install FixPak 2 for DB2 8.1 from
Determine what instances are installed: db2ilist
If you need to know what databases have been created, for each instance, su to the instance owner and list all databases and aliases created for that instance: db2 list db directory
Shut down all DB2 activity. As the instance owner, either db2stop force or db2 force application all to disconnect all applications then db2stop for a quiesced shutdown.
As root, first noting it’s ownership and permissions, copy /opt/IBMdb2/V8.1/lib/libdb2.so.1 to /opt/IBMdb2/V8.1/lib/libdb2.so.1_copy
Copy /opt/IBMdb2/V8.1/lib/libdb2_36.so.1 to /opt/IBMdb2/V8.1/lib/libdb2.so.1. Ensure ownership and permissions are as noted in the previous step.
For each instance: db2iupdt <instance>
For the DAS instance: dasiupdt <dasinstance>
Start the database: db2start
We are now in a position to attempt the bind again, but must first bind another package:
db2 bind /export/home/db2inst1/sqllib/bnd/@db2ubind.lst BLOCKING ALL grant public CLIPKG 5
db2 bind /export/home/db2inst1/sqllib/bnd/@db2cli.lst BLOCKING ALL grant public CLIPKG 5
Now the broker can be created.
I'll let you all know how I get on! Cheers -
Cliff |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
