Re: RMAN post-structural autobackups

From: Vitalis <vitalisREMOVETHAT_at_numericable.fr>
Date: Sat, 06 Mar 2004 09:17:02 +0100
Message-Id: <pan.2004.03.06.08.16.59.890656@numericable.fr>

On Fri, 05 Mar 2004 23:00:52 +0100, Sybrand Bakker wrote:

> On Fri, 05 Mar 2004 17:48:23 +0100, Vitalis
> <vitalisREMOVETHAT_at_numericable.fr> wrote:
> 

>>Hello,
>>
>>My question is about the following circumstances in which RMAN performs a
>>control file autobackup (according to the doc.):
>>
>>After database structural changes such as adding a new tablespace,
>>altering the state of a tablespace or datafile (for example, bringing it
>>online), adding a new online redo log, renaming a file, adding a new redo
>>thread, and so forth. This type of autobackup, unlike autobackups that
>>occur in the preceding circumstances, goes only to disk. You can run
>>CONFIGURE CONTROLFILE AUTOBACKUP FOR DEVICE TYPE DISK to set a nondefault
>>disk location.
>>
>>I don't understand how, or when, RMAN gets to know about these changes. Is
>>it just by checking at the following RMAN invocation??

> 
> No of course not. It is triggered by the respective ALTER or CREATE
> command. Eg: the internal procedure to create a tablespace will call
> the procedure to backup the controlfile.

Thanks for this clarification! It goes further than what Brian explained.

I didn't think that Oracle server performs, on its own, tasks configured with RMAN. BTW is there other such "RMAN" tasks handled by the server? Received on Sat Mar 06 2004 - 02:17:02 CST