Previous  |  Next ]     [ Up  |  First  |  Last ]     (Article 8 of 25)

I used to patch Oracle Applications (11.0.x) by using a well-designed spreadsheet,
that leveraged copy⁄paste to a maximum.

By designating a common place for patches, a strict naming convention, the spreadsheet used formulas to build answers to the question that adpatch normaly brings forward.

The spreadsheet kept timing information, notes, used mnemonic color-coding, had a »cleanup zip-timer« etc. Thus making it easy to perform subsequent patchning in other instances, all up to production.
It was a great succes and the element of human error was effectively kept at bay
But the method had one inherent flaw: You had to manually perform all the copy⁄pasting yourself, quite often for a prolonged time, and also keeping track of the process.

Then a reinstall of 11i (11.5.7) was performed, and after a while of using the AD-tools, it was clear that these tools had improved quite a bit, and enabled adpatch, so it can run non-interactively in a supported manner.
And since my ksh-skills also had improved a bit it was time to make a swith to the next level.
supa was designed to be an evolotionary replacement of my good old patchtemplate spreadsheets, but still enforcing the virtues of a well planned⁄structured patch methodology.