Validate backupset RMAN

Hello

Two-node RAC system. Database version 11 GR 2

I have two scripts - a script backups, a database ASM FIU (local backup) and another script uses the command "backupset backup" as shown below to the remote NFS mounting.

Run {}
allocate channel device type d2 disc format ' / cloudfs/oracle/temp/%U';
backupset backup completed between ' sysdate-1' and 'sysdate ';
output channel d2;
}


First question - what happens if the FRA ASM is not finished on time and still running. And the second script that the FRA of ASM to the NFS will start the backup run at the same time?

I think that the NFS backup is damaged. I have two configuration scripts run two hours apart from each other. But I think that this is not a good way to do it, because if the first backup runs longer than two hours?

Second question - can the command «backup backupset...» "expected automatically the first backup before it continues so it can back up all of ASM backupset?

Thank you in advance.

Published by: feverlove on October 21, 2012 15:43

Published by: feverlove on October 21, 2012 15:46

Hello;

First question - What happens if the ASM FRA is not completed on time and still running. And the second script that backup to the NFS will start execute at the same time??

I think it would work because the backup locations are different. But I have no way to test. Maybe save a tablespace as a small test.

Second question - Can the command "backup backupset ..." automatically waits for the first backup to complete before it continues so it can backup everything from ASM backupset??

backup backupset is used to make copies of games to backup so not.

Example of

RMAN>backup device type disk
backupset
completed before 'sysdate-10'

Best regards

mseberg

Tags: Database

