>I am considering the appropriate way to do database >corruption prevention. > >Should I use one or more of the following as a >proactive measure ? > a) Export > b) DBVerify > c) Analyze table <table_name> validate structure >cascade > >Any advice ? > >Thanks, > >PH >
Pui Ho, The only way you can be 'proactive' concerning corruption is to have a sound backup strategy - if you really feel nervous about your hardware, first change it, and then use archive logging and the rest; export is a bad solution, because it will be long to restore. By definition, a corruption doesn't give any warning (it's even worth than earthquakes). If you want to be very reactive, set something to regularly scan your alert.log file. Regards, Stephane Faroult Oriole -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Stephane Faroul INET: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] (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).
