We'll assume you're ok with this, but you can opt-out if you wish. Accept Reject Read More. Close Privacy Overview This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent.
You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience. Necessary Necessary. Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information. Non-necessary Non-necessary.
Set the location of the flash recovery area. If the flash recovery area location is an Automatic Storage Management disk group named disk1 , for example, then you can do the following:. The files will still be known to the RMAN repository, however, and available for backup and restore activities. The backup retention policy specifies which backups must be retained to meet your data recovery requirements. This policy can be based on a recovery window the maximum number of days into the past for which you can recover or redundancy how many copies of each backed-up file to keep.
RMAN does not consider any full or level 0 incremental backup as obsolete if it falls within the recovery window. Additionally, RMAN retains all archived logs and level 1 incremental backups that are needed to recover to a random point within the window. This example ensures that you can recover the database to any point within the last week:. RMAN does not automatically delete backups rendered obsolete by the recovery window. As you produce more backups, RMAN keeps track of which ones to retain and which are obsolete.
RMAN retains all archived logs and incremental backups that are needed to recover the nonobsolete backups. Assume that you make a backup of datafile 7 on Monday, Tuesday, Wednesday, and Thursday. You now have four backups of the datafile. If you make another backup on Friday, then the Wednesday backup becomes obsolete. Sample output follows:. When you disable the retention policy, RMAN does not consider any backup as obsolete. Configuring the retention policy to NONE is not the same as clearing it.
Oracle does not delete eligible files from the flash recovery area until the space must be reclaimed for some other purpose. The effect is that files recently moved to tape are often still available on disk for use in recovery. The recovery area can thus serve as a kind of cache for tape. Once the flash recovery area is full, Oracle automatically deletes eligible files to reclaim space in the flash recovery area as needed. There are relatively simple rules governing when files become eligible for deleteion from the flash recovery area:.
In a Data Guard environment, archived redo log deletion policy governs when archived redo log files can be deleted from the flash recovery area. If, for instance, the RMAN retention policy requires keeping a set of backups larger than the flash recovery area disk quota, or if the retention policy is set to NONE, then the flash recovery area can fill completely with no reclaimable space.
However, the database continues to consume space in the flash recovery area until there is no reclaimable space left. The database handles a flash recovery area with insufficient reclaimable space just as it handles a disk full condition. Often, the result is an database hang, but not always. For example, if the flash recovery area is one of your mandatory redo log archiving destinations, and the database cannot archive a new log because the recovery area is full, then the archiver may, depending on your configuration, retry archiving periodically until space is freed in the recovery area.
For information on how a particular feature of Oracle responds to a disk full condition, see the documentation for that feature. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Helping communities build their own LTE networks. Podcast Making Agile work for data science. Featured on Meta.
New post summary designs on greatest hits now, everywhere else eventually. Related 5. The recovery area is defined by setting two initialization parameters. These two parameters can be dynamically altered or disabled. Enabling a Flash Recovery Area. Alter a Flash Recovery Area.
0コメント