Re: Ocopy and Archived Logs
Date: Mon, 14 Dec 2009 08:50:15 -0700
Message-ID: <hg5mo8$4cq$1_at_news.albasani.net>
Jeremiah Wilton wrote:
> You can query something like:
>
> select l.name
> from v$archived_log l,
> v$database d
> where l.activation# = d.activation#
> and l.next_change# <
> (select min(change#)
> from v$backup);
>
> The above query lists all archivelogs older than the earliest start-
> backup time of all datafiles. You can delete logs in this list,
> assuming that:
Excellent. This is exactly what I was looking for. Thank you.
> 1. You are in fact using tablespace hot backup mode. If not, then all
> open backups are invalid.
> 2. You never want to recover to a point in time prior to the most
> recent backup using a prior backup
> 3. You are in fact copying all files that you put into backup mode
> 4. Your controlfile record keep time is longer than the age of your
> oldest archivelog.
- Correct. The database is in archivelog mode and the backups are being done within 'begin backup' and 'end backup' statement.
- Correct. Any older ocopy backups will be restored from the time they are run. Transactions logs will not be used.
- Correct. I'm using a script which loops through the tablespaces in sys.dba_tablespaces, putting them in backup mode, backing them up with ocopy, and taking them out of backup mode.
- I'm not sure. The control files are being backed up to trace, then backed up to file:
dbms_output.put_line('alter database backup controlfile to trace;'); dbms_output.put_line('alter database backup controlfile to '||''''||
copy_dest||'control.'||dbname||'.'||
to_char(sysdate,'DDMonYYHH24MI')||''''||';');
This section comes last in the backup script, just before the the logfile is switched. I'm not sure what is meant by "keeptime is longer than the age of the oldest archivelog"; does this mean the controlfile should be backed up /first/ in the script?
Thanks again,
-Gary
Received on Mon Dec 14 2009 - 09:50:15 CST