Data Guard archive political deletion log

Similar Questions

• Data Guard problem (sequence of log says 1,2,3..)

  Hello
  
  I have a database (Prim) of production and ensure a physics database (Stand).
  
  Production down, I started standby (Stand) by the command 'alter database enable the database pending '.
  
  Now Eve will have production
  
  More I wanted to do (prim) database of production prior to standby controlfile and taking backup in sleep mode (stand)
  
  Restore on prim and mounted to the database.
  
  list of newspapers of record now shows log archiving as sequence 1,2,3,4...
  and the recovery does not occur.

  If you have flashbacks on, then Yes, you can restore [url http://nikolayivankin.wordpress.com/2012/02/14/dgmgrl-reinstating-ex-primary-to-standby-by-flashback-database-feature/] ex-primaires as before

  Otherwise, you only have to recreate the config.

• Purge logs archiving on things primary and Standby and for Data Guard RMAN

  
  Hi, I saw a couple of orders in regard to the purge archive records in a Data Guard configuration.

  Set UP the STRATEGY of SUPPRESSION of ARCHIVE to SHIPPED to All RELIEF;

  Set UP the STRATEGY of ARCHIVELOG DELETION to APPLIED on All RELIEF;

  Q1. The above only removes logs archiving to the primary or primary and Standby?

  Q2. If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

  I also saw

  CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED;

  Q3. That what precedes, and once again it is something that you re primary side?

  I saw the following advice in the manual of Concepts of data protection & Admin

  Configure the DB_UNIQUE_NAME in RMAN for each database (primary and Standby) so RMAN can connect remotely to him

  Q4. Why would I want my primary ro connect to the RMAN Repository (I use the local control file) of the standby? (is this for me to say define RMAN configuration settings in the Standby) manual

  Q5. Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

  Q6. If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

  Q7. Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

  Q8. What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

  Any idea greatly appreciated,

  Jim

  The above only removes logs archiving to the primary or primary and Standby?

  When CONFIGURE you a deletion policy, the configuration applies to all destinations archive

  including the flash recovery area. BACKUP - ENTRY DELETE and DELETE - ARCHIVELOG obey this configuration, like the flash recovery area.

  You can also CONFIGURE an archived redo log political suppression that newspapers are eligible for deletion only after being applied to or transferred to database backup destinations.

  If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

  Its a configuration, it will not erase by itself.

  If you want to use FRA for the automatic removal of the archivelogs on a database of physical before you do this:

  1. make sure that DB_RECOVERY_FILE_DEST is set to FRA - view parameter DB_RECOVERY_FILE_DEST - and - setting DB_RECOVERY_FILE_DEST_SIZE

  2. do you have political RMAN primary and Standby set - CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON ALL STANDBY;

  If you want to keep archives more you can control how long keep logs by adjusting the size of the FRA

  Great example:

  http://emrebaransel.blogspot.com/2009/03/delete-applied-archivelogs-on-standby.html

  All Oracle is worth a peek here:

  http://emrebaransel.blogspot.com/

  That what precedes, and once again it is something that you re primary side?

  I would never use it. I always had it put it this way:

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

  I would use only 'BACKED UP' for the data protection system. Usually it tell oracle how many times to back up before removing.

  Why would I want my primary ro connect to the RMAN Repository?

  Because if you break down, you want to be able to backup there, too.

  Also if it remains idle for awhile you want.

  Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

  Always use a database of catalog RMAN with Data Guard.

  If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

  Same answer as 5, use a catalog database.

  Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

  Same answer as 5, use a catalog database.

  What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

  I think cron is still, but they all work. I like cron because the database has a problem at work always reports its results.

  Best regards

  mseberg

  Summary

  Always use a database with RMAN catalog.

  Always use CRF with RMAN.

  Always set the deletion «To APPLY ON ALL STANDBY» policy

  DB_RECOVERY_FILE_DEST_SIZE determines how long to keep the archives with this configuration.

  Post edited by: mseberg

• Data Guard - RMAN removing archive log

  Hello

  I ' v DataGuard with physical standby.

  I do a backup only on the primaries. Both sites have ther separate backup systems.

  I ' v FRA and configured archivelog deletion with RMAN configuration:

  on primary: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

  standby: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;

  It works fine but I think what if scenarios and I'v qestion on best practices for backup after the transition of role management. Let's say that for some reason, as i'v in switch mode sleep for a few days and the backup will be posible to watch (now primary) database. What would be the steps/reconfiguration appropriate to do?

  1 should I reconfigure RMAN?

  change of new primary to: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

  change back to sleep again: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;

  2. make full backup

  Hello

  1. you can refer to the oracle documentation: http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#CHDCFHBG

  section: "all archived Redo Log deletion policy."

  Document provides the best algorithm to analysis of work

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

  
  

  If the deletion policy is configured with the BACKED UP integer TIMES clause, then a BACKUP ARCHIVELOG , the command copy newspapers, unless integer already exist on the specified device type backups. If integer are backups of logs, then the BACKUP ARCHIVELOG command ignores the newspapers. In this way, the deletion of archived newspaper policy works as a default NOT BACKED UP integer TIMES clause on the BACKUP ARCHIVELOG command. Note that you can override the deletion policy by specifying the FORCE option on the BACKUP command.

  The deletion of archived newspaper policy has also options specific to an environment Data Guard. , then RMAN can delete logs after they have been applied to all destinations remote mandatory. If you specify SHIPPED TO STANDBY , for example, then RMAN can remove log files when they were transferred to all destinations of mandatory relief.

  2. the paper provides good information, just to check and decide easily based on the functionality of the database role you can configure.

  It will be useful.

  -Thank you

  Pavan Kumar N

• Archiving logs apply frequency in Data Guard

  Dear all,
  
  How can we verify/set up the frequency archive newspapers should be applied to the Data Guard?
  
  Version: 10 g 2; OS: Windows 2003 R2 (64-bit).

  How we can configure the frequency of archive logs must be applied to the DG?

  Erase the question once more what you're expecing, as I understand, it's...

  It depends on the Redo genearation / Archive primary & network latency between primary databases & Eve.
  There is a configuration, you can change in the primary to put options such as delay , net_timeout and so on.

  consult this manual too.
  http://download.Oracle.com/docs/CD/B28359_01/server.111/b28294/log_arch_dest_param.htm

• RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

  Hi Oracle Community,

  I have a few databases (11.2.0.4 POWER 2 block and 12.1.0.2) with Data Guard. Back up this database with RMAN to ribbons, only on the primaries.

  During the backup, sometimes I got RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

  By reason of this global warning to backup status is "COMPLETED WITH WARNINGS". Is it possible to remove this warning, or perhaps change RMAN configuration to avoid the appearance of this warning?

  Concerning

  J

  Where is the problem on these warnings? If you do not want to see such warnings, why not simply to perform the removal of the archivelogs in a separate step? For example:

  RMAN> backup database plus archivelog;
  RMAN> delete noprompt archivelog all completed before 'sysdate-1';
  

• Removal of RMAN, Data Guard, and Archives journal

  Our DG Environment running Oracle 11 g R2
  We have a 3 node DG Environment with
  A primary being
  B and C being Active Data Guard Standby
  Backups are taken out of B and go directly to tape.
  Standby Redo Logs and fast recovery area are used
  
  
  
  Holding the recommendation of "Using Recovery Manager with Oracle Data Guard in Oracle Database 10g"
  RMAN primary control ('A')
  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED PENDING
  
  RMAN standby ("B") where the backup is performed
  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY
  
  RMAN set the other Standby ("C")
  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED PENDING
  
  How can we know what newspaper Archives are eligible to be removed from 'A' and 'C '?
  When remove it takes place?
  How can say us when archiving logs are deleted from the 'A' and 'C '?

  Dear user10260925,

  The documentation that you read is reliable but not enough.

  The Oracle can handle the archivelog directory and know that you are eligible for deletion. Stuff you posted here was derived from the books online and is supported and can be used when the Oracle knows and manages the archivelogs. This is simply called the flash recovery area. Please read the FRA at this very moment.

  Under the personal component normal circumstances in the industry use a few scripts to achieve on backup archivelog deletion.

  Here's a useful example to you;

  # Remove old archivelogs
  ######################################
  00,30 * * * * /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
  ######################################
  
  vals3:/home/oracle#cat /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
  export ORACLE_SID=optstby
  export ORACLE_HOME=/oracle/product/10.2.0/db_1
  cd /db/optima/archive/OPTPROD/archivelog
  
  /oracle/product/10.2.0/db_1/bin/sqlplus "/ as sysdba" @delete_applied_redo_logs.sql
  grep arc delete_applied_redo_logs.lst > delete_applied_redo_logs_1.sh
  chmod 755 delete_applied_redo_logs_1.sh
  sh delete_applied_redo_logs_1.sh
  rm delete_applied_redo_logs_1.sh
  rm delete_applied_redo_logs.lst
  

  vals3:/home/oracle#cd /db/optima/archive/OPTPROD/archivelog
  vals3:/db/optima/archive/OPTPROD/archivelog#cat delete_applied_redo_logs.sql
  set echo off
  set heading off
  spool /db/optima/archive/OPTPROD/archivelog/delete_applied_redo_logs.lst
  select 'rm -f ' || name from v$archived_log where applied = 'YES';
  spool off
  exit
  vals3:/db/optima/archive/OPTPROD/archivelog#
  

  Hope that helps.

  Ogan

• Archive Data Guard and Flashback

  Hello
  
  I have a DB 11.2.0.1 with a database of pending.
  If I put a few tables to be in the flashback data archive, (support for FDA tables) will be copied to a db as well sleep?
  
  concerning

  Hello;

  I hesitate to answer because you don't seem to close your old questions or give points to those who help. But I also believe in giving the benefit of the doubt.

  If the FIU is configured on your watch then the answer is Yes.

  While this is not a requirement to use I would always use FRA with Data Guard.

  db_recovery_file_dest = ' / u01/app/oracle/flash_recovery_area.

  The following are some sample parameter values that might be used to configure a physical standby database to archive its standby redo log to the fast recovery area:
  
  LOG_ARCHIVE_DEST_2 = 'LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(STANDBY_LOGFILE,STANDBY_ROLE)' LOG_ARCHIVE_DEST_STATE_2=ENABLE
  

  Source

  DataGuard of Concepts and Administration 11g Release 2 (11.2) E10700-02

  With RMAN efficiently in an environment of Dataguard. [848716.1 ID]

  Best regards

  mseberg

  Published by: mseberg on December 1, 2012 13:53

• How to move from Data Guard time really apply (restore) to archive the journal

  Hello
  
  Standby database configured with broker and application really remake in time; However, I want to change it to archive the journal apply mode without losing the broker configuration. Is this possible? If it is not possible to use the broker to make archive log apply, I can remove the broker and use Data Guard to set up the day before to use the archive log apply?
  
  Concerning

  Hello;

  Broker automatically allows real-time applies to databases on hold if the standby database has standby redo logs configured.

  Stop repeat applies

  DGMGRL> EDIT DATABASE 'PRIMARY' SET STATE='APPLY-OFF';
  

  Repeat restart applies broker

  DGMGRL> EDIT DATABASE 'PRIMARY' SET STATE='APPLY-ON';
  

  In order to get rid of standby redo logs would be a way. I would like to leave myself alone. Real time assistance to prevent the loss of data.

  Best regards

  mseberg

• Can a weird question we use Data Guard to apply the bidirectional log?

  Hi I have a question about Data Guard, can we use Data Guard to apply the bidirectional log? I mean keeping the two of them primary and standby to Active status (read write Mode).
  
  Maybe my question seems silly, but I just wanted to check on it.
  
  Thank you

  Laughing out loud

  That Golden Gate or water courses that will work in two ways. One or the other. Puts additional requirements on the hardware is the downside.

  Data Guard does not do that.

• Restore the size of the log in Data Guard configurations

  DB version: 11.2
  Platform: Solaris 10
  
  We have currently a DB production which is not Dataguard.It has a load of joint working: some processing OLTP and batch.
  Its size of redo log is * 100 * MB.
  
  We will create a database with the requirement very similair but this DB will have primary standby (Data guard) and real time applies.
  
  To adapt to the requirements of dataguard, we should reduce the size of the recovery online newspapers? That is to say. Transport of small pieces of roll forward is better than carrying more. Right?

  Hello;

  If you use "real-time applies" the key is not the size so that the standby Redo Logs.

  In most cases, 100 MB is fine. Newspapers to sleep again must be the same size that it again.

  With 'real time applies' SRL act as a buffer.

  Unless you have a real problem with the size of do it again I would not change it.

  An excellent source of information on this is 'Restore the Services of Transport' in ' Data Guard Concepts and Administration 11 g Release 2 (11.2) "E10700-02".

  If you believe that your logs are too big departure "Troubleshooting performance problems with the database and base/MFG MRP [ID 100964.1]"

  Best regards

  mseberg

  Published by: mseberg on May 31, 2012 11:33

• RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  I get RMAN-08120: WARNING: journal archived not deleted, not yet applied watch on primaries
  but when I run under query, I get the same result of primary and backup
  
  SQL > select max(sequence#) from v$ archived_log;
  
  MAX(SEQUENCE#)
  --------------
  44051
  
  SQL >
  
  
  Eve is a log switch behind only!

  Hello;

  If RMAN tries to remove an archive which is not yet applied in standby log, you see the RMAN-08120

  It's a good thing. As long as you don't have any archives for days on standby, you probably don't have a problem.

  What are your RMAN settings for the database of the day before?

  MetaLink Note: 361182.1 can help too. Or Note 1079953.1

  Your main, make sure that:

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
  

  Please consider closing some of your old issues to clean up the forum.

  Best regards

  mseberg

• Check the log to delete oracle data file to be deleted from the root user.

  Any body can help me find the log to make sure all traces of the data files that are deleted from the root to the hp - ux Server user (and the sys log has already been modified by the root user).
  So is there a way to check the database or deleted from server level to check track of log files data files.

  Salvation;

  If, you don't have no OS level verification that it is difficult to find to answer your quesiton. For example, our system of verification on OS (also root password no case) and Db level.

  PS: @Sybrand thanks, I missed that part.

  Respect of
  HELIOS

• Additional logging with Oracle 10 g 2 streams and Data Guard

  Hello
  
  I have a physical environment with DB Oracle 10 g 2 and Standby with Data Guard DR CONF. At the present time, this environment will be extended to a pattern of replication using 2-way Oracle Streams Replication (for replication to the central office of this branch, other channels will be added soon). The primary DB is replicated to the other primary DB (at the telephone exchange remotely).
  
  So, there's my question: it is completely necessary to specify an additional record on data sources (primary) to set the 2-way Streams replication? and, if it is completely necessary, then, can configure additional connection on primary without affecting their physical Standby, or what I have to do something special?
  
  Thanks in advance.

  Yes, for the streams you need additional registration. There is no impact on databases physical standby.

• Data Guard: Primary descends from secondary crashes

  Hi Oracle experts.

  IM using Oracle Data Guard to the physical configuration of HA standby.

  I have primary with 70G of political RMAN and as noted flash recovery area size:

  RMAN > show all.

  using the control file of the target instead of recovery catalog database

  RMAN settings for database with db_unique_name MSEORCL are:

  CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default

  CONFIGURE BACKUP OPTIMIZATION # by default

  SET UP DEFAULT DISK DEVICE TYPE; # by default

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default

  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default

  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default

  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default

  CONFIGURE ENCRYPTION OF DATABASE # by default

  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default

  CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;

  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / opt/oracle/base/product/11.2.0/dbhome_1/dbs/snapcf_mseorcl.f'; # by default

  Size of the flash area is also pending physical (secondary node) 70G. and policies as described for RMAN:

  RMAN > show all.

  using the control file of the target instead of recovery catalog database

  RMAN settings for database with db_unique_name MSEOS3 are:

  CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default

  CONFIGURE BACKUP OPTIMIZATION # by default

  SET UP DEFAULT DISK DEVICE TYPE; # by default

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default

  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default

  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default

  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default

  CONFIGURE ENCRYPTION OF DATABASE # by default

  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default

  CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;

  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / opt/oracle/base/product/11.2.0/dbhome_1/dbs/snapcf_mseos3.f'; # by default

  Everything works fine as long as the two sites are on the rise, & I have cron job to remove the archive log has expired.

  Now, if I stop the secondary node, the head node site also goes to error state & watch special suite:

  ERROR:

  ORA-00257: archiver error. Connect internal only, until this just released.

  I checked the size of the log archive and its just Mo 837...

  My expectation is it should continue to operate until all 70 G are used. why he throws error so early? Please give me some advice if Im missing something here...

  ~ S.

  Do you mean by reliable?

  It will be permanent if you apply via dgmgrl database pending:

  Change the property set of database my_standby_db Binding = "optional."

  See the detailed database my_standby_db

  You must ask it also on the primaries for the cases of change of role, but for now, you need to change it for the day before to take effect.

  If the archivelogs can be deleted are beeing shipped in standby mode.

  Making the optional standby destination will prevent them from beeing deleted primary until shipped it standby after the host is again.

  Concerning

  Thomas