Backup archivelog-limit

Is there any way to limit the archive log file back up, I don’t want to take all the archive logs generated since it reaches 80 to 90 GB and more than 100 files. Backup time takes more than hour to complete and also it affects the performance of other process. I want take only 10 or 20 files at the time so that I can reduce the backup time during batch process, at the same time it solves my space issue.
I am using the following script and it takes all the archive logs exist.
backup as compressed backupset
filesperset 20
format $BKUP_FORMAT
archivelog all
delete input;

There's no point in arbitrarily backing up only 10 or 20 archivelogs. You wouldn't be able to RECOVER the database (to a point in time) from a backup if you miss even one archivelog from the backup.
Your only option for backps is to include "plus archivelog" when you "backup database" --- but that means you cannot recover to any point other than the time of the backup. And periodically delete archivelogs during your batch job, but add "crosscheck archivelog all" and "delete noprompt expired" in your backup script so that RMAN doesn't attempt to backup the deleted archivelogs.
This is not a strategy I would recommend.
The better methods would be to :
a. Increase disk space for archivelogs
b. Find out the reason for high rate of redo generation (e.g. some processes repeatedly doing delete-insert of all rows in a "working" table) and fix the batch job (e.g. "can the delete-insert" be replaced by "truncate-insertAPPEND ?" if it is a "working" table holding only transient data that can be redone" ?)
Hemant K Chitale

Similar Messages

How can I backup archivelog generated in the last 5 minutes ?

Version: 11.2.0.3
Platform : RHEL 6.2
How can I backup archivelog generated in the last 5 minutes ? Following is what I've attempted so far ?
RMAN> backup archivelog all format '/rman_backups/Nov21Bkp/archiveTest_%U' UNTIL TIME 'sysdate-5/1440';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "until": expecting one of: "archivelog, auxiliary, backupset, backup, channel, controlfilecopy, copy, current, database, datafilecopy, datafile, db_recovery_file_dest, delete, diskratio, filesperset, force, format, from, include, keep, maxsetsize, noexclude, nokeep, not, plus, pool, recovery, reuse, section, skip readonly, skip, spfile, tablespace, tag, to, comma, (, ;"
RMAN-01007: at line 1 column 81 file: standard input
RMAN> backup archivelog all UNTIL TIME 'sysdate-5/1440' format '/rman_backups/Nov21Bkp/archiveTest_%U';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "until": expecting one of: "archivelog, auxiliary, backupset, backup, channel, controlfilecopy, copy, current, database, datafilecopy, datafile, db_recovery_file_dest, delete, diskratio, filesperset, force, format, from, include, keep, maxsetsize, noexclude, nokeep, not, plus, pool, recovery, reuse, section, skip readonly, skip, spfile, tablespace, tag, to, (, ;"
RMAN-01007: at line 1 column 23 file: standard input

HemantKChitale wrote:
You shouldn't specify both "ALL" and "FROM/UNTIL TIME"
Also if you want the archivelogs generated in the last 5 minutes, you should be using FROM TIME.
If you want the archivelogs generated until 5minutes ago (and not the latest archivelogs), you should be using UNTIL TIME.
Hemant K Chitale
I've wondered about the utility of the FROM and UNTIL options for backup of archivelogs. If one is going to back them up, why would one use an option that distinctly introduces the possibility of having gaps - un-backed-up archivelogs? Why would one not simply back up all archives not previously backed up at least once?
I'm sure you'll give me a valid response for a situation for which my imagination fails to see.

Why Backup database then backup archivelog from time...

Dear Experts,
I found in one of our rman scripts the 2 following statements:
backup database;
backup archivelog from time 'SYSDATE -8';
It seems to me that a "backup database plus archivelog;" is more simple/accurate instead of these 2 lines as the retention windows is defined (5 days) for this DB so rman will manage the retention of datafiles and archived log, isn't it ?
Why this separate statement for the archivelog ? I find it redondant but is it...
Any advice is as usual greatly appreciated.
Best Regards,
Guillaume

You are right. The use of backup database plus archivelog; is much better and you are sure that you backup all archived log you need.
Probably that is an old script, previous version or the responsable of this script didn't know RMAN so good and the option you posted.
Bye, Aron

Backup archivelog all and backup archivelog in rman back

Hi,
Whats the difference between backup archivelog all and backup archivelog in rman backup.

Please find below explanation from the online documentation;
+"+
+If you specify BACKUP ARCHIVELOG ALL, then RMAN backs up exactly one copy of each distinct log sequence number. For example, if you archive to multiple destinations, RMAN backs up one copy of each log sequence number—not each copy of each log sequence number. For other commands, such as DELETE ALL does refer to every log, even duplicate log sequences.+
+"+
Hope That Helps.
Ogan
Edited by: Ogan Ozdogan on 27.Tem.2010 00:38
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta007.htm#RCMRF107

Backup archivelog all

Hi,
Whats the difference between backup archivelog all and backup archivelog using rman.

I think i have answered such question before, strange :)
Anyway please find below link to read something about the backup command;
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta007.htm#RCMRF107
+"+
+If you specify BACKUP ARCHIVELOG ALL, then RMAN backs up exactly one copy of each distinct log sequence number. For example, if you archive to multiple destinations, RMAN backs up one copy of each log sequence number—not each copy of each log sequence number. For other commands, such as DELETE ALL does refer to every log, even duplicate log sequences.+
+"+
Hope That Helps.
Ogan

