Commit the applied FixPak??
in [DB2]
|
From: Anurag on 22 Mar 2007 09:54 ENVIRONMENT: ============ (1) AIX 5.2 ML 8 and AIX 5.3 TL 4. (2) DB2 ESE on some servers and DB2 Connect Enterprise Edition on others. QUESTION: ========= I upgrade DB2 on some 15 Production servers using 'installFixPak -ay', from 8.1.4 to 8.1.11. All upgrade steps successful, goal achieved much before time, mgmt pats my back!! Now, I need to COMMIT the upgrade. I would not like to request another downtime; **** Can I COMMIT the upgrades without any disruption to applications / users using the existing DB2? **** Do I require downtime to COMMIT? Help very much appreciated...Anurag
From: Darin McBride on 22 Mar 2007 11:36 Anurag wrote: > ENVIRONMENT: > ============ > (1) AIX 5.2 ML 8 and AIX 5.3 TL 4. > (2) DB2 ESE on some servers and DB2 Connect Enterprise Edition on > others. > > QUESTION: > ========= > I upgrade DB2 on some 15 Production servers using 'installFixPak -ay', > from 8.1.4 to 8.1.11. > All upgrade steps successful, goal achieved much before time, mgmt > pats my back!! > > Now, I need to COMMIT the upgrade. I would not like to request another > downtime; > **** Can I COMMIT the upgrades without any disruption to > applications / users using the existing DB2? Yes > **** Do I require downtime to COMMIT? No > Help very much appreciated...Anurag Please see the AIX documentation on committing with installp and/or smit and/or smitty.
From: Anurag on 30 Mar 2007 09:00 I have response from IBM (had opened a PMR) on these 2 questions. Lemme share this with you all: > > **** Can I COMMIT the upgrades without any disruption to applications / users using the existing DB2? NO, unless it's a Client Installation. > > **** Do I require downtime to COMMIT? YES. You need db2stop and ipclean before COMMITing. So, after all the accolades from management, I now have to request downtime for COMMIT (maybe I do that over Easter weekend and nobody makes a fuss :) ....anurag On Mar 22, 4:36 pm, Darin McBride <dmcbr...(a)tower.to.org.no.spam.for.me> wrote: > Anuragwrote: > > ENVIRONMENT: > > ============ > > (1) AIX 5.2 ML 8 and AIX 5.3 TL 4. > > (2) DB2 ESE on some servers and DB2 Connect Enterprise Edition on > > others. > > > QUESTION: > > ========= > > I upgrade DB2 on some 15 Production servers using 'installFixPak -ay', > > from 8.1.4 to 8.1.11. > > All upgrade steps successful, goal achieved much before time, mgmt > > pats my back!! > > > Now, I need to COMMIT the upgrade. I would not like to request another > > downtime; > > **** Can I COMMIT the upgrades without any disruption to > > applications / users using the existing DB2? > > Yes > > > **** Do I require downtime to COMMIT? > > No > > > Help very much appreciated...Anurag > > Please see the AIX documentation on committing with installp and/or smit > and/or smitty.- Hide quoted text - > > - Show quoted text -
From: The Boss on 30 Mar 2007 14:44 Anurag wrote: > > On Mar 22, 4:36 pm, Darin McBride > <dmcbr...(a)tower.to.org.no.spam.for.me> wrote: >> Anuragwrote: >>> ENVIRONMENT: >>> ============ >>> (1) AIX 5.2 ML 8 and AIX 5.3 TL 4. >>> (2) DB2 ESE on some servers and DB2 Connect Enterprise Edition on >>> others. >> >>> QUESTION: >>> ========= >>> I upgrade DB2 on some 15 Production servers using 'installFixPak >>> -ay', >>> from 8.1.4 to 8.1.11. >>> All upgrade steps successful, goal achieved much before time, mgmt >>> pats my back!! >> >>> Now, I need to COMMIT the upgrade. I would not like to request >>> another >>> downtime; >>> **** Can I COMMIT the upgrades without any disruption to >>> applications / users using the existing DB2? >> >> Yes >> >>> **** Do I require downtime to COMMIT? >> >> No >> >>> Help very much appreciated...Anurag >> >> Please see the AIX documentation on committing with installp and/or >> smit and/or smitty. >> > > I have response from IBM (had opened a PMR) on these 2 questions. > Lemme share this with you all: >>> **** Can I COMMIT the upgrades without any disruption to >>> applications / users using the existing DB2? > NO, unless it's a Client Installation. > >>> **** Do I require downtime to COMMIT? > YES. You need db2stop and ipclean before COMMITing. > > So, after all the accolades from management, I now have to request > downtime for COMMIT (maybe I do that over Easter weekend and nobody > makes a fuss :) > > ...anurag Alternatively, you could just postpone the COMMIT until you have to bring DB2 down for some other reason. DB2 will run just happily in APPLY mode, without COMMITing. In case you want to do the COMMIT anyway, I did it only a couple of days ago, and it took only 15 minutes. -- Jeroen
From: Darin McBride on 30 Mar 2007 16:13
Anurag wrote: > I have response from IBM (had opened a PMR) on these 2 questions. Can you send me the PMR number? Was it against DB2 or AIX? These responses don't make a lot of sense to me - so I'd like to pursue it. > Lemme share this with you all: >> > **** Can I COMMIT the upgrades without any disruption to applications / >> > users using the existing DB2? > NO, unless it's a Client Installation. > >> > **** Do I require downtime to COMMIT? > YES. You need db2stop and ipclean before COMMITing. > > So, after all the accolades from management, I now have to request > downtime for COMMIT (maybe I do that over Easter weekend and nobody > makes a fuss :) Of course, it never hurts to be safe rather than sorry, but, still - it'd be nice to be able to just commit. (Nothing in the fixpack readme talks about shutting down the server prior to committing, which I presume would be there if DB2 developers knew of any reason why you would need to do so.) |