Skip to main content

Oracle Restore Failure Due to Insufficient Space with error ORACLE_DTC5

Oracle Restore Failure Due to Insufficient Space with error ORACLE_DTC5

Updated this week

Problem Description

  • An Oracle restore job was failing with I/O errors, specifically reporting "No space left on device."

  • The restore process was terminated prematurely when attempting to write database files with the error Rman failure. RMAN-06023: no backup or copy of datafile 9 found to restore.

Cause

  • The restore operation attempts to write database files to the local file system of the target server instead of the designated ASM (Automatic Storage Management) storage.

  • The local disk did not have sufficient capacity to accommodate the size of the database, leading to the space exhaustion error.

  • This misdirection occurred because the restore job parameters did not explicitly define the ASM disk groups as the destination for the database files.

Traceback / Logs:

The application and RMAN logs clearly indicated a space issue on the local device.

Application(OracleJob.log) Log Snippet:

level=debug ts=2025-08-26T18:18:50.617847987Z filename=rman_script.go:391 message="stdout: rman-15278_0: Linux-x86_64 Error: 28: No space left on device" Layer=OracleApi

RMAN Log(rman.log) Snippet:

ORA-19502: write error on file "/apps/oracle/DUMMY_DB/PDB_DUMMY/datafile.dbf", block number 308352 (block size=16384)

ORA-27072: File I/O error

Linux-x86_64 Error: 28: No space left on device

Additional information: 4

Additional information: 308352

channel ch6: restoring datafile 00012 to /apps/oracle/DUMMY_DB/PDB_DUMMY/undo_2.447.1110929721

Resolution:

  • The problem was resolved by explicitly defining the correct ASM storage locations within the restore job's database parameter settings.

  • Adding the following parameters ensured that RMAN directed all database files to the appropriate ASM disk groups:

    • control_files = +DATA/DUMMY_DB/controlfile/control01.ctl

    • db_create_file_dest = +DATA

    • db_create_online_log_dest_1 = +REDO

    • db_create_online_log_dest_2 = +FRA

    • db_recovery_file_dest = +FRA

  • After these parameters are applied, the restore job uses ASM location.

Recommendation/Reference:

  • When restoring an Oracle database to an environment that utilizes ASM, it is essential to explicitly specify the ASM disk groups for all database file types.

  • If parameters like db_create_file_dest and db_recovery_file_dest are not defined in the restore configuration, RMAN may default to writing files to the local file system.

  • Always verify that all storage-related parameters are correctly configured to point to your ASM disk groups before initiating a restore to avoid space-related failures.

Did this answer your question?