Rman backup 11g rel2

Hello Guys
I was testing rman backup on oracle 11g rel2 , logging time for backup using rman as in 2 ways 1) full database backup
2)full database backup /parallel feature say "section size 200M" in script
i was expecting due to new 11g feature option 2 should complete faster ,but its reverse without using this feature
its running more fast (completing by 4-5 minutes less time)
I also tried taking backup of 1 datafile or 1 tablespace using both the option and also placing backupsets
on different folders/mountpoints ,but result is same
if you had worked on this feature ,please give details what is benefit of using this feature,i can see disadvantage here
Thanks

804719 wrote:
so without section size this operation is not actually parallelYes, it's not parallel for datafile, but it parallel for the entire job.
You can analyze the backup log. It should contains the records about opening several channels simultaneously, for instance:
Starting backup at 26/04/12 23:14:19
channel tape1: starting full datafile backup set
channel tape1: specifying datafile(s) in backup set
input datafile file number=00049 name=/home/oracle/oradata/...
channel tape1: starting piece 1 at 26/04/12 23:14:21
channel tape2: starting full datafile backup set
channel tape2: specifying datafile(s) in backup set
input datafile file number=00050 name=/home/oracle/oradata/...
channel tape2: starting piece 1 at 26/04/12 23:14:22
channel tape3: starting full datafile backup set
channel tape3: specifying datafile(s) in backup set
All within 3 seconds, and working in parallel...

