How to fix RMAN-08118 / ORA-27056 Error in Oracle

🚨 Fixing RMAN-08118 / ORA-27056 Error in Oracle 🔧

Ever encountered this frustrating message during your RMAN backup or log deletion process?

RMAN-08118: warning: could not delete the following archived redo log
ORA-27056: could not delete file

This error usually appears when RMAN is unable to delete archive logs after backup, often due to permission or OS-level issues. Let's dive into the root cause and how to fix it — step-by-step! 🛠️

---

🔍 Root Cause

• RMAN-08118 ➜ RMAN tried but failed to delete the archived redo log.
• ORA-27056 ➜ OS error — usually due to file permission issues, file locks, missing files, or read-only filesystems.

---

✅ Step-by-Step Fix

1️⃣ Check File Permissions

Make sure the Oracle user has proper permission to delete the archived redo logs:

ls -l /path/to/archivelogs/

If the owner isn't oracle, fix it:

chown oracle:oinstall /path/to/archivelogs/*
chmod 660 /path/to/archivelogs/*

💡 Tip: Always check the directory permissions as well!

2️⃣ Crosscheck Logs in RMAN

Sometimes the log is already deleted manually, but RMAN doesn't know that. Use:

RMAN> crosscheck archivelog all;
RMAN> delete expired archivelog all;

🧠 Note: This updates RMAN's catalog/controlfile to reflect reality.

3️⃣ Check for File Locks

Verify if another process (like Data Guard or a backup tool) is holding the file:

lsof | grep <archived_log_file.arc>

🔍 Tip: This helps identify processes that are preventing file deletion.

4️⃣ Manually Delete (Only If Safe)

If you're sure the file is not needed and safe to delete:

rm -f /path/to/archivelogs/archived_log.arc

⚠️ Caution: Only delete files that are already backed up and not needed by recovery!

---

🛡️ Pro Tips to Avoid This in Future

• ✔️ Run crosscheck regularly as part of RMAN maintenance.
• ✔️ Never delete archive logs manually from OS without syncing with RMAN.
• ✔️ Monitor filesystem space and permissions proactively.
• ✔️ Automate log deletion with RMAN using delete archivelog until time.

---

📜 Sample RMAN Script for Auto Cleanup

run {
  crosscheck archivelog all;
  delete expired archivelog all;
  delete archivelog until time 'SYSDATE-3';
}

📌 Note: This keeps archive logs for the last 3 days only.

---

🎯 Conclusion

The RMAN-08118 / ORA-27056 error is common in many environments — but easy to resolve with proper checks on permissions, file locks, and RMAN catalog consistency. By following the above steps, you can keep your backups clean and your logs under control! 🎉

Have a script or tip that helped you fix this error? Share in the comments below! 💬