Should we backup Archivelogs for ad-hoc Cold backups ?

B version: 11.2
OS version : Solaris 5.10
Below is the script we use for ad-hoc cold backups. Is there a need to take the backup of archivelogs when we do the cold backup ?
Sometimes archivelog backup piece's size is bigger than the backup piece containing the full backup of the DB itself ! So, too much disk space is wasted.
The script we use
run
allocate channel t1 type disk;
sql 'alter system archive log current';
shutdown immediate;
startup mount;
backup full database format='/mypath/ORCL_full_%U_%T.bkp' tag='ORCL_full';
backup archivelog all tag='arch_bkp' format='/mypath/ORCL_BKP/arch_%U_%T.bkp' delete input;
release channel t1;
}

Hello;
A cold backup is a consistent state. So you don't have to back them up. No new archived logs generated during the backup either so you are still OK.
For other types of RMAN backup you ALWAYS want this. This guarantees that datafile backups taken during the command are recoverable to a consistent state.
Best Regards
mseberg

RMAN backup archivelog all delete input

Hello DBAs,
what does this command will do?
RMAN> backup archivelog all delete input;
DN

I have set cron job for RMAN> backup archivelog all delete input; and its work.
But I got following message in my log file.
Please give ur feed back.
Recovery Manager: Release 10.1.0.4.0 - 64bit Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
RMAN>
connected to target database: SIDNAME (DBID=XXXXXXXX)
using target database controlfile instead of recovery catalog
RMAN>
Starting backup at 10-FEB-06
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=269 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=268 devtype=DISK
channel ORA_DISK_1: starting compressed archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=5701 recid=2412 stamp=581958928
input archive log thread=1 sequence=5702 recid=2413 stamp=581961105
input archive log thread=1 sequence=5703 recid=2414 stamp=581964532
input archive log thread=1 sequence=5704 recid=2415 stamp=582025325
input archive log thread=1 sequence=5705 recid=2416 stamp=582029976
input archive log thread=1 sequence=5706 recid=2417 stamp=582031922
channel ORA_DISK_1: starting piece 1 at 10-FEB-06
channel ORA_DISK_2: starting compressed archive log backupset
channel ORA_DISK_2: specifying archive log(s) in backup set
input archive log thread=1 sequence=5707 recid=2418 stamp=582037207
input archive log thread=1 sequence=5708 recid=2419 stamp=582038471
input archive log thread=1 sequence=5709 recid=2420 stamp=582043538
input archive log thread=1 sequence=5710 recid=2421 stamp=582048518
input archive log thread=1 sequence=5711 recid=2422 stamp=582055205
channel ORA_DISK_2: starting piece 1 at 10-FEB-06
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/10/2006 18:00:
12
ORA-19502: write error on file "/u02/backup/backup_6ehb2t97_1_1", blockno 6145 (
blocksize=512)
ORA-27063: number of bytes read/written is incorrect
IBM AIX RISC System/6000 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576
channel ORA_DISK_1 disabled, job failed on it will be run on another channel
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 02/10/2006 18:00:
12
ORA-19502: write error on file "/u02/backup/6fhb2t97_1_1", blockno 6145
(blocksize=512)
ORA-27063: number of bytes read/written is incorrect
IBM AIX RISC System/6000 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576
channel ORA_DISK_2 disabled, job failed on it will be run on another channel
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/10/2006 18:00:
12
ORA-19502: write error on file "/u02/backup/backup_6ehb2t97_1_1", blockno 6145 (
blocksize=512)
ORA-27063: number of bytes read/written is incorrect
IBM AIX RISC System/6000 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576
RMAN>
Recovery Manager complete.
DN

