How to plan backup rman

I'm a little confused about incremental backup, I use the following command for the daily backup.

RUN

{

GET COPY OF DATABASE WITH TAG "incr_backup".

INCREMENTAL BACKUP LEVEL 1 for BACK OF COPY WITH TAG "incr_backup".

DATABASE;

}

It is good to run the level 0 backup by the following command after each week or over drive is sufficient.

DATABASE INCREMENTAL LEVEL 0 BACKUP;

Oracle 11g 2

Windows server 2008.

If I take Level0 backup first

DATABASE INCREMENTAL LEVEL 0 BACKUP;

then level 1 backup is very low, which means level1 beginning after Level0

DATABASE INCREMENTAL BACKUP OF LEVEL 1;

But if I take the backup with Level0 and after this backup with the following script, then level1 is very large which means that it has taken to safeguard the beginning.

RUN

{

GET COPY OF DATABASE WITH TAG "incr_backup".

INCREMENTAL BACKUP LEVEL 1 for BACK OF COPY WITH TAG "incr_backup".

DATABASE;

}

-should I use level 0 such tag used in above script.

Tags: Database

Similar Questions

  • How to use backups RMAN to restore a RAC database to single instance on another host?

    How to use backups Rman to restore a RAC database to single instance on another host?

    I tried to copy these inline for you:

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




    Backups RMAN disk HowTo restore database RAC to single Instance on another node (Doc ID 415579.1)

    Down

  • How to restore backup rman to the new host with the structure of the various files on windows?

    Here are the steps that I follow...

    1 oradim create new instance

    2 startup nomount pfile = 'C:\inittest.ora'

    3. restore conrolfile of 'c:\name.bak '.

    I found this file control point to the oradata folder as directed by the original host

    4. Alter database mount

    Mounted DB.

    5 restore database completed with error

    switch to the previous backup

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

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

    RMAN-03002: failure of the restore command at the 12:17:55 08/12/2014

    RMAN-06026: some targets not found - abandonment of restoration

    RMAN-06023: no backup or copy of the file 4 found to restore

    RMAN-06023: no backup or copy of datafile 3 found to restore

    RMAN-06023: no backup or copy of datafile 2 found to restore

    RMAN-06023: no backup or copy of datafile 1 found to restore

    So, it is possible to restore and recover the rman backup to the new host with the structure of different file...?

    Hello

    Try to rename the log file to roll forward online to the desired path on the destination server, and then open with resetlogs.

    SQL > alter database file rename ' G:\APP\ORADATA\HOOP\REDO01. JOURNAL "to"";

    Kind regards

    Shivananda

  • Backup RMAN of TAR FULL after finishing.

    Hi all
    We plan backups RMAN from EMGC 10
    Databases / DB / availability / schedule backup / database backup schedule / all custom...
    I can add the line of tar in the RMAN script but the RMAN does not tar - czvf...

    How is it possible to tar backup after arriving? I can string a bash script?
    Thank you
    * T

    When you use the OEM GC configuration for running a scheduled backup, OEM GC run an RMAN session. You will not be able to change this option by inserting the shell commands.

    What you could do, is have the OEM GC to create the RMAN script for you (or creat it yourself), store the RMAN script in your catalog RMAN and create a BONE type Job. In this job, you can run a shell script, which first start RMAN session and run the RMAN script stored, that you created, and then run your command "tar".

    You can even think to do that with a multi step employment type, so that if your RMAN defective stage, you do not want the step of tar to execute.

    Concerning
    Rob

  • How to restore the Rman incremental level 0 backup if the SID is different?

    Hi Experts,
    I had a little problem with restore rman backup of level 0. I have backup rman for oracle 11.2.0.1.0 - 64 bit and restore the server to Test 11.2.0.1.0 - 64 bit.

    Problem:
    Sid = prd production server
    Sid = prderp test server

    Operating system is Oracle linux 5 on both servers.

    How to restore Rman if the SID is different?

    Hello

    Refer to this http://shivanandarao.wordpress.com/2012/04/19/duplicating-primary-database-to-a-new-host-without-connecting-to-the-primary-database-in-oracle-10g11g/

    You need to restore it under the same name as you have in the production and later change the dbname using the NEST.

    If you don't want to go with this method, then I suggest you to go with the method of double RMAN.

    http://www.Oracle-base.com/articles/11g/duplicate-database-using-RMAN-11gr2.php
    http://docs.Oracle.com/CD/B28359_01/backup.111/b28270/rcmdupdb.htm

    rman target sys/@prod auxiliary sys/@tst
RMAN>duplicate target database to 'prderp' nofilenamecheck;

    Please close this Re: how to restore the Rman backup if the SID is different? wire by marking as replied.

  • How to ensure the rman backup is successful?

    Hello

    We have scheduled backup rman jobs.
    1. but how do ensure us that all rman backups are successful?
    2. If the rman written directly to tape, how to ensure that all tape backup are successful?

    Thank you

    Andrew

    Not sure why you were not able to download. I sent you a copy.

    Kind regards
    S.K.

  • How to remove the old backup RMAN

    Hello Experts,

    Please English me to remove my old backups RMAN. We act in RMAN backup on a daily basis on the disc. you want to delete the previous day from the disk backup.

    Any help?

    Ideally if your backup is automatic, you need to add a line "delete noprompt obsolete device type disk;" at the end of backup scripts based on your retention policy clean the old not required for backups.

    HTH.

  • Help remove backups rman (delete the repository)

    Hi all.

    I will soon be administering a few databases Oracle (11g Rel2). Currently these DBs area in log mode archive with a backup rman in place policy.


    I don't like this policy and you want to use my own, incremental backups from updadateable, so this is the plan I have in mind.


    (1) disable mode archive.


    (2) a clean shutdown and take a backup to cold.


    (3) since after you disable archiving, backups RMAN ALL will be unusable, I want to remove them (including newspapers archive and backup sets).


    (4) after the correct deletion, set up some persistent RMAN settings, such as retention policy, controlfile autobackup and optimization.


    (5) turn on archiving


    (6) to set up the new policy based backups backup incremental updateable with duplex location for archiving logs.


    Help is requested on the best way to clean all the backups (3).


    I can manually delete the backups and do overlap, but according to the Oracle Documentation "Delete backup" will be delete all backups for data recorded in the RMAN Repository.


    So which is the best way easier and faster? Will delete backup include the archive logs?


    Thanks in advance. Luis!


    myluism wrote:

    Can I still use them?

    I would say it is "the wrong answer to evil. When you disable log mode archive, you can only back up the database when it is stopped and only to restore and recover the database until the last stop.

    Looking at your plan, I wonder what you are trying to accomplish first log mode archive disabling and then enabling archive mode log again. Why do you think that this is necessary and what you're trying to accomplish.

    You need not disable and enable log mode archive in order to eliminate the obsolete achivelogs.

    If you are not satisfied with the retention policy, simply change it. All backups that are outside your retention policy will be considered as obsolete and you can remove them using RMAN delete obsolete, which will remove all files as well as the appropriate data backup from the RMAN Repository.

    For example you can archivelog delete all the entries backup and then delete the backupset or remove them at the OS level, do overlap and then use delete noprompt expired archivelog all.

    The retention policy applies to backup and archivelogs. However, you can have a separate archivelog deletion policy that applies to archivelogs.

  • Do not lock - automate the deletion of backups RMAN old day after a success

    Hi all

    Admin: Do not lock this thread. I moved here the database instance based on the suggestion of another Member, and the question to this forum. If you want to lock a thread, lock one in the forum of the database, not this one.

    I am looking for a way to automate the deletion of backups RMAN old days only after the occurrence of a success. At the present time, I have daily backups of L0 via crontab, and I need to create a script that can tell if a successful backup is done, then delete the old L0 if it has. Any suggestions on how to start? I'm stuck in code to see if a successful backup has been performed.

    Oracle 11.2.0.3

    Exadata (4 nodes)

    Linux 5.10

    * a from database forum

    A backup is completed when the backup command is complete.

    You have two 'blocks execution' in your rman script.

    Put the DELETE OBSOLETE between the end of the last execution block and EXIT:

    OUTPUT CHANNEL fs1b;
    OUTPUT CHANNEL fs2b;
    OUTPUT CHANNEL fs3b;
    CHANNEL fs4b;
    CHANNEL fs5b;
    CHANNEL fs6b;
    CHANNEL fs7b;
    CHANNEL fs8b;

    }

    remove the backup noprompt obsolete;
    "exit";

    You also want to do some other household:

    cross-checking of backup;

    delete expired backup noprompt.

    overlap archivelog all;

    delete noprompt expired archivelog all;

  • How to run the rman output files, which are more days of retention

    I use for my rman backup tasks.

    I have format my output files of rman to a specific path, instead of the fast recovery area.

    Also, I spend below command in RMAN

    RMAN > CONFIGURE RETENTION POLICY to RECOVERY OF 7-DAY WINDOW;

    And the "control_file_record_keep_time" parameter is also set to 7.

    I've been running rman for 8 days. Everything seems good. But I find several rman output files are more than 7 days.

    So, I just want to know how to handle the rman output, which is longer than 7 days files?

    In fact, I assumed that these older files should be obsolete files, but rman is not to declare that they are obsolete.

    So how do now?

    user8710670 wrote:

    I use for my rman backup tasks.

    I have format my output files of rman to a specific path, instead of the fast recovery area.

    Also, I spend below command in RMAN

    RMAN > CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;

    And the "control_file_record_keep_time" parameter is also set to 7.

    I've been running rman for 8 days. Everything seems good. But I find several rman output files are more than 7 days.

    So, I just want to know how to handle the rman output, which is longer than 7 days files?

    In fact, I assumed that these older files should be obsolete files, but rman is not to declare that they are obsolete.

    So how do now?

    Windows 7 day average recovery rman will protect everything necessary for the recovery to any point in time in the last 7 days.  In fact, in the last 604800 seconds.  The same will mean that he need the files OLDER than that.  Simply because a backupset is older that your recovery window does NOT as yet, it is obsolete.  Any recovery begins with the last FULL or INCREMENTAL backup ZERO before the recovery point.  And it does not matter how old the backup is, it will be obsolete.  Suppose you take a level 0 backup, 1 January and for the rest of the year taking nothing but level 1 and backup archivelog.  31 December than and only the full backup will still not be obsolete, even though he is a year old.

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

    removal of the obsolescence of RMAN

    Day 1 - level 0

    Day 2 - level 1

    Day 3 - level 1

    Day 4 - level 1

    Day 5 - level 1

    Day 6 - level 1

    Day 7 - level 1

    Day 8 - level 0

    Day 9 - level 1

    Day 10 - level 1

    Day 11 - level 1

    Day 12 - level 1

    Day 13 - level 1

    Day 14 - level 1

    On day 14, your window of 7 days is up to date 7.  A recovery to date must begin by restoring the backup of level 0 of the day 1. So it may be outdated.  Some level 1 between 1 and 6 days backups might be obsolete, depending on if they are incremental or cumulative, and it also happens with archivelogs.

    If you have access to MOS, you can review the notes 462978.1 and 463875.1.

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

  • 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

  • Restoring a backup RMAN to a new instance of the database

    Hi guys,.

    I have a problem with restoring a backup RMAN I have with me a new instance of the database. I have with me are:

    1. backup of the SPFile. (O1_MF_NCNNF_CTLFILE_BU_92DVGYO2_. BKP)

    2. backup of the control file (O1_MF_NNSNF_SPFILE_BU_92DVGW9H_. BKP)

    3. the full backup (O1_MF_NNSNF_FULLPROD_BU_92DVGW9H_. BKP)

    I received these files to a client environment and I need to restore these to a new instance of the database on a local computer. I gave an attempt as follows (in Oracle 10 g):

    1, creates a new instance of the (Test75) database using the Oracle Database Configuration Assistant

    2 SET ORACLE_SID = Test75

    3 connection to this instance with RMAN

    4 tried to restore the SPFILE from the BKP file received.


    I make mistakes and cannot continue. I don't know if I will carry out the correct steps. Please help me telling me how I should achieve this goal.


    Thank you.

    1. backup of the SPFile. (O1_MF_NCNNF_CTLFILE_BU_92DVGYO2_. BKP)

    2 backup of control file (O1_MF_NNSNF_SPFILE_BU_92DVGW9H_. BKP)

    The first backuppiece resembles a ControlFile and the other looks like a SPFILE'

    > I get error and cannot continue

    What is the error?  (I assume that you have tried to restore the O1_MF_NNSNF_SPFILE_BU_92DVGW9H_ SPFILE. BKP

    Note that you must also SET the DBID before restoring the controlfile

    Hemant K Collette

  • backup RMAN with damaged block

    Hello

    First-, I have problem on non-production 11.2.0.1.0 database, so I'm not deeply concerned about data. But I need to understand what happened with database backups and how to prevent these things in the future.
    So - I have backup complete regular weekly EM and daily incremental backups. Later, he had problem with equipment and some blocks corrupted database found. The weekly backup ran without error and obsolete backups have been removed. Now, it is not possible to 'retrieve the list of corruption' because there is no backup without the corruption (RMAN-06023: no backup or copy of the data file 6 found to restore). I'm not worried about the loss of data, but I need to know how is the backup contains the corrupt blocks.

    I checked the data file using utility dbv
    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 data file 6 - user03.dbf contains errors. Also the backups now contain errors.

    (1) so how is it possible that the scheduled backup EM took place without problems and now the backup contains corrupted blocks. How to avoid this in the future? I know there is MAXCORRUPT setting. How can I check its current value? How can I configure using backups EM on-demand?

    (2) Secondly, at the same time, I studied the RMAN commands. So I have suspended the work of backup EM and run follwing command. And backup represented without error. How is this possible, if the data in the file users06.dbf is corrupted block?


    Thank you!
    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

    OK, sounds good, do not hesitate to open a TAR because bedbugs are not all public...

    Keep us in the loop.

    Good bye.

  • Backup RMAN HRTO

    Oracle 11.2.0.2

    Question: Via TSM I need to copy a backup rman since a TSM server to the disk.

    I have rman backups who have written on tape SBT (TSM server). I can get the handle with the backup from the list, but how to find the path where it is written. Looking at the tdpo.opt file has a value for TDPO_FS, which is a virtual drive. I can't use backup because rman backup set which works only from disk to tape and NO tape on the disc. So I have to try to get this backupset through TSM commands.

    Any help would be appreciated!

    If you want to copy the TSM backups on disk, you can simulate a scenario to "restore to a new host. The TSM API knows where to find the tape backup.

    http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmadvre.htm#i1007814

    Otherwise, you have tom consult TSM staff, I am sure that 'somewhere' in the TSM environment that real places are stored. But who does not directly to RMAN/Oracle.

    Werner

  • Relationship between current incarnation & backup / RMAN-20011

    Hello

    I have

    the following situation in RMAN:

    Incarnations:

    >
    RMAN > list incarnation;


    List of Incarnations of the database
    DB key Inc key STATE ID DB name DB reset reset time SNA
    ------- ------- -------- ---------------- --- ---------- ----------
    133 146 TESTDB 2528045035 PARENT 05-SEPT 1.-10
    133 134 TESTDB 2528045035 CURRENT 972274 2 MARCH 11
    133 548 TESTDB 2528045035 ORPHAN 996374 MARCH 2, 11
    133 646 TESTDB 2528045035 ORPHAN 996490 4 MARCH 11
    133 460 TESTDB 2528045035 ORPHAN 997986 MARCH 2, 11
    >

    Backups:

    >
    RMAN > list backup;


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


    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    56,57 M 176 00:00 DRIVE: 42 MARCH 2, 11
    BP key: 177 situation: AVAILABLE Tablet: NO Tag: TAG20110302T100444
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/01m66vht_1_1

    List of newspapers archived in defined backup 176
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    1 2 977121 2 MARCH 11 988286 MARCH 2, 11
    1 3 988286 2 MARCH 11 994189 MARCH 2, 11

    Time of accomplishment BS key Type LV size device Type elapsed time
    ------- ---- -- ---------- ----------- ------------ ---------------
    Incr 187 0 M DISK 00:15:42 999,72 2 March 11
    BP key: 190 situation: AVAILABLE Tablet: NO Tag: TAG20110302T100531
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/02m66vjc_1_1
    List of defined backup data files 187
    Name of file LV Type cash SNA cash time
    ---- -- ---- ---------- --------- ----
    1 0 incr 994637 /CDATA/TESTDB/system01.dbf March 2, 11
    2 0 994637 /CDATA/TESTDB/sysaux01.dbf incr 2 March 11
    3 0 incr 994637 /CDATA/TESTDB/undotbs01.dbf March 2, 11
    4 0 incr 994637 /CDATA/TESTDB/users01.dbf March 2, 11

    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    DISK 4,48 M 201 00:00: 01 MARCH 2, 11
    BP key: 206 location: AVAILABLE Tablet: NO Tag: TAG20110302T102124
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/03m670h5_1_1

    List of newspapers archived on backup the value 201
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    1 4 994189 2 MARCH 11 996336 MARCH 2, 11

    Time of accomplishment BS key Type LV size device Type elapsed time
    ------- ---- -- ---------- ----------- ------------ ---------------
    214 full 9.36 M DISK 00:00:10 March 2, 11
    BP key: 216 situation: AVAILABLE Tablet: NO Tag: TAG20110302T102129
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-00
    SPFILE included: Modification Date: March 2, 11
    SPFILE db_unique_name: TESTDB
    Control file included: cash SNA: 996373 cash time: March 2, 11

    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    244 757,50 K DISK 00:00:01 MARCH 2, 11
    BP key: 247 Situation: AVAILABLE Tablet: NO Tag: TAG20110302T103137
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/05m67149_1_1

    List of newspapers archived in backup set 244
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    1 5 996336 2 MARCH 11 997210 MARCH 2, 11

    Time of accomplishment BS key Type LV size device Type elapsed time
    ------- ---- -- ---------- ----------- ------------ ---------------
    261 incr 0 M DISK 00:13:29 1001,02 March 2, 11
    BP key: 263 situation: AVAILABLE Tablet: NO Tag: TAG20110302T103138
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/06m6714b_1_1
    List of defined backup data files 261
    Name of file LV Type cash SNA cash time
    ---- -- ---- ---------- --------- ----
    1 0 incr 997238 /CDATA/TESTDB/system01.dbf March 2, 11
    2 0 997238 /CDATA/TESTDB/sysaux01.dbf incr 2 March 11
    3 0 incr 997238 /CDATA/TESTDB/undotbs01.dbf March 2, 11
    4 0 incr 997238 /CDATA/TESTDB/users01.dbf March 2, 11

    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    279 742,00 K DISK 00:00:01 MARCH 2, 11
    BP key: 284 situation: AVAILABLE Tablet: NO Tag: TAG20110302T104517
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/07m671tt_1_1

    List of newspapers archived on backup worth 279
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    1 6 997210 2 MARCH 11 997953 MARCH 2, 11

    Time of accomplishment BS key Type LV size device Type elapsed time
    ------- ---- -- ---------- ----------- ------------ ---------------
    297 full 9.36 M DISK 00:00:10 March 2, 11
    BP key: 299 situation: AVAILABLE Tablet: NO Tag: TAG20110302T104519
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-01
    SPFILE included: Modification Date: March 2, 11
    SPFILE db_unique_name: TESTDB
    Control file included: cash SNA: 997985 cash time: March 2, 11

    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    * 342 438,00 K DISK 00:00:00 MARCH 2, 11 *.
    BP key: 345 location: AVAILABLE Tablet: NO Tag: TAG20110302T104935
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/09m67260_1_1

    List of newspapers archived on backup worth 342
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    * 1 7 997953 2 MARCH 11 998260 2 MARCH 11 *.

    Time of accomplishment BS key Type LV size device Type elapsed time
    ------- ---- -- ---------- ----------- ------------ ---------------
    * 364 incr 0 M DISK 00:14:34 1001,65 2 March 11 *.
    BP key: 366 situation: AVAILABLE Tablet: NO Tag: TAG20110302T104937
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1
    List of defined backup data files 364
    Name of file LV Type cash SNA cash time
    ---- -- ---- ---------- --------- ----
    * 1 0 incr 998289 /CDATA/TESTDB/system01.dbf* March 2, 11
    * 2 0 998289 /CDATA/TESTDB/sysaux01.dbf* incr 2 March 11
    * 3 0 incr 998289 /CDATA/TESTDB/undotbs01.dbf* March 2, 11
    * 4 0 incr 998289 /CDATA/TESTDB/users01.dbf* March 2, 11

    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    * 7,58 M 387 00:00 DISK: 02 MARCH 2, 11 *.
    BP key: 392 situation: AVAILABLE Tablet: NO Tag: TAG20110302T110421
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0bm6731m_1_1

    List of newspapers archived in backup set 387
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    * 1 8 998260 2 MARCH 11 1000465 2 MARCH 11 *.

    Time of accomplishment BS key Type LV size device Type elapsed time
    ------- ---- -- ---------- ----------- ------------ ---------------
    * 410 full 9.36 M DISK 00:00:10 March 2, 11 *.
    BP key: 412 situation: AVAILABLE Tablet: NO Tag: TAG20110302T110425
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02
    SPFILE included: Modification Date: March 2, 11
    SPFILE db_unique_name: TESTDB
    Control file included: cash SNA: 1000507 cash time: March 2, 11

    Time of accomplishment BS key Type LV size device Type elapsed time
    ------- ---- -- ---------- ----------- ------------ ---------------
    483 full 9.36 M DISK 00:00:05 March 2, 11
    BP key: 484 situation: AVAILABLE Tablet: NO Tag: TAG20110302T113759
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-03
    SPFILE included: Modification Date: March 2, 11
    SPFILE db_unique_name: TESTDB
    Control file included: cash SNA: 998081 cash time: March 2, 11

    Time of accomplishment BS key Type LV size device Type elapsed time
    ------- ---- -- ---------- ----------- ------------ ---------------
    571 full 9.36 M 04:00:00 disc 2 March 11
    BP key: 572 situation: AVAILABLE Tablet: NO Tag: TAG20110302T121754
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-04
    SPFILE included: Modification Date: March 2, 11
    SPFILE db_unique_name: TESTDB
    Control file included: cash SNA: 996489 cash time: March 2, 11

    Time of accomplishment BS key Type LV size device Type elapsed time
    ------- ---- -- ---------- ----------- ------------ ---------------
    667 full 9.36 M DISK 00:00:18 March 4, 11
    BP key: situation 668: AVAILABLE Tablet: NO Tag: TAG20110304T132050
    Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110304-00
    SPFILE included: Modification Date: March 4, 11
    SPFILE db_unique_name: TESTDB
    Control file included: cash SNA: 996596 cash time: March 4, 11

    RMAN >
    >

    I want to rebuild the database with the backup (bold text).


    And I get the error after you run the following script:

    >
    RMAN > RUN
    2 > {}
    3 > # STARTUP NOMOUNT;
    4 > # RESTORE SPFILE to ' / u01/app/oracle/product/11.2.0.2/db_1/dbs/spfileTESTDB.ora' tag "TAG20110302T063849".
    5 > # SHUTDOWN IMMEDIATE;
    6 > STARTUP NOMOUNT;
    7 > RESTORE CONTROLFILE tag "TAG20110302T110425".
    8 > STARTUP MOUNT;
    9 > SET up to this THAT SNA 1000507.
    10 > RESTORE database;
    11 > RECOVER DATABASE;
    12 > ALTER DATABASE OPEN RESETLOGS;
    {13 >}
    database is already started

    From restoration to March 4, 11
    using channel ORA_DISK_1

    channel ORA_DISK_1: from the restore backup set data file
    channel ORA_DISK_1: restore the control file
    channel ORA_DISK_1: backup /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02 piece reading
    channel ORA_DISK_1: room handle=/opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02 tag = TAG20110302T110425
    channel ORA_DISK_1: restored the backup part 1
    channel ORA_DISK_1: restore complete, duration: 00:00:15
    output file name=/CDATA/TESTDB/control01.ctl
    output file name=/CFLASH/TESTDB/control02.ctl
    Restoration finished in March 4, 11

    database is already started
    mounted database
    output channel: ORA_DISK_1

    executing command: SET until clause

    From restoration to March 4, 11
    From implicit overlapping backup 4 March 11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID = 136 type of device = DISK
    Cut 11 objects
    Backup of implicit overlap finished March 4, 11

    Starting copy of implicit intersection to March 4, 11
    using channel ORA_DISK_1
    Copy of implicit cross ended up at March 4, 11

    the search for all files in the recovery area
    cataloging files...
    cataloging done

    List of cataloged files
    =======================
    File name: /CFLASH/TESTDB/archivelog/2011_03_04/o1_mf_1_1_6q1k25xs_.arc

    using channel ORA_DISK_1

    channel ORA_DISK_1: from the restore backup set data file
    channel ORA_DISK_1: specifying datafile (s) to restore from backup set
    channel ORA_DISK_1: restore datafile 00001 to /CDATA/TESTDB/system01.dbf
    channel ORA_DISK_1: restore datafile 00002 to /CDATA/TESTDB/sysaux01.dbf
    channel ORA_DISK_1: restore datafile 00003 to /CDATA/TESTDB/undotbs01.dbf
    channel ORA_DISK_1: restore datafile 00004 in /CDATA/TESTDB/users01.dbf
    channel ORA_DISK_1: backup /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1 piece reading
    channel ORA_DISK_1: room handle=/opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1 tag = TAG20110302T104937
    channel ORA_DISK_1: restored the backup part 1
    channel ORA_DISK_1: restore complete, duration: 00:13:45
    Restoration finished in March 4, 11

    From back to March 4, 11
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the command recover at 04/03/2011 13:47:17
    RMAN-06004: error ORACLE recovery catalog database: RMAN-20011: target database incarnation is not common in the recovery catalog

    >

    How will I know the right embodiment to restore power?


    Help, please

    Reagards

    hqr200475

    Edited by: hqt200475 the 04.03.2011 06:19

    To verify valid backups in the current version number:

    recoverable backup list;

    Definition of this statement:

    /*
    Specifies the data backups or copies file whose status in the repository is AVAILABLE and which can be used for restoration and recovery in the course of the incarnation target database. This list includes all backups and copies except the incremental backups that have no valid parent to which the differential can be applied.
    */

    Werner

Maybe you are looking for