RE: patch set testing
- From: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxxxxx>
- To: <Josh.Collier@xxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 3 Sep 2004 14:28:51 -0400
Josh,
Guidelines we follow are:
1) When moving a major release, like 8.1.7 to 9.2.0, always go
with the newest patchset that's out, in this case, 9.2.0.5.
2.) If just bumping up a patchset, don't go there, unless you
need to fix a problem that you actually have. If you're going
from 9.2.0.2 to 9.2.0.5 just cause 9.2.0.5 is there, that's not
a reason to go.
3.) Regardless of if we are going from one major release to
another, we always try to roll it out with the release of our
product, so that it gets a full complement of QA testing,=20
capacity testing and soak testing.
4.) We try to stay away from one-off patches all together,
but, sometimes you can't. In that case, we'll roll it into
our pre-prod environment, run a 3-4 hour cap test, and if that
succeeds, we'll run a weekend long soak test, to hopefully=20
catch memory leaks, and those types of problems.
Patching is always an art and never a science. You just mitigate
what you can and hope for the best. (And be prepared for the worst!)
Hope that helps,
-Mark
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Josh Collier
Sent: Friday, September 03, 2004 2:14 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: patch set testing
Greetings,
=20
Is there a routine you follow for testing patch sets, such as an upgrade
from 9.2.0.3 to 9.2.0.5?
=20
thanks,
=20
Josh C.=20
--
To unsubscribe - =
mailto:oracle-l-request@xxxxxxxxxxxxx&subject=3Dunsubscribe=20
To search the archives - //www.freelists.org/archives/oracle-l/
--
To unsubscribe - mailto:oracle-l-request@xxxxxxxxxxxxx&subject=unsubscribe
To search the archives - //www.freelists.org/archives/oracle-l/
Other related posts:
