This content has been marked as final. Show 7 replies
DB_FILE_NAME_CONVERT will change the directory, the location of file, not its name.
Here's a step by step using two servers :
My duplicate script has to run on the same host.
To be sure i do not overwrite source files, i prefer to change the filename as well.
Any other suggestions?
look at the Parameter nofilenamecheck in your duplicate command.
See the documentation:
Turns out I have a better document :
I understand your concern, as far as suggestions double check everything. Thinking RMAN won't overwrite a MOUNTED file.
*"To restore a datafile, either mount the database, or keep it open and take the datafile to be restored offline."*
Source - Database Backup and Recovery Advanced User's Guide.
When NOFILENAMECHECK is used with the DUPLICATE command, RMAN does not validate the filenames during restoration. Last I heard you don't use NOFILENAMECHECK when using the same host.
See - Restoring and Recovering Database Files - Database Backup and Recovery User's Guide 11g Release 2 (11.2) E10642-03
Edited by: mseberg on Jan 9, 2013 12:38 PM
My concern is not that Rman will overwrite the files.
We prefer to name the datafiles starting with the sid.
Just to avoid accidents during manual actions on the filesystem.
I would say that SET NEWNAME would be the only way to "rename" the files.
You can "generate" the SET NEWNAME commands with a simple SQL query on DBA_DATA_FILES that fetches the value of FILE_NAME and replaces the SID in it.
Hemant K Chitale
Yes i thought so,
Thank you all for the replies.