Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: RMAN internal`s mechanism

Re: RMAN internal`s mechanism

From: Vitalis <vitalisREMOVETHAT_at_numericable.fr>
Date: Fri, 05 Mar 2004 13:57:41 +0100
Message-ID: <pan.2004.03.05.12.57.41.312076@numericable.fr>


On Fri, 05 Mar 2004 04:04:20 -0800, srivenu wrote:

>> 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

Srivenu, thanks for your explanation about RMAN blocks handling. I just want to correct your last sentence: the user must not put the tablespaces in backup mode for RMAN backups. Received on Fri Mar 05 2004 - 06:57:41 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US