We are currently working on moving our databases to different geographic locations and try to look for the best approach. One of the suggested ideas was mapping the target server drive and backup directly to mapped network drive on the target server and get rid of copy step after the backup.
After the initial trials, every time RMAN failed to write to the network drive with the error stack below.
ORA-19504: failed to create file "X:\DB_T686079212_S20_P1"
ORA-27040: file create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
or
ORA-19504: failed to create file "\\SERVERNAME\DB_T686079212_S20_P1"
ORA-27040: file create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Metalink note 145843.1 came up with a solution
Basically all you need to do is update Oracle Services (both listener and Database) to run with Domain Account which has access on both servers with Administrator Privilege.
After you update the services ;
1- Restart the services
2-Use UNC naming instead of using drive letter on your script. (UNC naming part is not mentioned in the note)
3- Run the RMAN backup
Worked fine on my case.
Does’nt work when using DRCP.
Did’nt resolve yet.
Comment by Dominik — September 3, 2009 @ 10:24 am