Last week, I added a new tablespace with a new data file. The fact is since this moment, the backup faild with this error:
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-03009: failure of backup command on TSM3 channel at 04/06/2009 02:08:44
ORA-01157: cannot identify/lock data file 8 - see DBWR trace file
ORA-01110: data file 8: '/dev/rtf7moc_d_00_lv'
I search this error at metalink but always refers a problem with a problem for oracle to see the datafile. I try to create a new elements (tables, indexes, etc) over this tablespace and I have no problems to do it. And if i make querys over it always have answers (like dba_tables or dba_segments).
Yesterday I was searching the trace file, but i don't find it. No error at alertlog only in the log of the rman. I was executing some queries over this tablespace as I said, all with results ok. Finally I tryed to create a table on this tablespace and I decided don't drop it. The result was the next backup of this morning was ok without more changes.
Perhaps exist a problem to backup a new datafile if it's empty?
I also made the experience an emtpy tablespace located on a raw device is not the same as in a regular filesystem. It seems some Oracle commands don't recognize such empty tablespaces on raw devices and report 'file does not exist'.
With 'specific issues' I referred especially to this metalink note:
Raw Devices and Oracle - 20 Common Questions and Answers Doc ID: 37914.1