Skip to main content

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! 💬

Labels:

Comments

Post a Comment

Popular posts from this blog

🚀 Automating Oracle Database Patching with Ansible: A Complete Guide

Oracle database patching has long been the bane of DBAs everywhere. It's a critical task that requires precision, expertise, and often results in extended maintenance windows. What if I told you that you could automate this entire process, reducing both risk and downtime while ensuring consistency across your Oracle estate? 💡 In this comprehensive guide, I'll walk you through a production-ready Ansible playbook that completely automates Oracle patch application using OPatch. Whether you're managing a single Oracle instance or hundreds of databases across your enterprise, this solution will transform your patch management strategy! 🎯 🔥 The Challenge: Why Oracle Patching is Complex Before diving into the solution, let's understand why Oracle patching is so challenging: 🔗 Multiple dependencies : OPatch versions, Oracle Home configurations, running processes ⚠️ Risk of corruption : Incorrect patch application can render databases unusable ⏰ Downtime requirements : Da...
Post a Comment
Read more

⚡ Automating Oracle 19c Database Patching on Windows Server with PowerShell

Applying Oracle patches on Windows often feels repetitive and error-prone — stopping services, updating OPatch, applying patches, running datapatch , and restarting services. To save time ⏱ and reduce mistakes ⚠, I created a PowerShell automation script that performs the patching process end-to-end 🚀. 🔹 Why Automate Oracle Patching? ⏱ Save time by automating repetitive steps ⚙ Avoid manual errors during patching 📜 Maintain logs for auditing and troubleshooting 🛡 Ensure consistent, reliable patching 🔹 Full PowerShell Script # --- CONFIGURATION --- $oracleHome = "c:\users\administrator\downloads\v982656-01" # Change if this is not your actual Oracle Home! $patchDir = "C:\Users\Administrator\Downloads\p37962957_190000_MSWIN-x86-64\37962957" #update the Patchfile directory $opatchDir = "$oracleHome\OPatch" $opatchZip = "C:\Users\Administrator\Downloads\p6880880_190000_MSWIN-x86-64.zip" #Based on your setup update Opatch di...
Post a Comment
Read more

Installing pgBackRest on Linux (RHEL 9 / Rocky / AlmaLinux)

 When you work with PostgreSQL in real environments, one thing becomes very clear very quickly: Backups are not optional. It doesn’t matter how stable your database is — failures happen. Disks crash Files get corrupted Someone runs the wrong delete query A patch goes wrong A standby needs rebuilding. So having a proper backup strategy is not just good practice, it’s survival. That’s exactly why tools like pgBackRest are so widely used in PostgreSQL production systems. In this post, I’ll walk through a simple installation of pgBackRest on a Linux server (RHEL 9 / Rocky Linux / AlmaLinux). Why pgBackRest? PostgreSQL already provides tools like: pg_dump pg_basebackup And yes, they work. But once your database grows, or you start managing HA setups, these tools start feeling limited. pgBackRest is built for serious PostgreSQL backup requirements. Some of the reasons it stands out: Supports full, differential, and incremental backups Built-in compre...
Post a Comment
Read more