PARMS parameter in RMAN BACKUP Command

Hi,
I am planning to use Backup application “OMNIBACK”.
This application uses RMAN internally to manage the backups.
The backups will goes to tape.
I am concerned about the PARMS parameter, which can be used in RMAN Command Syntax to associate the tape drive.
What Value I provide to PARMS parameter (Omniback)?
For Example:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=
Thanks
Benazir

Thanks ,
Could you please inform me about the "OB2APPNAME=RMAN81T", which we can find in following command.
Should it mandatory to give the db name to this parameter?
As well as the following variables. Are these variable work?
s:%t:%p>.
Thanks
Benazir
run {allocate channel 'dev_0' type 'sbt_tape' parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=RMAN81T,OB2BARLIST=test_full)'; backup incremental level <incr_level> filesperset 1 format 'test_full<RMAN81T_%s:%t:%p>.dbf' database include current controlfile ; }

Similar Messages

  • Negative impact of RATE parameter in RMAN backups.. ?

    Hello all..
    Can u please tel me about the negative impact of rate parameter in RMAN backups.
    Thanks in advance,,
    Thanks & Regards
    Vinay Raj Malla

    Hi Jorgen,
    there's no rule of thumb, because every application is different, also the users behaviour...
    - every user needs an initial amount of memory while logged in (user context
    - then there comes the amount of memory while working with the application
    - then it depends if when for example a query is finished the memory gets freed up or if it will be held in memory
    - the behaviour of the user if he logs out correctly (memory is freed up) or just closes the browser (memory still in use until timeout occurs)
    So the best would be to simply monitor your system with SM04, there you can also click on GOTO -> MEMORY and you'll see the amount of memory for each user. Look what happens when a user works with the application and also what happens when a user closes the browser.
    Regards,
    Pascal
    PS: Please give points for usesful answers

  • Rman backup command hangs for datafile ,works with archivelogs backup.

    Issue is archivelogs backup is going fine ,But when we go for datafile backup its hanging there from oracle side as not able to give file handle.
    RMAN session started with debug it gives only
    DBGRPC: ENTERED krmqgns [expect.cpp/673]
    16:00:40.19 DBGRPC: krmqgns: looking for work for channel default (krmqgns) [expect.cpp/673]
    16:00:40.19 DBGRPC: krmqgns: commands remaining to be executed: (krmqgns) [expect.cpp/673]
    16:00:40.19 DBGRPC: CMD type=backup cmdid=1 status=STARTED [expect.cpp/673]
    16:00:40.19 DBGRPC: 1 STEPstepid=1 cmdid=1 status=STARTED [expect.cpp/673]
    16:00:40.19 DBGRPC: krmqgns: no work found for channel default (krmqgns) [expect.cpp/673]
    16:00:40.19 DBGRPC: (krmqgns) [expect.cpp/673]
    16:00:40.19 DBGRPC: EXITED krmqgns with status 1 [expect.cpp/673]
    16:00:40.19 DBGRPC: krmxpoq - returning rpc_number: 17 with status: STARTED16 for channel sqlbt_ch1 [expect.cpp/673]
    16:00:40.19 DBGRPC: krmxr - sleeping for 10 seconds [expect.cpp/673]
    Is any body seen this type of message from rman.
    Thanks
    Shirish

    OK. Did you miss the second Oracle document?
    RMAN Debug For Backup Shows "krmxr: sleeping for x seconds" [ID 458259.1]
    Also a ton of information here :
    RMAN backup database as copy from file system to ASM diskgroup very slow
    and here :
    RMAN Error > Please assist!
    and here :
    RMAN and Amazon Web Services
    http://oravdba.blogspot.com/2011_01_01_archive.html
    Best Regards
    mseberg

  • RMAN backup command

    hi
    In RMAN we have "backup database" and "backup as copy database"..in backup database,it stores the backup in .bkp format and in backup as copy database it stores the backup in .ctl, .dbf format..My question is which one is more effective and how we will decide which one to use...
    Thanks in advance..

    Backup as copy allows for faster recovery by allowing you to switch to a copy rather than restoring a backup. The copies usually take up more space though as they are not compressed in any way.
    Hope that helps,
    Regards,
    Iain Barr
    Ategrity Solutions Ltd

  • How to set the Rman backup parameter.

    Hi,
    Can U guide me how to set the Rman backup path,control file auto backup & others parameter.

    Hi,
    Go through this,
    Show all configurable settings:
    RMAN>SHOW ALL;
    Write disk backups to the /rmanback directory: (%U will be replaced with unique filenames)
    RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rmanback/%U';
    Backup using a flash recovery area rather than disk
    RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT CLEAR;
    Configure RMAN to back up the control file after each backup
    RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;
    By default, RMAN automatically names control file backups and stores them in the flashrecovery area.
    To configure RMAN to write control file backups to the /backup directory:( %F will generate a unique filename)
    RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/controlfile%F';
    Ensure that RMAN retains all backups needed to recover the database to any point in time in the last 7 days:
    RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    Retain three backups of each datafile:
    RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    Delete backups no longer required by the retention policy:
    RMAN> DELETE OBSOLETE;
    To override the configured retention policy for individual backups - use BACKUP.. KEEP (or CHANGE.. KEEP)
    Configure backups to run in parallel by assigning two sbt channels:
    RMAN> CONFIGURE DEVICE TYPE sbt PARALLELISM 2;
    Reset any CONFIGURE setting to its default by running the command with the CLEAR option
    RMAN> CONFIGURE CHANNEL DEVICE TYPE sbt CLEAR;
    RMAN> CONFIGURE RETENTION POLICY CLEAR;
    Regards,
    oraclekt
    Edited by: oraclekt on Sep 1, 2010 9:58 PM

  • How to pass parameter to RMAN command?

    Hi,
    When i am execute delete.sh file. the following error coming. it expecting to pass parameter YES or NO.
    How I can pass parameter to RMAN command in shell scripts.
    [oracle@dbNode1 rman]$ sh delete.sh
    Executing Command : Backup as copy to file system
    Recovery Manager: Release 10.2.0.3.0 - Production on Mon Apr 20 12:13:18 2009
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: HERMESQA (DBID=3819666523)
    connected to recovery catalog database
    RMAN> 2> 3>
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=135 devtype=DISK
    List of Backup Pieces
    BP Key BS Key Pc# Cp# Status Device Type Piece Name
    98 96 1 1 AVAILABLE DISK /u01/app/oracle/flash_recovery_area/HERMESQA/backupset/2009_03_17/o1_mf_ncnnf_TAG20090317T180639_4vz6bqkl_.bkp
    Do you really want to delete the above objects (enter YES or NO)?
    Error occurred getting response - assuming NO response
    thanks
    settu gopal

    Use
    DELETE NOPROMPT - then no questions will be asked.

  • Error while taking RMAN back up - RMAN-03009: failure of backup command ..

    Hi Experts,
    I am trying to take RMAN back up but at the end I get this error message.. I found a solution at http://www.oracle-base.com/articles/9i/RecoveryManager9i.php
    But this is of oracle 9i. Can I use it on 10g too ?
    So is this Step correct ?
    1) First create a user to hold the recovery catalog:
    a) CONNECT sys/password@w2k1 AS SYSDBA
    b) GRANT connect, resource, recovery_catalog_owner TO rman;
    2) Then create the recovery catalog:
    a) C:>rman catalog=rman/rman@w2k1
    b) RMAN> create catalog tablespace "RMAN";
    c) RMAN> exit
    3) Register Database
    a) C:>rman catalog=rman/rman@w2k1 target=sys/password@w2k2
    b) RMAN> register database;
    c) Existing user-created backups can be added to the catalog using: (*So far no Back up taken so I guess this step can be ignored*)
    i) RMAN> catalog datafilecopy 'C:\Oracle\Oradata\TSH1.dbf';
    ii) RMAN> catalog archivelog 'log1', 'log2', 'log3', ... 'logN';
    4) Full Backup Configuration
    RMAN> configure retention policy to recovery window of 7 days;
    RMAN> configure default device type to disk;
    RMAN> configure controlfile autobackup on;
    RMAN> configure channel device type disk format 'C:\Oracle\Admin\W2K2\Backup%d_DB_%u_%s_%p';
    5) Full back up
    RMAN> run {
    backup database plus archivelog;
    delete noprompt obsolete;
    6) RMAN> resync catalog;
    Starting backup at 15-MAY-10
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00006 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\DM_MENTOR200
    60430230208_DB.DBF
    input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\UNDOTBS01.DB
    F
    input datafile fno=00007 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\DM_MENTOR200
    60430230208_IND.DBF
    input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\SYSTEM01.DBF
    input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\SYSAUX01.DBF
    input datafile fno=00005 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\EXAMPLE01.DB
    F
    input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\USERS01.DBF
    channel ORA_DISK_1: starting piece 1 at 15-MAY-10
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/15/2010 05:11:
    03
    ORA-19809: limit exceeded for recovery files
    ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
    continuing other job steps, job failed will not be re-run
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    including current controlfile in backupset
    channel ORA_DISK_1: starting piece 1 at 15-MAY-10
    channel ORA_DISK_1: finished piece 1 at 15-MAY-10
    piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ZUMA\BACKUPSET\2010_05
    _15\O1_MF_NCNNF_TAG20100515T045136_5YX3TTFT_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:17
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup plus archivelog command at 05/15/2010 05:11:21
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/15/2010 05:11:
    03
    ORA-19809: limit exceeded for recovery files
    ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
    RMAN>
    Thanks & Regards,
    Ranjith John

    Provided you consult the 10g RMAN documentation and the online error documentation: yes.
    But apparently you didn't check documentation, not even the error messages!!!!! Why?
    You are backing up to the Flash Recovery Area, and the error messages mean too much space is occupied.
    How to configure the Flash Recovery Areea is fully documented in the Backup and Recovery manual for 10g at http://tahiti.oracle.com
    READ IT.
    Please do not ask a volunteer to abstract it.
    Sybrand Bakker
    Senior Oracle DBA

  • RMAN LIST BACKUP COMMAND

    I am using the following commands.
    RMAN> sql "alter session set nls_date_format=''dd-mon-yyyy HH24:MI:SS''";
    2> report unrecoverable database;
    3> report need backup days 2 database;
    4> list backup;
    5> EXIT;
    BS Key Type LV Size Device Type Elapsed Time Completion Time------- ---- -- ---------- ----------- ------------ ---------------
    6249525 Full 68G SBT_TAPE 01:38:05 *25-OCT-2010*
    BP Key: 6249547 Status: AVAILABLE Tag: TAG20101025T040741
    Even after setting nls_date_format, completion time in list backup command is not returning exact time..it is returning just the date..
    how to get completion time in RMAN LIST BACKUP COMMAND with hour,minute and second details...please let me know
    I am using catalog database...target database version 9i and catalog db version is 10g.
    Thanks,
    db

    NLS_DATE_FORMAT at OS level
    I tied this export NLS_DATE_FORMAT=DD-MON-YYYY HH24:MI:SS is throwing error
    NLS_DATE_FORMAT=DD-MON-YYYY: is not an identifier, please tell me what i am missing?

  • Delete all AVAILABLE valid RMAN backup by RMAN command

    Hi
    We are taking RMAN full backup on disk every day. But right now we don’t have enough space on RMAN backup mount point. So we want to delete all AVAILABLE valid RMAN backup by RMAN command.
    Please guide to delete all AVAILABLE valid RMAN backup by RMAN command.
    -Thanks
    Edited by: Fazlul Kabir Mahfuz on May 13, 2013 11:06 AM

    You can do it by manually delete the backups and archivelogs from OS location. Then use below commands
    RMAN>crosscheck backup;
    It will give status as EXPIRED for backups which are valid but not available at OS level.
    RMAN>delete expired backup;
    Delete all the backups whose status are EXPIRED from database level.
    Similarly for archivelogs
    RMAN>crosscheck archivelog all;
    RMAN>delete expired archivelog all;

  • RMAN backup destination changed to Disk

    11.2/Solaris 10
    We had set up the backups for a DB to go to Tape using
    CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default This was working fine.
    Yesterday we had to take an Ad hoc cold backup for this DB to Disk .Using FORMAT parameter to point to the disk location, I took this backup in NOCATALOG mode ie. using Control file as the catalog.
    Now , when i connected to the catalog for this DB and did a SHOW ALL; I can see that backup location is changed to Disk even in the Catalog.
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1; This happened due to the resync. I guess.
    So, whenever I take Disk based backups using Control file as the catalog , I have to connect to the actual RMAN Catalog schema and revert the Backup location to SBT_TAPE using
    CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default?

    Configuer is RMAN command which change permanent RMAN configuration settings.
    CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    Above would be permanent for external tape drive.
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
    You have overrided persistently from tape to disk.
    You can set on the fly for backup location by using
    run {
    allocate channel ch1 type DISK;
    backup database plus archivelog;
    release channel ch1;
    }If you want to have backup at tape cartridge then
    run
      ALLOCATE CHANNEL ch1 DEVICE TYPE sbt
        PARMS='ENV=(OB_MEDIA_FAMILY=daily_bkp)';
      BACKUP DATABASE;
      RELEASE CHANNEL ch1;
    }

  • Error , ORA-19809 & ORA-19804 While restoring RMAN backup .

    Hi Experts,
    I am restoring production RMAN backup to UAT . Using below steps
    1)rman target=/
    2)RMAN> startup nomount;
    3) RMAN> restore controlfile from '/orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl';
    Starting restore at 05-AUG-10
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=3 device type=DISK
    channel ORA_DISK_1: copied control file copy
    output file name=+DATA_ACME/acme/controlfile/current.256.724845209
    output file name=+DATA_ACME/acme/controlfile/current.257.724845209
    Finished restore at 05-AUG-10
    4) RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    5) RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME1/current/%F';
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
    new RMAN configuration parameters are successfully stored
    6) RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
    old RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
    new RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
    new RMAN configuration parameters are successfully stored
    released channel: ORA_DISK_1
    7) RMAN> CATALOG START WITH '/orabkdump/Rman_Bak/ACME';
    searching for all files that match the pattern /orabkdump/Rman_Bak/ACME
    List of Files Unknown to the Database
    =====================================
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
    File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
    File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
    File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
    File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
    File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
    Do you really want to catalog the above files (enter YES or NO)? YES
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
    File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
    File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
    List of Files Which Where Not Cataloged
    =======================================
    File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
    RMAN-07517: Reason: The file header is corrupted
    File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
    RMAN-07517: Reason: The file header is corrupted
    File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
    RMAN-07517: Reason: The file header is corrupted
    8) RMAN> run {
    2> set until sequence 1789 thread 2;
    3> restore database;
    4> recover database;
    5> sql 'alter database open resetlogs';
    6> }
    executing command: SET until clause
    Starting restore at 06-AUG-10
    using channel ORA_DISK_1
    Finished restore at 06-AUG-10
    Starting recover at 06-AUG-10
    using channel ORA_DISK_1
    starting media recovery
    channel ORA_DISK_1: starting archived log restore to default destination
    channel ORA_DISK_1: restoring archived log
    archived log thread=1 sequence=2803
    channel ORA_DISK_1: restoring archived log
    archived log thread=2 sequence=6051
    channel ORA_DISK_1: restoring archived log
    archived log thread=1 sequence=2804
    channel ORA_DISK_1: reading from backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/06/2010 23:10:38
    ORA-19870: error while restoring backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
    ORA-19809: limit exceeded for recovery files
    ORA-19804: cannot reclaim 49283072 bytes disk space from 5218762752 limit
    ** My UAT database should be in noarchival mode . Generally such errors have been observed during backup , but have no clue why they occurred during recovery .Please advice .
    Thanks
    Edited by: user11981514 on Aug 6, 2010 9:46 AM

    Hi,
    Since the error ORA-19809 indicates the lack of space in flash recovery area during the media recovery, I suggested increasing the value of the parameter DB_RECOVERY_FILE_DEST_SIZE.
    Yes, during the media recovery the RMAN will restore the archived log to the default destination (only if the required archived logs are not already on the disks).You can confirm the restore location of the archived log in RMAN restore log/destination specified by parameters log_archive_dest_1/db_recovery_file_dest.
    Regards,
    Vaibhav

  • 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.

  • Need inputs on RMAN Backup n Recovery for multiple restore of clean backup

    I will explain my scenario below:
    We have the requirement of performance testing of our proposed production platform, for this i am asked to take RMAN backup of clean position (Say Day0 or baseline backup) and restore it multiple times for few rounds of testing. My question is after 1st restore (with set until time of day0 position) if i open the database with resetlogs, would i be able to restore same clean backup again? I am using control file in the environment instead of RMAN catalog database. What i can do to make this scenario work? I am already in preperation of setting rman catalog database.
    Please suggest me the best way forward...
    Many Thanks
    Nukesh

    Hi Asif,
    I tried to make it work but seems there are still issue with my recovery, can you have a look and point out the shortcommings. i am totally lost here
    RMAN> list incarnation;
    using target database control file instead of recovery catalog
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 MYTEST 2433328848 PARENT 1 19-DEC-06
    2 2 MYTEST 2433328848 PARENT 564488 04-NOV-10
    3 3 MYTEST 2433328848 CURRENT 693719 06-NOV-10
    RMAN> exit
    TEST1DB-> rman target sys@MYTEST1
    Recovery Manager: Release 10.2.0.3.0 - Production on Sun Nov 7 11:43:01 2010
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    target database Password:
    connected to target database: MYTEST (DBID=2433328848, not open)
    RMAN> reset database to incarnation 2;
    using target database control file instead of recovery catalog
    database reset to incarnation 2
    RMAN> run {
    2> restore database until scn 10000;
    3> recover database until scn 10000;
    4> alter database open resetlogs;
    5> };
    Starting restore at 07-NOV-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=191 instance=MYTEST1 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=190 instance=MYTEST1 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/07/2010 11:45:18
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, c onnect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, l ibrary, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rm an, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, va lidate"
    RMAN-01007: at line 0 column 2 file: standard input
    RMAN>
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanbackup/MYTEST/ora_cf%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rmanbackup/MYTEST/ora_df%t_s%s_s%p';
    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 '/u01/app/oracle/product/10g/dbs/snapcf_MYTEST1.f'; # default
    RMAN> exit
    SQL> select name from v$database;
    NAME
    MYTEST
    SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME
    NAME TYPE VALUE
    control_file_record_keep_time integer 7
    SQL>

  • How to pass a parameter into RMAN script

    Hello,
    I have the following rman script :
    run {
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'c:\oracle\RmanORCL102\ora_df%t_s%s_s%p';
    This script called configure.rman is launch by a .bat script with the following command:
    rman target 'sys/sys12@ORCL102 as sysdba' @c:\oracle\RmanORCL102\configure.rman
    How can I pass a parameter into rman script, I want to pass an additional directory like this:
    rman target 'sys/sys12@ORCL102 as sysdba' @c:\oracle\RmanORCL102\configure.rman v_dir_name
    And use it in rman script:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'c:\oracle\RmanORCL102\$v_dir_name\ora_df%t_s%s_s%p';
    Is it a way to do this?
    Regards,
    Elodie

    One option would be to create a file called backup.bat with the following:
    echo run {
    echo CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    echo CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    echo CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
    echo CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'c:\oracle\RmanORCL102\%1\ora_df%t_s%s_s%p';
    echo } ) | rman target sys/sys12@orcl102and then call the script as:
    c:\> backup.bat backup_directory_name

  • Restoring RMAN backup on a different server

    Hi oracle gurus
    i have following scenario
    i have a compressed backup set of a database
    i want to restore that rman backup on to a different server.
    both the server have same version of oracle.and both the server are of 32 bit.
    please reply if any more info is required.

    RESTORE AND RECOVERY PROCEDURE OF PRODUCTION DATABASE BACKUP ON TEST SERVERS
    As part of disaster recovery exercise or to test the validity of a RMAN backup, a full restore and recovery of databases can be performed on scratch or test servers utilising the production RMAN backups which have been restored from the tape backups on these test or scratch servers.
    This note will illustrate the above procedure by detailing the steps required to restore the backup of a production database (prod1) on a test server linux01 .
    The following assumptions are made in this note:
    The RMAN backups have been restored from tape backups to the same backup location on the test server as the production server where the backup was originally taken
    The identical directory structure as is present on production has been created on the test server. This will apply to not only the location of the database files (data, control files, redo log files), but also to the bdump,cdump, udump and adump locations.
    Controlfile autobackup has been enabled. This is important.
    Overview
    Restore the spfile from the autobackup
    Restore the controlfile from the autobackup
    Restore the data files
    Recover by applying archived redo log files
    Open the database with resetlogs
    Restore the SPFILE
    [oracle@linux01 prod1]$ rman target /
    connected to target database (not started)
    RMAN> set dbid=4266928631
    executing command: SET DBID
    RMAN> startup force nomount;
    startup failed: ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file '/u01/app/oracle/product/10.2.0/dbs/initprod1.ora'
    starting Oracle instance without parameter file for retrival of spfile
    Oracle instance started
    Total System Global Area 159383552 bytes
    Fixed Size 2039056 bytes
    Variable Size 67109616 bytes
    Database Buffers 83886080 bytes
    Redo Buffers 6348800 bytes
    RMAN> run
    2> {SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u02/backup/prod1/%F';
    3> restore spfile from autobackup;
    4> }
    RMAN> shutdown immediate;
    Restore the Control File
    In this case, the instance is now being started with the restored spfile. We can create a pfile as well from this spfile is so required.
    RMAN> startup nomount
    connected to target database (not started)
    Oracle instance started
    RMAN> set dbid=4266928631
    executing command: SET DBID
    RMAN> run
    2> {SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u02/backup/prod1/%F';
    3> restore controlfile from autobackup;
    4> }
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    Restore the database
    RMAN> restore database;
    Recover the database
    The recovery will fail at a point where it cannot restore any more archived redo log files.
    In this case the last archived log file which has been backed up is sequence 613.
    This information can be obtained by issuing a LIST BACKUP OF ARCHIVELOG ALL command.
    So RMAN will fail when it tries to apply sequence 614 ….
    RMAN> recover database
    [oracle@linux01 PROD1]$ rman target /
    connected to target database: PROD1 (DBID=4266928631, not open)
    RMAN> sql 'alter database open resetlogs';
    RMAN>
    reference: http://gavinsoorma.com/recovery-scenarios/

Maybe you are looking for