Oracle7 Getting Started for Windows NT | ![]() Library |
![]() Product |
![]() Contents |
![]() Index |
Database Monitoring Overview
The following tools and procedures enable you to monitor and manipulate your server.
Each tool and procedure is described in the following sections.
Using Performance Monitor
To use the Performance Monitor to monitor and analyze Oracle7 Server for Windows NT database performance, you must first install the Oracle7 Performance Utility. The Oracle7 Performance Utility enables Database Administrators to monitor local and remote database performance through the Performance Monitor. Accessing the Performance Monitor
Monitoring Oracle7 Objects
When you monitor the database, you are essentially monitoring the behavior of its objects. In Windows NT, an object is a mechanism for identifying and using a system resource. Oracle7 objects represent sections of shared memory, tuning I/O, and tuning contention. Each Oracle7 object has a set of counters that produce statistical information. The following table shows the Oracle7 objects and their associated counters. For additional information on these objects, refer to Oracle7 Server Tuning, Release 7.3.3
Oracle7 Specific Information
The following list describes information specific to Oracle7 when you use the Windows NT Performance Monitor.
These values are located in the Windows NT Registry. Follow the procedures below to edit these values:
C:\> REGEDT32The Windows NT Registry opens.
|
As with other events displayed in the Event Viewer, you can double-click on them to display more detailed error information.
|
|
Using Trace and Alert Files
Trace Files
Oracle7 Server for Windows NT background threads use trace files to record occurrences and exceptions of database operations, as well as errors. Background thread trace files are created regardless of whether the BACKGROUND_DUMP_DEST parameter is set in the initialization parameter file. If BACKGROUND_DUMP_DEST is set, the trace files are stored in the directory specified. If the parameter is not set, the trace files are stored in the ORANT\RDBMS73\TRACE directory.
Trace files are also created for user threads if the USER_DUMP_DEST parameter is set in the initialization parameter file. The trace files for the user threads have the form ORAxxxxx.TRC, where xxxxx is a 5-digit number indicating the Windows NT thread ID.
For example, when automatic archiving of redo logs is halted because no disk space is available, a message is placed in the alert file. The alert file is the first place you should check if something goes wrong with the database and the cause is not immediately obvious.
The alert file is named sidALRT.LOG and is found in the directory specified by the BACKGROUND_DUMP_DEST parameter in the initialization parameter file. If the BACKGROUND_DUMP_DEST parameter is not set, the sidALRT.LOG file is generated in ORANT\RDBMS73\TRACE.
![]() ![]() Prev Next |
![]() Copyright © 1996 Oracle Corporation. All Rights Reserved. |
![]() Library |
![]() Product |
![]() Contents |
![]() Index |