...

1. Alerts through email when Oracle archive logs have reached a set threshold of available disk space.

2. Can delete Oracle archive logs after a set number of days.

3. Can ensure that only x number of Oracle archive log files remain on the server.

4. Can delete Oracle archive logs after available disk space has been used up to ensure continual database operation.

5. Ensures the Oracle archive logs have been sent to the standby database before removing any archive logs.

6. Can integrate with Backup software to ensure archive logs have been backed up before removing.

...

In the case of multiple standby databases, Dbvisit Standby checks if a an archive log has been transferred to all active standby databases before deleting it on the primary.

A standby database is considered to be active if a Dbvisit process has run within the last DBV_LAST_RUN_OFFSET days to ship archive logs to this database from the primary.

...

The order of precedence in managing the archive log files are:

1. If there are archive log files older than days to keep the archive log files, then delete these.

2. If there are more archive log files than Number of archive log files to keep, then delete these (oldest ones first).

3. If there are more archive logs that have been backed up by RMAN at least Number of times an archivelog archive log has to be backed up rman before being deleted times, then delete these.

4. If the Threshold in % of how much disk space may be used < mount point fullness criteria are met, then mark archives for deletion (oldest ones first). The number of archives marked for deletion is how many archive logs. The archives will only be deleted if Delete archive files once threshold is reached=Y. After deletion of the archives, and the criteria are still met (Threshold in % of how much disk space may be used < 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 the criteria are no longer met.

...

The Dbvisit Standby Archive Log Management Module (AMM) produces a separate log file to the Dbvisit Standby database processing. The log file can be found in the same location as the Dbvisit Standby database log file. The log file is called <DDC>_arch_management.log. The location is determined by the LOGDIR and LOGDIR_DR settings in the DDC file.

5.  Archivelog Management Settings (AMM)

This section provides an overview of the variables that can be configured for the AMM module with regards to the Primary Database. Unlike the previous versions, the archivelog archive log management module is completely separated from the DDC configurations and now can be edited directly from control center.

...

From the above screen shot the numbers 1 to 7 indicate the settings for managing oracle archivelogs archive logs in the primary database, this is optional if you have your backup jobs that take care of deleting the archivelogs archive logs , you can leave this setting disabled. Remember the archivelogs archive logs must be retained for the dbvisit process to transfer it from primary tostandby. The setting indicated from number 8 to 12 are for managing the standby database archivelogsarchive logs.

GUI field names and DDC variables referrence:

...

5.1 Primary Archive Management Settings

( 1 ) Enable archivelog archive log management on primary: By default, this setting is set to No and you can enable it when you want Dbvisit to manage the archivelogs archive logs from the primary database.

( 2 ) Number of archivelogs archive logs to keep: Specifies the number of archive log files to keep on the primary server. Log Archive log files greater than this number will be removed (oldest first).To disable this setting, set it to 0. If you are not sure, set it to 0 (disable).

( 3 ) Days to keep archive log files: Specify the number of days to keep the archive log files on the primary server. If this value (in days) is reached, the archive log files will be removed from the server. To disable this setting, set it to 0, if you are not sure, set it to 7. Ensure that enough disk space is available to store the archive logs.

...

...

( 8 ) Enable Archive Management on Standby: Specifies if the AMM module to manage the archive log files is turned on or off on the standby server. This is recommended to set to yes as it will manage the archivelogs archive logs that are shipped from primary to standby’s Archivelog Archive log destination location(ARCHDEST).

( 9 ) Number of archive log files to keep: Specifies the number of archive log files to keep on the standby server. Log Archive 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).

( 10 ) Days to keep archive log files: Specifies the number of days to keep the archive log files on the standby server. After this, the archive log files will be removed from the server. This is specific to the archive log destination location in standby from which the archivelog is applied. The archive logs are sent from primary to standby.

...

( 12 ) Delete archive files once threshold is reached?: Specifies if the archive log files should be deleted once the percentage threshold (THRESHOLD_ARCHDEST) on the standby server is reached. Once the threshold is reached the oldest ( archive ) log files are deleted first. 

...

Below is an example of the archive log management settings from both primary and standby. In this example we have set for both primary and standby. We recommend checking the archivelog archive logs and database backup schedules and deletion frequencies before enabling this in the primary.

...