Does hot backup trigger archive log?

Our archive log starts everyday around 5pm.
Our hot backup also starts everyday around 5pm.
Do they start in just coincidence?
Or hot backup does trigger archive log?
Our db version 9i. It writes one single archive log daily.
The transaction volume is minimal. sometimes no user login in a whole day.
Any idea?

How are you executing the backup? Via a script? Backup software tool?
You can manually issue a checkpoint which would cause a log switch and a write of the archivelog out to the backup directory, but I'm not familiar with any backup software that includes this as their standard operating procedure. This would account for the activity you are seeing.
If you are using some kind of shell script or such, you might check to see if the script includes a checkpoint command before it calls up RMAN to perform the backup.
The logic really isn't bad - by checkpointing the database just prior to a backup you would have almost no additional transactions outside of the archived log files, making the backup non-reliant on the current online redo files. If you are maintaining a good inventory of backed up archive logs, it should be fairly quick and easy to restore even in the event of a catastrophic isk failure that wiped out the database and online REDO logs.

Similar Messages

RMAN backup of archive logs

I am sort of new to RMAN, I've been playing with it for a while but that's about as far as I've taken it. My question is does RMAN automatically backup any archive logs needed for recovery when I run "backup database" command or do I have to issue "backup database plus archive log" in order to insure recovery.

Backup database also backups archivelogs.No,it does not. From documentation:
backup database;
Creates a backup set (AS BACKUPSET) or group of image copies (AS COPY) for all datafiles in the database. If generating a backup set, then RMAN can include only datafiles and control files: it cannot include archived redo logs.
Werner

RMAN-20242: specification does not match any archive log in the recovery ca

