RMAN backup policy needed to confirm!

Hi, All friends:
I am working on a production db, now set up Rman backup policy.
My purpose: keep only one backupset of datafile and control file, backup all archived logs--never delete--so database can be recovered to any time before.
so for Rman configuration;
configure retention policy to redundancy 1;
in DB control, setup a night whole db backup with backup archivelog and with with delete obsolete.
Am I right?
if anything wrong, please tell me, I want to confirm.
thanks a lot in advance.

thanks for your answer.
I want to use disk for backup storage because db size is small(only 7G) and we want a quick recovery.
To clarity, for my understanding,
if
configure retention policy to redundancy 1;
backups of archived redo logs won't be marked as obsolete, only backups of datafiles and control files will be marked as obsolete.
so if you run delete obsolete. it won't delete backups of archived logs.
(this is not like recovery windows, say you set retention policy to recovery window of 4 days, if you delete obsolete, RMAN will delete both backups of archived logs and data/control files)
AM I RiGHT?
thanks

Similar Messages

  • RMAN Backup policy

    Hi,
    I have few basic doubts in RMAN backup policy
    1 . Is that possible to set Retention policy to recovery window in minutes??
    2 . If i set Backup Retention Policy to recovery window to 3 days and i am performing RMAN differential incremental backup for 4 days. Will my backups become obsolete after 3 days even though they are needed for recovery or they won't become obsolete since they are needed for recovery ???
    Regards,
    007

    1 What does the documentation of your unknown version of RMAN say? Does it states minutes are possible? If so, why are you asking rhetorical questions? (questions for which you already know the answer)
    2 Rman only considers level 0 backups to determine whether a backup is obsolete, as you can't restore from an incremental backup.
    Setting up a backup scheme for 4 days with a recovery window of 3 days wouldn't make any backup obsolete.
    Sybrand Bakker
    Senior Oracle DBA

  • Rman Retention policy to recovery window

    Hi,
    I have few basic doubts in RMAN backup policy
    1 . Is that possible to set Retention policy to recovery window in minutes??
    2 . If i set Backup Retention Policy to recovery window to 3 days and i am performing RMAN differential incremental backup for 4 days. Will my backups become obsolete after 3 days even though they are needed for recovery or they won't become obsolete since they are needed for recovery ???
    Regards,
    007

    1) Syntax is .... TO RECOVERY WINDOW OF integer DAYS ... no other time statement.
    2) Backups become obsolete when no longer needed to fulfil a retention policy. In a (theoretical) scenario, you perform a level 0 backup and then only incremental backups, the starting level 0 backup must be kept for ever (even if it WOULD be possible to define a recovery window in minutes).
    Werner

  • The specified RMAN backup is invalid ?

    Hi,
    I'm trying to clone database by enterprise manager (OS: Win Server 2003, DB: 11gR1), but I'm getting the following error:
    >
    RMAN Backup Location - The specified RMAN backup is invalid. Could not identify controlfile from the backup.
    >
    I'm using this opyion:
    >
    -An existing database backup
    -RMAN backup
    >
    The "* RMAN Backup Location" I selected is where a full database backup location.
    what could be the problem?
    Saad,

    Saad Nayef wrote:
    Hi,
    I'm trying to clone database by enterprise manager (OS: Win Server 2003, DB: 11gR1), but I'm getting the following error:
    >
    RMAN Backup Location - The specified RMAN backup is invalid. Could not identify controlfile from the backup.
    >As per the error message, the control file backup is not there. So did you take this backup or its passed over to you? Whoever did the backup, they need to confirm the validity of it including the control file backup status.
    HTH
    Aman....

  • RMAN retention policy really long

    Hi,
    we are planning to have an RMAN backup policy really long, around 7 years, with all the backup piece stored on a shared drive.
    I would like to ask if there are problems or concern to have a recovery windows of around 2500 days, and if I have to change other Oracle parameter like control_file_record_keep_time.
    The oracle version is 10.2.0.4, on a Solaris box, the customer don't want you a Catalog.
    thanks for your time
    Nunzio

    I Nikolay,
    thanks for you answer.
    Nikolay Ivankin  wrote:
    Nunzio Cafarelli wrote:
    What do you mean for huge!? and, in your experience, we should expect some hi decrease of performance, or are we speaking of something like 1%.I can't say - I don't know db size, user's activity, amount of redo information, backup strategy.
    You are right, it's not easy to have an idea of what will happen.
    Except that 2 points, there are no other functionality concerns!?Aren't enough? I would say, those 2 points are enough to refuse to keep rman info in CF, but catalog db.
    Honestly no, if I will have a big (supposing 40 Mb) control file, and I'll have a performance decrease of around 1% or 2% is my opinion that that 2 points are not enough to refuse to proceed in this way.
    I'll be scared if I know that ORACLE can't manage that amount of days as recovery window, and I'll have problem if I need to recover the database in a point in time that, for example, is more than 3 years ago.
    Anyway, thanks.
    Regards
    Nunzio

  • 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

  • RMAN Backupset information needed for REFRESH

    Hi,
    Just need some information on following while doing RMAN Refresh from PROD to Test in remote server with different file structure.
    1)If i have RMAN cold backup(datafiles backupset) of PROD(Archivelog Mode) do i need to have archivelog backupset for refresh?
    2) What RMAN backups i need to have for doing PROD(non-archivelog) refresh through RMAN to Test in remote server with different file structure?
    DB Version : 10g
    Thanks in advance

    913410 wrote:
    Thanks for the response.
    So for COLD RMAN Backup (done when PROD db was in mount state) do i need to even put the redologs to the backup location in both PROD and TEST Server ?As i will be doing RMAN REfresh from PROD to TEST in remote server with different directory using "duplicate target database to test" commandHi,
    Your backup is consistent that means which your database backup that you can open with the RESETLOGS option without performing media recovery. In other words, the backup does not require the application of redo to be made consistent.
    At moment of "alter database open resetlogs" Oracle will re-create all redo automatically.
    Regards,
    Levi Pereira

  • Configure backup agent to take the RMAN backup

    Hi,
    We have a Sun Storagetek SL48 tape library with us. we want to take the backup to tape using Rman.
    In order to take the RMAN backup, we need a backup agent needs to be installed on the database server.
    1. My doubt is If we have Sun Storagetek SL48 tape library, what backup agent needs to be installed on the server?
    2. If we know agent name, Could you please share the document to install the agent?
    Thanks for your help.
    R.Sundaravel

    These softwares support the SL48 and they have an agent for RMAN : Symantec NetBackup, Legato Networker.
    For Symantec, please check this URL : http://www.symantec.com/business/support/index?page=content&id=HOWTO44847#v15496705
    For Legato, this one : https://store.emc.com/Product-Family/DATA-DOMAIN-PRODUCTS/EMC-NetWorker/p/EMC-NetWorker

  • SQL to find rman backup files required for recovery?

    Hi folks,
    I'm looking for a sql statement that I can use to query the database and return a list of the RMAN backup files needed for a successful recovery based on a SCN or a point in time. I want to do it through SQL (not though rman) because I want to script an automated refresh process. My databases are backed up online, so I would need any archive log backups done during the database backup as well. So for example...
    I do a database backup
    Then do an archive log backup.
    Pass a SQL script the lowest and highest scn numbers during the backup.
    It returns a list of the rman backup pieces needed to do a successful recovery.
    I've got a script, below, which shows the lowest and highest scn during the last full backup (all datafiles which exist have been backed up), if someone understands what I'm looking for and has done something similar, I would really appreciate any insight you may have. What I'd want to get back from the SQL is the names of the rman backup files (handles) which would be needed to get the database recovered to the highest scn during the backup.
    SELECT MIN(VBD.CHECKPOINT_CHANGE#), MAX(VBD.CHECKPOINT_CHANGE#)
    FROM V$BACKUP_DATAFILE VBD, V$DATAFILE VDF,
    (SELECT
    CREATION_CHANGE#,
    MAX(COMPLETION_TIME) COMPLETION_TIME
    FROM V$BACKUP_DATAFILE
    WHERE CREATION_CHANGE# IN (
    SELECT CREATION_CHANGE# FROM V$DATAFILE)
    GROUP BY CREATION_CHANGE#
    ) QUERY1
    WHERE VBD.CREATION_CHANGE# = VDF.CREATION_CHANGE#
    AND VBD.CREATION_CHANGE# = QUERY1.CREATION_CHANGE#
    AND VBD.COMPLETION_TIME = QUERY1.COMPLETION_TIME;
    Thanks very much for your time,
    -Adam vonNieda

    In case anyone's wondering, here's the answer. The following query returns the min and max SCN numbers contained in the last online backup.
    SELECT MIN(VBD.CHECKPOINT_CHANGE#), MAX(VBD.CHECKPOINT_CHANGE#)
    FROM V$BACKUP_DATAFILE VBD, V$DATAFILE VDF,
    (SELECT
    CREATION_CHANGE#,
    MAX(COMPLETION_TIME) COMPLETION_TIME
    FROM V$BACKUP_DATAFILE
    WHERE CREATION_CHANGE# IN (
    SELECT CREATION_CHANGE# FROM V$DATAFILE)
    GROUP BY CREATION_CHANGE#
    ) QUERY1
    WHERE VBD.CREATION_CHANGE# = VDF.CREATION_CHANGE#
    AND VBD.CREATION_CHANGE# = QUERY1.CREATION_CHANGE#
    AND VBD.COMPLETION_TIME = QUERY1.COMPLETION_TIME;
    This next one gets the session key for that backup.
    Select distinct session_key from v$backup_datafile_details
    where checkpoint_change# >= <min scn# from above> and checkpoint_change# <= <max scn# from above>;
    And finally, this one returns all files written out during that RMAN session, which includes control files, data files, and archived redo logs
    Select handle from v$backup_piece_details
    where session_key = <session key from above> order by completion_time;

  • Need Advice on RMAN backup script

    Hi;
    Can any one advice if any error or guide to make RMAN backup proper :
    Backup Policy are:
    1.     0 level backup
    2.     current log file is arvhived before backing up
    3.     backup whole database (datafiles)
    4.     backup separate control file
    5.     backup is done on disk
    6.     control file auto backup ON
    7.     only 7 days archive log are need to be preserve ; old need to be deleted
    ### one time paramters seting
    RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
    RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'O:\rman\backup\Auto_Ctrl_weekly_%F';
    RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;
    ### Command for weekly 0 level backup
    run {
    allocate channel c1 type disk;
    sql 'alter system archive log current';
    backup incremental level 0 tag = weekly_database format 'o:\rman\backup\full_weekly_%d_%s_%p_%t'(database);
    release channel c1;
    configure controlfile autobackup format for device type disk to 'o:\rman\backup\auto_ctrl_weekly_%f';
    allocate channel c1 type disk;
    backup tag = weekly_arch archivelog until time 'sysdate-7' format 'o:\rman\backup\archive_weekly_%d_%s_%p_%t';
    delete archivelog until time 'sysdate-7';
    release channel c1;
    Regards
    Smith

    Dear Pierre F.;
    Actually, I just added in my backup plan to have daily backup through RMAN, instead of COLD backup.
    I have planned to take cold backup once a week. here is the side of data:
    *** datafile 410
    *** size of database : 86 GM
    *** relog files size : 250MB
    *** daily archive logs are : 250MB * 4(number of files) = 1GM aprox.
    yes, time constraint is there; just because of the size of database. and we r going for 24/7
    Is this script going to run only one per week ?
    Ans: no I this was level 0 backup; i will take level 1 incremental backup with same script daily too.
    Do you have any other RMAN script ?
    ANS: no, I will modify same script for incremental.
    after local copy of backup all backup files (RMAN) will be copy over network to backup server or we can install LTO tape device to copy directly from database server.
    kindly advise me I am new in RMAN.
    regards;
    SMITH

  • Restoring RMAN backup from tape beyond retention policy ??

    Hello Friends,
    I just stuck in some basic finding. Need your help to resolve the questions.
    How we can use RMAN backup to restore oracle database when the RMAN backup pushed to tape already and being a OLD backup ( before retention policy date).
    Just to elaborate a more..  Say my retention policy is 3 days. I want to restore from a old backup  like 30 days old.
    So surely the requesting backup is behind retention date and has been pushed to tape.
    Please suggest.
    Thanks in advance.
    Regards
    Sinha.

    dba.arnab wrote:
    Hello Friends,
    I just stuck in some basic finding. Need your help to resolve the questions.
    How we can use RMAN backup to restore oracle database when the RMAN backup pushed to tape already and being a OLD backup ( before retention policy date).
    Just to elaborate a more..  Say my retention policy is 3 days. I want to restore from a old backup  like 30 days old.
    So surely the requesting backup is behind retention date and has been pushed to tape.
    Please suggest.
    Thanks in advance.
    Regards
    Sinha.
    Assuming the actual backup files still exist (the only thing actually deleted is the record of them in the catalog), you can make those files available and use the rman 'catalog' command to re-catalog them.

  • Will RMAN backup all the needed files for me automatically ?

    I have execued the following command:RMAN>CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
    I want to know: Will RMAN backup all the needed files for me automatically every 14 days and delete the metadata of the files older than 14 days automatically?---------No.158

    Short answer is No.
    What's the definition of all needed files ? datafiles, control files, archive logs and/or online redo? and perhaps spfiles?
    RMAN>CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;This is RMAN configure command, it won't do any backup by itself. You need to issue backup command to backup files needed.
    You also need to delete obsolete files. The files will become obsolete after 14days but they will not remove themselves automatically.

  • RMAN backups does not match its retention policy

    Hello,
    I have couple of PROD instances on Windows environment with 11.2.0.3 DB version. RMAN retention policy is set to 14 days but I have noticed that backup is showing longer than that.
    For example: LIST BACKUP OF DATABASE whows backups since 13th October. I also checked backup pieces at netapp share and they are present.
    DELETE NOPROMPT OBSOLETE do not remove anything as expired backup.
    I have clear retention policy and set to 14 days again but does not seem to work.
    I would appreciate suggestion(s) regarding the strange issue.
    Thanks a lot.
    Best Regards

    John-MK wrote:
    Hello,
    I have couple of PROD instances on Windows environment with 11.2.0.3 DB version. RMAN retention policy is set to 14 days but I have noticed that backup is showing longer than that.
    For example: LIST BACKUP OF DATABASE whows backups since 13th October. I also checked backup pieces at netapp share and they are present.
    DELETE NOPROMPT OBSOLETE do not remove anything as expired backup.
    I have clear retention policy and set to 14 days again but does not seem to work.
    I would appreciate suggestion(s) regarding the strange issue.
    Thanks a lot.
    Best Regards
    We would need to know what kind of backups and when they were taken.  Consider this scenario:
    retention policy of 7 days.
    Incremental level 0 backup taken on Sundays
    Incremental level 1 backups taken Mon through Sat.
    Let's say Oct 1 is a Sunday, so we take an inc-0 backup on Oct 1, and again on Oct 8.
    Now let's say we are at Oct 10.  Our 7 day retention policy dicatates that we be able to recover to any day back to Oct 3.
    The only way we can recover to Oct 3 is to begin with that inc-0 backup from Oct 1.
    All recovery begins with the last inc-0 backup prior to the point in time to be recovered.  In a normal, regularly cycling schedule of backups,  you will actually end up with backups 1 day short of being twice as old as your retention period.
    Let's take a more extreme example.  Same 7-day retention period, but after a single inc-0 backup, you don't take any more backups for 3 months.  That one single backup is still needed to enforce your recovery window, and so is not obsolete, despite the fact it is 3 months old and your recovery window is only 7 days.
    Also, you mention 'expired'.  In terms of oracle backups, 'expired' is not the same as 'obsolete'.
    "Obsolete" means 'no longer needed to enforce recovery policy'.
    "Expired" is a bit more complex.
    when a backup is taken, or an archivelog is written, a record of that is written to the repository.  when you do an rman 'crosscheck', those repository records are compared to reality -- to see if the recorded backup file or archivelog file actually exists.  Maybe someone used an OS command to delete them.  Any file found to have 'gone walkabout' have their repository records marked as 'expired'.  An rman 'delete expired' then removes those records from the repository.

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

  • Need help in the RMAN backup

    Hi everybody
    What are the steps needed if move the RMAN backup to other location in the OS level
    (ie) every week i have to move the backup to other location

    There are not problem for example:
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
    C:\Documents and Settings\comp>set ORACLE_SID=W
    C:\Documents and Settings\comp>sqlplus "/as sysdba"
    SQL*Plus: Release 10.2.0.2.0 - Production on Mon Apr 26 14:53:08 2010
    Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
    ERROR:
    ORA-01031: insufficient privileges
    Enter user-name:
    C:\Documents and Settings\comp>sqlplus "sys/sm as sysdba"
    SQL*Plus: Release 10.2.0.2.0 - Production on Mon Apr 26 14:53:15 2010
    Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> archive log list;
    Database log mode No Archive Mode
    Automatic archival Disabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 12
    Current log sequence 14
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area 125829120 bytes
    Fixed Size 1288100 bytes
    Variable Size 71305308 bytes
    Database Buffers 46137344 bytes
    Redo Buffers 7098368 bytes
    Database mounted.
    SQL> alter database archivelog;
    Database altered.
    SQL> alter databaseop;
    alter databaseop
    ERROR at line 1:
    ORA-00940: invalid ALTER command
    SQL> alter database open;
    Database altered.
    SQL> exit
    Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Pr
    oduction
    With the Partitioning, OLAP and Data Mining options
    C:\Documents and Settings\comp>rman target sys/sm
    Recovery Manager: Release 10.2.0.2.0 - Production on Mon Apr 26 14:55:58 2010
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: W (DBID=754336873)
    RMAN> backup database;
    Starting backup at 26-APR-10
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=144 devtype=DISK
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\SYSTEM01.DBF
    input datafile fno=00003 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\SYSAUX01.DBF
    input datafile fno=00005 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\EXAMPLE01.DBF
    input datafile fno=00002 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\UNDOTBS01.DBF
    input datafile fno=00004 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\USERS01.DBF
    channel ORA_DISK_1: starting piece 1 at 26-APR-10
    channel ORA_DISK_1: finished piece 1 at 26-APR-10
    piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\2010_04_26
    \O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP tag=TAG20100426T145611 comment=NON
    E
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:34
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    including current control file in backupset
    including current SPFILE in backupset
    channel ORA_DISK_1: starting piece 1 at 26-APR-10
    channel ORA_DISK_1: finished piece 1 at 26-APR-10
    piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\2010_04_26
    \O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP tag=TAG20100426T145611 comment=NON
    E
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:05
    Finished backup at 26-APR-10
    RMAN> crossckeck backupset;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "identifier": expecting one of: "allocate, alter
    , backup, beginline, blockrecover, catalog, change, connect, copy, convert, crea
    te, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flas
    hback, host, {, library, list, mount, open, print, quit, recover, register, rele
    ase, replace, report, renormalize, reset, restore, resync, rman, run, rpctest, s
    et, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport
    , upgrade, unregister, validate"
    RMAN-01008: the bad identifier was: crossckeck
    RMAN-01007: at line 1 column 1 file: standard input
    RMAN> crosscheck backupset;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'EXPIRED'
    backup piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\201
    0_04_26\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP recid=1 stamp=717346573
    crosschecked backup piece: found to be 'EXPIRED'
    backup piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\201
    0_04_26\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP recid=2 stamp=717346669
    Crosschecked 2 objects
    RMAN> delete expired backupset
    2> ;
    using channel ORA_DISK_1
    List of Backup Pieces
    BP Key BS Key Pc# Cp# Status Device Type Piece Name
    1 1 1 1 EXPIRED DISK D:\ORACLE\PRODUCT\10.2.0\FLASH_R
    ECOVERY_AREA\W\BACKUPSET\2010_04_26\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP
    2 2 1 1 EXPIRED DISK D:\ORACLE\PRODUCT\10.2.0\FLASH_R
    ECOVERY_AREA\W\BACKUPSET\2010_04_26\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP
    Do you really want to delete the above objects (enter YES or NO)? y
    deleted backup piece
    backup piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\201
    0_04_26\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP recid=1 stamp=717346573
    deleted backup piece
    backup piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\201
    0_04_26\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP recid=2 stamp=717346669
    Deleted 2 EXPIRED objects
    now i copy all backup to c:\db
    then
    RMAN> catalog start with 'c:\db';
    searching for all files that match the pattern c:\db
    List of Files Unknown to the Database
    =====================================
    File Name: C:\db\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP
    File Name: C:\db\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP
    Do you really want to catalog the above files (enter YES or NO)? y
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: C:\db\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP
    File Name: C:\db\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP
    RMAN> list backupset;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    1 Full 592.76M DISK 00:01:26 26-APR-10
    BP Key: 4 Status: AVAILABLE Compressed: NO Tag: TAG20100426T145611
    Piece Name: C:\DB\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP
    List of Datafiles in backup set 1
    File LV Type Ckp SCN Ckp Time Name
    1 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\SYSTEM01.
    DBF
    2 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\UNDOTBS01
    .DBF
    3 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\SYSAUX01.
    DBF
    4 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\USERS01.D
    BF
    5 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\EXAMPLE01
    .DBF
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2 Full 6.80M DISK 00:00:04 26-APR-10
    BP Key: 3 Status: AVAILABLE Compressed: NO Tag: TAG20100426T145611
    Piece Name: C:\DB\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP
    Control File Included: Ckp SCN: 947720 Ckp time: 26-APR-10
    SPFILE Included: Modification time: 26-APR-10
    RMAN>

Maybe you are looking for

  • Error message 'sender address rejected by server' w/MacMail

    I receive email ok but all of a sudden I cannot send email or reply to email using Mac Mail. The error message says: Message could not be delivered and will remain in outbox, The sender address xxx@xxx was rejected by the server. What's up Apple serv

  • LabVIEW Crashes while closing the VI

    Hi all, I am experiencing a labVIEW crash everytime I close my VI after running it. what the VI is doing is, it communicates with an opal kelly board through the okFrontPanel.dll and reads some data from it and displays it in the front panel. The vi

  • Using SQL query on user defined table

    Hi all, i'am currently working on a project which use user defined table and i would like to know if sap allow us to do insertion/deletion/update on those table using sql query or if we have to use the DI only? thanks Best regards,

  • Re-Direct Issue

    When using Form based authentication on Weblogic 6.0 sp2 we get two interesting issues, (i) Sometimes after login has been successful the redirect fails. You are authenticated onto the contain as you can then go to the secured page. The page it seems

  • Warning: remove all all plastic as soon as you get new phone

    I just took delivery of a new iPhone 4 today that was ordered online through AT&T. After deactivating my 3G and activating the new phone, and copying my 3G data to the new phone, I removed the front and back plastic protective film on the new phone o