Dbvisit Replicate offers automatic house keeping (housekeeping) on the following files:
...
The management of the plogs can be found in the Mine/Apply log files by searching for "plog maintenance with settings".
The management is done 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 are transferred from Fetcher after total size of all plogs exceeds size in MB. | 1024 |
| DELETE_OBSOLETE_RLOGS_GZIP | 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".
The management is done on every log switch. The redo logs are located in a directory called mine_stage.
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
...