Hi,
I'm working with an 9i Oracle RAC (yes, I know this version is out of support...). I'm launching my backup from node 1 with this script
run {
sql 'alter system switch logfile'
sql 'alter system archive log current'
allocate channel TSM1 type 'sbt_tape' connect *
parms='ENV=(TDPO_OPTFILE=/home/adsmadm/rman_INF01T01/opt/tdpo.opt)'
allocate channel TSM2 type 'sbt_tape' connect *
parms='ENV=(TDPO_OPTFILE=/home/adsmadm/rman_INF01T01/opt/tdpo.opt)'
backup
format 'brman_arch_%s_%p'
(archivelog like '/logs/bbdd/oracle/INF01T01/archiver/%' channel TSM1 delete input )
(archivelog like '/logs/bbdd/oracle/INF01T03/archiver/%' channel TSM2 delete input )
release channel TSM2
release channel TSM1
And fail with this error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 08/13/2012 22:36:43
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archive log in the recovery catalog
I've take a look to the archives directories and both nodes have archives:
ora10g:/opt/ora10g > ls -lrt /logs/bbdd/oracle/INF01T01/archiver
total 97896
-rw-r----- 1 ora10g dba 2048 Aug 13 22:36 T0001S00000061440648489222.ARC
-rw-rw---- 1 ora10g dba 38132224 Aug 13 22:36 T0001S00000061430648489222.ARC
-rw-r----- 1 ora10g dba 11984896 Aug 13 22:36 T0002S00000044040648489222.ARC
ora10g:/opt/ora10g > ls -lrt /logs/bbdd/oracle/INF01T03/archiver
total 392984
-rw-r----- 1 ora10g dba 49364992 Mar 24 2009 T0002S00000007020648489222.ARC
-rw-r----- 1 ora10g dba 49364992 Mar 25 2009 T0002S00000007030648489222.ARC
-rw-rw---- 1 ora10g dba 19314688 Mar 25 2009 T0002S00000007040648489222.ARC
-rw-rw---- 1 ora10g dba 4733952 Mar 25 2009 T0002S00000007050648489222.ARC
-rw-rw---- 1 ora10g dba 4608 Apr 09 2009 T0002S00000007440648489222.ARC
-rw-rw---- 1 ora10g dba 2541056 Sep 26 2009 T0002S00000015420648489222.ARC
-rw-rw---- 1 ora10g dba 49373184 Sep 28 2009 T0002S00000015430648489222.ARC
-rw-rw---- 1 ora10g dba 3410432 Feb 11 2010 T0002S00000018680648489222.ARC
-rw-rw---- 1 ora10g dba 599552 Feb 12 2010 T0002S00000018710648489222.ARC
-rw-rw---- 1 ora10g dba 6574080 Mar 03 2010 T0002S00000019200648489222.ARC
-rw-rw---- 1 ora10g dba 1663488 Mar 08 2010 T0002S00000019340648489222.ARC
-rw-rw---- 1 ora10g dba 431104 Apr 07 2010 T0002S00000020160648489222.ARC
-rw-rw---- 1 ora10g dba 13811712 Apr 19 2010 T0002S00000020460648489222.ARC
I've tried to made a crosscheck but, only found node1 archives:
RMAN> change archivelog all crosscheck;
validation succeeded for archived log
archive log filename=/logs/bbdd/oracle/INF01T01/archiver/T0001S00000061430648489222.ARC recid=10685 stamp=791246196
validation succeeded for archived log
archive log filename=/logs/bbdd/oracle/INF01T01/archiver/T0001S00000061440648489222.ARC recid=10686 stamp=791246196
validation succeeded for archived log
archive log filename=/logs/bbdd/oracle/INF01T01/archiver/T0002S00000044040648489222.ARC recid=10687 stamp=791246197
Crosschecked 3 objects
Any idea about the way to solve it?
Thanks in advance!
dbajug

Hi,
Connect to target through rman
crosscheck archivelog all;
Then re run the backup. This will work if those two locations provided are archive log destinations.
In case the issue still persists then
Connect to target through rman
catalog start with '/logs/bbdd/oracle/INF01T01/archiver/';
catalog start with '/logs/bbdd/oracle/INF01T03/archiver/';
Then re run the backup.
Thanks,
Vivek
Edited by: 952807 on Aug 16, 2012 5:21 PM

RMAN - specification does not match any archived log in the repository

Hi All,
Oracle 11G R2 on WIndows woo8 R2 Std Edition
I am running RMAN (almost for the first time), and i am using a script previously used. As i am checking through the log, i notice some 'errors' though the backup finishes successfully.
RMAN> crosscheck archivelog all;
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=352 device type=DISK
specification does not match any archived log in the repository
RMAN> crosscheck backupset;
using channel ORA_DISK_1
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
2013_04_23\O1_MF_NCNNF_TAG20130423T134331_8QFL24F7_.BKP RECID=16 STAMP=813505412
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
2013_04_23\O1_MF_ANNNN_TAG20130423T134334_8QFL26K1_.BKP RECID=17 STAMP=813505414
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
2013_04_23\O1_MF_NCNNF_TAG20130423T134423_8QFL3S48_.BKP RECID=18 STAMP=813505465
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
2013_04_23\O1_MF_ANNNN_TAG20130423T134427_8QFL3V9J_.BKP RECID=19 STAMP=813505467
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
2013_04_23\O1_MF_NNNDF_TAG20130423T134428_8QFL3XDT_.BKP RECID=20 STAMP=813505469
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
2013_04_23\O1_MF_NCSNF_TAG20130423T134428_8QFM4C5S_.BKP RECID=21 STAMP=813506507
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
2013_04_23\O1_MF_ANNNN_TAG20130423T140148_8QFM4DOT_.BKP RECID=22 STAMP=813506508
Crosschecked 7 objects
RMAN> crosscheck copy;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=352 device type=DISK
specification does not match any datafile copy in the repository
specification does not match any control file copy in the repository
specification does not match any archived log in the repositorySo there are 2 instances of the errors:
1) crosscheck archivelog all - when the error happens here, i think this means that there are no archived redo logs in the archivelog destination?? ..or something to that nature.
2) crosscheck copy - not sure what the other errors mean here.
Thx in advance!

1) crosscheck archivelog all - when the error happens here, i think this means that there are no archived redo logs in the archivelog destination?? ..or something to that nature.
2) crosscheck copy - not sure what the other errors mean here.
specification does not match any archived log in the repositoryI don't see the error here, it's only a msg that mean : There is no files on XXX destination, which is normal when no files found.

