How to Delete RMAN Backups in Oracle: Step-by-Step Guide

Managing Oracle RMAN backups effectively is essential for optimizing storage space and database performance. In this guide, we will explore how to delete RMAN backups, understand the role of the control file, and handle expired backups properly.

🗑️ How to Delete Backups in Oracle RMAN?

To delete backups, follow these steps:

1️⃣ Deleting Backups Using RMAN (Recommended Method)

✅ First, connect to RMAN:

rman traget /

✅ To delete all backups in a specific location:

Delete backup;

This command removes all backups from the physical storage and updates the control file accordingly.








Deleting Backups Using Linux rm Command (Manual Method)

Instead of using RMAN, you can delete backup files manually from the operating system:

cd /your/backup/location

rm -rf * or rm -rf filename.

Here in this case, used only filename.








🚨 Warning:

  • This method does not update the control file, so Oracle still thinks the backups exist.
  • You must manually resynchronize RMAN after using this method.

🤔 Why Do Backups Still Appear After Deleting?

If you manually delete backups using the rm command, Oracle RMAN still considers them available because the control file has a record of them. These backups are now called Expired Backups.







How to Identify Expired Backups?

Run the following RMAN command:

crosscheck backup;

This will check if the backups physically exist. If they don’t, RMAN will mark them as EXPIRED.

🗑️ How to Delete Expired Backups in RMAN?

To clean up expired backups and free up space, use:

DELETE EXPIRED BACKUP;

This ensures that both the backup files and their records in the control file are removed.





💡 Key Takeaways

✅ Use RMAN DELETE BACKUP to safely remove backups while updating the control file.
✅ If you manually delete files, run CROSSCHECK BACKUP and DELETE EXPIRED BACKUP to clean up records.
✅ Avoid expired backups by regularly monitoring and managing backup retention policies.

By following these best practices, you can optimize disk space, improve backup management, and ensure a healthy Oracle database environment. 🚀

💬 Related Topics You Might Like

Comments

Post a Comment

Popular posts from this blog

Image
Oracle Export Metadata only And Import the Metadata only Guide – Step-by-Step Tutorial Scenario : Client is wanted to export and import the metadata In this guide, we will learn how to use expdp (Data Pump Export) and impdp (Data Pump Import) in Oracle Database to back up metadata and restore the same only. To create a backup, first we have to set up a physical backup location. Creating a Backup location: On Linux server: mkdir -p /data/backup On Oracle Database: Command: create a directory TEST_DIR2 as '/data/backup'; Here, TEST_DIR2 is a logical directory pointing to the physical backup location. To verify the directory: SELECT * FROM dba_directories WHERE directory_name = 'TEST_DIR2'; Exporting a Metadata using expdp: To backup the Metadata for Schema U2,  expdp schemas=U2 directory=TEST_DIR2 dumpfile=schdata_only2.dmp logfile=schdata_only.log content=METADATA_ONLY Note:   Dump File (.dump): A binary file generated by expdp that contains exported schema objects, data...
Read more
Image
How to Enable Archive Log Mode in Oracle (Switch to ARCHIVELOG Mode) If you want to disable archive log mode (switch to NOARCHIVELOG mode), follow these steps: 1. Check Current Archive Log Mode Before making changes, check if your database is in NO ARCHIVELOG mode: command -> select log_mode from v$database; The database in noarchivelog mode   If the output is NO ARCHIVELOG , it means archive logging is disabled. 2. Shutdown the Database You cannot switch to ARCHIVELOG mode while the database is running, so first shut it down: commnd -> shut immediate; 3. Start the Database in MOUNT Mode the database should be in mount stage to disable or enable it 4. Enable Archive Log Mode (Switch to ARCHIVELOG Mode) Run the following command: ALTER DATABASE ARCHIVELOG; 5. Open the Database Normally ALTER DATABASE OPEN; 6. Verify the Change Run this command again to confirm the mode: SELECT log_mode FROM v$database; Impact of Enabling Archive Log Mode ✅ Point-in-Time Recovery: With...
Read more
Image
Oracle Export Previous SCN Data & Import into an Existing Table – Step-by-Step Guide Scenario: In this guide, we will explore how to use Oracle Data Pump Export (expdp) and Import (impdp) to back up historical data from a previous SCN (System Change Number) and restore it into an existing table. This approach is useful when you need to retrieve older data while preserving the table structure. Step 1: Setting Up a Backup Location Before exporting data, we need to create a physical backup location where the dump files will be stored. On Linux server: mkdir -p /data/backup On Oracle Database: We create a logical directory pointing to the physical backup location: Command: create a directory TEST_DIR2 as '/data/backup'; TEST_DIR2 -->  Logical directory pointing to the physical backup location. To verify the directory: SELECT * FROM dba_directories WHERE directory_name = 'TEST_DIR2'; Step 2: Checking Current Table Data Inserted few more records Before exporting, ...
Read more