![]() The values of all initialization parameters that had nondefault values at the time the database and instance start Messages and errors relating to the functions of shared server and dispatcher processesĮrrors occurring during the automatic refresh of a materialized view The alert log is a chronological log of messages and errors, and includes the following items:Īll internal errors ( ORA-00600), block corruption errors ( ORA-01578), and deadlock errors ( ORA-00060) that occurĪdministrative operations, such as some CREATE, ALTER, and DROP statements and STARTUP, SHUTDOWN, and ARCHIVELOG statements See Diagnosing and Resolving Problems for more information. Therefore, to track tracing for a specific session that connects using a dispatcher, you might have to explore several shared server trace files.Ĭritical errors also create incidents and incident dumps in the Automatic Diagnostic Repository. If shared server is enabled, each session using a dispatcher is routed to a shared server process, and trace information is written to the server trace file only if the session has enabled tracing (or if an error is encountered). ![]() Reading the Trace File for Shared Server Sessions.Controlling When Oracle Database Writes to Trace Filesīackground processes always write to a trace file when appropriate.You can control the maximum size of all trace files (excluding the alert log) using the initialization parameter MAX_DUMP_FILE_SIZE. Otherwise the database continues to append to the file. To control the size of an alert log, you must manually delete the file when you no longer need it. The trace file and alert log contain information about errors. About Monitoring Errors with Trace Files and the Alert Log.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |