When I've done duplications in the past, we've run into this error when the original database had two datafiles with the same name but in different directories. The db_file_name_convert was used to move things into the same directory. In this situation, we either over-wrote a datafile or we had this locking issue. So my short answer is to look at your file names. On Tue, 2009-09-08 at 07:09 +0530, Shastry(DBA) wrote: > Hello, > > > While restoring the datafiles using RMAN I am getting this below > error. FYI, I am using NFS filer for my restoration purpose due to > lack of space in local/SAN mount points. Guess this must be a RMAN > bug. Does anyone show light on this please? > I have a softlink pointing to NFS (/opt1 --> /backup/). > > > DB -9.2.0.7 > RMAN -9i > > > using channel ORA_AUX_DISK_1 > channel ORA_AUX_DISK_1: starting datafile backupset restore > channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup > set > restoring datafile 00001 to /opt1/app/TEST/oradata/system01.dbf > restoring datafile 00015 to /opt1/app/TEST/oradata/edi_1.dbf > RMAN-00571: > =========================================================== > RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS > =============== > RMAN-00571: > =========================================================== > RMAN-03002: failure of Duplicate Db command at 09/07/2009 11:32:16 > RMAN-03015: error occurred in stored script Memory Script > ORA-19504: failed to create file "/opt1/app/TEST/oradata/edi_1.dbf" > ORA-27086: skgfglk: unable to lock file - already in use > SVR4 Error: 46: No record locks available > Additional information: 8 > > > Recovery Manager complete. > > > Thanks, > An -- //www.freelists.org/webpage/oracle-l