| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMQI 2.1 Migration experiences needed |
« View previous topic :: View next topic » |
| Author |
Message
|
| zpat |
 Posted: Fri May 17, 2002 2:26 am Post subject: WMQI 2.1 Migration experiences needed |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
We currently have MQSI 2.02, MQ 5.1 and DB/2 6.1 on NT and AIX
We want to migrate to WMQI 2.1 CSD 2 and would appreciate any advice (other than read the manuals).
For example IBM recommend immediate updating of the control centers to 2.1 after the configuration manager is upgraded!
This is typical of IBM staff in laboratories who have a single environment.
We have about six MQSI environments and will migrate slowly to 2.1 - so can we safely use 2.1 control centers against 2.0.2 configuration managers? Or can we have both levels of CC installed on a PC?
Also did people upgrade MQ to 5.2 or DB/2 to 7.1 at the same time? |
|
| Back to top |
|
 |
| TorpedoSTu |
| Posted: Wed May 22, 2002 3:09 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2001
Posts: 73
|
Gosh,
There's lots to consider here & it all depends on your configuration and whether or not you're using the MRM.
First up, You can't use the 2.1 Control Centre with previuos versions of the Config Mgr as the database has changed (as has the XML for MRM definitions). so the only coice is to plan to move as a unit.
You can safely use DB2 up to GA level (CSD6) but be aware that there is an ODBC patch that you must apply for DB2 otherwise DB2 will core dump on AIX and Java Class Error on NT/2K. If you are only using DB2 for the ConfigMgr, then I suggest that you leave it at the current level unless your DB2 knowledge is up to scratch.
There's no real issues with going to MQ 5.2 (5.2.1 on NT/2K). remember to apply CSD04.
My recomendation is to ....
1. Config Manager.
a. Convert as per the IBM Manual (apply CSD2 of MQSI). (You'll need to do this as you need the XML to be the 2.1 version)
b. export all Message flows and Message sets
c. Completely uninstall all versions MQSI from your machine. (I've seen machine's get totally confused if you don't do this)  Don't forget to either clear down or delete/re-create the DB2 databases.
d. re-install MQSI 2.1 and immediately apply CSD02.
e. import message flows/message sets
2. Brokers
a. delete brokers (don't forget to either clear down or dlete/re-create the DB2 databases)
b. completely uninstall all versions of MQSI
c. install MQSI 2.1 and immediately apply CSD02
d. re-create and start brokers
3. Re-commission
a. configure Topology as required (note, there are rumours from IBM that there are problems with using 'default' as an execution group. I recommend that you delete it and create your own, before deploying the new Topology.
4. I should set up a 'practice' environment first so that you're sure of the procedures.
Hope this helps |
|
| Back to top |
|
|
| TorpedoSTu |
| Posted: Wed May 22, 2002 3:13 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2001
Posts: 73
|
| TorpedoSTu wrote: |
Gosh,
There's lots to consider here & it all depends on your configuration and whether or not you're using the MRM.
First up, You can't use the 2.1 Control Centre with previuos versions of the Config Mgr as the database has changed (as has the XML for MRM definitions). so the only coice is to plan to move as a unit.
You can safely use DB2 7.1 up to GA level (CSD6 (BTW after CSD3 it becomes 7.2 !)) but be aware that there is an ODBC patch that you must apply for DB2 otherwise DB2 will core dump on AIX and Java Class Error on NT/2K. If you are only using DB2 for the ConfigMgr, then I suggest that you leave it at the level supplied with the product media unless your DB2 knowledge is up to scratch.
There's no real issues with going to MQ 5.2 (5.2.1 on NT/2K). remember to apply CSD04.
My recomendation is to ....
1. Config Manager.
a. Convert as per the IBM Manual (apply CSD2 of MQSI). (You'll need to do this as you need the XML to be the 2.1 version)
b. export all Message flows and Message sets
c. Completely uninstall all versions MQSI from your machine. (I've seen machine's get totally confused if you don't do this) Don't forget to either clear down or delete/re-create the DB2 databases.
d. re-install MQSI 2.1 and immediately apply CSD02.
e. import message flows/message sets
2. Brokers
a. delete brokers (don't forget to either clear down or dlete/re-create the DB2 databases)
b. completely uninstall all versions of MQSI
c. install MQSI 2.1 and immediately apply CSD02
d. re-create and start brokers
3. Re-commission
a. configure Topology as required (note, there are rumours from IBM that there are problems with using 'default' as an execution group. I recommend that you delete it and create your own, before deploying the new Topology.
4. I should set up a 'practice' environment first so that you're sure of the procedures.
Hope this helps |
|
|
| Back to top |
|
|
| zpat |
| Posted: Wed May 22, 2002 4:18 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Thanks, I agree that MQ 5.2(1) is needed.
Can you tell me the APAR number of this DB/2 ODBC problem so I can check if we have the fix applied? Which CSD fixes it?
WMQI 2.1 is a bit of a nightmare because once you start migration of CM environments you can't export/import between CM levels so have to complete the migration before promoting any flows again. We have six levels, each with their own CM.
IBM have failed to provide their usual (mainframe) standards of compatibility and it's really not good enough if they expect large installations (we have 20 CUs worth of MQSI) to use this product intensively for business critical applications.
Even worse we suspect that our MQSI flows won't run on WMQI 2.1 and so we will have to re-code parts of them.
Anyone know if MQSeries 5.3 is compatible with WQMI 2.1? |
|
| Back to top |
|
|
| TorpedoSTu |
| Posted: Thu May 23, 2002 6:05 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2001
Posts: 73
|
zpat,
The fix is necessary because of UNICODE support in the MERANT driver
The DB2 fix for AIX goes as follows (Other UNIX platforms are essentially the same).
Install CSD6 then
1. Shut down all database instances as the instance owner ID. (eg.
db2stop force).
2. Shut down the administration server instance as the admin instance
ID. (eg. db2admin stop force) 8
3. Backup db2.o under /usr/lpp/db2_<ver>_<rel>/lib
4. Issue "slibclean" as root.
5. Copy db2_36.0 to db2.o, ensuring that ownership and permissions are
consistent:
cp db2_36.o db2.o
-r--r--r-- bin:bin for db2.o |
|
| 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
|
|
|
|
