RMAN Backup Archieve log

We are using rman to backup the archive log files. Due to space constraints in the disk, all the existing archivelog files are moved to another drive. In the init.ora also, the new archive log location is changed. Now we are not able to take backup of the old archive log files using backup command of rman. Since the control file is having the old location for archive log. How to take backup of these files from the new location in the disk. Whether backup archivelog like '' will be useful in this situation.

Dear user7277731,
Consider using the flash recovery area.
Define db_recovery_area_dest and db_recovery_area_dest_size in order to automatically delete the archivelogs. Archivelogs will be deleted from the location that you have defined when the recovery area destination size is near 100%.
You may also use;
crosscheck archivelog all;
delete noprompt expired archivelog all;hope it helps,
Ogan

Similar Messages

Rman backup archive log

Hi Guys,
Can advise on the syntax to perform rman backup of archive logs generated in last 2 days?
Should it be 1 or 2?
thanks!
1. BACKUP ARCHIVELOG UNTIL TIME 'SYSDATE-2';
2. BACKUP ARCHIVELOG FROM TIME 'SYSDATE-2';

What prevents you from trying both?
I'm not trying to be difficult here but why take the time to ask people in a forum, not even supplying a version number, and not just find out?
It took me less than 60 seconds to cut-and-paste both of your command lines into RMAN and look at the output.
Edited by: damorgan on Jan 19, 2013 4:11 PM

RMAN backup archive logs on tape that has not been backuped yet...

We are using RMAN with catalog on Legato. Oracle 10gR2.
Our archive log backup is taking every 2 hours with scriipt:
run {
allocate channel t1 type 'SBT_TAPE';
allocate channel t2 type 'SBT_TAPE';
send 'NSR_ENV=(NSR_SERVER=hitbackup.hit.hypohr,NSR_CLIENT=a22ff020.hit.hypobck)';
# 0.0840278 = 121 minutes!
backup archivelog FROM TIME = 'sysdate-0.0840278' filesperset 50 format '/arch1_%d_%u/';
release channel t1;
release channel t2;
}In the night we take everyday full backup where we delete all 9 days old archive log which has been backuped on tape at least once. The script is following:
run {
allocate channel t1 type 'SBT_TAPE';
allocate channel t2 type 'SBT_TAPE';
send 'NSR_ENV=(NSR_SERVER=hitbackup.hit.hypohr,NSR_CLIENT=a22ff020.hit.hypobck)';
backup full database filesperset 2 format '/full_%d_%U/';
release channel t1;
release channel t2;
allocate channel d2 type disk;
delete archivelog until time 'trunc(sysdate)-9'
backed up 1 times to device type SBT_TAPE;
release channel d2;
}Problem is that sometimes archive log backup is not performed (Legato head is busy with other backups or some restore that happened in the time when backup is scheduled and later 2hours frame is missing those logs) and then we backup them with some manual script.
We'd like to know how to backup to tape all archive logs in last 5 days that has not been backuped once to tape. I.E:
backup archivelog FROM TIME = 'sysdate-7' filesperset 50 format '/arch1_%d_%u/'
backed up 0 times to device type SBT_TAPE;This part will be included in daily job...which should recollect all missing archive logs from last seven days.
THX

You could try to use the NOT BACKED UP x TIMES clause from BACKUP command.

RMAN BACKUP hangs up on archive logs

Hi,
in 9i on Linux, My rman backup script is :
RMAN> run {
2> allocate channel t1 type disk;
3> backup incremental level=0 format '/mnt/rman/MYDB/full_%d_%t_%s_%p' database;
4> sql 'alter system switch logfile';
5> backup format '/mnt/rman/MYDB/al_%d_%t_%s_%p'
6> archivelog all delete input;
7> backup format '/mnt/rman/MYDB/ctl_%d_%t_%s_%p' current controlfile;
8> }
It works well until :
backup format '/mnt/rman/MYDB/al_%d_%t_%s_%p' archivelog all delete input;
Here it hangs up (may be there are many many archive log files). What do you propose ? How can we ask RMAN just backup archive logs since some recent dates ? How can we delete most of ancient archive logs ? Since many times RMAN backup was in error then archive logs were not deleted. Now impossible to finish RMAN backup. Many thanks for your help.

Hi,
I launched following since last night but it is always waiting :
RMAN> crosscheck archivelog all;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=110 devtype=DISK
What can I do ? Any other way to say to RMAN that archived logs are not available ?
Many thanks.

