By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,334 Members | 1,266 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,334 IT Pros & Developers. It's quick & easy.

Commit the applied FixPak??

P: n/a
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

Mar 22 '07 #1
Share this Question
Share on Google+
9 Replies


P: n/a
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.
Mar 22 '07 #2

P: n/a
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...@tower.to.org.no.spam.for.mewrote:
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 -
Mar 30 '07 #3

P: n/a
Anurag wrote:
>
On Mar 22, 4:36 pm, Darin McBride
<dmcbr...@tower.to.org.no.spam.for.mewrote:
>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
Mar 30 '07 #4

P: n/a
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.)
Mar 30 '07 #5

P: n/a
Darin McBride wrote:
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.)
I think you are right.
From the AIX Commands Reference (installp command):

<quote>
When a fileset update is applied to the system, the update is installed. The
current version of that software, at the time of the installation, is saved
in a special save directory on the disk so that later you can return to that
version if desired. Once a new version of a software product has been
applied to the system, that version becomes the currently active version of
the software.
<..>
When updates are committed with the -c flag, the user is making a commitment
to that version of the software product, and the saved files from all
previous versions of the software product are removed from the system,
thereby making it impossible to return to a previous version of the software
product. Software can be committed at the time of installation by using
the -ac flags. Note that committing already applied updates does not change
the currently active version of a software product. It merely removes saved
files for previous versions of the software product.
</quote>

--
Jeroen
Mar 30 '07 #6

P: n/a
Ian
Anurag wrote:
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 :)

I concur with Darin. This is wrong.

I have committed applied fixes with the database running more times than
I can count. And I have never had an issue.

Mar 31 '07 #7

P: n/a
In article <4D********************@newsfe08.phx>,
ia*****@mobileaudio.com says...
Anurag wrote:
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 :)

I concur with Darin. This is wrong.

I have committed applied fixes with the database running more times than
I can count. And I have never had an issue.

Then you concur with Anurag, Darin said no downtime was needed.
Mar 31 '07 #8

P: n/a
Gert van der Kooij wrote:
In article <4D********************@newsfe08.phx>,
ia*****@mobileaudio.com says...
>Anurag wrote:
>>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 :)


I concur with Darin. This is wrong.

I have committed applied fixes with the database running more times
than I can count. And I have never had an issue.


Then you concur with Anurag, Darin said no downtime was needed.
And that's what Ian is agreeing with.
I guess you mix up the meaning of 'to concur' with Dutch 'concurreren'.
http://www.m-w.com/dictionary/concur

--
Jeroen
Mar 31 '07 #9

P: n/a
In article <46***********************@news.xs4all.nl>,
us****@No.Spam.Please.invalid says...
Gert van der Kooij wrote:
In article <4D********************@newsfe08.phx>,
ia*****@mobileaudio.com says...
Anurag wrote:
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 :)

I concur with Darin. This is wrong.

I have committed applied fixes with the database running more times
than I can count. And I have never had an issue.

Then you concur with Anurag, Darin said no downtime was needed.

And that's what Ian is agreeing with.
I guess you mix up the meaning of 'to concur' with Dutch 'concurreren'.
http://www.m-w.com/dictionary/concur

I guess so :) Sorry, I withdraw my comment.
Mar 31 '07 #10

This discussion thread is closed

Replies have been disabled for this discussion.