"specification does not match any archived log in the recovery catalog"

I would like to know about this message.
I Validated my backup and archivelogs yesterday.
Today when I tried to do - CROSSCHECK ARCHIVELOG ALL;
I gave me the following error -
RMAN> crosscheck archivelog all;
released channel: ORA_SBT_TAPE_1
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=291 device type=DISK
specification does not match any archived log in the recovery catalog
when I tried to list all the archivelogs then also I am getting this message -
RMAN> list archivelog all;
specification does not match any archived log in the recovery catalog
I have retention policy of 15 Days.
Waiting for your inputs.

Thanks Werner..This means that it is just a message.
One more question related to Archive Log backups -
traditionally DBAs used to take backup of an Archivelog by spupplying "alter system archive log current" before taking the backup. somewhat like -
run
allocate channel t1 device type 'sbt_tape' PARMS="ENV=(TDPO_OPTFILE=/oracle/TESTDB/tdpo.opt)";
sql 'alter system archive log current';
backup archivelog all delete input;
release channel t1;
But, since RMAN automatically archives CURRENT redo log at the start of the archivelog backup, do we REALLY need to pass sql 'alter system archive log current'; before starting the archivelog backup in the script?
RMAN> backup archivelog all;
Starting backup at 11-MAR-10
current log archived ===========> RMAN automatically archived the CURRENT redo log
released channel: ORA_DISK_1
allocated channel: ORA_SBT_TAPE_1
related question to this is - Since it generates one archived log everytime it takes the archived log backup, this backup may get hung if the archived destination is 100% full. Is there any way we can take the archive log backup without generating an extra archived log before the start of the backup?
Thanks,
Roopesh

Specification does not match any archive log in the recovery catalog