Backup archive logs problem using RMAN

Hi guys
I got failure when using RMAN to backup archive log files:
Starting backup at 20-APR-06
current log archived
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/20/2006 21:53:57
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_17/o1_mf_1_1_21p5c251_.arc
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
RMAN> **end-of-file**
My archive log files location:
SQL> show parameter log_archive_dest
NAME TYPE VALUE
log_archive_dest_1 string LOCATION=/opt/oracle/oradata/DB10G/arch/
Current archive log files:
$ ls /opt/oracle/oradata/DB10G/arch
1_17_586191737.dbf 1_21_586191737.dbf 1_25_586191737.dbf 1_29_586191737.dbf 1_33_586191737.dbf
1_18_586191737.dbf 1_22_586191737.dbf 1_26_586191737.dbf 1_30_586191737.dbf 1_34_586191737.dbf
1_19_586191737.dbf 1_23_586191737.dbf 1_27_586191737.dbf 1_31_586191737.dbf 1_35_586191737.dbf
1_20_586191737.dbf 1_24_586191737.dbf 1_28_586191737.dbf 1_32_586191737.dbf afiedt.buf
$
But when I check v$archived_log:
SQL> select name,status,deleted from v$archived_log;
NAME S DEL
D YES
D YES
D YES
D YES
D YES
D YES
D YES
D YES
D YES
D YES
D YES
/opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_17/ A NO
/opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_18/ A NO
/opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_19/ A NO
/opt/oracle/oradata/DB10G/redo01.log A NO
/opt/oracle/oradata/DB10G/redo02.log A NO
/opt/oracle/oradata/DB10G/redo03.log A NO
/opt/oracle/oradata/DB10G/arch/1_5_585926175.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_6_585926175.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_7_585926175.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_1_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_2_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_3_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_4_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_5_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_6_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_7_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_8_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_9_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_10_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_11_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_12_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_13_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_14_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_15_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_16_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_17_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_18_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_19_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_20_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_21_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_22_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_23_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_24_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_25_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_26_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_27_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_28_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_29_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_30_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_31_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_32_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_33_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_34_586191737.dbf A NO
More records than actual archived logs. How could it happen? How to solve?
THanks in advance.
Sharon

Hi,
Use
RMAN>crosscheck archivelog all; cmd

RMAN backup in noarchived log mode

Hi,
can we take RMAN backup in noarchived log mode?
If yes, how? just run backup database command or ?
thanks

You can use RMAN to backup a database in noarchivelog mode but you need to shutdown and mount the database. e.g.:
rman target /
RMAN> shutdown immediate
RMAN> startup mount
RMAN> backup database

Log Switch during RMAN backup

I have seen in many RMAN backup scripts that a manual log switching is performed in first line of the script? What is it purpose, just to write changes needed to reconstruct the DML/DDL statements to online redo logfiles and start the archiving process if db is running in archive log mode?

918868 wrote:
I have seen in many RMAN backup scripts that a manual log switching is performed in first line of the script? What is it purpose, just to write changes needed to reconstruct the DML/DDL statements to online redo logfiles and start the archiving process if db is running in archive log mode?That could be the only reason but even that is not needed as RMAN would do a log switch automatically to push the current redo log file to make it's archive log and include it in the backup.
Aman....

Unable to backup arhcive logs in rman.

Hi,
Oracle Version :10.2.0.2
Operating system:linux
I was unable to backup the archive logs through rman .Here i changed the archive log destinatin also but still i am getting the errror
RMAN> backup database plus archivelog;
Starting backup at 04-DEC-09
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 12/04/2009 16:23:18
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_10/o1_mf_1_3_5bkc1o5q_.arc
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3Edited by: SIDDABATHUNI on Dec 4, 2009 2:59 AM

