This screen displays the current CPU utilization of each database
    process on the node as a percentage of the total processor
    utilization.

    This screen displays one line of information for each database
    process active on the node. If a process is attached to the
    database multiple times, the screen displays only one line of
    information.

    If the number of displayable processes is greater than the number
    of displayable lines, use the right arrow or up arrow and the
    left arrow or right arrow to navigate through the display pages.

    For each active database process, the CPU Utilization screen
    shows the following:

    o  Process ID

    o  Process name

    o  CPU utilization percentage of that process

       The histogram portion of the display shows the process'
       utilization percentage in graph format.

    Note that the displayed process CPU utilization, in addition to
    the database-related processing, includes the CPU utilization
    of ALL non-database related activities that the process also
    performs. In order to track the exact CPU utilization of the
    database-specific activity, Oracle Corporation recommends that
    you use Oracle Trace.

    By default, the processes on the screen appear in arbitrary
    (unsorted) order. By selecting the Config option, you can
    manually configure the CPU Utilization screen. Choose the Config
    option, by typing C, to display the CPU Utilization Configuration
    menu. This menu offers the following options:

    o  A. Unsorted Display

       Option A displays the processes in unsorted order.

    o  B. Sort by CPU Utilization

       Option B displays the processes sorted in order of descending
       CPU utilization. This display configuration can be difficult
       to view when the display rate is less than two seconds since
       the process CPU utilizations vary at any given time. Oracle
       Corporation recommends that you use the sorted display with a
       display rate of two seconds or more.

    The CPU Utilization screen is not saved by using the Output
    qualifier, therefore it cannot be replayed using the Input
    qualifier.