CREATE FAR

CREATE FAR_SYNC

The CREATE FAR_SYNC command creates a new far sync instance and adds it to the broker configuration. To use this command, Oracle wallet-based authentication must be configured and you must connect with SYSDBA privilege. In addition, an auxiliary instance must be started on the host where a new far sync instance is created.

Format

When the auxiliary instance is started using a parameter file (PFILE):

CREATE FAR_SYNC <db_unique_name> AS CONNECT IDENTIFIER IS <connect_identifier> [ SPFILE [ PARAMETER_VALUE_CONVERT '<string_pair_values>' ] [ SET <parameter_name> value ] ... [ SET <parameter_name value> ] [ RESET <parameter_name> ] ... [ RESET <parameter_name> ] ];

When the auxiliary instance is started using a server parameter file (SPFILE):

CREATE FAR_SYNC <db_unique_name> AS CONNECT IDENTIFIER IS <connect_identifier>;

Usage Notes

The version of the connected database must be the same as the DGMGRL version.
If the SPFILE clause is included, the initialization parameters in the specified spfile are used when creating the far sync instance.

This command uses the RMAN DUPLICATE command to create a far sync instance. If the auxiliary instance used during RMAN duplication was started using an spfile, you cannot include the SPFILE clause in the CREATE FAR_SYNC command.
The PARAMETER_VALUE_CONVERT clause must immediately follow the SPFILE clause. Note that the command fails if you use the PARAMETER_VALUE_CONVERT clause after the SET or RESET clause.
You must set up Oracle Wallet. The alias used in the wallet to connect to the far sync instance must resolve to a static service connection on both the primary database host and the far sync instance host. The alias used in the wallet to connect to the primary database does not need to resolve to a static service connection. For both hosts, the connect identifiers for each database must resolve to the same instance on both the primary database host and the far sync instance host.
You must start an auxiliary instance on the host where a new far sync instance is created. If the auxiliary instance is started with a server parameter file, you cannot specify the SPFILE,PARAMETER_VALUE_CONVERT, SET, and RESET clauses.
The version of the connected database must be the same as the DGMGRL version.
To create a far sync instance, this command invokes the RMAN DUPLICATE command with the specified PARAMETER_VALUE_CONVERT, SET, and RESET clauses.
The PARAMETER_VALUE_CONVERT clause must immediately follow the SPFILE clause. If you specify the PARAMETER_VALUE_CONVERT clause after the SET or RESET clause, the command will fail.
If the auxiliary instance is started with a parameter file, this command does the following:
- Sets the following initialization parameters for the far sync instance:
  - DB_NAME to the DB_NAME of the primary database
  - DB_UNIQUE_NAME to the specified db_unique_name
  - SGA_TARGET to 300MB
  - CPU_COUNT to 1
- Resets the following initialization parameters: CONTROL_FILES, CLUSTER_DATABASE, DB_RECOVERY_FILE_DEST,DB_RECOVERY_FILE_DEST_SIZE,DB_FILE_NAME_CONVERT, and LOG_ARCHIVE_CONFIG. Parameters that contribute the total size of SGA memory such as, but not limited to, DB_CACHE_SIZE, LOG_BUFFER, SHARED_POOL_SIZE,LARGE_POOL_SIZE, JAVA_POOL_SIZE,STREAMS_POOL_SIZE are reset.
- Clears the existing LOG_ARCHIVE_DEST_n initialization parameters.
If an initialization parameter of the far sync instance is not set appropriately, the command can fail because DGMGRL fails to start up the far sync instance. In this case, identify the cause of the problem by viewing the alert log files or broker log files on the far sync instance and modify the required initialization parameter either in the spfile or by appending thePARAMETER_VALUE_CONVERT, SET, or RESET clause.

Command Parameters

db_unique_name

The value for the DB_UNIQUE_NAME initialization parameter of the far sync instance.

connect_identifier

A fully specified connect descriptor or a name to be resolved by an Oracle Net Services naming method (for example, TNS). The value you specify is also used as the initial value of the DGConnectIdentifier database property.

string_value_pairs

A list of string pairs. The value is set to the value of PARAMETER_VALUE_CONVERT clause when the RMAN DUPLICATE command is invoked.

The PARAMETER_VALUE_CONVERT clause replaces the first string with the second string in all matching initialization parameter values. Multiple pairs of strings may be specified by this parameter.

For example, ‘ “string1”, “string2”, “string3”, “string4”, ... ’

Where:

• string1 is the pattern of initialization parameters of the primary database.
• string2 is the pattern of initialization parameters of the far sync instance.
• string3 is the pattern of initialization parameters of the primary database.
• string4 is the pattern of initialization parameters of the far sync instance.

This is an optional argument. If not specified, a copy of the server parameter file on the primary database will be used on far sync instance without any modification.

parameter_name: Name of the initialization parameter that must be set or reset.

value: Value that must be set for the specified initialization parameter.

Command Example

The following example creates a far sync instance named "FS1" and adds it to the broker configuration. The initialization parameters LOG_FILE_NAME_CONVERT, DB_RECOVERY_FILE_DEST, and DB_RECOVERY_FILE_DEST_SIZE will be set to the values specified. The initialization parameter UNDO_TABLESPACE will be reset.

DGMGRL> CREATE FAR_SYNC 'FS1' AS CONNECT IDENTIFIER IS 'FS1_STATIC_CONN'
          SPFILE
          PARAMETER_VALUE_CONVERT 'North_Sales','FS1','NORTH_SALES','FS1','NorthSales','FS1','NORTHSALES','FS1'
          SET LOG_FILE_NAME_CONVERT 'North_Sales','FS1','NORTH_SALES','FS1'
          SET DB_RECOVERY_FILE_DEST '/scratch/oracle/fast_recovery_area'
          SET DB_RECOVERY_FILE_DEST_SIZE '100G'
          RESET UNDO_TABLESPACE;
Creating far sync instance "FS1".
Connected to "North_Sales"
Connected to "Aux"
far sync instance "FS1" created
far sync instance "FS1" added