oracle log files

Jun 25 posted in Oracle (RSS), 104 views.

The following documents from the Oracle.

Routine surveillance of the use of diagnostic files:

• There are the following:
- AlertSID.log document - the background trace file - the user trace file

Monitor the use of diagnostic files document routine diagnosis is to obtain information on the activities of the database as a method. It is also a useful tool for management routines. There are several types of diagnostic files. Created the type of file depends on the diagnosis of the problem or need to disseminate information.
• alertSID.log document: a record day-to-day operation of the database information
• the background trace file: a record of SMON, PMON, DBWn failure of background processes and other important information when
• User tracking documents: records of serious user errors or user documentation enforcement to track important information when

Alert log file
• alertSID.log documents:
- Record order - record of the outcome of major events - used to record day-to-day operation of information - database error for the diagnosis
• each entry with a timestamp associated with
• Must be managed by the DBA
• storage location from the definition of BACKGROUND_DUMP_DEST

The background trace file
• the background to track documents - record of all background processes to detect the error - for the diagnosis and rule out an error
• error in the background process created when you
• storage location from the definition of BACKGROUND_DUMP_DEST

The background trace file the background trace file used to record background processes (such as SMON, PMON, DBWn and other background process) encountered an error.
Only there is a need to write trace file error when the trace file to create the background. You can use them to diagnose and solve the problem. The first track to create the background document, the document contains the instructions of the data server and operating system version number of the header information.
User trace file naming convention: sid_processname_PID.trc (db01_lgwr_23845.trc).
Its storage location defined by the initialization parameter BACKGROUND_DUMP_DEST.

Users to track documents
• User tracking document - generated by the user process - generated by the server process - contains the SQL statement to track statistical information - the error message contains the user
• errors in the user session is created when you encounter
• storage location from the definition of USER_DUMP_DEST
• the definition of size by MAX_DUMP_FILE_SIZE

Users to track the user trace file contains the SQL statement to track statistical information, which is very useful in SQL optimization. In addition, the user trace file contains the user an error message.
User trace file naming convention: sid_ora_PID.trc (db01_ora_23845.trc).
Its storage location defined by the initialization parameter USER_DUMP_DEST.

Enable or disable user tracking
• Session level:
- Use ALTER SESSION command:
ALTER SESSION SET SQL_TRACE = TRUE
- The process of implementation of DBMS:
dbms_system.SET_SQL_TRACE_IN_SESSION
• routine level - set the initialization parameters:
SQL_TRACE = TRUE

Enable or disable user tracking Note: In the routine level SQL_TRACE = TRUE will be set up to generate a large number of tracking data. Therefore, in order to use this option with caution.