The Dbvisit Standby Archive Log Management Module fully automates the management and monitoring of the Oracle archive log space on either the primary, standby server or both. Unlike the Oracle database files location, the Oracle archive logs location needs to be monitored and managed constantly to ensure the database continues its optimal operation. If the disk space available to Oracle archive logs is used up, the whole database will "freeze" and not allow any update or insert operation.
Follow the on-screen instructions to install AMM or please see theDbvisit Standby Archive log Management Module (AMM) setup section for description of each step.
Home > Setup > Update Dbvisit > Update Dbvisit Configuration. Choose the AMM settings to update and click on Save Configuration.
Dbvisit Standby Archive Log Management Module variables
The order of precedence in managing the log files are:
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.