Similar Messages

  • RMAN backup is getting failed after oracle 11g upgarde (11.2.0.2)

    Hi Basis Expert,
    We have done oracle 11g ugrade (11.2.0.2) in our Dev BI system.
    But after the upgrade the RMAN backup is failing. The backup use to work fine when we were on 10g (10.2.0.4).
    Has anyone face this issue earlier.
    Appreciate your help.
    Regards,
    Anil Shenoy

    Hello Anil,
    Syntax is -
    ln -s /path/to/original/ /path/to/linkName
    Output will be -
    linkName --> original
    In your case, 112_64 is the link name according to above SAP Note and 11202 is the original/physical path. So, the command should be -
    ln -s /oracle/<DBSID>/11202 /oracle/<DBSID>/112_64
    And the Result should be, 112_64 --> 11202 (in short)
    So, I think you should change the existing link, 11202->112_64
    Thanks

  • RMAN Can't Backup 11g Database

    I'm using Oracle 11.2.0.1 Enterprise Edition and I've enabled my DBMS to run in ARCHIVELOG mode as shown below:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> archive log list;
    Database log mode     Archive Mode
    Automatic archival     Enabled
    Archive destination     USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 1614
    Next log sequence to archive 1616
    Current log sequence     1616
    So now that I have my DBMS running in ARCHIVELOG mode, I've also configured my (FRA) or 'Fast Recovery Area' as shown below:
    SQL> show parameter recovery_file_dest;
    NAME                    TYPE     VALUE
    db_recovery_file_dest          string     /oracle/u01/app/oracle/backup
    db_recovery_file_dest_size     big integer 10G
    Now I know I need to backup a few things in order to make sure I can recover from a complete disaster but what those items are, I'm still very unclear. Does anyone have a command that now will allow me to backup the entire database and everything I would possible need to either rebuild this database on another machine or from scratch? Can anyone please explain what I need and what exactly the file does and why I need it? For example...
    connected to target database: CQDB (DBID=1854033249)
    RMAN> BACKUP database PLUS archivelog delete input;
    database = ?
    archivelog = ?
    delete input = ?
    How do I get the redo logs, control file, and spfile? Do I need those to recover every time I do a backup or just one a month is fine?

    Hello again
    ---FRA---( sorry I missed part of this )----------------------------------------
    If you have free space :
    PRIMARY >sqlplus "/ as sysdba"
    SQL> show parameter db_recovery_file_dest_size
    SQL> alter system set db_recovery_file_dest_size=22G scope=both;
    So if you have free space add a few GB to get you by.
    The check you FRA space using
    SQL> set linesize 200
    SQL> column FILE_TYPE format a20
    SQL> select * from v$flash_recovery_area_usage;
    This should show the breakdown in FRA, assuming most of the space is ARCHIVE and backup the script below
    will handle them first in - first out
    Look around and see if there's an RMAN scipt about and if it uses a CATALOG.
    ---FRA--------------------------------------------------------------------------
    What I do ( on Linux ) is this
    #!/bin/bash
    # Name: db_rman_full.sh
    # Purpose: Database rman backup
    # Usage : db_rman_full <DBNAME>
    if [ "$1" ]
    then DBNAME=$1
    else
    echo "basename $0 : Syntax error : use . db_rman_full <DBNAME> "
    exit 1
    fi
    . /u01/app/oracle/dba_tool/env/${DBNAME}.env
    echo "Starting RMAN..."
    $ORACLE_HOME/bin/rman target / catalog rma/<password>@orcl << EOF
    run { allocate channel d1 type disk;
    backup full as compressed backupset
    database plus archivelog;}
    delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-11';
    DELETE noprompt BACKUP COMPLETED BEFORE 'SYSDATE-2' DEVICE TYPE DISK;
    exit
    EOF
    echo `date`
    #So I use a CATALOG database, I can show NOCATALOG if you need that too.
    As you can see I delete old backup and archive ( after they go to tape ). So I do disk first then tape.
    Change these as need and you can use CONFIGURE to do additional setup if you wish. SHOW ALL is your friend.
    And I use the crontab to start daily
    00 16 * * 0-6 /u01/app/oracle/dba_tool/bin/db_rman_full.sh ORCL > /tmp/rmanfull.outFor NOCATALOG - edit as needed - and replace in the script sample.
    $ORACLE_HOME/bin/rman target sys/<password> nocatalog << EOFAs you can see I setup an .env for each database that holds the following variables : ( using Red Hat 5 AS U7 )
    ORACLE_BASE=/u01/app/oracle
    ULIMIT=unlimited
    ORACLE_SID=PRIMARY
    ORACLE_HOME=$ORACLE_BASE/product/11.2.0.2
    ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
    LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
    LIBPATH=$LD_LIBRARY_PATH:/usr/lib
    TNS_ADMIN=$ORACLE_HOME/network/admin
    PATH=$ORACLE_HOME/bin:$ORACLE_BASE/dba_tool/bin:/bin:/usr/bin:/usr/ccs/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:/usr/lbin:/GNU/bin/make:/u01/app/oracle/dba_tool/bin:/home/oracle/utils/SCRIPTS:/usr/local/bin:.
    export TERM=vt100
    export ORACLE_BASE ORACLE_SID ORACLE_TERM ULIMIT
    export ORACLE_HOME
    export LIBPATH LD_LIBRARY_PATH ORA_NLS33
    export TNS_ADMIN
    export PATHBest Regards
    Edited by: mseberg on Feb 20, 2012 12:29 PM
    Edited by: mseberg on Feb 20, 2012 12:52 PM

  • Can we restore oracle 11g RMAN backups to 10g server

    Hi,
    I have RMAN backups (full backup)of oracle 11g database. My server was suddenly crashed due to hardware failure.
    We have another Oracle 10g server. Is it possible to restore RMAN backups of 11g database to Oracle 10g server???
    Thanks

    I don't have 11g server ready with me. The other server running oracle 10g and I dont have rights to install oracle 11g on the 10g server. So I can not test the RESTORE/RECOVER commands.
    If anyone had experience in the past, please let me know whether we can RESTORE RMAN backups of 11g database to oracle 10g server...
    Thanks

  • Setting up new dbname/sid while creating oracle db from rman backups in 11g

    Hi all,
    I have rman backups and need to create another database from rman backups with different name... but it is unsuccessful..
    created instance with new db...
    running create new db connecting rman auxiliary sys/password@newdb
    run {
    SET NEWNAME FOR DATAFILE 1 TO 'F:\app\HOME\oradata\clonedb1\SYSTEM01.DBF';
    SET NEWNAME FOR DATAFILE 2 TO 'F:\app\HOME\oradata\clonedb1\SYSAUX01.DBF';
    SET NEWNAME FOR DATAFILE 3 TO 'F:\app\HOME\oradata\clonedb1\UNDOTBS01.DBF';
    SET NEWNAME FOR DATAFILE 4 TO 'F:\app\HOME\oradata\clonedb1\USERS01.DBF';
    SET NEWNAME FOR DATAFILE 5 TO 'F:\app\HOME\oradata\clonedb1\EXAMPLE01.DBF';
    SET NEWNAME FOR TEMPFILE 1 TO 'F:\app\HOME\oradata\clonedb1\TEMP01.DBF';
    DUPLICATE DATABASE TO clonedb
    pfile 'D:\TESTDELETE\initclonedb1.ora'
    BACKUP LOCATION 'F:\app\HOME\flash_recovery_area\orcl\'
    LOGFILE GROUP 1 ('F:\APP\HOME\ORADATA\ORCL\REDO01.LOG') SIZE 60M REUSE,
    GROUP 2 ('F:\APP\HOME\ORADATA\ORCL\REDO02.LOG.rdo') SIZE 60M REUSE,
    GROUP 3 ('F:\APP\HOME\ORADATA\ORCL\REDO03.LOG') SIZE 60M REUSE;
    Error it shown is in rman backup creation is as follows
    <part>>
    sql statement: alter system set db_name = ''ORCL'' comment= ''Modified by RMAN
    duplicate'' scope=spfile
    Oracle instance shut down
    Oracle instance started
    Total System Global Area 640286720 bytes
    Fixed Size 1376492 bytes
    Variable Size 314576660 bytes
    Database Buffers 318767104 bytes
    Redo Buffers 5566464 bytes
    Starting restore at 20-DEC-11
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=133 device type=DISK
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:07
    output file name=F:\APP\HOME\ORADATA\CLONEDB1\CONTROL01.CTL
    output file name=F:\APP\HOME\FLASH_RECOVERY_AREA\CLONEDB1\CONTROL02.CTL
    Finished restore at 20-DEC-11
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 12/20/2011 07:07:11
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01102: cannot mount databa
    se in EXCLUSIVE mode
    RMAN> EXIT
    how can i prevent rman setting db_name=orcl which is already exists in the db.. i need to create db from rman backups with different dbname...
    whould someone help me out, how can i create database from another database rman backups with different dbname/sid on same host..
    My pfile has new db_name , but while db creation rman setting to db_name to source dbname.. it should be new db name that i want create with new db name...
    is there any RMAN command to specify new DB name it should set while running
    sql statement: alter system set db_name = newdbname -- as part rman script execution...
    it appears to be i should not touch the soruce db.. i have access to only source db rman backups and need to create another db with different dbname/sid.. please do help...

    When you performing RMAN duplicate why you making your script so complicated?
    Your instance name and DB name can be different, But what is the contents in your pfile "D:\TESTDELETE\initclonedb1.ora" ? please do post
    Have you started any other services related to ORACLE? check in start --> run --> services.msc any other active oracles services, Make sure you have clonedb1.
    Startup in nomount
    check the connectivity to target server.
    SET NEWNAME FOR TEMPFILE 1 TO 'F:\app\HOME\oradata\clonedb1\TEMP01.DBF';Why you mentioning SET NEWNAME FOR DATAFILE ? You have option of db_file_name_convert/log_file_name_convert in case if your file system different in Target & auxiliary.
    BACKUP LOCATION 'F:\app\HOME\flash_recovery_area\orcl\'When you have backup in same location why you are mentioning this clause?
    First run duplicate from auxiliary server as
    rman target sys/*****@prod auxiliary /
    RMAN> duplicate target database to "db_name";
    Am not sure what you are trying to do. is it 11gR1 or 11gR2?
    You have option of duplicate from active database without having backup also..
    here some links please check it.
    http://docs.oracle.com/cd/E14072_01/backup.112/e10642/rcmdupdb.htm#BGBFDJHB
    RMAN 11GR2 : DUPLICATE WITHOUT CONNECTING TO TARGET DATABASE [ID 874352.1]
    knowledgespring      
         Newbie
    Handle:      knowledgespring
    Status Level:      Newbie (10)
    Registered:      Dec 26, 2007
    Total Posts:      243
    Total Questions:      77 (75 unresolved)
    So sad that forum was able to help only in two answers out of your 77 questions :(
    Edited by: CKPT on Dec 21, 2011 5:12 PM

  • 10g RMAN backup in 11g

    Hi all,
    1. Have installed 11.1.0.1 and upgraded that to 11.2.0.1. Have taken a cold rman golden backup of database files without any data.
    2. Now doing a cloning to another server. Copied the oracle home 11.2.0.1.
    3.Unfortunately the datafiles backup mountpoint got corrupted and lost the cold rman backup files.
    4. Is that clone of 11.1.0.1 datafiles to 11.2.0.1 oracle home can be done??
    baskar.l

    1. Have installed 11.1.0.1 and upgraded that to 11.2.0.1. Have taken a cold rman golden backup of database files without any data.What does golden backup of database files..
    2. Now doing a cloning to another server. Copied the oracle home 11.2.0.1.
    3.Unfortunately the datafiles backup mountpoint got corrupted and lost the cold rman backup files.
    4. Is that clone of 11.1.0.1 datafiles to 11.2.0.1 oracle home can be done??what you are trying to do clone of 11.1 datafiles to 11.2 oracle home...
    do you mean are you looking to use 11.1 database in 11.2 oracle home? if so you need to upgrade database..
    Thanks

  • Can not recover table from rman backup

    For testing I want to recover deleted table from rman backup.
    I have make vm of oracle 11g.  the following step i have applied but could not recover the table.
    rman> backup database ;
    On sqlplus create login as scott/tiger
    create table scott.emp1(col1 varchar2(10));
    insert into emp1(col1) value('Yasir ') ;
    commit ;
    select * from emp1 ;
    it shows me one row successfully.
    Now i have login the  sys as sysdba
    sqlplus> alter system switch logfile ;
    after this i have drop the table .
    Now to recover the table i have restored database on same vm.
    rman>restore database ;
    rman> recover database ;
    rman> alter database open ;
    on sqlplus i have issued
    sqlplus> select * from scott.emp1 ;
    table or view does not exist.
    any help how to recover the deleted table from rman backup

    Hi,
    Check this test case
    SQL> create table TEST2 as select * from emp;
    Table created.
    SQL> select count(*) from TEST2;
      COUNT(*)
            15
    SQL> select TO_CHAR(SYSDATE,'DD-MON-YYYY HH24:MI:SS') from dual;
    TO_CHAR(SYSDATE,'DD-
    10-SEP-2013 10:57:05
    SQL> alter system switch logfile;
    System altered.
    SQL> drop table TEST2 purge;
    Table dropped.
    SQL> shu immediate
    [oracle@vnode MYSHELL]$ rman target /
    Recovery Manager: Release 11.2.0.2.0 - Production on Tue Sep 10 10:58:39 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: DDTEST (DBID=1667776968, not open)
    RMAN> run{
    set until time "to_date('2013 Sep 10 10:57','yyyy mon dd hh24:mi')";
    restore database;
    recover database;
    alter database open resetlogs;
    }2> 3> 4> 5> 6>
    media recovery complete, elapsed time: 00:00:02
    Finished recover at 10-SEP-13
    database opened
    RMAN> exit
    SQL> set lin 200 pages 100
    SQL> select count(*) from test2;
      COUNT(*)
            15
    HTH

  • RMAN backup and restore for Disaster Recovery

    Hi Guys,
    I am very new to Oracle and have a question about RMAN backup and restore feature. I am simulating a disaster recovery scenario by having two VMs running oracle 11g, say hosta and hostb, hosta is sort of production db and the other a disaster recovery db (one that will be made primary when disaster occurs). My goal is to backup production db using RMAN and restore it on the other machine. For some reason when I restore the db on hostb, the command restores the previous backup but not the most recent one e.g. I took a backup yesterday (09/20) and applied it to the hostb that worked fine, but when I try to apply a fresh backup from today (09/21) it always picks up the old backup. Here's a dump of the screen:
    Starting restore at 21-SEP-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to /oracle/app/dev/oradata/forums/s
    ystem01.dbf
    channel ORA_DISK_1: restoring datafile 00002 to /oracle/app/dev/oradata/forums/s
    ysaux01.dbf
    channel ORA_DISK_1: restoring datafile 00003 to /oracle/app/dev/oradata/forums/u
    ndotbs01.dbf
    channel ORA_DISK_1: restoring datafile 00004 to /oracle/app/dev/oradata/forums/u
    sers01.dbf
    channel ORA_DISK_1: reading from backup piece /oracle/app/dev/flash_recovery_are
    a/FORUMS/backupset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp
    channel ORA_DISK_1: piece handle=/oracle/app/dev/flash_recovery_area/FORUMS/back
    upset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp tag=TAG20110920T040950
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:05
    Finished restore at 21-SEP-11
    Notice that it reads the backup piece from this location /oracle/app/dev/flash_recovery_are
    a/FORUMS/backupset/
    whereas my latest backups are stored at a different location.
    I am executing following steps at the RMAN prompt on hosta and hostb:
    hosta (production site)
    backup as compressed backupset database plus archivelog
    backup current controlfile format'/oracle/oracle_bkup/ctl_%U'
    backup spfile
    hostb (Disaster site)
    set dbid=13732232063
    startup force nomount
    restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/2011_09_21/o1_mf_nnsnf_TAG20110921T114945_77ndg9ys_.bkp'
    shutdown immediate
    /* create a init<db_name>.ora file with SPFILE= /oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora */
    startup force pfile='/export/home/dev/restore_db/initforums.ora' nomount
    restore controlfile from '/export/home/dev/restore_db/backupset/2011_09_21/ctl_1hmn3mic_1_1'
    /* restart rman here */
    quit
    alter database mount;
    catalog start with '/export/home/dev/restore_db/backupset/2011_09_21' noprompt;
    /* call the next two commands on run */
    restore database;
    recover database;
    alter database open resetlogs
    quit
    Any help will be greatly appreciated.
    Thanks,
    Rajesh

    Thanks guys, I really appreciate all your help here. I redid everything all over again to get all the information you guys wanted. Since I noticed that more eyes are looking into this I am going to reiterate my steps one more time followed by specific answers to questions. My first backup on Host B is located under ..../restore_db/backupset whereas the subsequent one is under .../restore_db/backupset/backupset2.
    I take backup on Host A using:
    rman target /
    backup as compressed backupset database plus archivelog;
    backup spfile;
    quit;
    I restore the backup on Host B using:
    set dbid=13732232063;
    startup force nomount;
    restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/o1_mf_nnsnf_TAG20110928T171830_787gbpxh_.bkp'
    shutdown immediate;
    startup force nomount;
    restore controlfile from '/export/home/dev/restore_db/backupset/o1_mf_ncsnf_TAG20110928T171638_787gbkxn_.bkp'
    quit;
    /* restart rman here */
    alter database mount;
    catalog start with '/export/home/dev/restore_db/backupset' noprompt;
    restore database;
    recover database;
    alter database open resetlogs;
    quit;
    I take another backup on Host A using (notice no spfile backup this time):
    backup as compressed backupset database plus archivelog;
    quit;
    I restore the database on Host B using:
    alter database mount;
    catalog start with '/export/home/dev/restore_db/backupset/backupset2' noprompt;
    recover database;
    alter database open;
    quit;
    Output of List Backup of database (I have done this after I recovered the second time, also note that it is referring to backupset2 which is were my second backup is stored)
    RMAN> list backup of database;
    using target database control file instead of recovery catalog
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    89 Full 261.87M DISK 00:01:37 28-SEP-11
    BP Key: 91 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
    Piece Name: /export/home/dev/restore_db/backupset/o1_mf_nnndf_TAG2011092
    8T171638_787g77rx_.bkp
    List of Datafiles in backup set 89
    File LV Type Ckp SCN Ckp Time Name
    1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
    2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
    3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
    4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    97 Full 259.16M DISK 00:00:00 28-SEP-11
    BP Key: 100 Status: AVAILABLE Compressed: YES Tag: TAG20110928T18352
    7
    Piece Name: /export/home/dev/restore_db/backupset/backupset2/o1_mf_nnndf
    TAG20110928T183527787lv0nb_.bkp
    List of Datafiles in backup set 97
    File LV Type Ckp SCN Ckp Time Name
    1 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
    2 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
    3 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
    4 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
    Output of list backup (done after restoring the control file)
    RMAN> list backup;
    BS Key Size Device Type Elapsed Time Completion Time
    87 89.20M DISK 00:00:26 28-SEP-11
    BP Key: 87 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
    Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
    _28/o1_mf_annnn_TAG20110928T171526_787g50bm_.bkp
    List of Archived Logs in backup set 87
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 34 1302253 20-SEP-11 1306439 20-SEP-11
    1 35 1306439 20-SEP-11 1307647 20-SEP-11
    1 36 1307647 20-SEP-11 1307701 20-SEP-11
    1 37 1307701 20-SEP-11 1311393 20-SEP-11
    1 38 1311393 20-SEP-11 1311511 20-SEP-11
    1 39 1311511 20-SEP-11 1332479 20-SEP-11
    1 40 1332479 20-SEP-11 1344418 20-SEP-11
    1 41 1344418 20-SEP-11 1350409 20-SEP-11
    1 42 1350409 20-SEP-11 1350449 20-SEP-11
    1 43 1350449 20-SEP-11 1350854 21-SEP-11
    1 44 1350854 21-SEP-11 1350895 21-SEP-11
    1 45 1350895 21-SEP-11 1353114 21-SEP-11
    1 46 1353114 21-SEP-11 1353254 21-SEP-11
    1 47 1353254 21-SEP-11 1353865 21-SEP-11
    1 48 1353865 21-SEP-11 1353988 21-SEP-11
    1 49 1353988 21-SEP-11 1375403 21-SEP-11
    1 50 1375403 21-SEP-11 1376149 21-SEP-11
    1 51 1376149 21-SEP-11 1376206 21-SEP-11
    1 52 1376206 21-SEP-11 1376246 21-SEP-11
    1 53 1376246 21-SEP-11 1379990 21-SEP-11
    1 54 1379990 21-SEP-11 1380229 21-SEP-11
    1 55 1380229 21-SEP-11 1380266 21-SEP-11
    1 56 1380266 21-SEP-11 1380528 21-SEP-11
    1 57 1380528 21-SEP-11 1380724 21-SEP-11
    1 58 1380724 21-SEP-11 1380861 21-SEP-11
    1 59 1380861 21-SEP-11 1381033 21-SEP-11
    1 60 1381033 21-SEP-11 1381077 21-SEP-11
    1 61 1381077 21-SEP-11 1402243 22-SEP-11
    1 62 1402243 22-SEP-11 1423341 22-SEP-11
    1 63 1423341 22-SEP-11 1435456 22-SEP-11
    1 64 1435456 22-SEP-11 1454415 23-SEP-11
    1 65 1454415 23-SEP-11 1490903 23-SEP-11
    1 66 1490903 23-SEP-11 1491266 23-SEP-11
    1 67 1491266 23-SEP-11 1491347 23-SEP-11
    1 68 1491347 23-SEP-11 1492761 23-SEP-11
    1 69 1492761 23-SEP-11 1492891 23-SEP-11
    1 70 1492891 23-SEP-11 1493678 23-SEP-11
    1 71 1493678 23-SEP-11 1493704 23-SEP-11
    1 72 1493704 23-SEP-11 1494741 23-SEP-11
    1 73 1494741 23-SEP-11 1494790 23-SEP-11
    1 74 1494790 23-SEP-11 1510154 23-SEP-11
    1 75 1510154 23-SEP-11 1514286 23-SEP-11
    1 76 1514286 23-SEP-11 1531967 24-SEP-11
    1 77 1531967 24-SEP-11 1543266 24-SEP-11
    1 78 1543266 24-SEP-11 1558427 24-SEP-11
    1 79 1558427 24-SEP-11 1566924 24-SEP-11
    1 80 1566924 24-SEP-11 1578292 24-SEP-11
    1 81 1578292 24-SEP-11 1596894 25-SEP-11
    BS Key Size Device Type Elapsed Time Completion Time
    88 84.03M DISK 00:00:30 28-SEP-11
    BP Key: 88 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
    Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
    _28/o1_mf_annnn_TAG20110928T171526_787g63s9_.bkp
    List of Archived Logs in backup set 88
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 82 1596894 25-SEP-11 1609028 25-SEP-11
    1 83 1609028 25-SEP-11 1622303 25-SEP-11
    1 84 1622303 25-SEP-11 1626430 25-SEP-11
    1 85 1626430 25-SEP-11 1634486 25-SEP-11
    1 86 1634486 25-SEP-11 1648398 25-SEP-11
    1 87 1648398 25-SEP-11 1669259 26-SEP-11
    1 88 1669259 26-SEP-11 1686820 26-SEP-11
    1 89 1686820 26-SEP-11 1686959 26-SEP-11
    1 90 1686959 26-SEP-11 1689168 26-SEP-11
    1 91 1689168 26-SEP-11 1704759 26-SEP-11
    1 92 1704759 26-SEP-11 1719597 27-SEP-11
    1 93 1719597 27-SEP-11 1740407 27-SEP-11
    1 94 1740407 27-SEP-11 1750125 27-SEP-11
    1 95 1750125 27-SEP-11 1765592 27-SEP-11
    1 96 1765592 27-SEP-11 1781498 28-SEP-11
    1 97 1781498 28-SEP-11 1802311 28-SEP-11
    1 98 1802311 28-SEP-11 1811009 28-SEP-11
    1 99 1811009 28-SEP-11 1813811 28-SEP-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    89 Full 261.87M DISK 00:01:37 28-SEP-11
    BP Key: 89 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
    Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
    _28/o1_mf_nnndf_TAG20110928T171638_787g77rx_.bkp
    List of Datafiles in backup set 89
    File LV Type Ckp SCN Ckp Time Name
    1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
    2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
    3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
    4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf

  • Restore RMAN Backup

    Dear All,
    I am practicing Oracle Restore scenarios on my Oracle 9i database. Once I complete my tests in Oracle 9i I will move up to 10g and then finally to 11g.
    Following is my recovery scenario:
    1) I did NOT configure Recovery Catalog
    2) I would like to restore my databse from a 15 days old backup
    3) control_file_record_keep_time is set to 7 days.
    4) Backups are on tape.
    Can you guys please shed some light on how to I proceed?
    - P

    In oracle 9i , check , which situation you can perform complete recovery and in which situations you have to select incomplete recovery.
    check the notes by Alejandro Vargas, BACKUP AND RECOVERY SCENARIOS
    http://www.google.co.in/#hl=en&q=oracle+backup+and+recovery+scenarios&aq=0&aqi=g10&aql=&oq=oracle+backup+and+reco&gs_rfai=&fp=aa24f2b3591f5f42
    [PDF]
    Backup and Recovery Scenarios - Backup & Recovery Check List
    - 4:11am
    File Format: PDF/Adobe Acrobat - Quick View
    Oracle Support Israel. User Managed Recovery Scenarios And Configuration .... 4. recover automatic database using backup controlfile; ...
    static7.userland.com/oracle/gems/.../BackupAndRecoveryChecklist.pdf
    refer this, this will helps you.
    Can one restore RMAN backups without a CONTROLFILE and RECOVERY CATALOG?_
    http://www.orafaq.com/wiki/Oracle_database_Backup_and_Recovery_FAQ#Can_one_restore_RMAN_backups_without_a_CONTROLFILE_and_RECOVERY_CATALOG.3F
    Edited by: rajeysh on Jun 20, 2010 6:36 PM

  • Standby database using rman backup

    I'm using oracle11g on my work place and now i wont to create duplicate database using rman backup.
    at the time i installed only oracle 11g software.
    Pls guide me to overcome the problem. i'm newcomer to oracle.
    Pls give the steps.
    Edited by: user10444101 on Apr 30, 2010 2:17 AM

    user10444101 wrote:
    I'm using oracle11g on my work place and now i wont to create duplicate database using rman backup.
    at the time i installed only oracle 11g software.
    Pls guide me to overcome the problem. i'm newcomer to oracle.
    Pls give the steps.
    Edited by: user10444101 on Apr 30, 2010 2:17 AMSee the following link
    http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmdupdb.htm#i1008564

  • RMAN backup issue

    Oracle 11.2.0.1
    Windows 7 Home Premium
    RMAN> backup database;
    Starting backup at 05-MAR-12
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/05/2012 12:25:05
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    continuing other job steps, job failed will not be re-run
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 05-MAR-12
    channel ORA_DISK_1: finished piece 1 at 05-MAR-12
    piece handle=E:\APP\NISHA\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012_03_05\O1_MF_NCSNF_TAG20120305T122505_7O8RTBXJ_.BKP tag=TAG20120305T122505 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/05/2012 12:25:05
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    RMAN> 1.What is the problem in above scnerio ?
    2.How to take RMAN backup when db is down ?
    3.How to take RMAN backup when db is noarchivelog mode ?
    Please help me. Thank you.

    I am trying to do a full RMAN cold backup and am getting the following :
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    What’s the cause ?
    Here’s the example
    connected to target database (not started)
    Oracle instance started
    database mounted Total System Global Area 1610612736 bytes Fixed Size 2056504 bytes
    Variable Size 603983560 bytes
    Database Buffers 989855744 bytes
    Redo Buffers 14716928 bytes using target database control file instead of recovery catalog
    allocated channel: backup_disk1
    channel backup_disk1: sid=4977 instance=TEST1 devtype=DISK Starting backup at 31-OCT-13
    channel backup_disk1: starting full datafile backupset
    channel backup_disk1: specifying datafile(s) in backupset
    RMAN-03009: failure of backup command on backup_disk1 channel at 31/10/2013 20:18:45
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    continuing other job steps, job failed will not be re-run
    channel backup_disk1: starting full datafile backupset
    channel backup_disk1: specifying datafile(s) in backupset
    RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:45
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    continuing other job steps, job failed will not be re-run
    channel backup_disk1: starting full datafile backupset
    channel backup_disk1: specifying datafile(s) in backupset
    RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:46
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    continuing other job steps, job failed will not be re-run
    channel backup_disk1: starting full datafile backupset
    channel backup_disk1: specifying datafile(s) in backupset
    released channel: backup_disk1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:47
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    RMAN>
    The cause is simple, the database has not been shutdown cleanly. You will require to restart the database and shutdown again, if in a RAC you will have to shutdown all instances cleanly.
    Disabing archive log and attempting to backup the database will demonstrate the cause.
    SQL> startup force;
    ORACLE instance started.
    Total System Global Area 1235959808 bytes
    Fixed Size 2175288 bytes
    Variable Size 620760776 bytes
    Database Buffers 603979776 bytes
    Redo Buffers 9043968 bytes
    Database mounted.
    Database opened.
    SQL> shutdown abort;
    ORACLE instance shut down.
    SQL> startup mount;
    ORACLE instance started.
    Total System Global Area 1235959808 bytes
    Fixed Size 2175288 bytes
    Variable Size 620760776 bytes
    Database Buffers 603979776 bytes
    Redo Buffers 9043968 bytes
    Database mounted.
    SQL>
    Now we’ll try again to backup datafile 1.
    RMAN> backup datafile 1;
    Starting backup at 31-OCT-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=133 device type=DISK
    channel ORA_DISK_1: starting compressed full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 13/10/2013 20:43:34
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    This is simply because we issue a shutdown abort on the instance. However, just preforming a recovery will allow you to backup as required.
    SQL> recover database;
    Media recovery complete.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    C:UsersGary>rman target sys/passwd@db11g
    Recovery Manager: Release 11.2.0.1.0 – Production on Thu  Oct 31 20:44:15 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: DB10G (DBID=3002158372, not open)
    RMAN> backup datafile 1;
    Starting backup at 06-DEC-10using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1channel ORA_DISK_1: SID=125 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=00001 name=C:APPGARYORACLEPRODUCT10.2.0DB_1ORADATADB10GSYSTEM01.DBF
    channel ORA_DISK_1: starting piece 1 at 31-OCT-13
    channel ORA_DISK_1: finished piece 1 at 31-OCT-13
    piece handle=C:APPGARYORACLEPRODUCT10.2.0DB_1FLASH_RECOVERY_AREADB10GBACKUPSET2010_12_06O1_MF_NNNDF_TAG20101206T204423_6HTCR810_.BKP tag=TAG20101206T204423 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
    Finished backup at 31-OCT-13
    Starting Control File and SPFILE Autobackup at 31-OCT-13
    piece handle=C:APPGARYORACLEPRODUCT10.2.0DB_1FLASH_RECOVERY_AREADB10GAUTOBACKUP2010_12_06O1_MF_S_737066556_6HTCSQVF_.BKP comment=NONE
    Finished Control File and SPFILE Autobackup at 31-OCT-13
    RMAN> exit
    Interestingly, even with the recovery performed, we cannot switch back to archivelog mode without a clean shutdown.
    SQL> alter database archivelog;
    alter database archivelog*
    ERROR at line 1:ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-00264: no recovery required
    SQL> alter database archivelog;
    alter database archivelog*
    ERROR at line 1:ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
    So we’ll startup and shutdown again. You cannot use the force option since that still does not perform a normal shutdown and you’ll get the same error.
    SQL> alter database open;
    Database altered.
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount;
    ORACLE instance started.
    Total System Global Area 1235959808 bytes
    Fixed Size 2175288 bytes
    Variable Size 620760776 bytes
    Database Buffers 603979776 bytes
    Redo Buffers 9043968 bytes
    Database mounted.
    SQL> alter database archivelog;
    Database altered.
    SQL> alter database open;
    Database altered.

  • RMAN backup on RAC

    Hi,
    DB=10.2.0.4 OS=RHL (RAC with 2 nodes db01,db02). Following are the types of automated RMAN backups taken on db01.
    - OCR
    - Voting Disk
    - Talespaces Snapshot
    - Archivelog (every hour)
    - Backup Incremental level 0 (SUNDAY)
    -- backup incrementa level 1 (Mon-SAT)
    - Autobackup of Control file and SPFILE (CONTROLFILE AUTOBACKUP ON)
    Two main questions please. First, are these backups/backup types are enough FOR FULL RESTORE when talking about RMAN backup on RAC environment with 2 nodes? If not please suggest what else I need to backup?
    Secondly, backup home location is /rman which I can see on db01 ONLY. This /rman directory I cannot see on db02. My question is that In case of db02 failure can I restore from this /rman directory? or do I need to automate backup schedules also on db02 separately?
    [root@db01~]# df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/VolGroup00-LogVol00
                          3.9G  2.9G  814M  79% /
    /dev/sda3             190M   34M  147M  19% /boot
    tmpfs                  16G     0   16G   0% /dev/shm
    /dev/mapper/VolGroup00-LogVol05
                          3.9G  137M  3.6G   4% /home
    /dev/mapper/VolGroup00-LogVol03
                          3.9G  225M  3.5G   6% /tmp
    /dev/mapper/VolGroup00-LogVol02
                          7.8G  3.7G  3.8G  50% /usr
    /dev/mapper/VolGroup00-LogVol04
                          3.9G  379M  3.4G  11% /var
    /dev/mapper/VolGroup00-ORACLE_BASE
                           12G  8.7G  2.6G  78% /oracle
    10.10.28.140:/vol/px4cinconso
                           40G  1.4G   39G   4% /inconso_px
    /dev/mapper/36001ec9000d5ea810000061349015d98
                          1.3T  551G  665G  46% /rman
    [root@db02~]# df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/VolGroup00-LogVol00
                          3.9G  887M  2.9G  24% /
    /dev/sda3             190M   34M  147M  19% /boot
    tmpfs                  16G     0   16G   0% /dev/shm
    /dev/mapper/VolGroup00-LogVol05
                          3.9G  137M  3.6G   4% /home
    /dev/mapper/VolGroup00-LogVol03
                          3.9G  261M  3.5G   7% /tmp
    /dev/mapper/VolGroup00-LogVol02
                          7.8G  3.7G  3.8G  50% /usr
    /dev/mapper/VolGroup00-LogVol04
                          3.9G  355M  3.4G  10% /var
    /dev/mapper/VolGroup00-ORACLE_BASE
                           12G  6.5G  4.8G  58% /oracle
    10.10.28.140:/vol/px4cinconso
                           40G  1.4G   39G   4% /inconso_px
    [oracle@db01~]$ rman target /
    Recovery Manager: Release 10.2.0.5.0 - Production on Fri Feb 24 11:49:59 2012
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    connected to target database: F1 (DBID=1245145263)
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 28 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/f1/fullbackup/%F';
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
    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 ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_f11.f'; # default
    # Script for backup
    level0 ()
    run {
      allocate channel c1 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/fullbackup/$ORACLE_SID-data-%U-%t';
      allocate channel c2 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/archive/$ORACLE_SID-arch-%U-%t';
      backup incremental level 0 tag = weeklyfull database channel c1
      plus archivelog tag = ARCH_$TODAY delete all input channel c2;
      release channel c1;
      release channel c2;
    run {
      allocate channel c1 type disk;
      delete noprompt obsolete;
      release channel c1;
    }Bundle of thanks.
    Regards,
    Edited by: 910385 on Feb 24, 2012 3:00 AM

    Hi,
    THanks alot for your feedback. Makes my life easier :) . But actually I started studying this all subject because of the following error message in the log file. I found out about this error that doesn't seem to harm. Just wait for the job to finish or it will sort out automatically. Here are the lines from the log file.
    Fehler in Backuplogs gefunden:/oracle/log/fcp11-backup-2300.log: RMAN-00571:
    ===========================================================brRMAN-00569: ===============
    ERROR MESSAGE STACK FOLLOWS ===============brRMAN-00571:
    ===========================================================brRMAN-03009: failure of
    Control File and SPFILE Autobackup command on c1 channel at 02/08/2012
    06:10:41brORA-00230: operation disallowed: snapshot control file enqueue unavailableI studied few important lines from one of my book, Oracle 11g RMAN backup and recovery (Roberg G Freeman) that I am going to write after the following MAIN ISSUE:
    Node 1
    RMAN> show all;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_fp11.f'; # default
    Node 2
    RMAN> show all;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_fp12.f'; # default
    Thing which I just noticed regarding the above RMAN error is that snapcf_fp11.f can be seen on the Node 1 on todays date but snapcf_fp12.f was only on 10th jan.
    [oracle@db01dbs]$ ls -lrth
    -rw-r----- 1 oracle oinstall  20M Feb 27 15:10 snapcf_fcp11.f
    [oracle@db02dbs]$ ls -lrth
    -rw-r----- 1 oracle oinstall  20M Jan 10 13:28 snapcf_fcp12.fTHe few lines from the book which I mentioned above are: (Though you might not need to read those lines):
    "You need to move the snapshot control file to a shared location if you plan to run backups from more than one node. If you do not move the snapshot control file to a shared file system such as OCFS or an ASM disk group, then you must make sure that the local destination is identical on all nodes."
    My question is of course, how to sort out the above log file error. Becuse in our case, backups are run only from one node, and snaphost control file is not being moved to ASM disk groups. Local destination is also same on both the Nodes, isn't it (with different names). Why on Node 2 last snapshot was taken on 10th jan while on Node 1 it is todays date which seems fine.
    Control file and SPFILE which I noticed are stored on ASM disk groups also, so being shared between the two Nodes.
    (Sanme names/same location for control file and SPFILE on Node 1 and Node 2)
    Control file:
    +REDO1/fp1/controlfile/current.256.652803827
    +DATA1/fp1/controlfile/current.441.652869697
    SPFILE:
    +DATA1/fp1/spfilefcp1.oraPlease suggest.
    Thank you.
    Regards,
    Edited by: 910385 on Feb 27, 2012 7:43 AM

  • E-business Suite RMAN backup retention

    Hi,
    i want to retain my backup for clone for 90 days. One parameter need to set at RMAN level is CONFIGURE RETENTION POLICY TO REDUNDANCY 90;
    What other parameter need to set at DB level?
    Thanks

    i want to retain my backup for clone for 90 days. One parameter need to set at RMAN level is CONFIGURE RETENTION POLICY TO REDUNDANCY 90;
    What other parameter need to set at DB level?Rman backup retention policy [ID 462978.1]
    Oracle10g / 11g - Getting Started with Recovery Manager (RMAN) [ID 360416.1]
    RMAN : Consistent Backup, Restore and Recovery using RMAN [ID 162855.1]
    Backup and Recovery
    http://www.oracle.com/pls/db112/portal.portal_db?selected=4&frame=#backup_and_recovery
    Thanks,
    Hussein

  • Rman backup on physical standby database without cancelling MRP

    Hi all,
    Could anyone share, is this possible to take RMAN backup on physical standby database without cancelling MRP process.
    regarrds,

    Hi,
    On Standby Side:
    SQL> alter database mount;
    Database altered.
    SQL> alter database recover managed standby database using current logfile disconnect from session;
    Database altered.
    SQL> select max(Sequence#)  from v$archived_log;
    MAX(SEQUENCE#)
            405
    SQL> select max(Sequence#)  from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
            404
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@oel62-x64 Desktop]$ rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:31:43 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ADMDB (DBID=4063877183, not open)
    RMAN> backup database plus archivelog delete all input;
    Starting backup at 21-MAY-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=32 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=390 RECID=391 STAMP=815416638
    input archived log thread=1 sequence=391 RECID=392 STAMP=815421952
    input archived log thread=1 sequence=392 RECID=393 STAMP=815422343
    input archived log thread=1 sequence=393 RECID=394 STAMP=815422434
    input archived log thread=1 sequence=394 RECID=395 STAMP=815422570
    input archived log thread=1 sequence=395 RECID=396 STAMP=815476598
    input archived log thread=1 sequence=396 RECID=397 STAMP=815476615
    input archived log thread=1 sequence=397 RECID=398 STAMP=815476645
    input archived log thread=1 sequence=398 RECID=399 STAMP=815477471
    input archived log thread=1 sequence=399 RECID=400 STAMP=815477475
    input archived log thread=1 sequence=400 RECID=401 STAMP=815477628
    input archived log thread=1 sequence=401 RECID=403 STAMP=815584146
    input archived log thread=1 sequence=402 RECID=402 STAMP=815584137
    input archived log thread=1 sequence=403 RECID=405 STAMP=816017446
    *input archived log thread=1 sequence=404 RECID=404 STAMP=816017444*
    *input archived log thread=1 sequence=405 RECID=406 STAMP=816017455*
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T153202_8spm937d_.bkp tag=TAG20130521T153202 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_390_8s48hfrp_.arc RECID=391 STAMP=815416638
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_391_8s4fohwb_.arc RECID=392 STAMP=815421952
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_392_8s4g1q0v_.arc RECID=393 STAMP=815422343
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_393_8s4g4l8z_.arc RECID=394 STAMP=815422434
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_394_8s4g8t9h_.arc RECID=395 STAMP=815422570
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_395_8s631622_.arc RECID=396 STAMP=815476598
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_396_8s631qjj_.arc RECID=397 STAMP=815476615
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_397_8s632od8_.arc RECID=398 STAMP=815476645
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_398_8s63whqc_.arc RECID=399 STAMP=815477471
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_399_8s63wly4_.arc RECID=400 STAMP=815477475
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_400_8s641d8j_.arc RECID=401 STAMP=815477628
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_401_8s9d21jk_.arc RECID=403 STAMP=815584146
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_402_8s9d1skv_.arc RECID=402 STAMP=815584137
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_403_8spm6p4h_.arc RECID=405 STAMP=816017446
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_404_8spm6mqj_.arc RECID=404 STAMP=816017444
    RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc thread=1 sequence=405
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
    input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
    input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T153213_8spm9fnc_.bkp tag=TAG20130521T153213 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:02:15
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T153213_8spmfqxf_.bkp tag=TAG20130521T153213 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    Finished backup at 21-MAY-13
    RMAN> exit
    Recovery Manager complete.
    [oracle@oel62-x64 Desktop]$ sqlplus / as sysdba
    SQL*Plus: Release 11.2.0.3.0 Production on Tue May 21 15:34:42 2013
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
    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 max(Sequence#) from  v$archived_log;
    MAX(SEQUENCE#)
            405
    SQL> select max(Sequence#) from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
            404
    SQL> There have no problem, backup database when MRP is running. But if you want delete, then you are getting RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process.
    And will not delete this archived log, because it is needed for standby or upstream capture process.
    Updated
    When MRP stoped
    SQL> alter database recover managed standby database cancel;
    Database altered.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@oel62-x64 Desktop]$ rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:46:07 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ADMDB (DBID=4063877183, not open)
    RMAN> backup database plus archivelog delete all input;
    Starting backup at 21-MAY-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=24 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=405 RECID=406 STAMP=816017455
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154617_8spn3s9w_.bkp tag=TAG20130521T154617 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc RECID=406 STAMP=816017455
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
    input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
    input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154618_8spn3v4f_.bkp tag=TAG20130521T154618 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:16
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154618_8spn6779_.bkp tag=TAG20130521T154618 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    Finished backup at 21-MAY-13
    RMAN> Apply process is stopped and new redo received from primary.
    SQL> select max(Sequence#)  from v$archived_log;
    MAX(SEQUENCE#)
            407
    SQL> select max(Sequence#)  from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
            405
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@oel62-x64 Desktop]$ rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:49:28 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ADMDB (DBID=4063877183, not open)
    RMAN> backup database plus archivelog delete all input;
    Starting backup at 21-MAY-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=32 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=406 RECID=407 STAMP=816018527
    input archived log thread=1 sequence=407 RECID=408 STAMP=816018530
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154937_8spnb1y3_.bkp tag=TAG20130521T154937 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_406_8spn8hkn_.arc thread=1 sequence=406
    RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_407_8spn8l69_.arc thread=1 sequence=407
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
    input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
    input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154939_8spnb3f5_.bkp tag=TAG20130521T154939 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154939_8spndhly_.bkp tag=TAG20130521T154939 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    Finished backup at 21-MAY-13
    RMAN> I think, codes is understandable.
    Regard
    Mahir M. Quluzade
    Edited by: Mahir M. Quluzade on May 21, 2013 3:36 PM

  • Cannot make rman backup - ORA-19501

    Hello,
    database and grid infrastuture 11.2.0.1 in Solaris X86
    I am trying to make an rman backup of 2 databases located in ASM but when I try it I have the following error:
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 09/08/2011 15:38:04
    ORA-19501: read error on file "+DG/prd.dbf", block number 28544 (block size=8192)
    ORA-15081: failed to submit an I/O operation to a disk
    ORA-15081: failed to submit an I/O operation to a disk
    The alertlog of the database, when I run the rman has the following errors:
    ORA-27063: number of bytes read/written is incorrect
    WARNING: IO Failed. group:2 disk(number.incarnation):0.0xf0f2117f disk_path:/dev/rdsk/c5t60060480000290104585533031374538d0s6
    AU:7063 disk_offset(bytes):7406092288 io_size:1048576 operation:Read type:asynchronous
    result:I/O error process_id:14808
    WARNING: failed to read mirror side 1 of virtual extent 139 logical extent 0 of file 273 in group [2.4251116087] from disk DG001 allocation unit 7063 reason error; if possible,will try another mirror side
    ORA-15080: synchronous I/O operation to a disk failed
    WARNING: failed to write mirror side 1 of virtual extent 139 logical extent 0 of file 273 in group 2 on disk 0 allocation unit 7063
    My suspicious was problems with ASM but I have no errors in ASM. All disks are OK and the databases are working fine.
    I runned dbverify against the database datafiles and no problems at all.
    The problems seems like the Bug 9068033: RMAN BACKUP FAILED INTERMITTENT ORA-19501 ORA-2706, or bug 8510426 but I can't see any solution in metalink and this bug probably aplies to 10g and not 11g.
    Can you please help me out?
    Thank you.

    The errors look like problems in the I/O system, I don't think there's block corruption from Oracle's point of view. Nevertheless you may check which object owns block 28544 in datafile +DG/prd.dbf.
    select file_id from dba_data_files
    where file_name = '+DG/prd.dbf';
    SELECT SEGMENT_NAME, SEGMENT_TYPE
    FROM DBA_EXTENTS
    WHERE FILE_ID = <file_id from above>
    AND 28544 BETWEEN block_id AND block_id + blocks;
    It may be the block belongs to nothing, but there's still a physical defect. I remember a problem where RMAN complained about a bad block, but no issues in the database business. The reason no object owned this block, so the database did never access it.
    Werner

Maybe you are looking for