DBAsupport.com Forums - Powered by vBulletin
Results 1 to 9 of 9

Thread: rman: CONFIGURE ARCHIVELOG DELETION

  1. #1
    Join Date
    Jul 2006
    Posts
    195

    rman: CONFIGURE ARCHIVELOG DELETION

    I am trying to configure RMAN to delete archive logs:

    I see this in the oracle documentation:

    You can use the CONFIGURE ARCHIVELOG DELETION POLICY BACKED UP integer TIMES TO DEVICE TYPE command to enable an archived log deletion policy. This configuration specifies that archived logs are eligible for deletion only when the specified number of archived log backups exist on the specified device type.

    Yet when I try different variations of this command (see below). I get
    the same error. Can this work with oracle 10.2.0.1.0? or can somebody
    give me the correct syntax.

    CONFIGURE ARCHIVELOG DELETION POLICY BACKED UP 2 times to device type;

    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "backed": expecting one of: "clear, to"
    RMAN-01007: at line 1 column 38 file: standard input



    Thanks in advance to all who answer this post.

  2. #2
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,555
    I would double-check if this is valid in Ora10gR2 - I think that's Ora11g syntax not valid on Ora10gR2
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

  3. #3
    Join Date
    Aug 2007
    Location
    Cyberjaya,kuala lumpur
    Posts
    340
    I think it's syntax problem, it is not working in 11g also, we need to crosscheck it...

    Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jul 14 12:42:15 2010

    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

    connected to target database: ORACLE (DBID=1593100988)

    RMAN> CONFIGURE ARCHIVELOG DELETION POLICY BACKED UP 2 times to device type;

    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "backed": expecting one of: "clear, to"
    RMAN-01007: at line 1 column 38 file: standard input

    RMAN>
    Last edited by gopu_g; 07-14-2010 at 05:24 AM.
    Thanks/Gopu

  4. #4
    Join Date
    Aug 2007
    Location
    Cyberjaya,kuala lumpur
    Posts
    340
    It Came up with 11G

    Archived log deletion policy enhancements

    When you CONFIGURE an archived log deletion policy, the configuration applies to all archiving destinations, including the flash recovery area. Both BACKUP ... DELETE INPUT and DELETE ... ARCHIVELOG obey this configuration, as does the flash recovery area. You can also CONFIGURE an archived redo log deletion policy so that logs are eligible for deletion only after being applied to or transferred to standby database destinations. You can set the policy for mandatory standby destinations only, or for any standby destinations.

    Examples
    =======
    RMAN> configure archivelog deletion policy to applied on standby;
    RMAN> configure archivelog deletion policy to applied on standby;
    RMAN> configure archivelog deletion policy to backed up 2 times to disk;
    Last edited by gopu_g; 07-14-2010 at 05:19 AM.
    Thanks/Gopu

  5. #5
    Join Date
    Aug 2007
    Location
    Cyberjaya,kuala lumpur
    Posts
    340
    And here is Ur output.

    RMAN> configure archivelog deletion policy to backed up 2 times to disk;

    new RMAN configuration parameters:
    CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
    new RMAN configuration parameters are successfully stored

    RMAN>
    Thanks/Gopu

  6. #6
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,555
    Quote Originally Posted by gopu_g View Post
    It Came up with 11G

    Archived log deletion policy enhancements...
    Thank you Gopu for taking the time to confirm this is a Ora11g enhancement. Syntax is just not supported on Ora10g.
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

  7. #7
    Join Date
    Jul 2006
    Posts
    195
    Thanks all, I appreciate your input/research.

  8. #8
    Join Date
    Nov 2000
    Location
    Pittsburgh, PA
    Posts
    4,166
    If you are using Oracle 10g there is another similar option that will let you control how many times each archive log is backed up.

    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO ${ARCHIVERETENTION};

  9. #9
    Join Date
    Aug 2007
    Location
    Cyberjaya,kuala lumpur
    Posts
    340
    Quote Originally Posted by gandolf989 View Post
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO ${ARCHIVERETENTION};
    Thanks Gandolf
    Thanks/Gopu

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width