Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Current »

In this section we’ll describe how to modify DDC file - add, remove or change existing parameters. The DDC file can be changed via GUI and by directly editing the existing DDC file on the filesystem.

Master DDC file is stored exclusively on primary server as standbymp/oracle/conf/dbv_<DDC>.env Standby server contains a DDC file copy in the same location.

Editing the DDC file via GUI will write the changes directly to the file and vice versa: any change done manually in the file will be then visible in the GUI as well.

DDC file doesn’t contain all possible variables. If any DDC variable isn’t present in DDC file, it assumes default value. DDC file variables reference: DDC File Reference

1 Modifying DDC File through GUI

Not all parameters which are possible to edit are shown in GUI due to safety reasons

To edit DDC file in dbvcontrol GUI, you need to go to configuration ACTIONS pane, expand advanced options and select “Edit DDC File”:

image-20250220-101743.png

You can add new parameter (1), edit existing (2) or display information (3):

image-20250220-103153.png

To add parameter, you can use the search function and specify desired value (1):

image-20250220-103435.pngimage-20250220-103505.png

You can afterwards save (2), which will make the parameter effective and add it at the end of the list.

You will be unable to remove parameters created by DDC setup. You can however remove (1) any parameter you add through this GUI:

image-20250220-103750.png

Modifying DDC file will cause ASU transfer & apply to be restarted in the background. We recommend that you verify that synchronization works without issues after DDC file modification.

2 Modifying DDC File directly on the filesystem

You can also directly edit the DDC file on the filesystem for example with “vi” or “notepad”. We recommend to stop Automated standby update (ASU) before editing DDC file and edit the DDC file on primary server only.

Primary server contains master DDC file, standby server only contains DDC file copy which is automatically overwriten by DDC from primary in case any difference is detected during archivelog transfer.

  • you can modify any existing parameter directly

  • if there’s a new parameter you want to add, enter it as newline at the end of the file

  • duplicate lines will be ignored

  • lines starting with “#” will be ignored (Windows and Linux)

If you would like to add new value, place it at the end of the file, for example:

APPLY_READ_ONLY = Y
RMAN_DBF_BACKUP_TYPE = AS BACKUPSET

If you would like to modify existing value, edit it in place. For example setting AMM for standby:

# 60 Standby Archive Log Management Settings
#>>>Explanation>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
# ARCHDEST_MANAGEMENT       - Turns AMM on or off for standby server.
# DAYS_TO_KEEP_ARCHDEST     - Days to keep the archive log files.
# NUM_ARCHDEST_TO_KEEP      - Number of archive log files to keep.
# THRESHOLD_ARCHDEST        - Threshold in % of how much disk space may be used.
# DELETE_ARCHDEST_THRESHOLD - Delete archive files once threshold is reached.
#<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
ARCHDEST_MANAGEMENT = Y
DAYS_TO_KEEP_ARCHDEST = 0
NUM_ARCHDEST_TO_KEEP = 5
THRESHOLD_ARCHDEST = 0
DELETE_ARCHDEST_THRESHOLD = N

Start ASU again once you finish editing DDC file. Once ASU is started, standby DDC file will be overwritten with the changes you have done on primary.

  • No labels