Backup archivelog all delete all input

RMAN> backup archivelog all delete all input;
i have backed up all my archivelogs using the above command, but after the backup archivelogs are not deleted from its default location .ie my default archive location is '/oracle/archive' . After executing the above command, I can see all the archivelogs still available in that location. why is it so
Db:10.2.0
OS: solaris 10
Edited by: user13364377 on Aug 22, 2010 10:44 AM

>
My control_file_record_keep_time is 7 days. My understanding is that when we specify the below command,
Rman>backup archivelog all delete all input;
rman will backup all the archive logs(one copy of each log sequece) from the archive location and then delete all the archive logs from the archive location. is it not correct?
>
That is generally right. But that assumes that RMAN knows about these archivelogfiles. It knows about them because of entries in the controlfile. If they are nolonger present - RMAN will not know them and not Backup & delete them.
Kind regards
Uwe Hesse
http://uhesse.wordpress.com

Backup archivelog all (RMAN)

For the first time Rman archive log backup, say for example log sequence 100 through 200 was backed.
After few days, log sequence has increased to 267, now if i run the same archive log backup command will rman backup 100 through 267 or 201 through 267. Am bit confused with this.
Help me
kumareshan

So i need to configure retention policy (Recovery window or redundancy) so that after certain period of time entry will be removed from the catalog so that RMAN will not backup the archived logs again.. Am i right??Partially.
You need to configure the retention policy AND add a instructions to delete the backuped archivelogs, with 'delete archivelog (all)'.

Rman error when i am doing backup archivelog delete input

