After completing this lesson, you should be able to do the following: Identify key tuning components of the alert log file Identify key tuning components of background trace files Identify key tuning components of user trace files Collect statistics with Oracle Enterprise Manager Describe how Statspack collects statistics Collect statistics with Statspack Identify dynamic performance views useful in tuning Describe other tools used for tuning | Diagnostic and Tuning Tools Objectives After completing this lesson, you should be able to do the following: Identify key tuning components of the alert log file Identify key tuning components of background trace files Identify key tuning components of user trace files Collect statistics with Oracle Enterprise Manager Describe how Statspack collects statistics Collect statistics with Statspack Identify dynamic performance views useful in tuning Describe other tools used for tuning Maintenance of the Alert Log File The alert log file consists of a chronological log of messages and errors. Check the alert log file regularly to: Detect internal errors (ORA-600) and block corruption errors Monitor database operations View the nondefault initialization parameters Remove or trim the file regularly after checking. The Alert Log File It is important for the database administrator to check the alert log file regularly to detect problems before they become serious. The following information is | Diagnostic and Tuning Tools Objectives After completing this lesson, you should be able to do the following: Identify key tuning components of the alert log file Identify key tuning components of background trace files Identify key tuning components of user trace files Collect statistics with Oracle Enterprise Manager Describe how Statspack collects statistics Collect statistics with Statspack Identify dynamic performance views useful in tuning Describe other tools used for tuning Maintenance of the Alert Log File The alert log file consists of a chronological log of messages and errors. Check the alert log file regularly to: Detect internal errors (ORA-600) and block corruption errors Monitor database operations View the nondefault initialization parameters Remove or trim the file regularly after checking. The Alert Log File It is important for the database administrator to check the alert log file regularly to detect problems before they become serious. The following information is logged in the alert log file: Internal errors (ORA-600) and block corruption errors (ORA-1578 or ORA-1498) Operations that affect database structures and parameters, and statements such as CREATE DATABASE, STARTUP, SHUTDOWN, ARCHIVE LOG, and RECOVER The values of all non-default initialization parameters at instance startup The location of the alert log file is given by the BACKGROUND_DUMP_DEST parameter Tuning Components of the Alert Log File The alert log file contains the following information which can be used in tuning the database: Checkpoint start and end times Incomplete checkpoints Time to perform archiving Instance recovery start and complete times Deadlock and timeout errors Checkpoint Start and End Times These values are written into the alert log file only if the LOG_CHECKPIONTS_TO_ALERT parameter has been set to True. Background Processes Trace Files The Oracle server dumps information about errors detected by any background process into trace files. Oracle Support uses .
