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 the Dbvisit 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 main variables that control the Dbvisit Standby Archive Log Management Module (AMM) processing are:
...
Note | ||
---|---|---|
| ||
|
Dbvisit Standby Archive Log Management Module processing overview
Align |
---|
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. |
Dbvisit Standby Archive Log Management Module log file
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 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.
Backup software
To use the Dbvisit Standby Archive log Management Module together with Backup software that backs up the archive logs, the post-processing option of Dbvisit Standby can be used. The post-processing option of Dbvisit Standby runs after Dbvisit Standby has executed, but before the Archive Management Module executes. This ensures that the archive logs have been backed up before they are removed by the Dbvisit Standby Archive log Management Module. The post-processing option can be called either on the primary or on the standby server or both.
On the primary server:
The sequence of events on the primary server is:
- Dbvisit Standby pre-processing
- Dbvisit Standby transfers the archive logs
- Dbvisit Standby post-processing (Backup software can be scheduled here)
- Dbvisit Standby Archive log Management Module.
On the standby server:
The sequence of events on the standby server is:
...