Real-World Oracle Database and EBS Troubleshooting Guides

A collection of real-world Oracle Database and EBS troubleshooting scenarios from production environments. These guides cover common issues encountered during day-to-day DBA operations.

---

Resolving RMAN ORA-19502 Backup Failure Due to Disk Full

RMAN backup job failed with the following errors:

ORA-19502: write error on file
ORA-27072: File I/O error
Linux-x86_64 Error: 28: No space left on device

Environment

Oracle Database 19c, RMAN Disk Backup, Linux Environment

Diagnosis

Checked RMAN logs and identified the backup destination filesystem was full:

-- Check filesystem usage
df -h

-- Check FRA usage from database
SELECT name, space_limit/1024/1024/1024 limit_gb,
       space_used/1024/1024/1024 used_gb,
       ROUND(space_used/space_limit*100,2) pct_used
FROM v$recovery_file_dest;

The backup mount point reached 100% utilization.

Resolution

Cleaned older backup files after validating they were no longer needed, then reran the backup job:

-- Use RMAN to safely clean up obsolete backups (preferred over OS delete)
RMAN> CROSSCHECK BACKUP;
RMAN> DELETE EXPIRED BACKUP;
RMAN> DELETE OBSOLETE;

After freeing space, the RMAN backup completed successfully.

Key Lesson

Always monitor backup destinations proactively. Schedule DELETE OBSOLETE as part of your regular RMAN maintenance to prevent FRA saturation.

---

Written by Syed Anwar Ahmed — Oracle Apps DBA with 11 years of production experience.
Connect: sdanwarahmed@gmail.com  |  LinkedIn