Primary Archive log Management Module (AMM)
Please see Archive log Management Module (AMM) for more information on AMM.
| Variable Name | Meaning |
|---|---|
| ARCHSOURCE_MANAGEMENT | Specifies if the AMM module to manage the archive log files is turned on or off on the primary server. |
| Values are Yes or No | |
| Yes = Turn on AMM on primary server. | |
| No = Turn off AMM on primary server. | |
| If you are not sure, set to Yes. | |
| Example: | |
| ARCHSOURCE_MANAGEMENT= Yes | |
| DAYS_TO_KEEP_ARCHSOURCE | Specifies the number of days to keep the Oracle log files on the primary server. |
| After this the log files will be removed from the server. | |
| To disable this setting, set to 0. | |
| If you are not sure, set to 7. | |
| Example: | |
| DAYS_TO_KEEP_ARCHSOURCE = 7 | |
| 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 | |
| ARCHSOURCE_BACKUP_COUNT | Specifies 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. | |
If you are not sure, set to 0. This uses column BACKUP_COUNT from v$archived_log to determine if the archive log file should be removed up or not. This column is updated by RMAN. | |
| Example: | |
| ARCHSOURCE_BACKUP_COUNT = 0 | |
| THRESHOLD_ARCHSOURCE | Specifies the threshold in percentage (%) of how much disk space may be taken up by the Oracle log files on disk before an alert is triggered on the primary server. |
| 80 means at 80% disk space full an alert will be triggered. | |
| Please specify threshold as an integer. | |
| If you are not sure, set to 80. | |
| Example: | |
| THRESHOLD_ARCHSOURCE = 80 | |
| FRA_THRESHOLD_ARCHSOURCE | Specifies the threshold in percentage (%) of how much FRA space may be taken up by the Oracle log files on disk before an alert is triggered on the primary server. |
| 80 means at 80% FRA space full an alert will be triggered. | |
| Please specify threshold as an integer. | |
| If you are not sure, set to 80. | |
| Example: | |
| FRA_ THRESHOLD_ARCHSOURCE = 80 | |
| DELETE_ARCHSOURCE | Specifies 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. | |
| The log files WILL have been transferred to the standby server. | |
| (There is no verification that these log files have been backed up). | |
| Values are Yes or No | |
| 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_ARCHSOURCE = No | |
| 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. |