Versions Compared

Old Version 7

changes.mady.by.user Anton Els

Saved on

compared with

New Version Current

changes.mady.by.user Anton Els

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Follow the on-screen instructions to install AMM or please see the  Dbvisit Standby Archive log Management Module (AMM) setup section for description of each step.

Image ModifiedHome > Setup > Update Dbvisit > Update Dbvisit Configuration. Choose the AMM settings to update and click on Save Configuration.

Dbvisit Standby AMM variables

...

Dbvisit Standby AMM processing overview


Align

The order of precedence in managing the log files are:

  1. If there are log files older than DAYS_TO_KEEP_ARCHSOURCE, then delete these.
  2. If there are more log files than NUM_ARCHSOURCE_TO_KEEP, then delete these (oldest ones first).
  3. If there are more logs that have been backed up by RMAN at least ARCHSOURCE_BACKUP_COUNT times, then delete these.
  4. If the THRESHOLD_ARCHSOURCE < mount point fullness criteria is met, then mark archives for deletion (oldest ones first). The number of archives marked for deletion is HOWMANY_ARCHSOURCE. The archives will only be deleted if DELETE_ARCHSOURCE=Y. After deletion of the archives, and the criteria is still met (THRESHOLD_ARCHSOURCE < mount point fullness), then mark more archives for deletion (number of archives marked for deletion will be again HOWMANY_ARCHSOURCE, and oldest ones first). This process will continue until criteria is no longer met.

If DELETE_ARCHSOURCE=N, then only a warning email will be sent. No archives will be deleted when the THRESHOLD_ARCHSOURCE < mount point fullness criteria is met.Setting variable DELETE_ARCHSOURCE=N has no influence over DAYS_TO_KEEP_ARCHSOURCE and NUM_ARCHSOURCE_TO_KEEP. These will still delete archive files when their criteria are met.

...

Note

Variables are sorted alphabetically in the table below

Variable Name

Meaning

ARCHSOURCE_BACKUP_COUNT

Specify the number of times an archive log has to be backed up by RMAN before Dbvisit Standby deletes it from the primary server.

To disable this setting, set to 0 which is the default value.

Example:

ARCHSOURCE_BACKUP_COUNT = 0


ARCHSOURCE_MANAGEMENT

Specify if the AMM module to manage the archive log files are turned on or off on the primary server.

Possible Values:

  • Yes (default)
    Enable the AMM module on primary server.

  • No
    Disable the AMM module on primary server.

Example:

ARCHSOURCE_MANAGEMENT= Yes


DAYS_TO_KEEP_ARCHSOURCE

Specify the number of days to keep the Oracle log files on the primary server. If this value (in days) are reached, the log files will be removed from the server.

To disable this setting, set to 0, if you are not sure, set to 7.

Note

Make sure you have sufficient disk space to store the archive logs.

See also the ARCHDEST parameter under the standby server variable section for more detail


Example:

DAYS_TO_KEEP_ARCHSOURCE = 7


DELETE_ARCHSOURCE

Specify if archive log files should be deleted once the percentage threshold (THRESHOLD_ARCHSOURCE) on the primary server is reached.

Once the threshold is reached oldest archive log files are deleted first. 

Note

There is no verification that these log files have been backed up. Dbvisit Standby does not perform backups, this should be configured outside the Dbvisit Standby product.

Possible Values:

  • Yes
    Let Dbvisit Standby delete archive log files once percentage threshold is met. 

  • No
    Dbvisit Standby will only alert when percentage threshold is met (no archive log files will be deleted). 

If you are not sure, set to No.

Example:

DELETE_ARCHSOURCE = No


Note

This setting has no influence whether (archive) log files are deleted for DAYS_TO_KEEP_ARCHSOURCE or NUM_ARCHSOURCE_TO_KEEP.

These settings will delete (archive) log files once the percentage threshold is met.

FRA_THRESHOLD_ARCHSOURCE

Specifies the threshold in percentage (%) of how much FRA (flash/fast recovery area) space may be taken up by the archive log files on disk before an alert is triggered on the primary server. A value of 80 means at 80% FRA space threshold is reached, an alert will be triggered.

Please specify threshold as an integer. 

Example:

   FRA_ THRESHOLD_ARCHSOURCE = 80


NUM_ARCHSOURCE_TO_KEEP

Specifies the number of archive log files to keep on the primary server. Log files greater than this number will be removed (oldest first).

To disable this setting, set to 0. If you are not sure, set to 0 (disable).

Example:

    NUM_ARCHSOURCE_TO_KEEP = 0


THRESHOLD_ARCHSOURCE

Specifies the threshold in percentage (%) of how much disk space may be taken up by the archive log files on disk before an alert is triggered on the primary server. A value of 80 means at 80% space threshold is reached, an alert will be triggered.

Please specify threshold as an integer. 

Example:

    THRESHOLD_ARCHSOURCE = 80




Standby AMM Configuration Variables

This section provides an overview of the variables that can be configured for the AMM module with regards to the Standby Database.

Please see Archive log Management Module (AMM) for more information on AMM.


Note

Variables are sorted alphabetically in the table below

Variable Name

Meaning

ARCHDEST_MANAGEMENT

Specifies if the AMM module to manage the archive log files is turned on or off on the standby server.

Possible Values:

  • Yes
    Enable AMM module on the standby server.

  • No
    Disable AMM module on the standby server.

If you are not sure, set to Yes.

Example:

    ARCHDEST_MANAGEMENT= Yes


DAYS_TO_KEEP_ARCHDEST

Specifies the number of days to keep the Oracle log files on the standby server. After this the log files will be removed from the server.

Note

This is specific to the Dbvisit Standby ARCHDEST location. Please see ARCHDEST in the Standby Variable section.

To disable this setting, set to 0. If you are not sure, set to 7.

Example:

DAYS_TO_KEEP_ARCHDEST = 7


DELETE_ARCHDEST

Specifies if archive log files should be deleted once the percentage threshold (THRESHOLD_ARCHDEST) on the standby server is reached.

Once the threshold is reached oldest (archive) log files are deleted first. 

Note

There is no verification that these log files have been backed up, this (backups) is outside the scope of Dbvisit Standby


Possible Values:

  • Yes
    Let Dbvisit Standby delete archive log files once percentage threshold is met. 

  • No
    Dbvisit Standby will only alert when percentage threshold is met (no log files will be deleted). 

If you are not sure, set to No.

Example:

DELETE_ARCHDEST = No


Note

This setting has no influence whether archive log files are deleted for DAYS_TO_KEEP_ARCHDEST or NUM_ARCHDEST_TO_KEEP.

These settings will delete archive log files once the percentage threshold is met.

NUM_ARCHDEST_TO_KEEP

Specifies the number of archive log files to keep on the standby server. Log files greater than this number will be removed (oldest first).

To disable this setting, set to 0. If you are not sure, set to 0 (disable).

Example:

NUM_ARCHDEST_TO_KEEP = 0


THRESHOLD_ARCHDEST

Specifies the threshold in percentage (%) of how much disk space may be taken up by the archive log files on disk before an alert is triggered on the standby server.

Note

This parameter is specific to the Dbvisit Standby ARCHDEST location


A value of 80 means that if the 80% disk space threshold is reached, an alert will be triggered. If you are not sure, set to 80.

Example:

THRESHOLD_ARCHDEST = 80