[OAUGNetDBA]-Re: Question on merging patches

["Stauffer, Robert G" <rstauffer@decommunications.com>]

My 2 cents:  The first time I apply new patches, I usually apply each
one individually to our dev environment.  Why?  Because I find it's
easier to troubleshoot patch problems.  More than once I'm glad I did
because researching a problem in Metalink for an individual patch number
is often easier than trying to do so with a merged patch.  And once all
of the patches go in successfully, then I merge them and apply the
merged patches to a restored dev environment or to the test/UAT
environment.  It may take a little extra time, but I've found that I end
up applying the patches numerous times anyway in the dev environment to
work out various patch or functional issues.



Bob Stauffer
DBA
D&E Communications
Ephrata, PA
rstauffer@decommunications.com
717-738-8737
-----Original Message-----
From: OAUG Net DBA listserver [mailto:OAUGNetDBA@oaug.com] On Behalf Of
James Morrow
Sent: Tuesday, June 03, 2008 17:09
To: OAUG Net DBA listserver
Subject: [OAUGNetDBA]-Re: Question on merging patches

Syed --

I would say "NO" to your supposition here.

Think about it this way:

First of all, you're going to apply the patches on your
list no matter what.  You've already made the decision to
apply patch "X".  In doing so, applying the prereqs is not
an "option".

So, you go to apply the patches.  Whether or not you merge
them is immaterial to your troubleshooting methodology if
you encounter a failure.

When you encounter that failure, say one of the workers
fails on a task... your SR will state "I'm applying these
patches... the worker fails on job abcdefg.sql... the
file version is 115.21".  Simple as that.  The troubleshooting
is not of the patch itself, but of the individual bit
of code that fails.

When you merge patches, the "most current" version of
all delivered code is put into the merged patch.  The idea
here is that you can avoid re-running the same (or gradually
newer) versions of code and, by doing so, eliminate duplication
of effort.

The adpatch utility (particularly since AD.H) divides the
components of the patch into "phases" to ensure that dependencies
within the processes are satisfied.

For example (gross oversimplification):
  Execute create table scripts before doing create view scripts.

I've been doing implementations, upgrades, and "patch current"
exercises at any number of clients for quite some time.  Merging
patches has been a very reliable tool for cutting the required
downtime...

-- James

On Tue, Jun 3, 2008 at 3:47 PM, Syed Aleem <syed.aleem@aarcorp.com>
wrote:
> Thanks guys for your reply. So, basically we coming back to the basics
> that all levels of patches such as pre-req, patch & post-install are
> applying separately to avoid any possible errors.
>
> Thanks,
>
> Syed.
>
> -----Original Message-----
> From: OAUG Net DBA listserver [mailto:OAUGNetDBA@oaug.com] On Behalf
Of
> Chad Nester
> Sent: Tuesday, June 03, 2008 3:38 PM
> To: OAUG Net DBA listserver
> Subject: [OAUGNetDBA]-Re: Question on merging patches
>
> In general I don't think you can merge pre-req patches into the patch
> they go with.  At least you probably shouldn't.  It's possible it
might
> work in some cases, but not in others.  I generally just avoid doing
it.
>
> Chad A. Nester
> Oracle EBS Practice
> Terillium, Inc.
> Cincinnati, OH
> Cell: 513-382-9397
> cnester@terillium.com
>
>> -----Original Message-----
>> From: OAUG Net DBA listserver [mailto:OAUGNetDBA@oaug.com] On Behalf
> Of
>> Syed Aleem
>> Sent: Tuesday, June 03, 2008 4:23 PM
>> To: OAUG Net DBA listserver
>> Subject: [OAUGNetDBA]-Question on merging patches
>>
>>
>> Hello everyone:
>>
>> I am in process of installing the latest INV rollup patches on
> 11.5.10.2
>> application to the current level.  The INV rollup 7 required
>> pre-requites and post-install patches.  Basically my question is can
I
>> merge pre-requites, INV rollup 7 and the post-install patches and
>> applied them as a single patch.  Please let me this is doable or not,
> or
>> is there any dependency issue with this merge
>>
>> Thanks in advance.
>>
>>
>> Syed.
>>
>>
>>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to the mailing
> list
>> <OAUGNetDBA@oaug.com>.
>> To unsubscribe, E-mail to: <OAUGNetDBA-off@oaug.com>
>> To switch to the FEED mode, send any message to
> <OAUGNetDBA-feed@oaug.com>
>> To switch to the DIGEST mode, E-mail to <OAUGNetDBA-digest@oaug.com>
>> To switch to the INDEX mode, E-mail to <OAUGNetDBA-index@oaug.com>
>> Send administrative queries to  <OAUGNetDBA-request@oaug.com>
>
>
> #############################################################
> This message is sent to you because you are subscribed to the mailing
> list <OAUGNetDBA@oaug.com>.
> To unsubscribe, E-mail to: <OAUGNetDBA-off@oaug.com>
> To switch to the FEED mode, send any message to
> <OAUGNetDBA-feed@oaug.com>
> To switch to the DIGEST mode, E-mail to <OAUGNetDBA-digest@oaug.com>
> To switch to the INDEX mode, E-mail to <OAUGNetDBA-index@oaug.com>
> Send administrative queries to  <OAUGNetDBA-request@oaug.com>
>
>
>
> #############################################################
> This message is sent to you because you are subscribed to the mailing
list <OAUGNetDBA@oaug.com>.
> To unsubscribe, E-mail to: <OAUGNetDBA-off@oaug.com>
> To switch to the FEED mode, send any message to
<OAUGNetDBA-feed@oaug.com>
> To switch to the DIGEST mode, E-mail to <OAUGNetDBA-digest@oaug.com>
> To switch to the INDEX mode, E-mail to <OAUGNetDBA-index@oaug.com>
> Send administrative queries to  <OAUGNetDBA-request@oaug.com>
>
>



--
----------------------------------------------------------------------
James J. Morrow | Senior Oracle Applications DBA
morrow.james <at> gmail <dot> com

#############################################################
This message is sent to you because you are subscribed to the mailing
list <OAUGNetDBA@oaug.com>.
To unsubscribe, E-mail to: <OAUGNetDBA-off@oaug.com>
To switch to the FEED mode, send any message to
<OAUGNetDBA-feed@oaug.com>
To switch to the DIGEST mode, E-mail to <OAUGNetDBA-digest@oaug.com>
To switch to the INDEX mode, E-mail to <OAUGNetDBA-index@oaug.com>
Send administrative queries to  <OAUGNetDBA-request@oaug.com>


**DISCLAIMER
This e-mail message and any files transmitted with it are intended for the use of the individual or entity to which they are addressed and may contain information that is privileged, proprietary and confidential. If you are not the intended recipient, you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received this communication in error, please notify the sender and delete this e-mail message. The contents do not represent the opinion of D&E except to the extent that it relates to their official business.

#############################################################
This message is sent to you because you are subscribed to the mailing list <OAUGNetDBA@oaug.com>.
To unsubscribe, E-mail to: <OAUGNetDBA-off@oaug.com>
To switch to the FEED mode, send any message to <OAUGNetDBA-feed@oaug.com>
To switch to the DIGEST mode, E-mail to <OAUGNetDBA-digest@oaug.com>
To switch to the INDEX mode, E-mail to <OAUGNetDBA-index@oaug.com>
Send administrative queries to  <OAUGNetDBA-request@oaug.com>