Hi,
I have changed the archive log distention and i think that i was deleted it manually.Here is the output of my crosscheck archivelog all;
RMAN> crosscheck archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=323 devtype=DISK
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_10/o1_mf_1_3_5bkc1o5q_.arc recid=6 stamp=697208725
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_10/o1_mf_1_4_5bkd60x4_.arc recid=7 stamp=697209883
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_10/o1_mf_1_5_5bkd78q9_.arc recid=8 stamp=697209922
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_10/o1_mf_1_6_5bkf2rwx_.arc recid=9 stamp=697210802
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_10/o1_mf_1_7_5blbdsqs_.arc recid=10 stamp=697240820
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_10/o1_mf_1_8_5blc2tvx_.arc recid=11 stamp=697241524
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_11/o1_mf_1_9_5bm1t7hk_.arc recid=12 stamp=697264802
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_11/o1_mf_1_10_5bmqwzr6_.arc recid=13 stamp=697287417
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_11/o1_mf_1_11_5bnjqg4n_.arc recid=14 stamp=697312840
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_11/o1_mf_1_12_5bnytoy5_.arc recid=15 stamp=697327280
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_12/o1_mf_1_13_5boplo7l_.arc recid=16 stamp=697351600
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_12/o1_mf_1_14_5bp6vv6w_.arc recid=17 stamp=697368277
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_12/o1_mf_1_15_5bpdtlfn_.arc recid=18 stamp=697374380
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_13/o1_mf_1_16_5br3nh19_.arc recid=19 stamp=697430505
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_13/o1_mf_1_17_5brvlghg_.arc recid=20 stamp=697455015
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_14/o1_mf_1_18_5btzdcv5_.arc recid=21 stamp=697524454
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_14/o1_mf_1_19_5bw0drf0_.arc recid=22 stamp=697558259
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_14/o1_mf_1_20_5bwvyksr_.arc recid=23 stamp=697586476
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_15/o1_mf_1_21_5bxmsqql_.arc recid=24 stamp=697610898
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_15/o1_mf_1_22_5bz0h5on_.arc recid=25 stamp=697656639
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_15/o1_mf_1_23_5bzjbvg2_.arc recid=26 stamp=697672884
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_16/o1_mf_1_24_5c0lgk9r_.arc recid=27 stamp=697707819
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_16/o1_mf_1_25_5c24o21l_.arc recid=28 stamp=697759227
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_17/o1_mf_1_26_5c30s9py_.arc recid=29 stamp=697788035
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_17/o1_mf_1_27_5c4s0wyy_.arc recid=30 stamp=697845623
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_18/o1_mf_1_28_5c5k0jrj_.arc recid=31 stamp=697870186
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_18/o1_mf_1_29_5c6z1g0p_.arc recid=32 stamp=697917319
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_18/o1_mf_1_30_5c7mqfl8_.arc recid=33 stamp=697938502
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_19/o1_mf_1_31_5c89jkhw_.arc recid=34 stamp=697960811
validation failed for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_19/o1_mf_1_32_5c9ggk5p_.arc recid=35 stamp=697998634
validation succeeded for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_12_02/o1_mf_1_343_5kdfc1sv_.arc recid=36 stamp=704560058
validation succeeded for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_12_02/o1_mf_1_344_5kdfy3pd_.arc recid=37 stamp=704560667
validation succeeded for archived log
archive log filename=/u05/archive/%t_%s_%r.arc1_345_697204983.dbf recid=38 stamp=704560901
validation succeeded for archived log
archive log filename=/u05/archive/1_346_697204983.dbf recid=39 stamp=704561258
validation succeeded for archived log
archive log filename=/u05/archive/1_347_697204983.dbf recid=40 stamp=704561835
validation succeeded for archived log
archive log filename=/u05/archive/1_348_697204983.dbf recid=41 stamp=704561992
validation succeeded for archived log
archive log filename=/u05/archive/1_349_697204983.dbf recid=42 stamp=704562987
validation succeeded for archived log
archive log filename=/u05/archive/1_350_697204983.dbf recid=43 stamp=704562987
validation succeeded for archived log
archive log filename=/u05/archive/1_351_697204983.dbf recid=44 stamp=704562992
validation succeeded for archived log
archive log filename=/u05/archive/1_352_697204983.dbf recid=45 stamp=704563257
validation succeeded for archived log
archive log filename=/u05/archive/1_353_697204983.dbf recid=46 stamp=704563321
validation succeeded for archived log
archive log filename=/u05/archive/1_354_697204983.dbf recid=47 stamp=704563408
validation succeeded for archived log
archive log filename=/u05/archive/1_355_697204983.dbf recid=48 stamp=704563434
validation succeeded for archived log
archive log filename=/u05/archive/1_356_697204983.dbf recid=49 stamp=704584836
validation succeeded for archived log
archive log filename=/u05/archive/1_357_697204983.dbf recid=50 stamp=704586204
validation succeeded for archived log
archive log filename=/u05/archive/1_358_697204983.dbf recid=51 stamp=704611511
validation succeeded for archived log
archive log filename=/u05/archive/1_359_697204983.dbf recid=52 stamp=704648675
validation succeeded for archived log
archive log filename=/u05/archive/1_360_697204983.dbf recid=53 stamp=704650176
validation succeeded for archived log
archive log filename=/u05/archive/1_361_697204983.dbf recid=54 stamp=704650675
validation succeeded for archived log
archive log filename=/u05/archive/1_362_697204983.dbf recid=55 stamp=704671244
validation succeeded for archived log
archive log filename=/u05/archive/1_363_697204983.dbf recid=56 stamp=704692487
validation succeeded for archived log
archive log filename=/u05/archive/1_364_697204983.dbf recid=57 stamp=704708839
validation succeeded for archived log
archive log filename=/u05/archive/1_365_697204983.dbf recid=59 stamp=704736263
validation succeeded for archived log
archive log filename=/u05/archive/1_366_697204983.dbf recid=58 stamp=704736262
validation succeeded for archived log
archive log filename=/u05/archive/1_367_697204983.dbf recid=60 stamp=704736266
validation succeeded for archived log
archive log filename=/u05/archive/1_368_697204983.dbf recid=61 stamp=704737398
Crosschecked 56 objectsHow can i over come this problem.

