RE: Question of degrees in Oracle DB recovery

Stephen,

Apart from being able to keep your DB up-and-runnng 24x7, doing hot backups 
instead of cold backups also preserves the carefully optimize SQL 
statements in your SQL area, not to forget all your caches etc.

At a site I'm working (almost) every database gets shut down on Sunday. The 
spikes in the I/O graphs at Monday morning are tremendous: when everyone 
comes in, Oracle has to re-optimize all statements, and refill all caches.

I think it was Connor McDonald (www.oracledba.co.uk) who discussed this 
topic two years ago at UKOUG in Birmingham. Oracle is at its best in 
optimizing I/O and memory-usage. Don't waste that by breaking up a nice and 
stable situation, reached at the end of the day, by shutting down the 
database because of doing cold backups.

When you perform OS/backups (non-RMAN), be aware that seldomly visited 
datablocks are not validated. Although this doesn't happen too often with 
today's HW, verification by creating exports or running dbverify will help 
you to prevent corrupted datablocks from going unnoticed beyond a point 
that you cannot recover them from remaining backups.

Regards, Carel-Jan

===
If you think education is expensive, try ignorance. (Derek Bok)
===

At 12:29 PM 6/29/2004 -0400, you wrote:
 >
 >Bottom line:
 >
 >4.)  Once you're in archive log mode, you don't *need* to do hot =
 >backups,
 >     it is nice to have that ability and not impact database uptime.
 >5.)  Consider RMAN, if at all possible.  RMAN is the future, and it
 >     also helps make your backups less error-prone.
 >
 >Hope that helps,
 >
 >-Mark




----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Other related posts: