RMAN and cold backup

I am taking cold backup manually through copy command on every sunday of database every week and archive log backup through RMAN
suppose i want to restore backup on wednesday
how to retreive and apply archive logs
as archive logs are after taking backup are in different format

connect target sys/aa@oas
connect catalog rman/rman@catdb
connect auxiliary /
run {
set newname for datafile 1 to '/ORADATA/dupdb/system01.dbf';
set newname for datafile 2 to '/ORADATA/dupdb/undotbs01.dbf';
set newname for datafile 3 to '/ORADATA/dupdb/users01.dbf';
set newname for datafile 4 to '/ORADATA/dupdb/indx01.dbf';
set newname for datafile 5 to '/ORADATA/dupdb/example01.dbf';
allocate auxiliary channel dupdb1 type disk;
set until sequence 2 thread 1;
duplicate target database to dupdb
logfile
GROUP 1 ('/ORADATA/u02/redo01.log') SIZE 200k REUSE,
GROUP 2 ('/ORADATA/u03/redo02.log') SIZE 200k REUSE;
I THINK THIS OPTION WILL WORK

Similar Messages

  • Migrate Oracle 11g database from Windows To Linux using RMAN hot / cold  backup ?

    Hi Friends,
    Is it possible to Migrate Oracle 11g database from Windows To Linux using RMAN hot / cold  backup ? ( as i would like to perform Point In Time recovery)
    (or) The only way is to use RMAN convert as mentioned here  - Transporting Data Across Platforms
    (or) Is there any other method (except exp/imp and data pump)
    Regards,
    DB

    HI
    his post describes the procedure required to migrate a database from Windows to Linux using the RMAN Convert Database command.
    Both Windows and Linux platforms have the same endian format, which makes possible to transfer the whole database, making the migration process very straightforward and simple.
    To migrate between platforms that have a different endian format, Cross Platform Transportable Tablespaces (XTTS) needs to be used instead.
    List of Steps Needed to Complete the Migration
    The migration process is simple, but as it has several steps it is convenient to be familiar with them before running it.
    1. Check platform compatibility between source and target OS
    2. Start the database in read only mode
    3. Check database readiness for transport from Windows to Linux using DBMS_TDB.CHECK_DB
    4. Check if there are any external objects
    5. Execute the Rman Convert database command
    6. Copy converted datafiles, generated Transport Script and Parameter File to Linux
    7. Edit the init.ora for the new database
    8. Edit the Transport Script and Parameter File changing the windows paths to Linux Paths
    9. Execute the Transport Script
    10.Change the Database ID
    11.Check database integrity
    Thank you

  • Hot and cold backups

    i am learning to take hot and cold backups and i am having doubts regarding restoring and recovering/
    1. When restoring the cold backup .. i am copying the control and datafiles from the backup and then starting the database with reset logs is this enough?
    2. When i am recovering a tablespace in hot backup .. i have replaced the file from backup. I need to do something with the archive log files. Where do i place them in the database? If i have done some transactions after taking the hotback.. will i loose those transactions?

    "1. When restoring the cold backup .. i am copying the control and datafiles from the backup and then starting the database with reset logs is this enough?"
    Yes, you are right.... also include password file in your backup file list...
    2. When i am recovering a tablespace in hot backup .. i have replaced the file from backup. I need to do something with the archive log files. Where do i place them in the database? If i have done some transactions after taking the hotback.. will i loose those transactions?
    You can place the old datafile at new location also. For hot backup, your DB must
    be running in archive log mode, so you will not loose any transaction.....

  • RMAN and consistent backup

    Hi,
    in10g, I stop my DB and make a cold backup of my database (it's then a consistent backup).
    Can RMAN use this backup ? How ?
    Thank you.

    Yes, you can use a Cold Backup that was not taken by RMAN -- provided that you have the controlfile included in the backup. In RMAN you'd have to CATALOG each of the files in the backup as DATAFILE COPYies before RMAN can be "aware" of them.
    If the backup was taken with an OS command, you simple use the revers e to restore it. If your backup did not include the Online Redo Logs, you'd need to use
    STARTUP MOUNT
    ALTER DATABASE RECOVER
    CANCEL
    ALTER DATABASE OPEN RESETLOGSin SQLPlus.
    If you want to Apply ArchiveLogs generated after the backup, then don't  open resetlogs !
    continue with
    RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCELand CANCEL when you have applied the last available archivelog, after which you will
    ALTER DATABASE OPEN RESETLOGSHemant K Chitale
    http://hemantoracledba.blogspot.com
    Edited by: Hemant K Chitale on Aug 30, 2009 11:31 PM

  • ASM and Cold backup

    Is there any way to coldbackup a database that is using ASM?
    My development server has a database of 500GB in size. To move this to the production server I used to do cold backups but unable to do it with ASM.
    I was planning to use EXPORT utility but I read a few articles saying the export files should be more than a few GB.
    Has anyone got any ideas how to move large database that is using ASM from dev to prod?
    Thanks

    RMAN is the only option to take backups of databases using on ASM and you can use RMAN to take the cold backup of your database. First shutdown the database cleanly and then mount it and issue "backup database" at rman prompt to the cold backup. Read oracle doc for more information on RMAN setup.
    Daljit Singh

  • RMAN and Legato Backup

    I am trying to setup the Oracle Agent for Legato to backup an oracle database. I keep getting insufficient privelages when trying to:
    rman nocatalog
    connect target userid/password@database
    I have been trying the system id and password but it doesn't work.

    Hi
    Are you trying to duplicate a database?
    Did you read the restriction of the SET DBID command?
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96565/rcmsynta50.htm#98274
    Restrictions and Usage Notes for the SET DBID Command
    You should only run the SET DBID command in the following specialized circumstances:
    * You are not connected to a recovery catalog and want to restore the control file or server parameter file.
    * You are connected to a recovery catalog want to restore the control file, but the database name is not unique in the recovery catalog.
    * The server parameter file is lost and you want to restore it.
    Is the 3rd point your case?
    Other good Metalink note:
    How to restore an Spfile File from autobackup older than 7 days https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=292835.1
    restore controlfile from autobackup maxdays <number>;
    Bye, Aron

  • RMAN and Begin backup mode

    Hi guys I have a couple of questiopns...
    I want to know whether data is written to datafiles by DBWR when the datafile is in begin backup mode.
    What is the difference in archive log creation during normal operation of a database and operation of a database during RMAN backup?

    user13087302 wrote:
    Normally, Oracle should write only changes into redolog files. But if tablespace is in backup mode, then entire block will be put into redolog as soon as this change it is 1st change occured on that block after enabling backup mode. That is why, we face massive redo log generation if the tablespace is in backup mode. So, logically you should be able to recover to the last SCN you have in hands.What do you mean by last SCN.Is it the SCN before puttting the tablespace in backup mode?Does that mean data present in other files will also be lost even though they are written in datafiles..Pls, look:
    SQL> create tablespace myts1 datafile 'C:\app\oracle\oradata\testdb\myts1.dbf' size 10m;
    Tablespace created.
    SQL> create tablespace myts2 datafile 'C:\app\oracle\oradata\testdb\myts2.dbf' size 10m;
    Tablespace created.
    SQL> create table myt1 tablespace myts1 as select * from dba_objects where rownum<10001;
    Table created.
    SQL> create table myt2 tablespace myts2 as select * from dba_objects where rownum<10001;
    Table created.
    SQL> alter tablespace myts1 begin backup;
    Tablespace altered.
    SQL> create table myt1_1 tablespace myts1 as select * from dba_objects where rownum<10001;
    Table created.
    SQL> create table myt2_1 tablespace myts2 as select * from dba_objects where rownum<10001;
    Table created.
    SQL> create table myt1_3 tablespace myts1 as select * from dba_objects where rownum<10001;
    Table created.Backup database:
    C:\Documents and Settings\Administrator>rman target /
    Recovery Manager: Release 11.2.0.1.0 - Production on Wed Nov 3 15:46:55 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: TESTDB (DBID=2517263760)
    RMAN> backup database;
    Starting backup at 03-NOV-10
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=44 device type=DISK
    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=C:\APP\ORACLE\ORADATA\TESTDB\SYSTEM01.DBF
    input datafile file number=00002 name=C:\APP\ORACLE\ORADATA\TESTDB\SYSAUX01.DBF
    input datafile file number=00003 name=C:\APP\ORACLE\ORADATA\TESTDB\UNDOTBS01.DBF
    input datafile file number=00005 name=C:\APP\ORACLE\ORADATA\TESTDB\EXAMPLE01.DBF
    input datafile file number=00006 name=C:\APP\ORACLE\ORADATA\TESTDB\MYTS1.DBF
    input datafile file number=00007 name=C:\APP\ORACLE\ORADATA\TESTDB\MYTS2.DBF
    input datafile file number=00004 name=C:\APP\ORACLE\ORADATA\TESTDB\USERS01.DBF
    channel ORA_DISK_1: starting piece 1 at 03-NOV-10
    channel ORA_DISK_1: finished piece 1 at 03-NOV-10
    piece handle=C:\APP\ORACLE\FLASH_RECOVERY_AREA\PRIM_DB\BACKUPSET\2010_11_03\O1_MF_NNNDF_TAG20101103T154701_6F2LXQ5C_.BKP tag=TAG20101103T154701 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:35
    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 03-NOV-10
    channel ORA_DISK_1: finished piece 1 at 03-NOV-10
    piece handle=C:\APP\ORACLE\FLASH_RECOVERY_AREA\PRIM_DB\BACKUPSET\2010_11_03\O1_MF_NCSNF_TAG20101103T154701_6F2M0PJ3_.BKP tag=TAG20101103T154701 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 03-NOV-10
    Recovery Manager complete.
    SQL> select current_scn from v$database;
    CURRENT_SCN
        1466019
    SQL> drop table myt1_3 purge;
    Table dropped.So, we dropped table MYT1_3 and now trying incomplete recovery.
    SQL> shutdown abort;
    ORACLE instance shut down.
    SQL> startup mount;
    ORACLE instance started.
    Total System Global Area  431038464 bytes
    Fixed Size                  1375088 bytes
    Variable Size             322962576 bytes
    Database Buffers          100663296 bytes
    Redo Buffers                6037504 bytes
    Database mounted. C:\Documents and Settings\Administrator>rman target /
    Recovery Manager: Release 11.2.0.1.0 - Production on Wed Nov 3 15:51:51 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: TESTDB (DBID=2517263760, not open)
    RMAN> run
    2> {
    3> set until scn 1466019;
    4> restore database;
    5> recover database;
    6> sql 'alter database open resetlogs';
    7> }
    executing command: SET until clause
    Starting restore at 03-NOV-10
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=20 device type=DISK
    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 C:\APP\ORACLE\ORADATA\TESTDB\SYS
    TEM01.DBF
    channel ORA_DISK_1: restoring datafile 00002 to C:\APP\ORACLE\ORADATA\TESTDB\SYSAUX01.DBF
    channel ORA_DISK_1: restoring datafile 00003 to C:\APP\ORACLE\ORADATA\TESTDB\UNDOTBS01.DBF
    channel ORA_DISK_1: restoring datafile 00004 to C:\APP\ORACLE\ORADATA\TESTDB\USERS01.DBF
    channel ORA_DISK_1: restoring datafile 00005 to C:\APP\ORACLE\ORADATA\TESTDB\EXAMPLE01.DBF
    channel ORA_DISK_1: restoring datafile 00006 to C:\APP\ORACLE\ORADATA\TESTDB\MYTS1.DBF
    channel ORA_DISK_1: restoring datafile 00007 to C:\APP\ORACLE\ORADATA\TESTDB\MYTS2.DBF
    channel ORA_DISK_1: reading from backup piece C:\APP\ORACLE\FLASH_RECOVERY_AREA\
    PRIM_DB\BACKUPSET\2010_11_03\O1_MF_NNNDF_TAG20101103T154701_6F2LXQ5C_.BKP
    channel ORA_DISK_1: piece handle=C:\APP\ORACLE\FLASH_RECOVERY_AREA\PRIM_DB\BACKUPSET\2010_11_03\O1_MF_NNNDF_TAG20101103T154701_6F2LXQ5C_.BKP tag=TAG20101103T154701
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:45
    Finished restore at 03-NOV-10
    Starting recover at 03-NOV-10
    using channel ORA_DISK_1
    starting media recovery
    media recovery complete, elapsed time: 00:00:03
    Finished recover at 03-NOV-10
    sql statement: alter database open resetlogs
    RMAN>Now, check tables:
    SQL> select count(*) from myt1;
      COUNT(*)
         10000
    SQL> select count(*) from myt2;
       COUNT(*)
         10000
    SQL> select count(*) from myt1_3;
      COUNT(*)
         10000
    SQL> select count(*) from myt2_1;
      COUNT(*)
         10000So, it does not matter what is the status of any tablespace: in backup mode or not. Incomplete recovery uses archivelogs + redologs.

  • Stop and start database for cold backup

    Hi,
    Database :Oracle 10g R1
    OS : Red hat 3
    I have a RAC database with 2 nodes.
    I build this script to make a cold backup of the database. (I will put it in the cron tab).
    My question is the SRVCTL will work in this scripts??
    # ***** COLDBACKUP ORACLE DATABASE ON LINUX *****
    DIRECTORY=/u02/backup/script/; export DIRECTORY
    cd ${DIRECTORY}
    # ***** SHUTDOWN THE DATABASE *******
    export oracle_sid=RCDB
    srvctl stop database -d RCDB
    # *****cold backup for "RCDB" database on 13-FEB-07 ... *****
    # ***** COPY FILES *****
    # Redo logs
    cp /u02/oradata/RCDB/redo01.log ${DIRECTORY}
    cp /u02/oradata/RCDB/redo07.log ${DIRECTORY}
    cp /u02/oradata/RCDB/redo03.log ${DIRECTORY}
    cp /u02/oradata/RCDB/redo08.log ${DIRECTORY}
    # Datafiles
    #*********START UP DATABASE AND SERVICES********
    srvctl start database -d RCDB
    exit
    Message was edited by:
    ASkika
    Message was edited by:
    ASkika

    I need to put a quick policy backup ... and cold
    backup it's what I use and it works.And reduces the availability of your cluster.
    The problem about RMAN is that we never use it. I
    have to learn about it to make scripts to test....
    and this will tack me 2 or 3 days...I'd assume that installing RAC didn't go overnight, so why underfund the crucial part of any database system, the backup?
    There's even a step by step guide for backup on the Getting Started: DBAs page.
    Samples (and changes) on the latest version of RMAN can be found for example in RMAN Enhancements.
    Or take a look at this Oracle Magazine article:Faster Backup, Faster Recovery
    Backup and Recovery Basics in the user documentation may also be a good starting point.
    C.

  • RAC to RAC CLONE FROM RMAN Cold Backup

    Hi All,
    I need your kind assistance in Cloning my Oracle RAC 11.2.0.2 Environment to remote host. Following is Disk layout
    DGVOT (ASM Disk group holding OCR and Voting Disk)
    DGDATA (ASM Disk Group Holding Data FIles)
    DGFRA (ASM Disk Group Holding Fast Recovery FIles)
    Remote Host is on different location so cannot use RMAN duplicate with auxiliary channel.
    Have luxury of downtime so I want to take RMAN Consistent( Cold Backup)
    SAME Disk layout is available to remote hosts.
    11.2.0.2 CLusterware (GI) Plus the oracle binaries are already installed.
    Can any body tell me the steps to
    1) How to take cold backup to disk so that I can tar and copy to remote host
    2) clone the database on remote host
    3) How i will add the database listener and other resources of this databasee to clusterware.
    actually this is my first RAC clone so i am not much aware of detail steps.
    I have gone though many metalink notes but no one is matching with my requirements. your expert advice will help me a lot
    Regards,

    Hi
    1) How to take cold backup to disk so that I can tar and copy to remote host.
    Use Rman for cold backupIn mount stage execute
    RMAN>backup database plus archivelog format '<disk_path>/dbp%U';
    RMAN> backup current controlfile format '<disk_path>/ctl%U';
    Copy thse backup sets to remote host
    2) clone the database on remote host
    Create Similar ASM Disk groups as on source
    create pfile/spifile, startup instance in nomount mode
    catalog backup set
    RMAN> catalog start with '<backup_set location>';
    Restore controlfile
    RMAN>restore controlfile;
    RMAN> restore database;
    RMAN> recover database;
    On successfull recovery
    RMAN>sql 'alter database open';
    3) How i will add the database listener and other resources of this databasee to clusterware.
    User srvctl to add resources
    Usage: srvctl <command> <object> [<options>]
    commands: enable|disable|start|stop|relocate|status|add|remove|modify|getenv|setenv|unsetenv|config|convert|upgrade
    objects: database|instance|service|nodeapps|vip|network|asm|diskgroup|listener|srvpool|server|scan|scan_listener|oc4j|home|filesystem|gns|cvu
    For detailed help on each command and object and its options use:
    srvctl <command> -h or
    srvctl <command> <object> -h
    Thanks,
    Ajay More

  • Cold backup of High Availability DB 10gR2 in SOLARIS 8 SPARC

    Hi
    I want to know the procedure of taking Cold backup in Solaris 8 SPARC in
    High Availability Environment.
    Any reference document will be helpful.
    Thanks in advance.
    Renuka

    That seems to be a contradiction in terms, high availibility and cold backup. When you do a cold backup the database is down and not available. In a primary - standby configuration, you could switch the standby to primary, shutdown the (former) primary and perform a cold backup of it.

  • Restore cold backup and RMAN backup

    Hi,
    I have cold backup as well as RMAN backup. But i don't know how to restore the backup.
    Please anybody send, steps or links for restoring both backups.
    Regs,
    Brijesh

    The "script" would depend on how the backup was done.
    A cold backup should be a backup of controlfiles and datafiles.
    Was it done using RMAN ? Or done using an OS command (e.g. "cp" or "tar" or "cpio") ?
    A non-RMAN cold backup can be restored with the same command that was used to create the backup. If the backup did not include the Online Redo Log files, you need to simulate a dummy recovery from the SQL command line (RECOVER DATABASE UNTIL CANCEL ; then CANCEL) and ALTER DATABASE OPEN RESETLOGS.
    If the backup was done using RMAN, you need to
    1. RESTORE CONTROLFILE FROM '/location_of_backuppiece'
    2. ALTER DATABASE MOUNT
    3. RESTORE DATABASE
    4. ALTER DATABASE OPEN
    Hemant K Chitale

  • Difference betwen RMAN,COLD and HOT backup

    Hi Experts,
    I have faces some interview question .
    what is difference between COLD and HOT backup ?
    what is difference between RMAN, COLD and HOT backup?

    You mean the following,
    Mark the beginning of the online tablespace backup.
    SQL> ALTER TABLESPACE users BEGIN BACKUP;
    Back up the online datafiles of the online tablespace with operating system commands. For UNIX:
    % cp /oracle/oradata/trgt/users01.dbf /d2/users01_'date "+%m_%d_%y"'.dbf
    After backing up the datafiles of the online tablespace, run the SQL statement ALTER TABLESPACE with the END BACKUP option.
    SQL> ALTER TABLESPACE users END BACKUP;
    Please visit here for more details:
    Making User-Managed Backups of Online Read/Write Tablespaces
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/osbackup004.htm#sthref1489
    Adith

  • RMAN cold backup taking more time than usual

    Hi everybody.. please help me resolving below issue..
    I have configured the RMAN in one of the production database with separate catalogue database six months earlier. I have sceduled weekly cold backup through RMAN on sunday 6pm. Normally it used to take one hour to complete the cold backup and database goes down soon as the job starts.
    But since from then every week the time taken to just initiate the database shutdown continuosly increasing and recently when i checked it is taking 1 hour to initiate the database shutdown. Once the initiation starts it hardly take 1 to 3 min to shutdown.
    Database is up and running during that one Hour. I was in the assumption that RMAN takes some time to execute its internal packages.
    Please help
    Regards,
    Arun Kumar

    Hi John and Tychos,
    Thank you very much for your valuable inputs.
    Yesterday there was cold backup and i have monitored the CPU usage. But there was no load on the CPU at that time and CPU usage was 0%
    I have tried connecting to RMAN manually and it connects within a second. And also noticed in prstat -a that rman connects as soon as the job starts.
    So i think that its taking time at the deleting obsolete backups.
    But I have observerd following observation.
    Before executing the delete obsolete command as mentioned before
    RMAN> REPORT OBSOLETE RECOVERY WINDOW OF 35 DAYS DEVICE TYPE 'SBT_TAPE';
    Report of obsolete backups and copies
    Type Key Completion Time Filename/Handle
    Backup Set 83409 25-JUL-09
    Backup Piece 83587 25-JUL-09 arc_SID_20090725_557_1
    Backup Set 83410 25-JUL-09
    Backup Piece 83588 25-JUL-09 arc_SID_20090725_558_1
    Backup Set 83411 25-JUL-09
    Backup Piece 83589 25-JUL-09 arc_SID_20090725_559_1
    After executing the delete obsolete command
    RMAN> REPORT OBSOLETE RECOVERY WINDOW OF 35 DAYS DEVICE TYPE 'SBT_TAPE';
    Report of obsolete backups and copies
    Type Key Completion Time Filename/Handle
    Backup Set 83409 25-JUL-09
    Backup Piece 83587 25-JUL-09 arc_SID_20090725_557_1
    Backup Set 83410 25-JUL-09
    Backup Piece 83588 25-JUL-09 arc_SID_20090725_558_1
    Backup Set 83411 25-JUL-09
    Backup Piece 83589 25-JUL-09 arc_SID_20090725_559_1
    Please advice me on the following.
    1. Why its not deleting the obsolete BACKUP SETS?
    2. Is it normal that RMAN takes this much deleting obsolete backup sets? How can i minimize the time taking for deleting obsolete files.
    Thanks and Regards,
    Arun Kumar

  • Cold backup downtime using RMAN

    Over the weekend I performed a cold RMAN backup on a 3.6 TB
    database. Because a lot of the database was backed up with
    transportable tablespaces, the net amount being backed up was
    approximately 365 Gb. I took down the database at 11:00 and the
    script finished at 4am, but in reviewing the logs, the database
    actually appears to have been opened at 2am.
    I assumed that the database would be down the entirety of the
    backup. Can anyone help me understand why the database was
    opened so long before the RMAN command completed? Was the
    backup adversely affected in any way by a user obtaining access
    prior to the RMAN process completing.
    Any information greatly appreciated.

    unfortunately i think you misunderstood the original question. i took the database down to do the cold backup. in order to use rman, you have to startup nomount the instance.
    the script run was:
    #!/usr/bin/ksh
    rman msglog '/data2/oracle2/local/log/rman_lvl0.log' <<EOF
    @connect.rman
    run {
    backup incremental level 0 tag full_bkup0 database diskratio=0;
    alter database open;
    exit;
    EOF
    exit
    the "alter database open" tells RMAN to open the database once the backup is completed. i had a process running that checked each 10 seconds to see if the PID for the RMAN process was still running. The process itself appears to have run for an additional 2 hours after the database was opened.
    there is nothing on the system to suggest that the database was opened by anything other than RMAN. was the database opened prematurely? was the additional time spent in the RMAN script doing the sync in the database? did the usage by the user prior to RMAN completing invalidate the backup? (so far the cloning is still running without error).

  • Cold backup using RMAN

    Dear All,
    db_version :10.2.0.4
    os_version:Window 2003 server
    Environment:Test
    I wish to perform cold backup using RMAN for the same i want to know following :
    1. What is the script / command ?
    2. How to restore cold backup completely ( ex:- if i lost all my data,redo and archives )
    3. Is it mandatory to open the database in RESETLOG mode after recovery ( since i have a cold backup ) ?
    Thanks in advance

    A "Cold" Backup is called a "Consistent" Backup.
    See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup003.htm#sthref297
    Backup :
    From the RMAN command line :
    SHUTDOWN IMMEDIATE
    STARTUP MOUNT
    BACKUP DATABASE
    BACKUP CURRENT CONTROLFILE  -- to get the controlfile in a separate backupsetRestore :
    STARTUP MOUNT
    RESTORE DATABASE
    ALTER DATABASE OPENIf you use an SPFILE, you can have an SPFILE backup included automatically with the controlfile backupset with CONFIGURE CONTROLFILE AUTOBACKUP ON and CONFIGURE CONTROLFILE AUTOBACKUP FORMAT ...
    Read the documentation.
    Hemant K Chitale

Maybe you are looking for