The newspaper to R12 retention policy

Similar Questions

• What is the Mozilla user data retention policy unique identifier?

  I read recently in the privacy policy of FF that an ID unique browser is sent to Mozilla with an IP address whenever the browser checks the updates:

  "This function sends also potentially personal information to Mozilla in the form of your IP address and a cookie that contains a unique numeric value to distinguish various Firefox installs."

  http://www.Mozilla.org/en-us/legal/privacy/Firefox.html

  This feature can potentially, provide a list complete IP addresses and sites that a user used to access the Internet, Mozilla. Can you please clarify your data retention policy? In other words, how long are the IP address or other identifier stored on your servers?

  Hello! I'm chime of the Mozilla Privacy team.

  For RFT pings, we don't hold anything in FHR > 6 months (180 days). That answer your question? Here is a link to the info - it's under "how enable or disable sharing of data".

  https://support.Mozilla.org/en-us/KB/Firefox-health-report-understand-your-browser-perf

• The Archive Log backup retention policy

  How can I define retention policy for backups of the log of the Archives?

  The question and the answer that you have marked as "Right answer" is misleading.

  For removal of journal policy archived, see below.

  Configuration of RMAN environment

  For the real question displayed "How can I define retention policy for backups of the log of the archives?", see link below. ""

  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#i1019318

  Also, have you started the thread to clear your doubts or test other users of the forum?

  Thank you!!

• Change the database with PowerCLI retention policy

  Anyone know if you can change the settings for retention policy database of vCenter with PowerCLI (Powershell v1.0)?

  The settings I want to modify are:

  The administration | vCenter Server Settings | Data retention policy. For tasks AND event held for

  I am using vCenter 4 update 4.

  I see, in this case we will have to fall back on the underlying method of the SDK.

  Try like this (you must be connected to the vCenter)

  $si = Get-View ServiceInstance $optMgr = Get-View $si.Content.Setting
  
  $spec = @()
  
  $event1 = New-Object VMware.Vim.OptionValue $event1.key = "event.maxAge"
  $event1.value = 120 $spec += $event1
  $event2 = New-Object VMware.Vim.OptionValue$event2.key = "event.maxAgeEnabled"
  $event2.value = $true$spec += $event2
  $task1 = New-Object VMware.Vim.OptionValue$task1.key = "task.maxAge"
  $task1.value = 120$spec += $task1
  $task2 = New-Object VMware.Vim.OptionValue$task2.key = "task.maxAgeEnabled"
  $task2.value = $true$spec += $task2
  $optMgr.UpdateOptions($spec)
  

• Query on the RMAN retention policy

  
  Hi, I have my retention set to 2 redundancy policy

  I took 3 backups so far (2 sets of backup, 1 copy of the Image)

  When I check the obsolete report I get the following

  RMAN retention policy apply to the order

  RMAN retention policy is set to 2 redundancy

  Report of obsolete backups and copies

  Making key time filename/handle type

  -------------------- ------ ------------------ --------------------

  Backup 1 05-SEP-13 set

  Exhibit 1 backup /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T100934_92jllgn1_.bkp 13-SEP-05

  Backup 2 05-SEPT-13 set

  Exhibit 2 backup /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_nnndf_TAG20130905T100949_92jllycp_.bkp 13-SEP-05

  Backup 3 05-SEPT-13 set

  Save the song 3 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_ncsnf_TAG20130905T100949_92jln4d5_.bkp 13-SEP-05

  Backup 4 05-SEPT-13 set

  Save the 4-13-SEVEN piece. 05 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T101030_92jln6cx_.bkp

  Backup 5 27-SEPT-13 set

  Save the song 5-/home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_annnn_TAG20130927T120734_94bsqrj6_.bkp 13-SEP-27

  Backup the value 7 13-SEP-27

  Save the song 7 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_ncsnf_TAG20130927T120751_94bssf0j_.bkp 27-SEP-13

  Archive newspaper 305 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_138_95dv9okt_.arc

  Archive newspaper 306 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_139_95dv9px0_.arc

  Archive journal 307 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_140_95dv9r8f_.arc

  Archive newspaper 308 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_141_95dv9sk9_.arc

  Backup 1,2,3,4 set elements are essentially equivalent to my older backup - so under a redundancy of the 2, I can see why it is obsolete

  5 and 7 were simply command file/SPFILE AutoSave backups and the 2 most recent backups of them have since been taken (backupset parts 9 and 10)

  Q. what happens if I wanted to restore the database to the 27/09? What control and SPFILE he would use (assuming that OBSOLETE files had been removed from the FRA)?

  If I have to restore the backup set removed in the FRA, Cross Check and restore the database using RMAN to 27/09?

  Q. Why are some today (10/10/13) archival newspapers marked OBSOLETE?

  Q. If I wanted to be able to restore the database for 2 days, is perhaps a policy of conservation of a day 2 Recovery window might be better than my current redundancy = 2 policy (associated with a daily backup)?

  any advice appreciated,

  Jim

  Yes, the BackupPieces names.

  A BACKUP of the LIST would show the content of BackupSets and BackupPieces.

  Hemant K Collette

