Rman retention to zero for primary

I am running backup on standby hence i have set the primary to
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
is there any reason why should i set below parameters to 7 and 1 ?
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
can i clear them ? syntaxt to set above parameters to 0 would be helpful.
oracle v11.2
thank you

CKPT wrote:
Hi,
Can you please tell these below configuration is from primary or standby?
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # defaultIf you set on primary it will affect to Primary not on standby, so please confirm that.its for primary,
if i leave as it is then how to i delete archivelgos that already been copied/applied to standby ?
can i delete arch logs thru rman without doing backup delete input ?

Similar Messages

  • RMAN 11gR2 DUPLICATE TARGET FOR STANDBY FROM ACTIVE DATABASE - Issue -HELP

    First question.
    Can primary and standby database have the same SID name?
    As I recall it is yes.
    I believe they must have different GLOBAL or DB_UNIQUE_NAME?
    Anyway, RMAN I believe is telling me it is having problems copying control file on first and dies.
    Permissions Issue on STANDBY machine?
    RMAN> connect target backup_admin/backup_admin
    connected to target database: LABDG (DBID=1973403623)
    RMAN> connect auxiliary sys/oracle@STANDBY;
    connected to auxiliary database: LABDG (not mounted)
    RMAN> DUPLICATE TARGET DATABASE FOR STANDBY FROM ACTIVE DATABASE;
    Starting Duplicate Db at 18-JUL-11
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=10 device type=DISK
    contents of Memory Script:
    backup as copy reuse
    targetfile '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwLABDG' auxiliar
    '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwLABDG' ;
    executing Memory Script
    Starting backup at 18-JUL-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=151 device type=DISK
    Finished backup at 18-JUL-11
    contents of Memory Script:
    backup as copy current controlfile for standby auxiliary format '/u01/oradat
    restore clone controlfile to '/u01/app/oracle/flash_recovery_area/LABDG/cont
    '/u01/oradata/LABDG/control01.ctl';
    executing Memory Script
    Starting backup at 18-JUL-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile copy
    copying standby control file
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 07/18/2011 11:20:54
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/18/2011 11:20:
    ORA-17628: Oracle error 19505 returned by remote Oracle server

    Hi,
    Permissions Issue on STANDBY machine?First problem I see is the sysdba password must be the same on both sides (target and auxiliary dbs).
    From the documentation.
    The source database and auxiliary instances must use the same SYSDBA password, which means that both instances must have password files. You can
    create the password file with a single password so you can start the auxiliary instance and enable the source database to connect to it.Check all prereqs for the standby db duplicate here.
    http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta020.htm#i81724
    Rgds,
    Tycho

  • RMAN Retention Policy - redundancy vs recovery window

    Hi All,
    I'm wondering what the most commonly used rman retention policy is, to provide point-in-time recovery. We have 2 oracle servers, one using redundancy policy (3) and the other using recovery window (2 days). I would like to standardize them but am not confident in which direction I should go in.
    I'm tempted to lean towards redundancy but wanted to pose the question to a wider, experienced audience for any things to think about/watch out for. Also, I assume the restore process would the same for either.
    Thanks in advance.

    Redundancy based retention policy means how many backups of each datafile must be retained and Recovery windows based retention policy is a period of time which starts with current time and goes backward in time upto the point of recoverability.
    Oracle suggests and its Best practice is "Recovery Window" .( I don't know the reason though)
    Two things you need to consider:
    1) You might need more space in case of "recovery window" because it depends upon the schedule of the backup. In "redundancy" , your space consumption will be same.
    2) You need to keep "recovery window" time less than the value of "control_file_Record_keep_time" so your backup records won't be overwritten in controlfile.
    We use "Recovery Window"

  • Long-term  retention backup strategy for Oracle 10g

    Hello,
    I need design a Archivelog, Level 0 and Level 1 long-term retention backup strategy for Oracle 10g, It must be based in Rman with tapes.
    ¿Somebody could tell me what it's the best option to configure long-term retention backups in Oracle?, "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1825 DAYS;" It's posibble ?
    Regards and thanks in advance

    Hello;
    RECOVERY WINDOW is an integer so yes its possible. Does it make sense?
    Later My bad, this is Oracle 11 only ( the gavinsoorma link ) . Getting harder and harder to think about 10. Don't think I would use RECOVERY WINDOW.
    I would let the tape backup system handle the retention of your rman backups.
    Using crosscheck and delete expired commands you can keep the catalog current with the available backups on tape.
    Oracle 10
    Keeping a Long-Term Backup: Example
    http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmbackp.htm#i1006840
    http://web.njit.edu/info/oracle/DOC/backup.102/b14191/advmaint005.htm
    Oracle 11
    If you want to keep 5 years worth of backups I might just use KEEP specific date using the UNTIL TIME clause :
    keep until time 'sysdate+1825'More info :
    RMAN KEEP FOREVER, KEEP UNTIL TIME and FORCE commands
    http://gavinsoorma.com/2010/04/rman-keep-forever-keep-until-time-and-force-commands/
    Best Regards
    mseberg
    Edited by: mseberg on Dec 4, 2012 7:20 AM

  • Oracle data guard configuration for primary and standby db_name

    I am working on configuring an active data guard for one primary DB and one standby DB. I have a few questions:
    1. Can I use different db_name, db_unique_name and instance_name for primary and standby. For example: primary(db_name, db_unique_name and instance_name)=chicago. When I create standby DB with Rman backup and copy of pfile and control file from primary DB or use Grid control to create standby database. Oracle document or Grid control all keep standby db_name=chicago. Only make standby db_unique_name and instance_name=boston. Due to my application system condition, I want to make db_name=boston, not keep it as the same as primary=chicago. Is this valid configuration?
    2. In primary datafiles, application system generate datafile name like this: hr_chicago_01.dbf, fn_chicago_01.dbf. When I move datafiles to standby server, if I plan to use db_name=boston for standby DB, can I rename datafiles as
    hr_boston_01.dbf, fn_boston_01.dbf? In this way, datafile name match up with db_name. but I will create standby log group and members on primary and standby identically. If in future switching over, DB will not have problems.
    3. If I don't use primary DB backup. Instead, I copy all datafiles, redo_log files (no control files) to standby. Then "alter database backup controlfile to trace" from promary and also " create pfile='/xxx/initSTANDBY.ora' from primary. Then modify init.ora and controlfile. Then run control.sql to bring standby DB up. After that, configure redo log shipping and apply with data guard or SQL. Is this a acceptable way to create physical standby DB?
    Please advise your comments. Thanks in advance.

    I want to make db_name=boston, not keep it as the same as primary=chicago. Is this valid configuration?NO. DB_NAME must be the same ("chicago") at both sites. The Standby will be using a different DB_UNIQUE_NAME (e.g. "boston") and can be using a different Instance name / SID (e.g. "boston").
    can I rename datafiles Yes. The database file names can be changed.
    If I don't use primary DB backup. Instead, I copy all datafiles, redo_log files (no control files) to standbyWhat is the difference between the first sentence (a backup of the primary) and the second sentence (a copy of the primary) ? A Copy is a backup.
    Are you intending to differentiate between an RMAN Backup and a User-Managed (aka "scripted") backup ?
    Normally, for DataGuard, tou can use non-RMAN methods to copy the database but there's no value add in this.
    You'd still have to setup DataGuard ! (and I wonder if you'd have complications setting up Active DataGuard).
    But remember that you MUST create the Standby controlfile from the Primary and copy it over to your Standby -- particularly as you are planning to use DataGuard. This is not created by 'alter database backup controlfile to trace' , but by 'ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'filename''
    Hemant K Chitale

  • 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

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

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

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

  • Dataguard configured using RMAN not in sync with Primary

    Hi All.
    I have configured physical standby using RMAN it has errored out as below message since the Physical standby is came in Mount state and it is not in sync with Primary.
    $ rman target sys/oracle1@PROD_st_STBY auxiliary /
    Recovery Manager: Release 11.2.0.1.0 - Production on Sun Jul 29 13:27:02 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: PROD_ST (DBID=609107922)
    connected to auxiliary database: PROD_ST (not mounted)
    RMAN> duplicate target database for standby dorecover;
    Starting Duplicate Db at 29-JUL-12
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=156 device type=DISK
    contents of Memory Script:
    set until scn 239665;
    restore clone standby controlfile;
    executing Memory Script
    executing command: SET until clause
    Starting restore at 29-JUL-12
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: reading from backup piece /oracle1/oraerp/PROD_st/rman/07ngg1p6_1_1
    channel ORA_AUX_DISK_1: piece handle=/oracle1/oraerp/PROD_st/rman/07ngg1p6_1_1 tag=TAG20120719T140110
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
    output file name=/oracle1/oraerp/PROD_st/cont_.ctl
    Finished restore at 29-JUL-12
    contents of Memory Script:
    sql clone 'alter database mount standby database';
    executing Memory Script
    sql statement: alter database mount standby database
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 07/29/2012 13:27:29
    RMAN-05501: aborting duplication of target database
    RMAN-05001: auxiliary file name /oracle1/oraerp/PROD_st/undotbs1.dbf conflicts with a file used by the target database
    RMAN-05001: auxiliary file name /oracle1/oraerp/PROD_st/sysaux.dbf conflicts with a file used by the target database
    RMAN-05001: auxiliary file name /oracle1/oraerp/PROD_st/system01.dbf conflicts with a file used by the target database
    RMAN>
    SQL> select name,open_mode from v$database;
    NAME OPEN_MODE
    PROD_ST MOUNTED
    SQL> select name,db_unique_name,database_role from v$database;
    NAME DB_UNIQUE_NAME DATABASE_ROLE
    PROD_ST PROD_st_STBY PHYSICAL STANDBY
    SQL>
    SQL> alter database recover managed standby database disconnect;
    Database altered.
    SQL>
    SQL> alter system set log_archive_dest_state_2=enable;
    System altered.
    SQL> sho parameter log_archive_dest_2
    NAME TYPE VALUE
    log_archive_dest_2 string LOCATION=/oracle1/oraerp/PROD_
    st/arch/ VALID_FOR=(ALL_LOGFIL
    ES,ALL_ROLES)
    On Primary
    ==========
    SQL> SELECT THREAD# "Thread",SEQUENCE# "Last Sequence Generated"
    FROM V$ARCHIVED_LOG
    WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)
    ORDER BY 1; 2 3 4
    Thread Last Sequence Generated
    1 281
    ON STANDBY
    SQL> SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
    2 FROM
    3 (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
    4 (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
    5 WHERE
    6 ARCH.THREAD# = APPL.THREAD#
    ORDER BY 1; 7
    no rows selected
    SQL>
    SQL> SELECT THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# FROM V$ARCHIVE_GAP;
    no rows selected
    SQL>
    Please suggest solution.
    Best Regards,
    Edited by: user13707876 on 19-Jul-2012 02:04

    Hi,
    It has worked now since error with warnings encountered as below:
    $ rman target sys/oracle1@PROD_st_STBY auxiliary /
    Recovery Manager: Release 11.2.0.1.0 - Production on Sun Jul 29 15:57:39 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: PROD_ST (DBID=609107922)
    connected to auxiliary database: PROD_ST (not mounted)
    RMAN> duplicate target database for standby nofilenamecheck;
    Starting Duplicate Db at 29-JUL-12
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=156 device type=DISK
    contents of Memory Script:
    restore clone standby controlfile;
    executing Memory Script
    Starting restore at 29-JUL-12
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: reading from backup piece /oracle1/oraerp/PROD_st/rman/0enggc17_1_1
    channel ORA_AUX_DISK_1: piece handle=/oracle1/oraerp/PROD_st/rman/0enggc17_1_1 tag=TAG20120719T165607
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
    output file name=/oracle1/oraerp/PROD_st/cont_.ctl
    Finished restore at 29-JUL-12
    contents of Memory Script:
    sql clone 'alter database mount standby database';
    executing Memory Script
    sql statement: alter database mount standby database
    contents of Memory Script:
    set newname for tempfile 1 to
    "/oracle1/oraerp/PROD_st/temp01.dbf";
    switch clone tempfile all;
    set newname for datafile 1 to
    "/oracle1/oraerp/PROD_st/system01.dbf";
    set newname for datafile 2 to
    "/oracle1/oraerp/PROD_st/sysaux.dbf";
    set newname for datafile 3 to
    "/oracle1/oraerp/PROD_st/undotbs1.dbf";
    set newname for datafile 4 to
    "/oracle1/oraerp/PROD_st/users01.dbf";
    restore
    clone database
    executing Memory Script
    executing command: SET NEWNAME
    renamed tempfile 1 to /oracle1/oraerp/PROD_st/temp01.dbf in control file
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 29-JUL-12
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_1: restoring datafile 00001 to /oracle1/oraerp/PROD_st/system01.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00004 to /oracle1/oraerp/PROD_st/users01.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /oracle1/oraerp/PROD_st/rman/09nggc0j_1_1
    channel ORA_AUX_DISK_1: piece handle=/oracle1/oraerp/PROD_st/rman/09nggc0j_1_1 tag=TAG20120719T165547
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_1: restoring datafile 00002 to /oracle1/oraerp/PROD_st/sysaux.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00003 to /oracle1/oraerp/PROD_st/undotbs1.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /oracle1/oraerp/PROD_st/rman/08nggc0j_1_1
    channel ORA_AUX_DISK_1: piece handle=/oracle1/oraerp/PROD_st/rman/08nggc0j_1_1 tag=TAG20120719T165547
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
    Finished restore at 29-JUL-12
    contents of Memory Script:
    switch clone datafile all;
    executing Memory Script
    datafile 1 switched to datafile copy
    input datafile copy RECID=1 STAMP=789926299 file name=/oracle1/oraerp/PROD_st/system01.dbf
    datafile 2 switched to datafile copy
    input datafile copy RECID=2 STAMP=789926299 file name=/oracle1/oraerp/PROD_st/sysaux.dbf
    datafile 3 switched to datafile copy
    input datafile copy RECID=3 STAMP=789926299 file name=/oracle1/oraerp/PROD_st/undotbs1.dbf
    datafile 4 switched to datafile copy
    input datafile copy RECID=4 STAMP=789926299 file name=/oracle1/oraerp/PROD_st/users01.dbf
    ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 1 thread 1: '/oracle1/oraerp/PROD_st/redo.log'
    RMAN-05535: WARNING: All redo log files were not defined properly.
    ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 2 thread 1: '/oracle1/oraerp/PROD_st/redo_2.log'
    RMAN-05535: WARNING: All redo log files were not defined properly.
    ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 5 thread 0: '/oracle1/oraerp/PROD_st/log5.log'
    RMAN-05535: WARNING: All redo log files were not defined properly.
    ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 6 thread 0: '/oracle1/oraerp/PROD_st/log6.log'
    RMAN-05535: WARNING: All redo log files were not defined properly.
    Finished Duplicate Db at 29-JUL-12
    RMAN>
    So please suggest can i rename them all redolog file.
    Best Regards,

  • RMAN retention policy

    Hi,
    on 10g R2 on AIX6.1 , I have the followings :
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;My backup script :
    RMAN> run
          allocate channel t1 type disk;
          backup as compressed backupset format '$dir/df_%d_%T_%s_%p' database;
          sql 'alter system switch logfile';
          backup as compressed backupset format '$dir/al_%d_%T_%s_%p' archivelog all delete input;
          backup as compressed backupset format '$dir/ctl_%d_%T_%s_%p' current controlfile;
    crosscheck backup;
    delete noprompt obsolete;
    delete noprompt expired backup of database;But I have the backup files of 3th of March yet :
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110303_179_1 recid=171 stamp=744800219And the only file it deletes is :
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 14 days
    using channel ORA_DISK_1
    Deleting the following obsolete backups and copies:
    Type                 Key    Completion Time    Filename/Handle
    Backup Set           13404  18-MAR-11
      Backup Piece       13408  18-MAR-11          /appli/oracle/BACKUP/RMAN/INCR/MYDB/ctl_MYDB_20110318_339_1
    deleted backup piece
    backup piece handle=/appli/oracle/BACKUP/RMAN/INCR/MYDB/ctl_MYDB_20110318_339_1 recid=331 stamp=746072971
    Deleted 1 objectsShould not RMAN delete the backup files of before 15 of March ? Why it does not ?
    Thank for explanation ? Or more.

    Thank to all.
    We backup it every night (FULL at WE and incremental in week).
    list backup of database;
    List of Backup Sets
    ===================
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    7145    Full    571.86M    DISK        00:01:55     03-MAR-11
            BP Key: 7151   Status: AVAILABLE  Compressed: YES  Tag: TAG20110303T085658
            Piece Name: /appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110303_179_1
      List of Datafiles in backup set 7145
      File LV Type Ckp SCN    Ckp Time  Name
      1       Full 75445711   03-MAR-11 /data01/bases/MYDB/system01.dbf
      2       Full 75445711   03-MAR-11 /data01/bases/MYDB/psundots01.dbf
      4       Full 75445711   03-MAR-11 /data01/bases/MYDB/psdefault.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    19112   Full    772.42M    DISK        00:03:05     01-APR-11
            BP Key: 19118   Status: AVAILABLE  Compressed: YES  Tag: TAG20110401T121403
            Piece Name: /appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110401_60_1
      List of Datafiles in backup set 19112
      File LV Type Ckp SCN    Ckp Time  Name
      8       Full 152751106  01-APR-11 /data01/bases/MYDB/ptprc.dbf
      10      Full 152751106  01-APR-11 /index01/bases/MYDB/pttbl.dbf
      15      Full 152751106  01-APR-11 /data01/bases/MYDB/pttlrg.dbf
      19      Full 152751106  01-APR-11 /data01/bases/MYDB/ptprjwk.dbf
      20      Full 152751106  01-APR-11 /data01/bases/MYDB/ptaudit.dbf
      24      Full 152751106  01-APR-11 /data01/bases/MYDB/amlarge.dbf
      26      Full 152751106  01-APR-11 /data01/bases/MYDB/apapp.dbf
      27      Full 152751106  01-APR-11 /data01/bases/MYDB/aparch.dbf
      34      Full 152751106  01-APR-11 /data01/bases/MYDB/aucapp.dbf
      35      Full 152751106  01-APR-11 /data01/bases/MYDB/auclrge.dbf
      37      Full 152751106  01-APR-11 /data01/bases/MYDB/bdapp.dbf
      38      Full 152751106  01-APR-11 /data01/bases/MYDB/bdlarge.dbf
      40      Full 152751106  01-APR-11 /data01/bases/MYDB/bilarge.dbf
      42      Full 152751106  01-APR-11 /data01/bases/MYDB/caapp.dbf
      50      Full 152751106  01-APR-11 /data01/bases/MYDB/cuaudit.dbf
      54      Full 152751106  01-APR-11 /data01/bases/MYDB/cularge.dbf
      58      Full 152751106  01-APR-11 /data01/bases/MYDB/dpwork.dbf
      60      Full 152751106  01-APR-11 /data01/bases/MYDB/eobfapp.dbf
      64      Full 152751106  01-APR-11 /data01/bases/MYDB/eocmwrk.dbf
      71      Full 152751106  01-APR-11 /data01/bases/MYDB/eoecwrk.dbf
      74      Full 152751106  01-APR-11 /data01/bases/MYDB/eoepapp.dbf
      75      Full 152751106  01-APR-11 /data01/bases/MYDB/eoeplrg.dbf
      77      Full 152751106  01-APR-11 /data01/bases/MYDB/eoewapp.dbf
      81      Full 152751106  01-APR-11 /data01/bases/MYDB/eoiulrg.dbf
      84      Full 152751106  01-APR-11 /data01/bases/MYDB/eoltapp.dbf
      85      Full 152751106  01-APR-11 /data01/bases/MYDB/eoppapp.dbf
      88      Full 152751106  01-APR-11 /data01/bases/MYDB/eotplrg.dbf
      93      Full 152751106  01-APR-11 /data01/bases/MYDB/faapp.dbf
      95      Full 152751106  01-APR-11 /data01/bases/MYDB/fawork.dbf
      101     Full 152751106  01-APR-11 /data01/bases/MYDB/fgwork.dbf
      107     Full 152751106  01-APR-11 /data01/bases/MYDB/fowork.dbf
      109     Full 152751106  01-APR-11 /data01/bases/MYDB/fsapp1.dbf
      112     Full 152751106  01-APR-11 /data01/bases/MYDB/glapp.dbf
      122     Full 152751106  01-APR-11 /data01/bases/MYDB/inlarge.dbf

  • Rman retention window doubt

    Hello, i have RMAN backup in the way of backupsets on two node 11gR2 RAC on linux standard edition.
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters for database with db_unique_name MGW are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_mgw2.f'; # default
    RMAN>And now i dont understand why RMAN is not deleting backupsets that are older then 24 hours , although i have set
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS.
    I have in my rman script that is executing every day @ 23:00 this:
    backup as COMPRESSED BACKUPSET database FORMAT '/home/oracle/rman/%U' plus archivelog delete input;
    delete noprompt obsolete;And now i see in my rman backup folder that there is backupset from yesterdey 23:00 ,and also from the day before yesterday 23:00.
    [oracle@data02 rman]$ ls -l
    total 51889864
    -rw-r----- 1 oracle asmadmin 26454474752 Jul 14 00:19 0bmhcc1s_1_1
    -rw-r----- 1 oracle asmadmin     1245184 Jul 14 00:19 0cmhcg84_1_1
    -rw-r----- 1 oracle asmadmin 26626334720 Jul 15 00:18 0fmhf0ep_1_1
    -rw-r----- 1 oracle asmadmin     1245184 Jul 15 00:18 0gmhf4ih_1_1
    -rw-r--r-- 1 oracle oinstall           0 Jul 14 16:52 aa_1_1I thoght that if i have run my rman script today @ 23:00 , than that will do backup but also delete backup from the day before because i have set
    retention to 1 day .
    Can you please say why i am wrong in this ?

    The RMAN retention policy doesn't just keep the amount of days specified. It calculates the interval from the end of the current time and extends back in time for the number of days specifed.
    So for example if you set the backup retention policy to 1 day today. Then RMAN will keep the backups for 15th July, 16th July.
    Then on the 17th July, the 15th July backup will be obsolete.
    I.e.
    Current date   Status                                 Recovery Point
    15th July        available                               15-1 = 14th July
    16th July        available                               16-1 = 15th July
    17th July        backup of 15th July obsolete  17-1 = 16th July
    So your backup for today wouldn't be marked as obsolete until the 17th July.
    5 Configuring the RMAN Environment
    However, if you have a fixed-date database then you should be setting the retention policy to redundancy instead of recovery window.
    RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

  • RMAN -Retention policy doubt

    Hi,
    I have doubt on RMAN retention policy.
    we are taking daily cumulative backup and weekly Full database backup.
    And our retention policy is "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS"
    My assumption is that RECOVERY window of 3 days will hold the backups of 3 days and delete the previous backups,since we are taking cumulative backups,and using them database can be recovered.
    we used below commands to take cumulative backup.
    backup incremental level 1 cumulative as COMPRESSED BACKUPSET tag '%TAG' database include current controlfile;
    backup as COMPRESSED BACKUPSET tag '%TAG' archivelog all not backed up;
    Regards,
    mannu

    Thanks for reply.
    A recovery window is a period of time that begins with the current time and extends backward in time to the point of recoverability. The point of recoverability is the earliest time for a hypothetical point-in-time recovery, that is, the earliest point to which you can recover following a media failure. For example, if you implement a recovery window of one week, then this window of time must extend back exactly seven days from the present so that you can restore a backup and recover it to this point. You implement this retention policy as follows:
    In our case:
    Jan 24---Level 0 Full backup
    Jan 25-Cumulative backup
    Jan 26-Cumulative backup
    Jan 27--->Cumulative backup
    Jan-28 ----->cumulative backup
    What would be my point of recoverability? How my recovery window period of 3 days work here.
    Regards,
    Mannu

  • Number of Page View is showing zero for Site web Analytics Reports

    Hi,
    We have enabled Site Web Analytics reports in our Site Collection but the Number of Page views is showing zero for all the dates. We have checked all the events to capture in Site Collection Audit settings, Reporting feature is also activated but still the
    count shows 0 for all the dates.
    There are other Site Collection that exists under that Web Application but they show the count for Number of Page views in Site.
    Any help would be appreciated.
    Regards,
    Vijay

    hi
    1-first check "Usage and Health Data Collection Proxy" is started, if not started:
    find usage proxy id with following command:
    Get-SPServiceApplicationProxy
    then start service with following command:
    $UsageApp = Get-SPServiceApplicationProxy | Where {$_.ID -eq "[usage proxy ID]"}
    $UsageApp.Provision()
    2-check following link:
    Popularity Trends populating 0 results
    yaşamak bir eylemdir

  • Want to Use eHD for Primary Storage

    Good day,
    My question basically is: How do I change over to use my eHD as my primary storage instead of using it for back up through Time Machine? AND Can anyone explain how to do it as though I just plugged in a Mac for the first time yesterday?
    Background: About 2 years ago with some great advice from people who answered a previous post I purchased a 1TM OWC external HD.  I was down to 4GB left available on my internal and I find myself in a similar situation now with only 11.93GB left on my internal HD despite the 1TM eHD which is only a fraction full. 
    2 years ago when I originally connected my eHD I was given the option to store directly to eHD OR use it for back up through TM.  Being a novice to it all and for whatever reason, not sure why exactly but at the time I chose to back up through TM.  I was having issues with getting TimeVault turned off and was overwhelmed etc. etc. 
    Anyhow--flash forward 2 years later I am filling up my internal again with only the 11.93GB left that I mentioned.  According to OmniDiskSweeper a good 142.9GB of it is coming from my movies---mostly the events vs. projects of course but 142.9GB none-the-less.  I know when I import movies from my camera I can choose to direct them to the OWC but because the internal shows up first by default, sometimes I rush import without changing it to the OWC, hence filling up my internal.
    Basically what I really want to do is  store everything directly to the eHD and I am not sure how to do it.  Is there anyone that can walk me through the process in simple, simple terms?  Although I feel I've come a long way in 2 years I still consider myself a novice. 
    Yes, I have read many posts, threads, discussions but with different suggestions so not sure what is right.  I am not familiar with this stuff such so I end up being afraid to "try" any of it for fear of losing my pics, movies forever. Or having to re-do them somehow.  I read about just moving iMovie but too many options as to how and not sure which is right.  Most forums are for people who know more than I about this already and suggest things like change events to view by volume (did it) but then I read stuff like open volume where events are stored and drag to volume you want to store it.  Well for someone like me that raises more questions than answers.  What volume?  Do they mean in my case drag to the eHD?  Will this keep everything the same as I had it?  Will I still have my dates?  Titles?  Some discussions say copy.  Do they mean move?  Etc. Etc. Etc.
    Really I want to just store directly to eHD for primary.  I want to be able to open iMovie, iPhoto and have everything just like I do now but with all that glorius 1TB storage.  I don't want to redo anything---just move and run off the eHD.  Possible?  If I simply unplug my eHD and reconnect---will I get the option I did 2 years ago to store directly to the eHD?  
    UGH! 
    Message was edited by: dgc0225 to re-arrange wording just after posting

    Hi BDAqua,
    If it's "easy" I would consider getting another 1 to 2 GB. 
    I read a post before I posted here that referred me to Ken Stone's site about formatting and partitioning but I couldn't change the "Volume Scheme" like in his examples.  My real ones were greyed out so I didn't have the option to select.  And honestly--reading on it's pretty complicated (based on my lack of knowledge with this) and I'm afraid I would screw it up anyhow.  Anything else besides partitioning? 
    Anyone know what happens if I just turn-off Time Machine? What if I unplug the eHD and plug back in and start over?  Like a re-boot of sorts?  Too good to be true? 

  • Query on RMAN Retention Policy

    Hi, I have my Retention policy set to Redundancy 2
    I have taken 3 backups so far ( 2 Backup Sets, 1 Image Copy )
    When I check report obsolete I get the following
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    Report of obsolete backups and copies
    Type                 Key    Completion Time    Filename/Handle
    Backup Set           1      05-SEP-13
      Backup Piece       1      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T100934_92jllgn1_.bkp
    Backup Set           2      05-SEP-13
      Backup Piece       2      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_nnndf_TAG20130905T100949_92jllycp_.bkp
    Backup Set           3      05-SEP-13
      Backup Piece       3      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_ncsnf_TAG20130905T100949_92jln4d5_.bkp
    Backup Set           4      05-SEP-13
      Backup Piece       4      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T101030_92jln6cx_.bkp
    Backup Set           5      27-SEP-13
      Backup Piece       5      27-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_annnn_TAG20130927T120734_94bsqrj6_.bkp
    Backup Set           7      27-SEP-13
      Backup Piece       7      27-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_ncsnf_TAG20130927T120751_94bssf0j_.bkp
    Archive Log          305    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_138_95dv9okt_.arc
    Archive Log          306    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_139_95dv9px0_.arc
    Archive Log          307    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_140_95dv9r8f_.arc
    Archive Log          308    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_141_95dv9sk9_.arc
    Backup Set pieces 1,2,3,4 basically equate to my oldest backup - hence under redundancy of 2, I can see why that is obsolete
    5 and 7 were simply Control File/SPFILE backups from Auto Backup and the 2 newer backups of these have been taken since ( i.e. backupset pieces 9 and 10 )
    Q. What happens if I wanted to restore the database to the 27/09 ? What SPFILE and Control would it use ( presuming the OBSOLETE files had been removed out of the FRA ) ?
    Would I have to restore the removed backup set into the FRA, Cross Check and then restore the database via RMAN to the 27/09 ?
    Q. Why are some of today's ( 10/10/13 ) archive logs marked as OBSOLETE ?
    Q. If I wanted to have the ability to restore the database to 2 days ago, is perhaps a Rentention Policy of a 2 day Recovery Window perhaps better than my current Redundancy=2 policy ( combined with taking a daily backup ) ?
    any advice appreciated,
    Jim

    Q. What happens if I wanted to restore the database to the 27/09 ? What SPFILE and Control would it use ( presuming the OBSOLETE files had been removed out of the FRA ) ?
    Would I have to restore the removed backup set into the FRA, Cross Check and then restore the database via RMAN to the 27/09 ?
    - Yes you can get the database to the date which ever you want , using recover database until time.
    Q. Why are some of today's ( 10/10/13 ) archive logs marked as OBSOLETE ?
    - can you please provide the output of below command
    RMAN> show all;
    Q. If I wanted to have the ability to restore the database to 2 days ago, is perhaps a Rentention Policy of a 2 day Recovery Window perhaps better than my current Redundancy=2 policy ( combined with taking a daily backup ) ?
    - You can restore the database back  to two days or 5 days based on your requirement. You nee to recover the database using  until time option.
    Thanks,
    http://gssdba.wordpress.com

  • Remove Leading zeros for Material in Transformation

    Hi Experts,
    I'm using DTP first time. I don't have much exp on DTP & Transformations.
    I'm creating infocube with some objects. I want to remove leading zeros for zmaterial.
    In 3.x writen update routines as fallows:
    data: zmat(18) type c.
    zmat = COMM_STRUCTURE-/BIC/ZMAT.
    shift zmat left deleting leading '0'.
    result value of the routine
      RESULT = zmat.
    I'm confusing in Transfermation where to write this routines.
    I'm writing in Transformation as fallows:
    data: zmat(18) type c.
    zmat = SOURCE_FIELDS-/BIC/ZMAT.
    shift zmat left deleting leading '0'.
    RESULT = zmat.
    But it's getting remove zero's.
    Anybody suggest on this.
    Siri

    Dear Sir,
    No confusion at all.
    Just double click on the Target Infoobjct i,e Material object in Transformation, you will see a wizard popping up.
    There you will see a option called "RULE TYPE" and the default value will be "Direct Assignment". In the same check box click on the drop down icon and select "Routine".
    The moment you select the routine option, it will open up ABAP workspace where in you can write your routine and get the desired result.
    Hope it helps.

Maybe you are looking for