Retention policy for archive logs.

Similar Questions

• Secondary destination for archived logs

  Version: 10.2, 11.1, 11.2
  
  Occasionally, we get "archiver error" on our production because of our satiety LOG_ARCHIVE_DEST_1 DBs. How can I have a secondary for archiving logs location where my position "primary" (LOG_ARCHIVE_DEST_1) saturates?
  
  I think that LOG_ARCHIVE_DEST_2 is reserved for archiving to Dataguard standby DB logs in which specify you the day before tns input using the parameter of the shipping SERVICE.
  
  Can I specify LOG_ARCHIVE_DEST_3 as my secondary site in case LOG_ARCHIVE_DEST_1 saturates? -What is LOG_ARCHIVE_DEST_n meant for? Even though the documentation says that you can have up to 10 locations, I'm confused, if they are intended to store copies of archive logs multiplex? This is not what I'm looking for?

  >

  Hi Tom,

  Occasionally, we get "archiver error" on our production because of our satiety LOG_ARCHIVE_DEST_1 DBs. How
  can I have a secondary for archiving logs location where my position "primary" (LOG_ARCHIVE_DEST_1) saturates?

  From [https://forums.oracle.com/forums/thread.jspa?threadID=1033460 url] here:

  LOG_ARCHIVE_DEST_STATE_n = ALTERNATE
  To specify the nth destination metnioned in the LOG_ARCHIVE_DEST_n as a destination alternative.

  Look at "replacement" [url http://docs.oracle.com/cd/E14072_01/server.112/e10595/archredo004.htm] here - if all else fails, read the docco ;)

  Also check out here [url http://docs.oracle.com/cd/B10501_01/server.920/a96521/archredo.htm].
  HTH,

  Paul...

• RMAN retention policy does not log source archive

  Oracle 11.2
  Windows server 2008
  CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED 1 TIME TO THE DISK.
  
  I ran after command
  TIME BACKUP ARCHIVELOG ' SYSDATE-6' UNTIL ' SYSDATE-1';
  
  RMAN > ARCHIVELOG BACKUP OF TIME ' SYSDATE-6' until ' SYSDATE-1';
  
  From backup may 29, 13
  using the control file of the target instead of recovery catalog database
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID = 386 type device = DISK
  allocated channel: ORA_DISK_2
  channel ORA_DISK_2: SID = 773 type device = DISK
  jump the C:\ARC\ARC0000000564_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000564_0808506935.0001; already saved 1 time
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000565_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000565_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000566_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000566_0808506935.0001 archived log file; already supported
  up to 1 times
  jump the C:\ARC\ARC0000000567_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000567_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000568_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000568_0808506935.0001; already saved 1 time
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000569_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000569_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000570_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000570_0808506935.0001 archived log file; already supported
  up to 1 times
  Backup finished 29 May 13
  
  RMAN >
  
  
  According to policy to delete rman does not delete source archive logs.

  This is the backup... command where the delete command

  obsolete report;

  Confirm if the archivelog you want to remove, then

  remove obsolete;

  so if you had manually deleted archivelogs use below to remove the entry of records controlfile

  overlap archivelog all;

  list expired archivelog all;

  REMOVE EXPIRED ARCHIVELOG ALL;

  edited part-

  read [url http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#CHDCFHBG]

  This plocy deletion makes these archivelog eligible for deletion. They will be deleted automatocally if they are inside the FRA FRA is short of space.

  Published by: Patricia kebe on May 29, 2013 01:16

• Retention policy for the grid control

  Hello

  One of our clients wants to change the retention policy of the Grid control to 2 years in order to check the statistics of the application of these last 2 years,

  Default purge policy is as follows:

  Raw metrics - 7 days

  An hour aggregate metrics data - 31 days

  A day aggregate metrics data - 365 days

  Having someone of you will never change these default policies to a great values?

  I'm afraid of performance issues

  Depends on what policy they want change, but I n ' tthink this will help you at all.  If they are looking for AWR data, it is not stored in MS, unless you configure CWA warehouse.   EM will be measures such as SQL response time, but it does not store the SQL query and the stats you'd see in an AWR report.   Storing so for 2 years will not help.  If you want just generic performance history, then changing strategies of purge will be fine, but you don't want to store the raw data for 2 years. Keep in mind that you will increase the size of your repository database as well.

• The Archive Log backup retention policy

  How can I define retention policy for backups of the log of the Archives?

  The question and the answer that you have marked as "Right answer" is misleading.

  For removal of journal policy archived, see below.

  Configuration of RMAN environment

  For the real question displayed "How can I define retention policy for backups of the log of the archives?", see link below. ""

  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#i1019318

  Also, have you started the thread to clear your doubts or test other users of the forum?

  Thank you!!

• RMAN: Deletion retention policy policy VS Archivelog

  I am a newbie to RMAN, so I did a lot of reading and experimentation, and I'm stuck on a problem.

  TASK: I want to keep two days of archived newspapers and a days worth of backups.

  SOLUTION: set 1 retention policy, set the deletion policy to archive 2

  (CONFIGURE ARCHIVELOG DELETION of SAVED POLICY 2 TIMES TO THE DISK.)

  and it's my simple backup script

  run

  {

  database backup "nightly_backup" tag more archivelog;

  delete noprompt obsolete;

  }

  PROBLEM: it does not work. Oracle documentation clearly (as clearly as possible the documentation) that "remove obsolete" uses the retention policy to clear logs archived. and deletion policy deletion archivelog to use "delete archivelog all;

  My tests verifies this.

  ISSUE. How remove the database obsolete backupsets ONLY by using the delete command?

  -Mark

  Just for clarity - if other people who have this issue will find this thread-I found the answer.

  Two policies are in effect only when you use the quick recovery for all your backup needs area. The database will automatically manage files according to policies. But as soon as you run manually ' rman > delete noprompt obsolete ' Oracle will only follow the retention policy.

  So as soon as FRA got up to about 78 percent full, he began to delete files, you can see in the alert.log

  Deleted Oracle managed file +FRA/sndbox/backupset/2014_07_23/annnf0_nightly_backup_0.435.853650191

  Deleted Oracle managed file +FRA/sndbox/archivelog/2014_07_23/thread_1_seq_204.439.853668327

  Deleted Oracle managed file +FRA/sndbox/autobackup/2014_07_23/s_853650247.441.853650249

  Deleted Oracle managed file +FRA/sndbox/archivelog/2014_07_23/thread_2_seq_189.434.853668653

  Another consequence of this fun is that Oracle will not automatically manage files outside of the FRA. So, if you save FRA on the disk, Oracle removes only files of FRA. If you must manually remove FRA backups, but which will also remove the FRA files according to the retention policies.

• backup with the retention policy to recovery of N days window

  Hello

  I did command to create an incremental backup of database with the configuration:

  run

  {

  Configure retention policy to recovery of 14 days window;

  backup incremental level 1 cumulative

  tag daily_incr_14_days

  database

  more archivelog delete all input;

  }

  All parameters are set to their default values, and backups of data goes to FRA. I've got catalog recovery connected and all the views RC_ at my disposal.

  (1) is it possible to know which window of recovery has been used for any command in the rman backup or query view RC_ or local database (control file information)?

  (2) if I use other settings of window of recovery with command configures which would overlap or report rman commands do?

  BR

  Sandrine.

  TenakaKhan wrote:

  Mahir,

  Thanks for the reply - in other words, this window of recovery should be used mainly for maintenance purposes (overlap, remove obsolete, report need backup etc.) and he was not associated with the actual with backup items as retention period "keep until the" safeguard clause... command database (this information are saved with the backup as I could verify according to rc_backup_set of the recovery catalog)?

  Yes.

  Maintaining backups RMAN and repository & nbsp; Reviews

  keepOption

  backup retention policy

  A policy defined by the user to determine how long the backups and archived logs must be kept for the media recovery. You can define a retention policy in terms of redundancy backup or a recovery window.

  RMAN keeps backups of data files that are required to meet the current retention policy, and all logs archived redo necessary to a complete recovery of data files.

  Recovery window

  A recovery window is a type of RMAN backup retention policy, in which the ADMINISTRATOR specifies a period of time and RMAN ensures the retention of backups and Archives redo logs required for recovery to point-in-time at any time during the recovery window.

  The interval always ends at the present time and is extended in time for the number of days specified by the user. For example, if the retention policy is set for a window of recovery of seven days and the current time is 11:00 Tuesday

  RMAN maintains the necessary backups to recover point-in-time at 11:00 the previous Tuesday.

  Concerning

  Mr. Mahir Quluzade

• RMAN retention policy

  Hello everyone, I think to create a retention policy, but the problem is if I want to have the backup that ran daily from detention for 15 days and each backup run a monthly backup for a year which is the best option to set up the recovery window retention policy, because if I set with 365 days I'm going to keep daily backups for the whole year, suggest or advise

  Hello

  set the retention policy for 15 days (daily policy):

  RMAN > CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 60 DAYS;

  And add keep until 'sysdate + 365' monthly backup.

  RMAN > backup format incremental level 0 '% d.n0.%T.set_%s_%t' TAG data = 'BK_DATA_monthly_20150501' keep until 'SYSDATE + 365' opens a session;

  If you can make backup maintenance with delete obsolete;

  RMAN > remove force noprompt obsolete;

  
  

  It works with oracle 9i, 10g and 11g

• RMAN-06059: expected archived log not found

  DB version: 11.1.0.7
  Operating system: Solaris 10
  
  Our cron job RMAN has met the following error.
  -First save attempt (complete bkp more archive log) done by connecting to the catalog

  Starting backup at 14-MAR-12
  current log archived
  released channel: ch00
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of backup plus archivelog command at 03/14/2012 08:09:58
  RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
  ORA-19625: error identifying file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc
  ORA-17503: ksfdopn:2 Failed to open file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc
  ORA-15173: entry 'pqwsp_26530_1_764525298.arc' does not exist in directory 'pqwsp_arch'

  Because I didn't share RMAN catalog schema password, I used the control as a catalog file and run the CROSSCHECK command.
  
  -Use the control as a catalog file

  $ rman target /
  
  Recovery Manager: Release 11.1.0.7.0 - Production on Wed Mar 14 09:45:59 2012
  
  Copyright (c) 1982, 2007, Oracle.  All rights reserved.
  
  connected to target database: PQWSP (DBID=1638594930)
  
  RMAN> crosscheck archivelog all;
  
  using target database control file instead of recovery catalog
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID=429 instance=pqwsp1 device type=DISK
  validation succeeded for archived log
  archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26563_1_764525298.arc RECID=19019 STAMP=777888587
  validation succeeded for archived log
  archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26564_1_764525298.arc RECID=19022 STAMP=777890270
  validation succeeded for archived log
  .
  .
  .
  .
  .
  
  Crosschecked 14 objects

  Cannot find objects expired in the output above. I had * "validation succeeded" * message to arch all newspapers.
  
  So I ran a

  BACKUP ARCHIVELOG ALL DELETE ALL INPUT;

  and this backup was successful.
  
  No idea why the first attempt failed when there were not all logs archived expired? If I run the command of OVERLAP by connecting to the catalog, I could find out of date newspapers?

  No idea why the first attempt failed when there were not all logs archived expired?
  this case is not releated archivelog expired, however it seems the requested archivelog 26530 isn't available on destinationas, that it can be removed manually or another taking backup operation the backup and deleted if the execution of the whole.

  crosscheck updated detail that its not available for backup... Check the output of you overlap cmd to 26530 archivelog.

  Thank you
  Tylay Singh

• Recovery window retention policy removes the archive logs before backup?

  Hi all

  Oracle 11G on Windows 2008 R2

  This afternoon, I've changed my retention policy RMAN "RETENTION POLICY 3 REDUNDANCY"on RECOVERY WINDOW OF 3 DAYS RETENTION POLICY

  However, I checked tonight and after that my daily backup, all the archive before backup logs had been removed! So that means I don't think I can restore to any point in time, before my daily backup. All newspapers .arc were there after the backup. Then I tried another test and began the daily backup again. During the backup process, archive logs were deleted again! Now, I don't have any archives of newspapers...

  Is this good behavior OF RETENTION POLICY RECOVERY WINDOW? I thought that she would keep all the files needed for to restore me to any point in time for the previous 3 days. When I used a REDUNDANCY, with my daily backups, he kept 3 days of backups + archiving logs so that I could restore point-in-time at any point. How can I use WINDOW RECOVERY so that I can actually restore to any point in time for the 3 days?

  I wanted to change WINDOW of recovery, since I read that using the REDUNDANCY, it keeps only X copy a backup (so if I ran the backup 3 times a day, I would have only these 3).

  Thanks in advance.

  After a database RESTORE, Oracle tries to RECOVER a DATABASE.  He tries to 'find' the archivelogs for this phase in the location expected archivelog.  If they are NOT present in the location expected archivelog, it attempts to restore backups before applying them.

  Since your BACKUP... DELETE ENTRY deletes the archivelogs after that that they are saved, Oracle will have to use backups to recover the archivelogs.

  Hemant K Collette

• Cannot change properties of the log events in the security policy for replace mode archive

  Hello

  We use windows server 2012 R2 Edition OS Server in my organization. We have newspapers of facility security events "archive newspapers when it is full" and he used to use 133 MB of available space. Recently, as the daily logs of the security being created 133 MB size, the local volume was full and I had to delete the old archives manually. Then, we decided to change the settings of the Archive to replace the events if necessary. But when I try to change it and click on apply, it does not seem to apply the changes, his new ghost "archive logs. Please help me out here. Also please ask me questions just in case I missed any important points to mention here. I am a newbie in this forum.

  Hello

  Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

  http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

  See you soon.

• 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

• 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

• With RMAN for backup, but not with the archive logs

  We run a 10.2.0.4 database and the rest 11.2.0.3. All databases are on RHEL 5.7.
  
  Our backups are via RMAN, with the data files, controlfiles and spfile saved to disk, then each day, it is copied off site to a backup server.
  
  My question is around logs archiving and RMAN.
  Our current situation is:
  -We do not save the logs to archive via RMAN. for example: backup of the list of the archivelog all; gives "specification does not match backups in the repository.
  -We set the archive_lag_target so archiving logs is produced every 30 minutes.
  -a cron job running on a remote server runs periodically to synchronize data (rsync server) the directory of archives with a remote control.
  -daily archive logs on the server host are bzip. Purge of these newspapers is scheduled for more than 3 days rman 'window of recovery '.
  
  I'm interested in feedback as to if our strategy around archiving logs is correct or not.
  
  Should we be backup logs archiving via RMAN? Are there potential problems with our approach?
  We just kept our backups in this way the DBA in the past want to see newspapers archived as opposed to it while a backupset.
  
  Curious to know what others are doing.

  Hello

  Welcome to OTN!

  Archivelogs with RMAN backup is a better option. When the archives are supported by RMAN, RMAN would be aware of the backup items which are required at the time of the recovery archives. You don't have to do it manually.

  On the disk space, you can delete the archives once they were saved by RMAN.

  RMAN > delete any backup archivelog entry;

  This supports the archivelogs and then remove the archives from the disk.

  If you have a dataguard configured, you can set the deletion policy 'applied on Eve', which removes the archives as and when they are applied to the database ensures there by the management of disk space again.

  RMAN > configure archivelog political of deletion to applied pending;

• RMAN backup for lack of archive log - Urgent

  Dear all,
  How to take backup in oracle rman for lack of logseq at logseq archiving log.
  
  Please help me urgent.
  
  Thank you
  Manas

  The SNA method before roll is easiest to get your sleep in harmony rather than completely rebuild.

  The RCS on primary continues to rise and if the archives get generated on primary at a regular stage, would be late the night before by a huge margin.

  If there is a gap of newspaper caused lack of archives and his backup is not available, then I'd rather go with the Roll Forward YVERT method.