How to check RMAN backup report or log

Hi Guys,
I have RMAN schduled to backup my database daily.
Please what are the steps to check the report of the backup to see what was actually backed up and if it backup up ok
Thanks

Use "LIST BACKUP" to display information about backup sets, proxy copies, and image copies. With LIST command you can list the following:
- Backups and copies that do not have the status AVAILABLE in the RMAN repository
- Backups and copies of datafiles that are available and can possibly be used in a restore operation
- Specified archived logs, backup sets, backup pieces, control file copies, datafile copies, and proxy copies
- Backups and copies restricted by tag, completion time, recoverability, or device
- Incarnations of a specified database or of all databases known to the repository
- Stored scripts in the recovery catalog
Examples on how to use LIST command are listed below:
RMAN> LIST BACKUP;
RMAN> LIST EXPIRED BACKUP;
RMAN> LIST BACKUP OF DATABASE;
RMAN> LIST BACKUP SUMMARY;
RMAN> LIST BACKUP BY FILE;
RMAN> LIST ARCHIVELOG ALL;
RMAN> LIST COPY OF DATABASE ARCHIVELOG ALL;
RMAN> LIST COPY OF DATAFILE 1, 2, 3;
RMAN> LIST BACKUP OF ARCHIVELOG FROM SEQUENCE 1437;
RMAN> LIST BACKUPSET OF DATAFILE 1;You can use the VALIDATE keyword of the BACKUP command to do the following:
- Check datafiles for physical and logical corruption
- Confirm that all database files exist and are in the correct locations
For example, you can validate that all database files and archived redo logs can be backed up by running a command as follows:
RMAN> BACKUP VALIDATE DATABASE ARCHIVELOG ALL;I suggest you read Oracle® Database Backup and Recovery Manuals:
http://www.oracle.com/pls/db102/portal.portal_db?selected=3

RMAN BACKUPS AND ARCHIVED LOG ISSUES

