Dbvisit Standby uses a range of techniques to rename database files in the standby control file:

Use Oracle database parameters db_file_name_convert and log_file_name_convert
Use RMAN command "set newname"
Ensure creation of OMF files is enabled in the standby database, to create OMF and FQSN files automatically

Standby Database File Renaming Rules

The user can provide full name for FS or ALIAS control files
To create OMF or FQSN control files, the parameter control_files should be left empty, or in case of the ASM standby, only the name of ASM diskgroup(s) should be specified. Creation of OMF files should be enabled on the standby by setting parameters db_create_file_dest and/or db_create_online_log_dest_n and/or db_recovery_file_dest
If the parameter control_files is not set, and creation of OMF files is not enabled on the standby, standby control files will be created in a default operating system location.

Primary FS => Standby FS
Datafiles and tempfiles
Primary FS file	Standby FS file	A valid existing filesystem location must be specified for the standby FS file
Primary OMF file	Standby OMF file	Creation of OMF files must be enabled on the standby by setting parameter db_create_file_dest. Datafiles and tempfiles will be created in this location.
Redo logs
Primary FS fredo	Standby FS fredo	A valid existing filesystem location must be specified for the standby FS redo
Primary OMF redo	Standby OMF redo	Creation of OMF files must be enabled on the standby by setting parameters db_create_file_dest and/or db_create_online_log_dest_n and/or db_recovery_file_dest. Redo logs will be created in these locations.
Primary ASM => Standby FS
Datafiles and tempfiles
Primary FQSN file	Standby OMF file	Creation of OMF files must be enabled on the standby by setting parameter db_create_file_dest. Datafiles and tempfiles will be created in this location.
Primary ALIAS file	Standby FS file	A valid existing filesystem location must be specified for the standby FS file
Redo logs
Primary FQSN redo	Standby OMF redo	Creation of OMF files must be enabled on the standby by setting parameters db_create_file_dest and/ordb_create_online_log_dest_n and/or db_recovery_file_dest. Redo logs will be created in these locations.
		if CSD_FORCE_ASM_REDO_CONVERT set to Y in the DDC file (default N) then a FS redo will be created. This setting can be used for some environments that do not allow mounting of the standby database when its control file contains ASM names for redo and an ASM instance is not running.

Primary ALIAS redo	Standby FS redo	A valid existing filesystem location must be used for the standby FS redo
Primary FS => Standby ASM
Datafiles and tempfiles
Primary FS file	Standby FQSN file	A valid ASM diskgroup name must be specified. File will be created under ASM_diskgroup/db_unique_name/datafile\|tempfile
Primary OMF file	Standby FQSN file	A valid ASM diskgroup name must be specified. File will be created under ASM_diskgroup/db_unique_name/datafile\|tempfile
Redo logs
Primary FS redo	Standby ALIAS fredo	A valid ASM diskgroup name must be specified. File will be created under ASM_diskgroup/db_unique_name/onlinelog
Primary OMF redo	Standby FQSN redo	A valid ASM diskgroup name must be specified. File will be created under ASM_diskgroup/db_unique_name/onlinelog
Primary ASM => Standby ASM
Datafiles and tempfiles
Primary FQSN file	Standby FQSN file	A valid ASM diskgroup name must be specified. File will be created under ASM_diskgroup/db_unique_name/datafile\|tempfile
Primary ALIAS file	Standby FQSN file	A valid ASM diskgroup name must be specified. File will be created under ASM_diskgroup/db_unique_name/datafile\|tempfile
Redo logs
Primary FQSN fredo	Standby ALIAS fredo	A valid ASM diskgroup name must be specified. File will be created under ASM_diskgroup/db_unique_name/onlinelog
Primary ALIAS redo	Standby FQSN redo	A valid ASM diskgroup name must be specified. File will be created under ASM_diskgroup/db_unique_name/onlinelog