| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message Broker Migration From 6.0 to 6.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Shahid.Hussain |
 Posted: Sun Apr 25, 2010 12:07 am Post subject: Message Broker Migration From 6.0 to 6.1 |
 |
|
Novice
Joined: 18 Mar 2009
Posts: 13
|
Hi All,
i have some confusion regarding the migration of message broker from 6.0 to 6.1 on the windows cluster environment.
i installed broker 6.1 on the same machine as broker 6.0. then ran the mqsimigratecomponents command for configuration manager and broker. which executed without any problem. then i open broker 6.1 command console and issue mqsilist command and see both configuration manager and broker running. when i execute mqsilist command under broker 6.0 command console, i am not getting anything.
Problem is that under windows services list i only see broker and configuration manager services running for version 6.0. it should show the version 6.1 services .
can any one suggest any thing ??
Best Regards
Shahid Hussain |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Sun Apr 25, 2010 8:31 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I'd probably have upgraded the software on both nodes before migrating the components (on one node only). That way (IMHO) everything keeps in sync.
What would have happened in the code upgrade to the 2nd machine failed?
You can't go back as you have already mangled the components.
_________________
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 |
|
|
| Shahid.Hussain |
| Posted: Sun Apr 25, 2010 9:00 pm Post subject: |
|
|
Novice
Joined: 18 Mar 2009
Posts: 13
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Apr 25, 2010 9:59 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Shahid.Hussain wrote: |
| is there any solution ? |
Yes.
Delete everything and re-create the Broker etc from the scripts you have.
It should only take a few minutes.
You do have scripts to do this don't you?
or are you a GUI only sort of person?
Oh, as this is 6.1, I'd probably drop the Broker DB as well. Again, this is not a big job if you have taken the time and trouble up-front to do everything via scripts.
_________________
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: Mon Apr 26, 2010 4:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
mqsilist under version 6.0 will never show you any version 6.1 objects.
mqsilist under version 6.1 will only show you version 6.0 objects if you specify -a
If you have *migrated* a service, you have not *created a new one*, you have *transformed* the existing service from one version to another.
So where before you had a Windows Service that represented your Broker named, say "TEST BROKER", you will *still* have the *same* Windows Service that represents your broker named "TEST BROKER".
And the Windows Service view doesn't show anything about the version that "TEST BROKER" is at.
Nothing you have so far said represents a problem, and nothing therefore needs a solution.
smdavies99 may be correct that it is *better* to create a new broker rather than migrate an existing one, but that still doesn't mean it's a "problem" to migrate an existing broker. |
|
| 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
|
|
|
|
