Primary Server Settings

Owned by Anton Els (Deactivated)
Last updated: Jan 21, 2015
4 min read

This section is specific to the Primary Server settings used in the Dbvisit Standby Configuration file.

Variables are sorted alphabetically in the table below

Variable Name

Variable Description

DBPASSWD

The password for the Dbvisit Standby database repository (DDR) owner.

Example (default) value:

    DBPASSWD = dbvisitpasswd

 

DBUSER

The Dbvisit Standby database repository (DDR) owner in the Oracle database. The default username in Dbvisit Standby version 7 is "dbvisit7" where in version 6 it was "dbvisit".

If you do upgrade an environment from prior versions to version 7, the username will stay at "dbvisit"

Example (default) value:

    DBUSER = dbvisit7

 

DBVISIT_BASE

Dbvisit software installation directory, also known as the DBVISIT_BASE directory.

Example (Linux Default):

    DBVISIT_BASE = /usr/dbvisit

 

Example (Windows Default):

    DBVISIT_BASE = c:\Program Files\dbvisit

 

ENCRYPT_PASSWDS

Specify whether all passwords should be encrypted in the Dbvisit Standby Database Configuration (DDC) file. To change ENCRYPT_PASSWDS from Yes to No, the DBPASSWD is required.

This value cannot be manually edited. Use "dbvisit_setup" utility, and choose the menu option: "Update the Dbvisit Standby Database configuration (DDC) file"

 

Possible Values:

ENCRYPT_PASSWDS=Y

ENCRYPT_PASSWDS=N

The default value is N (No) If you are unsure, leave it at the default value.

Example (default) value:

ENCRYPT_PASSWDS = N

 

LEAVE_COMPRESS_SOURCE

Specifies whether the log files should be left compressed or not on the primary server AFTER having been transferred to the standby server.

It is recommended this value be left at the default which is LEAVE_COMPRESS_SOURCE=YES

 

If using RMAN, the log files should be left uncompressed, otherwise RMAN will not be able to find the archive logs for backup. If using other backup methods (not RMAN), the archive logs can be left in a compressed state.

Note: Log files will always be sent compressed to the standby server if the COMPRESS/UNCOMPRESS variables are set to use compression. This setting does not influence that.

Possible Values:

Yes = Leave compressed AFTER having being transferred

No = Uncompress log file AFTER having being transferred

If you are not sure, set to Yes.

Example (default) value:

LEAVE_COMPRESS_SOURCE = Yes

 

LOGDIR

This parameter is used to specify a new location for your Dbvisit Standby log files such as the history log. (This is not the default trace file location, see TRCDIR) - this parameter applies to the Primary Database Server (Source)

This Parameter is not set in the DDC file, but will have the default value of DBVISIT_BASE/standby/log

To overwrite the default value, set this parameter in the DDC file:

Example:

LOGDIR=/u01/dbvisit/standby/log

LOGSWITCH

Determines if a database log switch - "alter system switch logfile" should be performed every time Dbvisit Standby executes on the primary database. A database log switch will start the background process to archive the current redo log.

Possible Values:

  • No (default value)
    Dbvisit Standby will perform a database log switch ONLY when there are no new archive logs to transfer. If Dbvisit Standby is executed and an Archive log was generated since the last run, no log switch will be performed and the already created archive log will be transferred to the standby database. If no archive logs have been created since the last Dbvisit Standby execution, a log switch will be forced to start the generation of an archive log to be transferred.

  • Yes
    Dbvisit Standby will perform a database log switch every time it executes.
  • Ignore 
    Dbvisit Standby will never perform a database log switch.  Use this option with caution as Dbvisit Standby will not be able to guarantee how far behind in time the standby database is.  
    Only when Oracle performs a database log switch will Dbvisit Standby transfer the current archive redo log to the standby database.

If you are not sure, set to the default value which is "No".

Example:

    LOGSWITCH = No

 

ORACLE_SID_ASM

Specifies the name of the ASM instance on the primary server - if the primary database uses ASM. If primary database does not use ASM, this value is ignored and can be left at the default which is +ASM.

Default value is +ASM, but on Oracle RAC environments, the value should match the ASM instance name on the specific node. Example if the ASM instance on Node 1 is +ASM1 then the DDC file for Node 1 should reflect +ASM1 for this setting. For Node 2 the ASM instance number will be +ASM2 and for that specific DDC file the value should be set to +ASM2.

Example (when using single instance environment running ASM):

ORACLE_SID_ASM = +ASM

Example (RAC Node 1):

ORACLE_SID_ASM = +ASM1

Example (RAC Node 2):

ORACLE_SID_ASM = +ASM2


SOURCE

Primary server on which the primary database is installed. Dbvisit Standby software must be installed on this server.

Example:

SOURCE = dbvlin101

 

SYNCH_DBVISIT_INSTALL

Specifies whether the Dbvisit Standby configuration file between the primary and standby server should automatically be checked for differences, and if the standby Dbvisit Database Configuration File (DDC) file is different than the primary server DDC file, the primary server DDC file will be copied to the Standby server, overwriting it's DDC file. The primary server DDC file is seen as the "master" DDC file and if any changes are to be made to a configuration, it should be done on the primary side. Changes to the Standby DDC file will be lost (overwritten) if this value is set to the default which is "Yes".

If turned off (No), then the Dbvisit Standby installation can be manually synchronised with command: dbvisit -c <DDC>

Possible Values:

  • Yes
    Compare Primary and Standby DDC files and synchronise differences (Standby file will be overwritten with primary DDC file if any differences are found)
  • No
    The Primary and Standby DDC files are not compared or synchronised.

Example (default - recommended) value:

SYNCH_DBVISIT_INSTALL = Yes

 

Also see setting SYNCH_ENV_FILE_ONLY parameter

TMPDIR

This parameter is used to specify a new location for your Dbvisit Standby temporary files created during normal Dbvisit Standby operations (example sending and applying logs, but also during graceful switchover) - this parameter applies to the Primary Database Server (Source).

This Parameter is not in the DDC file by default, but will have the default value of DBVISIT_BASE/standby/tmp

To overwrite the default value, set this parameter in the DDC file:

Example:

LOGDIR=/u01/dbvisit/standby/tmp

 
TRCDIR

This parameter is used to specify a new location for your Dbvisit Standby trace files created during Dbvisit Standby operations - this parameter applies to the Primary Database Server (Source).

This Parameter is not in the DDC file by default, but will have the default value of DBVISIT_BASE/standby/trace

In some environments trace files including their size can grow rapidly. This location should be monitored and either moved to a different location if required, or you should make use of the NUM_TRACE_TO_KEEP or DAYS_TO_KEEP_TRACE parameters to manage this location.

 

To overwrite the default value, set this parameter in the DDC file:

Example:

LOGDIR=/u01/dbvisit/standby/trace