Hi
My rman backups sometimes fails with below error, any idea the reason ?
run {
allocate channel t1 type 'SBT_TAPE';
backup
incremental level 0
format '/%d_%p_%t.%s/'
maxsetsize = 8G
(database);
backup
format '/%d_%p_%t_al.%s/'
(archivelog from time 'SYSDATE-2');
backup
format '/%d_%p_%t_al.%s/'
(archivelog until time 'SYSDATE-2' delete input);
release channel t1;
Starting backup at 2011-01-18 22:41:59
current log archived
channel t1: starting archive log backupset
channel t1: specifying archive log(s) in backup set
input archive log thread=1 sequence=7348 recid=6260 stamp=740682001
input archive log thread=1 sequence=7349 recid=6261 stamp=740702540
input archive log thread=1 sequence=7350 recid=6262 stamp=740739604
input archive log thread=1 sequence=7351 recid=6263 stamp=740746801
input archive log thread=1 sequence=7352 recid=6264 stamp=740757602
input archive log thread=1 sequence=7353 recid=6265 stamp=740768401
input archive log thread=1 sequence=7354 recid=6266 stamp=740788921
channel t1: starting piece 1 at 2011-01-18 22:42:04
channel t1: finished piece 1 at 2011-01-18 22:42:29
channel t1: backup set complete, elapsed time: 00:00:26
Finished backup at 2011-01-18 22:42:29
Starting backup at 2011-01-18 22:42:31
released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 01/18/2011 22:42:31
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archive log in the recovery catalog
Recovery Manager complete.

Hi Ora 83,
What is the reason of this error ? The reason for the RMAN-20242 is there are no archivelogs which comply to the filter "until time 'SYSDATE-2'" at 18 Jan 22:42.
Probably you run a purge command more frequent because the oldest logsequence available for backup was created at:
2011 JAN 17 17 00 01 (=sequence=7348)
and the latest at:
2011 JAN 18 22 42 01 (=sequence=7354)
according to your output.
So for some reason the archivelogs created before 16th Jan 22:42 are not on the system as well as the archivelogs created between 16th Jan 22:42 and 17 Jan 17:00.
Maybe there are none (you can check in the alertlog and let us know)?
Regards,
Tycho

Pecification does not match any archive log in the recovery catalog

MAN> list archivelog all;
pecification does not match any archive log in the recovery catalog
RMAN> list backup of archivelog all
BS Key Size Device Type Elapsed Time Completion Time
671197 5.17M DISK 00:00:03 29-MAY-11
BP Key: 671200 Status: AVAILABLE Compressed: YES Tag: TAG20110529T180030
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_FVMDIGPU_S25087_P1
List of Archived Logs in backup set 671197
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44836 503663671 29-MAY-11 503675934 29-MAY-11
2 22517 503663669 29-MAY-11 503675932 29-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671232 5.12M DISK 00:00:02 29-MAY-11
BP Key: 671235 Status: AVAILABLE Compressed: YES Tag: TAG20110529T200050
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G1MDINRJ_S25089_P1
List of Archived Logs in backup set 671232
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44837 503675934 29-MAY-11 503688661 29-MAY-11
2 22518 503675932 29-MAY-11 503688659 29-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671267 5.14M DISK 00:00:03 29-MAY-11
BP Key: 671270 Status: AVAILABLE Compressed: YES Tag: TAG20110529T220036
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G3MDIUS4_S25091_P1
List of Archived Logs in backup set 671267
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44838 503688661 29-MAY-11 503701009 29-MAY-11
2 22519 503688659 29-MAY-11 503701007 29-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671302 16.55M DISK 00:00:05 30-MAY-11
BP Key: 671305 Status: AVAILABLE Compressed: YES Tag: TAG20110530T000048
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110530_G5MDJ5TG_S25093_P1
List of Archived Logs in backup set 671302
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44839 503701009 29-MAY-11 503716961 30-MAY-11
2 22520 503701007 29-MAY-11 503716959 30-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671337 5.13M DISK 00:00:02 30-MAY-11
BP Key: 671340 Status: AVAILABLE Compressed: YES Tag: TAG20110530T020121
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110530_G7MDJCVI_S25095_P1
List of Archived Logs in backup set 671337
Thrd Seq Low SCN Low Time Next SCN Next Time
1 44840 503716961 30-MAY-11 503729544 30-MAY-11
2 22521 503716959 30-MAY-11 503729542 30-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
671372 5.25M DISK 00:00:03 30-MAY-11
BP Key: 671375 Status: AVAILABLE Compressed: YES Tag: TAG20110530T040055
Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110530_G9MDJJVN_S25097_P1
the archives are in the location of
F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G1MDINRJ_S25089_P1
when it is not specified in catalog how can i delete archives from f location i.e
F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G1MDINRJ_S25089_P1
please let me know from rman how can i delete archives from f location...........................
do i need to register with catalog?
i have used Delete archivelog all completed before 'SYSDATE-10';
but no use
out put is
MAN> Delete archivelog all completed before 'SYSDATE-10';
eleased channel: ORA_DISK_1
llocated channel: ORA_DISK_1
hannel ORA_DISK_1: sid=311 devtype=DISK
pecification does not match any archive log in the recovery catalog
MAN> crosscheck backup archivelog all;
please send me the query which i can delete ......................thanks
cheers
mahesh

EdStevens wrote:
856483 wrote:
<snip>
can i have you mobile contact phone number if possible?
I have seen some pretty astonishing requests on this board, but this one really raises (or lowers) the bar. Just what is it your boss is paying you to do?
Some listserves have lots of people giving their number. I find it odd that people would, but not astonishing for someone to ask. Outside the norm here, but how would someone know ahead of time? It's a bravely connected new world.

Specification does not match any archived log in the repository

Hi,
in 11G R2 on Win 2008, I backup via RMAN nocatalog , the whole database and archived logs.
backup as compressed backupset format 's:\rman\incr/al_%d_%T_%s_%p' archivelog all delete input;
But :
RMAN> LIST ARCHIVELOG all;
specification does not match any archived log in the repositoryWhat does it mean ? No archived log is backed up ?
Thank you.

Hello;
The archive logs deleted as and when they're backed up ( archivelog all delete input )
So if you then try to list them they are gone. Nothing to list, at least until the next log switch.
Maybe keep a few days around
BACKUP ARCHIVELOG ALL DELETE INPUT UNTIL TIME 'SYSDATE - 2
Best Regards
mseberg

Unique Error while doing hot backup Cloning!

Dear All,
I am using EBS 11.5.10.2 with DB 9.2.0.6.
I am doing hot backup cloning by referring *[Cloning Oracle Application 11i /R12 with Rapid Clone - Database (9i/10g/11g) Using Hot Backup on Open Database|https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=760772.1]*
I am facing a unique issue, when I run adcfgclone.pl dbconfig <my_context_file>, application of my Production Server start misbehaving and it gives me an error:
Node Id does not exist for the current application server id.When I check the FND_NODE table I found that there server id was empty in it.
I have to run than run the following steps as the resolution:
1. Shutdown all the services.
2. EXEC FND_CONC_CLONE.SETUP_CLEAN;
3. COMMIT;
4. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers,to repopulate the required system tables.
5.start all the services and verify the issue.
Than application behaves normally.
Is there any additional step to be followed while Hot Backup Cloning other than mentioned in the above mentioned ML Doc?
Please suggest,
Anchorage :)