Similar Questions

  • validate backupset

    Hi all

    I'm using Oracle 11 g 2.

    I take the backup of my database as below:

    database of the 'LEV0' tag drive backup incremental level 0 appliance type include current controlfile more archivelog tag 'LEV0' not backed up 2 times

    To make another copy of the backups that I am:

    backup format tag 'LEV0' backupset "backup_location/destination /".

    The statements above generate the same key backupset at two different location the first disk ASM + FRA and the second group to ' backup_location/destination / ".

    Let's say that the commands above created backup sets as below:

    Backup the key value in the key to backup location

    19173                         37470                                      +FRA....

    19173 37471 "backup_location/destination /"

    When I am trying to validate the backup as set below:

    validate backupset 19173.

    It's playback of + FRA or "/ destination/backup_location" (randomly sometimes it reads the backup sets of + FRA sometimes "/ destination/backup_location ' )

    My question is possible to force the "validate backupset 19173;" read + FRA only during the validation of the backupsets?

    Kind regards

    The exemplary value 15264 defined backup #1 backup

    Time of accomplishment of the time Type compressed device Tag

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

    00:19:04 DISC 17 JUNE 15 NO INCR_LV1_1506170100

    The list of items to backup to the backup set 15264 copy #1

    Name of the Key BP Pc # status element

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

    22580 +FRA/DB_NAME/backupset/2015_06_17/nnndn1_incr_lv1_1506170100_0.2699.882579633 AVAILABLE 1

    Backup the exemplary value n ° 2 defined backup 15264

    Time of accomplishment of the time Type compressed device Tag

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

    00:19:04 DISC 17 JUNE 15 NO INCR_LV1_1506170100

    The list of items to backup to the backup set 15264 copy #2

    Name of the Key BP Pc # status element

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

    22585 1 AVAILABLE/location_on_disk/INCR_LV1_1506170100_t7q9m65e_1_2

    You can also change COPY #2 unavailable to force rman validate the first copy.

    RMAN > change backuppiece 22585 unavailable;

    RMAN > validate backupset 15264.

    RMAN > change backuppiece 22585 available;

    If you don't want to validate all FRA, you can change only the backupieces filtering by tag.

    Select "change backuppiece ' |" RECID: ' unavailable;' -' available ';

    cmd to v$ element_sauvegarde

    where copy # 1

    and IS_RECOVERY_DEST_FILE = 'NO '.

    and tag = "INCR_LV1_1506170100."

    - AND COMPLETION_TIME FROM SYSDATE-1 TO SYSDATE"

    ;

    PS: Files in the recovery area flash cannot be marked as UNAVAILABLE. Because that where clause have ' IS_RECOVERY_DEST_FILE = 'NO "".

  • validate the rman backups

    Hello

    Oracle 9.2.0.1
    backup incremental cumalative RMAN

    Hello

    I do backups incremental cumalative. Full level 0 Friday, level 1 differential made Mon. - game.

    I noticed that if I run a RESTORE DATABASE VALIDATE command, it checks / uses all the pieces that are part of FULL LEVEL 0 only. But it doesn't tell me whether the incremental backup items created are good or not.

    How (without actually restoring to test the server) can test/validate until the last daily incremental backup?

    J

    VALIDATE RESTORE them will do only full backups, LEVEL 0 backups, controlfiles, spfile, copies of data file and the archivelogs. However, you can VALIDATE a LEVEL 1 backupset with simply:

    RMAN> VALIDATE BACKUPSET ;
    
  • Validate the RMAN backup in parallel

    Hello
    OS = Solaris 10
    Basis of data = 10 gr 2

    I use the following script to validate physical and logical corruption in the database using RMAN:

    RMAN target /.

    RMAN > RUN {
    SET UP THE DEVICE TYPE DISK PARALLELISM 8;
    ALLOCATE CHANNEL d1 DEVICE TYPE DISK;
    ALLOCATE CHANNEL d2 DEVICE TYPE DISK;
    ALLOCATE CHANNEL d3 DEVICE TYPE DISK;
    ALLOCATE CHANNEL d4 DEVICE TYPE DISK;
    VALIDATE THE BACKUP OF DATABASE;
    OUTPUT CHANNEL;
    }

    My machine has 4 processors.

    I just want to check that the RMAN script above will open up to 4 channels simultaneously and validate the database?

    concerning

    Hello

    Yes she open the four channels at the same time (as you have allocated for it), but why you specified 8?

    -Pavan Kumar N
    -ORACLE 9i / 10g - OCP
    http://www.oracleinternals.blogspot.com

  • How to validate a rman restore?

    Hi gurus,

    IM using 11.2.0.3 database oracle under redhat 5.3.

    I do every Monday and Thursday prod of a restore/recovery with a full backup of database to test the database (in a different server).

    I think I can use a view or a table to check if the restore was successful or not with this script:

    Select end_time, status, input_type
    v $ rman_backup_job_details
    where input_type <>'ARCHIVELOG;

    For example, I did a restore 12 and 15 this week, but it is appear:
    END_TIME  STATUS                  INPUT_TYPE
    --------- ----------------------- -------------
    10-NOV-12 COMPLETED               DB FULL
    11-NOV-12 COMPLETED               DB FULL
    12-NOV-12 COMPLETED               DB FULL
    13-NOV-12 COMPLETED               DB FULL
    14-NOV-12 COMPLETED               DB FULL
    15-NOV-12 COMPLETED               DB FULL
    Why does appear other days if I omitted 'ARCHIVELOGS', is there another way to query only the result of rman backup restore/recovery?

    You can filter the output, something like this:

    select OUTPUT,
      case
        when upper(output) like '%RESTORE COMPLETE%' then 'completed'
        when UPPER(OUTPUT) LIKE '%FINISHED RESTORE%' then 'completed'
        else 'error'
      end
    from v$rman_output
    where
         upper(output) like '%RESTORE COMPLETE%' OR
         UPPER(OUTPUT) LIKE '%FINISHED RESTORE%'
     OR (
    -- to avoid the controled erros you are having:
                                       SUBSTR(upper(output),1,5) = 'RMAN-'  AND
                                       SUBSTR(UPPER(OUTPUT),6,5) <> '00571' AND
                                        SUBSTR(UPPER(OUTPUT),6,5) <> '00569' AND
                                        SUBSTR(UPPER(OUTPUT),6,5) <> '03002' AND
                                        SUBSTR(UPPER(OUTPUT),6,5) <> '06054'
         );
    
  • RMAN BACKUP - validate

    Dear Experts,

    Version of DB - 11.1.0.7

    I have an RMAN BACKUP taken on the disk with the tag 'NAME of the tag. Is there a way to validate the backup using its tag name to check if it will be useful for a successful restoration and recovery of a different envt? Enjoy your thougts

    Thank you

    You can try

    RESTORE DATABASE FROM TAG 'tagname' VALIDATE ;
    RESTORE ARCHIVELOG ALL FROM TAG 'tagname' VALIDATE;
    

    There is also a command post, but it's the syntax requires allows you to specify the BACKUPSET and not the tag

    VALIDATE BACKUPSET 'key' ;
    

    Hemant K Collette

  • ASM files using RMAN backupset backup system migration

    my script to backup daily as below

    backup in the format of compressed backupset "$BACKUP_DIR/db_%U" database

    backup current controlfile "$BACKUP_DIR/Cont_%U" format

    backup as backupset archivelog Tablet format all '$BACKUP_DIR/arch_%U ';

    It is possible to migrate the database ASM uses above backup backupset RMAN?

    because I restore the database is restored, the problem is when he try to recover it, unable to understand the archivelog and redlog files.

    Hello

    in fact, after I moved the pieces to another server and called with RMAN (including the archivelog files)

    1. When you have moved to another server, then at this stage - my hypothesis, you have restored the controlfile to fileystem and mounted

    2. as you said moved to another server, the parts are on file system or (ASM location - still the second server can see)? If your answer is no, when you catalog now, controfile must save it with the file system path but not ASM

    Note - If you're still see ASM path then. the migration of the ASM to no - asm (the steps are not correct) logically you went wrong and implementation/execution thrown.

    3. provide the plan and execution - what you did (while we can fix). To be honest, while on the move DB to non - asm, why you need first to recovery? Tell me about your backup procedure itself is gone bad.

    To be honest, you try to database host of ASM no - asm as backup in function (but no real process of moving).  Therefore, in spite of the use of rman backup in dual function duplication... you have implemented in the wrong approach.

    This is the reason why I have provided the link and examples to understand.

    Hope you understand now.

    -Pavan Kumar N

  • Backup using RMAN error

    HI good day,

    I'm under oracle 11g on windows, as I am new to oracle database im practicing in my pc.

    When I practice I came across an error

    While taking ArchiveLog backup

    I did these steps

    RMAN > backup alchive connect all;

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-00558: error occurred during parsing of order entry

    RMAN-01009: syntax error: found 'identifier': expected an a: ' archivelog, too. "

    auxiliary, backupset backup, channel, check, controlfilecopy, copies, copy, cu

    mulative, common, database, data, db_file_name_convert, datafilecopy, db_re file

    covery_file_dest, diskratio, duration, filesperset, force, unit, format,.

    Since, full, incremental, keep maxsetsize nochecksum, noexclude, nokeep, p

    OOL, proxy, recovery, re-use, section, readonly jump, jump, spfile, tablespace, t

    AG, in, validate (")

    RMAN-01008: the identifier of the AfDB was: alchive

    RMAN-01007: line 1 column 8 file: entry standard

    This is the error that I had can someone help me solve this problem

    thanking you in advance

    Prakash

    Hello

    The problem is the syntax:

    Examples:

    RMAN > ARCHIVELOG BACKUP ALL.

    RMAN > delete any backup archivelog entry;

    Note: This save your archive and delete them;

    BACKUP DATABASE MORE ARCHIVELOG;

    Note: This will backup your database and your archive without deleting the archives.

    I hope this help you

    Concerning

  • How to make a backup of the database with RMAN Oracle Single Instance

    People,

    Hello. I use the server of Oracle 11 GR 1 material with operating system Oracle Linux 5.10 database.

    I understand how to back up the database instance in SQL Server with Windows. But do not really understand how to back up the database instance in Oracle on Linux.
    I did it cold and hot backup for the database HRCS90 instance, but both receive the same error message.


    Cold backup is below:

    SQL > startup
    ORACLE instance started.

    Total System Global Area 538677248 bytes
    Bytes of size 2146024 fixed
    528482584 variable size bytes
    4194304 buffers of data bytes
    Redo buffers 3854336 bytes
    Mounted database.
    Open database.


    SQL > shutdown immediate
    The database is closed.
    The database is dismounted.
    ORACLE instance stops.


    RMAN > backup database;

    From backup 25 November 13
    using the control file of the target instead of recovery catalog database
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the backup command to the 25/11/2013 14:26:52
    RMAN-06171: not connected to the target database


    RMAN > backup HRCS90

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-00558: error occurred during parsing of order entry
    RMAN-01009: syntax error: found 'distinctive sign': expected an of: ' archivelog, auxiliary, as, backup backupset, blocks, channel, check, copy, copies, controlfilecopy, cumulative, current, basic data, datafile, datafilecopy, device, diskratio, db_recovery_file_dest, db_file_name_convert, duration, filesperset, for, format, from, full, strength, file, incremental, keep, (, maxsetsize nochecksum, noexclude, nokeep, not, proxy, pool, re-use, recovery, section, skip). ', spfile, skip readonly, setsize, tablespace, tag to validate.
    RMAN-01008: the identifier of the AfDB was: HRCS90
    RMAN-01007: line 1 column 8 file: entry standard


    RMAN > backup database HRCS90

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-00558: error occurred during parsing of order entry
    RMAN-01009: syntax error: found 'distinctive sign': expected an of: ' archivelog, auxiliary, backupset channel, copy, controlfilecopy, backup, common, base data, data file, datafilecopy, remove, diskratio, db_recovery_file_dest, filesperset, format, force, file, include, keep, (, maxsetsize, noexclude, nokeep, not, pool, more reuse, recovery, section, skip, spfile, pass readonly, setsize, tablespace, tag, to).
    RMAN-01008: the identifier of the AfDB was: HRCS90
    RMAN-01007: line 1 column 17 file: entry standard

    While the instance of database HRCS90 is starting, I do hot backup by using the same commands and get the same error message with above cold backup.

    My question is:

    Can any folk tell me specific steps (order by order) to back up a single instance of the database in Oracle with RMAN?


    Thank you.

    Yes, you can restore and recover the backup, but not at the moment. You will only be able to restore and recover at the time of your backup.

    For example.

    If you take backup (mount point with no mode of journal archive) at 06:00 and your grave database crashes at 21:00, you will be able to restore and recover until 06:00. You will find all the changes made to the database between 06:00 and 21:00.

    If you want your database to recover until 9 PM or until a point in time, then you must put your database in log mode archive, and then save the archives.

  • RMAN does not delete obsolete files in a reliable way

    Hello experts RMAN,

    I have 11.2.0.1.0 on Windows Server 2003

    This instance IS in ArchiveLog mode. Do NOT use the catalogue

    Recently, I noticed inconsistent behavior of RMAN to delete obsolete backup sets.

    Let me give you an example: for months, I had the window of recovery set to 12 days.

    RMAN > view the retention policy.
    CONFIGURE RETENTION POLICY TO RECOVERY OF 12 DAYS WINDOW;

    Yesterday, 3/27 report obsolete showed this file:

    20270 23 March 12 backup set
    Total backup, 20270 F:\ORACLE\FLASH_RECOVERY_AREA\PBS March 23, 12
    \BACKUPSET\2012_03_23\O1_MF_ANNNN_TAG20120323T050002_7PRLFJ36_. BKP

    Today, 3/28, ran my work of simple deletion: delete NOPROMPT obsolete;

    Now, 2012_03_23\O1_MF_ANNNN_TAG20120323T050002_7PRLFJ36_. BKP no longer exists.

    Not all the files backup for 3/23 have been removed, only a small number.

    But why is any file 3/23 get deleted when the recovery window is 12 days?

    Of course, I'm afraid that my RMAN backups is perhaps not valid.

    Is that what someone did this experiment with RMAN on Windows?

    Thanks for all the ideas. John

    BACKUP VALIDATE... will not check your backups already taken.
    To do this, you need to run VALIDATE BACKUPSET or RESTORE VALIDATE that will search all the backup files needed to do a restore.

    Restoration of points must be created manually, so it's ok your results, if you have not created a.

    Concerning
    Nelson

  • Problem with RMAN

    People,
    I'm below when trying to clear channel configuration


    FYI
    --------------------------------------------------------------
    Oracle Database 10g Express Edition Release 10.2.0.1.0 - production
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    AMT for 32-bit Windows: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production

    RMAN > set UP the CHANNEL DEVICE TYPE DISK FORMAT CLEAR;

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-00558: error occurred during parsing of order entry
    RMAN-01009: syntax error: found 'Clear': expected an a: 'double-quoted-string '.
    equal, single-quoted-string. "
    RMAN-01007: in the file column 43-line 1: entry standard

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-00558: error occurred during parsing of order entry
    RMAN-01009: syntax error: found ';': expected an a: "assign, edit, save,
    beginline, blockrecover, catalog, change, connect, copy, convert, create, cross
    Verify, configure, duplicate, debug, delete, move, out, endinline, flashback, ho
    St, {, library, list, mount, open, print, quit smoking, recover, registry, liberation, repl}
    ACE, report, renormalize, reset, restore, resync, rman, run, rpctest, set, setli
    MIT, sql, switch, coil, start, stop, transmission, show, test, transport, upgrade
    unregister, validate.
    RMAN-01007: in the file column 48 line 1: entry standard


    RMAN > view all
    2 >.

    RMAN configuration parameters are:
    CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
    CONFIGURE BACKUP OPTIMIZATION # by default
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP # by default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE the FORMAT of DISC TYPE CHANNEL DEVICE "C:\oraclexe\oradata\backup\%U";
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SE
    RVER\DATABASE\SNCFXE. ORA'; # by default

    RMAN >

    Thanks in advance,
    Yann

    RMAN > CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT CLEAR;
    RMAN-00558: error occurred during parsing of order entry
    RMAN-01009: syntax error: found ';': expected an a: "assign, edit, save,
    beginline, blockrecover, catalog, change, connect, copy, convert, create, cross
    Verify, configure, duplicate, debug, delete, move, out, endinline, flashback, ho
    St, {, library, list, mount, open, print, quit smoking, recover, registry, liberation, repl}
    ACE, report, renormalize, reset, restore, resync, rman, run, rpctest, set, setli
    MIT, sql, switch, coil, start, stop, transmission, show, test, transport, upgrade

    This is completely incorrect syntax.

    + RMAN > CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT CLEAR; +

    +RMAN-00571: ===========================================================+
    + RMAN-00569: = ERROR MESSAGE STACK FOLLOWS = +.
    +RMAN-00571: ===========================================================+
    + RMAN-00558: error occurred during parsing of order entry.
    + RMAN-01009: syntax error: found 'Clear': expected an a: 'double-quoted-string, equal, new, single-quoted-string +.
    + RMAN-01007: in the file column 43-line 1: enter + standard

    * + RMAN > CONFIGURE CHANNEL DEVICE TYPE DISK CLEAR; + *

    * + using control file target instead of recovery catalog database + *.
    * + former RMAN configuration settings are correctly deleted + *.

    * + RMAN > + *.
    * + RMAN > + *.

    See the ORACLE documentation * http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/setup004.htm *.

  • content managed rman backup crushing and selection procedure of the tape media

    Hello Experts.

    I have a question about the backupset rman tape media manage tape of the osb.

    [ENV]

    Exadata rman backup assistance OSB(version: 10.4.0.3.0) SL500 LTO5 4 Tape Drive with rman scripts and full backup is working well.

    1 Appendix backup on OS crontab

    -Each backup full day at 00:00 AM

    2 rman view all:

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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

    RMAN settings for database with db_unique_name TESTDW are:

    CONFIGURE RETENTION POLICY TO 3 DAY RECOVERY WINDOW;

    CONFIGURE BACKUP OPTIMIZATION # by default

    CONFIGURE THE TYPE OF DEFAULT DEVICE TO 'SBT_TAPE ';

    SET UP THE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 TYPE OF BACKUP BACKUPSET.

    CONFIGURE CONTROLFILE AUTOBACKUP ON;

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    3 rman backup scirpts

    Run {}

    allocate channels c01 type 'sbt_tape' connect 'sys/manager@testdw1';

    allocate channel c02 type 'sbt_tape' connect 'sys/manager@testdw2';

    allocate channel c03 type 'sbt_tape' connect 'sys/manager@testdw1';

    allocate channels c04 type 'sbt_tape' connect 'sys/manager@testdw2';

    Backup section size 900g database;

    output channel c01;

    output channel c02;

    output channel c03;

    output channel c04;

    }

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    1st quarter > after several weeks and I run the command as "#obtool u admin Pei welcome1 lsvol-L lib1.

    and are used in many media of rman backup band (about 50EA media, perhaps 46EA are full and 4EA are appendble)

    So, I issue the command 'lsvol - a - c' and could not display expired on all media content.

    Why OSB no has not select and replace the tape media despite the rman rman default retention policy (3days) all show the setting.

    Why OSB does not have the expired status of rman content on tape media?

    -> I need the rman (delete expired, delete obsolete etc...) command to share the summary status of OSB and rman rman?

    Q2 > selection procedure for the tape media all backup rman

    Suppose the total number of tape media is 5EA. (1,2,3,4,5) with an available tape LTO5 drive.

    Status: 1 (full-rman content already expired), 2 (content integral-rman not expired), 3 (editable, remaining space), 4 (new media), 5 (currnet wring media)

    If OSB burn now 5 and reach at the end of the Strip and possibly another media, media to be selected by the OSB?

    Advanced thanks.

    If I place the order obsolete in the rman script as 'delete type 'SBT_TAPE' noprompt obsolete device;' the results will be the same as your

    the syntax because rman default setting (CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 3 DAYS ;) has already been fixed on the command "Show all", right? @)

    Yes.

    I use the catalog of recovery on a different database and backup script has catalog db connection string.

    And if I only use controlfile instead of recovery catalog to save the backup information and put in place "control_file_record_keep_time" a default of 7 days to 365 days, "remove obsolete" command to remove several weeks backupset works well, is it not?

    Possible problem are existing backups for several weeks if you left default control_file_record_keep_time. Change now will not help unless you catalog later manually all the old pieces not catalogued on tape backup.

    After you clean up the situation and particularly to remove obsolete in your script, rman, you will never make problems with control_file_record_keep_time from this moment. By default will do just fine because it is larger than your window of recovery.

    Kind regards

    Mitja

  • wit problem via rman backup

    10 2 0 5 version
    Windows xp

    I am taking cold backup of test data without using the catalogue.

    I mounted database and tried the following query, his throw errror below... Please help

    RMAN > backup database;

    From backup February 17, 11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid = 155 devtype = DISK
    channel ORA_DISK_1: from full datafile backupset
    channel ORA_DISK_1: specifying datafile (s) in backupset
    RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 17/02/2011 15:56:28
    ORA-19602: no backup or copy of current file in NOARCHIVELOG mode
    continue other job steps, not a not working will not re-run
    channel ORA_DISK_1: from full datafile backupset
    channel ORA_DISK_1: specifying datafile (s) in backupset
    including the current control in backupset file
    including current SPFILE in backupset
    channel ORA_DISK_1: starting piece 1 to February 17, 11
    channel ORA_DISK_1: finished piece 1 to February 17, 11
    room handle=D:\ORACLE\PRODUCT1\10.2.0\FLASH_RECOVERY_AREA\CATALOG\BACKUPSET\2011_02_17\O1_MF_NCSNF_TAG20110217T155628_6OSXYQHK_. Tag BKP = comment TAG20110217T155628 = NONE
    channel ORA_DISK_1: complete set of backups, time: 00:00:03
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================

    RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 17/02/2011 15:56:28
    ORA-19602: no backup or copy of current file in NOARCHIVELOG mode

    Thanks and greetings
    Arun

    Was there a 'cancel the stop' or a crash before mount 'start '? If so start database, stop it properly and try again.

    Werner

  • is validate the restore of the databases fairly

    Hi guys

    Is it enough to perform this restore validate sufficient data to prove that the databases can be restored?

    Please tell me whether or not.

    Thank you

    Hi haggy_fleisch,

    Oracle documentation.

    RESTORATION... VALIDATE causes RMAN select existing backups that she would use to perform a RESTORE operation and scan them all to make sure that they are present and free of corruption.

    If this seems sufficient.

    There is an argument for actually performing a restore (or duplicate) so not only a scan is performed, but also a write to the disk in a way a little more tests.

    Kind regards

    Tycho

  • size of block RMAN error

    Hi I was taking before backup. After a lot of time when I repeated the backup, I had this messge anyone could guide what could be the possible reason for this error and the cure.


    RMAN > backup database;

    From backup 20 April 09
    using channel ORA_DISK_1
    channel ORA_DISK_1: from full datafile backupset
    channel ORA_DISK_1: specifying datafile (s) in backupset
    including current SPFILE in backupset
    including current controlfile in backupset
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 2009-04-20 08:30:
    08
    ORA-19597: file E:\ORADB10G\ORADATA\MISDB\SYSTEM01. DBF 8192 blocksize is not m
    atch value 16384 blocksize

    regards and thanks in advance n
    efshafi

    Hello

    you could look at metalink id: 234178.1
    It might help you.

    Thank you
    Benjamin Gopal

Maybe you are looking for