| Author |
Message
|
| raam |
 Posted: Fri Dec 30, 2011 11:13 pm Post subject: Unable to Rollback MQ/MB from V7 to V6 |
 |
|
Apprentice
Joined: 14 May 2011
Posts: 29
|
AIX- V5.3
WMB- Current (V7.0.0.1); Previously (V6.1.0.9)
WMQ- Current (V7.0.1.5); Previously (V6.0.2.5)
Hi,
I had successfully migrated MQ (one QMgr) and Broker (one Broker) on one of our System Test servers to version 7. I followed proper documentation as far as I am aware and did the migration around Dec 03. The environment has been working fine since then.
However, since a capacity baseline measurement for the project was required, I was requested to revert the environment back to the previous versions. So I reverted Message Broker to version 6.1.0.9 which went through successfully.
http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/bh44770_.htm
mqbrk@:/opt/IBM/mqsi/7.0/bin >mqsimigratecomponents GSBBKRT01 -s 7.0.0.1 -t 6.1.0.9
WebSphere MQ queue manager 'GSBBUST01' starting.
5 log records accessed on queue manager 'GSBBUST01' during the log replay phase.
Log replay for queue manager 'GSBBUST01' complete.
Transaction manager state recovered for queue manager 'GSBBUST01'.
WebSphere MQ queue manager 'GSBBUST01' started.
BIP8849I: Broker 'GSBBKRT01' (Version 7.0) with Queue Manager 'GSBBUST01' and Data Source 'WBRKDBA' specified for migration.
BIP8785I: Starting WebSphere MQ queue migration for component 'GSBBKRT01'.
BIP8788I: Deleted WebSphere MQ queue 'SYSTEM.BROKER.ADMIN.REPLYTODM'
BIP8788I: Deleted WebSphere MQ queue 'SYSTEM.BROKER.DEPLOY.QUEUE'
BIP8788I: Deleted WebSphere MQ queue 'SYSTEM.BROKER.DEPLOY.REPLY'
BIP8789I: Finished WebSphere MQ queue migration for component 'GSBBKRT01'.
BIP8768I: Finished registry migration for component 'GSBBKRT01'.
BIP8654I: Moving file system artifacts from '/var/mqsi' to '/var/mqsi'.
BIP8071I: Successful command completion.
But the components (config manager and broker) did not restart after the above.
mqbrk@gsb-t-app-02:/home/mqbrk >mqsistart CMGR00
exec(): 0509-036 Cannot load program mqsistart.bin because of the following errors:
0509-022 Cannot load module /opt/IBM/mqsi/6.0/lib/libbipodbc64.a(shr_64.o).
0509-150 Dependent module /opt/IBM/mqsi/6.0/lib/libodbc.a(odbc.so) could not be loaded.
0509-103 The module has an invalid magic number.
0509-022 Cannot load module mqsistart.bin.
0509-150 Dependent module /opt/IBM/mqsi/6.0/lib/libbipodbc64.a(shr_64.o) could not be loaded.
0509-022 Cannot load module .
I have tried various options to get this fixed, but I am back at square one.
Prior to migration to version 7, the backup of the file systems were taken. So we tried restoring these file systems. But still, although the restoration process showed to be successful, it did not get through properly as I still see the above invalid magic number error.
Also, I am not sure if the backup was done right because, after trying to restore the file systems, MQ is still at version 7, but Broker is restored to version 6.1.0.9. And yet the broker components are not starting up.
Any advise at this point will be appreciated. Kindly let me know.
_________________
Thanks a lot.
You're only given a little spark of madness. You mustn't lose it…..  |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Sat Dec 31, 2011 12:28 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
AFAIK, migration only works in one direction, upwards.
If I were having to do your job, I'd delete everything and recreate the V6.1.0.9 broker from scratch. Then redeploy all the flows, messagesets etc.
Naturally, I'd have a script (or two) that did this all for me.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| raam |
| Posted: Sat Dec 31, 2011 1:30 am Post subject: |
|
|
Apprentice
Joined: 14 May 2011
Posts: 29
|
Thanks. I agree with you. I did not want to do a rollback to V6 as I don't recommend it myself.
But now, I realized that the backup that was taken on Nov 19th had a retention policy of only 30 days which wasn't communicated to me. Now the backup seems to be unavailable.
So when the restoration was tried on Wednesday, the restoration point was for Nov 27th. So now I have MQ at v7 and MB at v6109. However, the invalid magic number still exists as I mentioned and hence the Broker/Config Manager does not start up.
I am looking into the task of uninstall/re-install MQ and MB from scratch.
However, any tips on the error will be greatly appreciated.
Thanks for your feedback.
_________________
Thanks a lot.
You're only given a little spark of madness. You mustn't lose it….. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Dec 31, 2011 6:02 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| raam wrote: |
I am looking into the task of uninstall/re-install MQ and MB from scratch.
|
Why?
Why are you uninstalling WMQ? WMQ V7.0.1.3 upwards will happily work with V6.1 and V7 brokers
Why reinstall Broker? Both V6 and V7 brokers can co exist on the same system. Just keep the files pointed to by $ODBCINI different. Use different users to run the different broker versions.
This is all explained in the documentation but sadly all too few people think of reading that before asking for help. {see a plethora of other posts here}
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Dec 31, 2011 8:13 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| raam wrote: |
Thanks. I agree with you. I did not want to do a rollback to V6 as I don't recommend it myself.
But now, I realized that the backup that was taken on Nov 19th had a retention policy of only 30 days which wasn't communicated to me. Now the backup seems to be unavailable.
So when the restoration was tried on Wednesday, the restoration point was for Nov 27th. So now I have MQ at v7 and MB at v6109. However, the invalid magic number still exists as I mentioned and hence the Broker/Config Manager does not start up.
I am looking into the task of uninstall/re-install MQ and MB from scratch.
However, any tips on the error will be greatly appreciated.
Thanks for your feedback. |
Don't trust the back.
Just delete the Broker and ConfigMgr.
Recreate from scratch.
Creating a properly restorable backup of a broker really onyl came in with V7. (mqsibackbroker)
you didn't explain why you think that you need to re-install WMQ. you dont.
Create a clean system.
Install & Patch V6.1
Install & Patch V7.0
Delete Queue Manager
Create a new QM from the scripts you have (you do have this don't you?)
Create a V6.1 broker.
Deploy V6.1 Bar files etc to V6.1 broker using the scripts you have
If you don't have the scripts, now is a great time to create them for future use.
don't forget to check them into your source control system along with all the deployed objects for both versions of the broker.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Dec 31, 2011 8:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You can either uninstall things, or install older levels of Broker in new locations.
Broker can coexist at multiple full versions. Broker can coexist at multiple fix pack levels, and the fix level that a given broker will run at is determined by the combination of the -f switch and the version of the mqsiprofile that is applied when you mqsistart. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Dec 31, 2011 1:38 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Your magic # problem is a problem in your environment.
Could be that you are not sourcing the mqsiprofile correctly.
Could also be that some environment variables (library path) or the MQ shortcuts are not as they should be. (see WMQ V6 vs V7)
Apart from this, I would not go back to MQ V6...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
