DBMS_FILE_TRANSFER utility

Question

I have been trying to do a clone from ASM-ASM using the dbms_file_transfer utility in 10.2.0.4 by copying the datafiles from the source database to the target database.RMAN is not an option for us as the source and target database are on different clusters. I am using the syntax as given below.
exec dbms_file_transfer.get_file('SOURCE_DIRECTORY_OBJECT','SOURCE_FILE_NAME','SOURCE_DATABASE','DESTINATION_DIRECTORY_OBJECT','DESTINATION_FILE_NAME')
An example would be as given below to copy the datafile related to system tablespace.
exec dbms_file_transfer.get_file('sgecm', 'system.1161.639928703','sgeca2','SgecM','system')
Everything works fine except that, the files are transferred with the file name as FILE_TRANSFER_XXXXXXXX and have an alias to the file name given by me(system).
I would like to know how I can change the format of the default name from FILE_TRANSFER_XXXXXXXX to some other format, this would be really helpful to fine tune my cloning document.
Currently, the procedure I am using is as follows.
1) Copy the datafiles using the DBMS_FILE_TRANSFER utility and get a backup of the control file trace from the source.
2) Edit the control file script to reflect the new file name(system in our example above).
3) Open the database using resetlogs options.
4) Take an RMAN backup of the new database.
5) Shutdown the database and delete all the datafiles.
6) startup mount
7) Restore the datafiles from backup. (Here, RMAN creates OMF file names and creates aliases to the file names like system etc as those are still the data file names in the controlfile).
8) shutdown the database again.
9) startup mount
10) Rename the datafiles to point from names like system(the aliases) etc., to the OMF file names like system.123.456789 etc.
11) Start the database.
I am basically looking for a solution where I dont need to take up so many steps as it might be pretty time consuming when we try to clone huge databases.
Best Regards,
Prithvi

Answer 1

This whole scenario has been drawn up for the following reasons.
1) We are migrating to different servers where the existing legato tapes are not accessible.
2) We take an RMAN backup to disk(ASM) initially but this cannot be used as the source and target are on different disk groups.
3) The source databases are on 10.2.0.3(32-bit linux) and we are migrating to 10.2.0.4(linux 64-bit) servers. RMAN cannot be used if the backup was taken using 10.2.0.3 binaries and you are trying to restore using 10.2.0.4 binaries.
Prithvi