Previous  |  Next ]     [ Up  |  First  |  Last ]     (Article 9 of 25)
Tips and Tricks

Do take a look at these resources for nice scripts to further automate the overall patchproces:
Tanel Põder has a very fine script named that lets you further wrap other scripts and commands.
It can be found inside http:⁄⁄⁄11idowntime.doc as Appendix B: Applications shell scripting
I use it in a slightly tweaked version: I have to supply a keyword to really start processing (just for sake of extra saftety), and since adpatch needs special consideration in a »restart scenario« (and supa can deal with that)  I have turned off the restarting capability.
No doubt you're already acquainted with manuel patchdownload, using the MetaLink web-interface,
but then you need to re-upload to your UNIX-box afterwards (if not using wget directly).
There's another neat alternative from the superb 11i-Newsletter from Solution Beacon.
Do have look at http:⁄⁄⁄SBNewsletter2002June.pdf
and read the article 'Automated Patch Download Utility'
This script could easily be tweaked.
I have tweaked so that NLS patches for my language gets downloaded in the same go.

A nice simple harmless patch to test with is:
The active part of\2647958\ad\patch\115\sql\adtsttmp.sql
is just a select * from dual;

Consider using an external ticket⁄task⁄issue system (with unique numbers)
Place the downloaded patches inside a subdirectory, named after the ticketnumber.
It's much more manageable this way, and easier to avoid ambiguity when dealing with other staff⁄testers⁄end-users.
(Do have a look at »Tasks« or similar)

supa sends a small mail if a patchrun gets into trouble, and so it's ideal to be monitored by a PDA polling every x minutes, instead of beeing glued to the screen.
(actual footage)