My Oracle Support Banner

Administering and Customising catalog.txt for Backup and Recovery (Doc ID 857446.1)

Last updated on JULY 01, 2024

Applies to:

Oracle Fusion Middleware - Version 10.1.2.0.0 to 10.1.2.3.0 [Release AS10gR2]
Information in this document applies to any platform.
Oracle Application Server 10g Enterprise Edition - Version: 10.1.2.0.0 to 10.1.2.3.0


Purpose

The goal of this document is to group together a set of related questions concerning catalog management for OracleAS  10g Backup and Recovery. It is targeted at any Oracle Administrator or Systems Administrator responsible for Backup and Recovery.

Questions and Answers

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Purpose
Questions and Answers
 How to automatically purge old backups taken using the AS Backup and Recovery tool.
 Is there any automated implementation of Retention Policies in AS 10g?
 As the database component of any AS home containing a metadata repository will be backed up using RMAN, are any steps necessary to update RMAN before deleting the backup files?
 As per Oracle Application Server Administrator's Guide, "
20.6.4 Purging Backups and Moving Them to Tertiary Storage", the Backup and Restore Tool saves records of successful backups in a catalog file (data/catalog.txt) in the backup_restore directory. How is $ORACLE_HOME/backup_restore/data/catalog.txt cleared down?
 Is it supported to manually edit out entries from  $ORACLE_HOME/backup_restore/data/catalog.txt?
Once an entry is removed from the file it is no longer possible to do a restore operation corresponding to that entry's backup timestamp. As long as the corresponding backup has already been deleted this would cause no problem.
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.