제품 : RMAN
작성날짜 : 2004-02-17
RMAN BACKUPS AND ARCHIVED LOG ISSUES
=====================================
Scenario #1:
1)RMAN이 모든 archived log들을 삭제할 때 실패하는 경우.
database는 두 개의 archive destination에 archive file을 생성한다.
다음과 같은 스크립트를 수행하여 백업후에 archived redo logfile을 삭제한다.
run {
allocate channel c1 type 'sbt_tape';
backup database;
backup archivelog all delete input;
Archived redo logfile 삭제 유무를 확인하기 위해 CROSSCHECK 수행시 다음과
같은 메시지가 발생함.
RMAN> change archivelog all crosscheck;
RMAN-03022: compiling command: change
RMAN-06158: validation succeeded for archived log
RMAN-08514: archivelog filename=
/oracle/arch/dest2/arcr_1_964.arc recid=19 stamp=368726072
2) 원인분석
이 문제는 에러가 아니다. RMAN은 여러 개의 arhive directory중 하나의
directoy안에 있는 archived file들만 삭제한다. 그래서 나머지 directory안의
archived log file들은 삭제되지 않고 남게 되는 것이다.
3) 해결책
RMAN이 강제로 모든 directory안의 archived log file들을 삭제하게 하기 위해서는
여러 개의 채널을 할당하여 각 채널이 각 archive destination안의 archived file을
백업하고 삭제하도록 해야 한다.
이것은 아래와 같이 구현될 수 있다.
run {
allocate channel t1 type 'sbt_tape';
allocate channel t2 type 'sbt_tape';
backup
archivelog like '/oracle/arch/dest1/%' channel t1 delete input
archivelog like '/oracle/arch/dest2/%' channel t2 delete input;
Scenario #2:
1)RMAN이 archived log를 찾을 수 없어 백업이 실패하는 경우.
이 시나리오에서 database를 incremental backup한다고 가정한다.
이 경우 RMAN은 recover시 archived redo log대신에 incremental backup을 사용할
수 있기 때문에 백업 후 모든 archived redo log를 삭제하기 위해 OS utility를 사용한다.
그러나 다음 번 backup시 다음과 같은 Error를 만나게 된다.
RMAN-6089: archive log NAME not found or out of sync with catalog
2) 원인분석
이 문제는 OS 명령을 사용하여 archived log를 삭제하였을 경우 발생한다. 이때 RMAN은
archived log가 삭제되었다는 것을 알지 못한다. RMAN-6089는 RMAN이 OS 명령에 의해
삭제된 archived log가 여전히 존재하다고 생각하고 백업하려고 시도하였을 때 발생하게 된다.
3) 해결책
가장 쉬운 해결책은 archived log를 백업할 때 DELETE INPUT option을 사용하는 것이다.
예를 들면
run {
allocate channel c1 type 'sbt_tape';
backup archivelog all delete input;
두 번째로 가장 쉬운 해결책은 OS utility를 사용하여 archived log를 삭제한 후에
다음과 같은 명령어를 RMAN prompt상에서 수행하는 것이다.
RMAN>allocate channel for maintenance type disk;
RMAN>change archivelog all crosscheck;
Oracle 8.0:
RMAN> change archivelog '/disk/path/archivelog_name' validate;
Oracle 8i:
RMAN> change archivelog all crosscheck ;
Oracle 9i:
RMAN> crosscheck archivelog all ;
catalog의 COMPATIBLE 파라미터가 8.1.5이하로 설정되어 있으면 RMAN은 찾을 수 없는
모든 archived log의 status를 "DELETED" 로 셋팅한다. 만약에 COMPATIBLE이 8.1.6이상으로
설정되어 있으면 RMAN은 Repository에서 record를 삭제한다.

Very strange, I issue following command in RMAN on both primary and standby machine, but it they don't delete the 1_55_758646076.dbf, I find in v$archived_log, this "/home/oracle/app/oracle/dataguard/1_55_758646076.dbf" had already been applied.
RMAN> connect target /
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
old RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
new RMAN configuration parameters are successfully stored
RMAN>
----------------------------------------------------------------------------------

How to control RMAN backup of archive logs in FRA

Setup:
11.2.0.2 GI
ASM Diskgroup for Fast Recovery Area
10.2.0.4 Enterprise Database
Without Catalog Database
To get familiar with Flashback Database we set up RMAN Backups
without deleting the archive logs,
as published in Oracle10g / 11g - Getting Started with Recovery Manager (RMAN) (Doc ID 360416.1)
"These deletions are managed by Oracle when space is required."
We observed that RMAN takes backups of all archive logs every time,
here we go with backing up archive logs every 30 minutes.
So the question is:
Is this (backing up all archive logs every time) the expected behavior or
the result of not using a catalog database or
any other mismatch?
thanx for any hint
Michael

Hi Michael,
In Note 360416.1 it refers to two archivelog backup commands.
BACKUP ARCHIVELOG ALL;and
BACKUP ARCHIVELOG FROM TIME 'SYSDATE-30' UNTIL TIME 'SYSDATE-7';Your question:
Is this (backing up all archive logs every time) the expected behavior or the result of not using a catalog database or any other mismatch?If you used the first script you will backup alle archivelogs everytime.
If you use the second one it will do a subset (probably not the range you want to backup...)
You could implement another script
BACKUP ARCHIVELOG NOT BACKED UP 2 TIMES;So every archivelog is only backed up twice.
Check
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#i78895
for more information.
Regards,
Tycho

Rman backup errors..

hi guru's
please tell me the answeres..for this
what will happen if we re run the Rman backup due to the job failure...will take a new backup from the begining? or will start from the first backup end where it left ?
i am deleting some archieved logs on the archieved destination before takeing the RMAN backup, and then running rman backup ...then any error will raised for the missing files during Rman archive log backup for missing files? i have the files like 1 to 10 ...in that 5 and 6 logs are deleted before takeing the Rman backup..how to resolve this?

user13014926 wrote:
hi guru's
please tell me the answeres..for this
what will happen if we re run the Rman backup due to the job failure...will take a new backup from the begining? or will start from the first backup end where it left ?
You can continue backup from which files not backed up and this is call restartable backup.Please refer below link
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1008543
>
i am deleting some archieved logs on the archieved destination before takeing the RMAN backup, and then running rman backup ...then any error will raised for the missing files during Rman archive log backup for missing files? i have the files like 1 to 10 ...in that 5 and 6 logs are deleted before takeing the Rman backup..how to resolve this?If you manually delete archivelogs then you will get an error so before executing this backup command you have to execute CROSSCHECK ARCHIVELOG ALL and DELETE EXPIRED ARCHIVELOG ALL then your problem will solve.

Problem with the Archieve log

Hi there!
In our production box, we have solaris and oracle 9i, suddenly the achieve logs was created dramatically every minutes, and it pile up the memory.
I did do some search on google got some ideas try them, but nothing could help, still the problem occur
Any suggestion please!

Hi,
1. Are you using RMAN? (then run backup to tape or
disk and delete input)
yes im using RMAN, and im putting everything in disk, then later in tape
2. How much space left in your disk now ?? (Archive
destination?)
now the archieve log is left with 3580766
3. What is the size of your redo log ?? (yes
mentioned you can try to increase it)
i will check on this
4. Try to have metalink account instead of Google
(always read the oracle documentation.. of course it
takes time to identify the correct note but worth
it)
we try metalink too... nothing!!!
Thanks
--Raman

Unable to restore and recover my Database from RMAN Backup

Dear All,
Iam practicing RMAN in Windows environment.
My configurations are
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:\Backup\%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\ORACLE\DATABASE\SNCFORCL.ORA';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'F:\Backup\%U.bak';
Then i took the RMAN backup, now iam shutdown my DB and removed one logfile..
then i tried to startup the DB but it is saying
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: 'E:\ORADATA\ORCL\REDO03.LOG'
So i tried to restore the Database with my rman backup
RMAN> restore database;
But i am unable to restore my logfile in the Datafiles location where as all other datafiles are restored but redo logfiles are not restored.
So, i am unable to recover my DB
Please tell me whether i am doing any mistake, what is the solution for my problem.
Thanks in advance
Mahi

All you restored was your datafiles.
Now issue recover database and that will apply the archive logs.
This is in the oracle documentation.
"You must restore backups of these archived logs for recovery to proceed. You can restore either to the default or nondefault location. If you do not have backups, then you must performing incomplete recovery up to an SCN before the first missing redo log and open RESETLOGS."
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/osrecvry.htm
In this case after issuing restore database in RMAN, then issue this.
"Recover database"
It will then be an incomplete recovery. They should have been multiplexed. Did you restore your controlfile with this backup? You may have to issue an "Alter database open resetlogs;"

I am getting below error while taking RMAN backup.

Friends,
I am getting below error while taking RMAN backup.
The issue is related with a lock while trying to backup the controlfile.
The lock is more likely caused by the autobackup controlfile process started just before RMAN process was also trying the backup controlfile as shown in the following alert.log excerpt.
Starting Control File and SPFILE Autobackup at 2009-04-07 09:24:58
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 04/07/2009 09:25:03
ORA-00230: operation disallowed: snapshot control file enqueue unavailable
Is there anyway to solve this issue?Thanks in advance.

Hi,
SQL> SELECT s.sid, username AS "User", program, module, action, logon_time "Logon", l.*
FROM v$session s, v$enqueue_lock l
WHERE l.sid = s.sid and l.type = 'CF' AND l.id1 = 0 and l.id2 = 2; 2 3
no rows selected
Oracle version : 10.2.0.3
I am getting this error once in a month not everyday.
Starting Control File and SPFILE Autobackup at 2009-04-07 09:24:58
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 04/07/2009 09:25:03
ORA-00230: operation disallowed: snapshot control file enqueue unavailable
Please suggest me based on this..Thanks in advance..

RMAN Backup Archieve log

Similar Messages

Maybe you are looking for