Dbvisit Replicate offers automatic house keeping (housekeeping) on the following files:
...
| Default | ||
|---|---|---|
| DELETE_OBSOLETE_PLOGS_AGE | Delete PLOGs after specific time period. Time period can be days (d) or hours(h) | 3d |
| DELETE_OBSOLETE_PLOGS_SIZE_MB | Delete PLOGs are total size of all PLOGs exceeds size in MB | 1024 |
| DELETE_OBSOLETE_PLOGS_GZIP | Delete Compress the PLOGs as soon as they are not needed by Dbvisit Replicate anymore | Yes |
The management of the PLOGs can be found in the MINE/APPLY log files by searching for "plog maintenance with settings".
| Note |
|---|
The management of plogs is only done on every PLOG switch. |
Last obsolete plog on Apply
The last plog (last obsolete plog) needed on apply can be found by searching in the Apply log for the following string:
| No Format |
|---|
First plog needed (and thus not eligible for deletion): |
If Apply is restarted, it will start processing from this plog.
| Note |
|---|
The last obsolete plog information is only updated on every PLOG switch. |
Dbvisit Replicate redo files
If the FETCHER process is used, then redo logs are transferred from the source database server to the server where the MINE process running. The management of these redo logs are done according to the following settings:
| Default | ||
|---|---|---|
| DELETE_OBSOLETE_RLOGS_AGE | Delete the redo logs transferred from FETCHER after specific time period. Time period can be days (d) or hours(h). | 3d |
| DELETE_OBSOLETE_RLOGS_SIZE_MB | Delete the redo logs transferred from FETCHER after total size of all PLOGs exceeds size in MB. | 1024 |
| DELETE_OBSOLETE_RLOGS_GZIP | Delete Compress the redo logs transferred from FETCHER as soon as they are not needed by Dbvisit Replicate anymore. | Yes |
The management of the redo logs can be found in the MINE log files by searching for "rlog maintenance with settings". If there are long running transactions, then the oldest redo logs belonging to the start of the transactions will be kept. Use the command dbvrep> LIST OBSOLETE REDO to identify the oldest redo log required. This is very important, if MINE is shutdown, when MINE restarts it will start at the redo specified.
The management is done on every log switch. The redo logs are located in a directory called mine_stage.
** Note if the result of performing dbvrep> list obsolete redo goes back more than 24 hours you may wish to check long running transactions or uncommitted transactions with idle sessions using http://support.dbvisit.com/hc/en-us/articles/215913398-Oldest-redo-log-sequence-required-by-MINE
Dbvisit Replicate log files
- . These are set managed to keep one backup file and a size limit of 100MB. This is configurable through the parameters:
- LOG_FILE_SIZE
- LOG_FILE_COUNT
- LOG_FILE_DATE_ROTATE
...