• in R12, we create magazines... Once created newspapers, we approve it. Then, there are some workflows processed will be made. Meanwhile, newspaper notification will be sent to the contractor of the person who throws the newspaper.  now that I could f

  in R12, we create magazines... Once created newspapers, we approve it. Then, there are some workflows processed will be made. Meanwhile, newspaper notification will be sent to the contractor of the person who throws the newspaper.  now, I could find the type of item for this workflow is: GLBATCH but you want to know the complete workflow process. for this I need wft file name.  Please tell us how to get the wft file.

  Workflow type: sheet

  Hello

  I ran these commands from a remote session (PuTTY, for example):

  CD GL_TOP/patch/115/import/US $

  grep 'ITEM_TYPE "GLBATCH" ' * wft

  I don't think this information is found in any table.

  Kind regards

  Bashar

• Problems with the retention policy that removes a Cumulative incremental backup

  Hello

  I have following two scripts:

  1 RMAN script runs the weekend and made a full backup of level 0.

  2 RMAN script works on a daily basis and a level 1 Cumulative backup.

  at the end of each script I delete noprompt obsolete redundancy 1; (I don't need a single copy of local disk)

  My problem is that it seems that remove obsolete handles only level 0 (full) backups.

  for example, my goal is:

  Saturday = > level 0 + delete obsolete (level 0 + all the incremental)

  Sunday = > obsolete level 1 cumulative + delete

  Monday = > level 1 cumulative + Delete obsolete (backup Sunday)

  etc...

  What happens in reality is rather that remove obsolete Monday, completely ignores Sunday 1 cumulative level.

  and he keeps all the up to the next level 0 backup

  its actually covered in the Oracle Documentation:

  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV8400

  but it's just not make sense.

  in order to have redundancy of 1 copy I only need to level 0 + unique Level 1 cumulative backup.

  I don't have level 0 + all level 1 cumulative backups between full backups.

  
  

  so my question is there a way to make the retention policy to keep only the last level 1 cumulative?
  

  It's true window of 1 day recovery ignores several backups of cumulativ made the same day as being obsolete. Regular retention strategies rman probably cannot provide what you want. You can manually identify the backupset and delete them or change of cumulativ backups to incremental backups.

  That would save the space of several cumulative backups and and would work even for several backups on the same day. Of course with the disadvantage that you need all of the incremental backups and your recovery time may be longer

• Retention policy for the grid control

  Hello

  One of our clients wants to change the retention policy of the Grid control to 2 years in order to check the statistics of the application of these last 2 years,

  Default purge policy is as follows:

  Raw metrics - 7 days

  An hour aggregate metrics data - 31 days

  A day aggregate metrics data - 365 days

  Having someone of you will never change these default policies to a great values?

  I'm afraid of performance issues

  Depends on what policy they want change, but I n ' tthink this will help you at all.  If they are looking for AWR data, it is not stored in MS, unless you configure CWA warehouse.   EM will be measures such as SQL response time, but it does not store the SQL query and the stats you'd see in an AWR report.   Storing so for 2 years will not help.  If you want just generic performance history, then changing strategies of purge will be fine, but you don't want to store the raw data for 2 years. Keep in mind that you will increase the size of your repository database as well.

• Recovery window retention policy removes the archive logs before backup?

  Hi all

  Oracle 11G on Windows 2008 R2

  This afternoon, I've changed my retention policy RMAN "RETENTION POLICY 3 REDUNDANCY"on RECOVERY WINDOW OF 3 DAYS RETENTION POLICY

  However, I checked tonight and after that my daily backup, all the archive before backup logs had been removed! So that means I don't think I can restore to any point in time, before my daily backup. All newspapers .arc were there after the backup. Then I tried another test and began the daily backup again. During the backup process, archive logs were deleted again! Now, I don't have any archives of newspapers...

  Is this good behavior OF RETENTION POLICY RECOVERY WINDOW? I thought that she would keep all the files needed for to restore me to any point in time for the previous 3 days. When I used a REDUNDANCY, with my daily backups, he kept 3 days of backups + archiving logs so that I could restore point-in-time at any point. How can I use WINDOW RECOVERY so that I can actually restore to any point in time for the 3 days?

  I wanted to change WINDOW of recovery, since I read that using the REDUNDANCY, it keeps only X copy a backup (so if I ran the backup 3 times a day, I would have only these 3).

  Thanks in advance.

  After a database RESTORE, Oracle tries to RECOVER a DATABASE.  He tries to 'find' the archivelogs for this phase in the location expected archivelog.  If they are NOT present in the location expected archivelog, it attempts to restore backups before applying them.

  Since your BACKUP... DELETE ENTRY deletes the archivelogs after that that they are saved, Oracle will have to use backups to recover the archivelogs.

  Hemant K Collette

• backup with the retention policy to recovery of N days window

  Hello

  I did command to create an incremental backup of database with the configuration:

  run

  {

  Configure retention policy to recovery of 14 days window;

  backup incremental level 1 cumulative

  tag daily_incr_14_days

  database

  more archivelog delete all input;

  }

  All parameters are set to their default values, and backups of data goes to FRA. I've got catalog recovery connected and all the views RC_ at my disposal.

  (1) is it possible to know which window of recovery has been used for any command in the rman backup or query view RC_ or local database (control file information)?

  (2) if I use other settings of window of recovery with command configures which would overlap or report rman commands do?

  BR

  Sandrine.

  TenakaKhan wrote:

  Mahir,

  Thanks for the reply - in other words, this window of recovery should be used mainly for maintenance purposes (overlap, remove obsolete, report need backup etc.) and he was not associated with the actual with backup items as retention period "keep until the" safeguard clause... command database (this information are saved with the backup as I could verify according to rc_backup_set of the recovery catalog)?

  Yes.

  Maintaining backups RMAN and repository & nbsp; Reviews

  keepOption

  backup retention policy

  A policy defined by the user to determine how long the backups and archived logs must be kept for the media recovery. You can define a retention policy in terms of redundancy backup or a recovery window.

  RMAN keeps backups of data files that are required to meet the current retention policy, and all logs archived redo necessary to a complete recovery of data files.

  Recovery window

  A recovery window is a type of RMAN backup retention policy, in which the ADMINISTRATOR specifies a period of time and RMAN ensures the retention of backups and Archives redo logs required for recovery to point-in-time at any time during the recovery window.

  The interval always ends at the present time and is extended in time for the number of days specified by the user. For example, if the retention policy is set for a window of recovery of seven days and the current time is 11:00 Tuesday

  RMAN maintains the necessary backups to recover point-in-time at 11:00 the previous Tuesday.

  Concerning

  Mr. Mahir Quluzade

• Images of base and the retention policy

  How often should a kernel take images of basic officer? For some reason, I was under the impression that base image that is happening, then EACH snapshot after it is progressive, and they all get just rolled in the other when the time comes. I have machines here with 3 or 4 images of base in recent months. Some seem to match with my retention policy, and others do not.

  Someone has an idea?

  You answer @itcaswg post:
  @itcaswg said "why it would trigger a full after a 'dirty '?" I think it would just dump the partial and take another differential from the beginning.

  So when your taking a backup create us a log, which is replaced each snap, in the System Volume information file, this is where we consider what has changed since the last backup and what channel we are linking to the heart. If the officer was in the middle of a write to this file and a crash occurs the log file might be damaged. This would make it impossible for the officer to determine what has changed. So, I set off a baseline plan to repair the chain.

  @itcaswg said «...» I guess that number three is not a problem unless the disk is full. right? »

  Yes and no. Permissions or GP can play in this trigger. Also when you configure you differential interval and place all the volumes on the same time, all volume lock in that time as a job. The partition of the RPS is relatively small and can fill. This can trigger the basis for the entire machine as all volumes are connected by the work of the interval. Often RPS do not even have a drive assigned to often most watched his letter but he too has a SVI folder and is clipped like any other drive.

  In addition, food for thought, your retention applies only at increments up to your most recent base line. Anything before that is ignored and must be cleaned manually.

• Basic question on redundancy as the retention policy enforcement

  DB version: 11 g
  
  I intend to implement a differential incremental backup of my database. My strategy is
  

  Sunday -->     Level 0 backup
  Monday -->     Level 1 backup
  Tuesday-->     Level 1 backup
  Wednesday-->     Level 1 backup
  Thursday-->     Level 1 backup
  Friday-->     Level 1 backup
  Saturday-->      Level 1 backup
  
  Again, the new weekly backup cycle starts
  Sunday -->     Level 0 backup
  Monday -->     Level 1 backup
  .
  .

  Set on the Recovery window retention policy
  ==========================
  
  I understand that recovery window retention policy: If I set up

  'CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;' 

  This means only these backups that are older than 7 days will be reported as obsolete when executing the command "remove obsolete.
  
  Retention set on redundancy policy
  =============================
  
  But I'm a little confused about the retention set to redundancy policy:
  
  Does

  CONFIGURE RETENTION POLICY TO REDUNDANCY 3;

  say that you keep 3 copies of backups on different locations on disk? How does this fit with my above mentioned incremental backup strategy?

  REDUNDANCY is 'Keep' copies

  The BACKUP is 'Create' copies of

  Copies which exceed the requirement of REDUNDANCY become OBSOLETE.

  Hemant K Collette

• Question on the implementation of the RMAN retention policy

  Version: 11 g
  OPERATING SYSTEM: AIX 5.3
  
  
  I intend to implement a differential incremental backup of my database. My strategy is
  

  Sunday -->     Level 0 backup
  Monday -->     Level 1 backup
  Tuesday-->     Level 1 backup
  Wednesday-->     Level 1 backup
  Thursday-->     Level 1 backup
  Friday-->     Level 1 backup
  Saturday-->      Level 1 backup
  
  Again, the new weekly backup cycle starts
  Sunday -->     Level 0 backup
  Monday -->     Level 1 backup
  .
  .

  First script to perform the backup of level 0 - this script will be run by a cron job every Sunday morning 02:00
  ==================================================================

  run{
  crosscheck backup;
  crosscheck archivelog all;
  crosscheck copy;
  crosscheck backup of database;
  crosscheck backup of controlfile;
  delete noprompt obsolete device type disk;
  }
  
  
  run {
  allocate channel ch1 device type disk;
  backup incremental level 0 format '/u07/rman_backup/FULL_%d_%u' database tag "weekly_full";
  backup format '/u07/rman_backup/RMAN_CTL%s:%t:%p.bkp' current controlfile;
  --release channel ch1;
  allocate channel ch1 device type disk;
  backup (archivelog all  format='/u08/rman_backup/archbkp_dir/ARCH_%d_%T_%u_s%s_p%p' DELETE INPUT TAG "archivelogs");
  release channel ch1;
  }

  The second script for differential incremental backup at level 1 for the next 6 days. This script will run every day
  at 02:00 from Monday to Saturday by a cron job. I have 6 scripts like below, the only difference being the tag "Monday-level 1", "Tuesday-level1"... etc.
  =======================================================

  run{
  crosscheck backup;
  crosscheck archivelog all;
  crosscheck copy;
  crosscheck backup of database;
  crosscheck backup of controlfile;
  delete noprompt obsolete device type disk;
  }
  
  
  run {
  allocate channel ch1 device type disk;
  backup incremental level 1 format '/u07/rman_backup/RMAN_DBF_%s:%t:%p.bkp' database tag "Monday-level1";
  backup format '/u07/rman_backup/RMAN_CTL<%s:%t:%p>.bkp' current controlfile;
  --release channel ch1;
  allocate channel ch1 device type disk;
  backup (archivelog all  format='/u08/rman_backup/archbkp_dir/ARCH_%d_%T_%u_s%s_p%p' delete input tag "archivelogs");
  release channel ch1;
  }

  Question1.
  I want to as backups to become obsolete and deleted as below

  At the end of every week's backup cycle.ie Just after taking a new Sunday's level 0 backup, 
  i need all the old level 1 and level 0 backups from the previous week to get deleted.

  The setting persist following should do the trick. Right?

  CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

  Question2.
  Since

  CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

  is defined. When the new backup cycle begins next Sunday, RMAN should delete the backup of level 0 of last Sunday. Ideally, RMAN should remove all its ' (child) of level 1 backups to Saturday because it makes no sense to keep these level 1 backups when its parent 0 level was obseleted and deleted. RMAN removes level 1 level 0 backup child deleted backups Sunday (when the new backup cycle begins)?
  
  Question3:
  Suggestions that you guys have about the scripts above?
  
  Published by: resistanceIsFruitful on October 30, 2009 06:04

  You have answered your question yourself in your question, when you understand

  Ideally RMAN should remove all its ' other (children) level 1 backups to Saturday because it makes no sense to keep these level 1 backups when its parent 0 level was obseleted and removed_

  Yes indeed RMAN done, did you check it yourself?

  Khurram

• Custom data retention policy

  Hi all

  Is it possible to set up below the retention to Foglight (5.6.10) policy.

  * Save 10 minutes for 90 days and then purge *.

  Kind regards

  Roshan Varughese

  Hi Roshan,

  You must set all three generations in the custom retention policy to preserve data for 10 minutes.

  Please find the custom in FMS UI retention policy under: management data/servers/server management / retention policy/policy current. Here, select the menu drop-down and click custom.

  Once there you should be able to select 10 minutes for each generation, then purge the data after 3 months. (see image below)

  Keep in mind that political detention is very granular and the size of your database is likely to increase. Also, when you use larger slots in the user interface, the server will have to deal with more values and will add a certain amount of overhead.

  More information in Foglight documentation - creation of custom retention policies.

  

  Gaston.

• RMAN retention policy

  Hello everyone, I think to create a retention policy, but the problem is if I want to have the backup that ran daily from detention for 15 days and each backup run a monthly backup for a year which is the best option to set up the recovery window retention policy, because if I set with 365 days I'm going to keep daily backups for the whole year, suggest or advise

  Hello

  set the retention policy for 15 days (daily policy):

  RMAN > CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 60 DAYS;

  And add keep until 'sysdate + 365' monthly backup.

  RMAN > backup format incremental level 0 '% d.n0.%T.set_%s_%t' TAG data = 'BK_DATA_monthly_20150501' keep until 'SYSDATE + 365' opens a session;

  If you can make backup maintenance with delete obsolete;

  RMAN > remove force noprompt obsolete;

  
  

  It works with oracle 9i, 10g and 11g