Date: Fri, 29 Mar 2024 04:41:17 +0000 (UTC) Message-ID: <859901299.15.1711687277708@fbad8371d7ee> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_14_636570677.1711687277708" ------=_Part_14_636570677.1711687277708 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This section will provide you with more information about how the Dbvisi= t Standby version 10 manages log and trace files.
Dbvisit Standby produces temporary files in the TMPDIR directory (can be= specified in the DDC file) every time Dbvisit Standby executes.
The default location for the TMPDIR variable is in the DBVISIT_= BASE/standby/tmp
The TMPDIR location is also used during the refresh one datafile operati= on. The backup is created in this location (using compressed RMAN bac= kups). It is therefore recommended to make sure this location has suf= ficient space available.
/usr/dbvisit/standby/tmp
C:\Program Files\dbvisit\standby\tmp
The temporary files are automatically deleted when Dbvisit Standby finis= hes execution.
Do not set REMOVE_TEMP_FILE=3DN in the Dbvisit Configuration File (DDC) = unless instructed by the Dbvisit support.
If this value is set all temporary files will be NOT be deleted when Dbv= isit Standby has completed processing, which can interfere with the next sc= heduled run.
This setting does not apply to Dbvisit Standby trace files.
Dbvisit Standby trace files are files that are created every time Dbvisi= t Standby executes, these trace files contain a large amount of inform= ation about the execution of Dbvisit Standby and can be sent to Dbvisit sup= port for fast issue resolution.
Trace files are created in the TRCDIR (trace) directory (can be specifie= d in the DDC file).
The default location for the TRCDIR variable is in the DBVISIT_= BASE/standby/trace
/usr/dbvisit/standby/trace
C:\Program Files\dbvisit\standby\trace
Dbvisit Standby trace files have the following format: <pid>= _dbvisit_<DDC>_<function>_<yyyymmddhhmi>.trc
The trace file starts with a number also known as the process number of = the process that generated the trace file, it is followed by the name dbvis= it, then the DDC name and then the timestamp with extension .t= rc.
Dbvisit Standby trace files are automatically deleted according to setti= ngs specified in the DDC file. The following settings (located in the= DDC file) can be used to manage the maintenance of the trace files:
The least restrictive setting applies between DAYS_TO_KEEP_TRACE and NUM= _TRACE_TO_KEEP.
To turn off these maintenance settings, set to 0.
Dbvisit Standby produces two log dbvisit.hist and the Dbvisit Standby Ar= chivelog Management Module (AMM) log file in the format <DDC>_arch_ma= nagement.logfiles
The default location for the LOGDIR variable is in the DBVISIT_= BASE/standby/log
/usr/dbvisit/standby/log
C:\Program Files\dbvisit\standby\log
These log files will automatically be kept at a specific size based on t= he following settings specified in the Dbvisit Database Configuration File = (DDC).
Default Value: 5
Indicates how many backups are made of the log files before it is overwr= itten.
Default Value: 5
Indicates the size of the log file before the log file is rotated as abo= ve.
In some cases it might be required to move the default LOG, TRACE and TM= P locations for the Dbvisit Standby log, trace and temp files.
The default location should be sufficient for most environments, but if = you do want to move these directories to a different location, you can use = the LOGDIR, TRCDIR and TMPDIR directory parameters in the DDC file. <= /p>
There are also standby equivalent parameters with the _DR at the end (LO= GDIR_DR, TRCDIR_DR and TMPDIR_DR).
The following parameters can be set in the DDC file to overwrite the def= ault locations of these directories inside DBVISIT_BASE/standby:
LOGDIR=3D/your_primary_log_dir_location TRCDIR=3D/your_primary_trace_dir_location TMPDIR=3D/your_primary_temp_dir_location LOGDIR_DR=3D/your_standby_server_log_location TRCDIR_DR=3D/your_standby_server_trace_location TMPDIR_DR=3D/your_standby_server_temp_location
When you execute a Dbvisit Standby process, example the sending and appl= ying of logs. You will notice the header "banner" is displayed, which= contains a process id see example below where it is (pid 18054)
[oracle= @dbvel71 standby]$ ./dbvctl -d orcl -i =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Dbvisit Standby Database Technology (10.0.0RC_24_g94ba1d85) (pid 18054) dbvctl started on dbvel71: Thu Dec 3 13:22:54 2020 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ... ... ...
Now to identify the trace file for this process, review the trace direct= ory under DBVISIT_BASE/standby/trace and search for the file that starts wi= th this process id number - 18054