Re: Patchset 9.2.0.6 stable ?

One thing we always do ( with our old dbms )after testing and certification is to do a parallel run on all major apps. We use a test server installed with the new patchset and refresh with same production data and compare results. Depends on your environment this might not be possible because of space and user commitment issues. But we have relatively small db and we are using SAN, so acquire and release disk space is relatively easy. Most of our users are very understanding and cooperative too.

"hpuxrac" <johnbhurley_at_sbcglobal.net> wrote:

>snip
>
>Don wrote:
>> We are fairly new to Oracle and this is our first application of
>> patchset. In terms of test and validation plan, from high level
>> standpoint :
>>
>> 1. Complete backup test server.
>> 2. apply patchset to test server.
>> 3. Re-test/re-certify all applications by developers
>> 4. Test/in-house utilities/backup/maintenance jobs
>> 4. perform complete backup of production server
>> 5. test ( should be re-test ) fall back plan
>> 6. apply patchset to production server
>> 7. switch over and monitor closely
>>
>> How was your test and validation plan??
>
>Don your plan looks fine and I can't think at the moment of anything it
>doesn't have ( except more detail which I am sure you also have ).
>(For example, we use emc storage here and get disk backups on bcv's
>along with tape backups, ...).
>
>Validation on a test system before applying on production is of course
>what way too many people skip sometimes. The closer your test system
>and environment is to production, the better off you are.
>
>Make sure you have a reasonable amount of time " whatever that means in
>your environment " to understand and investigate anything unexpected
>during your steps 1,2,3,4,4, and 5.
Received on Thu Mar 17 2005 - 11:58:22 CST