RMAN Backup Failing with ORA-01157 ORA-01110 if Tablespace or Datafiles get Dropped During RMAN Backup
(Doc ID 1526542.1)
Last updated on FEBRUARY 14, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 22.214.171.124 [Release 10.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
RMAN looks for the datafiles to backup and identifies that the datafile doesn't exist any more ( dropped ) that cause the backup to fail.
The question is,
Does any workaround/patch exist so rman does not fail and exit, but to continue the backup with error message,
or warning that the Tablespace / Datafile was dropped after backup has started and so not available.
RMAN-03009: failure of backup command on ch01 channel at 02/05/2013 12:51:00
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: 'No file with this number, file does not exist'
RMAN-06056: could not access datafile 5 <<-- This tablespace/datafile was dropped after rman backup was already started
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document