Re: RMAN internal`s mechanism

srivenu_at_hotmail.com (srivenu) wrote in message news:<1a68177.0403050404.624d4aa1_at_posting.google.com>...
> > How are you handling fractured blocks? Are you talking about copies
> > of datafiles that were made during a hot backup? Even then RMAN is
> > dependent on recovery with redo to fix it.
>
> RMAN backups dont suffer from split block or fractured block problem.
> RMAN first reads the blocks into its input buffers and while writing
> the data from inout buffers to output buffers, it checks for split
> blocks. If it encounters a split block, RMAN will reread that oracle
> block. RMAN also takes care of the start SCN in file headers. This is
> the reason why you need to put the Tablespaces in backup mode for RMAN
> backups.
> regards
> Srivenu

My goof on my last sentence, thanks for the clarification. I meant to say Oracle instead of RMAN there. And someone else corrected your last sentence :-)

I couldn't quite figure out if the OP was trying to update RMAN created files or what, I got the impression "or what," perhaps copies of live db files? The important point is, of course, that RMAN is smart enough to deal with fractures, and Oracle can't know if someone else copying files is that smart, hence the backup mode being more impactful.

jg

--
@home.com is bogus.
Happy Birthday Spam!  I still have my "C & S Spamming the Globe"
T-shirt!http://news.netcraft.com/archives/2004/03/05/spams_tenth_birthday_today.html