I am facing a unique issue, when I run adcfgclone.pl dbconfig <my_context_file>, application of my Production Server start misbehaving and it gives me an error:
Node Id does not exist for the current application server id.Where did you get this error?
This is very strange, how come this happens in Production, when you are doing cloning in TEST/DEV instance.
Is there any additional step to be followed while Hot Backup Cloning other than mentioned in the above mentioned ML Doc?I feel there are no other additional steps, as I Recently did successfully hotbackup cloning using the same document.

Brrestore RMAN-20242: specification does not match any archived log in the repository

Dear all,
When trying to restore arvhive logs which are taken through netbackup with the following command brrestore -a se1-seqLast=path like in the image attached . It fails with the following image:

1) crosscheck archivelog all - when the error happens here, i think this means that there are no archived redo logs in the archivelog destination?? ..or something to that nature.
2) crosscheck copy - not sure what the other errors mean here.
specification does not match any archived log in the repositoryI don't see the error here, it's only a msg that mean : There is no files on XXX destination, which is normal when no files found.

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>
----------------------------------------------------------------------------------

Full Backups, Level 0 Backups, and Archived Logs

We have an active Oracle server and a standby Oracle server. We keep the standby database up to date with a cron script. The script tells the active database to do 'alter system switch logfile;'. We then rsync the archived logs to our standby server and have rman apply them.
This works everyday except Monday (of course!) and it only recently started failing on Mondays. The only change was that our Sunday backups used to be 'Full' backups but are now 'level 0' backups. Ever since that change, the first attempt to apply the archived logs to the standby server after the level 0 is taken on the active server gives us something like this:
ORA-00308: cannot open archived log
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60519_%u_.arc'
ORA-27037: unable to obtain file status
Of course, the file is not there and doesn't exist on the active server either. And of course, the nightly level1 backups fo not give us problems applying archived logs to the standby database the rest of the week.
The only way I know to recover from this is to apply the level 0 backup or take a new level 0 and apply it. After that, all subsequent archive logs just work. Any idea why changing from Full to Level 0 would break this? The Oracle docs insist that a Level 0 is identical to a Full except that level 1s can reference them as parents. This simply cannot be true based on what I'm seeing! I really want to keep the level 0 backups in play if possible. Level 1 cumulatives wont be useful without them.

Here are the RMAN settings:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%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 '/opt/oracle/102/dbs/snapcf_ORCL.f'; # default
I'm not sure how changing ARCHIVELOG BACKUP COPIES would help. Can you give me a little more information about how that setting comes into play in this situation?
I actually don't want an archive deletion policy here. We have this done in script three days after the needed archive logs have been applied. Is it possible that the we're deleting archivelogs too soon? Would we ever need to reach back in time to previously applied archive logs to apply new ones?
The %u does resolve, but this message isn't showing it. Here is that same log entry plus a few previous entries that show it does resolve.
ORA-00279: change 1284618956 generated at 04/13/2012 15:30:05 needed for thread
1
ORA-00289: suggestion :
/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60518_%u_.arc
ORA-00280: change 1284618956 for thread 1 is in sequence #60518
ORA-00278: log file
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_13/o1_mf_1_60517_7rjzox
0l_.arc' no longer needed for this recovery
ORA-00279: change 1284618958 generated at 04/13/2012 15:30:05 needed for thread
1
ORA-00289: suggestion :
/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60519_%u_.arc
ORA-00280: change 1284618958 for thread 1 is in sequence #60519
ORA-00278: log file
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_13/o1_mf_1_60518_7rjzox
0x_.arc' no longer needed for this recovery
ORA-00308: cannot open archived log
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60519_%u_.ar
c'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

