Archive log deletion

Similar Questions

• Archive log deletion with no backup of the archive logs

  I suffer from enormous size archive of the newspaper. In my previous post, I asked for help. I almost 480 GB archive log every day in our database of 11 2 under redhat linux 5.8 GR. Now, if you please help me in another case.
  
  If I take backup of archive logs and run delete archivelog everything until ' sysdate-1' with each backup database of day how it affects. " In my opinion there should be no problem in that I have the last incremental backup and recovery 1 days archive log in archivelog destination. If I do not archive log backups to how it will be different. Help, please.

  >

  Hello

  Sir, I know how to remove. But in my opinion delete up to sysdate-1 and taking no backup of the Archives of newspapers will
  no effect. Is in my opinion is right or wrong, that is the question.

  What I read in your original post, is that you take a daily incremental backup - Yes? I'm assuming that you also take
  a full backup on a regular basis (Sunday?).

  I was working on the assumption that the foregoing is available? I worked on a project where installation has been similar. We
  tested regularly backups - I hope that you do the same thing?

  What we used to do was FTP (script Unix - cron job - if you Google you will find Python or Perl to do the same thing - that is)
  what I wanted to, but was cancelled - very 1980, anyway) the archived redo logs on to a specific computer that holds only these files.
  After FTP "d - they have been removed from the server, freeing up space.

  Now, you say you have TB 0.5 per day - while more than a week, you will need a machine with ~ 3 TB of disk - if you can get a kind
  the scenario as this place and running, then you will have both your incremental backup and your archived redo logs for the last
  24 hours and the full backup with recovery archived records dating back to this full backup. You can also always archive on tape if
  suits. So, you will have redundant coverage - 'belt and braces' as the Americans say.

  But, to answer your question directly, "take no backup of archive logs have no effect" - that is true - it
  will not affect the operation of the database server, but if I were you, I would hang on to enough archived redo log to return to the
  last backup. That's just my humble OPINION.

  HTH,

  Paul...

  Published by: Paulie July 21, 2012 19:28

• Archive log deletion policy explanation

  How can the archived logs are deleted automatically by the database? I don't get it...
  
  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#CHDCFHBG
  
  I quote:
  
  Archived recovery logs can be deleted automatically by the database or RMAN command initiated by the user. Only newspapers in the field of quick recovery can be deleted automatically by the database.
  
  When that will happen? Without RMAN?
  
  Any ideas?

  Hello;

  If you use FRA as destination for you archive logs they will get deleted until the following conditions:

  1. If there is pressure of space in the flash recovery area (Oracle decides)

  2. what policy of removal of rman archive log is configured.

  3. when the recovery window retention policy is configured and when all unwanted archives are saved.

  Here, there is a short note which will help you understand:

  http://www.oraclefaq.NET/2007/10/18/archive-log-automatically-getting-deleted-from-Oracle-10G-database-with-OMF/

  This can also help:

  http://docs.Oracle.com/CD/B19306_01/backup.102/b14192/rpfbdb001.htm

  http://umardba.blogspot.com/2010/03/maintenance-of-archivelogs-on-standby.html

  Best regards

  mseberg

• archive log deletion pending

  Hi all
  
  I'm working on oracle database enterprise edition 10.2.0.4.I have created a database.the physical standby of the primary database name is prim and the standby database name Eve.He has 100 files of newspapers to archive are generating each size is 300 MB per day. I applied archive log political removal of watch on the primary database. So all the newspaper shifted and applied pending archive are deleted from primary. But my concern is the archive logs staggered into sleep mode. The archivelogs in the standby server must be deleted.how that it can be removed. Help, please

  use RMAN to this effect, as you do in primaries.

  It will make a backup if you need and delete the archivelogs.