archive log filename=+FRA01/osondemand/archivelog/2012_02_27/thread_2_seq_15028.7182.776323223 recid=122876 stamp=77
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 02/27/2012 05:23:14
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 3: ORA-00603: ORACLE server session terminated by fatal error
ORA-04030: out of process memory when trying to allocate 272 bytes (PL/SQL DIANA,PTG: No
10.2.04
windows
two node rac
please help me with above error
thanks for help

Hi;
Duplicate post:
rman error when taking backup archivelog all delete input
Please close your othere thread as answered and keep updating your other thread here
Regard
Helios

Rman error when taking backup archivelog all delete input

archive log filename=+FRA01/osondemand/archivelog/2012_02_27/thread_2_seq_15028.7182.776323223 recid=122876 stamp=77
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 02/27/2012 05:23:14
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 3: ORA-00603: ORACLE server session terminated by fatal error
ORA-04030: out of process memory when trying to allocate 272 bytes (PL/SQL DIANA,PTG: No
10.2.04
windows
two node rac
please help me with above error
thanks for help

Hi;
Duplicate post
Re: rman error when i am doing backup archivelog delete input
Regard
Helios

Backup archivelog in flash recovery area

Hi,
I want to backup my archivelogs in specified directory but when i do a backup rman my archivelog are backuped in my FRA.
Why ???
Regards

848546 wrote:
Hi,
I want to backup my archivelogs in specified directory but when i do a backup rman my archivelog are backuped in my FRA.
Why ???
This is default behavior but you can use format clause like
backup archivelog all format 'path\arch_s%s_p%p';

Backup archivelogs from different location

DB : 10.2.0.4
OS : HEHL5
due to space issue i moved the archived to different location from log_archive_dest_1.
is it possible to backup the archivelogs from different location as i moved them?
Thanks.

My bad , it's not a must! Please see,
bash-3.2$ ls
o1_mf_1_34_8jk60c7b_.arc o1_mf_1_35_8jkz3p0l_.arc o1_mf_1_36_8jlcqpky_.arc
bash-3.2$ mkdir /tmp/archivelognewloc
bash-3.2$ cp *.* /tmp/archivelognewloc
bash-3.2$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jan 30 14:40:17 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
allconnected to target database: **** (DBID=1228973204)
RMAN>
RMAN> catalog start with '/tmp/archivelognewloc';
searching for all files that match the pattern /tmp/archivelognewloc
List of Files Unknown to the Database
=====================================
File Name: /tmp/archivelognewloc/o1_mf_1_36_8jlcqpky_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_35_8jkz3p0l_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_34_8jk60c7b_.arc
Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /tmp/archivelognewloc/o1_mf_1_36_8jlcqpky_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_35_8jkz3p0l_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_34_8jk60c7b_.arc
RMAN>
Update : A little better demo
SQL*Plus: Release 11.2.0.1.0 Production on Wed Jan 30 15:00:32 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
SQL> alter system checkpoint;
System altered.
SQL> alter system switch logfile;
System altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options
bash-3.2$ ls
o1_mf_1_38_8jldnkog_.arc o1_mf_1_40_8jlfdnph_.arc
o1_mf_1_39_8jlfdmoq_.arc o1_mf_1_41_8jlff2nn_.arc
bash-3.2$ pwd
/u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30
[root@EDHDR3P0 ~]# ls /tmp/archivelognewloc/
[root@EDHDR3P0 ~]# exit
logout
bash-3.2$
bash-3.2$
bash-3.2$ pwd
/u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30
bash-3.2$ ls
o1_mf_1_38_8jldnkog_.arc o1_mf_1_40_8jlfdnph_.arc
o1_mf_1_39_8jlfdmoq_.arc o1_mf_1_41_8jlff2nn_.arc
bash-3.2$ ls /tmp/archivelognewloc/
bash-3.2$ ls -l /tmp/archivelognewloc/
total 0
bash-3.2$ cp * /tmp/archivelognewloc/
bash-3.2$ ls -l /tmp/archivelognewloc/
total 3620
-rw-r----- 1 oracle oinstall 549888 Jan 30 15:02 o1_mf_1_38_8jldnkog_.arc
-rw-r----- 1 oracle oinstall 3117568 Jan 30 15:02 o1_mf_1_39_8jlfdmoq_.arc
-rw-r----- 1 oracle oinstall    1024 Jan 30 15:02 o1_mf_1_40_8jlfdnph_.arc
-rw-r----- 1 oracle oinstall   19456 Jan 30 15:02 o1_mf_1_41_8jlff2nn_.arc
bash-3.2$ pwd
/u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30
bash-3.2$ rm -rf *
bash-3.2$ ls
bash-3.2$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jan 30 15:03:13 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: AMER (DBID=1228973204)
RMAN> backup archivelog all;
Starting backup at 30-JAN-13
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=151 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 01/30/2013 15:03:32
RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
ORA-19625: error identifying file /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_38_8jldnkog_.arc
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
RMAN> catalog start with '//tmp/archivelognewloc';
searching for all files that match the pattern //tmp/archivelognewloc
List of Files Unknown to the Database
=====================================
File Name: /tmp/archivelognewloc/o1_mf_1_39_8jlfdmoq_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_41_8jlff2nn_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_40_8jlfdnph_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_38_8jldnkog_.arc
Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /tmp/archivelognewloc/o1_mf_1_39_8jlfdmoq_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_41_8jlff2nn_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_40_8jlfdnph_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_38_8jldnkog_.arc
RMAN> backup archivelog all;
Starting backup at 30-JAN-13
current log archived
using channel ORA_DISK_1
archived log /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_38_8jldnkog_.arc not found or out of sync with catalog
trying alternate file for archived log of thread 1 with sequence 38
archived log /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_39_8jlfdmoq_.arc not found or out of sync with catalog
trying alternate file for archived log of thread 1 with sequence 39
archived log /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_40_8jlfdnph_.arc not found or out of sync with catalog
trying alternate file for archived log of thread 1 with sequence 40
archived log /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_41_8jlff2nn_.arc not found or out of sync with catalog
trying alternate file for archived log of thread 1 with sequence 41
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=38 RECID=45 STAMP=806079846
input archived log thread=1 sequence=39 RECID=42 STAMP=806079846
input archived log thread=1 sequence=40 RECID=44 STAMP=806079846
input archived log thread=1 sequence=41 RECID=43 STAMP=806079846
input archived log thread=1 sequence=42 RECID=41 STAMP=806079812
input archived log thread=1 sequence=43 RECID=46 STAMP=806079851
channel ORA_DISK_1: starting piece 1 at 30-JAN-13
channel ORA_DISK_1: finished piece 1 at 30-JAN-13
piece handle=/u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T150411_8jlfmcmf_.bkp tag=TAG20130130T150411 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 30-JAN-13
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key Size       Device Type Elapsed Time Completion Time
1       981.94M    DISK        00:01:15     30-JAN-13
        BP Key: 1   Status: AVAILABLE Compressed: NO Tag: TAG20130130T143224
        Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T143224_8jlcqs5d_.bkp
List of Archived Logs in backup set 1
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    5       830546     25-JAN-13 841823     25-JAN-13
1    6       841823     25-JAN-13 866733     25-JAN-13
1    7       866733     25-JAN-13 889743     25-JAN-13
1    8       889743     25-JAN-13 912846     26-JAN-13
1    9       912846     26-JAN-13 931109     26-JAN-13
1    10      931109     26-JAN-13 952239     26-JAN-13
1    11      952239     26-JAN-13 979268     26-JAN-13
1    12      979268     26-JAN-13 1004465    26-JAN-13
1    13      1004465    26-JAN-13 1021707    26-JAN-13
1    14      1021707    26-JAN-13 1040437    27-JAN-13
1    15      1040437    27-JAN-13 1068031    27-JAN-13
1    16      1068031    27-JAN-13 1091450    27-JAN-13
1    17      1091450    27-JAN-13 1114656    27-JAN-13
1    18      1114656    27-JAN-13 1137779    27-JAN-13
1    19      1137779    27-JAN-13 1165125    27-JAN-13
1    20      1165125    27-JAN-13 1199499    28-JAN-13
1    21      1199499    28-JAN-13 1228282    28-JAN-13
1    22      1228282    28-JAN-13 1249640    28-JAN-13
1    23      1249640    28-JAN-13 1270613    28-JAN-13
1    24      1270613    28-JAN-13 1291570    28-JAN-13
1    25      1291570    28-JAN-13 1312497    28-JAN-13
1    26      1312497    28-JAN-13 1332622    28-JAN-13
1    27      1332622    28-JAN-13 1365097    28-JAN-13
1    28      1365097    28-JAN-13 1395297    28-JAN-13
1    29      1395297    28-JAN-13 1407058    28-JAN-13
1    30      1407058    28-JAN-13 1437549    29-JAN-13
1    31      1437549    29-JAN-13 1469773    29-JAN-13
1    32      1469773    29-JAN-13 1504608    29-JAN-13
1    33      1504608    29-JAN-13 1522578    29-JAN-13
1    34      1522578    29-JAN-13 1553706    30-JAN-13
1    35      1553706    30-JAN-13 1586954    30-JAN-13
1    36      1586954    30-JAN-13 1603625    30-JAN-13
BS Key Size       Device Type Elapsed Time Completion Time
2       538.00K    DISK        00:00:01     30-JAN-13
        BP Key: 2   Status: AVAILABLE Compressed: NO Tag: TAG20130130T144745
        Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T144745_8jldnkxt_.bkp
List of Archived Logs in backup set 2
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    38      1604067    30-JAN-13 1604680    30-JAN-13
BS Key Size       Device Type Elapsed Time Completion Time
3       3.64M      DISK        00:00:00     30-JAN-13
        BP Key: 3   Status: AVAILABLE Compressed: NO Tag: TAG20130130T150411
        Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T150411_8jlfmcmf_.bkp
List of Archived Logs in backup set 3
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    38      1604067    30-JAN-13 1604680    30-JAN-13
1    39      1604680    30-JAN-13 1606046    30-JAN-13
1    40      1606046    30-JAN-13 1606049    30-JAN-13
1    41      1606049    30-JAN-13 1606057    30-JAN-13
1    42      1606057    30-JAN-13 1606303    30-JAN-13
1    43      1606303    30-JAN-13 1606353    30-JAN-13
RMAN> crosscheck backup of archivelog all;
using channel ORA_DISK_1
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T143224_8jlcqs5d_.bkp RECID=1 STAMP=806077945
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T144745_8jldnkxt_.bkp RECID=2 STAMP=806078865
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T150411_8jlfmcmf_.bkp RECID=3 STAMP=806079851
Crosschecked 3 objects
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key Size       Device Type Elapsed Time Completion Time
1       981.94M    DISK        00:01:15     30-JAN-13
        BP Key: 1   Status: AVAILABLE Compressed: NO Tag: TAG20130130T143224
        Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T143224_8jlcqs5d_.bkp
List of Archived Logs in backup set 1
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    5       830546     25-JAN-13 841823     25-JAN-13
1    6       841823     25-JAN-13 866733     25-JAN-13
1    7       866733     25-JAN-13 889743     25-JAN-13
1    8       889743     25-JAN-13 912846     26-JAN-13
1    9       912846     26-JAN-13 931109     26-JAN-13
1    10      931109     26-JAN-13 952239     26-JAN-13
1    11      952239     26-JAN-13 979268     26-JAN-13
1    12      979268     26-JAN-13 1004465    26-JAN-13
1    13      1004465    26-JAN-13 1021707    26-JAN-13
1    14      1021707    26-JAN-13 1040437    27-JAN-13
1    15      1040437    27-JAN-13 1068031    27-JAN-13
1    16      1068031    27-JAN-13 1091450    27-JAN-13
1    17      1091450    27-JAN-13 1114656    27-JAN-13
1    18      1114656    27-JAN-13 1137779    27-JAN-13
1    19      1137779    27-JAN-13 1165125    27-JAN-13
1    20      1165125    27-JAN-13 1199499    28-JAN-13
1    21      1199499    28-JAN-13 1228282    28-JAN-13
1    22      1228282    28-JAN-13 1249640    28-JAN-13
1    23      1249640    28-JAN-13 1270613    28-JAN-13
1    24      1270613    28-JAN-13 1291570    28-JAN-13
1    25      1291570    28-JAN-13 1312497    28-JAN-13
1    26      1312497    28-JAN-13 1332622    28-JAN-13
1    27      1332622    28-JAN-13 1365097    28-JAN-13
1    28      1365097    28-JAN-13 1395297    28-JAN-13
1    29      1395297    28-JAN-13 1407058    28-JAN-13
1    30      1407058    28-JAN-13 1437549    29-JAN-13
1    31      1437549    29-JAN-13 1469773    29-JAN-13
1    32      1469773    29-JAN-13 1504608    29-JAN-13
1    33      1504608    29-JAN-13 1522578    29-JAN-13
1    34      1522578    29-JAN-13 1553706    30-JAN-13
1    35      1553706    30-JAN-13 1586954    30-JAN-13
1    36      1586954    30-JAN-13 1603625    30-JAN-13
BS Key Size       Device Type Elapsed Time Completion Time
2       538.00K    DISK        00:00:01     30-JAN-13
        BP Key: 2   Status: AVAILABLE Compressed: NO Tag: TAG20130130T144745
        Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T144745_8jldnkxt_.bkp
List of Archived Logs in backup set 2
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    38      1604067    30-JAN-13 1604680    30-JAN-13
BS Key Size       Device Type Elapsed Time Completion Time
3       3.64M      DISK        00:00:00     30-JAN-13
        BP Key: 3   Status: AVAILABLE Compressed: NO Tag: TAG20130130T150411
        Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T150411_8jlfmcmf_.bkp
List of Archived Logs in backup set 3
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    38      1604067    30-JAN-13 1604680    30-JAN-13
1    39      1604680    30-JAN-13 1606046    30-JAN-13
1    40      1606046    30-JAN-13 1606049    30-JAN-13
1    41      1606049    30-JAN-13 1606057    30-JAN-13
1    42      1606057    30-JAN-13 1606303    30-JAN-13
1    43      1606303    30-JAN-13 1606353    30-JAN-13
RMAN> HTH
Aman....
Edited by: Aman.... on Jan 30, 2013 3:06 PM

8i backup archivelog

Hello,
I want to backup all my archivelogs in one arch dest. I use two.
Can I use the LIKE in 8i ?
Thanks,
sql 'alter system archive log current';
backup archivelog all like '?/arch/log' delete input;
release channel ch01;

user771256 wrote:
Yes, but the other location is never backed up with RMAN and cannot be backed up.
When I run it without using just one dest I get error cannot find log in other dest.
Thanks, You don't need to back up both locations. You backup your archive logs. Why does it matter which location is used -- they are both the same.
The reason you have two archlog locations is to protect against loss of archlogs before they get backed up. If you want extra protection for the backups themselves, then don't delete the archlogs until they have been backed up twice. And/or create a second backup layer by making a backup of the backup. In my shop, we take a daily backup of the archivelogs. My rman script is configured to backup all archlogs that have not been backed up twice, then delete the ones that have been backed up twice. So an archlog that is created Monday afternoon will be backed up Monday night, then again on Tuesday night, then deleted. In the mean time after the nightly rman backup, the SA runs a full system backup that catches my rman backup files. So I have multiple backups at multiple levels.

How to list all obsolete backuped archivelog

today I backup the whole database(this is the
first time I backup the database) with command
" backup database",and alse backup all
archivelog,and the oldest archivelog is three days
ago,and after the backup,I want to report obsolete
backup,but using
"report obsolete until time 'SYSDATE-1'"
command get a output of nothing,and IMO because I
backup the whole database,at least the archivelogs
before yesterday are not usefull for restore,and
it should be obsolete.When I read rman reference,it
sames that obsolete only apply to datafile,but no
archivedlog.

You are right, in the 8i doc, it contains an "until" clause and does not list obsolete archive logs.
http://download-uk.oracle.com/docs/cd/A87860_01/doc/server.817/a76990/rmansy35.htm#23596
You should then try to write your own script in sqlplus.
Example, which delete all backups of archive logs older then yesterday.
$ sqlplus rman/rman@RMANREP
SQL> select db_name, max(THREAD#), max(SEQUENCE#) from rc_backup_redolog where completion_time < sysdate-1 group by db_name;
DB_NAME MAX(THREAD#) MAX(SEQUENCE#)
PROD 1 133
$ rman sys/change_on_install@PROD rman/rman@RMANREP
RMAN> delete noprompt archivelog until sequence 133 thread 1;

Backup archivelog-limit

Similar Messages

Maybe you are looking for