You are here:

Restore Jobs - Rename Mount Points and Initialization Parameter Options

This option is available for supported Restore jobs running Instant Database Restore and DevOps workflows.

Mount Point Rename

This option controls how mount points and ASM diskgroups are renamed when they are mounted on the destination host/cluster during recovery.

Append a timestamp: By default, ECX appends a timestamp to the original mount point. For example:

Mount Point Rename - Append a timestamp
Original Mount Point	New Mount Point
/u02/myproddb/data	/u02/myproddb/data_1479400505
+MYPRODDATA	+MYPRODDATA1479400505

Do not rename: Select this option if you do not want to rename mount points or ASM diskgroups during recovery. ECX will mount them with the same path/name as the source.

Add a custom prefix: Select this option and specify a custom prefix to be prepended to the source paths/names. The prefix value may contain leading or trailing slashes. In the case of ASM diskgroup names, the slashes are removed. For example:

Mount Point Rename - Add a custom prefix
Original Mount Point	Prefix	New Mount Point
/u02/myproddb/data	tmp	/tmpu02/myproddb/data
/u02/myproddb/data	/tmp/	/tmp/u02/myproddb/data
+MYPRODDATA	/tmp/	+TMPMYPRODDATA

Add a custom suffix: Select this option and specify a custom suffix to be appended the source paths/names. For example:

Mount Point Rename - Add a custom suffix
Original Mount Point	Suffix	New Mount Point
/u02/myproddb/data	tmp	/u02/myproddb/datatmp
/u02/myproddb/data	/tmp/	/u02/myproddb/data/tmp
+MYPRODDATA	/tmp/	+MYPRODDATATMP

Replace a substring: Select this option and specify a custom string of characters in the old mount point to be replaced with another string of characters. The old and new substrings must be simple alphanumeric strings with no special characters. All occurrences of the specified substring are replaced. The value of the new substring may be left empty if you want to remove the old substring. For example:

Mount Point Rename - Replace a substring
Original Mount Point	Old Substring	New Substring	New Mount Point
/u02/myproddata/data	prod	test	/u02/mytestdata/data
/u02/myproddata/data	data	newdata	/u02/myprodnewdata/newdata
+MYPRODDATA	prod	test	+MYTESTDATA
+MYPRODDATA	prod	<empty>	+MYDATA

Database Initialization Parameters

This option controls the initialization parameters used to start up the recovered database in Oracle Instant Database Restore and DevOps workflows.

Use same parameters as source: This is the default option. ECX uses the same initialization parameters as the source database, but with the following changes:

Parameters that contain paths such as control_files, db_recovery_file_dest, or log_archive_dest_* are updated to reflect the new paths based on the renamed mount points of the recovered volumes.
Parameters such as audit_file_dest and diagnostic_dest are updated to point to the appropriate location under the Oracle Base directory on the destination server if the path differs from the source server.
The db_name and db_unique_name are updated to reflect the new name of the database if a new name is specified.
Cluster-related parameters such as instance_number, thread, and cluster_database are set automatically by ECX depending on the appropriate values for the destination.

Use a template pfile: You can customize the initialization parameters by specifying a template file containing the initialization parameters that ECX should use.

The specified path must be to a plain text file that exists on the destination server and is readable by the ECX user. The file must be in Oracle pfile format, consisting of lines in the form name = value. Comments beginning with the # character are ignored.

ECX reads the template pfile and copies the entries to the new pfile that will be used to start up the recovered database. However, the following parameters in the template are ignored. Instead, ECX sets their values to reflect appropriate values from the source database or to reflect new paths based on the renamed mount points of the recovered volumes.

control_files
db_block_size
db_create_file_dest
db_recovery_file_dest
log_archive_dest
spfile
undo_tablespace

Additionally, cluster-related parameters like instance_number, thread, and cluster_database are set automatically by ECX depending on the appropriate values for the destination.