Error updating db file on disk
Verify that all paths are accessible on the host where the database is being duplicated.Example 13-1 shows sample initialization parameter settings for the duplicate database.If the duplicate host is not the same as the target host, then you must make backups on disk on the target host available to the duplicate host with the same full path name as in the primary database.When using disk backups, you can accomplish this goal in any of the following ways: When using tape backups, you must make the tapes containing the backups accessible to the remote node.
All backups and archived redo logs used for creating and recovering the duplicate database, however, must be accessible by the server session on the duplicate host.For the duplication to work, you must connect RMAN to both the target (primary) database and an auxiliary instance started in mode.Allocate at least one auxiliary channel on the auxiliary instance.Hence, it is a good idea to create a server-side initialization parameter file for the auxiliary instance in the default location.If you do not have a server-side initialization parameter file for the auxiliary instance in the default location, then you must specify the client-side initialization parameter file with the Make sure backups all target datafiles are accessible on the duplicate host.
The farthest that RMAN can go in recovery of the duplicate database is the most recent redo log archived by the target database. When choosing names for the duplicate control files, make sure you set the parameters in the initialization parameter file of the auxiliary database correctly; otherwise, you could overwrite the control files of the target database.