Backup from rman coldbackuk

DB 10.2.0.5
OS Linux
I restore the database from a rman cold backup. I am getting the below error while starting the database.
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
Is it needed to start the database in resetlog mode after rman cold backup restore.

Yes. RMAN does not backup the online redo log files. In order to open the database, the redo log files need to be created using the RESETLOGS option. Alternatively, you can use the OS to perform a backup of all files while the OS is shutdown, including the redo log files.

Similar Messages

  • DELETE ONLY 3 DAYS BACKUP FROM RMAN

    Hi,
    How we can delete only 3 days of backup from RMAN.
    Our retention policy is 15 days.
    Thanks in advance.

    Sounds like a strange requirement, but nonetheless, you could issue:
    RMAN> list backupset;and then find the backups that correspond to the days in question and then delete them with:
    RMAN> delete backupset <day3_backupset#>, <day5_backupset#>, <day7_backupset#>;

  • Removing RMAN backup files from RMAN prompt

    DB version: 10.2.0.4
    OS : AIX
    Due to space constraints, we had to change our retention policy today. So, i need to remove some old backup files manually to free up some space. Should i remove the backup files from OS using rm command and then issue a
    delete expired backup;from RMAN prompt?
    Or is there another recommended way?

    If you remove them manually from the O/S, then you'll have to perform a CROSSCHECK BACKUP prior to the DELETE EXPIRED.
    Or once you change your retention policy you could issue DELETE OBSOLETE, which may be the safer way to ensure you don't accidentally remove wrong backup files.

  • 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

  • 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

  • Restore spfile from rman backup ---- error.

    Hi,
    I am trying to execute recovery on new machine ...
    I have done the following steps..
    I have one database as ora10g2 as peroduction database on one machine as hosta
    I have created a catalog on another machine cora10g2 (hostb)
    I have taken a full backup from hosta as per following ...
    the following command execute from hosta machine.
    $ rman target sys/<passwd>@ora10g2 catalog rman/rman@cora10g2 ...
    Backup completed ...
    Now I am trying to restore this backup on hostb machine where i have already rman catlog database ..
    I have done the following setting ...on host b
    set oracle_sid=DUP
    and execute following command ...
    rman target / catalog rman/rman@cora10g2
    RMAN> set dbid 2760732370
    executing command: SET DBID
    database name is "BAAN10G2" and DBID is 2760732370
    RMAN>
    RMAN>
    RMAN> startup force nomount ;
    startup failed: ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file '/oracle/dbs/baan10g2/dbs/initbaan10g2.ora'
    starting Oracle instance without parameter file for retrival of spfile
    Oracle instance started
    Total System Global Area 159383552 bytes
    Fixed Size 1977112 bytes
    Variable Size 67114216 bytes
    Database Buffers 83886080 bytes
    Redo Buffers 6406144 bytes
    RMAN>
    RMAN>
    RMAN>
    RMAN> show all ;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/backup/control/cntrl_%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/baanora3/rman/ora10g2/bkup_db_%d_s%s_P%p_t%t' MAXPIECESIZE 1024;
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    RMAN>
    RMAN>
    RMAN> list backup of spfile ;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2420 Full 7.33M DISK 00:00:01 14-JUN-07
    BP Key: 2426 Status: AVAILABLE Compressed: NO Tag: TAG20070614T182935
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070614-00
    SPFILE Included: Modification time: 14-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2509 Full 7.33M DISK 00:00:01 15-JUN-07
    BP Key: 2515 Status: AVAILABLE Compressed: NO Tag: TAG20070615T130416
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-00
    SPFILE Included: Modification time: 15-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2694 Full 7.33M DISK 00:00:01 15-JUN-07
    BP Key: 2739 Status: AVAILABLE Compressed: NO Tag: TAG20070615T131703
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-01
    SPFILE Included: Modification time: 15-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2760 Full 80.00K DISK 00:00:01 15-JUN-07
    BP Key: 2763 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163437
    Piece Name: /rman/spfile/spfile.ora
    SPFILE Included: Modification time: 15-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2769 Full 7.33M DISK 00:00:02 15-JUN-07
    BP Key: 2771 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163441
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-02
    SPFILE Included: Modification time: 15-JUN-07
    RMAN>
    RMAN>
    RMAN> restore spfile from autobackup ;
    Starting restore at 19-JUN-07
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=36 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=35 devtype=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: sid=34 devtype=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: sid=33 devtype=DISK
    channel ORA_DISK_1: looking for autobackup on day: 20070619
    channel ORA_DISK_1: looking for autobackup on day: 20070618
    channel ORA_DISK_1: looking for autobackup on day: 20070617
    channel ORA_DISK_1: looking for autobackup on day: 20070616
    channel ORA_DISK_1: looking for autobackup on day: 20070615
    channel ORA_DISK_1: looking for autobackup on day: 20070614
    channel ORA_DISK_1: looking for autobackup on day: 20070613
    channel ORA_DISK_1: no autobackup in 7 days found
    channel ORA_DISK_2: looking for autobackup on day: 20070619
    channel ORA_DISK_2: looking for autobackup on day: 20070618
    channel ORA_DISK_2: looking for autobackup on day: 20070617
    channel ORA_DISK_2: looking for autobackup on day: 20070616
    channel ORA_DISK_2: looking for autobackup on day: 20070615
    channel ORA_DISK_2: looking for autobackup on day: 20070614
    channel ORA_DISK_2: looking for autobackup on day: 20070613
    channel ORA_DISK_2: no autobackup in 7 days found
    channel ORA_DISK_3: looking for autobackup on day: 20070619
    channel ORA_DISK_3: looking for autobackup on day: 20070618
    channel ORA_DISK_3: looking for autobackup on day: 20070617
    channel ORA_DISK_3: looking for autobackup on day: 20070616
    channel ORA_DISK_3: looking for autobackup on day: 20070615
    channel ORA_DISK_3: looking for autobackup on day: 20070614
    channel ORA_DISK_3: looking for autobackup on day: 20070613
    channel ORA_DISK_3: no autobackup in 7 days found
    channel ORA_DISK_4: looking for autobackup on day: 20070619
    channel ORA_DISK_4: looking for autobackup on day: 20070618
    channel ORA_DISK_4: looking for autobackup on day: 20070617
    channel ORA_DISK_4: looking for autobackup on day: 20070616
    channel ORA_DISK_4: looking for autobackup on day: 20070615
    channel ORA_DISK_4: looking for autobackup on day: 20070614
    channel ORA_DISK_4: looking for autobackup on day: 20070613
    channel ORA_DISK_4: no autobackup in 7 days found
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 06/19/2007 18:00:13
    RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
    RMAN>
    I am not able to restore spfile from rman backup ;;;

    Hi,
    I would like to know few things
    1. How are you setting the db_name ? you can set db_id at RMAN, how are you setting the db_name ?
    2. Do you have any default init file at default location ? if yes, is the db_name parameter set correctly in that file ?
    Since spfile is yet to be restored, you must set the db_name parameter correctly before you start spfile restore.This can be done with init file at default location which can even contain just one paremeter i.e db_name.

  • Undo tablespace recovery from RMAN backup

    Hi,
    Lets's assume we have RMAN backup and archivelog backups, and now
    my undo tablespace's disk crashed ,how can i recover?
    Can i recover while database is up?
    Thanks,
    Kumar.

    to recover UNDO tablespace from RMAN backup you must shutdown the database and start it in the MOUNT state to recover the missing files as follows
    rman target /
    RUN
    STARTUP MOUNT;
    ALLOCATE CHANNEL ch3 TYPE Disk;
    RESTORE datafile 'c:\u01\prod3\undo01.dbf';
    RECOVER datafile 'c:\u01\prod3\undo01.dbf';
    ALTER DATABASE OPEN;
    RELEASE CHANNEL ch3;
    hope this will help you

  • Restore RMAN backup from tape

    I have to restore the RMAN full backup from tape to new host to a previous date say March 1st. My target database RMAN retention period is 28 days, today is 11th May.
    Is it possible to restore the obsolete database from tape backup to new host as of May 1st. If not possible, I would like to restore the available backup say as 15th April from tape to new host.
    Can you please provide me the steps to restore the tape old backup to new host.
    Thanks,
    Mahi

    Can't read documentation? You also seem to be unable to mark questions as answered
    Mahi      
         Newbie
    Handle:      Mahi
    Status Level:      Newbie
    Registered:      Nov 24, 2010
    Total Posts:      24
    Total Questions:      15 (13 unresolved)
    Sybrand Bakker
    Senior Oracle DBA

  • Spfile restore from RMAN Tape backup to different server

    Hi All,
    First of all let me thank you to the forum from which I keep updating my knowledge on oracle.
    I am having issues when trying to restore spfile from controlfile autobackup to different server. Problem and other details are below:
    Target version : 10.2.0.2
    Netbackup : 6.5.6
    Taken the tape backup through rman on server ABC and trying to restore the spfile from controlfile autobackup to server XYZ. Tape backup has been taken today morning and trying restore now.
    Both servers ABC and XYX have been added (as clients) to netbackup policy.
    Below is the syntax I used for restoring spfile and getting error as mentioned.
    RMAN> run {
    2> set controlfile autobackup format for device type 'SBT_TAPE' to '%F';
    3> allocate channel ch00 device type 'sbt_tape'
    4> parms='ENV=(NB_ORA_SERV=Mediaserver,NB_ORA_CLIENT=XYZ)';
    5> restore spfile to pfile '/oracle/product/10g/dbs/inittest.ora' from
    6> autobackup maxseq 5 maxdays 3;
    7> }
    executing command: SET CONTROLFILE AUTOBACKUP FORMAT
    allocated channel: ch00
    channel ch00: sid=36 devtype=SBT_TAPE
    channel ch00: Veritas NetBackup for Oracle - Release 6.5 (2010042405)
    Starting restore at 03-AUG-2011
    channel ch00: looking for autobackup on day: 20110803
    channel ch00: looking for autobackup on day: 20110802
    channel ch00: looking for autobackup on day: 20110801
    channel ch00: no autobackup in 3 days found
    released channel: ch00
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 08/03/2011 14:03:26
    RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
    Not sure where I am doing wrong. The same can be restored onto same host (I.E ABC) without any issues .
    Request your help and guidance.
    Thanks,
    SSS

    I don't know whether you can restore to a different server. The easier way should be
    RMAN> restore spfile to pfile 'YOUR_PFILE_NAME' from autobackup;
    then copy this to the new host.
    Check this link
    restore spfile to another host
    Hope this helps

  • Creating Standby From RMAN Compressed backup taken on Primary ....

    I am creating a Standby from RMAN Compressed backup taken on Primary.
    On Primary, I have taken Compressed backup as follows:
    RMAN> run
    allocate channel c1 type disk;
    allocate channel c2 type disk;
    allocate channel c3 type disk;
    BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG format '/dboracle/orbit_pr_bkp/primary_%U';
    backup current controlfile for standby format '/dboracle/orbit_pr_bkp/primary_cntl.bkp';
    oracle@apl06635orbvu1:/dboracle/orbit_pr_bkp>ls -ltr
    total 51652
    -rw-r----- 1 oracle dba 11972608 Jan 7 13:45 primary_0tm1h32n_1_1
    -rw-r----- 1 oracle dba 15762432 Jan 7 13:45 primary_0sm1h32n_1_1
    -rw-r----- 1 oracle dba 16785920 Jan 7 13:45 primary_0rm1h32n_1_1
    -rw-r----- 1 oracle dba 1088000 Jan 7 13:45 primary_0um1h32v_1_1
    -rw-r----- 1 oracle dba 32768 Jan 7 13:45 primary_12m1h33r_1_1
    -rw-r----- 1 oracle dba 7143424 Jan 7 13:47 primary_cntl.bkp
    On Standby, I restored the control file as below:
    RMAN> restore standby controlfile from '/dboracle/orbit_pr_bkp/primary_cntl.bkp';
    Starting restore at 10-JAN-11
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
    output filename=/dboracle/orbit_dr/oradata/ORBIT_DR/controlfile/o1_mf_6lo6nwfr_.ctl
    output filename=/dboracle/orbit_dr/flash_recovery_area/ORBIT_DR/controlfile/o1_mf_6lo6nwky_.ctl
    Finished restore at 10-JAN-11
    But, When I am trying to restore the datafiles, RMAN is throwing error:
    RMAN> run {
    allocate channel d1 type disk format '/dboracle/orbit_pr_bkp/primary_%U';
    allocate channel d2 type disk format '/dboracle/orbit_pr_bkp/primary_%U';
    restore database;
    2> 3> 4> 5>
    released channel: ORA_DISK_1
    allocated channel: d1
    channel d1: sid=155 devtype=DISK
    allocated channel: d2
    channel d2: sid=151 devtype=DISK
    Starting restore at 10-JAN-11
    released channel: d1
    released channel: d2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 01/10/2011 05:38:56
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 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
    What would be the correct RMAN command?
    Regards, Anirban

    After your RESTORE the (standby) controlfile, you must MOUNT the database instance with "ALTER DATABASE MOUNT".
    You can also then query the controlfile with a "LIST BACKUP" or "LIST BACKUP SUMMARY" in RMAN to see if the deseired backups have been cataloged in the controlfile.
    Don't specify the format for the ALLOCATE CHANNEL when you RESTORE DATABASE. In fact, you don't need to ALLOCATE CHANNEL at all when the device type is the default value of DISK if your are on 10gR2 or above.
    Hemant K Chitale

  • Taking rman backup from a different server

    HI Al,
    Is it possible for us run the rman backup from a different server other than the server on which database exist .
    For Ex :
    Our database is on server X
    But , I want to schedulde the archive backup from the server Y .
    How can we do this and is it possible ...
    Regds
    Rahul Gupta

    Yes, as long the RMAN executable is compatible to the target database, on metalink:
    RMAN Compatibility Matrix
    Doc ID: 73431.1
    rman sys/<password>@<connect_string>
    Werner

  • RMAN backup from another DB server

    Hi all,
    I would like to know Can we take a rman backup from another DB server in oracle 9.2...
    i.e
    suppose that we have two server
    1. main server
    2. dup server
    I want to take a backup of main server throeugh dup server.....
    if it is poosible then what are all the things that i have to configure....
    pls suggest me.....

    getting an error,
    here hotest is the main db
    and testho is dup db
    F:\Documents and Settings\deepali>rman target rman/cat@hotest catalog rman/cat@testho
    Recovery Manager: Release 9.2.0.4.0 - Production
    Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.
    connected to target database: HOTEST (DBID=982176707)
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04004: error from recovery catalog database: ORA-01045: user RMAN lacks CRE
    ATE SESSION privilege; logon denied
    F:\Documents and Settings\deepali>sqlplus /nolog
    SQL*Plus: Release 9.2.0.4.0 - Production on Mon Apr 6 12:17:13 2009
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    SQL> conn sys/deepali as sysdba
    Connected.
    SQL>  GRANT RECOVERY_CATALOG_OWNER TO rman;
    Grant succeeded.
    SQL> GRANT CONNECT, RESOURCE TO rman;
    Grant succeeded.
    SQL> exit
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.4.0 - Production
    F:\Documents and Settings\deepali>rman target rman/cat@hotest catalog rman/cat@t
    estho
    Recovery Manager: Release 9.2.0.4.0 - Production
    Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.
    connected to target database: HOTEST (DBID=982176707)
    connected to recovery catalog database
    recovery catalog is not installed
    RMAN> register database;
    recovery catalog is not installed
    recovery catalog is not installed
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of register command at 04/06/2009 12:18:09
    RMAN-06429: RCVCAT database is not compatible with this version of RMAN
    RMAN> select * from rc_database;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01005: syntax error: found "identifier": expecting one of: "allocate, alter
    , backup, beginline, blockrecover, catalog, change, connect, copy, create, cross
    check, configure, duplicate, debug, delete, drop, exit, endinline, host, {, libr
    ary, list, mount, open, print, quit, recover, register, release, replace, report
    , renormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, s
    pool, startup, shutdown, send, show, test, upgrade, validate"
    RMAN-01008: the bad identifier was: select
    RMAN-01007: at line 1 column 1 file: standard input
    RMAN>pls suggest me whether i am following the right path or not...

  • Steps to restore RMAN backups from tape to disk

    Hi All,
    using Netbackup Veritas Volume
    DB:10.2.0.3.0
    OS:AIX 64 bit
    Could nayone please share the steps to - restore RMAN backups from tape to disk.
    An early reply would be appreciated!!
    Thanks for your time!
    Regards,

    Hi,
    I went through as per your action plan it is giving below error I found a solution on meta doc id 559190.1 but i am not able to understant how to start observiced as it is mentioned in the doc id.
    allocated channel: t1
    channel t1: sid=2386 devtype=SBT_TAPE
    channel t1: Data Protection for Oracle: version 5.4.1.0
    Starting restore at 09-MAY-10
    channel t1: looking for autobackup on day: 20100509
    released channel: t1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 05/09/2010 11:57:01
    ORA-27191: sbtinfo2 returned error
    Additional information: 2
    RMAN>
    Thanks,

  • How to estimate recovery time from rman backup

    how to estimate recovery time from rman backup?
    The database is of size 800GB.
    the approximate time to backup is 8- 10 hours.

    "Recovery time" is : RESTORE DATABASE time + RECOVER DATABASE time.
    RESTORE can be done
    a. in parallel with multiple channels if your backup was created as multiple backupsets
    b. using incremental backups
    c. whether the backups are on
    i. disk
    ii. tape
    Alternatively, if you have a Recovery Area with an Incrementally Update backup of the database, you can SWITCH DATABASE almost immediately
    RECOVER depends on
    a. how many archivelogs (in terms of size, not necessarily number) need to be applied
    -- this depends on
    i. transaction volume
    ii. the "freshness" of the backups (how recent the backups are)
    b. whether required archivelogs are available on disk (which can be the case if the database backup itself is a very recent backup and archivelogs since then haven't been deleted {whether they have been backed up or not}) OR whether they need to be restored from
    i. disk backup
    ii. tape backup

  • Completeness of Prerequisites for Recovering Tables for PDBs from RMAN Backups

    Could you verify the completeness of following prerequisities on pag. 441 of the "Backup and Recovery User's Guide 12c Release 1 (12.1) E17630-14"
    Prerequisites for Recovering Tables and Table Partitions from RMAN Backups
    ■ The target database must be in read-write mode.
    ■ The target database must be in ARCHIVELOG mode.
    ■ You must have RMAN backups of the tables or table partitions as they existed at the point in time to which you want recover these objects.
    ■ To recover single table partitions, the COMPATIBLE initialization parameter for target database must be set to 11.1.0 or higher.
    According to my test Database administrator workshop: How to recover a table in a pluggable database from a backup
    those prerequisities are valid for CDBs or non-CBDs, but if you want to recover tables or table partitions in PDBs a different prerequisite is needed.
    Indeed if you have a backup of only the pluggable database including the missing table (the third prerequisite above), but you don't have any backup of the container database the command...
    recover table ... of pluggable database ... until scn ... auxiliary destination ...
    will fail with the following errors:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 02/12/2014 12:22:18
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 3 found to restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    So to recover table in PDBs you must have also the RMAN backups of the CDB or in the opposite way it's not sufficient to have only the backups of the pluggable database, because during the creation of the auxiliary database the SYS, SYSAUX and the UNDO tablespace are required.
    Regards,
    MarcoV

    Hi,
    Before dropping a DB we had taken an RMAN backup.I hope you were in mount mode.
    Will RMAN automatically recognize the FORMAT of the backup piece and restore ?No it won't.
    First you have to restore a controlfile in nomount mode with:
    restore controlfile from '/u04/backup/rmanbkp /02mo9fnc_1_1';
    and do alter database mount.
    Than you have to run "catalog start with '/u04/backup/rmanbkp'; " so the instance now knows where to find the pieces.
    Now you can run a restore database command.
    Than open the database with resetlogs.
    Regards,
    Tycho

Maybe you are looking for