04-08-2005 01:26 AM
I am in the process of getting my servers up to date with the latest Gold packs along with doing patch assessments. My questions are:
What precautions do you take prior to patching?
(Do you swlist to a file prior so you know which patches you had prior?)
Besides looking at the log file which tends to be somewhat muddy when you’ve applied 50-150 patches. Is there a way to look at which patches were applied after the fact? (kind of goes to swlisting prior)
Do you relink Oracle after patching?
Looking at all the patches. It’s hard to tell if there’s really something there that could cause issues. For example something changed after patching where now I’m getting dld.sl can not find library type errors. I’m guessing it’s because a lib file was updated and now some specific oracle processes aren’t starting correctly.
Solved! Go to Solution.
04-08-2005 01:54 AM
R1: make a full OS backup with Ignite to a tape before applying any patch (specially PHKL patches)
R2: all applied patches are saved to /var/adm/sw/save. I recommend you to apply the patches by bundles downloading them from ITRC: this allow you to analyse each patch individually (reading Special Instructions, Warnings, ...)
R3: if you have a Test environment, apply patches here first and test all the Oracle apps & bd after patches
04-08-2005 02:22 AM
One of the servers I'm doing tomorrow has 122 out of the 300+ patches for the Goldpatch/HWEnablement patches selected to go. Not to mention the 77 patches patches that I pulled down from the cpm patch assessment. What are the chances that close to 200 patches it will muck something up?
Now I have 27 servers, trying to keep this as simple as possible.
We do have test/dev servers, some of my issues are the hardware platforms are in some cases not the same. Even the OS can be different. 11.0 versions 11.11. So short of reading all the patch notes for all the patches. (And really how will I know if the patch that updates /usr/lib/libxti.2 is going to break something?) I agree, patching test/dev should shake some of these loose though.
*remind me not to cut and paste from word. the squares should be '.
04-08-2005 02:23 AM
Before installing gold packs
#swlist -l fileset -a state | grep -v configured
Take ignite backup.
Open a telnet session to your system and issue shutdown command without any option to bring in single user mode ( It will make sure that all applications are down during patch installation) and you can have two sessions one on console and one on telnet window. Install patches through telnet session.
After patch installation is successful, Verify your patches with
#swlist -l fileset -a state
All patches should be in configured state. After that you should relink oracle with
04-08-2005 03:53 AM
In this case you should have a different time frame to patch each OS version group of servers...
Personaly, I never got a patch issue on Production environment simply because of this "Patch & Test before Production" strategy: I strongly recommend it!
04-08-2005 04:02 AM
I want to go back to management with sugesting to relink after doing patching. I wasn't aware if Oracle recommends this practice.
It seems like you can be as safe as possible, and reassue everyone that what your applying shouldn't break anything. But at the same time, theres always finger pointing and that "Guilty until proven innocent" feeling anytime you make so many OS level changes. I'm still investigating the dld.sl issue. Looking at the old rc.log it didn't have problems until after I patched. This stemmed from another issue where it turned out a specific oracle process didn't start, which they started by hand by fine. But of course, my patches were under the spot light.
04-08-2005 04:33 AM
04-08-2005 05:51 AM
Actually this is what I was looking for also of a way to see what patches afterwards were installed. Looks like I can do this:
hainan:root /root # swlist -a mod_date -a title | grep "Apr 7"
PHCO_28125 Thu Apr 7 14:02:05 CDT 2005 cumulative SAM/ObAM patch
PHCO_29288 Thu Apr 7 14:56:59 CDT 2005 locale library cumulative patch
Which shows me all the patches that were modified at the time I patched.
Thanks again, will follow up if anything turns up.