...
AMM will perform archivelog deletion on primary after successful archivelog transfer
Criteria 1&2: AMM will delete any archivelogs exceeding the count of 100 file (oldest first) AND it will not delete any archivelog which less than exactly 1 day old
Criteria 3: AMM will delete only archivelogs which were backed up at least 1 time by RMAN
there is logical AND between criteria 1 & 2 & 3
If disk space where primary archivelogs reside is more than 85% used, dbvisit will disregard criteria 1,2 and 3 and delete archivelos in an attempt to get below the threshold
If disk FRA of primary database is more than 85% used, dbvisit will disregard criteria 1,2 and 3 and delete archivelos in an attempt to get below the threshold
...
2.4 Primary AMM advanced options
These options are by default not shown in dbvcontrol GUI and user must add manually parameters to the DDC file to enable these options. It is because they are only valid for specific use cases. Refer to https://dbvisit.atlassian.net/wiki/spaces/DSMPV12/pages/4446683207/Modifying+DDC+parameters for details how to modify DDC parameters.
A. Multiple Standby Databases and Primary AMM
In the case of multiple standby databases, Dbvisit Standby checks if an archive log has been transferred to all active standby databases before deleting it on the primary.
...
This value must be manually set in the DDC file, it is not possible to use dbvcontrol.
B. Multiple Archivelog Destinations with ARCHSOURCE_BACKUP_COUNT enabled on primary database and AMM
In case there are multiple archivelog destinations specified on the primary database AND ARCHSOURCE_BACKUP_COUNT is set as well, it is possible to further control behavior of AMM by setting following parameter in DDC file:
| Code Block |
|---|
AMM_BACKUP_COUNT_FUNCTION=SUM |
value SUM means that if you have log_archive_dest_1 and log_archive_dest_2 then it is enough if archivelog is backed up in one of the locations (or both locations) for the criteria ARCHSOURCE_BACKUP_COUNT to be fulfilled.
Otherwise AMM_BACKUP_COUNT_FUNCTION has default value MIN meaning that archivelog must be backed up ARCHSOURCE_BACKUP_COUNT times in log_archive_dest_1 AND in log_archive_dest_2 at the same time, otherwise the ARCHSOURCE_BACKUP_COUNT criteria isn't fulfilled.
3. Standby Database Archivelogs and AMM
Archivelogs on standby server are Dbvisit specific and we recommed to enable AMM in every case. AMM should be always enabled for standby. AMM then deletes all archivedlogs from ARCHDEST location (ARCHDEST is specified during DDC creation). There are never any archivelogs placed in Standby database db_recovery_file_dest or log_archive_dest by Dbvisit StandbyMP.
...