| Author |
Message
|
| PeterPotkay |
 Posted: Thu Oct 21, 2004 2:01 pm Post subject: |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
We by chance happened to apply CSD08 using the MQPINUSEOK flag, while the QM was running! Rebooted, and everything seems hunky-dory.
Is this supported? Can I really apply CSD08 to 5.3 on Windows while the QM is running, and reduce my outage Window to the time it takes to reboot?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| Tibor |
| Posted: Thu Oct 21, 2004 4:05 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| PeterPotkay wrote: |
We by chance happened to apply CSD08 using the MQPINUSEOK flag, while the QM was running! Rebooted, and everything seems hunky-dory.
Is this supported? Can I really apply CSD08 to 5.3 on Windows while the QM is running, and reduce my outage Window to the time it takes to reboot? |
I believe this isn't supported - but can work... As Jason pointed earlier: when a process or library is in the memory its won't be reloaded (generally).
But, I don't understand why developers can't share the source of cool installers at IBM  e.g. if I start the DB2 Fixpak installer this can
- list the processes and ask about it
- stop db2 services
- restart db2 services
Tibor |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Oct 21, 2004 6:34 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Tibor wrote: |
But, I don't understand why developers can't share the source of cool installers at IBM e.g. if I start the DB2 Fixpak installer this can
- list the processes and ask about it
- stop db2 services
- restart db2 services
Tibor |
I think DB2 doesn't use DLLs as much as MQ does.
But I agree.
It would be nice if, for example, the Portal Express installer would use the same methods that the Commerce Express installer uses. Because, you know, the Portal Express installer doesn't really work.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Oct 22, 2004 1:04 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Dont get me going about the install... 
The 'problems' we face are:
1. User applications still running with our libraries loaded but not connected
2. O/S has loaded com.ibm.mq.jar even for a non-MQ java pgm!
3. O/S Performance tokens are loaded and not unloaded by something
4. MQ still running (possibly as a service, possibly not)
5. Other parts of the o/s loading parts of our code (eg. MSCS)
Pre about fp6 the fixpack installer does a basic in-use check of all the files. Any it finds it couldnt replace it gives up on
fp6 (I think) tries to stop the MQ service and (I think) any qmgr started, then checks the files and gives up if any are locked
We cant stop user apps, or the o/s obviously, so the MQPINUSEOK has been documented (it was always there, just undocumented)
What this does is ignore the inuse and use the deferred installation mechanism. This means a reboot is required but the fixpack install can at least proceed.
The only 'dangerous' part about it is if a new process starts while the fixpack is installing and loads some dlls which could be replaced (ie fixpack N) but others which were in use (fixpack N-1). Other applications just do the install this way and dont worry about it, but I think IBM was just being careful. It wouldnt suprise me if this became an option on the interactive install sometime either, but certainly not in the 5.3 timeframe.
As to sharing installs, I cant comment... I agree but also know that changing the install mechanism is notorious for causing new types of problems! |
|
| Back to top |
|
|
| mqsha |
| Posted: Fri Oct 22, 2004 5:09 am Post subject: |
|
|
Novice
Joined: 10 Jun 2004
Posts: 17
|
I had similar issue on my windows boxes. I tried several way changed all MQSeries services and Windows Installer and Norton to manual and rebooted the server.
It works some times.
or
renamed the *.dll whic is failed on amqicsdn.txt file.
or
use MQPINUSEOK=1.
it works for me most of the times . |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Oct 22, 2004 5:21 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Jason, I am curious on your viewpoint: Can the QM stay running while we install the CSD, and then reboot? This would greatly reduce the outage period that the customer has to deal with.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Oct 22, 2004 5:34 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Can it - possibly. However I really wouldnt recommend it. As I said, if something starts up while the install is going on, and pulls in a dll which has been replaced, then you are in trouble (possibly).
The real answer is something like a fully deferred option, ie flag every file to be replaced post-restart. Then it would be completely safe... I'll have to talk to someone about that!
Jaosn |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Oct 22, 2004 5:42 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I thought I remember a comment at the all-hands session of the technical conference about updating the software without having to bring the qmgr down. It was supposed to be a requirement that was being looked at without any promises being given on its being done.
Of course, I'm older than I used to be, and they may have been talking about something else.... |
|
| Back to top |
|
|
|
|
