Delete backups Archivelogs

Hello!

How can I configure rman (11 g/Win2003) to keep my backups of database for 7 days and to remove all logs archiving before this backup without saving the archivelogs.

I added 'DELETE OBSOLETE RECOVERY WINDOW 7 DAYS;' But with that archive logs are not deleted because I don't backup of archive logs.

I need something like "REMOVE OBSOLETE but keep the backupsets for 7 days.

I don't want to use "rman delete archivelog until the ' sysdate-1' ' because if the backup fails I don't want the deletion of archive logs.»

Can someone help me?

Kind regards
Martin

Why you don't want to backup archived redo logs? Note that in general you need to backup archived redo logs as a hot backup / online / incompatible must always archived redo when you are recovering.

You can only configure 1 retention policy that will apply to all games backups (data files and recovery logs archived):

configure retention policy to recovery window of 7 days;

Running OBSOLETE DELETE will delete any backups older than the current RMAN political of retention.

Edited by: P. Forstmann on June 21, 2010 12:31

Tags: Database

Similar Questions

  • My backup archivelog never becomes obsolete for the deletion

    Hello

    I am running version 11.1.0.7.0 and backup using rman and tivoli backup as media management layer.

    I make daily backups for a week, weekly full backups for a month, complete monthly full backups kept for one year and annual full backups kept for 7 years.

    My general retention policy is 30 days:

    RMAN > show all.

    using the control file of the target instead of recovery catalog database
    RMAN settings for database with db_unique_name PRODPRIM are:
    CONFIGURE RETENTION POLICY to the WINDOW of RECOVERY OF 30 DAYS; *
    CONFIGURE BACKUP OPTIMIZATION
    SET UP DEFAULT DISK DEVICE TYPE;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 8 TYPE OF BACKUP TO COMPRESSED BACKUPSET;
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1;
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE MAXSETSIZE TO UNLIMITED;
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE COMPRESSION ALGORITHM 'BZIP2 '; # by default
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / oracle/PROD/db/tech_st/11.1.0/dbs/snapcf_PROD_PRIM.f';


    The daily backup script is as below:

    RMAN > print script prod_daily;

    printing stored script: prod_daily
    +{+
    allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_usrFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.usr) ';
    allocate channel t2 type 'sbt_tape' parms 'ENV=(TDPO_usrFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.usr) ';
    allocate channel t3 type 'sbt_tape' parms 'ENV=(TDPO_usrFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.usr) ';
    format "prod_dailybackup_ % d_ % s_ %t" Dungeon of the database backup to the time = ' sysdate 7' newspapers. +
    backup format 'prodarchbackup_ % d_ % s_ %t' archivelog all not saved 1 time;
    cross-checking of backup;
    overlap archivelog all;
    delete noprompt obsolete;
    delete expired backup noprompt.
    delete noprompt expired archivelog all;
    outline report;
    output channel t1;
    output channel t2;
    output channel t3;
    +}+

    This line: backup format + database "prod_dailybackup_ % d_ % s_ %t" keep until time = 'sysdate-7'-newspapers; I don't expect the archivelogs compulsory to recover from that backup backups will be kept and will expire when this backup expires.

    But when I list backup of archivelogs, I find archivelogs backups that were taken as early as next January, and the archivelog backups never get deleted or obsolete:

    RMAN >

    List of backup sets
    +===================+


    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    + 9485 M 326.00 SBT_TAPE 00:00:10: 28 - JAN-11 +.
    BP key: 9758 situation: AVAILABLE Tablet: NO Tag: TAG20110128T201149
    Handle: prodarchbackup_PROD_927_741643910 Media:

    List of newspapers archived in defined backup 9485
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    4266 + 1 220134037 28 JANUARY 11 220161176 28 - JAN-11 +.
    + 1 4267 220161176 28 JANUARY 11 220184892 28 - JAN-11 +.
    4268 + 1 220184892 28 JANUARY 11 220218518 28 - JAN-11 +.
    + 1 4269 220218518 28 JANUARY 11 220230438 28 - JAN-11 +.
    + 1 4270 220230438 28 JANUARY 11 220273374 28 - JAN-11 +.
    4271 + 1 220273374 28 JANUARY 11 220278622 28 - JAN-11 +.
    4272 + 1 220278622 28 JANUARY 11 220282989 28 - JAN-11 +.
    4273 + 1 220282989 28 JANUARY 11 220285629 28 - JAN-11 +.
    + 1 4274 220285629 28 JANUARY 11 220287861 28 - JAN-11 +.
    + 1 4275 220287861 28 JANUARY 11 220290432 28 - JAN-11 +.
    4276 + 1 220290432 28 JANUARY 11 220293038 28 - JAN-11 +.
    + 1 4277 220293038 28 JANUARY 11 220295570 28 - JAN-11 +.
    4278 + 1 220295570 28 JANUARY 11 220302972 28 - JAN-11 +.

    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    + 9486 435,25 M SBT_TAPE 00:00:13: 28 - JAN-11 +.
    BP key: 9759 situation: AVAILABLE Tablet: NO Tag: TAG20110128T201149
    Handle: prodarchbackup_PROD_925_741643910 Media:

    List of newspapers archived in defined backup 9486
    The next time that THRD Seq YVERT low low time next YVERT
    + 'archivelog.log' [read-only] 11993 lines, characters 647140 +.


    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    + 9486 435,25 M SBT_TAPE 00:00:13: 28 - JAN-11 +.
    BP key: 9759 situation: AVAILABLE Tablet: NO Tag: TAG20110128T201149
    Handle: prodarchbackup_PROD_925_741643910 Media:

    List of newspapers archived in defined backup 9486
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    + 1 4254 219859033 28 JANUARY 11 219894422 28 - JAN-11 +.
    + 1 4255 219894422 28 JANUARY 11 219919680 28 - JAN-11 +.
    + 1 4256 219919680 28 JANUARY 11 219942950 28 - JAN-11 +.
    4257 + 1 219942950 28 JANUARY 11 219967656 28 - JAN-11 +.
    4258 + 1 219967656 28 JANUARY 11 219976051 28 - JAN-11 +.
    4259 + 1 219976051 28 JANUARY 11 219987397 28 - JAN-11 +.
    + 1 4260 219987397 28 JANUARY 11 220006347 28 - JAN-11 +.
    + 1 4261 220006347 28 JANUARY 11 220025985 28 - JAN-11 +.
    4262 + 1 220025985 28 JANUARY 11 220047061 28 - JAN-11 +.
    4263 + 1 220047061 28 JANUARY 11 220074802 28 - JAN-11 +.
    + 1 4264 220074802 28 JANUARY 11 220102835 28 - JAN-11 +.
    + 1 4265 220102835 28 JANUARY 11 220134037 28 - JAN-11 +.

    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    + 9487 427,25 SBT_TAPE 00:00:14 M 28 - JAN-11 +.
    BP key: 9760 situation: AVAILABLE Tablet: NO Tag: TAG20110128T201149
    Handle: prodarchbackup_PROD_926_741643910 Media:

    List of newspapers archived in defined backup 9487
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    + 1 4231 218972478 28 JANUARY 11 218974637 28 - JAN-11 +.
    + 1 4232 218974637 28 JANUARY 11 218976683 28 - JAN-11 +.
    + 1 4233 218976683 28 JANUARY 11 218979456 28 - JAN-11 +.
    4234 + 1 218979456 28 JANUARY 11 218981788 28 - JAN-11 +.
    + 1 4235 218981788 28 JANUARY 11 218984100 28 - JAN-11 +.
    4236 + 1 218984100 28 JANUARY 11 218986873 28 - JAN-11 +.
    + 1 4237 218986873 28 JANUARY 11 218990404 28 - JAN-11 +.
    + 1 4238 218990404 28 JANUARY 11 218993848 28 - JAN-11 +.
    + 1 4239 218993848 28 JANUARY 11 218998167 28 - JAN-11 +.
    ---------------------------------------------------------------------------------------------


    My question is, when these archivelog backups become obsolete and are deleted?

    Dula

    Published by: user13005731 on May 19, 2011 10:10

    Published by: user13005731 on May 19, 2011 10:11

    10.2, you have to specify NEWSPAPERS.

    10.2 documentation:
    http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14194/rcmsynta035.htm#sthref554

    However, 11.1 and above, it is NOT necessary and, I would say, must not be specified.
    11.1 documentation:
    http://download.Oracle.com/docs/CD/B28359_01/backup.111/b28273/rcmsubcl011.htm#i97063
    «+ An archive backup is autonomous because is contains all the files needed to restore the backup and recover in a consistent state.» "If the database is open during backup, then RMAN automatically generates and saves them archived redo logs necessary for the protection of the compatible database.

    and
    http://download.Oracle.com/docs/CD/B28359_01/backup.111/b28270/wnbradv.htm#sthref6
    "+ Long term + improved backup management.
    + You can create a backup archiving or long-term with the BACKUP... "KEEP that keeps only the required log files archived to make consistent backup.

    and
    http://download.Oracle.com/docs/CD/B28359_01/backup.111/b28270/rcmbckba.htm#CHDHAFHJ
    "+ When you specify the DUNGEON on the BACKUP command, RMAN generates multiple backup sets. ...... It automatically generates a recovery archived log backup to ensure that the backup of the database can be recovered to a consistent state. »

    You could log a SR with support of Oracle to confirm if you need the key word "LOGS" in the BACKUP... KEEP and to identify the behavior if you happen to keep this in your backup command.

    In my humble OPINION, not be specify the LOGS of the BACKUP... KEEP.
    You could test this in a test environment by doing a BACKUP... MAINTAIN a database that has a very small WINDOW of RETENTION.

    Hemant K Collette
    http://hemantoracledba.blogspot.com

    Published by: Hemant K grapple on May 20, 2011 15:21
    Quotations in italics of the documentation.

  • During the backup archivelog backups online

    Hello

    Oracle 11.2.0.4

    Linux SLES 11 SP2


    During our backup window, some batches are executed generate an amount of redo. Completion of our hot backup, it backs up all records generated and removes all the. We are afraid to fill our archivelog files before the end of hot backup. It's going to be any problem if I back up and delete the archivelogs during the backup hot (using a different RMAN command)?  For the moment, we are unable to add space for the file archive system.


    These are the rman commands executed:


    Hot backup


        RUN{
                ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch02 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch03 TYPE 'SBT_TAPE';
                SEND 'NB_ORA_SERV=$NB_ORA_SERV,NB_ORA_CLIENT=$NB_ORA_CLIENT,NB_ORA_POLICY=$NB_ORA_POLICY';
                BACKUP
                       $BACKUP_TYPE
                       SKIP INACCESSIBLE
                       TAG $BTAG$(date +"%Y%m%d%H%M%S")
                       FILESPERSET 1
                       FORMAT 'bk_%U_%t'
                       DATABASE;
                sql 'alter system archive log current';
                RELEASE CHANNEL ch00;
                RELEASE CHANNEL ch01;
                RELEASE CHANNEL ch02;
                RELEASE CHANNEL ch03;
                # backup all archive logs
                ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
                BACKUP
                        filesperset 20
                        TAG $BTAGAR$(date +"%Y%m%d%H%M%S")
                        FORMAT 'al_%s_%p_%t'
                        ARCHIVELOG ALL DELETE INPUT;
                RELEASE CHANNEL ch00;
                RELEASE CHANNEL ch01;
        }


    Archives


          RUN{
                # backup all archive logs
                ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch02 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch03 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch04 TYPE 'SBT_TAPE';
                SEND 'NB_ORA_SERV=$NB_ORA_SERV,NB_ORA_CLIENT=$NB_ORA_CLIENT,NB_ORA_POLICY=$NB_ORA_POLICY';
                BACKUP
                        filesperset 10
                        TAG $BTAGAR$(date +"%Y%m%d%H%M%S")
                        FORMAT 'al_%s_%p_%t'
                        ARCHIVELOG ALL DELETE INPUT;
                RELEASE CHANNEL ch00;
                RELEASE CHANNEL ch01;
                RELEASE CHANNEL ch02;
                RELEASE CHANNEL ch03;
                RELEASE CHANNEL ch04;
        }


    Thank you for your time.

    Kind regards

    Ferran

    If you delete the archivelogs that have not been funded until you lose the ability to recover your database using incremental backups hot. When you make a hot backup, you'll need archivelogs to recover data files to recover the database in a consistent state. As long as you have archivelogs in any backupset should not be a problem. Archivelogs are always in their own backupset. You can use additional settings when you perform the backup of the archivelogs, such as 'no saved' or 'skip inaccessible', in order to avoid the mistakes of rman backup.

  • How to plan the backup archivelog in EM12c for a group

    I am aware that I can schedule a backup of archivelog to a single database, but it is recommended, or indeed only just backs up multiple databases is to consolidate upward under a group and then schedule a backup for that group.

    However, I think that Oracle can be left aside the backup archivelog to a group option. All that I can find a full or incremental backup option. Anyone know if it is possible to backup archivelog planned for a group?

    In addition, on a somewhat independent question;

    If I put in place a system of backup of 1st day of the month and incr full backup for the rest of the month and I have a retention time of 14 days, food will be possible after 15 days?

    You can schedule the backup archivelog as well as the full backup, there is a checkbox to do this, if it is enough for you. If you want to schedule a backup archivelog only you have the ability to create a multitasking job, with one step for each instance: Set rman environment and launch with the controls. That's the way I do my backups one after the other. But of course it is static, you must hardcode the instances in the work. There is no option to make backups only archivelog through em12c, at least not through the GUI.

    Regarding your backup problem:

    The recovery window tells rman to consider as possible, obsolete backups after 14 days. He still however will check that they are really obsolete. Your only full backup will become obsolete until you make a new. However, the incremental backup may become obsolete and deleted. RMAN was able to retrieve the instance with the full backup and the archivelogs, so the oldest incremental backup should be obsolete.

    You can ask rman which files are obsolete and explicitly specify the recovery window:

    RMAN > window recovery obsolete report 15 days;

    Concerning

    Thomas

  • Conflict with the L1 backup task backup ARCHIVELOG

    DB version: 11.2.0.4

    Platform: RHEL 6.3

    We have a backup archivelog that starts at 22:00 and an incremental backup that starts at 23:50.

    The backup archivelog usually ends at 23:00. But lately, he took more time. Sometimes, he finished only at 12:30, which is like 40minutes after the incremental backup is started. That is, backup Archivelog overlaps with the incremental backup.

    One of our colleagues has proposed adding 'FILESPERSET 1' to speed up the backup archivelog. So he changed the backup archivelog script of

    BACKUP FORMAT '% s_ %%t p_ manhArc_' ARCHIVELOG ALL DELETE all THE ENTRY;

    TO

    BACKUP FILESPERSET 1 FORMAT '% s_ %%t p_ manhArc_' ARCHIVELOG ALL DELETE all THE ENTRY;

    He gave the reason was that "this will prevent channels stuck with the unreachable archivelogs.

    Question1. Adds 'FILESPERSET 1' really useful in this scenario?

    Question2. 'FILESPERSET 1' in the archivelog script means 1 for each archivelog backup piece. Right? This means that a lot of backup in the backup media.

    The justification is not applicable.

    FILESPERSET 1 would not help you here.

    Each consisting of 1 ArchiveLog BackupSet would result in a very large number of BackupSets.  Your controlfile would have to create a lot more locations for BackupSets.

    Hemant K Collette

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

    Version: 11.2.0.3
    Platform: RHEL 6.2

    How can I backup archivelog generated in the last 5 minutes? Here's what I've tried so far?

    RMAN > archivelog backup all the format ' / rman_backups/Nov21Bkp/archiveTest_%U' until TIME ' sysdate-5/1440 ';

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-00558: error occurred during parsing of order entry
    RMAN-01009: syntax error: found ' until the ': expected an of: ' archivelog, auxiliary, backupset channel, backup, controlfilecopy, copy, current, data bases, datafilecopy, datafile, db_recovery_file_dest, delete, diskratio, filesperset, force, format, include, keep, maxsetsize, noexclude, nokeep, not more, pool, recovery, reuse, section, jump, skip readonly, spfile, tablespace, tag, to, comma, (,»
    RMAN-01007: line 1 column 81 file: entry standard

    RMAN > archivelog backup everything until THE format ' sysdate-5/1440 ' HOUR ' / rman_backups/Nov21Bkp/archiveTest_%U';

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-00558: error occurred during parsing of order entry
    RMAN-01009: syntax error: found ' until the ': expected an of: ' archivelog, auxiliary, backupset channel, backup, controlfilecopy, copy, current, data bases, datafilecopy, datafile, db_recovery_file_dest, delete, diskratio, filesperset, force, format, include, keep, maxsetsize, noexclude, nokeep, not more, pool, recovery, reuse, section, jump, skip readonly, spfile, tablespace, tag, to, (,»
    RMAN-01007: line 1 column 23 file: entry standard

    You cannot specify both 'ALL' and ' FROM/UNTIL TIME '.

    Also if you want the archivelogs generated in the last 5 minutes, you should use TIME.

    If you want the archivelogs generated until 5 minutes ago (and not the last archivelogs), you should use up to the HOUR.

    Hemant K Collette

  • Should we backup Archivelogs special cold backups?

    B version: 11.2
    Version of the operating system: Solaris 5.10

    Here's the script that we use for ad-hoc cold backups. Is it necessary to take the backup of the archivelogs when we do the backup to cold?
    Size of the backup archivelog room is sometimes greater than the backup piece containing the full backup of the comic itself! Then lost too much disk space.

    The script that we use
    run
{
allocate channel t1 type disk;
sql 'alter system archive log current';
shutdown immediate;
startup mount;
backup  full database format='/mypath/ORCL_full_%U_%T.bkp' tag='ORCL_full';
backup archivelog all tag='arch_bkp' format='/mypath/ORCL_BKP/arch_%U_%T.bkp' delete input;
release channel t1;
}

    Hello;

    A cold backup is a consistent state. If you do not have to save them. No new archived logs generated during the backup or if you're still OK.

    For other types of RMAN backup, you STILL want it. This ensures that backups of data taken when the command file is recoverable in a consistent state.

    Best regards

    mseberg

  • back up and delete the archivelogs on primary

    Hello

    I have a primary db (11.2) and physical standby

    I understand that I must save archive logs on primary once a while in case the newspapers does not get delivered on time and I have loss the primary db, including newspapers, which couldn't have been shipped...! It's okay?

    I want to configure rman to run twice a day, but my concern is that I don't want rman to delete the archivelogs (remove entry), unless they have been shipped an app in standby mode. How can I configure rman then it deletes only if newspapers is applied in sleep mode?


    Thank you

    RMAN set it to primary DB:

    RMAN > CONFIGURE ARCHIVELOG DELETION POLICY APPLIED TO ALL STANDBY;

    Follow this forum discussion.hope this helps.

    Ark of physical backup Delete Watch

  • backup archivelog problem

    Hello
    I'm working on my PC. I deleted by mistake some archiving logs. Now when I take backup of archive logs it shows error of missing log archiving.

    RMAN > backup archivelog all;

    From backup 2 November 10
    Current archived log
    using channel ORA_DISK_1
    using the ORA_DISK_2 channel
    using the ORA_DISK_3 channel
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the backup command to the 02/11/2010 21:37:10
    RMAN-06059: journal archived expected not found, lost of archived newspaper compromised recoverability
    ORA-19625: error identification of file /oracle/10.2.0/dbs/arch1_26_733325987.dbf
    ORA-27037: unable to get file status
    Linux error: 2: no such file or directory
    Additional information: 3

    Help, please

    Ashutosh

    It should remove according to retention, when the backup items has not erased you can use tag also

    OK, you can close the thread as answered...

  • RMan is missing some files when deleting obsolete archivelogs

    Hi all

    in one of our databases 9iR2, I noticed a rather strange behavior of the RMan delete obsolete archivelogs. The RMan script has the "OBSOLETE RECOVERY WINDOW DELETE 7 DAYS DEVICE TYPE DISK"-command. If RMan deletes the archivelogs regularly. But unfortunately, in every race, it leaves 3 files cancelled. The log file is (only relevant lines):

    Remove the following obsolete backups and copies:
    Making key time filename/handle type
    ---- ----
    Archive 24779 08 - SEVEN journal.-10 /oralogs/oraArchive/VG41MED/VG41MED_12402.ora
    Archive Log 24780 08-SEVEN.-10 /oralogs/oraArchive/VG41MED/VG41MED_12403.ora
    ...
    Archive 24785 08 - SEVEN journal.-10 /oralogs/oraArchive/VG41MED/VG41MED_12408.ora

    on the next race (the next day) the log file says:

    Remove the following obsolete backups and copies:
    Making key time filename/handle type
    ---- ----
    Archive Log 24799 09-SEPT.-10 /oralogs/oraArchive/VG41MED/VG41MED_12412.ora
    Archive 24800 09 - SEVEN journal.-10 /oralogs/oraArchive/VG41MED/VG41MED_12413.ora
    ...
    Archive Log 24805 09-SEPT.-10 /oralogs/oraArchive/VG41MED/VG41MED_12418.ora

    As you can see, RMan lack VG41MED12409.ora log file, VG41MED12410.ora, and VG41MED_12411.ora that are available before and after the backup procedure. We treat archivelogs on operating system level. A "overlap archivelog all ' - command does not list these 3 files, if the database thinks that they are removed - which is not really true. This odd pattern is repeated every day, so my archivelog directory is growing everyday with the 3 files not deleted.

    This behavior appears still more strange, because the RMan backup script even run on 3 other databases with same structure does not show this "error". I checked the configuration of 4 databases and not detected no difference.

    Maybe it's a corrupt controlfile (we do not catalog-db). Someone has any idea how to solve this problem?

    Thank you
    Friedhelm

    Edited by: user8964905 the 20.09.2010 00:18

    Hello
    (1) I think the command of OVERLAP is the only way to know what archivelogs are always specific to the database (expired or available) kn.
    (2) thank you for your explanations. You're right - the order REPORT OBSOLETE list backups, but my problem are the obsolete archivelogs of backups. If my humble opinion REPORT OBSOLETE wouldn't help.

    In fact no and no :).

    (1) a simple

    list archivelog all;

    lists the known archivelog (expired or available) files.

    crosscheck archivelog all;

    will check if the information on their availability is still topical, but it will not help you in this case (they exist!)

    2.

    report obsolete recovery...;

    http://download.Oracle.com/docs/CD/B10501_01/server.920/a96566/rcmconc3.htm#463220
    Order REPORT displays OBSOLETE backups and copies of data files, control files, and archived redo logs that can be deleted because they are no longer needed.
    ...
    OK, but if you read a little more of the documentation:
    ...
    In addition to backups of file obsolete data, RMAN reports obsolete archived newspapers and archived backups of logs. When backups of files of data from one point in time are obsolete, then archived logs that can apply to these data files are also is no longer necessary and become obsolete according to the specified retention policy.

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

    I have increased the CONTROLFILE_RECORD_KEEP_TIME now and watch the results next night. Perhaps the reason for this behavior is the fact that this database is very small compared to other databases, which do not show the effect.
    I'll post the result of this strategy, here the next few days.
    Wait & see

    Best regards
    Phil

  • Time Machine: deleted backups of the status "pending".

    Hello world

    I manually deleted some old backups Time Machine interface, by clicking on the gear button in the backup Finder and selecting Remove backup.

    Now deleted backups are no more hard disk or in the trash, but they are always present in the Time Machine interface in a "pending" status and it is not possible any action on them.

    How can I remove them completely from Time Machine?

    Thanks in advance for any suggestion,

    Good bye

    Gabriele

    Manual removal of the old backups is not a good thing to do. Let Time Machine take care of itself.

    I suggest you use Spotlight to reindex your hard disk and backup disk, then run a backup Time Machine and see what clears the problem. If this isn't the case, you might be better off erase your backup disk and start a new Time Machine backup.

    Spotlight - re - index

  • any backup archivelog

    Hello

    What is the difference between all the backup archivelog and archivelog backup with rman.

    You cannot issue a "BACKUP ARCHIVELOG' by itself. The syntax of 'archivelogRecordSpecifier' requires a specification for which ArchiveLogs supported upwards - for example 'ALL' or "until...". ' or 'FROM... '. "etc.

    The only time that you do not have to specify the ArchiveLogs is when you use the 'PLUS ARCHIVELOG' to a 'BACKUP DATA base'

    Hemant K Collette

  • RMAN to DELETE backups?

    How to use RMAN to DELETE backups that I don't want anymore?
    at the same time all the

    Hello...

    Are you sure you want to delete all backups?

    If you want to delete all records then: -.

    RMAN > delete backup.

    Anand

  • It is safe to delete the archivelogs FRA?

    Hello

    I'm running an Oracle 12 c database and running a backup script every week:

    RMAN > BACKUP of DATA PLUS ARCHIVELOG;

    The archivelog should therefore be connected, no? Today I got an ora-00257. The current solution is to resize the area of 6 GB to 20 GB backup. But I guess it will grow only if I do not say on the subject.

    So I searched this forum and the web to find an adequate solution. I found a thread that recommends the race

    RMAN > overlap archivelog all;

    RMAN > delete all. expired archivelog

    I didn't run it without being sure of what will be removed. So I ran the overlap and the suite:

    RMAN > list expired archivelog all;

    It does not work... After some research, I discovered that the archivelog must be safeguarded in accordance with the retention policy that is currently on the default 1. Since there are already 3 full backups, why are there no expired archivelogs?

    How to remove the log file archive that they suggest to remove some files archive and run the overlap, but is this safe to do? I mean, they must be saved, because I used the command backup so archivelog, right?

    I'm open to suggestions. (I thought affecting conservation status 1 week should be good, but maybe you guys have better solutions).

    You mixed outdated and obsolete.

    Please check the discussion Re: what is the difference between the obsolete backups RMAN expried vs?

  • I can't able to take backup archivelog

    Hello

    I can't able to archivelog backup.how can take backup.yesterday I took the backup of archivelog by the same command.

    RMAN > run
    2 > {}
    3 > backup as compressed backupset
    4 > device type disk
    5 > tag "daily_archivelog".
    6 > format ' / sw/daily_archivelog_%d_t%t_c%c_s%s_p%p'
    7 > archivelog from time ' SYSDATE-2';
    {8 >}

    From backup February 14, 11
    Current archived log
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid = 112 devtype = DISK
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the backup command to 14/02/2011 11:51:22
    RMAN-06059: journal archived expected not found, lost compromise journal archived re
    Coverability
    ORA-19625: error identification of file /u02/proddata/ARCH/1_310_742566836.dbf
    ORA-27037: unable to get file status
    IBM AIX RISC System/6000 error: 2: no such file or directory
    Additional information: 3

    Amal wrote:
    Hello

    I can't able to archivelog backup.how can take backup.yesterday I took the backup of archivelog by the same command.

    RMAN > run
    2 > {}
    3 > backup as compressed backupset
    4 > device type disk
    5 > tag "daily_archivelog".
    6 > format ' / sw/daily_archivelog_%d_t%t_c%c_s%s_p%p'
    7 > archivelog from time ' SYSDATE-2';
    {8 >}

    From backup February 14, 11
    Current archived log
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid = 112 devtype = DISK
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the backup command to 14/02/2011 11:51:22
    RMAN-06059: journal archived expected not found, lost compromise journal archived re
    Coverability
    ORA-19625: error identification of file /u02/proddata/ARCH/1_310_742566836.dbf
    ORA-27037: unable to get file status
    IBM AIX RISC System/6000 error: 2: no such file or directory
    Additional information: 3

    Run the following commands, and then try the backup again:

    RMAN> CROSSCHECK ARCHIVELOG ALL;
RMAN> DELETE OBSOLETE

    Kamran Agayev a.
    Oracle ACE
    - - - - - - - - - - - - - - - - - - - - -
    My video tutorials of Oracle - http://kamranagayev.wordpress.com/oracle-video-tutorials/

Maybe you are looking for