• Data Guard archive political deletion log

  Hi all

  I configured the data guard with 2 bases Eve in oracle 11g.

  I want to use rman to delete archives on all servers.

  I have configured no FRA, no recovery catalog.

  My question is:

  If I delete waiting til sequence # 1627 and on primary sequence til = # = 1620 or vice versa this would cause problems for Data Guard.

  I say delete until the different sequences # on primary and standby cause problems for synchronization?

  Thank you

  So if I understand delete archivelog to sysdate - or delete archivelog all completed before sysdate n is not the archivelog deletion policy you put on RMAN?

  She depends on it. The note was made at the base of the MOS document how ensure that RMAN is NOT delete archived logs that have not yet shipped to standby mode (Doc ID 394261.1)

  Delete archivelog to sysdate - depends on all of the deletion policy. If the deletion policy is set on "applied pending all", then it does not delete the archives, if they are not applied on the day before. If the deletion policy is set to none, then it does not check if the archive is applied on the eve and deletes them directly.

  Last Archive generated on primary:

  SYS@oraprim > select max(sequence#) from v$ archived_log;

  MAX(SEQUENCE#)

  --------------

  114

  Last check-in applied in mode ensures:

  SYS@orastb > select max(sequence#) from v$ archived_log in case of application = 'YES ';

  MAX(SEQUENCE#)

  --------------

  109

  Delete policy set to NONE on primary:

  RMAN > show archivelog deletion policy;

  using the control file of the target instead of recovery catalog database

  RMAN settings for database with db_unique_name ORAPRIM are:

  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY;

  RMAN > delete archivelog until 'sysdate;

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 60 type of device = DISK

  List copies of newspapers archived to database with db_unique_name ORAPRIM

  =====================================================================

  Thrd Seq S key low time

  ------- ---- ------- - ---------

  110-1-214 A JANUARY 13, 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_110.318.901050727

  216-1-111 A JANUARY 13, 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_111.317.901050731

  217-1-112 A JANUARY 13, 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_112.316.901050731

  113. OF 1 219 A 13 JANUARY 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_113.315.901050733

  222 1 114 A JANUARY 13, 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_114.314.901050737

  You sure you want to delete the items above (enter YES or NO)? NO.

  It is the removal of primary archives that have not yet been applied on the eve.

  Delete policy 'APPLIES ON STANDBY ALL' value on the primary:

  RMAN > show archivelog deletion policy;

  RMAN settings for database with db_unique_name ORAPRIM are:

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

  RMAN > delete archivelog until 'sysdate;

  output channel: ORA_DISK_1

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 60 type of device = DISK

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_110.318.901050727 thread = 1 sequence = 110

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_111.317.901050731 thread = 1 sequence = 111

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_112.316.901050731 thread = 1 sequence = 112

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_113.315.901050733 thread = 1 sequence = 113

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_114.314.901050737 thread = 1 sequence = 114

  It checks if the archive has been applied on the day before. As the 110 to 114 sequence is not applied in the waiting, the archives are not deleted on the primary.

  Hope that gives you a clear picture of how it works.

  -Jonathan Rolland

• RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

  Hi Oracle Community,

  I have a few databases (11.2.0.4 POWER 2 block and 12.1.0.2) with Data Guard. Back up this database with RMAN to ribbons, only on the primaries.

  During the backup, sometimes I got RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

  By reason of this global warning to backup status is "COMPLETED WITH WARNINGS". Is it possible to remove this warning, or perhaps change RMAN configuration to avoid the appearance of this warning?

  Concerning

  J

  Where is the problem on these warnings? If you do not want to see such warnings, why not simply to perform the removal of the archivelogs in a separate step? For example:

  RMAN> backup database plus archivelog;
  RMAN> delete noprompt archivelog all completed before 'sysdate-1';
  

• delete files from archive log with rman

  Hi guys,.

  I try to delete the log file archive on my backup site, but I get the following message. There are a lot of archive logs is present on the storage but rman may show that. No idea what I'm doing wrong here.

  RMAN > list archivelog all;

  specification does not match any newspaper archived in the repository

  RMAN >

  Kind regards

  Sorry about that. Its 11g 2 R (11.2.0.1) and OS Version is 2008 R2 64 bit. Sleep is in auto recovery mode. (hope this helps).

• Current archive log has been deleted, how to recover using the previous archive log?

  Hello
  
  My current log sequence #819 and it has been deleted and no other choice to get it back and I have previous newspapers archived with sequences #814 à 818.
  
  When I start my database is to show that the use ' MUST USE RESETLOGS or NORESETLOGS option of database open, then I used the command
  
  SQL > ALTER DATABASE OPEN RESETLOGS;
  ALTER DATABASE OPEN RESETLOGS
  *
  ERROR on line 1:
  ORA-01113: file 1 needs media recovery
  ORA-01110: data file 1: ' E:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01. DBF'
  
  SQL > alter database recover;
  ALTER database recover
  *
  ERROR on line 1:
  ORA-00283: cool cancelled due to errors
  ORA-01610: recovery using BACKUP CONTROLFILE option must be
  SQL > alter database recovery using backup controlfile;
  change the database recovery using backup controlfile
  *
  ERROR on line 1:
  ORA-00279: change 8433746 September at 15/01/2013 19:51:59 needed to screw 1
  ORA-00289: suggestion:
  E:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_01_16\O1_MF_1_819_
  
  % U_. ARC
  ORA-00280: change 8433746 thread 1 is in sequence #819
  
  now, I don't have the log archiving with 819 sequence, I recover from 818. Please tell me how to do?

  Hello

  1. select * from v$log and see which log file is current. Query v$logfile to check physical file location belonging to current log group.
  2. Take bacup of your curent control file using copy/paste of your OS
  3. Issue following command in mount state
  recover database until cancel using backup controlfile
  4. When it finishes applying available archived logs, still it will ask for the location of archived logs which have not been applied, here provide path of current redo log file you got in first step. Here your recovery will finish after applying current redo log
  5.alter database open resetlogs.
  

  Salman

• Delete pending archive logs

  Hello
  
  My oracle database is 11.2.0.2 RDBMS RAC on RHEL 5. 6
  
  We have recently established physics of the standby database. How to remove archive logs waiting for physical standby mode?

  Hello;

  There is a little different to do this. I would consider these notes:

  How to ensure that RMAN is NOT delete archived logs that have not yet shipped to standby [394261.1 ID]

  RMAN removes records of logs on the primary database not applied pending physical [ID 1324759.1]

  Configure RMAN to purge the archivelogs after application on hold [728053.1 ID]

  You can use an RMAN script to do this:

  echo "Starting RMAN..."
  $ORACLE_HOME/bin/rman target / catalog user/password@rcatalog << EOF
  
  delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';
  
  exit
  EOF
  

  Best regards

  mseberg

• RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  I get RMAN-08120: WARNING: journal archived not deleted, not yet applied watch on primaries
  but when I run under query, I get the same result of primary and backup
  
  SQL > select max(sequence#) from v$ archived_log;
  
  MAX(SEQUENCE#)
  --------------
  44051
  
  SQL >
  
  
  Eve is a log switch behind only!

  Hello;

  If RMAN tries to remove an archive which is not yet applied in standby log, you see the RMAN-08120

  It's a good thing. As long as you don't have any archives for days on standby, you probably don't have a problem.

  What are your RMAN settings for the database of the day before?

  MetaLink Note: 361182.1 can help too. Or Note 1079953.1

  Your main, make sure that:

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
  

  Please consider closing some of your old issues to clean up the forum.

  Best regards

  mseberg

• delete the archive logs after cold backup?

  Hi all
  my database is in archivelog mode, I do COLD backup every night, can I just remove the archive logs after I do my cold backup, because there is no need of them, as the closed DB should have all the info in the archived papers
  
  and archive connected is needed only during the day, if a sudden power outage that happened.
  
  Thank you very much

  The ArchiveLogs allow you RollForward a backup restored to a specific point in time.

  Assuming that stop you your database at 23:00 (2300) every night and backup up to 11 h 45 (2345) tracks...

  Significant transactions entered between 15:00 and 16:00 on Friday, but a person deleted by mistake the lines (or some other lines) at 17:00

  your current backup strategy of "restoration" of the database only allows 23:00 Thursday night. If you also back up your archivelogs (in this case, the backup of Friday night would the archivelogs), you restore Thursday night backup 'cold' and "rollforward" by publishing a RECOVER database with the HELP of BACKUP CONTROLFILE until 16:00 Friday.

• Deletion of backups of level 1 and archive logs

  Hello
  
  Everyone knows that "the retention policy would be applicable on level 0 backups or only full backups.
  
  So how will be reported what backups and level 1 backup of archive logs are no longer needed for recovery?
  
  And after that as the command "remove obsolete", y at - it a command to remove these unwanted 1 level and archiving logs backups?
  
  Any suggestion?
  
  Thank you
  Nitesh.

  So how will be reported what backups and level 1 backup of archive logs are no longer needed for recovery?

  If you have the revoery retention strategy window 1 day and you take backup of level 0 Sat and then consecutive level until Friday 1 daily backup, again on backup sat level 0 will be obsolete previous level 0 backup sat and its seven consecutive level 1 so is found in the archived log alls before this level 0 current backup will be marked.

  Obsolete report will show you alls backup piece and the archivelogs that are marked as obsolete.

  And after that as the command "remove obsolete", y at - it a command to remove these unwanted 1 level and archiving logs backups?

  What do you mean by backups, undesirable level 1, on what basis you say that backup of level 1 are undesirable?

  Khurram

• Problem with the archive log when you use RMAN for backup and restore (11g 2)

  Hello world
  Please help me solve this problem.
  I'm just beginner in Oracle Database (11 g 2). Today, I had a problem, I tried to back up and restore my db by RMAN. I delete all the files in /u01/app/oracle/oradata/orcl / * , then I restore them easily, but the point is I have a table, I can restore Hungarian, but cannot restore anything ranks in it (something wrong with step restore database). I'll tell the detail below.
  -First, I create a 'Day' with command table create table hr.day (varchar (20)) day. Then I backup complete by this:
  run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_FULL_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 0 tag 'DB_FULL' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}
  

  
  D ' other hand, I have insert 'Monday' to table. then do an incremental backup by this:

  run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_INC_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 1 tag 'DB_INC' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_INC' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}

  Repeat 7 times (Monday-> Saturday). And I got these files:

  [oracle@rac ~]$ ls -l /u01/backup/
total 400280
-rw-r----- 1 oracle oinstall  10158080 Jan 20 07:23 c-1428943247-20160120-01
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:04 c-1428943247-20160120-02
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:05 c-1428943247-20160120-03
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:06 c-1428943247-20160120-04
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-05
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-06
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:09 c-1428943247-20160120-07
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:32 c-1428943247-20160120-08
-rw-r----- 1 oracle oinstall 296337408 Jan 20 07:23 DB_FULL_ORCL_20160120_s89_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 07:23 DB_FULL_ORCL_20160120_s90_p1
-rw-r----- 1 oracle oinstall   2266624 Jan 20 07:23 DB_FULL_ORCL_20160120_s91_p1
-rw-r----- 1 oracle oinstall   4073984 Jan 20 07:23 DB_FULL_ORCL_20160120_s92_p1
-rw-r----- 1 oracle oinstall  11201536 Jan 20 07:23 DB_FULL_ORCL_20160120_s93_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:05 DB_INC_ORCL_20160120_s100_p1
-rw-r----- 1 oracle oinstall    146944 Jan 20 08:05 DB_INC_ORCL_20160120_s101_p1
-rw-r----- 1 oracle oinstall    884736 Jan 20 08:06 DB_INC_ORCL_20160120_s103_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:06 DB_INC_ORCL_20160120_s104_p1
-rw-r----- 1 oracle oinstall     82432 Jan 20 08:06 DB_INC_ORCL_20160120_s105_p1
-rw-r----- 1 oracle oinstall    294912 Jan 20 08:07 DB_INC_ORCL_20160120_s107_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:07 DB_INC_ORCL_20160120_s108_p1
-rw-r----- 1 oracle oinstall     18944 Jan 20 08:08 DB_INC_ORCL_20160120_s109_p1
-rw-r----- 1 oracle oinstall    155648 Jan 20 08:08 DB_INC_ORCL_20160120_s111_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:08 DB_INC_ORCL_20160120_s112_p1
-rw-r----- 1 oracle oinstall    131584 Jan 20 08:08 DB_INC_ORCL_20160120_s113_p1
-rw-r----- 1 oracle oinstall    647168 Jan 20 08:09 DB_INC_ORCL_20160120_s115_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:09 DB_INC_ORCL_20160120_s116_p1
-rw-r----- 1 oracle oinstall      8704 Jan 20 08:09 DB_INC_ORCL_20160120_s117_p1
-rw-r----- 1 oracle oinstall   2203648 Jan 20 08:04 DB_INC_ORCL_20160120_s95_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:04 DB_INC_ORCL_20160120_s96_p1
-rw-r----- 1 oracle oinstall   1899008 Jan 20 08:04 DB_INC_ORCL_20160120_s97_p1
-rw-r----- 1 oracle oinstall    327680 Jan 20 08:05 DB_INC_ORCL_20160120_s99_p1


  And
  RMAN> list backup summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
80      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
81      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
82      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
83      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
84      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
85      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T072332
86      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
87      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
88      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
89      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080440
90      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
91      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
92      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
93      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080545
94      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
95      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
96      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
97      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080657
98      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
99      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
100     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
101     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080801
102     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
103     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
104     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
105     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080844
106     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
107     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
108     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC

  My configuration of rman:
  RMAN> show all;
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/backup/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/u01/backup/backup_df%t_s%s_s%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome/dbs/snapcf_orcl.f'; # default

  - Thirdly, i removed all file in /u01/app/oracle/oradata/orcl/*. then restore control file from the newest backup control file (saturday backup) + restore database. Seem nothing's wrong here.
RMAN> restore controlfile from '/u01/backup/c-1428943247-20160120-08';
Starting restore at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=20 device type=DISK
channel ORA_DISK_2: skipped, AUTOBACKUP already found
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:09
output file name=/u01/app/oracle/oradata/orcl/control01.ctl
output file name=/u01/app/oracle/flash_recovery_area/orcl/control02.ctl
Finished restore at 20-JAN-16

RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
released channel: ORA_DISK_2

RMAN> restore database;
Starting restore at 20-JAN-16
Starting implicit crosscheck backup at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=18 device type=DISK
Crosschecked 29 objects
Finished implicit crosscheck backup at 20-JAN-16

Starting implicit crosscheck copy at 20-JAN-16
using channel ORA_DISK_1
using channel ORA_DISK_2
Finished implicit crosscheck copy at 20-JAN-16

searching for all files in the recovery area
cataloging files...
no files cataloged

using channel ORA_DISK_1
using channel ORA_DISK_2

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_FULL_ORCL_20160120_s89_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_FULL_ORCL_20160120_s89_p1 tag=DB_FULL
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:15
Finished restore at 20-JAN-16


  -Fourth, the problem here, I got the database;
.. .every oky until this line...
starting media recovery

channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=15
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_INC_ORCL_20160120_s117_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_INC_ORCL_20160120_s117_p1 tag=ARCL_BKP_INC
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2016_01_20/o1_mf_1_15_c9xsyx9k_.arc thread=1 sequence=15
unable to find archived log
archived log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/20/2016 08:50:22
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 1205841

The error said that it is impossible to find the archived log thread = 1 sequence = 1. Then I check it with this command always there (oh, I'm wrong?)
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
82      2.16M      DISK        00:00:00     20-JAN-16     
        BP Key: 82   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s91_p1

  List of Archived Logs in backup set 82
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
1    1       1154833    20-JAN-16 1177422    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
83      3.88M      DISK        00:00:00     20-JAN-16     
        BP Key: 83   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s92_p1

  List of Archived Logs in backup set 83
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
1    1       1162729    20-JAN-16 1188784    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
84      10.68M     DISK        00:00:01     20-JAN-16     
        BP Key: 84   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s93_p1

  List of Archived Logs in backup set 84
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    2       1177422    20-JAN-16 1201833    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
88      1.81M      DISK        00:00:01     20-JAN-16     
        BP Key: 88   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s97_p1

  List of Archived Logs in backup set 88
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    3       1201833    20-JAN-16 1204844    20-JAN-16
  1    4       1204844    20-JAN-16 1204893    20-JAN-16
  1    5       1204893    20-JAN-16 1204958    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
92      143.00K    DISK        00:00:00     20-JAN-16     
        BP Key: 92   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s101_p1

  List of Archived Logs in backup set 92
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    6       1204958    20-JAN-16 1205034    20-JAN-16
  1    7       1205034    20-JAN-16 1205253    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
96      80.00K     DISK        00:00:00     20-JAN-16     
        BP Key: 96   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s105_p1

  List of Archived Logs in backup set 96
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    8       1205253    20-JAN-16 1205354    20-JAN-16
  1    9       1205354    20-JAN-16 1205433    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
100     18.00K     DISK        00:00:00     20-JAN-16     
        BP Key: 100   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s109_p1

  List of Archived Logs in backup set 100
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    10      1205433    20-JAN-16 1205519    20-JAN-16
  1    11      1205519    20-JAN-16 1205559    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
104     128.00K    DISK        00:00:00     20-JAN-16     
        BP Key: 104   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s113_p1

  List of Archived Logs in backup set 104
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    12      1205559    20-JAN-16 1205624    20-JAN-16
  1    13      1205624    20-JAN-16 1205739    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
108     8.00K      DISK        00:00:00     20-JAN-16     
        BP Key: 108   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s117_p1

  List of Archived Logs in backup set 108
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    14      1205739    20-JAN-16 1205796    20-JAN-16
  1    15      1205796    20-JAN-16 1205840    20-JAN-16

  
If i ignore it and open the database, just my table in full backup come back but rows was not restored. I'm sure the problem is my archive log backup but i don't know how to solve it. Plz help me.

  Sorry for a long post.


  > 1 and from the 1205841 SNA sequence

  The SCN that indicates Oracle is above the range of SNA that you have in the ArchiveLog backups for sequence 1 to 15 (15 sequence ends at 1205840).

  The message

  channel ORA_DISK_1: restoring archives Journal

  Archives journal thread = 1 sequence = 15

  channel ORA_DISK_1: backup/u01/backup/DB_INC_ORCL_20160120_s117_p1 piece reading

  channel ORA_DISK_1: piece handle = / u01/backup/DB_INC_ORCL_20160120_s117_p1 tag = ARCL_BKP_INC

  indicates that he has restored the sequence up to 15

  You can check the log file alert database instance for messages on the fact of recovery.

  He is now asking sequence #1 it seems you did a RESETLOGS after sequence #15.

  Note: If you have NOT issued a COMMIT after the line is INSERTED in the table 'Day', the recovery of the database will have no * transactions * to retrieve.  An uncomitted transaction is cancelled.

  Hemant K Collette

• Data Guard - RMAN removing archive log

  Hello

  I ' v DataGuard with physical standby.

  I do a backup only on the primaries. Both sites have ther separate backup systems.

  I ' v FRA and configured archivelog deletion with RMAN configuration:

  on primary: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

  standby: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;

  It works fine but I think what if scenarios and I'v qestion on best practices for backup after the transition of role management. Let's say that for some reason, as i'v in switch mode sleep for a few days and the backup will be posible to watch (now primary) database. What would be the steps/reconfiguration appropriate to do?

  1 should I reconfigure RMAN?

  change of new primary to: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

  change back to sleep again: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;

  2. make full backup

  Hello

  1. you can refer to the oracle documentation: http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#CHDCFHBG

  section: "all archived Redo Log deletion policy."

  Document provides the best algorithm to analysis of work

  You can use the CONFIGURE ARCHIVELOG DELETION POLICY BACKED UP integer TIMES TO DEVICE TYPE command to allow a policy of removal of archived newspaper. This configuration specifies that archived newspapers are eligible for deletion only when the specified number of archived log backups exist on the specified device type.

  
  

  If the deletion policy is configured with the BACKED UP integer TIMES clause, then a BACKUP ARCHIVELOG , the command copy newspapers, unless integer already exist on the specified device type backups. If integer are backups of logs, then the BACKUP ARCHIVELOG command ignores the newspapers. In this way, the deletion of archived newspaper policy works as a default NOT BACKED UP integer TIMES clause on the BACKUP ARCHIVELOG command. Note that you can override the deletion policy by specifying the FORCE option on the BACKUP command.

  The deletion of archived newspaper policy has also options specific to an environment Data Guard. , then RMAN can delete logs after they have been applied to all destinations remote mandatory. If you specify SHIPPED TO STANDBY , for example, then RMAN can remove log files when they were transferred to all destinations of mandatory relief.

  2. the paper provides good information, just to check and decide easily based on the functionality of the database role you can configure.

  It will be useful.

  -Thank you

  Pavan Kumar N

• can't understand why an extract of the database restore fails (missing archive logs)

  Dear,

  I'm completely back up my database ensures every night with following statement.

  full backup AS BACKUPSET COMPRESSED ORCL_FULL_STBY format database tag ' / oradata/archive/fast_recovery_area/%d_%T_%s_%p_FULL_STBY' more tag ORCL_FULL_STBY archivelog delete all entries;

  I wanted to check with 'restore... Preview' if my backup is good enough to restore the database from scratch.
  result = failed!
  Reason:
  "any backup log archived for thread 1 with sequence 65 and YVERT departure from 49020676 found to restore."

  I have read the documentation oracle and articles for days, but I did not understand that even though I take online backup yesterday if I want to restore my database today I still need archival newspapers last month?

  can you please review my analysis and tell me where I am doing wrong?

  for example a piece from my last backup;

  Time of accomplishment BS key Type LV size device Type elapsed time
  ------- ---- -- ---------- ----------- ------------ ---------------
  1008 full 199.25 M DISK 00:04:44 October 8, 15
  BP key: 1010 situation: AVAILABLE Tablet: YES Tag: ORCL_FULL_STBY
  Item name: / oradata/archive/fast_recovery_area/QIPDB1_20151008_1057_1_FULL_STBY
  List of defined backup data files 1008
  Name of file LV Type cash SNA cash time
  ---- -- ---- ---------- --------- ----
  50570723 full 1 8 October 15 /oradata/data/qipdb1/system01.dbf
  4 integer 50570723 8 October 15 /oradata/data/qipdb1/users01.dbf

  as you can see "Cash SNA" is 50570723 so tells me that my understanding if restore these backups I need archived newspapers on top of the YVERT.
  for me the best candidate is

  Time of accomplishment time BS key size Device Type
  ------- ---------- ----------- ------------ ---------------
  65,25 M 1004 00:01 DRIVE: 24 OCTOBER 8, 15
  BP key: 1006 situation: AVAILABLE Tablet: YES Tag: ORCL_FULL_STBY
  Part name: /oradata/archive/fast_recovery_area/QIPDB1_STBY/backupset/2015_10_08/o1_mf_annnn_ORCL_FULL_STBY_c1dkfw9k_.bkp

  List of newspapers archived in backup set 1004
  The next time that THRD Seq YVERT low low time next YVERT
  ---- ------- ---------- --------- ---------- ---------
  1 79 50310555 7 OCTOBER 15 50570723 8 OCTOBER 15
  
  BUT out of "restore...". Preview' RMAN stil tells me that

  any backup log archived for thread 1 with sequence 65 and YVERT departure from 49020676 found to restore
  any backup log archived for thread 1 with sequence 66 and YVERT departure from 49020693 found to restore
  any backup log archived for thread 1 with sequence 67 and YVERT departure from 49020696 found to restore
  any backup log archived for thread 1 with sequence 68 and YVERT departure from 49020761 found to restore
  any backup log archived for thread 1 with sequence 69 and YVERT departure from 49020836 found to restore
  any backup log archived for thread 1 with sequence 70 and YVERT departure from 49020919 found to restore
  any backup log archived for thread 1 with sequence 71 and YVERT departure from 49021021 found to restore
  any backup log archived for thread 1 with sequence 72 and YVERT departure from 49155291 found to restore
  any backup log archived for thread 1 with sequence 73 and YVERT departure from 49324912 found to restore
  any backup log archived for thread 1 with sequence 74 and YVERT departure from 49498102 found to restore

  When I look at V$ ARCHIVED_LOG I see seems indeed to these archived logs removed for cause of "more tag ORCL_FULL_STBY archivelog delete all entries ' that they have been deleetd after saving.
  and because of my retention policy and script; I remove the logs also archived backups that are more than 2 days.

  S SEQUENCE # FIRST_CHANGE # NEXT_CHANGE #.
  - ---------- ------------- ------------
  65 49020676 49020693 D
  A 49020693 OF 49020676 65
  D 68 49020761 49020836
  66 49020693 49020696 D
  67 49020696 49020761 D
  69 49020836 49020919 D
  70 49020919 49021021 D
  49155291 49021021 71 D
  72 49155291 49324912 D
  D 73 49324912 49498102
  74 49498102 49632131 D

  I still don't understand why rman complains of the archived logs that are for an older sequence (SNA) as my last backup
  because I was assuming that the concerned newspapers archived should have already applied to these files of data, right?

  My final goal is to deliver below for the case that we have lost everything.

  Run {}
  restore the database;
  recover the database;
  }

  Thanks in advance,
  Halit

  Hi guys,.

  I found the root cause and workaround

  RMAN-06025 - RMAN RESTORE DATABASE OVERVIEW to the backup site asks former newspaper (Doc ID 1599013.1)

  CAUSE Checkpoint_change# standby controlfile not refreshed properly.  BUG 15876029 - RESTORE PREVIEW ASKING OLD ARCHIVE LOG IN STANDBY DATABASE  Closed as DUPLICATE of  BUG 8740124 - CURRENT STANDBY REDO LOG GROUP SHOULD BE INCLUDED IN THE DATABASE BACKUP BY RMAN SOLUTION  1) Workaround is to recreate the standby controlfile.  OR  2) upgrade to 11.2.0.4 or above where Bug 8740124  is fixed  OR  3) check for availability of patch 8740124