| Author |
Message
|
| jon |
 Posted: Thu Jul 23, 2009 5:30 pm Post subject: |
 |
|
Apprentice
Joined: 17 May 2009
Posts: 32
|
Hi Aditya & Vitor,
thanks for your reply.
Aditya : I think you are replying to "sandiksk" who raised this problem some 4 years back 
Vitor: I totally agree with your suggestion -
| Quote: |
Upgrade. v5.3 is not just outdated it's out of support.
CSD08 is actually withdrawn by IBM because it's problematic. If your client insists on using v5.3 then they should apply the latest maintenance.
|
Only problem is this server is having a total of 3 queue managers,and two of them are already running and being used by applications, I am facing problem in starting the remaining queue manager. If I go ahead with applying the latest fix pack on MQ5.3, probably I have to stop the remaining 2 queue managers which applications team wont allow.
Is there any way we can apply the latest patch without stopping MQ/queue managers? |
|
| Back to top |
|
 |
| exerk |
| Posted: Fri Jul 24, 2009 12:06 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| jon wrote: |
| ...Is there any way we can apply the latest patch without stopping MQ/queue managers? |
No...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| jon |
| Posted: Fri Jul 24, 2009 2:17 am Post subject: |
|
|
Apprentice
Joined: 17 May 2009
Posts: 32
|
Hi Exerk,
thanks for reply.
| Quote: |
jon wrote:
...Is there any way we can apply the latest patch without stopping MQ/queue managers?
exerk wrote:
No...
|
Can you suggest me an alternative, as stopping others queue managers would require management approval, which will come with lot of questions  |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Jul 24, 2009 2:22 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
There is no alternative...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| sumit |
| Posted: Fri Jul 24, 2009 2:35 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
Use your application outage window.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jul 24, 2009 4:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| exerk wrote: |
| There is no alternative... |
There's always an alternative.
Move the development qmgr onto a different box, so that it is properly not sharing the same physical hardware as queue managers that require additional approvals to stop and start.
That is, set up a new machine with proper and supported levels of software, and move the qmgr to it.
And while you're at it, set up another new machine with proper and supported levels of software to host the other qmgrs, and migrate them during proper maintenance windows using normal change control practices (including management approval). |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Jul 24, 2009 4:52 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mqjeff wrote: |
| exerk wrote: |
| There is no alternative... |
There's always an alternative. |
Clarification: There's no alternative on that server without stopping the queue managers... 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
|
|
