Dbvisit Standby Trace Files

Dbvisit Standby produces trace file every time it executes. The trace files can be sent to Dbvisit support for investigation, error resolution and analysis.
The Dbvisit Standby trace files are meant for Dbvisit support services only and do not contain information helpful to the user.
The Dbvisit Standby trace file can be identified as follows:

  • The trace filename will start with a number (process id), then the name of the dbvisit executable (dbvisit, dbv_oraStartSop, dbv_functions or dbvisit_setup)n, then the name of the DDC file and then the timestamp and will end with extension .trc.

(Example 3118_dbv_functions_prod10g_200610091322.trc)

  • The location of the trace file is DBVISIT_BASE/standby/tmp on the primary and DBVISIT_BASE_DR/standby/tmp. To overwrite default location, set TMPDIR and TMPDIR_DR (not recommended)
  • The trace filename will be displayed in the email that is sent by Dbvisit Standby when an error or alert is triggered.

Manage trace files

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 = 200 
DAYS_TO_KEEP_TRACE = 15

Least restrictive setting applies between DAYS_TO_KEEP_TRACE and NUM_TRACE_TO_KEEP.   To turn off, set to 0.

 

Â