TOCPREVNEXTINDEX

Lund Performance Solutions


SOS Oracle Detail Events

The Oracle Detail Events Screen

The Oracle Detail Events screen provides statistics related to Oracle database events.
To access the Oracle Detail Events screen from any SOS display screen:
  • Type s from the SOS Enter command: prompt to view the Screen Selection Menu.
  • From the Screen Selection Menu, enter E (upper case). An example of the screen is shown in Figure 40.1.




  • Figure 40.1 SOS Oracle Detail Events screen

    Oracle Detail Events Display Items

    The data values in brackets ([ ]) are cumulative values for the period since SOS was started. (The length of this "elapsed" time is displayed in the SOS banner line as "E: HH:MM:SS.") The data value outside of the brackets is the count for the current interval (displayed in the banner line as "I: MM:SS").

    DB File

    The DB File section of the Oracle Detail Events screen displays counts of various db file events.
    Table 40.1 SOS Oracle Detail Events data items: DB File
    Data Item
    Description
    Sequential Read
    The number of times the session waited while a sequential read from the database was performed. Sequential reads are also used to rebuild the control file, dump datafile headers, and get the database file headers.
    Scattered Read
    The number of times the session waited while a read from multiple data blocks was performed.
    Parallel Read
    The number of times during recovery that database blocks that need to be changed as part of recovery are read in parallel from the database.
    Single Write
    The number of times the session waited for the writing of the file headers.
    Parallel Write
    The number of times the DBWR process performed a parallel write to files and blocks.

    Log File

    The Log File section shows counts of log file events.
    Table 40.2 SOS Oracle Detail Events data items: Log File
    Data Item
    Description
    Sequential Read
    The number of times the session waited for the read from a log file to return. This event is used to read redo records from the log file.
    Sync
    The number of times a user session committed, and flushed the session’s redo information to the redo log file.
    Single Write
    The number of times the session waited for the write to a logfile to complete.
    Parallel Write
    The number of times redo records were written to the redo log files from the log buffer.

    File

    The File section shows file event counts.
    Table 40.3 SOS Oracle Detail Events data items: File
    Data Item
    Description
    Identify
    The number of times the identify event was used to identify a file so that it could be opened later.
    Open
    The number of times the open event was used to open a file.

    Control File

    The Control File section displays control file event statistics.
    Table 40.4 SOS Oracle Detail Events data items: Control File
    Data Item
    Description
    Sequential Read
    The number of times a read from the control file occurred. For example, to:
  • Make a backup of the control files.
  • Share information between instances from the control file.
  • Read other blocks from the control files.
  • Read the header block.
  • Parallel Write
    The number of times a parallel write occurred when the session was writing physical blocks to all control files. This event can take place when:
  • The session starts a control file transaction to make sure that the control files are up-to-date in case the session crashes before committing the control file transaction.
  • The session commits a transaction to a control file, changing a generic entry in the control file, and the new value is written to all control files.
  • Refresh Command
    The number of times Oracle issued a command to refresh the control file for a database.

    Net Events

    The Net Events section displays counts related to net events.
    Table 40.5 SOS Oracle Detail Events data items: Net Events
    Data Item
    Description
    SQL* Net break/reset to client
    The number of times the server sent a break or reset message to the client—the session running on the server waited for a reply from the client.
    SQL* Net message from client
    The number of times the server process (foreground process) waited for a message from the client process to arrive.
    SQL* Net message to client
    The number of times the server (foreground process) sent a message to the client.

    Lund Performance Solutions
    www.lund.com
    Voice: (541) 812-7600
    Fax: (541) 81207611
    info@lund.com
    TOCPREVNEXTINDEX