...
Dbvisit Standby trace files are files that are created every time Dbvisit Standby executes. Dbvisit Standby trace files can be sent to Dbvisit support for fast issue resolution.
Trace files are created in the TMP* directory. The trace filename will start with a number, then the name dbvisit, then the database name and then the timestamp and will end with extension .trc.
Example:
3118_dbvisit_prod10g_200901091322.trc
Since Dbvisit Standby version 5.1.19, Dbvisit Standby trace files are automatically deleted according to settings:
NUM_TRACE_TO_KEEP
= The number of trace files to keep after which trace files are deleted.
DAYS_TO_KEEP_TRACE
= The number of days to keep the trace files after which trace files are deleted.
Default settings are:
NUM_TRACE_TO_KEEP
...
=
...
100
...
DAYS_TO_KEEP_TRACE
...
=
...
10
Least restrictive setting applies between DAYS_TO_KEEP_TRACE and NUM_TRACE_TO_KEEP.
To turn off, set to 0.
Prior to version 5.1.19 Dbvisit Standby trace files are not removed.
...
The Dbvisit Standby log file (dbvisit.hist) and the Dbvisit Standby archive management module log file (<DDC>_arch_management.log) will automatically be kept at a specific s
| Anchor | ||||
|---|---|---|---|---|
|
LOG_FILE_ROTATE_MAX
LOG_FILE_SIZE_MAX_MB
LOG_FILE_ROTATE_MAX indicates how many backups are made of the log files before it is overwritten.
The
...
first
...
backup
...
will
...
be:
...
dbvisit_hist.log.1
The
...
second
...
backup
...
will
...
be:
...
dbvisit_hist.log.2
etc.
LOG_FILE_SIZE_MAX_MB indicates the size of the log file before the log file is rotated as above.
Example:
LOG_FILE_ROTATE_MAX
...
=
...
5
LOG_FILE_SIZE_MAX_MB
...
=
...
5
This setting ensures the maximum size of the Dbvisit Standby log file will be 5MB. If the log file is greater than 5MB, it will be copied to a backup log file.
This setting ensures there will be 5 backup versions of the Dbvisit Standby log file before backup versions of the log file will be overwritten.
...