Dbvisit Replicate offers automatic house keeping (housekeeping) on the following files:
Dbvisit Replicate
...
PLOG files
The management of plog PLOG files on source and target systems are done according to the following settings:
| Default | ||
|---|---|---|
| DELETE_OBSOLETE_PLOGS_AGE | Delete plogs PLOGS after specific time period. Time period can be days (d) or hours(h) | 3d |
| DELETE_OBSOLETE_PLOGS_SIZE_MB | Delete plogs PLOGS are total size of all plogs PLOGS exceeds size in MB | 1024 |
| DELETE_OBSOLETE_PLOGS_GZIP | Compress the plogs PLOGS as soon as they are not needed by Dbvisit Replicate anymore | Yes |
The management of the plogs PLOGS can be found in the MineMINE/Apply APPLY log files by searching for "plog maintenance with settings".
The management is done on every plog 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 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 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 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
...
| No Format | ||
|---|---|---|
| ||
LIST OBSOLETE REDO [THREAD thread] |
The oldest archive log that MINE will ever need is "last obsolete sequence" + 1
The oldest archive log that APPLY wil will ever need is the sequence # that APPLY is working on
Scripting the output of the "list status" command
...
| No Format | ||
|---|---|---|
| ||
start-console.sh --silent engine mine send engine status | grep Sequence start-console.sh --silent engine apply send engine status | grep Sequence |
The Mine MINE process returns the plog PLOG sequence and the redo sequence. If RAC is not used, then this number will be the same.
...