| Author |
Message
|
| pfarrel |
 Posted: Tue Jun 19, 2012 2:24 am Post subject: WMB Upgrade V6.1 to V8 ODBC Changes |
 |
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
I am upgrading WMB from V6.1 to V8 on AIX, and I need help with the changes to the odbc file, located at /var/mqsi/.odbc64.ini.
I have read the information Center section on this, but it doesn't seem to help.
Basically, I have 3 kinds of changes to make, and I think I understand the first 2, but not the last one.
I believe that the following 2 changes need to be made:
Driver=/opt/IBM/mqsi/6.1/ODBC64/V5.3/lib/UKmsss23.so
becomes Driver=/opt/IBM/mqsi/8.0.0.0/ODBC/V6.0/lib/UKmsss24.so
Driver=/opt/IBM/mqsi/6.1/ODBC64/V5.3/lib/UKora23.so
becomes Driver=/opt/IBM/mqsi/8.0.0.0/ODBC/V6.0/lib/UKora24.so
but, I also have the following:
Driver=/opt/IBM/mqsi/6.1/lib/libdb2Wrapper64.so
I don't see what it should become. Can anyone please help ?
Thanks ! |
|
| Back to top |
|
 |
| marko.pitkanen |
| Posted: Tue Jun 19, 2012 2:47 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi pfarrel,
So you mean driver for DB2, did you searched http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/topic/com.ibm.etools.mft.doc/bk58070_.htm sample ODBC configurations file?
Migration document at the InfoCenter says
| Quote: |
| Before you run the commands at the new service level, check that your ODBCINI environment variable points to the new file and not to the existing file |
Perhaps it is wise to pick up the sample odbc.ini that came with version 8 and use it as an template and configure your existing connections from scratch.
--
Marko |
|
| Back to top |
|
|
| pfarrel |
| Posted: Tue Jun 19, 2012 5:58 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
|
| Back to top |
|
|
| pfarrel |
| Posted: Tue Jun 19, 2012 6:18 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
I think I may have spoken too soon.
According to the sample for DB2, I will have to make the following change in my Broker ODBC:
/opt/IBM/mqsi/6.1/lib/libdb2Wrapper64.so
becomes /udb/db2/v9.1r/lib64/db2o.o
Note that DB2 version 9.1r is there to support the broker database for Broker V6.1. I was planning to remove DB2 from this lpar after I have upgraded Broker to V8. If I make this change I will never be able to get rid of DB2 on the broker lpar. Is there another solution ?
( My broker will be using DB2 systems which are on other lpars, not on the broker lpar ). |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Tue Jun 19, 2012 6:37 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi,
I think you should search some more information what are your options to connect to remote DB2 from your broker environment and how to configure message broker to connect with them.
--
Marko |
|
| Back to top |
|
|
| pfarrel |
| Posted: Tue Jun 19, 2012 7:24 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
Thanks, but I already have all this working OK with my V6.1 broker. We connect to other DB2 systems, including one on a mainframe, using the ODBC file, with a stanza entry like this one:
[MFDB]
Driver=/opt/IBM/mqsi/6.1/lib/libdb2Wrapper64.so
Description=IBM DB2 ODBC Driver
Database=DB2T
I am wanting to know how to change this so that it continues to work when I upgrade Broker to V8.
You can see that for Broker V6.1, the driver is included with Broker, and we are not using a file that is part of a local DB2 install.
For Broker V8, the sample suggests using the following:
[MFDB]
Driver=/udb/db2/v9.1r/lib64/db2o.o
Description=IBM DB2 ODBC Driver
Database=DB2T
This will require a local installation of DB2, even though I don't need one. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 19, 2012 7:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It will require a local installation of DB2, yes.
Broker v8 does not ship with any DB2 install media.
It does not require a local installation of DB2 Server.
You can always just switch to using JDBC, if you're unhappy with having to maintain a proper database client for your broker database needs. |
|
| Back to top |
|
|
|
|
