| Author |
Message
|
| klamerus |
 Posted: Sat Apr 29, 2006 1:21 pm Post subject: v5.3 and v6.0 |
 |
|
Disciple
Joined: 05 Jul 2004
Posts: 199
Location: Detroit, MI
|
| Are there any issues or problems in using 5.3 and 6.0 together within the same cluster? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sat Apr 29, 2006 2:26 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
As a general rule, it is always best to ensure that your full repositories are at the most recent level of the software in your cluster.
That is, don't run a cluster that mixes v6 with v5 unless your FRs are v6. The repository datastructures are version specific and if you try and add v6 data to a v5.3 cluster, you can trash the repository.
Likewise, with v5.2 and 5.3 mixed clusters - if your FRs weren't v5.3 and you tried to use SSL *anywhere*, boom no more repository.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| klamerus |
| Posted: Sat Apr 29, 2006 3:51 pm Post subject: |
|
|
Disciple
Joined: 05 Jul 2004
Posts: 199
Location: Detroit, MI
|
Okay,
We'll stay from any mixing. While I'm sure we could remote between versions, but I doubted mixing within a cluster was going to work out. |
|
| Back to top |
|
|
| Ivans |
| Posted: Sun Apr 30, 2006 2:30 am Post subject: |
|
|
Apprentice
Joined: 03 Jan 2006
Posts: 48
Location: Hursley
|
| Quote: |
| Are there any issues or problems in using 5.3 and 6.0 together within the same cluster? |
This should work as long as you don't use the new workload balancing features.
Even if you do use the new workload balancing features, this should not trash any repositories, but the cluster workload algorithm may use a default value (e.g. CLWLRANK=0, CLWLWGHT=50, etc) instead of the actual value in rare circumstances.
I'd be very interested in hearing if anyone has had any problems using mixed V5.3 and V6 clusters, as I have not.
Cheers,
Ian |
|
| Back to top |
|
|
| vraju |
| Posted: Mon May 01, 2006 7:59 pm Post subject: |
|
|
Novice
Joined: 24 Apr 2006
Posts: 16
|
While working in windows, I encountered a strange problem..
when the cluster is created in V.5.3 and the QM is placed in V6.0(in different machine of windows), while administering the QM which is on v6.0, the explorer(MQV.5.3) hangs up..
Not sure, how many of you have faced this. |
|
| Back to top |
|
|
| Ivans |
| Posted: Tue May 02, 2006 3:02 am Post subject: |
|
|
Apprentice
Joined: 03 Jan 2006
Posts: 48
Location: Hursley
|
Using the V5.3 explorer to administrate V6 queue managers should work (although you obviously can't admin the V6 features that way). I suggest you raise a PMR for the explorer hang.
Apart from the explorer hang, did the mixed version cluster work ok?
Cheers,
Ian |
|
| Back to top |
|
|
| tleichen |
| Posted: Mon May 08, 2006 10:22 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
Not meaning to sidetrack this discussion any; but since it is of a similar nature, I thought I would put this inquiry here also.
Is there anything to be aware of if we upgrade our WAS and repository servers to 6.0 from 5.3, but have the rest of the cluster on 5.2? They are running AS/400s that are back-leveled, and cannot go beyond 5.2.
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
|
|
