Backup with delete input

Hi
I use the command below :
backup database plus archivelog delete input,
Works fine.
I just want to know why the directory of archivelog file (like 2007_09_13) stay there empty.
Is there a way to delete it as the archivelog ?
Thanks.

When you use DELETE INPUT while taking the backup of archivelogs then it takes the backup of archivelogs and delete them from their original location.
But it doesn't delete the folder, you can delete it if you want to, there is no harm in doing this just make sure the folder is empty and I dont think there is any way to delete those empty folders through RMAN.
Daljit Singh
Message was edited by:
Daljit

Similar Messages

  • Rman error when i am doing backup archivelog delete input

    archive log filename=+FRA01/osondemand/archivelog/2012_02_27/thread_2_seq_15028.7182.776323223 recid=122876 stamp=77
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_2 channel at 02/27/2012 05:23:14
    RMAN-10015: error compiling PL/SQL program
    RMAN-10033: error during compilation of job step 3: ORA-00603: ORACLE server session terminated by fatal error
    ORA-04030: out of process memory when trying to allocate 272 bytes (PL/SQL DIANA,PTG: No
    10.2.04
    windows
    two node rac
    please help me with above error
    thanks for help

    Hi;
    Duplicate post:
    rman error when taking backup archivelog all delete input
    Please close your othere thread as answered and keep updating your other thread here
    Regard
    Helios

  • Rman error when taking backup archivelog all delete input

    archive log filename=+FRA01/osondemand/archivelog/2012_02_27/thread_2_seq_15028.7182.776323223 recid=122876 stamp=77
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_2 channel at 02/27/2012 05:23:14
    RMAN-10015: error compiling PL/SQL program
    RMAN-10033: error during compilation of job step 3: ORA-00603: ORACLE server session terminated by fatal error
    ORA-04030: out of process memory when trying to allocate 272 bytes (PL/SQL DIANA,PTG: No
    10.2.04
    windows
    two node rac
    please help me with above error
    thanks for help

    Hi;
    Duplicate post
    Re: rman error when i am doing backup archivelog delete input
    Regard
    Helios

  • Full backup with archivelogs

    I tried to do an incremental level 0 backup with archivelogs, it failed with the error messages said that can not recognize file C:\ARCHIVE\ORCL\4_1_684433700.ARC, the error code was ORA-19625. So I added "crosscheck archivelog all;" to the backup script and Redo it.
    This time it succeeded, but there is still something I'm confused. I set up two folders to store the archivelogs, during the process, the archivelogs in the folders were not deleted synchronously,for example arhivelog a was deleted from one folder while the same file in the other folder was remained. Below is my backup script
    RUN {
    ALLOCATE CHANNEL ch00 TYPE DISK;
    ALLOCATE CHANNEL ch01 TYPE DISK;
    BACKUP
              incremental level 0
    SKIP INACCESSIBLE
    TAG hot_db_bk_level0
    FILESPERSET 5
    # recommended format
    FORMAT '\\dell090121\rman_hotbackup\bk_full_%s_%p_%t'
    DATABASE;
    sql 'alter system archive log current';
    RELEASE CHANNEL ch00;
    RELEASE CHANNEL ch01;
    # backup all archive logs
    ALLOCATE CHANNEL ch00 TYPE DISK;
    ALLOCATE CHANNEL ch01 TYPE DISK;
    BACKUP
    filesperset 20
    FORMAT '\\dell090121\rman_hotbackup\al_%s_%p_%t'
    ARCHIVELOG ALL DELETE INPUT;
    RELEASE CHANNEL ch00;
    RELEASE CHANNEL ch01;
    # Note: During the process of backing up the database, RMAN also backs up the
    # control file. This version of the control file does not contain the
    # information about the current backup because "nocatalog" has been specified.
    # To include the information about the current backup, the control file should
    # be backed up as the last step of the RMAN section. This step would not be
    # necessary if we were using a recovery catalog.
    ALLOCATE CHANNEL ch00 TYPE DISK;
    BACKUP
    # recommended format
    FORMAT '\\dell090121\rman_hotbackup\cntrl_%s_%p_%t'
    CURRENT CONTROLFILE;
    RELEASE CHANNEL ch00;
    }

    Even if you have two (or more) archivelog destination directories, the "DELETE INPUT" clause in "BACKUP ARCHIVELOG ..." would delete only archivelogs which it reads for the backup. Thus, because the backup could read from dest_1 (for instance), it would archivelogs from dest_1 but not from dest_2. The Backup is free to backup files at either dest location and delete only what it has backed up, by default with "DELETE INPUT".
    However if you specify DELETE ALL INPUT, then Oracle deletes all copies of the ArchiveLogs.
    Thus your backup command would be
    BACKUP ARCHIVELOG ALL DELETE ALL INPUT;where the first "ALL" is "all archived log sequences available, but only 1 copy of each" while the second "ALL" is "all copies of each archived log backed up by the BACKUP"

  • RMAN backup archivelog all delete input

    Hello DBAs,
    what does this command will do?
    RMAN> backup archivelog all delete input;
    DN

    I have set cron job for RMAN> backup archivelog all delete input; and its work.
    But I got following message in my log file.
    Please give ur feed back.
    Recovery Manager: Release 10.1.0.4.0 - 64bit Production
    Copyright (c) 1995, 2004, Oracle. All rights reserved.
    RMAN>
    connected to target database: SIDNAME (DBID=XXXXXXXX)
    using target database controlfile instead of recovery catalog
    RMAN>
    Starting backup at 10-FEB-06
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=269 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=268 devtype=DISK
    channel ORA_DISK_1: starting compressed archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=5701 recid=2412 stamp=581958928
    input archive log thread=1 sequence=5702 recid=2413 stamp=581961105
    input archive log thread=1 sequence=5703 recid=2414 stamp=581964532
    input archive log thread=1 sequence=5704 recid=2415 stamp=582025325
    input archive log thread=1 sequence=5705 recid=2416 stamp=582029976
    input archive log thread=1 sequence=5706 recid=2417 stamp=582031922
    channel ORA_DISK_1: starting piece 1 at 10-FEB-06
    channel ORA_DISK_2: starting compressed archive log backupset
    channel ORA_DISK_2: specifying archive log(s) in backup set
    input archive log thread=1 sequence=5707 recid=2418 stamp=582037207
    input archive log thread=1 sequence=5708 recid=2419 stamp=582038471
    input archive log thread=1 sequence=5709 recid=2420 stamp=582043538
    input archive log thread=1 sequence=5710 recid=2421 stamp=582048518
    input archive log thread=1 sequence=5711 recid=2422 stamp=582055205
    channel ORA_DISK_2: starting piece 1 at 10-FEB-06
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/10/2006 18:00:
    12
    ORA-19502: write error on file "/u02/backup/backup_6ehb2t97_1_1", blockno 6145 (
    blocksize=512)
    ORA-27063: number of bytes read/written is incorrect
    IBM AIX RISC System/6000 Error: 28: No space left on device
    Additional information: -1
    Additional information: 1048576
    channel ORA_DISK_1 disabled, job failed on it will be run on another channel
    RMAN-03009: failure of backup command on ORA_DISK_2 channel at 02/10/2006 18:00:
    12
    ORA-19502: write error on file "/u02/backup/6fhb2t97_1_1", blockno 6145
    (blocksize=512)
    ORA-27063: number of bytes read/written is incorrect
    IBM AIX RISC System/6000 Error: 28: No space left on device
    Additional information: -1
    Additional information: 1048576
    channel ORA_DISK_2 disabled, job failed on it will be run on another channel
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/10/2006 18:00:
    12
    ORA-19502: write error on file "/u02/backup/backup_6ehb2t97_1_1", blockno 6145 (
    blocksize=512)
    ORA-27063: number of bytes read/written is incorrect
    IBM AIX RISC System/6000 Error: 28: No space left on device
    Additional information: -1
    Additional information: 1048576
    RMAN>
    Recovery Manager complete.
    DN

  • Can I delete old backups from other devices if my new iphone 6 has a current backup with everything on my new phone?

    Can I delete old backups from other devices if my new iphone 6 has a current backup with everything on my new phone?

    Hi there dyarrell,
    You can do this if you are confident that your current device has all of the data on it that you want to keep. The method for deleting the backup will be differnt depending on the backup method. Take a look at the articles below for more information. 
    Create and delete iPhone, iPad, and iPod touch backups in iTunes
    iCloud: Remove an iOS device backup from iCloud
    -Griff W. 

  • Hello, I have an ipad mini and I have made ​​a backup with iCloud, I deleted a game and now I would like to get my game progress, Can you recover? How?

    Hello, I have an ipad mini and I have made ​​a backup with iCloud, I deleted a game and now I would like to get my game progress, Can you recover? How?

    You would have to restore your entire backup to recover your game progress.

  • Backup with retention policy to recovery window of N days

    Hello,
    I've issued command to create database incremental backup with configuration:
    run
      configure retention policy to recovery window of 14 days;
      backup incremental level 1 cumulative
        tag daily_incr_14_days
        database
      plus archivelog delete all input;
    All parameters are set to their default values and database backups goes to FRA. I've got recovery catalog connected and all RC_ views at my disposal.
    1) Is there any way to find out, what recovery window was used for backup from any command in rman or query from RC_ views or local database views (information from control file)?
    2) If I use other recovery window setting with configure command what would rman crosscheck or report commands do?
    BR
    Patrycjusz.

    TenakaKhan wrote:
    Mahir,
    thanks for answer - this means that recovery window should be used mainly for maintenance purposes (crosscheck, delete obsolete, report need backup etc.) and it's not related to actual retention period with backup pieces like 'keep until' clause for backup ... database command (this information are saved with backup as I could check in rc_backup_set view from recovery catalog)?
    Yes it is.
    Maintaining RMAN Backups and Repository Records
    keepOption
    backup retention policy
    A user-defined policy for determining how long backups and archived logs must be retained for media recovery. You can define a retention policy in terms of backup redundancy or a recovery window.
    RMAN retains the data file backups required to satisfy the current retention policy, and any archived redo logs required for complete recovery of those data file backups.
    recovery window
    A recovery window is one type of RMAN backup retention policy, in which the DBA specifies a period of time and RMAN ensures retention of backups and archived redo logs required for point-in-time recovery to any time during the recovery window.
    The interval always ends with the current time and extends back in time for the number of days specified by the user. For example, if the retention policy is set for a recovery window of seven days, and the current time is 11:00 AM on Tuesday,
    RMAN retains the backups required to allow point-in-time recovery back to 11:00 AM on the previous Tuesday.
    Regards
    Mahir M. Quluzade

  • RMAN backup with smallest backup size

    Oralce 11g2 on Redhat 5. The diskspace is our tightest resource, and we want to an incremental backup with level0 on Sunday and level 1 every week days and Saturday. I am to use the comamnds to do the job--Sunday
    backup incremental level 0 tag 'level_0' database plus archivelog;
    --Other days
    backup incremental level 1 database plus archivelog delete all input;I do not think this is the best practice nor produce smallest backup files.
    What are you comments and opinions. Thanks

    Pavan, Thank you for reply. Here are the info requested
    what is size of DB ??
    ~250GB, including UNDO and TEMP. It is a dev database and not very big. But we have total 800GB disk space. After setting some housekeeoing folders, and allow some space for data growth, it leaves 180GB for flash_recovery_area.
    what would be max size of archive logs generated per day ??
    Variable from less than 1 GB to 12 GB
    Are you taking backups to tape or Disk ??
    Disk. In the 180GB flash_recovery_area, Current backup size is 152GB. If a backup fails to delete obsolete files, the next backup will fill the flash_recovery_area.
    Provide the Rman configuration information ??
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name TDEV2 are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%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 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_1/dbs/snapcf_tdev2.f'; # default

  • Error While Doing Backup with SuperDuper

    I bought a new hard drive and was atempting to do a backup with SuperDuper and got these messages:
    WARNING: Caught I/O exception(5): Input/output error
    | 08:32:50 AM | Info | WARNING: Source: /Library/Frameworks/LAME.framework/Versions/A/LAME, lstat(): 0
    | 08:32:50 AM | Info | WARNING: Target: /Volumes/WD USB 2/Library/Frameworks/LAME.framework/Versions/A/LAME, lstat(): 0
    | 08:32:50 AM | Info | Attempting to copy file using copyfile().
    | 08:33:32 AM | Info | Attempting to copy file using ditto.
    | 08:34:08 AM | Error | ditto: /Library/Frameworks/LAME.framework/Versions/A/./LAME: Input/output error
    Can anyone help me resolve this error? I used Disk Utility before SuperDuper and that backup also failed.
    Message was edited by: ImaVeggie

    I was trying to create a bootable backup to an external USB drive prior to installing my new internal hard drive. I simply deleted the LAME Framework folder that was giving the error and was able to complete the process. I think that had something to do with MP3 encoding, converting. Hopefully not in relation to iTunes. Anyone know?

  • Rman backup with a missing archivelog.

    hello,
    I backed my database up yesterday after you guys helped me fix few problems I had on it. I used RMAN with the following command in a run block:
    *run {*
    allocate channel t1 type disk;
    backup current controlfile ;
    backup database;
    backup archivelog all delete input;
    release channel c1;
    At the end of the operation, RMAN indicates that and archivelog is missing and it couldn't find it. As a result, recover operation can be compromised. Now am confused because I do not know whether the command executed successfully or not and how to fix the missing archivelog.
    Below is the entire output of the operation along with error message:
    canal affectÚ : t1
    canal t1 : sid=131 typedev=DISK
    DÚmarrage de backup dans 16/04/09
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    insertion du fichier de contr¶le en cours dans l'ensemble de sauvegarde
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/ncnnf0_tag20090416t211049_0.334.684
    *364257 Útiquette=TAG20090416T211049 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:00:14
    Fin de backup dans 16/04/09
    DÚmarrage de backup dans 16/04/09
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    fichier de donnÚes en entrÚe fno=00008 nom=+ASMTEST/meta4/m4prod.dbf
    fichier de donnÚes en entrÚe fno=00010 nom=H:\ORADATA\M4REC.DBF
    fichier de donnÚes en entrÚe fno=00009 nom=E:\DATAFILEMETA4\M4PROD02.DBF
    fichier de donnÚes en entrÚe fno=00001 nom=+ASMTEST/meta4/system01.dbf
    fichier de donnÚes en entrÚe fno=00003 nom=+ASMTEST/meta4/sysaux01.dbf
    fichier de donnÚes en entrÚe fno=00006 nom=C:\TEST.DBF
    fichier de donnÚes en entrÚe fno=00007 nom=+ASMTEST/meta4/meta4.dbf
    fichier de donnÚes en entrÚe fno=00005 nom=+ASMTEST/meta4/example01.dbf
    fichier de donnÚes en entrÚe fno=00002 nom=+ASMTEST/meta4/undotbs01.dbf
    fichier de donnÚes en entrÚe fno=00004 nom=+ASMTEST/meta4/users01.dbf
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/nnndf0_tag20090416t211107_0.333.684
    *364271 Útiquette=TAG20090416T211107 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:51:10
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    insertion du fichier de contr¶le en cours dans l'ensemble de sauvegarde
    inclusion du SPFILE en cours dans l'ensemble de sauvegarde
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/ncsnf0_tag20090416t211107_0.345.684
    *367351 Útiquette=TAG20090416T211107 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:00:26
    Fin de backup dans 16/04/09
    DÚmarrage de backup dans 16/04/09
    journal en cours archivÚ
    canal libÚrÚ : t1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: Úchec de la commande backup Ó 04/16/2009 22:04:03
    RMAN-06059: journal d'archivage attendu introuvable ; la perte du journal d'arch
    ivage compromet la possibilitÚ de rÚcupÚration
    ORA-19625: erreur lors de l'identification du fichier H:\ARCHIVEMETA4\ARC00001_0
    *682674928.001*
    ORA-27041: ouverture du fichier impossible
    OSD-04002: ouverture impossible du fichier
    O/S-Error: (OS 2) Le fichier spÚcifiÚ est introuvable.
    Here's my nderstanding and please correct me if am wrong:
    The first 3 instructions of the run block executed successfully, but
    the last one didn't. Is that so?
    Whatever the understanding, do I have a backup? WHat can I do to have a consistent backup?
    Thanks in advance.

    Adomi,
    It is sad to see you are still running RMAN in 8i fashion where you are on 10g.
    The script is bs, sorry
    run {
    allocate channel t1 type disk; -- not required
    backup current controlfile ; -- not required, as this is already done by backup database
    backup database;
    backup archivelog all delete input;
    release channel c1; -- not required.
    If you have controlfile autobackup on, you could just
    backup database plus archivelog
    and be done with it.
    As you didn't make a RMAN backup from the start, your backup archivelog statement should have read
    backup archivelog all skip inaccessible delete input;
    Once that succeeds Oracle shouldn't need the archivelog anymore, and you should make a second backup without the skip inaccessible clause.
    Sybrand Bakker
    Senior Oracle DBA

  • Rman backup with corrupted block

    Hello,
    Firstly - I have problem on non-production database 11.2.0.1.0, so I am not deeply worried about data. But I need to understand what happened with database backups and how to prevent such things in future.
    So - I have EM scheduled weekly full backup and daily incremental backups. Later there was problem with hardware and some corrupted blocks in database were found. The weekly backup ran without error and obsolete backups were deleted. Now it is not possible to "recover corruption list" because no backup without corruption exists (RMAN-06023: no backup or copy of datafile 6 found to restore). I am not worried about the lost data, but I need to find out how come the backup contains corrupted block.
    I have checked the data file using dbv utility
    DBVERIFY - Verification starting : FILE = /opt/oracle/oradata/orcl/users03.dbf
    DBV-00200: Block, DBA 27525766, already marked corrupt
    csc(0x0001.7b01729f) higher than block scn(0x0000.00000000)
    Page 2359942 failed with check code 6054
    DBVERIFY - Verification complete
    Total Pages Examined         : 3840000
    Total Pages Processed (Data) : 453896
    Total Pages Failing   (Data) : 1
    Total Pages Processed (Index): 2959104
    Total Pages Failing   (Index): 0
    Total Pages Processed (Other): 424025
    Total Pages Processed (Seg)  : 0
    Total Pages Failing   (Seg)  : 0
    Total Pages Empty            : 2975
    Total Pages Marked Corrupt   : 1
    Total Pages Influx           : 0
    Total Pages Encrypted        : 0
    Highest block SCN            : 2156227446 (1.2156227446)As you can see the datafile 6 - user03.dbf has errors. Also backups now contain errors.
    1) So how is it possible that the EM scheduled backup ran without problems and the backup now contains corrupted blocks. How to prevent this in future ? I know there is setting MAXCORRUPT. How can I check its current value ? How can I configure it using EM scheduled backups ?
    2) Secondly, meanwhile I studied the RMAN commands. So I have suspended EM backup jobs, and executed follwing command. And backup ran without error again. How is this possible, if data file users06.dbf has corrupted block ?
    Thanks !
    RMAN> run {
    set MAXCORRUPT for datafile 6 to 0;
    backup as compressed backupset datafile 6;
    2> 3> 4>
    executing command: SET MAX CORRUPT
    Starting backup at 07-NOV-12
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    using channel ORA_DISK_3
    using channel ORA_DISK_4
    using channel ORA_DISK_5
    channel ORA_DISK_1: starting compressed full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
    channel ORA_DISK_1: starting piece 1 at 07-NOV-12
    channel ORA_DISK_1: finished piece 1 at 07-NOV-12
    piece handle=/opt/oraBackup/rman/nrnpo0sg_1_1 tag=TAG20121107T200120 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 01:13:05
    Finished backup at 07-NOV-12
    Starting Control File and SPFILE Autobackup at 07-NOV-12
    piece handle=/opt/oraBackup/rman/c-1253245572-20121107-03 comment=NONE
    Finished Control File and SPFILE Autobackup at 07-NOV-12

    I have updated database to 11.2.0.3
    However, the problem still persists. rman backup went ok on broken file
    oracle@orcl-cluster:~> sqlplus
    SQL*Plus: Release 11.2.0.3.0 Production on Tue Nov 20 09:24:11 2012
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
    Enter user-name: system
    Enter password:
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select * from V$DATABASE_BLOCK_CORRUPTION;
         FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
             6    2359942          1                  0 FRACTURED
            25    1855622          1                  0 FRACTURED
    oracle@orcl-cluster:~> rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue Nov 20 08:04:57 2012
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ORCL (DBID=1253245572)
    RMAN> backup as compressed backupset datafile 6;
    Starting backup at 20-NOV-12
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=1596 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=1568 device type=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: SID=2357 device type=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: SID=2341 device type=DISK
    allocated channel: ORA_DISK_5
    channel ORA_DISK_5: SID=86 device type=DISK
    channel ORA_DISK_1: starting compressed full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
    channel ORA_DISK_1: starting piece 1 at 20-NOV-12
    channel ORA_DISK_1: finished piece 1 at 20-NOV-12
    piece handle=/opt/oraBackup/rman/2rnqovpp_1_1 tag=TAG20121120T080513 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 01:10:35
    Finished backup at 20-NOV-12
    Starting Control File and SPFILE Autobackup at 20-NOV-12
    piece handle=/opt/oraBackup/rman/c-1253245572-20121120-00 comment=NONE
    Finished Control File and SPFILE Autobackup at 20-NOV-12
    RMAN> backup validate datafile 6;
    Starting backup at 20-NOV-12
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    using channel ORA_DISK_3
    using channel ORA_DISK_4
    using channel ORA_DISK_5
    channel ORA_DISK_1: starting compressed full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
    channel ORA_DISK_1: backup set complete, elapsed time: 00:03:05
    List of Datafiles
    =================
    File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
    6    OK     1              2975         3840000         6489027926
      File Name: /opt/oracle/oradata/orcl/users03.dbf
      Block Type Blocks Failing Blocks Processed
      Data       0              453912
      Index      0              2959091
      Other      0              424022
    Finished backup at 20-NOV-12Edited by: kamilp on Nov 20, 2012 12:23 AM

  • Hot Backup with RMAN question.

    Hi all.
    We want to make a full backup with RMAN every night with the db up. Version 9i in archive log mode.
    My question is if with the command:
    backup database plus archivelog delete input format 'MY_FORMAT_STRING';
    will store all the files needed for the recovery in one file or I need to backup some other file or do more actions. The backup will be consistent?
    Regards.

    By using this command you are only taking the backup
    all the database files plus all the archived logs
    needed for point on recovery.
    But still you will have to take the backup of Control
    file and parameter files. Which you do by configuringi think its not
    RMAN> configure controlfile autobackup off
    2> ;
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    new RMAN configuration parameters are successfully stored
    RMAN> backup database
    2> ;
    Starting backup at 28-NOV-07
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL\ORCL\SYSTEM01.DBF
    input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL\ORCL\SYSAUX01.DBF
    input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL\ORCL\UNDOTBS01.DB
    F
    input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL\ORCL\USERS01.DBF
    input datafile fno=00005 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL\ORCL\DATA.DBF
    channel ORA_DISK_1: starting piece 1 at 28-NOV-07
    channel ORA_DISK_1: finished piece 1 at 28-NOV-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ORCL\BACKUPSET\2007_11_28\O1_MF_
    NNNDF_TAG20071128T151313_3NTHSTK9_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    including current controlfile in backupset
    including current SPFILE in backupset
    channel ORA_DISK_1: starting piece 1 at 28-NOV-07
    channel ORA_DISK_1: finished piece 1 at 28-NOV-07
    piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\ORCL\BACKUPSET\2007_11_28\O1_MF_
    NCSNF_TAG20071128T151313_3NTHV8S5_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 28-NOV-07
    RMAN>backup database backup controlfile as well spfile but its better backup control file separately after backing up the database plus archivelog cause a backup set info within control file which will not be in control file which is just backed up by backup database .
    Khurram
    null

  • Hi Friends... I'm trying to delete a back-up file on mu TC but I get the message "The operation could not be completed because the item "bands" is in use. I'd like to start the Back from scratch, could help me out with deleting the current file?

    Hi Friends...
    I’m trying to delete a back-up file on mu TC but I get the message “The operation could not be completed because the item “bands” is in use. I’d like to start the Back from scratch, could help me out with deleting the current file?

    Sorry, I am very confused. I asked the following question....
    Is this the only backup file on your Mac, or do you have other backup files and data on the Time Capsule disk?
    The answer that you gave was....
    This is the only one
    Now you are saying that....
    But I have lots of other files on Time Capsule! The back up file is only one of them.
    Can you clarify, please?

  • Backup with Data Protector is not working

    Hello,
    [US]We have an Oracle DB which is saved by HP Data Protector
    [FR]Nous avons une BDD Oracle qui est sauvegardée via HP DataProtector.
    [US]During our last backup, the Data Protector Server has crashed which has stopped the backup during the process.
    [FR]Lors de la dernière sauvegarde, le serveur de backup a planté, arrêtant de ce fait la sauvegarde en cours de la BDD Oracle.
    [US]Now, when we are trying to relaunch the backup, it doesn't work at all.
    The Data Protector agent is starting, it sends the RMAN command to the DB and then stop.
    [FR]Maintenant, lorsque nous voulons relancer la sauvegarde, elle ne fonctionne plus.
    L'agent démarre bien, il envoie bien la commande à RMAN qui démarre puis s'arrête.
    [US] Of we launch the backup manually thru RMAN, it works
    [FR]Lorsqu'on lance cette même sauvegarde manuellement via RMAN, elle fonctionne !
    [US]Lors are not really explicit !
    [FR]Les logs ne sont pas très parlant:
    LOGS of DATA PROTECTOR (in french but I've translated (in bold) which I think, is important)
    Citation:
    [Normal] De : [email protected] "Base10G_DBName_1_Archivelogs_rman_delete" Heure : 26/02/2013 12:10:31
    La session de sauvegarde 2013/02/26-31 a démarré.
    [Normal] De : [email protected] "Base10G_DBName_1_Archivelogs_rman_delete" Heure : 26/02/2013 12:10:33
    Lancement de l'application OB2BAR sur "clientxxx.domain.com" réalisé avec succès.
    [Normal] De : [email protected] "DBNameq" Heure : 26/02/2013 12:10:34
    D?marrage de la sauvegarde de la base de donn?es cible.
    Nom du service r?seau : DBNameq.
    Etat de l'instance : OPEN.
    Nom d'instance : DBNameq.
    DBID de la base de donn?es = 3864252955.
    Type de fichier de contr?le de BDD : CURRENT.
    Mode journalisation BDD : ARCHIVELOG.
    Logging mode: ARCHIVELOG.
    [Normal] De : [email protected] "DBNameq" Heure : 26/02/2013 12:10:35
    D?marrage de Oracle Recovery Manager.
    Recovery Manager: Release 10.2.0.4.0 - Production on Mar. F?vr. 26 12:10:35 2013
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    RMAN> CONNECT TARGET *
    2> CONNECT CATALOG *
    3> HOST 'exit';
    4> run {
    5> allocate channel 'dev_0' type 'sbt_tape'
    6> parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DBNameq,OB2BARLIST=Base10G_DBName_1_Archivelogs_rman_delete)'
    7> ;
    8> allocate channel 'dev_1' type 'sbt_tape'
    9> parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DBNameq,OB2BARLIST=Base10G_DBName_1_Archivelogs_rman_delete)'
    10> ;
    11> allocate channel 'dev_2' type 'sbt_tape'
    12> parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DBNameq,OB2BARLIST=Base10G_DBName_1_Archivelogs_rman_delete)'
    13> ;
    14> allocate channel 'dev_3' type 'sbt_tape'
    15> parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DBNameq,OB2BARLIST=Base10G_DBName_1_Archivelogs_rman_delete)'
    16> ;
    17> allocate channel 'dev_4' type 'sbt_tape'
    18> parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DBNameq,OB2BARLIST=Base10G_DBName_1_Archivelogs_rman_delete)'
    19> ;
    20> allocate channel 'dev_5' type 'sbt_tape'
    21> parms 'SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DBNameq,OB2BARLIST=Base10G_DBName_1_Archivelogs_rman_delete)'
    22> ;
    23>
    24> send device type 'sbt_tape' 'OB2BARHOSTNAME=clientxxx.domain.com';
    25> sql 'alter system archive log current';
    26> backup
    27> format 'Base10G_DBName_1_Archivelogs_rman_delete<DBNameq_%s:%t:%p>.dbf'
    28> archivelog all
    29> delete input;
    30> backup
    31> format 'Base10G_DBName_1_Archivelogs_rman_delete<DBNameq_%s:%t:%p>.dbf'
    32> current controlfile;
    33> }
    34> EXIT
    RMAN-06005: connect? ? la base de donn?es cible : DBNameQ (DBID=3864252955)
    RMAN-06005: connected to targeted database : DBNameQ (DBID=3864252955)
    RMAN-06008: connect? ? la base de donn?es du catalogue de r?cup?ration
    RMAN-06008: connected to recovery database
    RMAN-08030: canal affect? : dev_0
    RMAN-08030: allocated chanel : dev_0
    RMAN-08500: canal dev_0 : sid=422 typedev=SBT_TAPE
    RMAN-08500: dev_0 channel : sid=422 typedev=SBT_TAPE
    RMAN-08526: canal dev_0 : Data Protector A.06.20/DPWIN_00536(b621)
    RMAN-08526: dev_0 channel : Data Protector A.06.20/DPWIN_00536(b621)
    RMAN-08030: canal affect? : dev_1
    RMAN-08500: canal dev_1 : sid=888 typedev=SBT_TAPE
    RMAN-08526: canal dev_1 : Data Protector A.06.20/DPWIN_00536(b621)
    RMAN-08500: canal dev_2 : sid=681 typedev=SBT_TAPE
    RMAN-08526: canal dev_2 : Data Protector A.06.20/DPWIN_00536(b621)
    RMAN-08030: canal affect? : dev_3
    RMAN-08500: canal dev_3 : sid=717 typedev=SBT_TAPE
    RMAN-08526: canal dev_3 : Data Protector A.06.20/DPWIN_00536(b621)
    RMAN-08030: canal affect? : dev_4
    RMAN-08500: canal dev_4 : sid=223 typedev=SBT_TAPE
    RMAN-08526: canal dev_4 : Data Protector A.06.20/DPWIN_00536(b621)
    RMAN-08030: canal affect? : dev_5
    RMAN-08500: canal dev_5 : sid=212 typedev=SBT_TAPE
    RMAN-08526: canal dev_5 : Data Protector A.06.20/DPWIN_00536(b621)
    RMAN-06421: commande envoy?e au canal : dev_0
    RMAN-06421: command send to channel : dev_0
    RMAN-06421: commande envoy?e au canal : dev_1
    RMAN-06421: commande envoy?e au canal : dev_2
    RMAN-06421: commande envoy?e au canal : dev_3
    RMAN-06421: commande envoy?e au canal : dev_4
    RMAN-06421: commande envoy?e au canal : dev_5
    RMAN-06162: instruction SQL : alter system archive log current
    RMAN-06162: SQL query : alter system archive log current
    RMAN-03090: D?marrage de backup dans 26/02/13
    RMAN-03090: BAckup is starting in 26/02/13
    RMAN-08031: canal lib?r? : dev_0
    RMAN-08031: released channel : dev_0
    RMAN-08031: canal lib?r? : dev_1
    RMAN-08031: canal lib?r? : dev_2
    RMAN-08031: canal lib?r? : dev_3
    RMAN-08031: canal lib?r? : dev_4
    RMAN-08031: canal lib?r? : dev_5
    [Normal] De : [email protected] "Base10G_DBName_1_Archivelogs_rman_delete" Heure : 26/02/2013 12:10:46
    Application OB2BAR sur "clientxxx.domain.com" déconnectée.
    Application OB2BAR on"xxx" disconnected.
    [Critique] De : [email protected] "Base10G_DBName_1_Archivelogs_rman_delete" Heure : 26/02/2013 12:10:46
    Aucun Agent de disque ne s'est effectué correctement.
    La session a échoué.
    None of the Disk Agents completed successfully.
    Session has failed.
    [Normal] De : [email protected] "Base10G_DBName_1_Archivelogs_rman_delete" Heure : 26/02/2013 12:10:46
    Statistiques de la sauvegarde :
    Temps de file d'attente de la session (en heures) 0,00
    Agents de disque terminés ........ 0
    Agents de disque ayant échoué ........... 0
    Agents de disque abandonnés .......... 0
    Total des Agents de disque ........... 0
    ========================================
    Agents de support terminés ....... 0
    Agents de support ayant échoué .......... 0
    Abandon des Agents de support ......... 0
    Total des Agents de support .......... 0
    ===========================================
    Total Méga-octets ................. 0 Mo
    Total des supports utilisés ............. 0
    Total d'erreurs d'Agent de disque ...... 0

    Hello,
    No disconnection at all.
    It doesn't work since a crash of the DP server during the DB backup.
    When we move the catalog on the same server as the DB, the backup works but if we set the catalog to an other server (like the original setting) it doesn't work and we don't know why.
    It seems that when a backup is launched thru Data Protector, RMAN can't find the DB catalog. But if we run (manually) the RMAN command that DP used to do a backup, it works...

Maybe you are looking for