RMAN-20242: specification does not match any archive log in the catalog

Dear Experts ,
My rman script is as follows :
4> run
5> {
6> allocate channel dev1 type disk format 'Z:\Rbackup\DMP\db_t%t_s%s_p%p';
7> allocate channel dev2 type disk format 'Z:\Rbackup\DMP\db_t%t_s%s_p%p';
8> backup database FILESPERSET 20 ;
9> backup archivelog until time 'sysdate-1' delete all input ;
10> release channel dev1 ;
11> release channel dev2 ;
12> }
The above script is run every day at 2 PM .
Today accidently I ran this script twice . The second run wiped out the dmp created first . In effect I lost all the archive logs of sysdate-2 to sysdate-1 . After this I took a full backup .
Now though I have a full back , I have lost 1 days archive logs .
Please tell me what are the consequences of this ?
Regards
Renjith Madhavan

Dear ckpt .. the rman-20242 error was in a different scenario ... (sorry for the heading ) ... The one i am talking abt now didnt give any error .. back up was successful ....
My question is what happens if I lost one days archive log though i have taken a full backup .... nothing will happen
but if you restore any old database, which before "archives deleted" later you cannot apply. because those are not exist...
but you have full backup then nothing to worry..
I know this depends on the business requirements .. but could you suggest from your experience a few consequences (generic)if already backed up and those archives not exist in OS.... there is no worries on business requirements..because it is already in RMAN repositry

How to backup the archived log after a crosscheck .

Hi all,
Here is the scenario:
My archive area got full, I moved some archived logs to another destination. My main script to backup archive log raised a error informing that some files were missing, so I issued a crosscheck archivelog all command.
I realized that I did something insane and is there any way to fix it? I mean, how could I backup the missed sequence? Because I'll need to send them to a tape and also register the files in the RMAN's catalog.
Regards and thanks in advance,
Emerson

user11983913 wrote:
Hi all,
Here is the scenario:
My archive area got full, I moved some archived logs to another destination. My main script to backup archive log raised a error informing that some files were missing, so I issued a crosscheck archivelog all command.
I realized that I did something insane and is there any way to fix it? I mean, how could I backup the missed sequence? Because I'll need to send them to a tape and also register the files in the RMAN's catalog.
Regards and thanks in advance,
EmersonHi Emerson
Use the following command to register moved archived redo logs to RMAN repository
CATALOG ARCHIVELOG '';

My Backups and Archive Logs

Hi All,
I have an Oracle 10G installation on a solaris host and at the moment, there are a lot of archive log files on the server, full level 0 backups are executed every week, and level 1 differentials are done on a daily basis, now the problem is that I have a lot of archive log which has not been deleted, I am not sure if I can delete it now.
At the moment, the last backkup which was done today also backed up the archive log as well and the latest sequence ID is 2367, the backup done this morning covered the archive logs up till sequence ID 2351 - 2360. The oldest backup goes as far back as sequence ID 2070. I was wondering whether I can delete all archive logs prior to this sequence ID.
Also, is there a functionality in Enterprise Manager that automatically deletes.
I look forward to your replies.
thanks

If it's a simple "no change to existing scripts" sort of thing you are after, then just add another job to run after the existing ones, as follows (you'll want to follow whatever approach your existing scripts use - this is just a demo.):
$ORACLE_HOME/bin/rman <<EOF
connect target
backup archivelog all delete input;
exit;
EOFAnd add whatever error checking the existing script has (if any).
Or, if changing the existing script/s is OK, add PLUS ARCHIVELOG DELETE INPUT to the script/s.
And TEST it first, before putting it into production.

Does hot backup trigger archive log?

Similar Messages

Maybe you are looking for