CPUJAN2009 Patch Installation and Q/A
From: Greenlaw, Sam (N-Apex Systems) <"Greenlaw,>
Date: Thu, 29 Jan 2009 09:03:11 -0700
Message-id: <DFAB39F1F2CF164D9E00C5972A62E5A5024884B5_at_emss02m22.us.lmco.com>
We are doing the Solaris 10.2.0.4 7592346 patch with RHEL to follow. README leaves issues with Best Practices:
Date: Thu, 29 Jan 2009 09:03:11 -0700
Message-id: <DFAB39F1F2CF164D9E00C5972A62E5A5024884B5_at_emss02m22.us.lmco.com>
We are doing the Solaris 10.2.0.4 7592346 patch with RHEL to follow. README leaves issues with Best Practices:
- At what point should an Instance that is monitored with Grid Control
be put in GC blackout ? Is this critical ?
- Shutdown, blackout, backup, startup-and-apply-CPU procedures, post-apply work, backup, shutdown, end-blackout, startup ?
- Guessing that an SA with some Oracle experience could be performing the patch work, can you recommend URLs that presents examples of CPU installations ?
- What do you like for an intuitive directory - OFA-happy - for storing
the patch and its unzip ?
- $ORACLE_HOME/OPatch/patch is an obvious choice. $ORACLE_BASE/admin/patch is used, too. Preferences ???
- Finally, testing after a CPU cycle. We had a suite of RAT (Real Application Test) runs, back a bit. Is there anything recommended for a Best Practices suite, today, suitable for post-install testing ?
TIA
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Jan 29 2009 - 10:03:11 CST