Hi List ,
What strategy you guys adapt for rolling back a
database patch ( I am talking about application patch not the oracle
software patch ) . For example if some table updates or some stored procs
are going in .. how you guys backout patch if something doesn't work
after the patch . I was thinking of taking export before applying patch and
keeping it but that will be time consuming ..considering data . Other strategy
might be for each ddl there should be an undo ddl and for each dml there should
be an undo dml . but that's complicates the life considering number of changes
that might go in patch . Any other ideas ??
Bp
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: BigP
INET: big_planet_2000_at_hotmail.com
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Mon Sep 23 2002 - 16:53:23 CDT
