AW: RMAN fast incremental

  • From: Petr Novak <Petr.Novak@xxxxxxxxxxxx>
  • To: "harel.safra@xxxxxxxxx" <harel.safra@xxxxxxxxx>, "seekuel@xxxxxxxxx" <seekuel@xxxxxxxxx>
  • Date: Tue, 18 Jan 2011 08:38:14 +0000

Hi,

it is set with 'alter database ..'.

Check with  'select * from v$BLOCK_CHANGE_TRACKING;'

You should be aware of 

Bug 10170431  CTWR consuming lots of CPU cycles with block tracking .
Patch should be available.

Best Regards,
Petr


________________________________________
Von: oracle-l-bounce@xxxxxxxxxxxxx [oracle-l-bounce@xxxxxxxxxxxxx]&quot; im 
Auftrag von &quot;Harel Safra [harel.safra@xxxxxxxxx]
Gesendet: Dienstag, 18. Januar 2011 07:51
Bis: seekuel@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Betreff: Re: RMAN fast incremental

Block change tracking should be enabled on the production database.

Harel Safra
Sent from my phone

On Jan 18, 2011 8:01 AM, "seekuel" 
<seekuel@xxxxxxxxx<mailto:seekuel@xxxxxxxxx>> wrote:
> Hi list,
>
> May I ask for your guidance in configuring fast incremental backup.
>
> I have already setup RMAN (catalog) to run via cron level 0 on mondays and
> the rest of the days are level 1 each of the backup will have its own log
> file generated. What I an not sure is where to place the command block
> tracking changes. Is it on RMAN server or in the production server?
>
> Any idea?
>
> Thank you
--
//www.freelists.org/webpage/oracle-l


Other related posts:

  • » AW: RMAN fast incremental - Petr Novak