54 - Enterprise Manager Metric Reference Manual

Oracle® Enterprise Manager
Metric Reference Manual

10g Release 1 (10.1)
Part No. B12015-01
June 2004
Oracle Enterprise Manager Metric Reference Manual, 10g Release 1 (10.1)
Part No. B12015-01
Copyright © 2004, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they
are provided under a license agreement containing restrictions on use and disclosure and are also protected
by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly,
or decompilation of the Programs, except to the extent required to obtain interoperability with other
independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in
the documentation, please report them to us in writing. This document is not warranted to be error-free.
Except as may be expressly permitted in your license agreement for these Programs, no part of these
Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on
behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data
delivered to U.S. Government customers are "commercial computer software" or "commercial technical data"
pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As
such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation
and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license
agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial
Computer Software--Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City,
CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy and other measures to ensure the safe use of such applications if the Programs are used for such
purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks
of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third
parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites.
You bear all risks associated with the use of such content. If you choose to purchase any products or services
from a third party, the relationship is directly between you and the third party. Oracle is not responsible for:
(a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the
third party, including delivery of products or services and warranty obligations related to purchased
products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from
dealing with any third party.
Contents
Send Us Your Comments .................................................................................................................. xxxix
Preface ................................................................................................................................................................ xli

Intended Audience..................................................................................................................................... xli
Purpose of This Manual ............................................................................................................................ xli
Documentation Accessibility .................................................................................................................... xli
Structure ..................................................................................................................................................... xlii
Related Documents ................................................................................................................................... xlv
Conventions .............................................................................................................................................. xlvi
1 How To Use This Manual

Structure of the Metric Reference Manual............................................................................................ 1-1
Metric Information............................................................................................................................. 1-1
Examples of Metric Summary Tables.............................................................................................. 1-2
Definitions of Columns in Metric Summary Tables ..................................................................... 1-2
Abbreviations and Acronyms .......................................................................................................... 1-3
Background Information on Metrics, Thresholds, and Alerts ........................................................ 1-4
Editing Thresholds............................................................................................................................. 1-4
Specifying Multiple Thresholds ....................................................................................................... 1-4
Accessing Metrics Using the Grid Control Console...................................................................... 1-5
Part I Oracle Database Metrics
2 Database
Alert Log..................................................................................................................................................... 2-1
Alert Log Error Trace File ................................................................................................................. 2-1
Alert Log Name .................................................................................................................................. 2-1
Archiver Hung Alert Log Error ....................................................................................................... 2-2
Data Block Corruption Alert Log Error .......................................................................................... 2-3
Generic Alert Log Error..................................................................................................................... 2-3
Session Terminated Alert Log Error................................................................................................ 2-4
Alert Log Error Status .............................................................................................................................. 2-5
Archiver Hung Alert Log Error Status............................................................................................ 2-5
Data Block Corruption Alert Log Error Status .............................................................................. 2-6
Generic Alert Log Error Status......................................................................................................... 2-6
iii
Session Terminated Alert Log Error Status.................................................................................... 2-7
Archive Area.............................................................................................................................................. 2-7
Archive Area Used (%)...................................................................................................................... 2-8
Archive Area Used (KB).................................................................................................................... 2-9
Free Archive Area (KB) .................................................................................................................. 2-10
Total Archive Area (KB)................................................................................................................. 2-11
Data Guard ............................................................................................................................................. 2-11
Data Guard Status ........................................................................................................................... 2-12
Data Not Applied (logs) ................................................................................................................ 2-12
Data Not Applied (MB) ................................................................................................................. 2-13
Data Not Received (logs) ............................................................................................................... 2-14
Data Not Received (MB)................................................................................................................. 2-15
Database Files ........................................................................................................................................ 2-16
Average File Read Time (centi-seconds)...................................................................................... 2-16
Average File Write Time (centi-seconds)..................................................................................... 2-17
Database Job Status .............................................................................................................................. 2-18
Broken Job Count ............................................................................................................................ 2-18
Failed Job Count .............................................................................................................................. 2-18
Database Limits ..................................................................................................................................... 2-19
Current Logons Count.................................................................................................................... 2-19
Current Open Cursors Count........................................................................................................ 2-20
Lock Limit Usage (%) ..................................................................................................................... 2-20
Process Limit Usage (%)................................................................................................................. 2-21
Session Limit Usage (%) ................................................................................................................. 2-22
User Limit Usage (%)...................................................................................................................... 2-23
Database Services .................................................................................................................................. 2-24
Service CPU Time (per user call) (microseconds) ...................................................................... 2-24
Service Response Time (per user call) (microseconds).............................................................. 2-24
Deferred Transactions........................................................................................................................... 2-25
Deferred Transaction Count .......................................................................................................... 2-25
Deferred Transaction Error Count................................................................................................ 2-26
Dump Area ............................................................................................................................................. 2-27
Dump Area Directory..................................................................................................................... 2-27
Dump Area Used (%) ..................................................................................................................... 2-27
Dump Area Used (KB) ................................................................................................................... 2-28
Free Dump Area (KB) ..................................................................................................................... 2-29
Total Dump Area (KB).................................................................................................................... 2-30
Efficiency................................................................................................................................................. 2-30
Buffer Cache Hit (%) ....................................................................................................................... 2-30
CPU Usage (per second) ................................................................................................................ 2-32
CPU Usage (per transaction) ......................................................................................................... 2-32
Cursor Cache Hit (%)...................................................................................................................... 2-33
Data Dictionary Hit (%).................................................................................................................. 2-33
Database CPU Time (%) ................................................................................................................. 2-34
Library Cache Hit (%)..................................................................................................................... 2-35
Library Cache Miss (%) .................................................................................................................. 2-36
Parallel Execution Downgraded (per second) ............................................................................ 2-37
iv
Parallel Execution Downgraded (per transaction) ..................................................................... 2-38
Parallel Execution Downgraded 25% or more (per second)..................................................... 2-38
Parallel Execution Downgraded 25% or more (per transaction).............................................. 2-39
Parallel Execution Downgraded to Serial (per second)............................................................. 2-42
Parallel Execution Downgraded to Serial (per transaction) ..................................................... 2-42
PGA Cache Hit (%) ......................................................................................................................... 2-43
Redo Log Allocation Hit (%) ......................................................................................................... 2-43
Response Time (per transaction)................................................................................................... 2-44
Row Cache Miss Ratio (%) ............................................................................................................. 2-45
Sorts in Memory (%) ....................................................................................................................... 2-45
Global Cache Statistics......................................................................................................................... 2-47
Global Cache Average Convert Time (centi-seconds) ............................................................... 2-47
Global Cache Average CR Block Request Time (centi-seconds) .............................................. 2-47
Global Cache Average Current Block Request Time (centi-seconds)...................................... 2-48
Global Cache Average Get Time (centi-seconds) ....................................................................... 2-49
Global Cache Blocks Corrupt ........................................................................................................ 2-49
Global Cache Blocks Lost ............................................................................................................... 2-50
Idle Events .............................................................................................................................................. 2-51
Invalid Objects....................................................................................................................................... 2-53
Total Invalid Object Count............................................................................................................. 2-53
Invalid Objects by Schema.................................................................................................................. 2-53
Owner's Invalid Object Count....................................................................................................... 2-54
Recovery Area ........................................................................................................................................ 2-54
Recovery Area Free Space (%)....................................................................................................... 2-54
Response ................................................................................................................................................. 2-55
State ................................................................................................................................................... 2-55
Status................................................................................................................................................. 2-55
User Logon Time (msec) ................................................................................................................ 2-56
Session Suspended ............................................................................................................................... 2-56
Session Suspended by Data Object Limitation ........................................................................... 2-56
Session Suspended by Quota Limitation..................................................................................... 2-57
Session Suspended by Rollback Segment Limitation ................................................................ 2-57
Session Suspended by Tablespace Limitation ............................................................................ 2-57
SGA Pool Wastage................................................................................................................................. 2-57
Java Pool Free (%) ........................................................................................................................... 2-57
Large Pool Free (%) ......................................................................................................................... 2-58
Shared Pool Free (%)....................................................................................................................... 2-58
Snapshot Too Old .................................................................................................................................. 2-59
Snapshot Too Old due to Rollback Segment Limit .................................................................... 2-59
Snapshot Too Old due to Tablespace Limit ................................................................................ 2-60
SQL Response Time.............................................................................................................................. 2-60
SQL Response Time (%) ................................................................................................................. 2-60
Suspended Session ............................................................................................................................... 2-61
v
Suspended Session Count.............................................................................................................. 2-61
System Response Time Per Call ......................................................................................................... 2-62
System Response Time (centi-seconds)........................................................................................ 2-62
System Sessions Waiting ..................................................................................................................... 2-62
Waiting Session Count ................................................................................................................... 2-63
Tablespaces Full..................................................................................................................................... 2-63
Tablespace Space Used (%)............................................................................................................ 2-63
Tablespaces Full (dictionary managed)............................................................................................. 2-65
Tablespace Space Used (%) (dictionary managed) .................................................................... 2-65
Tablespaces With Problem Segments................................................................................................ 2-65
Segments Approaching Maximum Extents................................................................................. 2-66
Segments Approaching Maximum Extents Count..................................................................... 2-66
Segments Not Able to Extend ....................................................................................................... 2-67
Segments Not Able to Extend Count ........................................................................................... 2-67
Throughput............................................................................................................................................. 2-68
All Sessions ...................................................................................................................................... 2-68
BG Checkpoints (per second) ........................................................................................................ 2-69
Branch Node Splits (per second)................................................................................................... 2-69
Branch Node Splits (per transaction) ........................................................................................... 2-70
Consistent Read Blocks Created (per second) ............................................................................ 2-70
Consistent Read Blocks Created (per transaction) ..................................................................... 2-71
Consistent Read Changes (per second)........................................................................................ 2-71
Consistent Read Changes (per transaction) ................................................................................ 2-72
Consistent Read Gets (per second) ............................................................................................... 2-72
Consistent Read Gets (per transaction)........................................................................................ 2-73
Consistent Read Undo Records Applied (per second) .............................................................. 2-74
Consistent Read Undo Records Applied (per transaction)....................................................... 2-74
Cumulative Logons (per second).................................................................................................. 2-75
Cumulative Logons (per transaction) .......................................................................................... 2-75
Database Block Changes (per second) ......................................................................................... 2-76
Database Block Changes (per transaction) .................................................................................. 2-77
Database Block Gets (per second)................................................................................................. 2-77
Database Block Gets (per transaction) ......................................................................................... 2-78
DBWR Checkpoints (per second) ................................................................................................. 2-79
Enqueue Deadlocks (per second).................................................................................................. 2-80
Enqueue Deadlocks (per transaction) .......................................................................................... 2-81
Enqueue Requests (per second) .................................................................................................... 2-81
Enqueue Requests (per transaction) ............................................................................................. 2-82
Enqueue Timeout (per second) ..................................................................................................... 2-82
Enqueue Timeout (per transaction).............................................................................................. 2-83
Enqueue Waits (per second) .......................................................................................................... 2-83
Enqueue Waits (per transaction)................................................................................................... 2-84
Executes (per second) ..................................................................................................................... 2-84
Executes Performed without Parses (%)...................................................................................... 2-85
Full Index Scans (per second)........................................................................................................ 2-86
Full Index Scans (per transaction) ................................................................................................ 2-86
Hard Parses (per second) ............................................................................................................... 2-87
vi
Hard Parses (per transaction)........................................................................................................ 2-88
Leaf Node Splits (per second) ....................................................................................................... 2-90
Leaf Node Splits (per transaction) ................................................................................................ 2-90
Network Bytes (per second) .......................................................................................................... 2-91
Number of Transactions (per second).......................................................................................... 2-92
Open Cursors (per second) ............................................................................................................ 2-93
Open Cursors (per transaction)..................................................................................................... 2-94
Parse Failure Count (per second).................................................................................................. 2-94
Parse Failure Count (per transaction) .......................................................................................... 2-95
Physical Reads (per second) .......................................................................................................... 2-95
Physical Reads (per transaction) ................................................................................................... 2-97
Physical Reads Direct (per second) .............................................................................................. 2-98
Physical Reads Direct (per transaction) ....................................................................................... 2-99
Physical Reads Direct Lobs (per second) ..................................................................................... 2-99
Physical Reads Direct Lobs (per transaction)............................................................................ 2-100
Physical Writes (per second) ....................................................................................................... 2-100
Physical Writes (per transaction) ................................................................................................ 2-101
Physical Writes Direct (per second) ........................................................................................... 2-102
Physical Writes Direct (per transaction) .................................................................................... 2-103
Physical Writes Direct Lobs (per second) .................................................................................. 2-103
Physical Writes Direct Lobs (per transaction)........................................................................... 2-104
Recursive Calls (per second)........................................................................................................ 2-105
Recursive Calls (per transaction) ................................................................................................ 2-106
Redo Generated (per second) ...................................................................................................... 2-107
Redo Generated (per transaction)............................................................................................... 2-108
Redo Writes (per second) ............................................................................................................. 2-109
Redo Writes (per transaction)...................................................................................................... 2-110
Rows Processed (per sort)............................................................................................................ 2-112
Scans on Long Tables (per second)............................................................................................. 2-113
Scans on Long Tables (per transaction) ..................................................................................... 2-114
Session Logical Reads (per second) ............................................................................................ 2-115
Session Logical Reads (per transaction)..................................................................................... 2-116
Soft Parse (%) ................................................................................................................................. 2-117
Sorts to Disk (per second) ............................................................................................................ 2-118
Sorts to Disk (per transaction) ..................................................................................................... 2-119
Total Index Scans (per second).................................................................................................... 2-121
Total Index Scans (per transaction) ............................................................................................ 2-121
Total Parses (per second) ............................................................................................................. 2-122
Total Parses (per transaction) ...................................................................................................... 2-123
Total Table Scan (per second)...................................................................................................... 2-125
Total Table Scan (per transaction) .............................................................................................. 2-125
Total Table Scans (per second) .................................................................................................... 2-126
Total Table Scans (per transaction)............................................................................................. 2-126
User Calls (%) ................................................................................................................................ 2-127
User Calls (per second)................................................................................................................. 2-129
User Calls (per transaction) ......................................................................................................... 2-129
User Commits (per second) ......................................................................................................... 2-130
vii
User Commits (per transaction) .................................................................................................. 2-131
User Rollback Undo Records Applied (per second) ................................................................ 2-132
User Rollback Undo Records Applied (per transaction)......................................................... 2-133
User Rollbacks (per second) ........................................................................................................ 2-133
User Rollbacks (per transaction) ................................................................................................. 2-134
User Audit............................................................................................................................................. 2-135
Audited User.................................................................................................................................. 2-135
Audited User Host ........................................................................................................................ 2-136
Audited User Session Count ....................................................................................................... 2-137
User Block ............................................................................................................................................. 2-137
Blocking Session Count ................................................................................................................ 2-137
User Defined Metrics.......................................................................................................................... 2-138
User Defined Numeric Metric ..................................................................................................... 2-138
User Defined String Metric .......................................................................................................... 2-139
Wait Bottlenecks .................................................................................................................................. 2-139
Active Sessions Using CPU ......................................................................................................... 2-139
Active Sessions Waiting: I/O ...................................................................................................... 2-139
Active Sessions Waiting: Other ................................................................................................... 2-139
Average Instance CPU (%)........................................................................................................... 2-140
buffer busy waits (%).................................................................................................................... 2-140
CPU Time Delta (sec).................................................................................................................... 2-141
db file scattered read (%).............................................................................................................. 2-142
db file sequential read (%) ........................................................................................................... 2-143
db file single write (%).................................................................................................................. 2-144
direct path read (%) ...................................................................................................................... 2-145
direct path read (lob) (%) ............................................................................................................. 2-146
direct path write (%) ..................................................................................................................... 2-147
direct path write (lob) (%) ............................................................................................................ 2-149
enqueue - other (%)....................................................................................................................... 2-150
enqueue: DML - contention (%) .................................................................................................. 2-151
enqueue: HW, Segment High Water Mark - contention (%) .................................................. 2-152
enqueue: ST, Space Transaction - contention (%)..................................................................... 2-153
enqueue: TM, TX, Transaction - row lock contention (%)....................................................... 2-154
enqueue: TX mode 4, Transaction - allocate ITL entry (%) ..................................................... 2-154
enqueue: UL: User-defined - contention (%)............................................................................. 2-155
free buffer waits (%)...................................................................................................................... 2-156
Host CPU Utilization (%)............................................................................................................. 2-157
latch free - other (%)...................................................................................................................... 2-158
latch: cache buffer chains (%) ...................................................................................................... 2-159
latch: library cache (%) ................................................................................................................. 2-160
latch: redo copy (%) ...................................................................................................................... 2-161
latch: shared pool (%) ................................................................................................................... 2-162
library cache load lock (%)........................................................................................................... 2-163
library cache lock (%).................................................................................................................... 2-163
library cache pin (%) ..................................................................................................................... 2-165
local write wait (%) ....................................................................................................................... 2-166
log buffer space (%)....................................................................................................................... 2-167
viii
log file switch (archiving needed) (%) ....................................................................................... 2-168
log file switch (checkpoint complete) (%).................................................................................. 2-169
log file switch completion (%) ..................................................................................................... 2-169
log file sync (%) ............................................................................................................................. 2-170
log switch/archive (%) ................................................................................................................. 2-171
pipe put (%).................................................................................................................................... 2-172
row cache lock (%) ........................................................................................................................ 2-173
SQL*Net break/reset to client (%) .............................................................................................. 2-173
SQL*Net break/reset to dblink (%) ............................................................................................ 2-175
SQL*Net message to client (%).................................................................................................... 2-176
SQL*Net message to dblink (%).................................................................................................. 2-176
SQL*Net more data from client (%)............................................................................................ 2-177
SQL*Net more data from dblink (%).......................................................................................... 2-178
SQL*Net more data to client (%)................................................................................................. 2-179
SQL*Net more data to dblink (%)............................................................................................... 2-180
Wait Time (%) ................................................................................................................................ 2-180
write complete waits (%).............................................................................................................. 2-181
Wait by Session Count........................................................................................................................ 2-182
Session Waiting for Event Count ................................................................................................ 2-182
Waits by Wait Class ............................................................................................................................. 2-183
Average Users Waiting Count .................................................................................................... 2-183
Database Time Spent Waiting (%) .............................................................................................. 2-184
3 Listener
General Status........................................................................................................................................... 3-1
Alias...................................................................................................................................................... 3-1
Security ................................................................................................................................................ 3-1
SID List................................................................................................................................................. 3-2
SNMP Status ....................................................................................................................................... 3-2
Start Date ............................................................................................................................................. 3-3
TNS Address ....................................................................................................................................... 3-3
Trace Level .......................................................................................................................................... 3-3
Version ................................................................................................................................................. 3-4
Load............................................................................................................................................................. 3-4
Connections Established (per min).................................................................................................. 3-4
Connections Refused (per min)........................................................................................................ 3-5
Response .................................................................................................................................................... 3-5
Response Time (msec) ....................................................................................................................... 3-5
Status.................................................................................................................................................... 3-6
Part II Host Metrics
4 Host
Aggregate Resource Usage Statistics (By Project).............................................................................. 4-1
Cumulative CPU Wait Time(Seconds)............................................................................................ 4-1
Cumulative Data Page Fault Sleep Time(Seconds) ....................................................................... 4-1
ix
Cumulative Major Page Faults......................................................................................................... 4-2
Cumulative Minor Page Faults ........................................................................................................ 4-2
Cumulative Number Character IO (bytes) Read and Written .................................................... 4-3
Cumulative Number Of Blocks Read.............................................................................................. 4-3
Cumulative Number Of Blocks Written ......................................................................................... 4-3
Cumulative Number of Involuntary Context Switches ............................................................... 4-4
Cumulative Number Of Messages Received ................................................................................. 4-4
Cumulative Number Of Messages Sent.......................................................................................... 4-4
Cumulative Number of Signals Received ...................................................................................... 4-5
Cumulative Number of System Calls Made .................................................................................. 4-5
Cumulative Number of Voluntary Context Switches................................................................... 4-6
Cumulative Project Lock-Wait Sleep Time(Seconds) ................................................................... 4-6
Cumulative Project Other Sleep Time(Seconds)............................................................................ 4-6
Cumulative Stop Time(Seconds)...................................................................................................... 4-7
Cumulative Swap Operations .......................................................................................................... 4-7
Cumulative System Mode Time (seconds)..................................................................................... 4-7
Cumulative System Page Fault Sleep Time(Seconds)................................................................... 4-8
Cumulative System Trap Time (seconds)....................................................................................... 4-8
Cumulative Text Page Fault Sleep Time(Seconds)........................................................................ 4-9
Cumulative User Mode Time (seconds) ......................................................................................... 4-9
Number of Processes Owned by Project......................................................................................... 4-9
Project CPU Time (%) ..................................................................................................................... 4-10
Project Process Memory Size (%) .................................................................................................. 4-10
Project's Total Process Heap Size(KiloBytes) .............................................................................. 4-10
Project's Total Process Resident Set Size(KiloBytes) .................................................................. 4-11
Project's Total Process Virtual Memory Size(KiloBytes) ........................................................... 4-11
Status................................................................................................................................................. 4-12
Total Number of Threads in Project's Processes......................................................................... 4-12
Aggregate Resource Usage Statistics(By User) ................................................................................ 4-12
Cumulative CPU Wait Time(Seconds)......................................................................................... 4-12
Cumulative Data Page Fault Sleep Time(Seconds) .................................................................... 4-13
Cumulative Major Page Faults...................................................................................................... 4-13
Cumulative Minor Page Faults ..................................................................................................... 4-13
Cumulative Number Character IO (bytes) Read and Written ................................................. 4-14
Cumulative Number Of Blocks Read........................................................................................... 4-14
Cumulative Number Of Blocks Written ...................................................................................... 4-14
Cumulative Number of Involuntary Context Switches ............................................................ 4-15
Cumulative Number Of Messages Received .............................................................................. 4-15
Cumulative Number Of Messages Sent....................................................................................... 4-16
Cumulative Number of Signals Received ................................................................................... 4-16
Cumulative Number of System Calls Made ............................................................................... 4-16
Cumulative Number of Voluntary Context Switches................................................................ 4-17
Cumulative Stop Time(Seconds)................................................................................................... 4-17
Cumulative Swap Operations ....................................................................................................... 4-17
Cumulative System Mode Time (seconds).................................................................................. 4-18
Cumulative System Page Fault Sleep Time(Seconds)................................................................ 4-18
Cumulative System Trap Time (seconds).................................................................................... 4-19
x
Cumulative Text Page Fault Sleep Time(Seconds)..................................................................... 4-19
Cumulative User Lock-Wait Sleep Time(Seconds) .................................................................... 4-19
Cumulative User Mode Time (seconds) ...................................................................................... 4-20
Cumulative User Other Sleep Time(Seconds) ............................................................................ 4-20
Number of Processes Owned by User ......................................................................................... 4-20
Total Number of Threads in User's Processes ............................................................................ 4-21
User CPU Time (%) ......................................................................................................................... 4-21
User Process Memory Size (%)...................................................................................................... 4-22
User's Total Process Heap Size(KiloBytes) .................................................................................. 4-22
User's Total Process Resident Set Size(KiloBytes)...................................................................... 4-22
User's Total Process Virtual Memory Size(KiloBytes) ............................................................... 4-23
Buffer Activity........................................................................................................................................ 4-23
Buffer Cache Read Hit Ratio (%)................................................................................................... 4-23
Buffer Cache Reads (per second) .................................................................................................. 4-24
Buffer Cache Write Hit Ratio (%).................................................................................................. 4-24
Buffer Cache Writes (per second) ................................................................................................. 4-25
Physical I/O Reads (per second) ................................................................................................. 4-25
Physical I/O Writes (per second) ................................................................................................. 4-25
Physical Reads (per second) .......................................................................................................... 4-26
Physical Writes (per second) ......................................................................................................... 4-26
CPU Usage .............................................................................................................................................. 4-27
CPU Idle Time (%) .......................................................................................................................... 4-27
CPU Interrupt Time (%) ................................................................................................................. 4-28
CPU System Time (%) .................................................................................................................... 4-28
CPU User Time (%) ......................................................................................................................... 4-29
CPU Wait Time (%)......................................................................................................................... 4-29
Disk Activity .......................................................................................................................................... 4-30
Average Disk I/O Service Time (ms) ........................................................................................... 4-30
Average Disk I/O Wait Time (ms) ............................................................................................... 4-31
Average Outstanding Disk I/O Requests ................................................................................... 4-32
Average Run Time (ms) ................................................................................................................. 4-33
Disk Block Writes (per second) ..................................................................................................... 4-33
Disk Blocks Reads (per second) .................................................................................................... 4-34
Disk Reads (per second)................................................................................................................. 4-34
Disk Utilization (%)......................................................................................................................... 4-35
Disk Writes (per second) ................................................................................................................ 4-36
Disk Device Errors ................................................................................................................................ 4-36
Hard Errors ...................................................................................................................................... 4-37
Soft Errors......................................................................................................................................... 4-37
Total................................................................................................................................................... 4-37
Transport Errors .............................................................................................................................. 4-38
File Access System Calls ...................................................................................................................... 4-38
Blocks Read by Directory Search Routine (per second) ............................................................ 4-38
iget() Calls (per second).................................................................................................................. 4-39
lookuppn() Calls (per second) ....................................................................................................... 4-39
Filesystems.............................................................................................................................................. 4-40
Filesystem......................................................................................................................................... 4-40
xi
Filesystem Size (MB)....................................................................................................................... 4-40
Filesystem Space Available (%)..................................................................................................... 4-41
Filesystem Utilization (MB) ........................................................................................................... 4-42
Inventory................................................................................................................................................. 4-42
Kernel Memory...................................................................................................................................... 4-42
Failed Requests for Large Kernel Memory.................................................................................. 4-42
Failed Requests for Oversize Kernal Memory ............................................................................ 4-43
Failed Requests for Small Kernel Memory ................................................................................. 4-43
KMA Available for Large Memory Requests (Bytes) ................................................................ 4-43
KMA for Oversize Memory Requests (Bytes)............................................................................. 4-43
KMA for Small Memory Requests ............................................................................................... 4-44
Memory Allocated for Large Memory Requests (Bytes)........................................................... 4-44
Memory Allocated for Small Memory Requests (Bytes) ........................................................... 4-44
Load.......................................................................................................................................................... 4-45
CPU in IO-Wait (%)......................................................................................................................... 4-45
CPU in System Mode (%)............................................................................................................... 4-46
CPU in User Mode (%) ................................................................................................................... 4-46
CPU Interrupt Time (%) ................................................................................................................. 4-47
CPU Queue Length ........................................................................................................................ 4-48
CPU Utilization (%) ........................................................................................................................ 4-48
Free Memory (%)............................................................................................................................. 4-49
Longest Service Time (ms) ............................................................................................................. 4-50
Memory Page Scan Rate (per second) .......................................................................................... 4-50
Memory Utilization (%).................................................................................................................. 4-51
Page Transfers Rate......................................................................................................................... 4-52
Run Queue Length (1 minute average)........................................................................................ 4-52
Run Queue Length (15 minute average)...................................................................................... 4-53
Run Queue Length (5 minute average)........................................................................................ 4-54
Swap Utilization (%) ....................................................................................................................... 4-54
Total I/O (per second).................................................................................................................... 4-55
Total Processes................................................................................................................................. 4-56
Total Swap, Kilobytes ..................................................................................................................... 4-56
Total Users........................................................................................................................................ 4-57
Used Swap, Kilobytes ..................................................................................................................... 4-57
Message and Semaphore Activity ...................................................................................................... 4-58
msgrcv() System Calls (per second) ............................................................................................. 4-58
semop() System Calls (per second)............................................................................................... 4-58
Network Interfaces................................................................................................................................ 4-59
Network Interface Input Errors (%) ........................................................................................... 4-59
Network Interface Collisions (%).................................................................................................. 4-60
Network Interface Combined Utilization (%)............................................................................. 4-60
Network Interface Output Errors (%) .......................................................................................... 4-61
Network Interface Read (MB/s) ................................................................................................... 4-62
Network Interface Read Utilization (%) ...................................................................................... 4-62
Network Interface Write (MB/s) .................................................................................................. 4-63
Network Interface Write Utilization (%) ..................................................................................... 4-63
Paging Activity....................................................................................................................................... 4-64
xii
Address Translation Page Faults (per second) ........................................................................... 4-64
Cache Faults (per second) .............................................................................................................. 4-65
Copy-on-write Faults (per second)............................................................................................... 4-65
Demand Zero Faults (per second) ................................................................................................ 4-66
igets with Page Flushes(%) ............................................................................................................ 4-66
Page Faults (per second) ................................................................................................................ 4-67
Page Faults from Software Lock Requests .................................................................................. 4-67
Page-in Requests (per second)....................................................................................................... 4-68
Page-out Requests (per second) .................................................................................................... 4-69
Pages Paged-in (per second).......................................................................................................... 4-69
Pages Paged-out (per second) ....................................................................................................... 4-70
Pages Put on Freelist by Page Stealing Daemon (per second).................................................. 4-71
Pages Scanned by Page Stealing Daemon (per second) ............................................................ 4-71
Transition Faults (per second)....................................................................................................... 4-72
Process, Inode, File Tables Statistics.................................................................................................. 4-72
File Table Overflow Occurrences ................................................................................................. 4-73
Inode Table Overflow Occurrences .............................................................................................. 4-73
Maximum Size of Inode Table....................................................................................................... 4-74
Maximum Size of Process Table ................................................................................................... 4-74
Maximum Size of System File Table............................................................................................. 4-75
Process Table Overflow Occurrences........................................................................................... 4-75
Size of Inode Table .......................................................................................................................... 4-76
Size of Process Table ....................................................................................................................... 4-76
Size of System File Table ................................................................................................................ 4-76
Response ................................................................................................................................................. 4-77
Status................................................................................................................................................. 4-77
Swap Area Status................................................................................................................................... 4-77
Swap Free ......................................................................................................................................... 4-77
Swap Size.......................................................................................................................................... 4-78
Switch/Swap Activity ........................................................................................................................... 4-79
Process Context Switches (per second) ........................................................................................ 4-79
Swapins Transfers (per second) .................................................................................................... 4-79
Swapout Transfers (per second) ................................................................................................... 4-80
System Swapins (per second) ........................................................................................................ 4-80
System Swapouts (per second)...................................................................................................... 4-81
System Calls ........................................................................................................................................... 4-81
Characters Transferred by Read System Calls (per second)..................................................... 4-82
Characters Transferred by Write System Calls (per second) .................................................... 4-82
exec() System Calls (per second)................................................................................................... 4-83
fork() System Calls (per second) ................................................................................................... 4-83
read() System Calls (per second)................................................................................................... 4-84
System Calls (per second) .............................................................................................................. 4-84
write() System Calls (per second) ................................................................................................. 4-85
Top Processes.......................................................................................................................................... 4-85
Command and Arguments ............................................................................................................ 4-86
CPU Time for Top Processes ......................................................................................................... 4-86
CPU Utilization for Top Processes (%) ........................................................................................ 4-86
xiii
Memory Utilization for Top Processes (%).................................................................................. 4-87
Physical Memory Utilization (KB)................................................................................................ 4-87
Process User ID................................................................................................................................ 4-88
Virtual Memory Utilization (KB) .................................................................................................. 4-88
TTY Activity ........................................................................................................................................... 4-88
Incoming Character Interrupts (per second)............................................................................... 4-89
Input Characters Processed by canon()........................................................................................ 4-89
Modem Interrupt Rate (per second)............................................................................................. 4-89
Outgoing Character Interrupts (per second)............................................................................... 4-90
TTY Output Characters (per second) ........................................................................................... 4-90
TTY Raw Input (chars/s) ............................................................................................................... 4-91
User Defined Metrics............................................................................................................................ 4-91
User Defined Numeric Metric ....................................................................................................... 4-92
User Defined String Metric ............................................................................................................ 4-92
Users......................................................................................................................................................... 4-92
Number of Logons ......................................................................................................................... 4-92
Part III Oracle Application Server Metrics
5 Application Server
Application Response.............................................................................................................................. 5-1
Application URL Response Time (seconds)................................................................................... 5-1
Application URL Status..................................................................................................................... 5-2
OPMN Process Information Metrics .................................................................................................... 5-2
Component CPU Usage (%) ............................................................................................................. 5-3
Component Memory Usage (%) ...................................................................................................... 5-3
Component Memory Usage (MB).................................................................................................... 5-4
Component Start Time (ms since epoch) ........................................................................................ 5-5
Component Up Time (ms) ................................................................................................................ 5-5
Component Up/down Status........................................................................................................... 5-5
Free Memory (%)................................................................................................................................ 5-6
Free Memory (MB) ............................................................................................................................. 5-6
Idle CPU Time (%) ............................................................................................................................. 5-7
Total Memory (MB) ........................................................................................................................... 5-7
Resource Usage ......................................................................................................................................... 5-7
CPU Idle Time (%) ............................................................................................................................. 5-8
CPU Usage (%) ................................................................................................................................... 5-8
Free Memory (%)................................................................................................................................ 5-9
Free Memory (MB) ............................................................................................................................. 5-9
Memory Usage (%) ............................................................................................................................ 5-9
Memory Usage (MB)....................................................................................................................... 5-10
Other CPU Usage (%) ..................................................................................................................... 5-10
Other Memory Usage (%) .............................................................................................................. 5-11
Other Memory Usage (MB) ........................................................................................................... 5-11
Total Memory (MB) ........................................................................................................................ 5-12
Response ................................................................................................................................................. 5-12
UpDown Status ............................................................................................................................... 5-12
xiv
6 Discoverer
Discoverer Components.......................................................................................................................... 6-1
CPU Usage (%) ................................................................................................................................... 6-1
Memory Usage (MB).......................................................................................................................... 6-1
Number of Sessions ........................................................................................................................... 6-2
Discoverer Plus Sessions ........................................................................................................................ 6-2
Component Type................................................................................................................................ 6-2
CPU Usage (%) ................................................................................................................................... 6-2
DBUser@DB - EUL ............................................................................................................................. 6-3
Memory Usage (MB).......................................................................................................................... 6-3
OS Process ID...................................................................................................................................... 6-3
SSO User .............................................................................................................................................. 6-3
Discoverer Portlet Provider Sessions ................................................................................................... 6-3
Component Type................................................................................................................................ 6-3
CPU Usage (%) ................................................................................................................................... 6-3
DBUser@DB - EUL ............................................................................................................................. 6-4
Memory Usage (MB).......................................................................................................................... 6-4
OS Process ID...................................................................................................................................... 6-4
SSO User .............................................................................................................................................. 6-4
Discoverer Sessions ................................................................................................................................. 6-4
Component Type................................................................................................................................ 6-4
CPU Usage (%) ................................................................................................................................... 6-5
DBUser@DB - EUL ............................................................................................................................. 6-5
Memory Usage (MB).......................................................................................................................... 6-5
OS Process ID...................................................................................................................................... 6-5
Private Memory Usage (MB) ............................................................................................................ 6-5
Shared Memory Usage (MB) ............................................................................................................ 6-5
SSO User .............................................................................................................................................. 6-5
Discoverer Viewer Sessions ................................................................................................................... 6-6
Component Type................................................................................................................................ 6-6
CPU Usage (%) ................................................................................................................................... 6-6
DBUser@DB - EUL ............................................................................................................................. 6-6
Memory Usage (MB).......................................................................................................................... 6-6
OS Process ID...................................................................................................................................... 6-6
SSO User .............................................................................................................................................. 6-6
Response .................................................................................................................................................... 6-7
UpDown Status .................................................................................................................................. 6-7
Total Discoverer CPU Usage .................................................................................................................. 6-7
Total Discoverer CPU Usage (%) ..................................................................................................... 6-7
Total Discoverer Memory Usage ........................................................................................................... 6-8
Total Discoverer Memory Usage (MB) ........................................................................................... 6-8
Total Number Of Discoverer Plus Sessions ........................................................................................ 6-8
Total Number Of Discoverer Plus Sessions ................................................................................... 6-9
Total Number Of Discoverer Portlet Provider Sessions ................................................................... 6-9
Total Number Of Discoverer Portlet Provider Sessions............................................................... 6-9
Total Number Of Discoverer Sessions ................................................................................................. 6-9
Total Number Of Discoverer Sessions ............................................................................................ 6-9
xv
Total Number Of Discoverer Viewer Sessions................................................................................ 6-10
Total Number Of Discoverer Viewer Sessions ........................................................................... 6-10
7 Forms
Load............................................................................................................................................................. 7-1
Total CPU (%) ..................................................................................................................................... 7-1
Total Memory (%) .............................................................................................................................. 7-1
Total number of users........................................................................................................................ 7-2
Response .................................................................................................................................................... 7-2
ResponseTime(ms) ............................................................................................................................. 7-3
Status.................................................................................................................................................... 7-3
8 HTTP Server
Host Metrics .............................................................................................................................................. 8-1
Name.................................................................................................................................................... 8-1
modplsql_Cache Metrics ........................................................................................................................ 8-1
cacheStatus.value ............................................................................................................................... 8-1
hits.count, ops ..................................................................................................................................... 8-2
hits.percentage.................................................................................................................................... 8-2
modplsql.............................................................................................................................................. 8-2
Name.................................................................................................................................................... 8-2
newMisses.count, ops........................................................................................................................ 8-3
newMisses.percentage....................................................................................................................... 8-3
requests.count ..................................................................................................................................... 8-3
staleMisses.count, ops ....................................................................................................................... 8-4
staleMisses.percentage ...................................................................................................................... 8-4
modplsql_HTTPResponseCodes Metrics............................................................................................ 8-4
HTTP 200s ........................................................................................................................................... 8-4
HTTP 200s percentage ....................................................................................................................... 8-5
HTTP 300s Resolved .......................................................................................................................... 8-5
HTTP 300s resolved percentage....................................................................................................... 8-5
HTTP 400s ........................................................................................................................................... 8-6
HTTP 500s ........................................................................................................................................... 8-7
Total HTTP responses........................................................................................................................ 8-8
modplsql_RequestGroupingSQLErrorList Metrics .......................................................................... 8-8
errorCount.count................................................................................................................................ 8-8
lastErrorDate.value ............................................................................................................................ 8-8
lastErrorRequest.value ...................................................................................................................... 8-9
lastErrorText.value............................................................................................................................. 8-9
Name.................................................................................................................................................... 8-9
modplsql_RequestLast10SQLErrorList Metrics.............................................................................. 8-10
errorDate.value................................................................................................................................ 8-10
errorRequest.value .......................................................................................................................... 8-10
errorText.value ................................................................................................................................ 8-10
Name................................................................................................................................................. 8-11
xvi
OHS General Metrics ........................................................................................................................... 8-11
Start Time (ms since Epoch) .......................................................................................................... 8-11
OHS Module Metrics............................................................................................................................ 8-11
Active Requests for a Module ....................................................................................................... 8-11
Request Handling Throughput, for a Module (requests per second) ..................................... 8-12
Request Handling Time, for a Module (seconds)....................................................................... 8-12
OHS Process Metrics ............................................................................................................................ 8-12
Heap Usage (MB) ............................................................................................................................ 8-13
OHS Server Metrics .............................................................................................................................. 8-13
Active HTTP Connections ............................................................................................................. 8-13
Active HTTP Requests.................................................................................................................... 8-13
Busy Processes ................................................................................................................................. 8-14
Connection Duration (seconds)..................................................................................................... 8-14
Error Rate (%) .................................................................................................................................. 8-15
Idle Processes ................................................................................................................................... 8-15
Percentage of Busy Processes ........................................................................................................ 8-15
Request Processing Time (seconds).............................................................................................. 8-16
Request Throughput (requests per second) ................................................................................ 8-17
Response Data Processed (KB per response) .............................................................................. 8-17
Response Data Throughput (KB per second).............................................................................. 8-18
OHS Virtual Host Metrics ................................................................................................................... 8-18
Active Requests for a Virtual Host ............................................................................................... 8-18
Request Processing Time for a Virtual Host (seconds).............................................................. 8-19
Request Throughput for a Virtual Host (requests per second) ................................................ 8-19
Response Data Processed for a Virtual Host (KB per response) .............................................. 8-20
Response Data Throughput for a Virtual Host (KB per second) ............................................. 8-20
Virtual Host Type............................................................................................................................ 8-21
Process Metrics....................................................................................................................................... 8-21
Host ................................................................................................................................................... 8-21
Name................................................................................................................................................. 8-21
Resource Usage ...................................................................................................................................... 8-21
CPU Idle Time (%) .......................................................................................................................... 8-21
CPU Usage (%) ................................................................................................................................ 8-22
Free Memory (%)............................................................................................................................. 8-22
Free Memory (MB) .......................................................................................................................... 8-23
Memory Usage (%) ......................................................................................................................... 8-23
Memory Usage (MB)....................................................................................................................... 8-23
Other CPU Usage (%) ..................................................................................................................... 8-24
Other Memory Usage (%) .............................................................................................................. 8-24
Other Memory Usage (MB) ........................................................................................................... 8-24
Total Memory (MB) ........................................................................................................................ 8-25
Response ................................................................................................................................................. 8-25
UpDown Status ............................................................................................................................... 8-25
9 Internet File System

Application URL Timing ........................................................................................................................ 9-1
Application URL Response Time (seconds)................................................................................... 9-1
xvii
Application URL Status..................................................................................................................... 9-2
Document Statistics ................................................................................................................................. 9-2
Average Document Size (bytes) ....................................................................................................... 9-2
Total Number of Documents............................................................................................................ 9-3
Total Size of Documents (bytes)....................................................................................................... 9-3
Documents By MIME Type .................................................................................................................... 9-3
Documents .......................................................................................................................................... 9-3
Size of Documents (bytes)................................................................................................................. 9-4
Domain Response .................................................................................................................................... 9-4
Domain Controller Status ................................................................................................................. 9-4
Node Status ......................................................................................................................................... 9-4
Node Status Message......................................................................................................................... 9-5
Status.................................................................................................................................................... 9-5
Load Balanced Application URL Timing............................................................................................. 9-6
Load Balanced Application URL Response Time (seconds)........................................................ 9-6
Load Balanced Application URL Status ......................................................................................... 9-6
Node Statistics .......................................................................................................................................... 9-7
Host Name and IP.............................................................................................................................. 9-7
JVM Free Memory (%)....................................................................................................................... 9-7
JVM Free Memory (MB) .................................................................................................................... 9-8
JVM Threads ....................................................................................................................................... 9-8
JVM Total Memory (MB) .................................................................................................................. 9-9
JVM Used Memory (MB) .................................................................................................................. 9-9
Sessions ................................................................................................................................................ 9-9
Resource Usage ...................................................................................................................................... 9-10
CPU Idle (%) .................................................................................................................................... 9-10
CPU Other (%) ................................................................................................................................. 9-10
CPU Usage (%) ................................................................................................................................ 9-10
Memory Usage (%) ......................................................................................................................... 9-11
Memory Usage (MB)....................................................................................................................... 9-12
Total Memory (MB) ........................................................................................................................ 9-12
Response ................................................................................................................................................. 9-12
Status................................................................................................................................................. 9-12
Sessions By Server (Domain) .............................................................................................................. 9-13
Sessions By Server........................................................................................................................... 9-13
Sessions By Server (Node)................................................................................................................... 9-13
Host Name and IP........................................................................................................................... 9-14
Sessions By Server........................................................................................................................... 9-14
Users......................................................................................................................................................... 9-14
All Users ........................................................................................................................................... 9-15
Average Consumed Quota By All Users (bytes) ........................................................................ 9-15
Average Consumed Quota By Limited Users (bytes)................................................................ 9-15
Average Consumed Quota By Unlimited Users (bytes) ........................................................... 9-15
Consumed Quota By All Users (bytes) ........................................................................................ 9-16
Consumed Quota By Limited Users (bytes)................................................................................ 9-16
Consumed Quota By Unlimited Users (bytes) ........................................................................... 9-16
Users With Limited Quota............................................................................................................. 9-17
xviii
Users With Unlimited Quota......................................................................................................... 9-17
Users (With Limited Quota) ................................................................................................................ 9-17
Average Allocated Quota (bytes).................................................................................................. 9-18
Average Consumed Quota (bytes) ............................................................................................... 9-18
Consumed (%) ................................................................................................................................. 9-18
Total Allocated Quota (bytes) ....................................................................................................... 9-18
Total Consumed Quota (bytes) ..................................................................................................... 9-19
Users (With Limited Quota) .......................................................................................................... 9-19
10 JServ
Response ................................................................................................................................................. 10-1
Status................................................................................................................................................. 10-1
11 OC4J
Application Metrics for OC4J Instances ........................................................................................... 11-1
Application - Delta EJB Method Execution Time (seconds) ..................................................... 11-1
Application - Delta EJB Method Invocations .............................................................................. 11-1
Application - Delta Request Processing Time (seconds) ........................................................... 11-2
Application - Delta Requests Completed .................................................................................... 11-2
Application - Delta Servlet, JSP and EJB Time (seconds) .......................................................... 11-2
Application - Requests Completed since Startup....................................................................... 11-2
Application - Total EJB Method Execution Time (seconds)...................................................... 11-3
Application - Total EJB Method Invocations .............................................................................. 11-3
Application - Total Request Processing Time (seconds) ........................................................... 11-3
Application - Total Servlet, JSP and EJB Time (seconds) .......................................................... 11-4
OC4J All Instances Metrics ................................................................................................................. 11-4
OC4J Instances - Active Sessions .................................................................................................. 11-4
OC4J Instances - Request Processing Time (seconds)................................................................ 11-4
OC4J Instances - Requests Per Second ......................................................................................... 11-5
OC4J Application Metrics.................................................................................................................... 11-5
Application - Active EJB Methods ................................................................................................ 11-5
Application - Active Requests ....................................................................................................... 11-6
Application - Active Sessions ........................................................................................................ 11-6
Application - EJB Method Execution Rate (per second)............................................................ 11-7
Application - EJB Method Execution Time (seconds)................................................................ 11-7
Application - Request Processing Time (seconds) ..................................................................... 11-8
Application - Requests Per Second............................................................................................... 11-8
OC4J EJB Metrics................................................................................................................................... 11-9
EJB - Active Methods ...................................................................................................................... 11-9
EJB - Method Execution Rate (per second)................................................................................ 11-10
EJB - Method Execution Time (seconds).................................................................................... 11-10
Type of EJB ..................................................................................................................................... 11-11
OC4J EJB Module Metrics ................................................................................................................. 11-11
EJB Module - Active Methods ..................................................................................................... 11-11
EJB Module - Method Execution Rate (per second)................................................................. 11-12
EJB Module - Method Execution Time (seconds) ..................................................................... 11-12
xix
OC4J Instance Metrics ........................................................................................................................ 11-13
OC4J Instance - Active EJB Methods .......................................................................................... 11-13
OC4J Instance - Active Requests ................................................................................................. 11-13
OC4J Instance - Active Sessions .................................................................................................. 11-14
OC4J Instance - Active Transactions .......................................................................................... 11-14
OC4J Instance - EJB Method Execution Rate (per second)...................................................... 11-14
OC4J Instance - EJB Method Execution Time (seconds).......................................................... 11-15
OC4J Instance - Heap Usage (MB).............................................................................................. 11-15
OC4J Instance - Open JDBC Connections.................................................................................. 11-16
OC4J Instance - Request Processing Time (seconds) ............................................................... 11-16
OC4J Instance - Requests Per Second......................................................................................... 11-17
OC4J Instance - Start Time (ms since Epoch) ............................................................................ 11-17
OC4J JSP Metrics................................................................................................................................. 11-17
Is multi-threaded? ......................................................................................................................... 11-17
JSP - Active Instances (STM only)............................................................................................... 11-18
JSP - Active Requests .................................................................................................................... 11-18
JSP - Available Instances (STM only) ......................................................................................... 11-19
JSP - Client Processing Time (seconds) ...................................................................................... 11-19
JSP - Requests Per Second ............................................................................................................ 11-20
OC4J Servlet Metrics .......................................................................................................................... 11-20
Servlet - Active Requests.............................................................................................................. 11-20
Servlet - Client Processing Time (seconds)................................................................................ 11-21
Servlet - Requests Per Second...................................................................................................... 11-22
OC4J Web Module Metrics................................................................................................................ 11-22
Web Module - Active Requests ................................................................................................... 11-22
Web Module - Active Sessions .................................................................................................... 11-23
Web Module - Class Load Time (seconds) ................................................................................ 11-23
Web Module - Client Time (seconds)......................................................................................... 11-24
Web Module - Request Processing Time (seconds) ................................................................. 11-24
Web Module - Requests Per Second........................................................................................... 11-25
Resource Usage .................................................................................................................................... 11-25
CPU Idle Time (%) ........................................................................................................................ 11-25
CPU Usage (%) .............................................................................................................................. 11-25
Free Memory (%)........................................................................................................................... 11-26
Free Memory (MB) ........................................................................................................................ 11-26
Memory Usage (%) ....................................................................................................................... 11-26
Memory Usage (MB)..................................................................................................................... 11-27
Other CPU Usage (%) ................................................................................................................... 11-27
Other Memory Usage (%) ............................................................................................................ 11-28
Other Memory Usage (MB) ......................................................................................................... 11-28
Total Memory (MB) ...................................................................................................................... 11-28
Response ............................................................................................................................................... 11-29
UpDown Status ............................................................................................................................. 11-29
12 OID LDAP Server

(Critical Events)Security Events ......................................................................................................... 12-1
Event Name...................................................................................................................................... 12-1
xx
Event Result ..................................................................................................................................... 12-1
Event Time ....................................................................................................................................... 12-1
Instance Number ............................................................................................................................. 12-1
Process ID ......................................................................................................................................... 12-2
Sample ID ......................................................................................................................................... 12-2
User DN ............................................................................................................................................ 12-2
(Critical Events)System Resource Events ......................................................................................... 12-2
Event Name...................................................................................................................................... 12-2
Instance Number ............................................................................................................................. 12-2
Last Event Time ............................................................................................................................... 12-2
Number of Event Occurence ......................................................................................................... 12-2
Process ID ......................................................................................................................................... 12-3
Sample ID ......................................................................................................................................... 12-3
(Resource Statistics)LDAP Server and System Memory ............................................................... 12-3
Date and Time Stamp ..................................................................................................................... 12-3
Instance Number ............................................................................................................................. 12-3
LDAP Server's average memory growth (%).............................................................................. 12-3
Sample ID ......................................................................................................................................... 12-3
System's Total Free Physical Memory (KB)................................................................................. 12-4
(Resource Statistics)LDAP Server's Data Base Usage .................................................................... 12-4
Active Data Base Sessions .............................................................................................................. 12-4
Instance Number ............................................................................................................................. 12-4
Open Data Base Sessions................................................................................................................ 12-4
Sample ID ......................................................................................................................................... 12-4
Configuration sets of LDAP Server ................................................................................................... 12-5
Configuration set number.............................................................................................................. 12-5
Max concurrent DB conn ............................................................................................................... 12-5
Non SSL port number..................................................................................................................... 12-5
Number of server process .............................................................................................................. 12-5
SSL authentication type.................................................................................................................. 12-5
SSL enabled ...................................................................................................................................... 12-5
SSL port number.............................................................................................................................. 12-6
SSL Version ...................................................................................................................................... 12-6
SSL wallet URL ................................................................................................................................ 12-6
Directory Integration Profiles............................................................................................................. 12-6
Execution Errors .............................................................................................................................. 12-6
Execution Status .............................................................................................................................. 12-6
Last Applied Change Number ...................................................................................................... 12-6
Last Execution Time........................................................................................................................ 12-6
Operation.......................................................................................................................................... 12-6
Schedule (secs)................................................................................................................................. 12-7
State ................................................................................................................................................... 12-7
Type................................................................................................................................................... 12-7
Directory Integration Server ............................................................................................................... 12-7
Directory Integration Server Host ................................................................................................ 12-7
Downtime Count............................................................................................................................. 12-7
xxi
Instance ............................................................................................................................................. 12-7
LDAP Server .................................................................................................................................... 12-7
Start Time ......................................................................................................................................... 12-7
LDAP All Instance IDs......................................................................................................................... 12-7
Instance Number ............................................................................................................................. 12-7
LDAP Entry Cache Hit Ratio............................................................................................................... 12-7
Instance Number ............................................................................................................................. 12-8
Process ID ......................................................................................................................................... 12-8
Sample ID ......................................................................................................................................... 12-8
Server Entry Cache Hit Ratio ........................................................................................................ 12-8
LDAP Load and Response ................................................................................................................... 12-8
Instance Number ............................................................................................................................. 12-8
Sample ID ......................................................................................................................................... 12-9
Server Average Response Time (in Milliseconds)...................................................................... 12-9
Server Load ...................................................................................................................................... 12-9
LDAP Logon Session Statistics........................................................................................................... 12-9
Instance Number ............................................................................................................................. 12-9
Sample ID ......................................................................................................................................... 12-9
Total LDAP Logon Sessions ........................................................................................................ 12-10
LDAP Operations profile................................................................................................................... 12-10
Completed Add Operations ........................................................................................................ 12-10
Completed Compare Operations................................................................................................ 12-10
Completed Delete Operations ..................................................................................................... 12-10
Completed Login Operations ...................................................................................................... 12-10
Completed Modify Operations ................................................................................................... 12-10
Completed Search Operations..................................................................................................... 12-11
Date and Time Stamp ................................................................................................................... 12-11
Instance Number ........................................................................................................................... 12-11
Sample ID ....................................................................................................................................... 12-11
LDAP Server Response ...................................................................................................................... 12-11
Status............................................................................................................................................... 12-11
Total Number................................................................................................................................. 12-11
LDAP Server Total Memory Usage .................................................................................................. 12-11
Total Size (in KB)........................................................................................................................... 12-12
LDAP Server Total User Sessions .................................................................................................... 12-12
Total Users Sessions...................................................................................................................... 12-12
Running instances of LDAP Replication Server........................................................................... 12-12
Config Set ....................................................................................................................................... 12-12
Downtime Count........................................................................................................................... 12-12
Instance ........................................................................................................................................... 12-12
Oracle Directory Server ................................................................................................................ 12-12
Start Time ....................................................................................................................................... 12-13
Running instances of LDAP Server ................................................................................................. 12-13
Config Set Number ....................................................................................................................... 12-13
xxii
Downtime Count........................................................................................................................... 12-13
Host Name ..................................................................................................................................... 12-13
Instance Number ........................................................................................................................... 12-13
Port Number .................................................................................................................................. 12-13
Up Since.......................................................................................................................................... 12-13
Stopped instances of LDAP Server.................................................................................................. 12-14
Config Set Number ....................................................................................................................... 12-14
Host Name ..................................................................................................................................... 12-14
Instance Number ........................................................................................................................... 12-14
13 Portal
Database Instance.................................................................................................................................. 13-1
Instance Name ................................................................................................................................. 13-1
Start Time ......................................................................................................................................... 13-1
Version .............................................................................................................................................. 13-2
Database Portlet Metrics ...................................................................................................................... 13-2
Cache Hits ........................................................................................................................................ 13-2
Count of HTTP 200 Response codes............................................................................................. 13-2
Count of requests which timed out .............................................................................................. 13-4
Count of Resolved HTTP 300 Response codes ........................................................................... 13-4
Count of Unresolved HTTP 300 Response codes ....................................................................... 13-4
Database Portlet Average Time (msec) ........................................................................................ 13-5
Database Portlet Maximium Time (msec) ................................................................................... 13-5
Database Portlet Minimum Time (msec) ..................................................................................... 13-5
Last Response Code ........................................................................................................................ 13-6
Requests............................................................................................................................................ 13-6
Database Providers Metrics................................................................................................................. 13-7
Cache Hits ........................................................................................................................................ 13-7
Count of requests which timed out .............................................................................................. 13-8
Count of Resolved HTTP 300 Response codes ........................................................................... 13-8
Count of Unresolved HTTP 300 Response codes ....................................................................... 13-9
Database Provider Portlets Average Time (msec)...................................................................... 13-9
Database Provider Portlets Maximium Time (msec) ............................................................... 13-10
Database Provider Portlets Minimum Time (msec)................................................................. 13-11
Database Provider Status ............................................................................................................. 13-11
Offline ............................................................................................................................................. 13-12
Percentage of Database Provider HTTP 500 Response codes................................................. 13-12
Requests.......................................................................................................................................... 13-13
General Page Engine Metrics............................................................................................................ 13-13
Average Queue Length ................................................................................................................ 13-14
Average Time in Page Engine Queue (msec)............................................................................ 13-14
Cache Hits ...................................................................................................................................... 13-14
xxiii
Percentage of Requests that were serviced by the cache......................................................... 13-15
Percentage of Requests Timing Out in the Page Engine Queue ............................................ 13-15
Requests for cache enabled pages............................................................................................... 13-16
Requests to the Cache ................................................................................................................... 13-16
Total Page Requests ...................................................................................................................... 13-16
Page Engine Response Code Metrics .............................................................................................. 13-17
Percentage of http 200 responses ................................................................................................ 13-17
Percentage of http 300 Resolved responses............................................................................... 13-17
Percentage of http 300 Unresolved responses .......................................................................... 13-18
Timeouts ......................................................................................................................................... 13-19
Total http 200 responses............................................................................................................... 13-19
Total http 300 Resolved responses.............................................................................................. 13-19
Total http 300 Unresolved responses ......................................................................................... 13-20
Total requests................................................................................................................................. 13-21
Unresolved Redirects.................................................................................................................... 13-21
Portal Homepage Metric .................................................................................................................... 13-22
Homepage Download (msec)...................................................................................................... 13-22
Status............................................................................................................................................... 13-22
Portal Metadata Repository Version Metric................................................................................... 13-23
Portal Metadata Repository Version .......................................................................................... 13-23
Response Metric .................................................................................................................................. 13-23
Status............................................................................................................................................... 13-23
Syndication Server Status Metric..................................................................................................... 13-24
Syndication Server Status ............................................................................................................ 13-24
Top Level Monitoring Status Metric................................................................................................ 13-25
Top Level Monitoring Status....................................................................................................... 13-25
Ultra Search Status Metric ................................................................................................................. 13-25
Ultra Search Status ........................................................................................................................ 13-25
Web Portlet Metrics............................................................................................................................. 13-26
Cache Hits ...................................................................................................................................... 13-26
Count of HTTP 200 Response codes........................................................................................... 13-26
Count of requests which timed out ............................................................................................ 13-27
Count of Resolved HTTP 300 Response codes ......................................................................... 13-28
Count of Unresolved HTTP 300 Response codes ..................................................................... 13-28
Last Response Code ...................................................................................................................... 13-29
Requests.......................................................................................................................................... 13-29
Web Portlet Average Time (msec) .............................................................................................. 13-29
Web Portlet Maximium Time (msec) ......................................................................................... 13-30
Web Portlet Minimum Time (msec) ........................................................................................... 13-30
Web Providers Metrics ....................................................................................................................... 13-30
Cache Hits ...................................................................................................................................... 13-31
xxiv
Count of requests which timed out ............................................................................................ 13-32
Count of Resolved HTTP 300 Response codes ......................................................................... 13-32
Count of Unresolved HTTP 300 Response codes ..................................................................... 13-33
Offline ............................................................................................................................................. 13-33
Percentage of Web Provider HTTP 500 Response codes......................................................... 13-34
Requests.......................................................................................................................................... 13-34
Web Provider Portlets Average Time (msec)............................................................................ 13-35
Web Provider Portlets Maximium Time (msec) ....................................................................... 13-35
Web Provider Portlets Minimum Time (msec)......................................................................... 13-36
Web Provider Status ..................................................................................................................... 13-37
14 Reports Server
Cluster Information .............................................................................................................................. 14-1
Current Jobs ..................................................................................................................................... 14-1
Failed Jobs ........................................................................................................................................ 14-1
Finished Jobs .................................................................................................................................... 14-1
Response Time (ms) ........................................................................................................................ 14-1
Scheduled Jobs................................................................................................................................. 14-1
Current Jobs............................................................................................................................................ 14-1
Job Name .......................................................................................................................................... 14-1
Output Format................................................................................................................................. 14-2
Output Type..................................................................................................................................... 14-2
Owner ............................................................................................................................................... 14-2
Queued At ........................................................................................................................................ 14-2
Started At.......................................................................................................................................... 14-2
Status................................................................................................................................................. 14-2
Engine Information............................................................................................................................... 14-2
Engines.............................................................................................................................................. 14-2
Running ............................................................................................................................................ 14-2
Failed Jobs............................................................................................................................................... 14-2
Finished At ....................................................................................................................................... 14-2
Job Name .......................................................................................................................................... 14-3
Output Format................................................................................................................................. 14-3
Output Type..................................................................................................................................... 14-3
Owner ............................................................................................................................................... 14-3
Queued At ........................................................................................................................................ 14-3
Started At.......................................................................................................................................... 14-3
Status................................................................................................................................................. 14-3
Finished Jobs.......................................................................................................................................... 14-3
Finished At ....................................................................................................................................... 14-3
Job Name .......................................................................................................................................... 14-3
Output Format................................................................................................................................. 14-3
Output Type..................................................................................................................................... 14-3
Owner ............................................................................................................................................... 14-4
xxv
Queued At ........................................................................................................................................ 14-4
Started At.......................................................................................................................................... 14-4
Status................................................................................................................................................. 14-4
Response ................................................................................................................................................. 14-4
Server Status..................................................................................................................................... 14-4
Scheduled Jobs....................................................................................................................................... 14-4
Job Name .......................................................................................................................................... 14-4
Last Run At ...................................................................................................................................... 14-4
Next Run At ..................................................................................................................................... 14-5
Output Format................................................................................................................................. 14-5
Output Type..................................................................................................................................... 14-5
Owner ............................................................................................................................................... 14-5
Repeat Interval................................................................................................................................. 14-5
Server Information................................................................................................................................ 14-5
Active Engines ................................................................................................................................. 14-5
Average Elapsed Time (ms)........................................................................................................... 14-5
Average Response Time (ms) ........................................................................................................ 14-5
Cluster Name ................................................................................................................................... 14-5
Current Jobs ..................................................................................................................................... 14-5
Failed Jobs ........................................................................................................................................ 14-6
Failed Ratio (%) ............................................................................................................................... 14-6
Finished Jobs .................................................................................................................................... 14-6
Scheduled Jobs................................................................................................................................. 14-6
Since (Start Time) ............................................................................................................................ 14-6
Trace File Name............................................................................................................................... 14-6
Trace Mode....................................................................................................................................... 14-6
Transferred Jobs .............................................................................................................................. 14-6
Version .............................................................................................................................................. 14-6
Server Performance Data ..................................................................................................................... 14-6
Active Engines ................................................................................................................................. 14-7
Average Elapsed Time to date (ms) ............................................................................................. 14-7
Cluster Name ................................................................................................................................... 14-7
Current Job Load ............................................................................................................................. 14-7
Current Jobs ..................................................................................................................................... 14-8
Failed Jobs ........................................................................................................................................ 14-8
Job Load............................................................................................................................................ 14-8
Scheduled Jobs................................................................................................................................. 14-8
Since (Start Time) ............................................................................................................................ 14-9
Successful Jobs ................................................................................................................................. 14-9
Trace File Name............................................................................................................................... 14-9
Trace Mode....................................................................................................................................... 14-9
Transferred Jobs ............................................................................................................................ 14-10
Version ............................................................................................................................................ 14-10
15 Single Sign-On Server

Login Server Metrics For The Last 24 Hours.................................................................................... 15-1
Number of Login Attempts ........................................................................................................... 15-1
xxvi
Number of Successful Login Attempts ........................................................................................ 15-1
Number of Unsuccessful Login Attempts ................................................................................... 15-2
Percentage of Successful Logins .................................................................................................. 15-2
Percentage of Unsuccessful Logins ............................................................................................. 15-2
Login Server Metrics For The Last Hour .......................................................................................... 15-3
Number of Login Attempts ........................................................................................................... 15-3
Number of Successful Login Attempts ........................................................................................ 15-3
Number of Unsuccessful Login Attempts ................................................................................... 15-4
Percentage of Successful Logins .................................................................................................. 15-4
Percentage of Unsuccessful Logins ............................................................................................. 15-4
Most Failed Login Users Metrics........................................................................................................ 15-5
Frequency ......................................................................................................................................... 15-5
Subscriber ID.................................................................................................................................... 15-5
Subscriber Name ............................................................................................................................. 15-5
SSO Database Instance Metric ........................................................................................................... 15-6
Instance Name ................................................................................................................................. 15-6
Start Time ......................................................................................................................................... 15-6
Version .............................................................................................................................................. 15-7
SSO Status Metric ................................................................................................................................. 15-7
Status................................................................................................................................................. 15-7
16 Web Cache
Cache Performance................................................................................................................................ 16-1
Allocated Cache Memory (%)........................................................................................................ 16-1
Cacheable Misses (% of requests) ................................................................................................. 16-1
Cached Documents Count ............................................................................................................. 16-2
Compression Savings (%) .............................................................................................................. 16-2
Data Served (MB/second) ............................................................................................................. 16-2
Errors (% of requests) ..................................................................................................................... 16-3
Hit Rate Per Second ........................................................................................................................ 16-3
Hits (% of requests) ......................................................................................................................... 16-3
Invalidated Objects Per Second..................................................................................................... 16-4
Invalidation Requests Per Second ................................................................................................ 16-4
Misses Per Second ........................................................................................................................... 16-5
Network Errors Per Second ........................................................................................................... 16-5
Noncacheable Misses (% of requests) .......................................................................................... 16-6
Open Connections........................................................................................................................... 16-6
Partial Page Errors Per Second...................................................................................................... 16-7
Refreshes (% of requests) ............................................................................................................... 16-7
Requests Per Second ....................................................................................................................... 16-7
Site Busy Errors Per Second........................................................................................................... 16-8
Size of Cached Documents (MB)................................................................................................... 16-8
Stale Hits (% of requests) ............................................................................................................... 16-8
Total Errors Per Second.................................................................................................................. 16-9
Up Since............................................................................................................................................ 16-9
ESI Errors .............................................................................................................................................. 16-10
ESI Exceptions Not Caught Per Second ..................................................................................... 16-10
xxvii
Times Default ESI Fragment Served Per Second...................................................................... 16-10
Resource Usage .................................................................................................................................... 16-10
CPU Idle Time (%) ........................................................................................................................ 16-10
Free Memory (%)........................................................................................................................... 16-11
Free Memory (MB) ........................................................................................................................ 16-11
Other CPU Usage (%) ................................................................................................................... 16-11
Other Memory Usage (%) ............................................................................................................ 16-12
Other Memory Usage (MB) ......................................................................................................... 16-12
Total Memory (MB) ...................................................................................................................... 16-12
Web Cache CPU Usage (%) ......................................................................................................... 16-12
Web Cache Memory Usage (%)................................................................................................... 16-13
Web Cache Memory Usage (MB)................................................................................................ 16-13
Response ............................................................................................................................................... 16-14
Status............................................................................................................................................... 16-14
Server Performance ............................................................................................................................. 16-14
Active Requests ............................................................................................................................. 16-14
Processing Time (seconds) ........................................................................................................... 16-15
Proxy Server................................................................................................................................... 16-15
Requests Per Second ..................................................................................................................... 16-15
Status............................................................................................................................................... 16-16
17 Web Application
HTTP Content ........................................................................................................................................ 17-1
Average Connect Time ................................................................................................................... 17-1
Average First Byte Time................................................................................................................. 17-1
Average Page Response ................................................................................................................. 17-1
Computed Response Time............................................................................................................. 17-2
Connect Time ................................................................................................................................... 17-2
Content Time ................................................................................................................................... 17-2
DNS Time ......................................................................................................................................... 17-2
First Byte Time................................................................................................................................. 17-3
HTML Bytes ..................................................................................................................................... 17-3
HTML Time...................................................................................................................................... 17-3
Page Content Bytes ......................................................................................................................... 17-3
Page Content Count........................................................................................................................ 17-4
Redirect Count................................................................................................................................. 17-4
Redirect Time................................................................................................................................... 17-4
Request Count ................................................................................................................................. 17-4
Slowest Page Response................................................................................................................... 17-4
Status................................................................................................................................................. 17-5
Status Description ........................................................................................................................... 17-5
Total Bytes ........................................................................................................................................ 17-5
Total Transaction Time................................................................................................................... 17-5
Transfer Rate .................................................................................................................................... 17-5
HTTP Response ..................................................................................................................................... 17-6
Average Connect Time ................................................................................................................... 17-6
Average First Byte Time................................................................................................................. 17-6
xxviii
Average Page Response ................................................................................................................. 17-6
Computed Response Time............................................................................................................. 17-6
Connect Time ................................................................................................................................... 17-7
Content Time ................................................................................................................................... 17-7
DNS Time ......................................................................................................................................... 17-7
First Byte Time................................................................................................................................. 17-7
HTML Time...................................................................................................................................... 17-7
Redirect Time................................................................................................................................... 17-8
Slowest Page Response................................................................................................................... 17-8
Status................................................................................................................................................. 17-8
Status Description ........................................................................................................................... 17-9
Total Transaction Time................................................................................................................... 17-9
Transfer Rate.................................................................................................................................... 17-9
18 Wireless
Active User Count Across all Instances ............................................................................................ 18-1
Active Users ..................................................................................................................................... 18-1
Active User Sessions Across Instances.............................................................................................. 18-1
Active Sessions ................................................................................................................................ 18-1
Average Response Time for the Interval........................................................................................... 18-2
Average Response Time (seconds) ............................................................................................... 18-2
Response ................................................................................................................................................. 18-2
Status................................................................................................................................................. 18-2
Services Requested ............................................................................................................................... 18-3
Services Invoked.............................................................................................................................. 18-3
Status Codes of all components.......................................................................................................... 18-3
Status Code ...................................................................................................................................... 18-4
Part IV Oracle Collaboration Suite Metrics
19 Calendar Applications
Calendar Applications DB Size.......................................................................................................... 19-1
% Disk Space Available .................................................................................................................. 19-1
Filesystem......................................................................................................................................... 19-2
Mounted on...................................................................................................................................... 19-2
Total Disk Space (Kb) ..................................................................................................................... 19-2
Total Size (Kb).................................................................................................................................. 19-3
Total Space Free (Kb) ...................................................................................................................... 19-3
Total Space Used (Kb) .................................................................................................................... 19-3
Calendar Applications Processes Info............................................................................................... 19-3
CPU Time ......................................................................................................................................... 19-4
Elapsed Time.................................................................................................................................... 19-4
Memory Size (Kb) ........................................................................................................................... 19-4
PID..................................................................................................................................................... 19-5
Response ................................................................................................................................................. 19-5
Response Time................................................................................................................................. 19-5
xxix
Status Code ...................................................................................................................................... 19-5
20 Calendar Server
Calendar DB Size .................................................................................................................................. 20-1
% Disk Space Available .................................................................................................................. 20-1
Filesystem......................................................................................................................................... 20-2
Mounted on...................................................................................................................................... 20-2
Total Disk Space (MB) .................................................................................................................... 20-2
Total Size (MB)................................................................................................................................. 20-3
Total Space Free (MB)..................................................................................................................... 20-3
Total Space Used (MB) ................................................................................................................... 20-3
Calendar Server Top Processes ........................................................................................................... 20-4
CPU Time ......................................................................................................................................... 20-4
Elapsed Time.................................................................................................................................... 20-4
Memory Size (MB) .......................................................................................................................... 20-4
PID..................................................................................................................................................... 20-5
Connections ............................................................................................................................................ 20-5
Number of Dedicated Connections .............................................................................................. 20-5
Number of Reserved Connections................................................................................................ 20-5
Number of Shared Connections.................................................................................................... 20-6
Total Number of Calendar Connections...................................................................................... 20-6
Current Requests in CWS Queue....................................................................................................... 20-6
Alert Requests.................................................................................................................................. 20-6
Mail Requests................................................................................................................................... 20-7
Replication Requests....................................................................................................................... 20-7
Web Conf. Requests ........................................................................................................................ 20-8
CWS Cumulative Queue Stats ............................................................................................................ 20-8
Mail Requests Errors....................................................................................................................... 20-8
Mail Requests Processed ................................................................................................................ 20-9
Replication Requests Errors........................................................................................................... 20-9
Replication Requests Processed .................................................................................................... 20-9
SSR Requests Errors...................................................................................................................... 20-10
SSR Requests Processed ............................................................................................................... 20-10
Wireless Requests Errors.............................................................................................................. 20-10
Wireless Requests Processed ....................................................................................................... 20-11
Response ............................................................................................................................................... 20-11
Status............................................................................................................................................... 20-11
Status Code .................................................................................................................................... 20-12
Response Time (64Kb)........................................................................................................................ 20-12
Time Excluding Authentication OH (ms).................................................................................. 20-12
Time Excluding Connection OH (ms) ........................................................................................ 20-13
Total Transaction Time (ms)........................................................................................................ 20-13
21 IMAP Server
Append Details...................................................................................................................................... 21-1
Append Average Time ................................................................................................................... 21-1
Append Count ................................................................................................................................. 21-1
xxx
Append Failure Count.................................................................................................................... 21-1
Authenticate Details ............................................................................................................................. 21-2
Authenticate Average Time........................................................................................................... 21-2
Authenticate Count......................................................................................................................... 21-2
Authenticate Failure Count ........................................................................................................... 21-3
Bytes Transferred................................................................................................................................... 21-3
Bytes Received By Server ............................................................................................................... 21-3
Bytes Sent By Server ....................................................................................................................... 21-3
Client Connections................................................................................................................................ 21-4
Lost Client Connections ................................................................................................................. 21-4
Timed Out Client Connections...................................................................................................... 21-4
Total Client Connections................................................................................................................ 21-5
Copy Details ........................................................................................................................................... 21-5
Copy Average Time ........................................................................................................................ 21-5
Copy Count ...................................................................................................................................... 21-6
Copy Failure Count ........................................................................................................................ 21-6
Examine Details ..................................................................................................................................... 21-6
Examine Average Time .................................................................................................................. 21-6
Examine Count ................................................................................................................................ 21-7
Examine Failure Count................................................................................................................... 21-7
Expunge Details..................................................................................................................................... 21-7
Expunge Average Time.................................................................................................................. 21-7
Expunge Count................................................................................................................................ 21-8
Expunge Failure Count .................................................................................................................. 21-8
Fetch Details ........................................................................................................................................... 21-8
Fetch Average Time ........................................................................................................................ 21-8
Fetch Count ...................................................................................................................................... 21-9
Fetch Failure Count......................................................................................................................... 21-9
Login Details .......................................................................................................................................... 21-9
Login Average Time ....................................................................................................................... 21-9
Login Count ................................................................................................................................... 21-10
Login Failure Count...................................................................................................................... 21-10
Login Success Count ..................................................................................................................... 21-10
Logout Details...................................................................................................................................... 21-11
Logout Average Time................................................................................................................... 21-11
Logout Count................................................................................................................................. 21-11
Logout Failure Count ................................................................................................................... 21-11
NOOP Details ...................................................................................................................................... 21-12
NOOP Average Time.................................................................................................................... 21-12
NOOP Count.................................................................................................................................. 21-12
NOOP Failure Count .................................................................................................................... 21-12
Pass Details........................................................................................................................................... 21-13
Pass Average Time........................................................................................................................ 21-13
Pass Count...................................................................................................................................... 21-13
Pass Failure Count ........................................................................................................................ 21-13
Quit Details .......................................................................................................................................... 21-14
Quit Average Time........................................................................................................................ 21-14
xxxi
Quit Count...................................................................................................................................... 21-14
Quit Failure Count ........................................................................................................................ 21-14
Reset Details......................................................................................................................................... 21-15
Reset Average Time ...................................................................................................................... 21-15
Reset Count .................................................................................................................................... 21-15
Reset Failure Count....................................................................................................................... 21-15
Response ............................................................................................................................................... 21-16
Status............................................................................................................................................... 21-16
Retries Details...................................................................................................................................... 21-16
Retries Average Time ................................................................................................................... 21-17
Retries Count ................................................................................................................................. 21-17
Retries Failure Count .................................................................................................................... 21-17
Stat Details............................................................................................................................................ 21-17
Stat Average Time ......................................................................................................................... 21-18
Stat Count ....................................................................................................................................... 21-18
Stat Failure Count ......................................................................................................................... 21-18
Status Details ....................................................................................................................................... 21-18
Status Average Time..................................................................................................................... 21-19
Status Count................................................................................................................................... 21-19
Status Failure Count ..................................................................................................................... 21-19
Store Details ......................................................................................................................................... 21-19
Store Average Time....................................................................................................................... 21-20
Store Count..................................................................................................................................... 21-20
Store Failure Count ....................................................................................................................... 21-20
22 IMAP Service
Response ................................................................................................................................................. 22-1
Connect Time (ms) .......................................................................................................................... 22-1
Login Time (ms) .............................................................................................................................. 22-1
Status................................................................................................................................................. 22-2
Time to List Folders (ms) ............................................................................................................... 22-2
Time to Read Email (ms) ................................................................................................................ 22-3
Total Time (ms)................................................................................................................................ 22-3
23 Mailstore
Message Queue ...................................................................................................................................... 23-1
Length Of All Queues..................................................................................................................... 23-1
Length of Collect Queue ................................................................................................................ 23-1
Length of List Queue ...................................................................................................................... 23-2
Length of Local Queue ................................................................................................................... 23-2
Length of Prune Queue .................................................................................................................. 23-2
Length of Relay Queue................................................................................................................... 23-3
Length of Submit Queue ................................................................................................................ 23-3
Messages Being Processed ............................................................................................................. 23-4
Messages Marked For GC .............................................................................................................. 23-4
Response ................................................................................................................................................. 23-4
Status................................................................................................................................................. 23-4
xxxii
24 OID Client
Response ................................................................................................................................................. 24-1
Addressing Search Time (ms) ....................................................................................................... 24-1
Base Search Time (ms) .................................................................................................................... 24-1
Compare Time (ms) ........................................................................................................................ 24-2
Messaging Search Time (ms) ......................................................................................................... 24-2
Status................................................................................................................................................. 24-3
25 OVF AQMWI Application

Response ................................................................................................................................................. 25-1
Status................................................................................................................................................. 25-1
26 OVF FaxIn Application

Response ................................................................................................................................................. 26-1
Status................................................................................................................................................. 26-1
27 OVF Mailstore
Activity Time.......................................................................................................................................... 27-1
Activity User Count ........................................................................................................................ 27-1
Average Response Time................................................................................................................. 27-1
Sum of Response Time ................................................................................................................... 27-2
Database Login Time ............................................................................................................................ 27-2
DB Login Time User Count ........................................................................................................... 27-2
Delivery Time......................................................................................................................................... 27-3
Elapsed Time (msec) ....................................................................................................................... 27-3
Listen To Message Time ....................................................................................................................... 27-3
Listen Time User Count ................................................................................................................. 27-3
Response ................................................................................................................................................. 27-4
Status................................................................................................................................................. 27-4
User Login Time .................................................................................................................................... 27-5
User Count for Login Time............................................................................................................ 27-5
28 OVF Telephony Midtier

Number of Callers................................................................................................................................. 28-1
Current Number of Callers............................................................................................................ 28-1
Total Number of Callers................................................................................................................. 28-1
Response ................................................................................................................................................. 28-1
Status................................................................................................................................................. 28-2
29 OVF MWI Service

Response ................................................................................................................................................. 29-1
Status................................................................................................................................................. 29-1
xxxiii
30 OVF Recording Application
Activity Total Time................................................................................................................................ 30-1
Recording Activity Total Response Time .................................................................................... 30-1
Recording Activity User Count..................................................................................................... 30-1
Recording Avg Response Time ..................................................................................................... 30-2
Caller Greeting Wait Time................................................................................................................... 30-2
Num Users waiting for Greeting .................................................................................................. 30-2
Response ................................................................................................................................................. 30-3
Response Status ............................................................................................................................... 30-3
31 OVF Recovery Application

Response ................................................................................................................................................. 31-1
Status................................................................................................................................................. 31-1
32 OVF Retrieval Application

Activity Total Time................................................................................................................................ 32-1
Retrieval Avg Response Time ....................................................................................................... 32-1
Retrieval Number of Users ............................................................................................................ 32-2
Retrieval Sum of Response Time .................................................................................................. 32-2
Database Login Time ............................................................................................................................ 32-2
DB Login Time User Count ........................................................................................................... 32-2
Listen To Message Time ....................................................................................................................... 32-3
Listen Time User Count ................................................................................................................. 32-3
Response ................................................................................................................................................. 32-4
Status................................................................................................................................................. 32-4
User Login Time .................................................................................................................................... 32-4
Login Time User Count .................................................................................................................. 32-4
33 OVF Routing Application

Response ................................................................................................................................................. 33-1
Status................................................................................................................................................. 33-1
34 OVF Transfer Application

Response ................................................................................................................................................. 34-1
Status................................................................................................................................................. 34-1
35 POP Server
Response ................................................................................................................................................. 35-1
Status................................................................................................................................................. 35-1
36 POP Service
Response ................................................................................................................................................. 36-1
Connect Time (ms) .......................................................................................................................... 36-1
Login Time (ms) .............................................................................................................................. 36-1
xxxiv
Status................................................................................................................................................. 36-2
Time to Read Email (ms)................................................................................................................ 36-2
Total Time (ms)................................................................................................................................ 36-3
37 SMTP IN Server
Bytes Transmitted ........................................................................................................................... 37-1
Client Connections................................................................................................................................ 37-1
Current Client Connections ........................................................................................................... 37-1
Current SMTP Connections ........................................................................................................... 37-2
Total Inbound SMTP Connections................................................................................................ 37-2
Messages ................................................................................................................................................. 37-3
Current number of messages deferred ........................................................................................ 37-3
Total number of messages deferred ............................................................................................. 37-3
Total number of messages transmitted........................................................................................ 37-4
Response ................................................................................................................................................. 37-4
Status................................................................................................................................................. 37-4
38 SMTP IN Service
Response ................................................................................................................................................. 38-1
Connect Time (ms) .......................................................................................................................... 38-1
Status................................................................................................................................................. 38-1
Time To Send Email(ms) ................................................................................................................ 38-2
Total Time (ms)................................................................................................................................ 38-2
39 SMTP OUT Server

Bytes Sent By Server ....................................................................................................................... 39-1
Messages ................................................................................................................................................. 39-1
Messages Queued ........................................................................................................................... 39-1
Messages Sent to DL ....................................................................................................................... 39-2
Messages Transmitted .................................................................................................................... 39-2
Outbound SMTP Connections ........................................................................................................... 39-3
Current Outbound SMTP Connections ....................................................................................... 39-3
Total Outbound SMTP Connections ............................................................................................ 39-3
Response ................................................................................................................................................. 39-4
Status................................................................................................................................................. 39-4
40 SMTP OUT Service

Response ................................................................................................................................................. 40-1
Status................................................................................................................................................. 40-1
41 Web Conferencing
Process Information .............................................................................................................................. 41-1
CPU Idle (%) .................................................................................................................................... 41-1
xxxv
CPU Other (%) ................................................................................................................................. 41-1
CPU Usage (%) ................................................................................................................................ 41-1
Free Physical Memory (MB) .......................................................................................................... 41-2
Page Size (Bytes).............................................................................................................................. 41-2
Physical Memory Percentage ........................................................................................................ 41-3
Physical Memory Usage (MB)....................................................................................................... 41-3
Total Physical Memory Usage (MB)............................................................................................. 41-3
Response ................................................................................................................................................. 41-3
Status................................................................................................................................................. 41-4
Service Usage ......................................................................................................................................... 41-4
Active Clients................................................................................................................................... 41-4
Active Sessions ................................................................................................................................ 41-4
Memory Used KB ............................................................................................................................ 41-5
Total Memory KB ............................................................................................................................ 41-5
Total Sessions................................................................................................................................... 41-6
Part V Metrics Specific to Enterprise Manager
42 Agent
Agent Process Statistics........................................................................................................................ 42-1
CPU Usage (%) ................................................................................................................................ 42-1
Number Files Open......................................................................................................................... 42-2
Number Threads Created .............................................................................................................. 42-2
Process ID ......................................................................................................................................... 42-3
Resident Memory Utilization (%) ................................................................................................. 42-3
Resident Memory Utilization (KB) ............................................................................................... 42-3
Virtual Memory Utilization (KB) .................................................................................................. 42-4
Virtual Memory Utilization Growth (%) ..................................................................................... 42-4
Response ................................................................................................................................................. 42-5
Status................................................................................................................................................. 42-5
Upload Statistics .................................................................................................................................... 42-6
Last Successful Upload................................................................................................................... 42-6
Number of Files to Upload ............................................................................................................ 42-6
Size of Files to Upload (MB) .......................................................................................................... 42-7
Upload Rate (KB/sec)..................................................................................................................... 42-7
User Identification ................................................................................................................................ 42-7
Group Name .................................................................................................................................... 42-8
Location ............................................................................................................................................ 42-8
Other Groups ................................................................................................................................... 42-8
User Name........................................................................................................................................ 42-9
User Limit Info....................................................................................................................................... 42-9
CoreDump (blocks)......................................................................................................................... 42-9
Data (kbytes) .................................................................................................................................... 42-9
File (blocks) .................................................................................................................................... 42-10
NoFiles (descriptors)..................................................................................................................... 42-10
Stack (kbytes) ................................................................................................................................. 42-11
Time (seconds) ............................................................................................................................... 42-11
xxxvi
Virtual Mem (kbytes).................................................................................................................... 42-12
43 Beacon
ICMP Echo Response............................................................................................................................ 43-1
Average Time (ms).......................................................................................................................... 43-1
Last Host........................................................................................................................................... 43-2
Number of Hops.............................................................................................................................. 43-2
Packets Dropped (%) ...................................................................................................................... 43-2
Status................................................................................................................................................. 43-3
HTTP Response ..................................................................................................................................... 43-3
Intermediate Host IP....................................................................................................................... 43-4
Intermediate Host Name................................................................................................................ 43-4
Packet Number ................................................................................................................................ 43-4
Round Trip Time ............................................................................................................................. 43-4
Time To Live .................................................................................................................................... 43-4
44 OMS and Repository

Notification Status ................................................................................................................................ 44-1
DBMS Job Bad Schedule................................................................................................................. 44-1
DBMS Job Processing Time, % of Last Hour............................................................................... 44-2
DBMS Job UpDown ........................................................................................................................ 44-2
Files Pending Load.......................................................................................................................... 44-2
Job Dispatcher Job Step Average Backlog ................................................................................... 44-3
Job Dispatcher Processing Time, % of Last Hour....................................................................... 44-4
Last Error.......................................................................................................................................... 44-4
Last Load Error................................................................................................................................ 44-4
Loader Directory ............................................................................................................................. 44-4
Loader Name ................................................................................................................................... 44-5
Loader Throughput (rows per hour)............................................................................................ 44-5
Loader Throughput (rows per second)........................................................................................ 44-5
Management Service Status........................................................................................................... 44-5
Message ............................................................................................................................................ 44-6
Next Scheduled Runtime ............................................................................................................... 44-6
Notification Delivery Time ............................................................................................................ 44-6
Notification Processing Time, % of Last Hour............................................................................ 44-6
Notification UpDown ..................................................................................................................... 44-7
Notifications Processed .................................................................................................................. 44-7
Notifications Waiting...................................................................................................................... 44-7
Number of Duplicate Targets........................................................................................................ 44-8
Number of Groups.......................................................................................................................... 44-8
Number of Roles.............................................................................................................................. 44-8
Number of Targets .......................................................................................................................... 44-8
Number of Users ............................................................................................................................. 44-9
Oldest Loader File ........................................................................................................................... 44-9
Repository Tablespace Used.......................................................................................................... 44-9
Session Count................................................................................................................................... 44-9
xxxvii
Status since ..................................................................................................................................... 44-10
Steps Per Second............................................................................................................................ 44-10
Targets not providing data .......................................................................................................... 44-10
Throughput Per Second ............................................................................................................... 44-10
Total Loader Runtime in the Last Hour..................................................................................... 44-10
Total Repository Tablespace........................................................................................................ 44-11
Response ............................................................................................................................................... 44-11
Status............................................................................................................................................... 44-11
xxxviii
Send Us Your Comments
Oracle Enterprise Manager Metric Reference Manual, 10g Release 1 (10.1)

Part No. B12015-01
Oracle welcomes your comments and suggestions on the quality and usefulness of this
publication. Your input is an important part of the information used for revision.
■ Did you find any errors?
■ Is the information clearly presented?
■ Do you need more information? If so, where?
■ Are the examples correct? Do you need more examples?
■ What features did you like most about this manual?
If you find any errors or have any other suggestions for improvement, please indicate
the title and part number of the documentation and the chapter, section, and page
number (if available). You can send comments to us in the following ways:
■ Electronic mail: nedc-doc_us@oracle.com
■ FAX: 603-897-3317 Attn: Oracle Enterprise Manager
■ Postal service:
Oracle Corporation
Oracle Enterprise Manager Documentation
1 Oracle Drive
Nashua, NH 03062
USA
If you would like a reply, please give your name, address, telephone number, and
electronic mail address (optional).
If you have problems with the software, please contact your local Oracle Support
Services.
xxxix
xl
Preface
This manual is a compilation of the target metrics provided in Oracle Enterprise

Manager.
Intended Audience
This manual is intended for Oracle Enterprise Manager users interested in target
metrics.
Purpose of This Manual

The purpose of this manual is to provide a summary of all the metrics available in
Enterprise Manager. Through the Grid Control Console, you can access all the metrics
mentioned in this manual. For those who are not familiar with metric and Enterprise
Manager terminology, here are a few definitions:
■ A metric is a unit of measurement used to report the health of the system.
■ A target is a single component you can monitor or configure with Enterprise
Manager. Examples of targets include: Oracle Database, Linux host, Oracle
Application Server, and Web Conferencing.
■ The Grid Control Console is the Web-based user interface used for centrally
managing your targets.
To access metrics, use the All Metrics page associated with a particular target by doing
the following:
1. From the Grid Control Console, choose the target.
2. On the target’s home page, click All Metrics in the Related Links section.
3. On the All Metrics page, choose the metric of interest and click Help. The help for
that metric displays.
For additional information about metrics and targets, see the Enterprise Manager
online help and Oracle Enterprise Manager Concepts.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible, with good usability, to the disabled community. To that end, our
documentation includes features that make information available to users of assistive
technology. This documentation is available in HTML format, and contains markup to
facilitate access by the disabled community. Standards will continue to evolve over
xli
time, and Oracle is actively engaged with other market-leading technology vendors to
address technical obstacles so that our documentation can be accessible to all of our
customers. For additional information, visit the Oracle Accessibility Program Web site
at
http://www.oracle.com/accessibility/
Accessibility of Code Examples in Documentation JAWS, a Windows screen reader,

may not always correctly read the code examples in this document. The conventions
for writing code require that closing braces should appear on an otherwise empty line;
however, JAWS may not always read a line of text that consists solely of a bracket or
brace.
Accessibility of Links to External Web Sites in Documentation This documentation

may contain links to Web sites of other companies or organizations that Oracle does
not own or control. Oracle neither evaluates nor makes any representations regarding
the accessibility of these Web sites.
Structure
This manual contains a chapter for each Enterprise Manager target for which there are
metrics. The chapters are divided into the following parts: Oracle Database metrics,
Host metrics, Oracle Application Server metrics, Oracle Collaboration Suite metrics,
and metrics specific to Oracle Enterprise Manager.
Chapter 1, "How To Use This Manual"

This chapter explains the structure of the Metric Reference Manual, the structure of the
metric information, abbreviations and acronyms, and background information about
metrics, thresholds, and alerts..
Part I, "Oracle Database Metrics"

This part contains the metrics for the Oracle Database target and the Oracle Listener
target.
Chapter 2, "Database"
This chapter contains the metrics for the Oracle Database target.
Chapter 3, "Listener"
This chapter contains the metrics for the Oracle Listener target.
Part II, "Host Metrics"

This part contains the metrics for the Host targets.
Chapter 4, "Host"
This chapter contains the metrics for the following host targets: Solaris, HP, Linux, HP
Tru64, IBM AIX, and Windows.
Part III, "Oracle Application Server Metrics"

This part contains the metrics for the Oracle Application Server targets.
Chapter 5, "Application Server"

This chapter contains the metrics for the Oracle Application Server target.
xlii
Chapter 6, "Discoverer"
This chapter contains the metrics for the Oracle Application Server Discoverer target.
Chapter 7, "Forms"
This chapter contains the metrics for the Oracle Application Server Forms target.
Chapter 8, "HTTP Server"

This chapter contains the metrics for the Oracle HTTP Server target.
Chapter 9, "Internet File System"

This chapter contains the metrics for the Oracle Internet File System target.
Chapter 10, "JServ"

This chapter contains the metrics for the Oracle JServ target.
Chapter 11, "OC4J"

This chapter contains the metrics for the Oracle Application Server Containers for J2EE
(OC4J) target.
Chapter 12, "OID LDAP Server"

This chapter contains the metrics for the Oracle Internet Directory (OID) Lightweight
Directory Access Protocol (LDAP) Server target.
Chapter 13, "Portal"

This chapter contains the metrics for the Oracle Application Server Portal target.
Chapter 14, "Reports Server"

This chapter contains the metrics for the Oracle Application Server Reports Server
target.
Chapter 15, "Single Sign-On Server"

This chapter contains the metrics for the Oracle Application Server Single Sign-On
Server target.
Chapter 16, "Web Cache"

This chapter contains the metrics for the Oracle Application Server Web Cache target.
Chapter 17, "Web Application"

This chapter contains the metrics for the Oracle Web Application Server target.
Chapter 18, "Wireless"

This chapter contains the metrics for the Oracle Application Server Wireless target.
Part IV, "Oracle Collaboration Suite Metrics"

This part contains the metrics for the Oracle Collaboration Suite metrics.
Chapter 19, "Calendar Applications"

This chapter contains the metrics for the Oracle Calendar Applications target.
xliii
Chapter 20, "Calendar Server"
This chapter contains the metrics for the Oracle Calendar Server target.
Chapter 21, "IMAP Server"

This chapter contains the metrics for the Interactive Mail Access Protocol (IMAP)
Server target.
Chapter 22, "IMAP Service"

This chapter contains the metrics for the Interactive Mail Access Protocol (IMAP)
Service target.
Chapter 23, "Mailstore"

This chapter contains the metrics for the Mailstore target.
Chapter 24, "OID Client"

This chapter contains the metrics for the Oracle Internet Directory Client target.
Chapter 25, "OVF AQMWI Application"

This chapter contains the metrics for the Oracle Voicemail & Fax (OVF) AQMWI
Application target.
Chapter 26, "OVF FaxIn Application"

This chapter contains the metrics for the Oracle Voicemail & Fax (OVF) FaxIn
Application target.
Chapter 27, "OVF Mailstore"

This chapter contains the metrics for the Oracle Voicemail & Fax (OVF) Mailstore
target.
Chapter 28, "OVF Telephony Midtier"

This chapter contains the metrics for the Oracle Voicemail & Fax (OVF) Telephony
Midtier target.
Chapter 29, "OVF MWI Service"

This chapter contains the metrics for the Oracle Voicemail & Fax (OVF) MWI Service
target.
Chapter 30, "OVF Recording Application"

This chapter contains the metrics for the Oracle Voicemail & Fax (OVF) Recording
Application target.
Chapter 31, "OVF Recovery Application"

This chapter contains the metrics for the Oracle Voicemail & Fax (OVF) Recovery
Application target.
Chapter 32, "OVF Retrieval Application"

This chapter contains the metrics for the Oracle Voicemail & Fax (OVF) Retrieval
Application target.
xliv
Chapter 33, "OVF Routing Application"
This chapter contains the metrics for the Oracle Voicemail & Fax (OVF) Routing
Application target.
Chapter 34, "OVF Transfer Application"

This chapter contains the metrics for the Oracle Voicemail & Fax (OVF) Transfer
Application target.
Chapter 35, "POP Server"

This chapter contains the metrics for the Post Office Protocol (POP) Server target.
Chapter 36, "POP Service"

This chapter contains the metrics for the Post Office Protocol Service (POP) target.
Chapter 37, "SMTP IN Server"

This chapter contains the metrics for the Simple Mail Transfer Protocol (SMTP) IN
Server target.
Chapter 38, "SMTP IN Service"

This chapter contains the metrics for the Simple Mail Transfer Protocol (SMTP) IN
Service target.
Chapter 39, "SMTP OUT Server"

This chapter contains the metrics for the Simple Mail Transfer Protocol (SMTP) OUT
Server target.
Chapter 40, "SMTP OUT Service"

This chapter contains the metrics for the Simple Mail Transfer Protocol (SMTP) OUT
Service target.
Chapter 41, "Web Conferencing"

This chapter contains the metrics for the Oracle Web Conferencing target.
Part V, "Metrics Specific to Enterprise Manager"

This part contains the metrics for the Oracle Management Agent, Oracle Beacon,
Oracle Management Service, and the Oracle Management Repository targets.
Chapter 42, "Agent"

This chapter contains the metrics for the Oracle Management Agent target.
Chapter 43, "Beacon"

This chapter contains the metrics for the Oracle Beacon target.
Chapter 44, "OMS and Repository"

This chapter contains the metrics for the Oracle Management Service and the Oracle
Management Repository targets.
Related Documents
For more information, see the following manuals in the Oracle Enterprise Manager 10g
Release 1 (10.1) documentation set:
xlv
■ Oracle Enterprise Manager Grid Control Installation and Basic Configuration
■ Oracle Enterprise Manager Concepts
■ Oracle Enterprise Manager Advanced Configuration
■ Extending Oracle Enterprise Manager
Conventions
The following conventions are also used in this manual:
Convention Meaning
. Vertical ellipsis points in an example mean that information not directly
. related to the example has been omitted.
.
... Horizontal ellipsis points in statements or commands mean that parts
of the statement or command not directly related to the example have
been omitted
boldface text Boldface type in text indicates a term defined in the text, the glossary,
or in both locations.
<> Angle brackets enclose user-supplied names.
[] Brackets enclose optional clauses from which you can choose one or
none.
Abbreviations
To reduce the page count in this document, the following abbreviations and acronyms
are used:
Abbreviation/Acronym Name
Agent Oracle Management Agent
Database Oracle Database
HTTP HyperText Transfer Protocol
IMAP Interactive Mail Access Protocol
LDAP Lightweight Directory Access Protocol
Listener Oracle Listener
OC4J Oracle Application Server Containers for J2EE
OID Oracle Internet Directory
OMS Oracle Management Service
OVF Oracle Voicemail & Fax
POP Post Office Protocol
Repository Oracle Management Repository
SMTP Simple Mail Transfer Protocol
xlvi
1
How To Use This Manual
The Oracle Enterprise Manager Metric Reference Manual (hereafter referred to as the
Metric Reference Manual) lists all the target metrics that Enterprise Manager monitors.
This manual compiles in one place all the target metric help available online,
eliminating the need to have the Grid Control Console up and running.
This chapter describes:
■ Structure of the Metric Reference Manual
■ Background Information on Metrics, Thresholds, and Alerts
Structure of the Metric Reference Manual

This manual contains a chapter for each Enterprise Manager target for which there are
metrics. The chapters are divided into the following parts:
■ Oracle Database Metrics
■ Host Metrics
■ Oracle Application Server Metrics
■ Oracle Collaboration Suite Metrics
■ Metrics Specific to Enterprise Manager
The metrics in each chapter are in alphabetical order according to category.
Metric Information
The information for each metric comprises a description, summary of the metric’s
"vital statistics", data source (if available), and user action. The following list provides
greater detail:
■ Description
Explanation following the metric name. This text defines the metric and, when
available, provides additional information pertinent to the metric.
■ Metric Summary
Explains in table format the target version, collection frequency, upload frequency,
operator, default warning threshold, default critical threshold, consecutive number
of occurrences preceding notification, and alert text for the metric. See Examples of
Metric Summary Tables for examples of Metric Summary tables. See Table 1–1 for
an explanation of each of these statistics.
■ Data Source
How To Use This Manual 1-1

How the metric is calculated. In some metrics, data source information is not
available.
■ User Action
Suggestions of how to solve the problem causing the alert.
Examples of Metric Summary Tables

This section provides examples of Metric Summary tables you will see in the Metric
Reference Manual.
Example 1–1 Target Version and Collection Frequency

When default thresholds are not defined for a metric, only the target version and
collection frequency are available.
Target Version Collection Frequency

All Versions Every 15 Minutes
Example 1–2 Same Evaluation and Collection Frequency

This table shows a metric where the server evaluation frequency is the same as the
collection frequency.
Consecutive
Evaluation Number of
and Default Occurrences
Target Collection Upload Warning Default Critical Preceding
Version Frequency Frequency Operator Threshold Threshold Notification Alert Text
All Every 10 After Every > 10000000 12500000 1 Bytes sent by the
Versions Minutes Sample server are
%value%
Example 1–3 Different Server Evaluation and Collection Frequencies

This table shows a metric where the server evaluation frequency is different from the
collection frequency.
Consecutive
Number of
Server Default Default Occurrences
Target Evaluation Collection Upload Warning Critical Preceding
Version Frequency Frequency Frequency Operator Threshold Threshold Notification Alert Text
10.1.0.x Every Every 5 After > Not Not 2 Generated By
Minute Minutes Every Defined Defined Database Server
Sample
Definitions of Columns in Metric Summary Tables

As previously mentioned, the Metric Summary table is part of the overall metric
information. Table 1–1 provides descriptions of columns in the Metric Summary table.
1-2 Oracle Enterprise Manager Metric Reference Manual

Table 1–1 Definitions of Columns in the Metric Summary Table

Column Header Column Definition
Target Version Version of the target, for example, 9.0.2.x and 10.1.0.x. The x at the end of a version (for example,
9.0.2.x) represents the subsequent patchsets associated with that release.
Evaluation and Collection The rate at which the metric is collected and evaluated to determine whether it has crossed its
Frequency threshold. The evaluation frequency is the same as the collection frequency.
Server Evaluation The rate at which the metric is evaluated to determine whether it has crossed its threshold. For
Frequency server-generated alerts, the evaluation frequency is determined by Oracle Database internals. For
example, if the evaluation frequency is 10 minutes, then when the Average File Write Time
degrades to the point an alert should trigger, it could be almost 10 minutes before Enterprise
Manager receives indication of the alert. This column is present in the Metric Collection Summary
table only for Oracle Database 10g metrics.
Collection Frequency The rate at which the Management Agent collects data. The collection frequency for a metric
comes from the Enterprise Manager default collection file for that target type.
Upload Frequency The rate at which the Management Agent moves data to the Management Repository. For
example, upload every nth collection. The upload frequency for a metric comes from the
Enterprise Manager default collection file for that target type. This column is present in the Metric
Collection Summary table only when the Upload Frequency is different from the Collection
Frequency.
Comparison Operator The comparison method Enterprise Manager uses to evaluate the metric value against the
threshold values.
Default Warning Threshold Value that indicates whether a warning alert should be initiated. If the evaluation of the warning
threshold value returns a result of TRUE for the specified number of consecutive occurrences
defined for the metric, an alert triggers at the warning severity level.
Default Critical Threshold Value that indicates whether a critical alert should be initiated. If the evaluation of the critical
threshold value returns a result of TRUE for the specified number of consecutive occurrences
defined for the metric, an alert triggers at the critical severity level.
Consecutive Number of Consecutive number of times a metric’s value reaches either the warning threshold or critical
Occurrences Preceding threshold before a notification is sent.
Notification
Alert Text Message indicating why the alert was generated. Words that display between percent signs (%)
denote variables. For example, Disk Utilization for %keyValue% is %value%% could
translate to Disk Utilization for d0 is 80%.
Abbreviations and Acronyms

To reduce the page count in this document, the following abbreviations and acronyms
are used:
Agent Oracle Management Agent
Database Oracle Database
HTTP HyperText Transfer Protocol
IMAP Interactive Mail Access Protocol
LDAP Lightweight Directory Access Protocol
Listener Oracle Listener
OC4J Oracle Application Server Containers for J2EE
OID Oracle Internet Directory
OMS Oracle Management Service
OVF Oracle Voicemail & Fax
POP Post Office Protocol
Repository Oracle Management Repository

Background Information on Metrics, Thresholds, and Alerts
SMTP Simple Mail Transfer Protocol

A metric is a unit of measurement used to determine the health of a target. It is
through the use of metrics and associated thresholds that Enterprise Manager sends
out alerts notifying you of problems with the target.
Thresholds are boundary values against which monitored metric values are compared.
For example, for each disk device associated with the Disk Utilization (%) metric, you
can define a different warning and critical threshold. Some of the thresholds are
predefined by Oracle, others are not.
Once a threshold is reached, an alert is generated. An alert is an indicator signifying
that a particular condition has been encountered and is triggered when one of the
following conditions is true:
■ A threshold is reached.
■ An alert has been cleared.
■ The availability of a monitored service changes. For example, the availability of an
application server changes from up to down.
■ A specific condition occurs. For example, an alert is triggered whenever an error
message is written to a database alert log file.
Alerts are detected through a polling-based mechanism by checking for the monitored
condition from a separate process at regular, predefined intervals.
See Also: See the Oracle Enterprise Manager Concepts manual and the
Enterprise Manager online help for additional information about
metrics, thresholds, and alerts
Editing Thresholds
Out of the box, Enterprise Manager comes with thresholds for critical metrics. Warning
and critical thresholds are used to generate an alert, letting you know of impending
problems so that you can address them in a timely manner.
To better suit the monitoring needs of your organization, you can edit the thresholds
provided by Enterprise Manager and define new thresholds. When defining
thresholds, the key is to choose acceptable values to avoid unnecessary alerts, while
still being notified of issues in a timely manner.
You can establish thresholds that will provide pertinent information in a timely
manner by defining metric baselines that reflect how your system runs for a normal
period of time.
The metrics listed on the Edit Thresholds page are either default metrics provided by
Oracle or metrics whose thresholds you can change.
Specifying Multiple Thresholds

The Specifying Multiple Thresholds functionality allows you to define various subsets
of data that can have different thresholds. By specifying multiple thresholds, you can
refine the data used to trigger alerts, which are one of the key benefits of using
Enterprise Manager.

The key in specifying multiple thresholds is to determine how the comparison relates
to the metric threshold as a whole. What benefit will be realized by defining a more
stringent or lax threshold for that particular device, mount point, and so on?
For example, using the Average Disk I/O Service Time metric, you can define warning
and critical thresholds to be applied to all disks (sd0 and sd1), or you can define
different warning and critical thresholds for a specific disk (sd0). This allows you to
adjust the thresholds for sd0 to be more stringent or lax for that particular disk.
Accessing Metrics Using the Grid Control Console

To access metrics in the Grid Control Console, use the All Metrics page associated with
a particular target by doing the following:
1. From the Grid Control Console, choose the target.
2. On the target’s home page, click All Metrics in the Related Links section.
3. On the All Metrics page, choose the metric of interest and click Help. The help for
that metric displays.


Part I
Oracle Database Metrics
Part I contains the metrics related to the Oracle Database.

Part I contains the following chapters:
■ Chapter 2, "Database"
■ Chapter 3, "Listener"
2
Database
The Oracle database metrics provide description, data source, metric index (where
applicable), and user action information for each metric.
Alert Log
This metric category contains the metrics that are used in creating the alert log, for
example, data block corruption, terminated session, and so on.
Alert Log Error Trace File

This metric is the name of the trace file (if any) associated with the logged error.
Metric Summary
The following table shows how often the metric's value is collected.

Data Source
$ORACLE_HOME/sysman/admin/scripts/alertlog.pl where $ORACLE_HOME
refers to the home of the Oracle Management Agent.
User Action
No user action is necessary.
Alert Log Name

This metric is the name of the alert log file.
Metric Summary

Database 2-1
Alert Log
Data Source
User Action
Archiver Hung Alert Log Error

This metric signifies that the archiver of the database being monitored has been
temporarily suspended since the last sample time.
If the database is running in ARCHIVELOG mode, an alert is displayed when
archiving is hung (ORA-00257) messages are written to the ALERT file. The ALERT
file is a special trace file containing a chronological log of messages and errors.
Metric Summary
The following table shows how often the metric's value is collected and compared
against the default thresholds. The 'Consecutive Number of Occurrences Preceding
Notification' column indicates the consecutive number of times the comparison
against thresholds should hold TRUE before an alert is generated.
Table 2–1 Metric Summary Table

Consecutive
and Default Default Occurrences
Target Collection Upload Warning Critical Preceding
All Every 15 After Every CONTAINS Not Defined ORA- 1* The archiver hung at
Versions Minutes Sample time/line number:
%timeLine%.
* Once an alert is triggered for this metric, it must be manually cleared.
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each
"Time/Line Number" object.
If warning or critical threshold values are currently set for any "Time/Line Number"
object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Time/Line
Number" object, use the Edit Thresholds page. See the Editing Thresholds topic in the
Enterprise Manager online help for information on accessing the Edit Thresholds page.
Data Source
User Action
Examine ALERT log and archiver trace file for additional information; however, the
most likely cause of this message is that the destination device is out of space to store
the redo log file. Verify the device specified in the initialization parameter ARCHIVE_
LOG_DEST is set up properly for archiving. Note: This event does not automatically

Alert Log
clear since there is no automatic way of determining when the problem has been
resolved. Hence, you need to manually clear the event once the problem is fixed.
Data Block Corruption Alert Log Error

This metric signifies that the database being monitored has generated a corrupted
block error to the ALERT file since the last sample time. The ALERT file is a special
trace file containing a chronological log of messages and errors. An alert event is
triggered when data block corrupted messages are written to the ALERT file.
Metric Summary

Consecutive
All Every 15 After Every CONTAINS Not Defined ORA- 1* A data block was
Versions Minutes Sample corrupted at
time/line number:
%timeLine%.
Multiple Thresholds
Data Source
User Action
Examine ALERT log for additional information. Note: This event does not
automatically clear since there is no automatic way of determining when the problem
has been resolved. Hence, you need to manually clear the event once the problem is
fixed.
Generic Alert Log Error

This metric signifies that the database being monitored has generated errors to the
ALERT log file since the last sample time. The ALERT log file is a special trace file
containing a chronological log of messages and errors. An alert event is triggered
Database 2-3
Alert Log
when Oracle Exception (ORA-006xx) messages are written to the ALERT log file. A
warning is displayed when other ORA messages are written to the ALERT log file.
Deadlock detected (ORA-00060), archiver hung (ORA-00257), and data block
corrupted (ORA-01578) messages are sent out as separate metrics.
Metric Summary

Consecutive
All Every 15 After Every MATCH ORA-0*(600? Not Defined 1* ORA-error stack
Versions Minutes Sample |7445|4[0-9][ (%errCodes%)
0-9][0-9])[^0-9 logged in
] %alertLogName%.
Multiple Thresholds
Data Source
User Action
Examine ALERT log for additional information. Note: This event does not
automatically clear since there is no automatic way of determining when the problem
has been resolved. Hence, you need to manually clear the event once the problem is
fixed.
Session Terminated Alert Log Error

This metric signifies that a session terminated unexpectedly since the last sample time.
The ALERT file is a special trace file containing a chronological log of messages and
errors. An alert is displayed when session unexpectedly terminated (ORA-00603)
messages are written to the ALERT file.

Alert Log Error Status
Metric Summary

Consecutive
All Every 15 After Every CONTAINS ORA- Not Defined 1* A session was
Versions Minutes Sample terminated at
time/line number:
%timeLine%.
Multiple Thresholds
Data Source
User Action
Examine the ALERT log and the session trace file for additional information. Note:
This event does not automatically clear since there is no automatic way of determining
when the problem has been resolved. Hence, you need to manually clear the event
once the problem is fixed.

This metric category places all the types of alert log errors into four categories:
Archiver Hung, Data Block Corruption, Session Terminated, and Generic. The metrics
in this category represent whether the last scan of the alert log identified any of the
aforementioned categories of error and, if so, how many.
Archiver Hung Alert Log Error Status

This metric reflects the number of Archiver Hung alert log errors witnessed the last
time Enterprise Manager scanned the Alert Log.
Database 2-5
Metric Summary

Consecutive
All Every 15 After Every > 0 Not Defined 1 Archiver hung errors
Versions Minutes Sample have been found in
the alert log.
Data Source
Alert Log metric
User Action
Examine the Alert Log.
Data Block Corruption Alert Log Error Status

This metric reflects the number of Data Block Corruption alert log errors witnessed the
last time Enterprise Manager scanned the Alert Log.
Metric Summary

Consecutive
All Every 15 After Every > 0 Not Defined 1 Data block
Versions Minutes Sample corruption errors
have been found in
the alert log.
Data Source
Alert Log metric
User Action
Generic Alert Log Error Status

This metric reflects the number of Generic alert log errors witnessed the last time
Enterprise Manager scanned the Alert Log.

Archive Area
Metric Summary

Consecutive
All Every 15 After Every > 0 Not Defined 1 %value% distinct
Versions Minutes Sample types of ORA- errors
have been found in
the alert log.
Data Source
Alert Log metric
User Action
Session Terminated Alert Log Error Status

This metric reflects the number of Session Terminated alert log errors witnessed the
last time Enterprise Manager scanned the Alert Log.
Metric Summary

Consecutive
All Every 15 After Every > 0 Not Defined 1 Session terminations
Versions Minutes Sample have been found in
the alert log.
Data Source
Alert Log metric
User Action
Archive Area
This metric category contains the metrics representing the utilization of the various
archive areas.
Database 2-7
Archive Area
If the database is running in ARCHIVELOG mode, this metric checks for available
redo log destination device. It returns the percentage of used space of the redo log
destination.
Archive Area Used (%)

The Archive Full (%) metric returns the percentage of space used on the archive area
destination. If the space used is more than the threshold value given in the threshold
arguments, then a warning or critical alert is generated.
If the database is not running in ARCHIVELOG mode or all archive destinations are
standby databases for Oracle8i, this metric fails to register.
Metric Summary

Consecutive
All Every 15 After Every > 80 Not Defined 1 %value%%% of
Versions Minutes 4 Samples archive area
%archDir% is used.
Multiple Thresholds
"Archive Area Destination" object.
If warning or critical threshold values are currently set for any "Archive Area
Destination" object, those thresholds can be viewed on the Metric Detail page for this
metric.
To specify or change warning or critical threshold values for each "Archive Area
Destination" object, use the Edit Thresholds page. See the Editing Thresholds topic in
the Enterprise Manager online help for information on accessing the Edit Thresholds
page.
Data Source
If no quota is set for archive area, the percentage is calculated using the UNIX df -k
command.
If quota is set:
archive area used (%) = (total area used / total archive area) * 100
User Action
Verify the device specified in the initialization parameter LOG_ARCHIVE_DEST is set
up properly for archiving.
■ For Oracle8, verify that the LOG_ARCHIVE_DEST and LOG_ARCHIVE_
DUPLEX_DEST initialization parameters are set up properly for archiving.

Archive Area
■ For Oracle8i, there are two methods you can use to specify archive destinations.
The first method is to use the LOG_ARCHIVE_DEST_n parameter (where n is an
integer from 1 to 5) to specify from one to five different destinations for archival.
Each numerically-suffixed parameter uniquely identifies an individual
destination, for example, LOG_ARCHIVE_DEST_1, LOG_ARCHIVE_DEST_2, and
so on. The second method, which allows you to specify a maximum of two
locations, is to use the LOG_ARCHIVE_DEST parameter to specify a primary
archive destination and the LOG_ARCHIVE_DUPLEX_DEST parameter to
determine an optional secondary location.
If the LOG_ARCHIVE_DEST initialization parameter is set up correctly and this
metric triggers, then free up more space in the destination specified by the archive
destination parameters.
Archive Area Used (KB)

This metric represents the total space used (in KB) on the device containing the archive
destination directory.
Metric Summary

Data Source
If no quota is set for archive area, this is calculated through the UNIX df -k
command.
If quota is set:
total area used = quota_used * db_block_size (in KB)
User Action
Database 2-9
Archive Area
Free Archive Area (KB)

When running a database in ARCHIVELOG mode, the archiving of the online redo log
is enabled. Filled groups of the online redo log are archived, by default, to the
destination specified by the LOG_ARCHIVE_DEST initialization parameter. If this
destination device becomes full, the database operation is temporarily suspended until
disk space is available.
If the database is running in ARCHIVELOG mode, this metric checks for available
redo log destination devices.
If the database is not running in ARCHIVELOG mode, or all archive destinations are
standby databases for Oracle8i, this metric fails to register.
Metric Summary

Consecutive
All Every 15 After Every < Not Defined Not Defined 1 Archive area
Versions Minutes 4 Samples %archDir% has
%value% free KB
remaining.
Multiple Thresholds
"Archive Area Destination" object.
If warning or critical threshold values are currently set for any "Archive Area
Destination" object, those thresholds can be viewed on the Metric Detail page for this
metric.
To specify or change warning or critical threshold values for each "Archive Area
Destination" object, use the Edit Thresholds page. See the Editing Thresholds topic in
the Enterprise Manager online help for information on accessing the Edit Thresholds
page.
Data Source
If the database is in NOARCHIVELOG mode, then nothing is collected.
If the database is in ARCHIVELOG mode, log_archive_destination from v$parameter
is queried to obtain the current list of archivelog destinations. The results are obtained
by directly checking the disk usage (df -kl).
User Action

Data Guard
Total Archive Area (KB)

This metric represents the total space (in KB) on the device containing the archive
Metric Summary

Data Source
If no quota is set for archive area, this is calculated through the UNIX df -k
command.
If quota is set:
total archive area = quota_size * db_block_size (in KB)
User Action
Oracle recommends that multiple archivelog destinations across different disks be
configured. When at least one archivelog destination gets full, Oracle recommends the
following:
■ If tape is being used, back up archivelogs to tape and delete the archivelogs.
■ If tape is not being used, back up the database and remove obsolete files. This also
removes archivelogs that are no longer needed based on the database retention
policy.
■ If archivelog destination quota_size is being used, raise the quota_size.
Data Guard
The Data Guard metrics check the status, data not received, and data not applied for
the databases in the Data Guard configuration.
For information about Data Guard metrics, see the "Managing Data Guard Metrics"
section of the "Data Guard Manager Scenarios" chapter in the Oracle10i Data Guard
Broker book.
Database 2-11
Data Guard
Data Guard Status

Use the Data Guard Status metric to check the status of each database in the Data
Guard configuration.
By default, a critical and warning threshold value was set for this metric column.
Alerts will be generated when threshold values are reached. You can edit the value for
a threshold as required.
Metric Summary

Consecutive
9.2.0.x; Every 5 After Every CONTAINS Warning Error 1 The Data Guard
10.1.0.x Minutes Sample status of %dg_
name% is %value%.
Multiple Thresholds
"Name" object.
If warning or critical threshold values are currently set for any "Name" object, those
thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Name" object, use
the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise Manager
online help for information on accessing the Edit Thresholds page.
User Action
1. Check the Edit Properties General page for the primary and standby databases for
detailed information.
2. Examine the database alert logs and the Data Guard broker logs for additional
information.
Broker book.
Data Not Applied (logs)

Use the Data Not Applied metric to measure the difference (in number of archived
redo logs) between the last log received and the last log applied for each standby
database in the Data Guard configuration.

Data Guard
Metric Summary

Consecutive
9.2.0.x; Every 5 After Every > 1 3 1 Standby database
10.1.0.x Minutes Sample %dg_name% has not
applied the last
%value% received
logs.
Multiple Thresholds
"Name" object.
User Action
1. Check the Log File Details page for detailed information.
information.
Broker book.
Data Not Applied (MB)

Use the Data Not Applied (MB) metric to measure the difference (in megabytes)
between the last log received and the last log applied for each standby database in the
Data Guard configuration.
By default, critical and warning threshold values were not set for this metric column.
Metric Summary
Database 2-13
Data Guard

Consecutive
10.1.0.x Every 5 After Every > Not Defined Not Defined 1 Standby database
Minutes Sample %dg_name% has not
applied the last
%value% megabytes
of data received.
Multiple Thresholds
"Name" object.
User Action
information.
Broker book.
Data Not Received (logs)

Use the Data Not Received metric to measure the difference (in number of archived
redo logs) between the current log on the primary database and the last log received
on each standby database in the Data Guard configuration.
Metric Summary

Data Guard

Consecutive
9.2.0.x; Every 5 After Every > 1 3 1 Standby database
10.1.0.x Minutes Sample %dg_name% has not
received the last
%value% logs from
the primary
database.
Multiple Thresholds
"Name" object.
User Action
information.
Broker book.
Data Not Received (MB)

This metric measures the difference (in megabytes) between the current log on the
primary database and the last log received to each standby database in the Data Guard
configuration.
By default, critical and warning threshold values were not set for this metric column.
Metric Summary
Database 2-15
Database Files

Consecutive
10.1.0.x Every 5 After Every > Not Defined Not Defined 1 Standby database
Minutes Sample %dg_name% has not
received the last
%value% megabytes
of data from the
primary database.
Multiple Thresholds
"Name" object.
User Action
information.
Broker book.
Database Files
This metric category contains the database file metrics.
Average File Read Time (centi-seconds)

This metric represents the average file read time, measured in hundredths of a second.
Metric Summary

Consecutive
Number of
10.1.0.x Every 10 Every 5 After Every > Not Not 1 Generated By
Minutes Minutes Sample Defined Defined Database Server

Database Files
Multiple Thresholds
"File Name" object.
If warning or critical threshold values are currently set for any "File Name" object,
those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "File Name" object,
use the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise
Manager online help for information on accessing the Edit Thresholds page.
User Action
View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more
detailed analysis, run ADDM from the Advisor Central link on the Database Home
page.
Average File Write Time (centi-seconds)

This metric represents the average file write time, measured in hundredths of a
second.
Metric Summary

Consecutive
Number of
10.1.0.x Every 10 Every 5 After Every > Not Not 1 Generated By
Minutes Minutes Sample Defined Defined Database Server
Multiple Thresholds
"File Name" object.
If warning or critical threshold values are currently set for any "File Name" object,
To specify or change warning or critical threshold values for each "File Name" object,
User Action
page.
Database 2-17
Database Job Status
Database Job Status

This metric category contains the metrics that represent the health of database jobs
registered through the DBMS_JOB interface.
Broken Job Count

The Oracle Server job queue is a database table that stores information about local jobs
such as the PL/SQL call to execute for a job such as when to run a job. Database
replication is also managed by using the Oracle job queue mechanism using jobs to
push deferred transactions to remote master sites, to purge applied transactions from
the deferred transaction queue or to refresh snapshot refresh groups.
A job can be broken in two ways:
Oracle has failed to successfully execute the job after sixteen attempts. The job has
been explicitly marked as broken by using the procedure DBMS_ JOB.BROKEN
This metric checks for broken DBMS jobs. A critical alert is generated if the number of
broken jobs exceeds the value specified by the threshold argument.
Metric Summary

Consecutive
All Every 5 Not > 0 Not Defined 1 %value% job(s) are
Versions Minutes Uploaded broken.
Data Source
SELECT COUNT(*)
FROM dba_jobs
WHERE broken aa 'N'
User Action
Check the ALERT log and trace files for error information. Correct the problem that is
preventing the job from running. Force immediate re-execution of the job by calling
DBMS_JOB.RUN.
Failed Job Count

The Oracle Server job queue is a database table that stores information about local jobs
such as the PL/SQL call to execute for a job such as when to run a job. Database
replication is also managed by using the Oracle job queue mechanism using jobs to
push deferred transactions to remote master sites, to purge applied transactions from
the deferred transaction queue or to refresh snapshot refresh groups.
If a job returns an error while Oracle is attempting to execute it, the job fails. Oracle
repeatedly tries to execute the job doubling the interval of each attempt. If the job fails

Database Limits
sixteen times, Oracle automatically marks the job as broken and no longer tries to
execute it.
This metric checks for failed DBMS jobs. An alert is generated if the number of failed
job exceeds the value specified by the threshold argument.
Metric Summary

Consecutive
All Every 5 Not > 0 Not Defined 1 %value% job(s) have
Versions Minutes Uploaded failed.
Data Source
SELECT COUNT(*)
FROM dba_jobs
WHERE NVL(failures, 0) aa 0"
User Action
Check the ALERT log and trace files for error information. Correct the problem that is
preventing the job from running.
Database Limits
This metric category contains the metrics that represent the percentage of resource
limitations at which the Oracle Server is operating.
Current Logons Count

This metric represents the current number of logons.
Metric Summary

Consecutive
Number of
10.1.0.x Every Every 5 After Every > Not Not 3 Generated By
Minute Minutes Sample Defined Defined Database Server
Database 2-19
Database Limits
Data Source
logons current
User Action
page.
Current Open Cursors Count

This metric represents the current number of opened cursors.
Metric Summary

Consecutive
Number of
10.1.0.x Every Every 5 After Every > 1200 Not 3 Generated By
Minute Minutes Sample Defined Database Server
Data Source
opened cursors current
User Action
page.
Lock Limit Usage (%)

The DML_LOCKS initialization parameter specifies the maximum number of DML
locks. The purpose of DML locks is to guarantee the integrity of data being accessed
concurrently by multiple users. DML locks prevent destructive interference of
simultaneous conflicting DML and/or DDL operations.
This metric checks for the utilization of the lock resource against the values
(percentage) specified by the threshold arguments. If the percentage of all active DML
locks to the limit set in the DML_LOCKS initialization parameter exceeds the values
specified in the threshold arguments, then a warning or critical alert is generated.
If DML_LOCKS is 0, this test fails to register. A value of 0 indicates that enqueues are
disabled.
Metric Summary

Database Limits


Consecutive
8.1.7.4; Every 15 After Every > 80 Not Defined 3 %target% has
9.0.1.x; Minutes Sample reached
9.2.0.x %value%%% of the
lock limit.
Data Source
SELECT resource_name name,
100*DECODE(initial_allocation, ' UNLIMITED', 0, current_utilization /
initial_allocation) usage
FROM v$resource_limit
WHERE LTRIM(limit_value)
!= '0' AND LTRIM(initial_allocation) != '0' AND resource_name = 'dml_locks'
User Action
Increase the DML_LOCKS instance parameter by 10%.
Process Limit Usage (%)

The PROCESSES initialization parameter specifies the maximum number of operating
system user processes that can simultaneously connect to a database at the same time.
This number also includes background processes utilized by the instance.
This metric checks for the utilization of the process resource against the values
(percentage) specified by the threshold arguments. If the percentage of all current
processes to the limit set in the PROCESSES initialization parameter exceeds the
values specified in the threshold arguments, then a warning or critical alert is
generated.
Metric Summary

Consecutive
8.1.7.4; Every 15 After Every > Not Defined Not Defined 3 %target% has
process limit.
Database 2-21
Database Limits

Consecutive
Number of
Data Source
100*DECODE(initial_allocation, ' UNLIMITED', 0, current_utilization) != '0'
AND resource_name = 'processes'
User Action
Verify that the current PROCESSES instance parameter setting has not exceeded the
operating system-dependent maximum. Increase the number of processes to be at least
6 + the maximum number of concurrent users expected to log in to the instance.
Session Limit Usage (%)

The SESSIONS initialization parameter specifies the maximum number of concurrent
connections that the database will allow.
This metric checks for the utilization of the session resource against the values
(percentage) specified by the threshold arguments. If the percentage of the number of
sessions, including background processes, to the limit set in the SESSIONS
initialization parameter exceeds the values specified in the threshold arguments, then
a warning or critical alert is generated.
Metric Summary

Consecutive
8.1.7.4; Every 15 After Every > 90 97 3 %target% has
session limit.

Consecutive
Number of
10.1.0.x Every Every 5 After Every > 90 97 3 Generated By
Minute Minutes Sample Database Server

Database Limits
Data Source
100*DECODE(initial_allocation, ' UNLIMITED', 0, current_utilization) != '0'
AND resource_name = 'sessions'
User Action
Increase the SESSIONS instance parameter. For XA environments, confirm that
SESSIONS is at least 2.73 * PROCESSES. For shared server environments, confirm that
SESSIONS is at least 1.1 * maximum number of connections.
User Limit Usage (%)

The LICENSE_MAX_SESSIONS initialization parameter specifies the maximum
number of concurrent user sessions allowed simultaneously.
This metric checks whether the number of users logged on is reaching the license limit.
If the percentage of the number of concurrent user sessions to the limit set in the
LICENSE_MAX_SESSIONS initialization parameter exceeds the values specified in the
threshold arguments, then a warning or critical alert is generated. If LICENSE_MAX_
SESSIONS is not explicitly set to a value, the test does not trigger.
Note: This metric is most useful when session licensing is enabled. Refer to the Oracle
Server Reference Manual for more information on LICENSE_MAX_SESSIONS and
LICENSE_MAX_USERS.
Metric Summary

Consecutive
8.1.7.4; Every 15 After Every > Not Defined Not Defined 3 %target% has
user limit.

Consecutive
Number of
Data Source
SELECT 'user' name,
100*DECODE(session_max, 0, 0, sessions_current/session_max) usage
FROM v$license
Database 2-23
Database Services
User Action
This typically indicates that the license limit for the database has been reached. The
user will need to acquire additional licenses, then increase LICENSE_MAX_
SESSIONS to reflect the new value.
Database Services
This metric category contains the database services metrics.
Service CPU Time (per user call) (microseconds)

This metric represents the average CPU time, in microseconds, for calls to a particular
database service.
Metric Summary

Consecutive
Number of
Multiple Thresholds
"Service Name" object.
If warning or critical threshold values are currently set for any "Service Name" object,
To specify or change warning or critical threshold values for each "Service Name"
object, use the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise
User Action
page.
Service Response Time (per user call) (microseconds)

This metric represents the average elapsed time, in microseconds, for calls to a
particular database service.
Metric Summary

Deferred Transactions


Consecutive
Number of
Multiple Thresholds
"Service Name" object.
If warning or critical threshold values are currently set for any "Service Name" object,
To specify or change warning or critical threshold values for each "Service Name"
User Action
page.
This metric category contains the metrics associated with this distributed database's
deferred transactions.
Deferred Transaction Count

Oracle uses deferred transactions to propagate data-level changes asynchronously
among master sites in an advanced replication system as well as from an updatable
snapshot to its master table.
This metric checks for the number of deferred transactions. An alert is generated if the
number of deferred transactions exceeds the value specified by the threshold
argument.
Metric Summary
Database 2-25

Consecutive
All Every 5 Not > 100 Not Defined 3 Number of deferred
Versions Minutes Uploaded transactions is
%value%.
Data Source
select count(*)
from sys.deftran
User Action
When the advanced replication facility pushes a deferred transaction to a remote site,
it uses a distributed transaction to ensure that the transaction has been properly
committed at the remote site before the transaction is removed for the queue at the
local site. If transactions are not being pushed to a given remote site, verify that the
destination for the transaction was correctly specified. If you specify a destination
database when calling DBMS_DEFER_SYS.SCHEDULE_EXECUTION using the
DBLINK parameter or DBMS_DEFER_SYS.EXECUTE using the DESTINATION
parameter, make sure the full database link is provided.
Wrong view destinations can lead to erroneous deferred transaction behavior. Verify
the DEFCALLEST and DEFTRANDEST views are the definitions from the
CATREPC.SQL not the ones from CATDEFER.SQL.
Deferred Transaction Error Count

Oracle uses deferred transactions to propagate data-level changes asynchronously
among master sites in an advanced replication system as well as from an updatable
snapshot to its master table. If a transaction is not successfully propagated to the
remote site, Oracle rolls back the transaction, logs the transaction in the
SYS.DEFERROR view in the remote destination database.
This metric checks for the number of transactions in SYS.DEFERROR view and raises
an alert if it exceeds the value specified by the threshold argument.
Metric Summary

Consecutive
All Every 5 Not > 0 Not Defined 3 Number of deferred
Versions Minutes Uploaded transactions with
errors is %value%.

Dump Area
Data Source
select count(*)
from sys.deferror
User Action
An error in applying a deferred transaction may be the result of a database problem,
such as a lack of available space in the table is to be updated or may be the result of an
unresolved insert, update or delete conflict. The SYS.DEFERROR view provides the ID
of the transaction that could not be applied. Use this ID to locate the queued calls
associated with the transaction. These calls are stored in the SYS.DEFCALL view. You
can use the procedures in the DBMS_DEFER_QUERY package to determine the
arguments to the procedures listed in the SYS.DEFCALL view.
Dump Area
The metrics in this metric category check for the percentage of used space of the dump
destination devices.
Dump Area Directory

This metric is the directory represented by this metric index's dump destination.
Each server and background process can write to an associated trace file to log
messages and errors.
Background processes and the ALERT file are written to the destination specified by
BACKGROUND_DUMP_DEST. Trace files for server processes are written to the
destination specified by USER_ DUMP_DEST.
Metric Summary

Data Source
data from v$parameter
User Action
Verify the device specified in the initialization parameters BACKGROUND_DUMP_
DEST and USER_DUMP_DEST are set up properly for archiving.
If the BACKGROUND_DUMP_DEST and USER_DUMP_DEST initialization
parameters are set up correctly and this metric triggers, then free up more space in the
destination specified by the dump destination parameters.
Dump Area Used (%)

This metric returns the percentage of used space of the dump area destinations.
If the space used is more than the threshold value given in the threshold arguments,
then a warning or critical alert is generated.
Database 2-27
Dump Area
Metric Summary

Consecutive
All Every 15 After Every > 95 Not Defined 1 %value%%% of
Versions Minutes 4 Samples %dumpType%
dump area is used.
Multiple Thresholds
"Type of Dump Area" object.
If warning or critical threshold values are currently set for any "Type of Dump Area"
To specify or change warning or critical threshold values for each "Type of Dump
Area" object, use the Edit Thresholds page. See the Editing Thresholds topic in the
Data Source
Calculated using the UNIX df -k command.
■ Critical threshold: Percentage of free space threshold for critical alert.
■ Warning threshold: Percentage of free space threshold for warning alert.
User Action
Dump Area Used (KB)

This metric represents the total space used (in KB) on the device containing the dump
Metric Summary

Data Source

Dump Area
User Action
Free Dump Area (KB)

Each server and background process can write to an associated trace file in order to log
messages and errors. Background processes and the ALERT file are written to the
destination specified by BACKGROUND_DUMP_DEST.
Trace files for server processes are written to the destination specified by USER_
DUMP_DEST.
This metric checks for available free space on these dump destination devices. If the
space available is less than the threshold value given in the threshold arguments, then
Metric Summary

Consecutive
All Every 15 After Every < 2000 Not Defined 1 %value% free KB
Versions Minutes 4 Samples remains in
%dumpType%
dump area.
Multiple Thresholds
"Type of Dump Area" object.
If warning or critical threshold values are currently set for any "Type of Dump Area"
To specify or change warning or critical threshold values for each "Type of Dump
Area" object, use the Edit Thresholds page. See the Editing Thresholds topic in the
Data Source
User Action
Database 2-29
Efficiency

Total Dump Area (KB)

This metric represents the total space (in KB) available on the device containing the
dump destination directory.
Metric Summary

Data Source
User Action
Efficiency
This metric category contains the metrics that have traditionally been considered to
represent the efficiency of some resource. Interpreting the wait interface is generally
accepted as a much more accurate approach to measuring efficiency, and is
recommended as an alternative to these hit ratios.
Buffer Cache Hit (%)

This metric represents the data block buffer cache efficiency, as measured by the
percentage of times the data block requested by the query is in memory.
Effective use of the buffer cache can greatly reduce the I/O load on the database. If the
buffer cache is too small, frequently accessed data will be flushed from the buffer
cache too quickly which forces the information to be re-fetched from disk. Since disk
access is much slower than memory access, application performance will suffer. In
addition, the extra burden imposed on the I/O subsystem could introduce a bottleneck
at one or more devices that would further degrade performance.
This test checks the percentage of buffer requests that were already in buffer cache. If
the value is less than or equal to the threshold values specified by the threshold
arguments, and the number of occurrences exceeds the value specified in the "Number
of Occurrences" parameter, then a warning or critical alert is generated.
Metric Summary

Efficiency


Consecutive
8.1.7.4; Every 5 After Every < Not Defined Not Defined 2 Buffer cache hit ratio
9.0.1.x; Minutes Sample is %value%%%.
9.2.0.x

Consecutive
Number of
10.1.0.x Every Every 5 After Every < Not Not 2 Generated By
Data Source
((DeltaLogicalGets - (DeltaPhysicalReads - DeltaPhysicalReadsDirect)) /
DeltaLogicalGets) * 100 where:
■ DeltaLogicalGets: difference in 'select value from v$sysstat where name='session
logical reads' ' between sample end and start
■ DeltaPhysicalReads: difference in 'select value from v$sysstat where
name='physical reads' ' between sample end and start
■ DeltaPhysicalReadsDirect: difference in 'select value from v$sysstat where
name='physical reads direct' ' between sample end and start (Oracle8i)
User Action
A low buffer cache hit ratio means that the server must often go to disk to retrieve the
buffers required to satisfy a query. The queries that perform the most physical reads
lower the numerical value of this statistic. Typically queries that perform full table
scans force large amounts of buffers into the cache, aging out other buffers that may be
required by other queries later. The Top Sessions page sorted by Physical Reads will
show the sessions performing the most reads and through further drilldown their
associated queries can be identified. Similarly, the Top SQL page sorted by Physical
Reads shows which SQL statements are performing the most physical reads. The
statements performing the most I/O should be looked at for tuning.
The difference between the two is that the Top Sessions chart shows the sessions that
are responsible for the physical reads at any given moment. The Top SQL view shows
all SQL that is still in the cache. The top statement may not be executing currently, and
thus not responsible for the current poor buffer cache hit ratio.
If the queries seem to be well tuned, the size of the buffer cache also determines how
often buffers need to be fetched from disk. The DB_BLOCK_BUFFERS initialization
parameter determines the number of database buffers available in the buffer cache. It
is one of the primary parameters that contribute to the total memory requirements of
the SGA on the instance. The DB_BLOCK_BUFFERS parameter, together with the DB_
BLOCK_SIZE parameter, controls the total size of the buffer cache. Since DB_BLOCK_
Database 2-31
Efficiency
SIZE can only be specified when the database is first created, normally the size of the
buffer cache size is controlled using the DB_BLOCK_BUFFERS parameter.
Consider increasing the DB_BLOCK_BUFFERS initialization parameter to increase the
size of the buffer cache. This increase allows the Oracle Server to keep more
information in memory, thus reducing the number of I/O operations required to do an
equivalent amount of work using the current cache size.
CPU Usage (per second)

This metric represents the CPU usage per second by the database processes, measured
in hundredths of a second. A change in the metric value may occur because of a
change in either workload mix or workload throughput being performed by the
database. Although there is no 'correct' value for this metric, it can be used to detect a
change in the operation of a system. For example, an increase in Database CPU usage
from 500 to 750 indicates that the database is using 50% more CPU. ('No correct value'
means that there is no single value that can be applied to any database. The value is a
characteristic of the system and the applications running on the system.)
Metric Summary

Consecutive
Number of
User Action
View the latest Automatic Database Diagnostic Monitor (ADDM) report. ADDM can
help to identify database operations that are consuming CPU. ADDM reports are
available from a number of locations including the Database Home page and Advisor
Central.
CPU Usage (per transaction)

This metric represents the average CPU usage per transaction expressed as a number
of seconds of CPU time. A change in this metric can occur either because of changing
workload on the system, such as the addition of a new module, or because of a change
in the way that the workload is performed in the database, such as changes in the plan
for a SQL statement. The threshold for this metric should be set based on the actual
values observed on your system.
Metric Summary

Efficiency

Consecutive
Number of
User Action
View the latest Automatic Database Diagnostic Monitor (ADDM) report. ADDM will
provide information about which operations are using the CPU resources.
Cursor Cache Hit (%)

This metric represents the percentage of soft parses satisfied within the session cursor
cache.
Metric Summary

Consecutive
Number of
Data Source
session cursor cache hits / (parse count (total) - parse count (hard))
User Action
page.
Data Dictionary Hit (%)

This metric represents dictionary cache efficiency as measured by the percentage of
requests against the dictionary data that were already in memory. It is important to
determine whether the misses on the data dictionary are actually affecting the
performance of the Oracle Server. The shared pool is an area in the SGA that contains
the library cache of shared SQL requests, the dictionary cache, and the other cache
structures that are specific to a particular instance configuration.
Misses on the data dictionary cache are to be expected in some cases. Upon instance
startup, the data dictionary cache contains no data, so any SQL statement issued is
likely to result in cache misses. As more data is read into the cache, the likelihood of
cache misses should decrease. Eventually the database should reach a steady state in
which the most frequently used dictionary data is in the cache. At this point, very few
Database 2-33
Efficiency
cache misses should occur. To tune the cache, examine its activity only after your
application has been running.
This test checks the percentage of requests against the data dictionary that were found
in the Shared Pool. If the value is less than or equal to the threshold values specified by
the threshold arguments, and the number of occurrences exceeds the value specified in
the "Number of Occurrences" parameter, then a warning or critical alert is generated.
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every < Not Defined Not Defined 2 Data dictionary hit
9.0.1.x; Minutes Sample ratio is %value%%%.
9.2.0.x

Consecutive
Number of
Data Source
(Gets/Misses) * 100 where:
■ Misses: select sum(getmisses) from v$rowcache
■ Gets: select sum(gets) from v$rowcache
User Action
If the percentage of gets is below %90 to %85, consider increasing SHARED_POOL_
SIZE to decrease the frequency in which dictionary data is being flushed from the
shared pool to make room for new data. To increase the memory available to the cache,
increase the value of the initialization parameter SHARED_POOL_SIZE.
Database CPU Time (%)

This metric represents the percentage of database call time that is spent on the CPU.
Although there is no 'correct' value for this metric, it can be used to detect a change in
the operation of a system, for example, a drop in Database CPU time from 50% to 25%.
('No correct value' means that there is no single value that can be applied to any
database. The value is a characteristic of the system and the applications running on
the system.)

Efficiency
Metric Summary

Consecutive
Number of
User Action
Investigate the change is CPU usage by using Automatic Database Diagnostic Monitor
(ADDM). ADDM reports are available from a number of locations including the
Database Home page and Advisor Central. Examine the report for increased time
spent in wait events.
Library Cache Hit (%)

This metric represents the library cache efficiency, as measured by the percentage of
times the fully parsed or compiled representation of PL/SQL blocks and SQL
statements are already in memory.
The shared pool is an area in the SGA that contains the library cache of shared SQL
requests, the dictionary cache and the other cache structures that are specific to a
particular instance configuration.
The shared pool mechanism can greatly reduce system resource consumption in at
least three ways: Parse time is avoided if the SQL statement is already in the shared
pool.
Application memory overhead is reduced, since all applications use the same pool of
shared SQL statements and dictionary resources.
I/O resources are saved, since dictionary elements that are in the shared pool do not
require access.
If the shared pool is too small, users will consume additional resources to complete a
database operation. For library cache access, the overhead is primarily the additional
CPU resources required to re-parse the SQL statement.
This test checks the percentage of parse requests where cursor already in cache If the
value is less than or equal to the threshold values specified by the threshold
Metric Summary
Database 2-35
Efficiency

Consecutive
8.1.7.4; Every 5 After Every < Not Defined Not Defined 2 Library cache hit
9.0.1.x; Minutes Sample ratio is %value%%%.
9.2.0.x

Consecutive
Number of
Data Source
(DeltaPinHits / DeltaPins) * 100 where:
■ DeltaPinHits: difference in 'select sum(pinhits) from v$librarycache' between
sample end and start
■ DeltaPins: difference in 'select sum(pins) from v$librarycache' between sample end
and start
User Action
The Top Sessions page sorted by Hard Parses lists the sessions incurring the most hard
parses. Hard parses occur when the server parses a query and cannot find an exact
match for the query in the library cache. You can avoid hard parses by sharing SQL
statements efficiently. The use of bind variables instead of literals in queries is one
method to increase sharing.
By showing you which sessions are incurring the most hard parses, this page can
identify the application or programs that are the best candidates for SQL rewrites.
Also, examine SQL statements that can be modified to optimize shared SQL pool
memory use and avoid unnecessary statement reparsing. This type of problem is
commonly caused when similar SQL statements are written which differ in space,
case, or some combination of the two. You may also consider using bind variables
rather than explicitly specified constants in your statements whenever possible.
The SHARED_POOL_SIZE initialization parameter controls the total size of the shared
pool. Consider increasing the SHARED_POOL_SIZE to decrease the frequency in
which SQL requests are being flushed from the shared pool to make room for new
requests.
To take advantage of the additional memory available for shared SQL areas, you may
also need to increase the number of cursors permitted per session. You can increase
this limit by increasing the value of the initialization parameter OPEN_CURSORS.
Library Cache Miss (%)

This metric represents the percentage of parse requests where the cursor is not in the
cache.

Efficiency
Metric Summary

Consecutive
Number of
Data Source
1 - pinhits / pins
User Action
page.
Parallel Execution Downgraded (per second)

Number of times per second parallel execution was requested and the degree of
parallelism was reduced because of insufficient parallel execution servers.
Metric Summary

Consecutive
10.1.0.x Every 5 After Every < Not Defined Not Defined 2 Not Defined
Minutes Sample
Data Source
(parallel operations downgraded 1 to 25 percent
+ parallel operations downgraded 25 to 50 percent
+ parallel operations downgraded 75 to 99 percent)
/ time
User Action
page.
Database 2-37
Efficiency
Parallel Execution Downgraded (per transaction)

Number of times per transaction parallel execution was requested and the degree of
parallelism was reduced because of insufficient parallel execution servers.
Metric Summary

Consecutive
Minutes Sample
Data Source
/ transactions
User Action
page.
Parallel Execution Downgraded 25% or more (per second)

parallelism was reduced to 25% and more because of insufficient parallel execution
servers.
Metric Summary

Consecutive
Number of
Data Source

Efficiency

/ time
User Action
page.
Parallel Execution Downgraded 25% or more (per transaction)

servers.
Metric Summary

Consecutive
Minutes Sample
Data Source
/ transactions
User Action
page.

servers.
Metric Summary
Database 2-39
Efficiency

Consecutive
Number of
Data Source
(+ parallel operations downgraded 50 to 75 percent
/ time
User Action
page.

parallelism was reduced to 50% or more because of insufficient parallel execution
servers.
Metric Summary

Consecutive
Minutes Sample
Data Source
/ transactions
User Action
page.

Efficiency

servers.
Metric Summary

Consecutive
Number of
Data Source
(parallel operations downgraded 75 to 99 percent)
/ time
User Action
page.

servers.
Metric Summary

Consecutive
Minutes Sample
Data Source
(parallel operations downgraded 75 to 99 percent)
/ transactions
Database 2-41
Efficiency
User Action
page.
Parallel Execution Downgraded to Serial (per second)

Number of times per second parallel execution was requested but execution was serial
because of insufficient parallel execution servers.
Metric Summary

Consecutive
Number of
Data Source
parallel operations downgraded to serial / time
User Action
page.
Parallel Execution Downgraded to Serial (per transaction)

Number of times per transaction parallel execution was requested but execution was
serial because of insufficient parallel execution servers.
Metric Summary

Consecutive
Minutes Sample

Efficiency
Data Source
parallel operations downgraded to serial / transactions
User Action
page.
PGA Cache Hit (%)

This metric represents the total number of bytes processed in the PGA versus the total
number of bytes processed plus extra bytes read/written in extra passes.
Metric Summary

Consecutive
Number of
User Action
page.
Redo Log Allocation Hit (%)

Redo log entries contain a record of changes that have been made to the database
block buffers. The log writer (LGWR) process writes redo log entries from the log
buffer to a redo log file. The log buffer should be sized so that space is available in the
log buffer for new entries, even when access to the redo log is heavy. When the log
buffer is undersized, user process will be delayed as they wait for the LGWR to free
space in the redo log buffer.
The redo log buffer efficiency, as measured by the hit ratio, records the percentage of
times users did not have to wait for the log writer to free space in the redo log buffer.
This metric monitors the redo log buffer hit ratio (percentage of success) against the
values specified by the threshold arguments. If the number of occurrences is smaller
than the values specified, then a warning or critical alert is generated.
Metric Summary
Database 2-43
Efficiency

Consecutive
8.1.7.4; Every 5 After Every < Not Defined Not Defined 2 Redo log allocation
9.0.1.x; Minutes Sample hit ratio is
9.2.0.x %value%%%.

Consecutive
Number of
Data Source
100 * (redo_entries_delta - redo_space_requests_delta)
/redo_entries_delta
where:
■ redo_enties_delta = difference between "SELECT value FROM v$sysstat
WHERE name = 'redo entries'" at the beginning and ending of the interval
■ redo_space_requests_delta = difference between "SELECT value FROM
v$sysstat WHERE name = 'redo log space requests'" at the
beginning and ending of the interval
User Action
The LOG_BUFFER initialization parameter determines the amount of memory that is
used when buffering redo entries to the redo log file.
Consider increasing the LOG_BUFFER initialization parameter in order to increase the
size of the redo log buffer. Redo log entries contain a record of the changes that have
been made to the database block buffers. The log writer process (LGWR) writes redo
log entries from the log buffer to a redo log. The redo log buffer should be sized so
space is available in the log buffer for new entries, even when access to the redo log is
heavy.
Note: For Oracle Management Agent release 9i, this metric has been obsoleted. It is
recommended that you use the Redo NoWait Ratio metric. This metric is kept for
backward compatibility with older versions of the Management Agent.
Response Time (per transaction)

This metric represents the time spent in database operations per transaction. It is
derived from the total time that user calls spend in the database (DB time) and the
number of commits and rollbacks performed. A change in this value indicates that
either the workload has changed or that the database's ability to process the workload
has changed because of either resource constraints or contention.
Metric Summary

Efficiency


Consecutive
Number of
User Action
page. Changes in the response time per transaction will appear as increased time spent
in the database, either on CPU or in wait events and ADDM will report the sources of
contention for both hardware and software resources.
Row Cache Miss Ratio (%)

This metric represents the percentage of row cache miss ratio.
Metric Summary

Consecutive
Number of
User Action
page.
Sorts in Memory (%)

This metric represents the sort efficiency as measured by the percentage of times sorts
were performed in memory as opposed to going to disk.
For best performance, most sorts should occur in memory because sorts to disks are
less efficient. If the sort area is too small, extra sort runs will be required during the
sort operation. This increases CPU and I/O resource consumption.
This test checks the percentage of sorts performed in memory rather than to disk. If the
Database 2-45
Efficiency
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every < Not Defined Not Defined 2 %value%%% of sorts
9.0.1.x; Minutes Sample are performed in
9.2.0.x memory.

Consecutive
Number of
Data Source
(DeltaMemorySorts / (DeltaDiskSorts + DeltaMemorySorts)) * 100 where:
■ DeltaMemorySorts: difference in 'select value from v$sysstat where name='sorts
(memory)'' between sample end and start
■ DeltaDiskSorts: difference in 'select value from v$sysstat where name='sorts
(disk)'' between sample end and start
User Action
The sessions that are performing the most sorts should be identified such that the SQL
they are executing can be further identified. The sort area sizes for the database may be
sized correctly, and the application SQL may be performing unwanted or excessive
sorts. The sessions performing the most sorts are available through the Top Sessions
page sorted by Disk Sorts.
Further drilldown into the session performing the most disk sorts with the Current
SQL page shows you the SQL statement responsible for the disk sorts.
The Top SQL page sorted by Sorts provides a mechanism to quickly display the SQL
statements in the cache, presented in sorted order by their number sort operations.
This is an alternative to viewing a sort of current sessions. It allows you to view sort
activity via SQL statements and contains cumulative statistics for all executions of that
statement.
If excessive sorts are taking place on disk and the queries are correct, consider
increasing the SORT_AREA_SIZE initialization parameter to increase the size of the
sort area. A larger sort area allows the Oracle Server to maintain sorts in memory,
reducing the number of I/O operations required to do an equivalent amount of work
using the current sort area size.

Global Cache Statistics

This metric category contains the metrics associated with global cache statistics.
Global Cache Average Convert Time (centi-seconds)

This metric represents the average convert time, measured in hundredths of a second.
Metric Summary

Consecutive
9.0.1.x; Every 5 After Every > 8 10 1 Global cache
9.2.0.x Minutes 3 Samples converts time is
%value% cs.
Data Source
global cache convert time * 10 / global cache converts
User Action
page.
Global Cache Average CR Block Request Time (centi-seconds)

This metric represents the average time, measured in hundredths of a second, that CR
block was received.
Metric Summary

Consecutive
9.0.1.x; Every 5 After Every > 3 5 1 Global cache CR
9.2.0.x Minutes 3 Samples Block request time is
%value% cs.
Database 2-47

Consecutive
Number of
Minute Minutes 3 Samples Database Server
Data Source
global cache CR block receive time * 10 / global cache current blocks received
User Action
page.
Global Cache Average Current Block Request Time (centi-seconds)

This metric represents the average time, measured in hundredths of a second, to get a
current block.
Metric Summary

Consecutive
9.0.1.x; Every 5 After Every > 3 5 1 Global cache Current
9.2.0.x Minutes 3 Samples Block request time is
%value% cs.

Consecutive
Number of
Minute Minutes 3 Samples Database Server
Data Source
global cache current block send time * 10 / global cache current blocks served
User Action
Specific to your site.

Global Cache Average Get Time (centi-seconds)

This metric represents the average get time, measured in hundredths of a second.
Metric Summary

Consecutive
9.0.1.x; Every 5 After Every > 3 6 1 Global cache gets
9.2.0.x Minutes 3 Samples time is %value% cs.
Data Source
global cache get time * 10 / global cache gets
User Action
page.
Global Cache Blocks Corrupt

This metric represents the number of blocks that encountered a corruption or
checksum failure during interconnect over the user-defined observation period.
Metric Summary

Consecutive
9.0.1.x; Every 5 After Every > Not Defined Not Defined 1* Total global cache
9.2.0.x Minutes 3 Samples blocks corrupt is
%value%.
Database 2-49

Consecutive
Number of
10.1.0.x Every Every 5 After Every > Not Not 1* Generated By
Minute Minutes 3 Samples Defined Defined Database Server
Data Source
global cache blocks corrupted
User Action
page.
Global Cache Blocks Lost

This metric represents the number of global cache blocks lost over the user-defined
observation period.
Metric Summary

Consecutive
9.0.1.x; Every 5 After Every > Not Defined Not Defined 1* Total global cache
9.2.0.x Minutes 3 Samples block lost is
%value%.

Consecutive
Number of
10.1.0.x Every Every 5 After Every > Not Not 1* Generated By
Minute Minutes 3 Samples Defined Defined Database Server
Data Source
global cache blocks lost

Idle Events
User Action
page.
Idle Events
The following is a list of the Idle Events.
■ ARCH random i/o
■ ARCH sequential i/o
■ KXFX: execution message dequeue - Slaves
■ LGWR random i/o
■ LGWR sequential i/o
■ LGWR wait for redo copy
■ Null event
■ PL/SQL lock timer
■ PX Deq Credit: need buffer
■ PX Deq: Execute Reply
■ PX Deq: Execution Msg
■ PX Deq: Index Merge Close
■ PX Deq: Index Merge Execute
■ PX Deq: Index Merge Reply
■ PX Deq: Join ACK
■ PX Deq: Msg Fragment
■ PX Deq: Par Recov Change Vector
■ PX Deq: Par Recov Execute
■ PX Deq: Par Recov Reply
■ PX Deq: Parse Reply
■ PX Deq: Table Q Normal
■ PX Deq: Table Q Sample
■ PX Deq: Txn Recovery Reply
■ PX Deq: Txn Recovery Start
■ PX Deque wait
■ PX Idle Wait
■ Queue Monitor Shutdown Wait
■ Queue Monitor Slave Wait
■ Queue Monitor Wait
■ RFS random i/o
■ RFS sequential i/o
Database 2-51
Idle Events
■ RFS write
■ SQL*Net message from client
■ SQL*Net message from dblink
■ STREAMS apply coord waiting for slave message
■ STREAMS apply coord waiting for some work to finish
■ STREAMS apply slave idle wait
■ STREAMS capture process filter callback wait for ruleset
■ STREAMS fetch slave waiting for txns
■ WMON goes to sleep
■ async disk IO
■ client message
■ control file parallel write
■ control file sequential read
■ control file single write
■ db file single write
■ db file parallel write
■ dispatcher timer
■ gcs log flush sync
■ gcs remote message
■ ges reconfiguration to start
■ ges remote message
■ io done
■ jobq slave wait
■ lock manager wait for remote message
■ log file parallel write
■ log file sequential read
■ log file single write
■ parallel dequeue wait
■ parallel recovery coordinator waits for cleanup of slaves
■ parallel query dequeue
■ parallel query idle wait - Slaves
■ pipe get
■ pmon timer
■ queue messages
■ rdbms ipc message
■ recovery read
■ single-task message

Invalid Objects by Schema
■ slave wait
■ smon timer
■ statement suspended, wait error to be cleared
■ unread message
■ virtual circuit
■ virtual circuit status
■ wait for activate message
■ wait for transaction
■ wait for unread message on broadcast channel
■ wait for unread message on multiple broadcast channels
■ wakeup event for builder
■ wakeup event for preparer
■ wakeup event for reader
■ wakeup time manager
Invalid Objects
This metric category contains the metrics associated with invalid objects.
Total Invalid Object Count

This metric represents the total invalid object count.
Metric Summary

Consecutive
All Every 24 Not > Not Defined Not Defined 1 %value% object(s)
Versions Hours Uploaded are invalid in the
database.
User Action
Invalid Objects by Schema

This metric category contains the metrics that represent the number of invalid objects
in each schema.
Database 2-53
Recovery Area
Owner's Invalid Object Count

This metric represents the invalid object count by owner.
Metric Summary

Consecutive
All Every 24 Not > 2 Not Defined 1 %value% object(s)
Versions Hours Uploaded are invalid in the
%owner% schema.
Multiple Thresholds
"Invalid Object Owner" object.
If warning or critical threshold values are currently set for any "Invalid Object Owner"
To specify or change warning or critical threshold values for each "Invalid Object
Owner" object, use the Edit Thresholds page. See the Editing Thresholds topic in the
Data Source
For each metric index:
select count(1)
User Action
View the status of the database objects in the schema identified by the Invalid Object
Owner metric. Recompile objects as necessary.
Recovery Area
This metric category contains the recovery area metrics.
Recovery Area Free Space (%)

This metric represents the recovery area free space as a percentage.
Metric Summary

10.1.0.x Every 15 Minutes

Response
User Action
page.
Response
This metric category contains the metrics that represent the responsiveness of the
Oracle Server, with respect to a client.
State
This metric represents the state of the database.
Metric Summary

Consecutive
All Every 5 After Every CONTAINS MOUNTED Not Defined 1 The database status
Versions Minutes Sample is %value%.
User Action
Status
This metric checks whether a new connection can be established to a database. If the
maximum number of users is exceeded or the listener is down, this test is triggered.
Metric Summary

Consecutive
All Every 5 After Every = Not Defined 0 1 Failed to connect to
Versions Minutes Sample database instance:
%oraerr%.
Database 2-55
Session Suspended
Data Source
Perl returns 1 when a connection can be made to the database (using Management
Agent monitoring connection details), 0 otherwise.
User Action
Check the status of the listener to make sure it is running on the node where the event
was triggered. If the listener is running, check to see if the number of users is at the
session limit. Note: The choice of user credentials for the Probe metric should be
considered. If the preferred user has the RESTRICED SESSION privilege, the user will
be able to connect to a database even if the LICENSE_MAX_SESSIONS limit is
reached.
User Logon Time (msec)

This metric represents the amount of time the agent takes to make a connection to the
database, measured in milliseconds.
Metric Summary

Consecutive
All Every 5 After Every > 1000 Not Defined 6 User logon time is
Versions Minutes Sample %value% msecs.
Data Source
Number of milliseconds (as measured in the Perl script) to connect to the database.
User Action
Session Suspended
This metric category contains the metrics that represent the number of resumable
sessions that are suspended due to some correctable error.
Session Suspended by Data Object Limitation

This metric represents the session suspended by data object limitation.
User Action
page.

SGA Pool Wastage
Session Suspended by Quota Limitation

This metric represents the session suspended by quota limitation.
User Action
page.
Session Suspended by Rollback Segment Limitation

This metric represents the session suspended by rollback segment limitation.
User Action
page.
Session Suspended by Tablespace Limitation

This metric represents the session suspended by tablespace limitation.
User Action
page.
SGA Pool Wastage

This metric category contains the metrics that represent the percentage of the various
pools in the SGA that are being wasted.
Java Pool Free (%)

This metric represents the percentage of the Java Pool that is currently marked as free.
Metric Summary

Consecutive
8.1.7.4; Every 15 After Every < Not Defined Not Defined 2 %value%%% of the
9.0.1.x; Minutes Sample Java pool is free.
9.2.0.x
10.1.0.x Every 15 After Every < Not Defined Not Defined 2 %value%%% of the
Minutes Sample Java pool is free.
Database 2-57
SGA Pool Wastage
Data Source
((Free/Total)*100) where
■ Free: select sum(decode(name,'free memory',bytes)) from v$sgastat where pool =
'java pool'
■ Total: select sum(bytes) from v$sgastat where pool = 'java pool'
User Action
If this pool size is too small, the database JVM (Java Virtual Machine) may not have
sufficient memory to satisfy future calls, leading potentially to unexpected database
request failures.
Large Pool Free (%)

This metric represents the percentage of the Large Pool that is currently marked as
free.
Metric Summary

Consecutive
9.0.1.x; Minutes Sample large pool is free.
9.2.0.x
10.1.0.x Every 15 After Every < Not Defined Not Defined 2 %value%%% of the
Minutes Sample large pool is free.
Data Source
((Free/Total)*100) where
■ Free: select sum(decode(name,'free memory',bytes)) from v$sgastat where pool =
'large pool'
■ Total: select sum(bytes) from v$sgastat where pool = 'large pool'
User Action
Consider enlarging the large pool or utilizing it more sparingly. This reduces the
possibility of large memory areas competing with the library cache and dictionary
cache for available memory in the shared pool.
Shared Pool Free (%)

This metric represents the percentage of the Shared Pool that is currently marked as
free.
This test checks the percentage of Shared Pool that is currently free. If the value is less
than or equal to the threshold values specified by the threshold arguments, and the

Snapshot Too Old
number of occurrences exceeds the value specified in the "Number of Occurrences"

parameter, then a warning or critical alert is generated.
Metric Summary

Consecutive
9.0.1.x; Minutes Sample shared pool is free.
9.2.0.x

Consecutive
Number of
Data Source
((Free/Total)*100) where:
■ free: select sum(decode(name,'free memory',bytes)) from v$sgastat where pool =
'shared pool'
■ total: select sum(bytes) from v$sgastat where pool = 'shared pool'
User Action
If the percentage of Free Memory in the Shared Pool rises above 50%, too much
memory has been allocated to the shared pool. This extra memory could be better
utilized by other applications on the machine. In this case the size of the Shared Pool
should be decreased. This can be accomplished by modifying the shared_pool_size
initialization parameter.
Snapshot Too Old

This metric category contains the snapshot too old metrics.
Snapshot Too Old due to Rollback Segment Limit

This metric represents the snapshot too old because of the rollback segment limit.
User Action
page.
Database 2-59
SQL Response Time
Snapshot Too Old due to Tablespace Limit

This metric represents the snapshot too old because of the tablespace limit.
User Action
page.
SQL Response Time

This metric category contains the metrics used to approximate the responsiveness of
SQL.
SQL Response Time (%)

SQL Response Time is the average elapsed time per execution of a representative set of
SQL statements, relative to a baseline. It is expressed as a percentage.
This metric is unavailable in versions 8.1.7 and earlier.
Metric Summary

Consecutive
All Every 5 After Every > 500 Not Defined 4 SQL response time is
Versions Minutes Sample %value%%% of
baseline.
Data Source
PL/SQL packaged procedure mgmt_response.get_metric_curs
User Action
If the SQL Response Time is less than 100%, then SQL statements are taking less time
to execute when compared to the baseline. Response Time greater than 100% indicates
that the database is not performing well when compared to the baseline.
SQL Response Time is a percentage of the baseline, not a simple percentage. So, for
example, 100% of baseline means the SQL Response Time is the same as the baseline.
200% of baseline means the SQL Response Time is two times slower than the baseline.
50% of baseline means SQL Response Time is two times faster than baseline. A
warning threshold of 200% indicates that the database is two times slower than the
baseline, while a critical threshold of 500% indicates the database is 5 times slower
than the baseline.
Representative statements are selected when two V$SQL snapshots are taken. All
calculations are based on the deltas between these two snapshots. First, the median
elapsed_time/execution for all statements that were executed in the time interval

Suspended Session
between the two snapshots are calculated. Then all statements that have an elapsed_
time/execution > median elapsed_time/execution are taken, and the top
25 most frequently executed statements are displayed.
Pre-requisites for Monitoring SQL Response Time Some tables and a PL/SQL package must
be installed on the monitored database. This can be done by going to the database
targets page and pressing the Configure button for your database. If a database has not
been configured, the message "Not configured" will be displayed for SQL Response
Time.
Configuring the Baseline The baseline is configured on demand, automatically. The first
time the agent calls the stored procedure to get the value of the metric, a snapshot of
V$SQL is taken. The second time, another snapshot is taken. Then the representative
statements are picked and stored in a table. The next time the agent requests the value
of the metric, we are able to calculate and return the relative SQL response time.
Because of baseline configuration, there will be a delay between the time the database
is configured and the value of the metric is displayed. During this period, the message
"Not available" will be displayed for SQL Response Time.
Enterprise Manager will automatically configure the baseline against which SQL
Response Time will be compared. However, in order for the SQL Response Time
metric to be truly representative, the DBA must reconfigure the baseline at a time
when the load on the database is typical.
To reconfigure the baseline, click on the link titled "Compared to Baseline" located next
to the SQL Response Time value on the Database Home Page. The SQL statements
used for tracking the SQL Response Time and baseline values are displayed. Click
Reset Baseline. This clears the list of statements and the baseline values. Enterprise
Manager will then automatically reconfigure the baseline within minutes.
If the database was lightly loaded at the time the baseline was taken, then the metric
can indicate that the database is performing poorly under typical load when such is
not the case. In this case, the DBA must reset the baseline. If the DBA has never
manually reset the baseline, then the metric value will not be representative.
Suspended Session
This metric category contains the metrics that represent the number of resumable
sessions that are suspended due to some correctable error.
Suspended Session Count

This metric represents the number of resumable sessions currently suspended in the
database.
Metric Summary
Database 2-61
System Response Time Per Call

Consecutive
9.0.1.x; Every 5 Not > 0 Not Defined 1 %value% session(s)
9.2.0.x Minutes Uploaded are suspended.
Data Source
select count(*)
from v$resumable
where status = 'SUSPENDED' and
enabled = 'YES'
User Action
Query the v$resumable view to see what the correctable errors are that are causing the
suspension. The way to correct each error depends on the nature of the error.
System Response Time Per Call

This metric category contains the system response time metrics.
System Response Time (centi-seconds)

This metric represents the average time taken for each call (both user calls and
recursive calls) within the database. A change in this value indicates that either the
workload has changed or that the database's ability to process the workload has
changed because of either resource constraints or contention.
Metric Summary

Consecutive
10.1.0.x Every 15 After Every > Not Defined Not Defined 1 Not Defined
Minutes Sample
User Action
page.
System Sessions Waiting

This metric category contains the metrics that represent the number of sessions
waiting.

Tablespaces Full
Waiting Session Count

This metric represents the number of sessions waiting at the sample time.
Metric Summary

Consecutive
8.1.7.4; Every After Every > Not Defined Not Defined 3 %value% sessions
9.0.1.x; Minute Sample are waiting.
9.2.0.x
Data Source
select count(*)
from v$session_wait
where wait_time = 0 and
event not in IdleEvents
See the Idle Events section in this chapter.
User Action
When this count is high, the system is doing more waiting than anything else.
Evaluate the various types of wait activity using the real-time and historical
performance monitoring capabilities of Enterprise Manager.
Tablespaces Full
The metrics in this metric category check for the amount of space used by the
tablespaces. If the percentage of used space is greater than the values specified in the
threshold setting, then a critical or warning alert is generated.
Tablespace Space Used (%)

As segments within a tablespace grow, the free space within that tablespace decreases.
Should free space become insufficient, the creation of new segments or the extension of
existing segments will fail.
This metric checks for the total free space in the tablespace specified by the Tablespace
name. If the percentage of used space is greater than the values specified in the
threshold arguments, then a warning or critical alert is generated.
Metric Summary
Database 2-63
Tablespaces Full

Consecutive
8.1.7.4; Every 30 After Every > 85 97 1 Tablespace
9.0.1.x; Minutes Sample [%name%] is
9.2.0.x [%value% percent]
full

Consecutive
Number of
10.1.0.x Every 10 Every 30 After Every > 85 97 1 Generated By
Minutes Minutes Sample Database Server
Multiple Thresholds
"Tablespace Name" object.
If warning or critical threshold values are currently set for any "Tablespace Name"
To specify or change warning or critical threshold values for each "Tablespace Name"
Data Source
(TotalUsedSpace / MaximumSize) * 100 where:
■ TotalUsedSpace: total used space in MB of tablespace
■ MaximumSize: maximum size (in MB) of the tablespace. The maximum size is
determined by looping through the tablespace's data files, as well as additional
free space on the disk that would be available for the tablespace should a data file
autoextend.
For additional information about the data source, refer to the fullTbsp.pl Perl script
located in the sysman/admin/scripts directory.
User Action
Perform one of the following:
■ Increase the size of the tablespace by enabling automatic extension for one of its
existing data files, manually resizing one of its existing data files. or adding a new
data file.
■ If the tablespace is suffering from tablespace free space fragmentation problems,
consider reorganizing the entire tablespace.
■ Relocate segments to another tablespace thus increasing the free space in this
tablespace.
■ Run the Segment Advisor on that tablespace.

Tablespaces With Problem Segments
Tablespaces Full (dictionary managed)

This metric category contains the metrics associated with tablespaces full.
Tablespace Space Used (%) (dictionary managed)

This metric represents the tablespace space used as a percentage.
Metric Summary

Consecutive
10.1.0.x Every 30 After Every > 85 97 1 Tablespace
Minutes Sample [%name%] is
[%value% percent]
full
Multiple Thresholds
User Action
page.

The metrics in this metric category check for the following:
■ The largest chunk-free space in the tablespace. If any table, index, cluster, or
rollback segment within the tablespace cannot allocate one additional extent, then
an alert is generated.
■ Whether any of the segments in the tablespace are approaching their maximum
extents. If, for any segment, the maximum number of extents minus the number of
existing extents is less than 2, then an alert is generated.
Only the tablespaces with problem segments are returned as results.
Database 2-65
Segments Approaching Maximum Extents

Segments which are nearing the upper limit of maximum extents.
Metric Summary

All Versions Every 24 Hours
Data Source
The first 10 segments names which are approaching their MaxExtent in the tablespace.
User Action
If possible, increase the value of the segment's MAXEXTENTS storage parameter.
Otherwise, rebuild the segment with a larger extent size ensuring the extents within a
segment are the same size by specifying STORAGE parameters where NEXT=INITIAL
and PCTINCREASE = 0.
For segments that are linearly scanned, choose an extent size that is a multiple of the
number of blocks read during each multiblock read. This will ensure that the Oracle
multiblock read capability is used efficiently.
Segments Approaching Maximum Extents Count

This metric checks for segments which are nearing the upper limit of the number of
maximum extents. If the number of segments is greater than the values specified in the
threshold arguments, then a warning or critical alert is generated.
Metric Summary

Consecutive
All Every 24 After Every > 0 Not Defined 1 %value% segments
Versions Hours Sample in %name%
tablespace
approaching max
extents.
Multiple Thresholds

Data Source
Number of segments for which the maximum number of extents minus the number of
existing extents is less than 2.
For additional information about the data source, refer to the problemTbsp.pl Perl
script located in the sysman/admin/scripts directory.
User Action
If possible, increase the value of the segment's MAXEXTENTS storage parameter.
Otherwise, rebuild the segment with a larger extent size ensuring the extents within a
segment are the same size by using a locally managed tablespace. In the case of a
dictionary managed tablespace, specify STORAGE parameters where NEXT=INITIAL
and PCTINCREASE = 0.
Segments Not Able to Extend

Segments which cannot allocate an additional extent.
Metric Summary

Data Source
The first 10 segments names which cannot allocate an additional extent in the
tablespace.
User Action
data file.
Segments Not Able to Extend Count

This metric checks for segments which cannot allocate an additional extent. If the
number of segments is greater than the values specified in the threshold arguments,
Metric Summary
Database 2-67
Throughput


Consecutive
All Every 24 After Every > 0 Not Defined 1 %value% segments
Versions Hours Sample in %name%
tablespace unable to
extend.
Multiple Thresholds
Data Source
After checking for the largest chunk free space in the tablespace, this is the number of
segments which cannot allocate an additional extent.
For additional information about the data source, refer to the problemTbsp.pl Perl
script located in the sysman/admin/scripts directory.
User Action
data file.
■ Relocate segments to another tablespace thus increasing the free space in this
tablespace.
Throughput
This metric category contains the metrics that represent rates of resource consumption,
or throughput.
All Sessions
This metric represents the number of users logged on at the sampling time.
Metric Summary

Throughput

8.1.7.4; 9.0.1.x; 9.2.0.x Every 5 Minutes
Data Source
SELECT value
FROM v$sysstat
WHERE name = ’logons current’;
User Action
BG Checkpoints (per second)

This metric represents the BG checkpoints per second.
Metric Summary

Consecutive
Number of
User Action
Branch Node Splits (per second)

Number of times per second an index branch block was split because of the insertion
of an additional value.
Metric Summary

Consecutive
Number of
Database 2-69
Throughput
Data Source
branch node slits / time
User Action
page.
Branch Node Splits (per transaction)

Number of times per transaction an index branch block was split because of the
insertion of an additional value.
Metric Summary

Consecutive
Number of
Data Source
branch node splits / transaction
User Action
page.
Consistent Read Blocks Created (per second)

This metric represents the number of current blocks per second cloned to create
consistent read (CR) blocks.
Metric Summary

Throughput

Consecutive
Number of
Data Source
CR blocks created / time
User Action
page.
Consistent Read Blocks Created (per transaction)

This metric represents the number of current blocks per transaction cloned to create
consistent read (CR) blocks.
Metric Summary

Consecutive
Number of
Data Source
CR blocks created / transactions
User Action
page.
Consistent Read Changes (per second)

This metric represents the number of times per second a user process has applied
rollback entries to perform a consistent read on the block.
Metric Summary
Database 2-71
Throughput


Consecutive
Number of
Data Source
consistent changes / time
User Action
page.
Consistent Read Changes (per transaction)

This metric represents the number of times per transaction a user process has applied
rollback entries to perform a consistent read on the block.
Metric Summary

Consecutive
Number of
Data Source
consistent changes / transactions
User Action
page.
Consistent Read Gets (per second)

This metric represents the number of times per second a consistent read was requested
for a block.

Throughput
Metric Summary

Consecutive
Number of
Data Source
consistent gets / time
User Action
page.
Consistent Read Gets (per transaction)

This metric represents the number of times per transaction a consistent read was
requested for a block.
Metric Summary

Consecutive
Number of
Data Source
consistent gets / transactions
User Action
page.
Database 2-73
Throughput
Consistent Read Undo Records Applied (per second)

This metric represents the number of undo records applied for consistent read per
second.
Metric Summary

Consecutive
Number of
Data Source
current blocks converted for CR / time
User Action
page.
Consistent Read Undo Records Applied (per transaction)

This metric represents the consistent read undo records applied per transaction.
Metric Summary

Consecutive
Number of
User Action
page.

Throughput
Cumulative Logons (per second)

This metric represents the number of logons per second during the sample period.
This test checks the number of logons that occurred per second during the sample
period. If the value is greater than or equal to the threshold values specified by the
threshold arguments, and the number of occurrences exceeds the value specified in the
"Number of Occurrences" parameter, then a warning or critical alert is generated.
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > 100 Not Defined 2 Cumulative logon
9.0.1.x; Minutes Sample rate is %value%/sec.
9.2.0.x

Consecutive
Number of
10.1.0.x Every Every 5 After Every >= 100 Not 2 Generated By
Minute Minutes Sample Defined Database Server
Data Source
DeltaLogons / Seconds where:
■ DeltaLogons: difference in 'select value from v$sysstat where name='logons
cumulative'' between end and start of sample period
■ Seconds: number of seconds in sample period
User Action
A high logon rate may indicate that an application is inefficiently accessing the
database. Database logon's are a costly operation. If an application is performing a
logon for every SQL access, that application will experience poor performance as well
as affect the performance of other applications on the database. If there is a high logon
rate try to identify the application that is performing the logons to determine if it could
be redesigned such that session connections could be pooled, reused or shared.
Cumulative Logons (per transaction)

This metric represents the number of logons per transaction during the sample period.
The value of this statistic will be zero if there have not been any write or update
transactions committed or rolled back during the last sample period. If the bulk of the
Database 2-75
Throughput
activity to the database is read only, the corresponding "per second" metric of the same
name will be a better indicator of current performance.
This test checks the number of logons that occurred per transaction. If the value is
greater than or equal to the threshold values specified by the threshold arguments, and
the number of occurrences exceeds the value specified in the "Number of Occurrences"
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Cumulative logon
9.0.1.x; Minutes Sample rate is
9.2.0.x %value%/transactio
n.

Consecutive
Number of
Data Source
DeltaLogons / Transactions where:
■ DeltaLogons: difference in 'select value from v$sysstat where name='logons
cumulative'' between end and start of sample period
■ Transactions: number of transactions in sample period
User Action
A high logon rate may indicate that an application is inefficiently accessing the
database. Database logon's are a costly operation. If an application is performing a
logon for every SQL access, that application will experience poor performance as well
as affect the performance of other applications on the database. If there is a high logon
rate try to identify the application that is performing the logons to determine if it could
be redesigned such that session connections could be pooled, reused or shared.
Database Block Changes (per second)

This metric represents the total number of changes per second that were part of an
update or delete operation that were made to all blocks in the SGA.

Throughput
Metric Summary

Consecutive
Number of
Data Source
db block changes / time
User Action
page.
Database Block Changes (per transaction)

This metric represents the total number of changes per transaction that were part of an
update or delete operation that were made to all blocks in the SGA.
Metric Summary

Consecutive
Number of
Data Source
db block changes / transactions
User Action
page.
Database Block Gets (per second)

This metric represents the number of times per second a current block was requested.
Database 2-77
Throughput
Metric Summary

Consecutive
Number of
Data Source
db block gets / time
User Action
page.
Database Block Gets (per transaction)

This metric represents the number of times per transaction a current block was
requested.
Metric Summary

Consecutive
Number of
Data Source
db block gets / transactions
User Action
page.

Throughput
DBWR Checkpoints (per second)

This metric represents the number of times, per second, during this sample period
DBWn was asked to scan the cache and write all blocks marked for a checkpoint.
The database writer process (DBWn) writes the contents of buffers to datafiles. The
DBWn processes are responsible for writing modified (dirty) buffers in the database
buffer cache to disk.
When a buffer in the database buffer cache is modified, it is marked dirty. The primary
job of the DBWn process is to keep the buffer cache clean by writing dirty buffers to
disk. As user processes dirty buffers, the number of free buffers diminishes. If the
number of free buffers drops too low, user processes that must read blocks from disk
into the cache are not able to find free buffers. DBWn manages the buffer cache so that
user processes can always find free buffers.
When the Oracle Server process cannot find a clean reusable buffer after scanning a
threshold of buffers, it signals DBWn to write. When this request to make free buffers
is received, DBWn writes the least recently used (LRU) buffers to disk. By writing the
least recently used dirty buffers to disk, DBWn improves the performance of finding
free buffers while keeping recently used buffers resident in memory. For example,
blocks that are part of frequently accessed small tables or indexes are kept in the cache
so that they do not need to be read in again from disk. The LRU algorithm keeps more
frequently accessed blocks in the buffer cache so that when a buffer is written to disk,
it is unlikely to contain data that may be useful soon.
Additionally, DBWn periodically writes buffers to advance the checkpoint that is the
position in the redo log from which crash or instance recovery would need to begin.
This test checks the number of times DBWR was asked to advance the checkpoint. If
the value is greater than or equal to the threshold values specified by the threshold
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 DBWR checkpoint
9.0.1.x; Minutes Sample rate is %value%/sec.
9.2.0.x

Consecutive
Number of
Database 2-79
Throughput
Data Source
DeltaCheckpoints / Seconds where:
■ DeltaCheckpoints: difference in 'select value from v$sysstat where name='DBWR
checkpoints'' between sample end and start
User Action
A checkpoint tells the DBWR to write out modified buffers to disk. This write
operation is different from the make free request in that the modified buffers are not
marked as free by the DBWR process. Dirty buffers may also be written to disk at this
time and freed.
The write size is dictated by the _db_block_checkpoint_batch parameter. If writing,
and subsequently waiting for checkpoints to complete is a problem, the checkpoint
completed event displays in the Top Waits page sorted by Time Waited or the Sessions
Waiting for this Event page.
If the database is often waiting for checkpoints to complete you may want to increase
the time between checkpoints by checking the init.ora parameter db_block_
checkpoint_batch: select name, value, is default from v$parameter where name = db_
block_checkpoint_batch. The value should be large enough to take advantage of
parallel writes. The DBWR uses a write batch that is calculated like this: (db_files * db_
file_simultaneous_writes)/2 The write_batch is also limited by two other factors:
■ A port specific limit on the numbers of I/Os (compile time constant).
■ 1/4 of the number of buffers in the SGA.
The db_block_checkpoint_batch is always smaller or equal to the _db_block_write_
batch. You can also consider enabling the check point process.
Enqueue Deadlocks (per second)

This metric represents the number of times per second that a process detected a
potential deadlock when exchanging two buffers and raised an internal, restartable
error.
Metric Summary

Consecutive
Number of
Data Source
enqueue deadlocks / time

Throughput
User Action
page.
Enqueue Deadlocks (per transaction)

This metric represents the number of times per transaction that a process detected a
potential deadlock when exchanging two buffers and raised an internal, restartable
error.
Metric Summary

Consecutive
Number of
Data Source
enqueue deadlocks / transactions
User Action
page.
Enqueue Requests (per second)

This metric represents the total number of table or row locks acquired per second.
Metric Summary

Consecutive
Number of
Database 2-81
Throughput
Data Source
enqueue requests / time
User Action
page.
Enqueue Requests (per transaction)

This metric represents the total number of table or row locks acquired per transaction.
Metric Summary

Consecutive
Number of
Data Source
enqueue requests / transactions
User Action
page.
Enqueue Timeout (per second)

This metric represents the total number of table and row locks (acquired and
converted) per second that time out before they could complete.
Metric Summary

Throughput

Consecutive
Number of
Data Source
enqueue timeouts / time
User Action
page.
Enqueue Timeout (per transaction)

This metric represents the total number of table and row locks (acquired and
converted) per transaction that timed out before they could complete.
Metric Summary

Consecutive
Number of
Data Source
enqueue timeouts / transactions
User Action
page.
Enqueue Waits (per second)

This metric represents the total number of waits per second that occurred during an
enqueue convert or get because the enqueue get was deferred.
Metric Summary
Database 2-83
Throughput


Consecutive
Number of
Data Source
enqueue waits / time
User Action
page.
Enqueue Waits (per transaction)

This metric represents the total number of waits per transaction that occurred during
an enqueue convert or get because the enqueue get was deferred.
Metric Summary

Consecutive
Number of
Data Source
enqueue waits / transaction
User Action
page.
Executes (per second)

This metric represents the rate of SQL command executions over the sampling
interval.

Throughput
Metric Summary

8.1.7.4; 9.0.1.x; 9.2.0.x Every 5 Minutes
Data Source
DeltaExecutions / Seconds where:
■ DeltaExecutions: difference in 'select value from v$sysstat where name='execute
count'' between end and start of sample period.
User Action
Executes Performed without Parses (%)

This metric represents the percentage of statement executions that do not require a
corresponding parse. A perfect system would parse all statements once and then
execute the parsed statement over and over without reparsing. This ratio provides an
indication as to how often the application is parsing statements as compared to their
overall execution rate. A higher number is better.
This test checks the percentage of executes that do not require parses. If the value is
less than or equal to the threshold values specified by the threshold arguments, and
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every < Not Defined Not Defined 2 Only %value%%% of
9.0.1.x; Minutes Sample executes are
9.2.0.x performed without
parses.

Consecutive
Number of
Database 2-85
Throughput
Data Source
((DeltaExecuteCount - (DeltaParseCountTotal)) / DeltaExecuteCount) * 100 where:
■ DeltaParseCountTotal: difference in 'select value from v$sysstat where
name='parse count (total)'' between sample end and start
■ DeltaExecuteCount: difference in 'select value from v$sysstat where
name='execute count'' between sample end and start
User Action
An execute to parse ratio of less than 70% indicates that the application may be
parsing statements more often than it should. Reparsing the statement, even if it is a
soft parse, requires a network round trip from the application to the database, as well
as requiring the processing time to locate the previously compiled statement in the
cache. Reducing network round trips and unnecessary processing improves
application performance.
Use the Top Sessions page sorted by Parses to identify the sessions responsible for the
bulk of the parse activity within the database. Start with these sessions to determine
whether the application could be modified to make more efficient use of its cursors.
Full Index Scans (per second)

This metric represents the number of fast full index scans per second.
Metric Summary

Consecutive
Number of
Data Source
index fast full scans (full) / time
User Action
page.
Full Index Scans (per transaction)

This metric represents the number of fast full index scans per transaction.

Throughput
Metric Summary

Consecutive
Number of
Data Source
index fast full scans (full) / transactions
User Action
page.
Hard Parses (per second)

This metric represents the number of hard parses per second during this sample
period. A hard parse occurs when a SQL statement has to be loaded into the shared
pool. In this case, the Oracle Server has to allocate memory in the shared pool and
parse the statement.
Each time a particular SQL cursor is parsed, this count will increase by one. There are
certain operations that will cause a SQL cursor to be parsed. Parsing a SQL statement
breaks it down into atomic steps, which the optimizer will evaluate when generating
an execution plan for the cursor.
This test checks the number of parses of statements that were not already in the cache.
If the value is greater than or equal to the threshold values specified by the threshold
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Hard parse rate is
9.0.1.x; Minutes Sample %value%/sec.
9.2.0.x
Database 2-87
Throughput

Consecutive
Number of
Data Source
DeltaParses / Seconds where:
■ DeltaParses: difference in 'select value from v$sysstat where name='parse count
(hard)'' between end and start of sample period
User Action
If there appears to be excessive time spent parsing, evaluate SQL statements to
determine those that can be modified to optimize shared SQL pool memory use and
avoid unnecessary statement reparsing. This type of problem is commonly caused
when similar SQL statements are written which differ in space, case, or some
combination of the two. You may also consider using bind variables rather than
explicitly specified constants in your statements whenever possible.
The Top Sessions page sorted by Hard Parses will show you which sessions are
incurring the most hard parses. Hard parses happen when the server parses a query
and cannot find an exact match for the query in the library cache. Hard parses can be
avoided by sharing SQL statements efficiently. The use of bind variables instead of
literals in queries is one method to increase sharing.
By showing you which sessions are incurring the most hard parses, this page may lead
you to the application or programs that are the best candidates for SQL rewrites.
Also, examine SQL statements which can be modified to optimize shared SQL pool
requests.
Hard Parses (per transaction)

This metric represents the number of hard parses per second during this sample
period. A hard parse occurs when a SQL statement has to be loaded into the shared
pool. In this case, the Oracle Server has to allocate memory in the shared pool and
parse the statement.
certain operations which will cause a SQL cursor to be parsed. Parsing a SQL

Throughput
statement breaks it down into atomic steps which the optimizer will evaluate when
generating an execution plan for the cursor. The value of this statistic will be zero if
there have not been any write or update transactions committed or rolled back during
the last sample period. If the bulk of the activity to the database is read only, the
corresponding "per second" metric of the same name will be a better indicator of
current performance.
This test checks the number of hard parses per second during this sample period. If
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Hard parse rate is
9.0.1.x; Minutes Sample %value%/transactio
9.2.0.x n.

Consecutive
Number of
Data Source
DeltaParses / Transactions where:
(hard)'' between end and start of sample period
User Action
determine which can be modified to optimize shared SQL pool memory use and avoid
unnecessary statement reparsing. This type of problem is commonly caused when
similar SQL statements are written which differ in space, case, or some combination of
the two. You may also consider using bind variables rather than explicitly specified
constants in your statements whenever possible.
Database 2-89
Throughput
requests.
Leaf Node Splits (per second)

Number of times per second an index leaf node was split because of the insertion of an
additional value.
Metric Summary

Consecutive
Number of
Data Source
leaf node splits / time
User Action
page.
Leaf Node Splits (per transaction)

Number of times per transaction an index leaf node was split because of the insertion
of an additional value.

Throughput
Metric Summary

Consecutive
Number of
Data Source
leaf node splits / transactions
User Action
page.
Network Bytes (per second)

This metric represents the total number of bytes sent and received through the SQL
Net layer to and from the database.
This test checks the network read/write per second. If the value is greater than or
equal to the threshold values specified by the threshold arguments, and the number of
occurrences exceeds the value specified in the Number of Occurrences parameter, then
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Bytes transmitted via
9.0.1.x; Minutes Sample SQL*Net is
9.2.0.x %value%/sec.
Database 2-91
Throughput

Consecutive
Number of
Data Source
(DeltaBytesFromClient+DeltaBytesFromDblink+DeltaBytesToClient+DeltaBytesToDbli
nk) / Seconds where:
■ Delta Bytes From Client: difference in 'select s.value from v$sysstat s, visitation n
where n.name='bytes received via SQL*Net from client' and
n.statistic#=s.statistic#' between end and start of sample period
■ DeltaBytesFromClient: difference in 'select s.value from v$sysstat s, v$statname n
where n.name='bytes received via SQL*Net from dblink' and
n.statistic#=s.statistic#' between end and start of sample period
where n.name='bytes sent via SQL*Net to client' and n.statistic#=s.statistic#'
between end and start of sample period
where n.name='bytes sent via SQL*Net to dblink' and n.statistic#=s.statistic#'
User Action
This metric represents the amount of network traffic in and out of the database. This
number may only be useful when compared to historical levels to understand network
traffic usage related to a specific database.
Number of Transactions (per second)

This metric represents the total number of commits and rollbacks performed during
this sample period.
This test checks the number of commits and rollbacks performed during sample
period. If the value is greater than or equal to the threshold values specified by the
threshold arguments, and the number of occurrences exceeds the value specified in the
"Number of Occurrences" parameter, then a warning or critical alert is generated.
Metric Summary

Throughput

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Transaction rate is
9.2.0.x

Consecutive
Number of
10.1.0.x Every Every 5 After Every >= Not Not 2 Generated By
Data Source
DeltaCommits + DeltaRollbacks where:
■ DeltaCommits: difference of 'select value from v$sysstat where name='user
commits'' between sample end and start
■ DeltaRollbacks: difference of 'select value from v$sysstat where name='user
rollbacks'' between sample end and start
User Action
This statistic is an indication of how much work is being accomplished within the
database. A spike in the transaction rate may not necessarily be bad. If response times
stay close to normal, it means your system can handle the added load. Actually, a drop
in transaction rates and an increase in response time may be indicators of problems.
Depending upon the application, transaction loads may vary widely across different
times of the day.
Open Cursors (per second)

This metric represents the total number of cursors opened per second.
Metric Summary

Consecutive
Number of
Database 2-93
Throughput
Data Source
opened cursors cumulative / time
User Action
page.
Open Cursors (per transaction)

This metric represents the total number of cursors opened per transaction.
Metric Summary

Consecutive
Number of
Data Source
opened cursors cumulative / transactions
User Action
page.
Parse Failure Count (per second)

This metric represents the total number of parse failures per second.
Metric Summary

Consecutive
Number of

Throughput
Data Source
parse count (failures) / time
User Action
page.
Parse Failure Count (per transaction)

This metric represents the total number of parse failures per transaction.
Metric Summary

Consecutive
Number of
Data Source
parse count (failures) / transactions
User Action
page.
Physical Reads (per second)

This metric represents the number of data blocks read from disk per second during
this sample period. When a user performs a SQL query, Oracle tries to retrieve the data
from the database buffer cache (memory) first, then searches the disk if it is not already
in memory. Reading data blocks from disk is much more inefficient than reading the
data blocks from memory. The goal with Oracle should always be to maximize
memory utilization.
This test checks the data blocks read from disk per second. If the value is greater than
or equal to the threshold values specified by the threshold arguments, and the number
of occurrences exceeds the value specified in the "Number of Occurrences" parameter,
Metric Summary
Database 2-95
Throughput


Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Physical reads are
9.2.0.x

Consecutive
Number of
Data Source
DeltaPhysicalReads / Seconds where:
■ DeltaPhysicalReads: difference in 'select s.value from v$sysstat s, v$statname n
where n.name='physical reads' and n.statistic#=s.statistic#' between sample end
and start
User Action
Block reads are inevitable so the aim should be to minimize unnecessary IO. This is
best achieved by good application design and efficient execution plans. Changes to
execution plans can yield profound changes in performance. Tweaking at system level
usually only achieves percentage gains.
To view I/O on a per session basis to determine which sessions are responsible for
your physical reads, you should visit the Top Sessions page sorted by Physical Reads.
This approach allows you to identify problematic sessions and then drill down to their
current SQL statement and perform tuning from there.
To identify the SQL that is responsible for the largest portion of physical reads, visit
the Top SQL page sorted by Physical Reads. This page allows you to quickly
determine which SQL statements are the causing your I/O activity. From this display
you can view the full text of the SQL statement.
The difference between the two methods for identifying problematic SQL is that the
Top Sessions view displays sessions that are performing the most physical reads at the
moment. The Top SQL view displays the SQL statements that are still in the SQL cache
that have performed the most I/O over their lifetime. A SQL statement could show up
in the Top SQL view that is not currently being executed.
If the SQL statements are properly tuned and optimized, consider the following
suggestions. A larger buffer cache may help - test this by actually increasing DB_
BLOCK_BUFFERS. Do not use DB_BLOCK_LRU_EXTENDED_STATISTICS, as this
may introduce other performance issues. Never increase the SGA size if it may induce
additional paging or swapping on the system.

Throughput
A less obvious issue which can affect the I/O rates is how well data is clustered
physically. For example, assume that you frequently fetch rows from a table where a
column is between two values via an index scan. If there are 100 rows in each index
block then the two extremes are: 1.Each of the table rows is in a different physical
block (100 blocks need to be read for each index block). 2.The table rows are all located
in the few adjacent blocks (a handful of blocks need to be read for each index block).
Pre-sorting or reorganizing data can improve this situation in severe situations as well.
Physical Reads (per transaction)

This metric represents the number of disk reads per transaction during the sample
period. When a user performs a SQL query, Oracle tries to retrieve the data from the
database buffer cache (memory) first, then goes to disk if it is not in memory already.
Reading data blocks from disk is much more expensive than reading the data blocks
from memory. The goal with Oracle should always be to maximize memory
utilization.
This test checks the data blocks read from disk per transaction. If the value is greater
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Physical reads are
9.2.0.x n.

Consecutive
Number of
Data Source
DeltaReads / Transactions where:
Database 2-97
Throughput
■ DeltaReads: difference in 'select value from v$sysstat where name='physical reads''

User Action
Block reads are inevitable so the aim should be to minimize unnecessary IO. This is
best achieved by good application design and efficient execution plans. Changes to
execution plans can yield orders of magnitude changes in performance. Tweaking at
system level usually only achieves percentage gains.
To identify the SQL that is responsible for the largest portion of physical reads, visit
the Top SQL page sorted by Physical Reads. This view will allow you to quickly
determine which SQL statements are causing the I/O activity. From this display you
can view the full text of the SQL statement.
To view I/O on a per session basis to determine which sessions are responsible for
your physical reads, you can visit the Top Sessions page sorted by Physical Reads. This
approach allows you to identify problematic sessions and then drill down to their
current SQL statement to perform tuning.
If the SQL statements are properly tuned and optimized the following suggestions
may help. A larger buffer cache may help - test this by actually increasing DB_
BLOCK_BUFFERS and not by using DB_BLOCK_LRU_EXTENDED_STATISTICS.
Never increase the SGA size if it will induce additional paging or swapping on the
system.
A less obvious issue which can affect the I/Orates is how well data is clustered
physically. For example, assume that you frequently fetch rows from a table where a
column is between two values via an index scan. If there are 100 rows in each index
block then the two extremes are: 1. Each of the table rows is in a different physical
block (100 blocks need to be read for each index block). 2. The table rows are all
located in the few adjacent blocks (a handful of blocks need to be read for each index
block).
Pre-sorting or reorganizing data can help to tackle this in severe situations as well.
Physical Reads Direct (per second)

This metric represents the number of direct physical reads per second.
Metric Summary

Consecutive
Number of

Throughput
Data Source
physical reads direct / time
User Action
page.
Physical Reads Direct (per transaction)

This metric represents the number of direct physical reads per transaction.
Metric Summary

Consecutive
Number of
Data Source
physical reads direct / transactions
User Action
page.
Physical Reads Direct Lobs (per second)

This metric represents the number of direct large object (LOB) physical reads per
second.
Metric Summary
Database 2-99
Throughput

Consecutive
Number of
Data Source
physical reads direct (lob) / time
User Action
page.
Physical Reads Direct Lobs (per transaction)

This metric represents the number of direct large object (LOB) physical reads per
transaction.
Metric Summary

Consecutive
Number of
Data Source
physical reads direct (lob) / transactions
User Action
page.
Physical Writes (per second)

This metric represents the number of disk writes per second during the sample period.
This statistic represents the rate of database blocks written from the SGA buffer cached
to disk by the DBWR background process, and from the PGA by processes performing
direct writes.
This test checks the data blocks written disk per second. If the value is greater than or

Throughput
occurrences exceeds the value specified in the "Number of Occurrences" parameter,

Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Physical writes are
9.2.0.x

Consecutive
Number of
Data Source
DeltaWrites / Seconds where:
■ DeltaWrites: difference in 'select value from v$sysstat where name='physical
writes'' between end and start of sample period
User Action
Because this statistic shows both DBWR writes as well as direct writes by sessions, you
should view the physical writes directly to determine where the write activity is
actually occurring. If the physical writes direct value comprises a large portion of the
writes, then there are probably many sorts or writes to temporary tablespaces
occurring.
If the majority of the writes are not direct, they are being performed by the DBWR
writes process. This is only be a problem if log writer or redo waits are showing up in
the Sessions Waiting for this Event page or the Top Waits page sorted by Time Waited.
Physical Writes (per transaction)

This metric represents the number of disk writes per transaction during the sample
period.
The value of this statistic is zero if there have not been any write or update
name is a better indicator of current performance.
Database 2-101
Throughput
This test checks the data blocks written disk per transaction. If the value is greater than
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Physical writes are
9.2.0.x n.

Consecutive
Number of
Data Source
DeltaWrites / Transactions where:
■ DeltaWrites: difference in 'select value from v$sysstat where name='physical
User Action
Because this statistic shows both DBWR writes as well as direct writes by sessions, you
should view the physical writes directly to determine where the write activity is really
occurring. If the physical writes direct value comprises a large portion of the writes,
then there are likely many sorts or writes to temporary tablespaces that are occurring.
If the majority of the writes are not direct, they are being performed by the DBWR
writes process. This will typically only be a problem if log writer or redo waits are
showing up in the Sessions Waiting for this Event page or the Top Waits page sorted
by Time Waited.
Physical Writes Direct (per second)

This metric represents the number of direct physical writes per second.
Metric Summary

Throughput


Consecutive
Number of
Data Source
physical writes direct / time
User Action
detailed analysis, run ADDM from the Advisor Central on the Database Home page.
Physical Writes Direct (per transaction)

This metric represents the number of direct physical writes per transaction.
Metric Summary

Consecutive
Number of
Data Source
physical writes direct / transactions
User Action
page.
Physical Writes Direct Lobs (per second)

This metric represents the number of direct large object (LOB) physical writes per
second.
Database 2-103
Throughput
Metric Summary

Consecutive
Number of
Data Source
physical writes direct (lob) / time
User Action
page.
Physical Writes Direct Lobs (per transaction)

This metric represents the number of direct large object (LOB) physical writes per
transaction.
Metric Summary

Consecutive
Number of
Data Source
physical writes direct (lob) / transactions
User Action
page.

Throughput
Recursive Calls (per second)

This metric represents the number of recursive calls, per second during the sample
period.
Sometimes, to execute a SQL statement issued by a user, the Oracle Server must issue
additional statements. Such statements are called recursive calls or recursive SQL
statements. For example, if you insert a row into a table that does not have enough
space to hold that row, the Oracle Server makes recursive calls to allocate the space
dynamically if dictionary managed tablespaces are being used. Recursive calls are also
generated:
■ When data dictionary information is not available in the data dictionary cache and
must be retrieved from disk
■ In the firing of database triggers
■ In the execution of DDL statements
■ In the execution of SQL statements within stored procedures, functions, packages
and anonymous PL/SQL blocks
■ In the enforcement of referential integrity constraints
This test checks the number of recursive SQL calls per second. If the value is greater
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Recursive call rate is
9.2.0.x

Consecutive
Number of
Data Source
DeltaRecursiveCalls / Seconds where:
■ DeltaRecursiveCalls: difference in 'select value from v$sysstat where
name='recursive calls'' between end and start of sample period
Database 2-105
Throughput
User Action
If the Oracle Server appears to be making excessive recursive calls while your
application is running, determine what activity is causing these recursive calls. If you
determine that the recursive calls are caused by dynamic extension, either reduce the
frequency of extension by allocating larger extents or, if you are using Oracle8i,
considering taking advantage of locally managed tablespaces.
Recursive Calls (per transaction)

This metric represents the number of recursive calls, per second during the sample
period.
Sometimes, to execute a SQL statement issued by a user, the Oracle Server must issue
generated:
■ When data dictionary information is not available in the data dictionary cache and
This test checks the number of calls that result in changes to internal tables. If the value
is greater than or equal to the threshold values specified by the threshold arguments,
and the number of occurrences exceeds the value specified in the "Number of
Occurrences" parameter, then a warning or critical alert is generated.
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Recursive call rate is
9.2.0.x

Throughput

Consecutive
Number of
Data Source
DeltaRecursiveCalls / Transactions where:
name='recursive calls'' between end and start of sample period
User Action
If the Oracle Server appears to be making excessive recursive calls while your
application is running, determine what activity is causing these recursive calls. If you
determine that the recursive calls are caused by dynamic extension, either reduce the
frequency of extension by allocating larger extents or, if you are using Oracle8i,
considering taking advantage of locally managed tablespaces.
Redo Generated (per second)

This metric represents the amount of redo, in bytes, generated per second during this
sample period.
The redo log buffer is a circular buffer in the SGA that holds information about
changes made to the database. This information is stored in redo entries. Redo entries
contain the information necessary to reconstruct, or redo, changes made to the
database by INSERT, UPDATE, DELETE, CREATE, ALTER or DROP operations. Redo
entries can be used for database recovery if necessary.
This test checks the amount of redo in bytes generated per second. If the value is
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Redo generated is
9.2.0.x
Database 2-107
Throughput

Consecutive
Number of
Data Source
DeltaRedoSize / Seconds where:
■ DeltaRedoSize: difference in 'select value from v$sysstat where name='redo size''
User Action
used when redo entries are buffered to the redo log file.
Consider increasing the LOG_BUFFER initialization parameter to increase the size of
the redo log buffer should waiting be a problem. Redo log entries contain a record of
the changes that have been made to the database block buffers. The log writer process
(LGWR) writes redo log entries from the log buffer to a redo log. The redo log buffer
should be sized so space is available in the log buffer for new entries, even when
access to the redo log is heavy.
Redo Generated (per transaction)

This metric represents the amount of redo, in bytes, generated per transaction during
this sample period.
entries are used for database recovery, if necessary.
The value of this statistic is zero if there have been no write or update transactions
committed or rolled back during the last sample period. If the bulk of the activity to
the database is read only, the corresponding "per second" metric of the same name will
be a better indicator of current performance.
This test checks the amount of redo in bytes generated per transaction. If the value is
Metric Summary

Throughput

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Redo generated is
9.2.0.x n.

Consecutive
Number of
Data Source
DeltaRedoSize / DeltaTransactions where:
■ DeltaRedoSize: difference in 'select value from v$sysstat where name='redo size''
■ Transactions: difference in 'select value from v$sysstat where name = 'user
commits'' between end and start of sample period
User Action
Redo Writes (per second)

This metric represents the number redo write operations per second during this
sample period.
entries can be used for database recovery if necessary.
The log writer processes (LGWR) is responsible for redo log buffer management; that
is, writing the redo log buffer to a redo log file on disk.
This test checks the number of writes by LGWR to the redo log files per second. If the
value is greater than or equal to the threshold values specified by the threshold
Database 2-109
Throughput
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Redo write rate is
9.2.0.x

Consecutive
Number of
Data Source
DeltaRedoWrites / Seconds where:
■ DeltaRedoWrites: difference in 'select value from v$sysstat where name='redo
User Action
used when redo entries are buffered to the redo log file.
Should waiting be a problem, consider increasing the LOG_BUFFER initialization
parameter to increase the size of the redo log buffer. Redo log entries contain a record
of the changes that have been made to the database block buffers. The log writer
process (LGWR) writes redo log entries from the log buffer to a redo log. The redo log
buffer should be sized so space is available in the log buffer for new entries, even
when access to the redo log is heavy.
Redo Writes (per transaction)

This metric represents the number of redo write operations per second during this
sample period.
entries are used for database recovery, if necessary.
The log writer process (LGWR) is responsible for redo log buffer management; that is,
writing the redo log buffer to a redo log file on disk.

Throughput
This test checks the number of writes by LGWR to the redo log files per transaction. If
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Redo write rate is
9.2.0.x n.

Consecutive
Number of
Data Source
DeltaRedoWrites /(DeltaCommits+DeltaRollbacks) where:
■ DeltaRedoWrites: difference in 'select s.value from v$sysstat s, v$statname n where
n.name='redo writes' and n.statistic#=s.statistic#' between sample end and start
■ DeltaCommits: difference in 'select s.value from v$sysstat s, v$statname n where
n.name='user commits' and n.statistic#=s.statistic#' between sample end and
sample start
■ DeltaRollbacks: difference in 'select s.value from v$sysstat s, v$statname n where
n.name='user commits' and n.statistic#=s.statistic#' between sample end and
sample start
User Action
Database 2-111
Throughput
Rows Processed (per sort)

This metric represents the average number of rows per sort during this sample period.
This test checks the average number of rows per sort during sample period. If the
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Average sort size is
9.0.1.x; Minutes Sample %value% rows.
9.2.0.x

Consecutive
Number of
Data Source
(DeltaSortRows / (DeltaDiskSorts + DeltaMemorySorts)) * 100 where:
■ DeltaSortRows: difference in 'select value from v$sysstat where name='sorts
(rows)'' between sample end and start
■ DeltaMemorySorts: difference in 'select value from v$sysstat where name='sorts
(memory)'' between sample end and start
(disk)'' between sample end and start
User Action
This statistic displays the average number of rows that are being processed per sort.
The size provides information about the sort size of the database. This can help you to
determine the SORT_AREA_SIZE appropriately. If the rows per sort are high, you
should investigate the sessions and SQL performing the most sorts to see if those SQL
statements can be tuned to reduce the size of the sort sample set.
The sessions that are performing the most sorts should be identified, such that the SQL
sized correctly and the application SQL may be performing unwanted or excessive

Throughput
sorts. The sessions performing the most sorts are available through the Top Sessions
page sorted by Disk Sorts.
SQL page displays the SQL statement responsible for the disk sorts.
statements in the cache presented in sorted order by their number of sort operations.
This is an alternative to viewing the sort of current sessions. It allows you to view sort
activity via SQL statements and contains cumulative statistics for all executions of that
statement.
If excessive sorts are taking place on disk and the queries are correct, consider
sort area. A larger sort area allows the Oracle Server to keep sorts in memory, reducing
the number of I/O operations required to do an equivalent amount of work using the
current sort area size.
Scans on Long Tables (per second)

This metric represents the number of long table scans per second during sample
period. A table is considered 'long' if the table is not cached and if its high-water mark
is greater than 5 blocks.
This test checks the long table scans per second. If the value is greater than or equal to
the threshold values specified by the threshold arguments, and the number of
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Rate of scans on long
9.0.1.x; Minutes Sample tables is

Consecutive
Number of
Data Source
DeltaScans / Seconds where:
Database 2-113
Throughput
■ DeltaScans: difference in 'select value from v$sysstat where name='table scans

(long tables)'' between end and start of sample period
User Action
A table scan means that the entire table is being scanned record by record in order to
satisfy the query. For small tables that can easily be read into and kept in the buffer
cache this may be advantageous. But for larger tables this will force a lot of physical
reads and potentially push other needed buffers out of the cache. SQL statements with
large physical read and logical read counts are candidates for table scans. They can be
identified either through the Top SQL page sorted by Physical Reads, or through the
Top Sessions page sorted by Physical Reads, with a drilldown to the current SQL for a
session.
Scans on Long Tables (per transaction)

This metric represents the number of long table scans per transaction during sample
period. A table is considered 'long' if the table is not cached and if its high-water mark
is greater than 5 blocks.
This test checks the number of long table scans per transaction. If the value is greater
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Rate of scans on long
9.0.1.x; Minutes Sample tables is
n.

Consecutive
Number of

Throughput
Data Source
DeltaScans / Transactions where:
■ DeltaScans: difference in 'select value from v$sysstat where name='table scans
(long tables)'' between end and start of sample period
User Action
A table scan means that the entire table is being scanned record by record in order to
satisfy the query. For small tables that can easily be read into and kept in the buffer
cache this may be advantageous. But for larger tables this will force a lot of physical
reads and potentially push other needed buffers out of the cache. SQL statements with
large physical read and logical read counts are candidates for table scans. They can be
identified either through the Top SQL page sorted by Physical Reads, or through the
Top Sessions page sorted by Physical Reads, with a drilldown to the current SQL for a
session.
Session Logical Reads (per second)

This metric represents the number of logical reads per second during the sample
period. A logical read is a read request for a data block from the SGA. Logical reads
may result in a physical read if the requested block does not reside with the buffer
cache.
This test checks the logical(db block gets + consistent gets) reads per second. If the
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Session logical reads
9.0.1.x; Minutes Sample are %value%/sec.
9.2.0.x

Consecutive
Number of
Database 2-115
Throughput
Data Source
LogicalReads / Seconds where:
■ LogicalReads: difference in 'select value from v$sysstat where name='session
logical reads'' between end and start of sample period
User Action
Excessive logical reads, even if they do not result in physical reads, can still represent
an area that should be considered for performance tuning. Typically large values for
this statistic indicate that full table scans are being performed. To identify the SQL that
is performing the most logical reads (buffer gets), use the Top SQL page sorted by
Buffer Gets. This quickly identifies the SQL responsible for the bulk of the logical
reads. You can further investigate these SQL statements via drilldowns. Tuning these
SQL statements will reduce your buffer cache access.
Session Logical Reads (per transaction)

This metric represents the number of logical reads per transaction during the sample
period.
The value of this statistic is zero if there have not been any write or update
activity to the database is read only, the corresponding per second metric of the same
This test checks the logical (db block gets + consistent gets) reads per transaction. If the
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Session logical reads
9.0.1.x; Minutes Sample are
n.

Consecutive
Number of

Throughput
Data Source
DeltaReads / Transactions where:
■ DeltaReads: difference in 'select value from v$sysstat where name='session logical
reads'' between end and start of sample period
User Action
Excessive logical reads, even if they do not result in physical reads, can still represent
an area that should be considered for performance tuning. Typically large values for
this statistic indicate that full table scans are being performed. To identify the SQL that
is performing the most logical reads (buffer gets) use the Top SQL page sorted by
Buffer Gets. This quickly identifies the SQL responsible for the bulk of the logical
reads.
Soft Parse (%)

A soft parse is recorded when the Oracle Server checks the shared pool for a SQL
statement and finds a version of the statement that it can reuse.
This metric represents the percentage of parse requests where the cursor was already
in the cursor cache compared to the number of total parses. This ratio provides an
indication as to how often the application is parsing statements that already reside in
the cache as compared to hard parses of statements that are not in the cache.
This test checks the percentage of soft parse requests to total parse requests. If the
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every < Not Defined Not Defined 2 Only %value%%% of
9.0.1.x; Minutes Sample parses are soft
9.2.0.x parses.

Consecutive
Number of
Database 2-117
Throughput
Data Source
((DeltaParseCountTotal - DeltaParseCountHard) / DeltaParseCountTotal) * 100 where:
■ DeltaParseCountTotal: difference in 'select value from v$sysstat where
name='parse count (total)'' between sample end and start
■ DeltaParseCountHard: difference in 'select value from v$sysstat where
name='parse count (hard)'' between sample end and start
User Action
Soft parses consume less resources than hard parses, so the larger the value for this
item, the better. But many soft parses indicate the application is using SQL
inefficiently. Reparsing the statement, even if it is a soft parse, requires a network
round trip from the application to the database, as well as requiring the processing
time to locate the previously compiled statement in the cache. Reducing network
round trips and unnecessary processing will improve application performance.
If this metric value is below 80% you should look at the Top Sessions page sorted by
Hard Parses. This page lists the sessions that are currently performing the most hard
parses. Starting with these sessions and the SQL statements they are executing will
indicate which applications and corresponding SQL statements are being used
inefficiently.
If the metric is currently showing a high value, the expensive hard parses are not
occurring but the application can still be tuned by reducing the amount of soft parses.
Visit the Top SQL page sorted by Parses to identify the SQL statements that have been
most parsed. This will allow you to quickly identify SQL that is being re-parsed
unnecessarily. You should investigate these statements first for possible application
logic changes such that cursors are opened once, and executed or fetched from many
times.
Sorts to Disk (per second)

This metric represents the number of sorts going to disk per second for this sample
period. For best performance, most sorts should occur in memory, because sorts to
disks are expensive to perform. If the sort area is too small, extra sort runs will be
required during the sort operation. This increases CPU and I/O resource consumption.
This test checks the number of sorts performed to disk per second. If the value is
Metric Summary

Throughput

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 The rate of sorts to
9.0.1.x; Minutes Sample disk is

Consecutive
Number of
Data Source
DeltaDiskSorts / Seconds where:
(disk)'' between end and start of sample period
User Action
sized correctly, the application SQL may be performing unwanted or excessive sorts.
The sessions performing the most sorts are available through the Top Sessions sorted
by Disk Sorts page.
SQL page will show you the SQL statement responsible for the disk sorts.
This is an alternative to viewing sort of current sessions, it allows you to view sort
activity via SQL statements, and will contain cumulative statistics for all executions of
that statement.
If excessive sorts are taking place on disk, and the query's are correct, consider
sort area. A larger sort area will allow the Oracle Server to keep sorts in memory,
Sorts to Disk (per transaction)

This metric represents the number of sorts going to disk per transactions for this
sample period. For best performance, most sorts should occur in memory, because
sorts to disks are expensive to perform. If the sort area is too small, extra sort runs will
be required during the sort operation. This increases CPU and I/O resource
consumption.
Database 2-119
Throughput
This test checks the number of sorts performed to disk per transaction. If the value is
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 The rate of sorts to
9.0.1.x; Minutes Sample disk is
n.

Consecutive
Number of
Data Source
DeltaDiskSorts / Transactions where:
(disk)'' between end and start of sample period
User Action
sized correctly, the application SQL may be performing unwanted or excessive sorts.
The sessions performing the most sorts are available through the Top Sessions page
sorted by Disk Sorts.
SQL page will show you the SQL statement responsible for the disk sorts.
This is an alternative to viewing sort of current sessions, it allows you to view sort

Throughput
activity via SQL statements, and will contain cumulative statistics for all executions of
that statement.
If excessive sorts are taking place on disk, and the query's are correct, consider
sort area. A larger sort area will allow the Oracle Server to keep sorts in memory,
Total Index Scans (per second)

This metric represents the total number of index scans per second.
Metric Summary

Consecutive
Number of
Data Source
index scans kdiixs1 / time
User Action
page.
Total Index Scans (per transaction)

This metric represents the total number of index scans per transaction.
Metric Summary

Consecutive
Number of
Database 2-121
Throughput
Data Source
index scans kdiixsl / transactions
User Action
page.
Total Parses (per second)

This number reflects the total number of parses per second, both hard and soft. A hard
parse occurs when a SQL statement has to be loaded into the shared pool. In this case,
the Oracle Server has to allocate memory in the shared pool and parse the statement. A
soft parse is recorded when the Oracle Server checks the shared pool for a SQL
statement and finds a version of the statement that it can reuse.
generating an execution plan for the cursor.
This test checks the number of parse calls per second. If the value is greater than or
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Total parse rate is
9.2.0.x

Consecutive
Number of
Data Source
DeltaParses / Seconds where:
(total)'' between end and start of sample period

Throughput
User Action
requests.
Total Parses (per transaction)

This number reflects the total number of parses per transaction, both hard and soft. A
hard parse occurs when a SQL statement has to be loaded into the shared pool. In this
case, the Oracle Server has to allocate memory in the shared pool and parse the
statement. A soft parse is recorded when the Oracle Server checks the shared pool for a
SQL statement and finds a version of the statement that it can reuse.
generating an execution plan for the cursor.
This test checks the number of parse calls per transaction. If the value is greater than or
Metric Summary
Database 2-123
Throughput

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Total parse rate is
9.2.0.x n.

Consecutive
Number of
Data Source
DeltaParses / Transactions where:
(total)'' between end and start of sample period
User Action
requests.

Throughput
Total Table Scan (per second)

This metric represents the number of long and short table scans per second.
Metric Summary

Consecutive
Number of
Data Source
(table scans (long tables) + table scans (short tables)) / time
User Action
page.
Total Table Scan (per transaction)

This metric represents the long and short table scans per transaction.
Metric Summary

Consecutive
Number of
Data Source
(table scans (long tables) + table scans (short tables)) / transactions
User Action
page.
Database 2-125
Throughput
Total Table Scans (per second)

This metric represents the number of long and short table scans per second during the
sample period. A table is considered 'long' if the table is not cached and if its
high-water mark is greater than 5 blocks.
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Total table scan rate
9.0.1.x; Minutes Sample is %value%/sec.
9.2.0.x
Data Source
(DeltaLongScans + DeltaShortScans) / Seconds where:
■ DeltaLongScans: difference in 'select value from v$sysstat where name='table
scans (long tables)'' between end and start of sample period
■ DeltaShortScans: difference in 'select value from v$sysstat where name='table
scans (short tables)'' between end and start of sample period
■ DBA_index_fast_full_scans_full
User Action
A table scan indicates that the entire table is being scanned record-by-record in order
to satisfy the query. For small tables that can easily be read into and kept in the buffer
cache, this may be advantageous. But larger tables will force many physical reads and
potentially push other required buffers out of the cache. SQL statements with large
physical read and logical read counts are candidates for table scans. They can be
identified through two different methods. The Top Sessions page sorted by Physical
Reads displays sessions that are responsible for the current I/O activity. The Top SQL
page sorted by Physical Reads lists the SQL statements in the cache by the amount of
I/O they have performed. Some of these SQL statements may have high I/O numbers
but they may not be attributing to the current I/O load.
Total Table Scans (per transaction)

This metric represents the number of long and short table scans per transaction during
the sample period. A table is considered 'long' if the table is not cached and if its
high-water mark is greater than 5 blocks.
This test checks the number of long and short table scans per transaction. If the value
is greater than or equal to the threshold values specified by the threshold arguments,

Throughput
and the number of occurrences exceeds the value specified in the "Number of
Occurrences" parameter, then a warning or critical alert is generated.
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 Total table scan rate
9.0.1.x; Minutes Sample is
n.
Data Source
(DeltaLongScans + DeltaShortScans) / Transactions where:
■ DeltaLongScans: difference in 'select value from v$sysstat where name='table
scans (long tables)'' between end and start of sample period
■ DBA_index_fast_full_scans_full
User Action
A table scan indicates that the entire table is being scanned record-by-record in order
to satisfy the query. For small tables that can easily be read into and kept in the buffer
cache, this may be advantageous. But larger tables will force many physical reads and
potentially push other required buffers out of the cache. SQL statements with large
physical read and logical read counts are candidates for table scans. They can be
identified through two different methods. The Top Sessions page sorted by Physical
Reads displays sessions that are responsible for the current I/O activity. The Top SQL
page sorted by Physical Reads lists the SQL statements in the cache by the amount of
I/O they have performed. Some of these SQL statements may have high I/O numbers
but they may not be attributing to the current I/O load.
User Calls (%)

This metric represents the percentage of user calls to recursive calls.
Occasionally, to execute a SQL statement issued by a user, the Oracle Server must issue
generated:
Database 2-127
Throughput
When data dictionary information is not available in the data dictionary cache and
This test checks the percentage of user calls to recursive calls. If the value is less than
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every < Not Defined Not Defined 2 %value%%% of calls
9.0.1.x; Minutes Sample are user calls.
9.2.0.x

Consecutive
Number of
Data Source
(DeltaUserCalls/(DeltaRecursiveCalls + DeltaUserCalls)) * 100 where:
name='recursive calls'' between sample end and start
■ DeltaUserCalls: difference in 'select value from v$sysstat where name='user calls''
between sample end and start
User Action
A low value for this metric means that the Oracle Server is making a large number of
recursive calls. If the Oracle Server appears to be making excessive recursive calls
while your application is running, determine what activity is causing these recursive
calls. If you determine that the recursive calls are caused by dynamic extension, either
reduce the frequency of extension by allocating larger extents or, if you are using
Oracle8i, considering taking advantage of locally managed tablespaces.

Throughput
User Calls (per second)

This metric represents the number of logins, parses, or execute calls per second during
the sample period.
This test checks the number of logins, parses, or execute calls. If the value is greater
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 User call rate is
9.2.0.x

Consecutive
Number of
Data Source
DeltaUserCalls / Seconds where:
User Action
This statistic is a reflection of how much activity is going on within the database.
Spikes in the total user call rate should be investigated to determine which of the
underlying calls is actually increasing. Parse, execute and logon calls each signify
different types of user or application actions and should be addressed individually.
User Calls is an overall activity level monitor.
User Calls (per transaction)

This metric represents the number of logins, parses, or execute calls per transaction
during the sample period.
Database 2-129
Throughput
This test checks the number of logins, parses, or execute calls per second. If the value is
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 User call rate is
9.2.0.x n.

Consecutive
Number of
Data Source
DeltaUserCalls / Transactions where:
User Action
This statistic is a reflection of how much activity is going on within the database.
Spikes in the total user call rate should be investigated to determine which of the
underlying calls is actually increasing. Parse, execute and logon calls each signify
different types of user or application actions and should be addressed individually.
User Calls is an overall activity level monitor.
User Commits (per second)

This metric represents the number of user commits performed, per second during the
sample period. When a user commits a transaction, the redo generated that reflects the
changes made to database blocks must be written to disk. Commits often represent the
closest thing to a user transaction rate.
This test checks the number of user commits per second. If the value is greater than or

Throughput

Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 User commit rate is
9.2.0.x

Consecutive
Number of
Data Source
DeltaCommits / Seconds where:
■ DeltaCommits: difference in 'select value from v$sysstat where name='user
User Action
times of the day.
User Commits (per transaction)

This metric represents the number of user commits performed, per transaction during
the sample period. When a user commits a transaction, the redo generated that reflects
the changes made to database blocks must be written to disk. Commits often represent
the closest thing to a user transaction rate.
Database 2-131
Throughput
This test checks the number of user commits per transaction. If the value is greater
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 User commit rate is
9.2.0.x n.

Consecutive
Number of
Data Source
DeltaCommits / Transactions where:
■ DeltaCommits: difference in 'select value from v$sysstat where name='user
User Action
times of the day.
User Rollback Undo Records Applied (per second)

This metric represents the number of undo records applied to user-requested rollback
changes per second.
Metric Summary

Throughput


Consecutive
Number of
Data Source
(rollback changes - undo records applied) / time
User Action
page.
User Rollback Undo Records Applied (per transaction)

This metric represents the number of undo records applied to user-requested rollback
changes per transaction.
Metric Summary

Consecutive
Number of
Data Source
(rollback changes - undo records applied) / transactions
User Action
page.
User Rollbacks (per second)

This metric represents the number of times, per second during the sample period, that
users manually issue the ROLLBACK statement or an error occurred during a user's
transactions.
Database 2-133
Throughput
This test checks the number of rollbacks per second. If the value is greater than or
Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 User rollback rate is
9.2.0.x

Consecutive
Number of
Data Source
DeltaRollbacks / Seconds where:
■ DeltaRollbacks: difference in 'select value from v$sysstat where name='user
rollbacks'' between end and start of sample period
User Action
This value shows how often users are issuing the ROLLBACK statement or
encountering errors in their transactions. Further investigation should be made to
determine if the rollbacks are part of some faulty application logic or due to errors
occurring through database access.
User Rollbacks (per transaction)

This metric represents the number of times, per transaction during the sample period,
that users manually issue the ROLLBACK statement or an error occurred during a
user's transactions.
This test checks the Number of rollbacks per transaction. If the value is greater than or

User Audit

Metric Summary

Consecutive
8.1.7.4; Every 5 After Every > Not Defined Not Defined 2 User rollback rate is
9.2.0.x n.

Consecutive
Number of
Data Source
DeltaRollbacks / Transactions where:
■ DeltaRollbacks: difference in 'select value from v$sysstat where name='user
rollbacks'' between end and start of sample period
User Action
This value shows how often users are issuing the ROLLBACK statement or
encountering errors in their transactions. Further investigation should be made to
determine if the rollbacks are part of some faulty application logic or due to errors
occurring through database access.
User Audit
This metric category contains the metrics used to represent logons to the database by
audited users (such as SYS).
Audited User
This metric monitors specified database user connections. For example, an alert is
displayed when a particular database user connection, specified by the User name
filter argument, has been detected.
Database 2-135
User Audit
Metric Summary

Consecutive
All Every 15 Not = SYS Not Defined 1 User %value%
Versions Minutes Uploaded logged on from
%machine%.
Multiple Thresholds
"Username_Machine" object.
If warning or critical threshold values are currently set for any "Username_Machine"
To specify or change warning or critical threshold values for each "Username_
Machine" object, use the Edit Thresholds page. See the Editing Thresholds topic in the
Data Source
select username
User Action
User actions may vary depending on the user connection that is detected.
Audited User Host

This metric represents the host machine from which the audited user's logon
originated.
Metric Summary

Data Source
select machine
User Action
Review the access to the database from this client machine.

User Block
Audited User Session Count

This metric represents the number of logons the audited user has from a given
machine.
Metric Summary

Data Source
select count(username)
User Action
User Block
This metric category contains the metrics that tell to what extent, and how consistently,
a given session is blocking multiple other sessions.
Blocking Session Count

This metric signifies that a database user is blocking at least one other user from
performing an action, such as updating a table. An alert is generated if the number of
consecutive blocking occurrences reaches the specified value.
Note: The catblock.sql script needs to be run on the managed database prior to using
the User Blocks test. This script creates some additional tables, view, and public
synonyms that are required by the User Blocks test.
Metric Summary

Consecutive
8.1.7.4; Every 5 Not > 11 Not Defined 3 Session %sid%
9.0.1.x; Minutes Uploaded blocking %value%
9.2.0.x other sessions.
Database 2-137
User Defined Metrics

Consecutive
Number of
10.1.0.x Every Every 15 Not > 11 Not 3 Generated By
Minute Minutes Uploaded Defined Database Server
Multiple Thresholds
"Blocking Session ID" object.
If warning or critical threshold values are currently set for any "Blocking Session ID"
To specify or change warning or critical threshold values for each "Blocking Session
ID" object, use the Edit Thresholds page. See the Editing Thresholds topic in the
Data Source
SELECT SUM(num_blocked)
FROM (SELECT id1, id2, MAX(DECODE(block, 1, sid, 0)) blocking_sid,
SUM(DECODE(request, 0, 0, 1)) num_blocked
FROM v$lock
WHERE block = 1 OR request > 0
GROUP BY id1, id2)
GROUP BY blocking SID
User Action
Either have user who is blocking other users rollback the transaction, or wait until the
blocking transaction has been committed.

The UDM metric allows you to execute your own SQL statements. The data returned
by these SQL statements can be compared against thresholds and generate severity
alerts similar to alerts in predefined metrics.
User Defined Numeric Metric

Contains a value if the value type is NUMBER. Otherwise, the value is "", if the value
is STRING.
Data Source
SQL statement which can be either a Select statement or function that returns a single
scalar value (numeric or string)
User Action

Wait Bottlenecks
User Defined String Metric

Contains a value if the value type is STRING. Otherwise, the value is "", if the value is
NUMBER.
Data Source
SQL statement which can be either a Select statement or function that returns a single
scalar value (numeric or string)
User Action
Wait Bottlenecks
This metric category contains the metrics that approximate the percentage of time
spent waiting by user sessions. This approximation takes system-wide totals and
discounts the effects of sessions belonging to background processes.
Active Sessions Using CPU

This metric represents the active sessions using CPU.
Metric Summary

8.1.7.4; 9.0.1.x; 9.2.0.x Every Minute
User Action
Active Sessions Waiting: I/O

This metric represents the active sessions waiting for I/O.
Metric Summary

8.1.7.4; 9.0.1.x; 9.2.0.x Every Minute
User Action
Active Sessions Waiting: Other

This metric represents all the waits that are neither idle nor user I/O.
Database 2-139
Wait Bottlenecks
Metric Summary

8.1.7.4; 9.0.1.x; 9.2.0.x Every Minute
User Action
Average Instance CPU (%)

This metric represents the average instance CPU as a percentage.
Metric Summary

8.1.7.4; 9.0.1.x; 9.2.0.x Every Minute
User Action
buffer busy waits (%)

This wait happens when a session wants to access a database block in the buffer cache
but it cannot because the buffer is busy. Another session is modifying the block and
the contents of the block are in flux during the modification. To guarantee that the
reader has a coherent image of the block with either all of the changes or none of the
changes, the session modifying the block marks the block header with a flag letting
other users know a change is taking place and to wait until the complete change is
applied.
The two main cases where this wait can occur are:
■ Another session is reading the block into the buffer
■ Another session holds the buffer in an incompatible mode to our request
While the block is being changed, the block is marked as unreadable by others. The
changes that are being made should last under a few hundredths of a second. A disk
read should be under 20 milliseconds and a block modification should be under one
millisecond. Therefore it will take a lot of buffer busy waits to cause a problem.
However, in a problem situation, there is usually a hot block, such as the first block on
the free list of a table, with high concurrent inserts. All users will insert into that block
at the same time, until it fills up, then users start inserting into the next free block on
the list, and so on.
Another example of a problem is of multiple users running full table scans on the same
large table at the same time. One user will actually read the block physically off disk,
and the other users will wait on Buffer Busy Wait for the physical I/O to complete.

Wait Bottlenecks
Metric Summary

Consecutive
8.1.7.4; Every After Every > 20 Not Defined 3 %value%%% of
9.0.1.x; Minute Sample service time is spent
9.2.0.x waiting on the
'buffer busy waits'
event.
Data Source
(DeltaBufferBusyWaitsTime/DeltaServiceTime)*100 where:
■ DeltaBufferBusyWaitsTime: difference of 'sum of time waited for sessions of
foreground processes on the 'buffer busy waits' event' between sample end and
start
■ DeltaServiceTime: difference of 'sum of time waited for sessions of foreground
processes on events not in IdleEvents + sum of 'CPU used when call started' for
sessions of foreground processes' between sample end and start
User Action
Look at v$waitstat (or the buffer busy drill down page) and determine the block type
with the highest waits.
Block Type and Action:
■ Undo Header - Use Automatic Undo Management (AUM) or add more RBS
segments)
■ Undo Block - Use AUM (or increase RBS sizes)
■ Data Block - First determine if it is an I/O problem. The Buffer Busy Waits
drill-down page should provide this information. Otherwise, sample from
v$session_wait
select p3, count(*) from v$session_wait where event='buffer
busy wait' ;
If p3 is less than 200 then it is an I/O problem. Either improve I/O performance or
change application. Applications running concurrent batch jobs that do full table
scans on the same large tables run into this problem.
■ Free List - Use ASSM (or freelists groups)
CPU Time Delta (sec)

This metric represents the time spent using CPU during the interval, measured in
hundredths of a second.
Database 2-141
Wait Bottlenecks
Metric Summary

8.1.7.4; 9.0.1.x; 9.2.0.x Every Minute
Data Source
The difference of sum of 'CPU used when call started' for sessions of foreground
processes' between sample end and start.
User Action
db file scattered read (%)

This is the same type of event as "db file sequential read", except that Oracle will read
multiple data blocks. Multi-block reads are typically used on full table scans. The
name "scattered read" refers to the fact that multiple blocks are read into database
block buffers that are 'scattered' throughout memory.
Metric Summary

Consecutive
9.2.0.x waiting on the 'db
file scattered read'
event.
Data Source
(DeltaDbFileScatteredReadTime/DeltaServiceTime)*100 where:
■ DeltaDbFileScatteredReadTime: difference of 'sum of time waited for sessions of
foreground processes on the 'db file scattered read' event' between sample end and
start
User Action
If the TIME spent waiting for multiblock reads is significant, then it is helpful to
determine against which segments Oracle is performing the reads. The files where the

Wait Bottlenecks
reads are occurring can be found by looking at the V$FILESTAT view where BLKS_
READ / READS > 1 . (A ratio greater than one indicates there are some multiblock
reads occurring).
It is also useful to see which sessions are performing scans and trace them to see if the
scans are expected. This statement can be used to see which sessions may be worth
tracing:
SELECT sid, total_waits, time_waited
FROM v$session_event
WHERE event='db file scattered read'
and total_waits>0
ORDER BY 3,2
;
You can also look at:

■ Statements with high DISK_READS in the V$SQL view
■ Sessions with high table scans blocks gotten in the V$SESSTAT view
db file sequential read (%)

This event shows a wait for a foreground process while doing a sequential read from
the database. The I/O is generally issued as a single I/O request to the OS; the wait
blocks until the I/O request completes.
Metric Summary

Consecutive
file sequential read'
event.
Data Source
(DeltaDbFileSequentialReadTime/DeltaServiceTime)*100 where:
■ DeltaDbFileSequentialReadTime: difference of 'sum of time waited for sessions of
foreground processes on the 'db file sequential read' event' between sample end
and start
Database 2-143
Wait Bottlenecks
User Action
Because I/O is a normal activity, take notice of unnecessary or slow I/O activity. If the
TIME spent waiting for I/Os is significant, then it can be determined for which
segments Oracle has to go to disk. See the "Tablespace I/O" and "File I/O" sections of
the ESTAT or STATSPACK reports to get information on which tablespaces and files
are servicing the most I/O requests, and to get an indication of the speed of the I/O
subsystem.
If the TIME spent waiting for reads is significant, then determine against which
segments Oracle is performing the reads. The files where the reads are occurring can
be found by looking at the V$FILESTAT view.
Also, see which sessions are performing reads and trace them to see if the I/Os are
expected. You can use this statement to see which sessions are worth tracing:
SELECT sid, total_waits, time_waited
FROM v$session_event
WHERE event='db file sequential read'
and total_waits>0
ORDER BY 3,2
;
You can also look at:

■ Statements with high DISK_READS in the V$SQL view
■ Sessions with high "physical reads" in the V$SESSTAT view
db file single write (%)

This event is used to wait for the writing of the file headers.
Metric Summary

Consecutive
file single write'
event.
Data Source
(DeltaDbFileSingleWriteTime/DeltaServiceTime)*100 where:
■ DeltaDbFileSingleWriteTime: difference of 'sum of time waited for sessions of
foreground processes on the 'db file single write' event' between sample end and
start

Wait Bottlenecks

User Action
direct path read (%)

The session is waiting for a direct read to complete. A direct read is a physical I/O
from a data file that bypasses the buffer cache and reads the data block directly into
process-private memory.
If asynchronous I/O is supported (and in use), then Oracle can submit I/O requests
and continue processing. Oracle can then pick up the results of the I/O request later
and wait on "direct path read" until the required I/O completes.
If asynchronous I/O is not being used, then the I/O requests block until completed
but these do not show as waits at the time the I/O is issued. The session returns later
to pick up the completed I/O data but can then show a wait on "direct path read" even
though this wait will return immediately.
Hence this wait event is very misleading because:
■ The total number of waits does not reflect the number of I/O requests
■ The total time spent in "direct path read" does not always reflect the true wait
time.
This style of read request is typically used for:
■ Sort I/O (when a sort does not fit in memory)
■ Parallel Query slaves
■ Read ahead (where a process may issue an I/O request for a block it expects to
need in the near future)
Metric Summary

Consecutive
9.2.0.x waiting on the 'direct
path read' event.
Data Source
(DeltaDirectPathReadTime/DeltaServiceTime)*100 where:
Database 2-145
Wait Bottlenecks
■ DeltaDirectPathReadTime: difference of 'sum of time waited for sessions of

foreground processes on the 'direct path read' event' between sample end and start
User Action
In DSS type systems, or during heavy batch periods, waits on "direct path read" are
normal. However, if the waits are significant on an OLTP style system, there may be a
problem.
You can:
■ Examine the V$SESSION_EVENT view to identify sessions with high numbers of
waits
■ Examine the V$SESSTAT view to identify sessions with high "physical reads
direct" (statistic only present in newer Oracle releases)
■ Examine the V$FILESTAT view to see where the I/O is occurring
■ Examine the V$SQLAREA view for statements with SORTS and high DISK_
READS (which may or may not be due to direct reads)
■ Determine whether the file indicates a temporary tablespace check for unexpected
disk sort operations.
■ Ensure that the DISK_ASYNCH_IO parameter is set to TRUE. This is unlikely to
reduce wait times from the wait event timings but may reduce sessions elapsed
times (as synchronous direct I/O is not accounted for in wait event timings).
■ Ensure the OS asynchronous I/O is configured correctly.
■ Check for I/O heavy sessions and SQL and see if the amount of I/O can be
reduced.
■ Ensure no disks are I/O bound.
direct path read (lob) (%)

The session is waiting for a direct read of a large object (lob) to complete. A direct read
is a physical I/O from a data file that bypasses the buffer cache and reads the data
block directly into process-private memory.
If asynchronous I/O is supported (and in use), then Oracle can submit I/O requests
and continue processing. Oracle can then pick up the results of the I/O request later
and wait on "direct path read" until the required I/O completes.
If asynchronous I/O is not being used, then the I/O requests block until completed
but these do not show as waits at the time the I/O is issued. The session returns later
to pick up the completed I/O data but can then show a wait on "direct path read" even
though this wait will return immediately.
Hence this wait event is very misleading because:
■ The total time spent in "direct path read" does not always reflect the true wait
time.

Wait Bottlenecks

■ Parallel Query slaves
■ Read ahead (where a process may issue an I/O request for a block it expects to
need in the near future)
Metric Summary

Consecutive
path read (lob)'
event.
Data Source
(DeltaDirectPathReadLobTime/DeltaServiceTime)*100 where:
■ DeltaDirectPathReadLobTime: difference of 'sum of time waited for sessions of
foreground processes on the 'direct path read (lob)' event' between sample end and
start
User Action
For noncached lob segments, it is helpful to place the data files where the LOB
SEGMENTS reside on a buffered disk, for example, on a File system disk. This
placement allows the direct reads to benefit from a cache not on Oracle for data read
operations.
direct path write (%)

Session is waiting for a direct write to complete.
Direct path writes allow a session to queue an I/O write request and continue
processing while the OS handles the I/O. If the session needs to know if an
outstanding write is complete, then it waits for this wait event. This can happen
because the session is either out of free slots and needs an empty buffer (it waits on the
oldest I/O) or it needs to ensure all writes are flushed.
If asynchronous I/O is not being used, then the I/O write request blocks until it is
completed but this does not show as a wait at the time the I/O is issued. The session
returns later to pick up the completed I/O data but can then show a wait on "direct
path write" even though this wait will return immediately.
Database 2-147
Wait Bottlenecks
Hence this wait event is misleading because:

■ The total time spent in "direct path write" does not always reflect the true wait
time.
■ Parallel DML are issued to create and populate objects
■ Direct load operations, for example, Create Table as Select (CTAS)
Metric Summary

Consecutive
path write' event.
Data Source
(DeltaDirectPathWriteTime/DeltaServiceTime)*100 where:
■ DeltaDirectPathWriteTime: difference of 'sum of time waited for sessions of
foreground processes on the 'direct path write' event' between sample end and
start
User Action
It is unusual to see lots of waits on "direct path write" except for specific jobs. If the
figure is a large proportion of the overall wait time it is best to identify where the
writes are coming from.
You can:
waits.
■ Examine the V$SESSTAT view to identify sessions with high "physical writes
direct" (statistic only present in newer Oracle releases).
■ Examine the V$FILESTAT view to see where the I/O is occurring.

Wait Bottlenecks
■ Ensure the DISK_ASYNCH_IO parameter is set to TRUE. This is unlikely to

times because synchronous direct I/O is not accounted for in wait event timings.
■ For parallel DML, check the I/O distribution across disks and make sure that the
I/O subsystem is adequately sized for the degree of parallelism.
direct path write (lob) (%)

Direct path write to a large object (LOB). The session is waiting on the operating
system to complete the write operation.
Metric Summary

Consecutive
path write (lob)'
event.
Data Source
(DeltaDirectPathWriteLobTime/DeltaServiceTime)*100 where:
■ DeltaDirectPathWriteLobTime: difference of 'sum of time waited for sessions of
foreground processes on the 'direct path write (lob)' event' between sample end
and start
User Action
It is unusual to see lots of waits on "direct path write (lob)" except for specific jobs. If
the figure is a large proportion of the overall wait time it is best to identify where the
writes are coming from.
You can:
waits.
■ Examine the V$SESSTAT view to identify sessions with high "physical writes
direct" (statistic only present in newer Oracle releases).
Database 2-149
Wait Bottlenecks
■ Examine the V$FILESTAT view to see where the I/O is occurring.

■ Ensure the DISK_ASYNCH_IO parameter is set to TRUE. This is unlikely to
times because synchronous direct I/O is not accounted for in wait event timings.
■ For parallel DML, check the I/O distribution across disks and make sure that the
I/O subsystem is adequately sized for the degree of parallelism.
enqueue - other (%)

Enqueues are local locks that serialize access to various resources. This wait event
indicates a wait for a lock that is held by another session (or sessions) in an
incompatible mode to the requested mode.
Metric Summary

Consecutive
'enqueue' event.
Data Source
(DeltaEnqueueTime/DeltaServiceTime)*100 where:
■ DeltaEnqueueTime: difference of 'sum of time waited for sessions of foreground
processes on the 'enqueue' event, or any other 'enqueue:' event' between sample
end and start
User Action
The action to take depends on the lock type which is causing the most problems. The
most common lock waits are generally for:
■ TX: Transaction Lock -- Generally due to application or table setup issues, for
example row level locking conflicts and ITL allocation

Wait Bottlenecks
■ TM: DML enqueue -- Generally due to application issues, particularly if foreign

key constraints have not been indexed.
■ ST: Space management enqueue -- Usually caused by too much space management
occurring (for example, small extent sizes, lots of sorting, and so on)
■ HW: High Water Mark -- Concurrent users trying to extend a segment's
high-water mark for space allocated.
In Oracle9i and earlier releases, all enqueue wait times are included in this alert.
To determine which enqueues are causing the most waits systemwide:
■ In Oracle9i and later, examine the V$ENQUEUE_STAT view thus:
SELECT eq_type "Lock",
total_req# "Gets",
total_wait# "Waits",
cum_wait_time
FROM V$enqueue_stat
WHERE Total_wait# > 0
;
■ In Oracle8i and earlier, examine the X$KSQST view thus:

SELECT ksqsttyp "Lock",
ksqstget "Gets",
ksqstwat "Waits"
FROM X$KSQST where KSQSTWAT > 0
;
The above give the systemwide number of waits for each lock type. Remember that it
only takes one long wait to distort the average wait time figures.
You can also examine:
■ Sessions with high numbers of "enqueue waits" in the V$SESSTAT view
■ Sampling of the V$LOCK view to find waiting / blocking sessions
enqueue: DML - contention (%)

TM Per table locks are acquired during the execution of a transaction when referencing
a table with a DML statement so that the object is not dropped or altered during the
execution of the transaction, if and only if the dml_locks parameter is non-zero.
TM Locks are held for base table/partition operations under the following conditions:
■ Enabling of referential constraints
■ Changing constraints from DIASABLE NOVALIDATE to DISABLE VALIDATE
■ Rebuild of an IOT
■ Create View or Alter View operations
■ Analyze table compute statistics or validate structure
■ Parallel DML operations
Metric Summary
Database 2-151
Wait Bottlenecks


Consecutive
'enqueue: DML -
contention' event.
Data Source
(DeltaEnqueueDMLTime/DeltaServiceTime)*100 where:
■ DeltaEnqueueDMLTime: difference of 'sum of time waited for sessions of
foreground processes on the 'enqueue: DML - contention' event' between sample
end and start
User Action
Examine the database locks page and determine the user who is blocking another user
and why, then decide the appropriate action.
enqueue: HW, Segment High Water Mark - contention (%)

The HW enqueue is used to serialize the allocation of space above the high-water mark
in an object.
This lock is acquired when a segment's high-water mark is moved, which typically is
the case during heavy inserts.
Metric Summary

Consecutive
'enqueue: HW,
Segment High Water
Mark - contention'
event.

Wait Bottlenecks
Data Source
(DeltaEnqueueHWTime/DeltaServiceTime)*100 where:
■ DeltaEnqueueHWTime: difference of 'sum of time waited for sessions of
foreground processes on the 'enqueue: Segment High Water Mark - contention'
event' between sample end and start
User Action
Use Locally Managed Tablespaces.
For version dictionary managed tablespaces:
■ Recreate the objects and preallocate extents with the following: ALTER
TABLE...ALLOCATE EXTENT statements.
■ Increasing the number of free lists may help, as well as moving the high-water
mark. This depends on the number of freelists.
enqueue: ST, Space Transaction - contention (%)

When Oracle needs to perform a space management operation (such as allocating
temporary segments for a sort) the user session acquires a special enqueue called the
'ST' enqueue.
Metric Summary

Consecutive
'enqueue: ST, Space
Transaction -
contention' event.
Data Source
(DeltaEnqueueSTTime/DeltaServiceTime)*100 where:
■ DeltaEnqueueSTTime: difference of 'sum of time waited for sessions of foreground
processes on the 'enqueue: Space Transaction - contention' event' between sample
end and start
Database 2-153
Wait Bottlenecks
User Action
Ensure that temporary tablespaces are proper temporary tablespaces of type
"temporary".
enqueue: TM, TX, Transaction - row lock contention (%)

Two users are attempting to change the same row.
These locks are of type TX.
Metric Summary

Consecutive
'enqueue: TM,TX,
Transaction - row
lock contention'
event.
Data Source
(DeltaEnqueueRowLockTime/DeltaServiceTime)*100 where:
■ DeltaEnqueueRowLockTime: difference of 'sum of time waited for sessions of
foreground processes on the 'enqueue: Transaction - row lock contention' event'
between sample end and start
User Action
Examine the database locks page and determine the user who is blocking another user
and why, then decide the appropriate action.
enqueue: TX mode 4, Transaction - allocate ITL entry (%)

Oracle keeps note of which rows are locked by which transaction in an area at the top
of each data block known as the 'interested transaction list'. The number of ITL slots in
any block in an object is controlled by the INITRANS and MAXTRANS attributes.
INITRANS is the number of slots initially created in a block when it is first used, while
MAXTRANS places an upper bound on the number of entries allowed. Each
transaction which wants to modify a block requires a slot in this 'ITL' list in the block.

Wait Bottlenecks
Metric Summary

Consecutive
'enqueue: TX mode
4, Transaction -
allocate ITL entry'
event.
Data Source
(DeltaEnqueueAllocITLTime/DeltaServiceTime)*100 where:
■ DeltaEnqueueAllocITLTime: difference of 'sum of time waited for sessions of
foreground processes on the 'enqueue: TX mode 4, Transaction - allocate ITL entry'
User Action
To increase the number of ITL slots, recreate the table and increase the INITRANS
parameter for the object with the contention. An alter table statement can be run to
increase the ITL slots by increasing the value for INITRANS, but this will only take
effect for new blocks.
enqueue: UL: User-defined - contention (%)

Caused by the application explicitly running commands of the nature "lock table".
Metric Summary
Database 2-155
Wait Bottlenecks

Consecutive
'enqueue: UL:
User-defined -
contention' event.
Data Source
(DeltaEnqueueUserDefTime/DeltaServiceTime)*100 where:
■ DeltaEnqueueUserDefTime: difference of 'sum of time waited for sessions of
foreground processes on the 'enqueue: User-defined - contention' event' between
User Action
This is an application issue. Determine where the application code is locking objects
and why. Make relevant application changes if necessary.
Use the "Blocking Sessions" page to find lock holds and waits.
free buffer waits (%)

This event occurs mainly when a server process is trying to read a new buffer into the
buffer cache but too many buffers are either pinned or dirty and thus unavailable for
reuse. The session posts to DBWR then waits for DBWR to create free buffers by
writing out dirty buffers to disk.
DBWR may not be keeping up with writing dirty buffers in the following situations:
■ The I/O system is slow.
■ There are resources it is waiting for, such as latches.
■ The buffer cache is so small that DBWR spends most of it's time cleaning out
buffers for server processes.
■ The buffer cache is so big that one DBWR process is not enough to free enough
buffers in the cache to satisfy requests.
Metric Summary

Wait Bottlenecks

Consecutive
9.2.0.x waiting on the 'free
buffer waits' event.
Data Source
(DeltaFreeBufferWaitsTime/DeltaServiceTime)*100 where:
■ DeltaFreeBufferWaitsTime: difference of 'sum of time waited for sessions of
foreground processes on the 'free buffer waits' event' between sample end and
start
User Action
Sometimes the easy solution is to increase the buffer cache to allow for more free
blocks. This works in many cases, but if the application is generating a sustained
amount of dirty blocks then increasing the buffer cache may only help or delay the
problem but not solve it.
If this event occurs frequently, examine the session waits for DBWR to see whether
there is anything delaying DBWR.
Run this query to see if the I/O is evenly distributed.
SELECT name, phyrds, phywrts
FROM v$filestat a, v$datafile b
WHERE a.file# = b.file#
Also look for files having full table scans, using this query:
SELECT name, phyrds, phyblkrd, phywrts
FROM v$filestat a, v$datafile b
WHERE a.file# = b.file#
and phyrds != phyblkrd
Host CPU Utilization (%)

This metric represents the percentage of CPU being used on the host.
Metric Summary

Database 2-157
Wait Bottlenecks
User Action
latch free - other (%)

A latch is a low-level internal lock used by Oracle to protect memory structures.
Latches are similar to short duration locks that protect critical bits of code. This wait
indicates that the process is waiting for a latch that is currently busy (held by another
process).
The latch free event is updated when a server process attempts to get a latch, and the
latch is unavailable on the first attempt.
Metric Summary

Consecutive
9.2.0.x waiting on the 'latch
free' event.
Data Source
(DeltaLatchFreeTime/DeltaServiceTime)*100 where:
■ DeltaLatchFreeTime: difference of 'sum of time waited for sessions of foreground
processes on the 'latch free' event, or any other 'latch:' event' between sample end
and start
User Action
Determine which latch is causing the highest amount of contention.
To find the problem latches since database startup, run the following query:
Select n.name, l.sleeps
from v$latch l, v$latchname n
where n.latch#=l.latch# and l.sleeps > 0 order by l.sleeps
;
To see latches that are currently a problem on the database run:

SELECT n.name, SUM(w.p3) Sleeps
FROM V$SESSION_WAIT w, V$LATCHNAME n
WHERE w.event = `latch free'
AND w.p2 = n.latch#

Wait Bottlenecks
GROUP BY n.name;
Take action based on the latch with the highest number of sleeps.
latch: cache buffer chains (%)

The cache buffers chains latches are used to protect a buffer list in the buffer cache.
These latches are used when searching for, adding, or removing a buffer from the
buffer cache.
Blocks in the buffer cache are placed on linked lists (cache buffer chains) which hang
off a hash table. The hash chain that a block is placed on is based on the DBA and
CLASS of the block. Each hash chain is protected by a single child latch. Processes
need to get the relevant latch to allow them to scan a hash chain for a buffer so that the
linked list does not change underneath them.
Contention on this latch usually means that there is a block that is in great contention
(known as a hot block).
Metric Summary

Consecutive
9.2.0.x waiting on the 'latch:
cache buffer chains'
event.
Data Source
(DeltaLatchCacheBufferChainsTime/DeltaServiceTime)*100 where:
■ DeltaLatchCacheBufferChainsTime: difference of 'sum of time waited for sessions
of foreground processes on the 'latch: cache buffer chains' event' between sample
end and start
User Action
To identify the heavily accessed buffer chain, and hence the contended for block, look
at latch statistics for the cache buffers chains latches using the V$LATCH_CHILDREN
view. If there is a specific cache buffers chains child latch that has many more GETS,
MISSES, and SLEEPS when compared with the other child latches, then this is the
contended for child latch.
This latch has a memory address, identified by the ADDR column.
Database 2-159
Wait Bottlenecks
select
addr,
sleeps
from
v$latch_children c,
v$latchname n
where
n.name='cache buffers chains' and
c.latch#=n.latch# and
sleeps > 100
order by sleeps
/
Use the value in the ADDR column joined with the V$BH view to identify the blocks
protected by this latch. For example, given the address (V$LATCH_
CHILDREN.ADDR) of a heavily contended latch, this queries the file and block
numbers:
SELECT file#, dbablk, class, state, TCH
FROM X$BH
WHERE HLADDR='address of latch';
X$BH.TCH is a touch count for the buffer. A high value for X$BH.TCH indicates a hot
block.
Many blocks are protected by each latch. One of these buffers will probably be the hot
block. Any block with a high TCH value is a potential hot block. Perform this query a
number of times, and identify the block that consistently appears in the output.
After you have identified the hot block, query DBA_EXTENTS using the file number
and block number to identify the segment.
latch: library cache (%)

There are multiple library cache latches. Each one protects a range of 'hash buckets'
and the latch covers all heaps.
Metric Summary

Consecutive
library cache' event.
Data Source
(DeltaLatchLibraryCacheTime/DeltaServiceTime)*100 where:

Wait Bottlenecks
■ DeltaLatchLibraryCacheTime: difference of 'sum of time waited for sessions of

foreground processes on the 'latch: library cache' event' between sample end and
start
User Action
Contention for the library cache latches can be caused by excessive parsing of literal
SQL. It is advisable to use sharable SQL wherever possible.
latch: redo copy (%)

When a sessions redo buffer is larger than <Parameter: log_small_entry_max_size> the
kernel first allocates a redo copy buffer, protected by a redo copy latch.
The buffer will not be used until space is allocated on the log buffer and some header
has been set. However, the redo copy latch is acquired to reduce the code inside the
allocation latch holding and to prevent further contention.
Metric Summary

Consecutive
redo copy' event.
Data Source
(DeltaLatchRedoCopyTime/DeltaServiceTime)*100 where:
■ DeltaLatchRedoCopyTime: difference of 'sum of time waited for sessions of
foreground processes on the 'latch: redo copy' event' between sample end and start
User Action
The number of redo copy latches is controlled by the init.ora <Parameter:log_
simultaneous_copies>. If the parameter is not set, it defaults to the number of CPUs.
Database 2-161
Wait Bottlenecks
For log generating processes, the latch get is made in an immediate mode, then it will
be convenient to have enough redo copy latches to reduce contention of foreground
processes.
Before flushing out the log buffer, the LGWR will acquire all redo copy latches in a
willing-to-wait mode. Thus an excessive number of copy latches will cause contention
in the log buffer flushing process.
The number of LWGR redo copy latch allocations is redo writes * No.redo copy
latches.
latch: shared pool (%)

This latch protects the allocation of memory from the shared pool.
If there is contention on this latch, it is often an indication that the shared pool is
fragmented.
Metric Summary

Consecutive
shared pool' event.
Data Source
(DeltaLatchSharedPoolTime/DeltaServiceTime)*100 where:
■ DeltaLatchSharedPoolTime: difference of 'sum of time waited for sessions of
foreground processes on the 'latch: shared pool' event' between sample end and
start
User Action
Shared pool latch contention is often an indication of high hard parsing usually caused
by the use of literal values in SQL statements. These statements could otherwise be
shared if bind variables were used.
Prior to Oracle Server release 8.1.6, shared pool fragmentation could be acerbated by a
shared pool that was too large. Reducing the size of the shared pool would reduce the
contention for this latch.

Wait Bottlenecks
For Oracle Server release 8.1.6 and later, there should be very little shared pool latch
contention. If there is, it is probably a symptom of an application using literals. One
possible solution is to use the init.ora parameter <cursor_sharing=FORCE>.
library cache load lock (%)

Oracle tries to find the load lock for the database object so that it can load the object.
The load lock is always gotten in Exclusive mode, so that no other process can load the
same object. If the load lock is busy the session will wait on this event until the lock
becomes available.
Metric Summary

Consecutive
'library cache load
lock' event.
Data Source
(DeltaLibraryCacheLoadLockTime/DeltaServiceTime)*100 where:
■ DeltaLibraryCacheLoadLockTime: difference of 'sum of time waited for sessions of
foreground processes on the 'library cache load lock' event' between sample end
and start
User Action
To be waiting for a load lock means that there is a blocker with a higher or
incompatible mode. This event in itself is not affected by the parallel server. However,
you must have acquired the 'library cache lock' before you get to this point. The 'cache
lock' is a DFS lock.
library cache lock (%)

The library cache lock controls the concurrency between clients of the library cache by
acquiring a lock on the object handle so that one client can prevent other clients from
accessing the same object or the client can maintain a dependency for a long time (no
other client can change the object). This lock is also gotten to locate an object in the
library cache.
Database 2-163
Wait Bottlenecks
Blocking situations can occur when two sessions compile the same PL/SQL package,
or one session is recreating an index while another session is trying to execute a SQL
statement that depends on that index.
Metric Summary

Consecutive
'library cache lock'
event.
Data Source
(DeltaLibraryCacheLockTime/DeltaServiceTime)*100 where:
■ DeltaLibraryCacheLockTime: difference of 'sum of time waited for sessions of
foreground processes on the 'library cache lock' event' between sample end and
start
User Action
Waiting for a load lock indicates that there is a blocker with a higher or incompatible
mode. Locks map to Instance Locks.
The following query will list waiters and the holder of the resource along with the
event the resource holder is waiting for.
column h_wait format A20
select s.sid,
waiter.p1raw w_p1r,
waiter.p2raw w_p2r,
holder.event h_wait,
holder.p1raw h_p1r,
holder.p2raw h_p2r,
count(s.sid) users_blocked,
sql.hash_value
from
v$sql sql,
v$session s,
x$kgllk l,
v$session_wait waiter,
v$session_wait holder
where
s.sql_hash_value = sql.hash_value and

Wait Bottlenecks
l.KGLLKADR=waiter.p2raw and
s.saddr=l.kgllkuse and
waiter.event like 'library cache lock' and
holder.sid=s.sid
group by
s.sid,
waiter.p1raw ,
waiter.p2raw ,
holder.event ,
holder.p1raw ,
holder.p2raw ,
sql.hash_value
;
library cache pin (%)

Library cache pins are used to manage library cache concurrency. Pinning an object
causes the heaps to be loaded into memory (if not already loaded). PINS can be
acquired in NULL, SHARE or EXCLUSIVE modes and can be considered like a special
form of lock. A wait for a "library cache pin" implies some other session holds that PIN
in an incompatible mode.
Metric Summary

Consecutive
'library cache pin'
event.
Data Source
(DeltaLibraryCachePinTime/DeltaServiceTime)*100 where:
■ DeltaLibraryCachePinTime: difference of 'sum of time waited for sessions of
foreground processes on the 'library cache pin' event' between sample end and
start
User Action
What to do to reduce these waits depends heavily on what blocking scenario is
occurring. A common problem scenario is the use of DYNAMIC SQL from within a
Database 2-165
Wait Bottlenecks
PL/SQL procedure where the PL/SQL code is recompiled and the DYNAMIC SQL
calls something which depends on the calling procedure.
■ If there is general widespread waiting then the shared pool may need tuning.
■ If there is a blocking scenario, collect evidence as described in the following query
and contact Oracle support.
The following query will list the waiters and the session holding the pin, along with
the wait event the holder is waiting for.
column h_wait format A20
select s.sid,
waiter.p1raw w_p1r,
holder.event h_wait,
holder.p1raw h_p1r,
holder.p2raw h_p2r,
holder.p3raw h_p2r,
count(s.sid) users_blocked,
sql.hash_value
from
v$sql sql,
v$session s,
x$kglpn p,
v$session_wait waiter,
v$session_wait holder
where
s.sql_hash_value = sql.hash_value and
p.kglpnhdl=waiter.p1raw and
s.saddr=p.kglpnuse and
waiter.event like 'library cache pin' and
holder.sid=s.sid
group by
s.sid,
waiter.p1raw ,
holder.event ,
holder.p1raw ,
holder.p2raw ,
holder.p3raw ,
sql.hash_value
;
local write wait (%)

The wait event can be caused by truncate operations. Truncate operations cause the
DBWR to be posted to flush out the space header.
Metric Summary

Wait Bottlenecks

Consecutive
9.2.0.x waiting on the 'local
write wait' event.
Data Source
(DeltaLocalWriteWaitTime/DeltaServiceTime)*100 where:
■ DeltaLocalWriteWaitTime: difference of 'sum of time waited for sessions of
foreground processes on the 'local write wait' event' between sample end and start
Wait time: Up to one second, then loop back and check that buffer is clean.
Parameters:
P1: Absolute file number
P2: Block number
User Action
log buffer space (%)

The system is waiting for space in the log buffer because data is being written into the
log buffer faster than LGWR can write it out.
Metric Summary

Consecutive
9.2.0.x waiting on the 'log
buffer space' event.
Data Source
(DeltaLogBufferSpaceTime/DeltaServiceTime)*100 where:
Database 2-167
Wait Bottlenecks
■ DeltaLogBufferSpaceTime: difference of 'sum of time waited for sessions of

foreground processes on the 'log buffer space' event' between sample end and start
User Action
Consider making the log buffer bigger if it is small, or moving the log files to faster
disks such as striped disks.
log file switch (archiving needed) (%)

The system is waiting for a log switch because the log being switched into has not
been archived yet.
Metric Summary

Consecutive
8.1.7.4; Every After Every > 1 5 1 %value%%% of
file switch (archiving
needed)' event.
Data Source
(DeltaLogFileSwitchArchTime/DeltaServiceTime)*100 where:
■ DeltaLogFileSwitchArchTime: difference of 'sum of time waited for sessions of
foreground processes on the 'log file switch (archiving needed)' event' between
User Action
Check the alert file to make sure that archiving has not stopped due to a failed archive
write. To speed up archiving consider adding more archive processes or putting the
archive files on striped disks.
If the archiver is slow, then it might be prudent to prevent I/O contention between the
archiver process and LGWR by ensuring that archiver reads and LGWR writes are
separated. This is achieved by placing logs on alternating drives.

Wait Bottlenecks
log file switch (checkpoint complete) (%)

Waiting for a log switch because the system cannot wrap into the next log because the
checkpoint for that log has not completed.
Metric Summary

Consecutive
8.1.7.4; Every After Every > 5 50 1 %value%%% of
file switch
(checkpoint
complete) event.
Data Source
(DeltaLogFileSwitchCkptTime/DeltaServiceTime)*100 where:
■ DeltaLogFileSwitchCkptTime: difference of 'sum of time waited for sessions of
foreground processes on the 'log file switch (checkpoint complete)' event' between
User Action
Increase the redo log sizes.
To speed up checkpoint, consider making the buffer cache smaller, or increasing
<Parameter:DB_BLOCK_CHECKPOINT_BATCH>, or adding more DBWR processes.
You can also enable the checkpoint process by setting the init.ora
<Parameter:CHECKPOINT_PROCESS> = TRUE.
log file switch completion (%)

Waiting for log switch because current log is full and LGWR needs to complete writing
to current log and open the new log or some other request to switch log files.
Metric Summary
Database 2-169
Wait Bottlenecks

Consecutive
file switch
completion' event.
Data Source
(DeltaLogFileSwitchCompleteTime/DeltaServiceTime)*100 where:
■ DeltaLogFileSwitchCompleteTime: difference of 'sum of time waited for sessions
of foreground processes on the 'log file switch completion' event' between sample
end and start
User Action
For the log file switch (checkpoint incomplete) event:
■ Check if there are too few, or too small redo logs. If there are a few redo logs or
small redo logs, and the system produces enough redo to cycle through all the logs
before DBWR has been able to complete the checkpoint, then increase the size or
number of redo logs. This is often the easiest solution but may increase time to
recovery.
■ Check if DBWR is slow, possibly due to an overloaded or slow I/O system. Check
the DBWR write times, check the I/O system, and distribute I/O if necessary.
log file sync (%)

When a user session COMMITs (or rolls back), the sessions redo information needs to
be flushed to the redo log file. The user session will post the LGWR to write all redo
required from the log buffer to the redo log file. When the LGWR has finished it will
post the user session. The user session waits on this wait event while waiting for
LGWR to post it back to confirm all redo changes are safely on disk.
Metric Summary

Wait Bottlenecks

Consecutive
file sync' event.
Data Source
(DeltaLogFileSyncTime/DeltaServiceTime)*100 where:
■ DeltaLogFileSyncTime: difference of 'sum of time waited for sessions of
foreground processes on the 'log file sync' event' between sample end and start
User Action
There are 3 main things you can do to help reduce waits on "log file sync":
■ Tune LGWR to get good throughput to disk.
■ Do not put redo logs on RAID 5.
■ Place log files on dedicated disks.
■ Consider putting log files on striped disks.
■ If there are lots of short duration transactions, see if it is possible to BATCH
transactions together so there are fewer distinct COMMIT operations. Each
commit has to have it confirmed that the relevant REDO is on disk. Although
commits can be piggybacked by Oracle, reducing the overall number of commits
by batching transactions can have a very beneficial effect.
■ Determine whether any activity can safely be done with NOLOGGING /
UNRECOVERABLE options.
log switch/archive (%)

Used as part of the 'alter system archive log change <scn>' command. Oracle is
basically waiting for the current log from an open thread other than our own to be
archived.
Metric Summary
Database 2-171
Wait Bottlenecks

Consecutive
switch/archive'
event.
Data Source
(DeltaLogSwitchArchTime/DeltaServiceTime)*100 where:
■ DeltaLogSwitchArchTime: difference of 'sum of time waited for sessions of
foreground processes on the 'log switch/archive' event' between sample end and
start
User Action
pipe put (%)

The session is waiting for the pipe send timer to expire or for space to be made
available in the pipe.
Metric Summary

Consecutive
9.2.0.x waiting on the 'pipe
put' event.
Data Source
(DeltaPipePutTime/DeltaServiceTime)*100 where:
■ DeltaPipePutTime: difference of 'sum of time waited for sessions of foreground
processes on the 'pipe put' event' between sample end and start

Wait Bottlenecks

User Action
You are dependent on space being freed up on the pipe, so you are not actually
dependent on any one session. You can query X$KGLOB to find the pipe name. There
is virtually no way of finding the pipe name other than via SQL, as there are no useful
addresses.
row cache lock (%)

This metric is used to wait for a lock on a data dictionary cache specified by "cache id".
If one is running in shared mode (Parallel Server), the LCK0 is signaled to get the row
cache lock for the foreground waiting on this event. The LCK0 process will get the lock
asynchronously. In exclusive mode, the foreground process will try to get the lock.
Metric Summary

Consecutive
9.2.0.x waiting on the 'row
cache lock' event.
Data Source
(DeltaRowCacheLockTime/DeltaServiceTime)*100 where:
■ DeltaRowCacheLockTime: difference of 'sum of time waited for sessions of
foreground processes on the 'row cache lock' event' between sample end and start
User Action
If this event shows up a lot, consider increasing the shared pool so that more data
dictionary can be cached.
SQL*Net break/reset to client (%)

The server is sending a break or reset message to the client. The session running on the
server is waiting for a reply from the client.
Database 2-173
Wait Bottlenecks
These waits are caused by an application attempting to:

■ Select from a closed cursor
■ Select on a cursor after the last row has already been fetched and no data has been
returned
■ Select on a non-existent table
■ Insert a duplicate row into a uniquely indexed table
■ Issuing a query with invalid syntax
If the value, v$session_wait.p2, for this parameter equals 0, it means a reset was sent to
the client. A non-zero value means that the break was sent to the client.
Metric Summary

Consecutive
'SQL*Net
break/reset to client'
event.
Data Source
(DeltaNetResetToClientTime/DeltaServiceTime)*100 where:
■ DeltaNetResetToClientTime: difference of 'sum of time waited for sessions of
foreground processes on the 'SQL*Net break/reset to client' event' between sample
end and start
Wait time: Up to one second, then loop back and check that buffer is clean.
Parameters:
P1: Absolute file number
P2: Block number
User Action
If these waits are significant, track down the application logic producing these errors
to reduce these waits. If you are using Oracle9i or higher, check in v$sysstat "parse
count (failures)" to see that statements have been parsed where columns or tables are
unknown. The statistic "parse count (failures)" does not increase if you send SQL with
invalid syntax.

Wait Bottlenecks
The clearest method to track down the root cause of the error is to run tracing on the
users experiencing the wait. Their trace files will contain the SQL statements failing
and generating the break/reset wait.
SQL*Net break/reset to dblink (%)

The server is sending a break or reset message to the client. The session running on the
server is waiting for a reply from the client.
These waits are caused by an application attempting to:
■ Select from a closed cursor
■ Select on a cursor after the last row has already been fetched and no data has been
returned
■ Select on a non-existent table
■ Insert a duplicate row into a uniquely indexed table
■ Issuing a query with invalid syntax
If the value, v$session_wait.p2, for this parameter equals 0, it means a reset was sent to
the client. A non-zero value means that the break was sent to the client.
Metric Summary

Consecutive
'SQL*Net
break/reset to
dblink' event.
Data Source
(DeltaNetResetToDblinkTime/DeltaServiceTime)*100 where:
■ DeltaNetResetToDblinkTime: difference of 'sum of time waited for sessions of
foreground processes on the 'SQL*Net break/reset to dblink' event' between
User Action
If these waits are significant, track down the application logic producing these errors
to reduce these waits. If you are using Oracle9i or higher, check in v$sysstat "parse
Database 2-175
Wait Bottlenecks
count (failures)" to see that statements have been parsed where columns or tables are
unknown. The statistic "parse count (failures)" does not increase if you send SQL with
invalid syntax.
SQL*Net message to client (%)

The shadow process is waiting for confirmation of a send to the client process.
Metric Summary

Consecutive
'SQL*Net message to
client' event.
Data Source
(DeltaNetMsgToClientTime/DeltaServiceTime)*100 where:
■ DeltaNetMsgToClientTime: difference of 'sum of time waited for sessions of
foreground processes on the 'SQL*Net message to client' event' between sample
end and start
User Action
This event could indicate network latency problems.
SQL*Net message to dblink (%)

The shadow process is waiting for confirmation of a send to the client process.
Metric Summary

Wait Bottlenecks

Consecutive
'SQL*Net message to
dblink' event.
Data Source
(DeltaNetMsgToDblinkTime/DeltaServiceTime)*100 where:
■ DeltaNetMsgToDblinkTime: difference of 'sum of time waited for sessions of
foreground processes on the 'SQL*Net message to dblink' event' between sample
end and start
User Action
This event could indicate network latency problems.
SQL*Net more data from client (%)

The shadow process has received part of a call from the client process (for example,
SQL*Plus, Pro*C, and JDBC) in the first network package and is waiting for more data
for the call to be complete. Examples are large SQL or PL/SQL block and insert
statements with large amounts of data.
Metric Summary

Consecutive
'SQL*Net more data
from client' event.
Data Source
(DeltaNetMoreFromClientTime/DeltaServiceTime)*100 where:
Database 2-177
Wait Bottlenecks
■ DeltaNetMoreFromClientTime: difference of 'sum of time waited for sessions of

foreground processes on the 'SQL*Net more data from client' event' between
User Action
This event could indicate:
■ Network latency problems
■ tcp_no_delay configuration issues
■ Large array insert
■ Soft parsing, shipping SQL and PL/SQL text. Using stored procedures and
packages will help alleviate this problem.
SQL*Net more data from dblink (%)

The shadow process has received part of a call from the client process (for example,
SQL*Plus, Pro*C, and JDBC) in the first network package and is waiting for more data
for the call to be complete. Examples are large SQL or PL/SQL block and insert
statements with large amounts of data.
Metric Summary

Consecutive
'SQL*Net more data
from dblink' event.
Data Source
(DeltaNetMoreFromDblinkTime/DeltaServiceTime)*100 where:
■ DeltaNetMoreFromDblinkTime: difference of 'sum of time waited for sessions of
foreground processes on the 'SQL*Net more data from dblink' event' between

Wait Bottlenecks
User Action
■ Large number of columns or wide column data
SQL*Net more data to client (%)

The shadow process has completed a database call and is returning data to the client
process (for example SQL*Plus). The amount of data being sent requires more than one
send to the client. The shadow process waits for the client to receive the last send. This
happens, for example, in a SQL statement that returns a large amount of data.
Metric Summary

Consecutive
'SQL*Net more data
to client' event.
Data Source
(DeltaNetMoreToClientTime/DeltaServiceTime)*100 where:
■ DeltaNetMoreToClientTime: difference of 'sum of time waited for sessions of
foreground processes on the 'SQL*Net more data to client' event' between sample
end and start
User Action
Database 2-179
Wait Bottlenecks
SQL*Net more data to dblink (%)

The shadow process has completed a database call and is returning data to the client
process (for example SQL*Plus). The amount of data being sent requires more than one
send to the client. The shadow process waits for the client to receive the last send. This
happens, for example, in a SQL statement that returns a large amount of data.
Metric Summary

Consecutive
'SQL*Net more data
to dblink' event.
Data Source
(DeltaNetMoreToDblinkTime/DeltaServiceTime)*100 where:
■ DeltaNetMoreToDblinkTime: difference of 'sum of time waited for sessions of
foreground processes on the 'SQL*Net more data to dblink' event' between sample
end and start
User Action
Wait Time (%)

This metric represents the percentage of time spent waiting, instance-wide, for
resources or objects during this sample period.
This test checks the percentage time spent waiting, instance-wide, for resources or
objects during this sample period. If the % Wait Time is greater than or equal to the
threshold values specified by the threshold arguments, and the number of occurrences
exceeds the value specified in the "Number of Occurrences" parameter, then a warning
or critical alert is generated.

Wait Bottlenecks
Metric Summary

Consecutive
Number of
Data Source
DeltaTotalWait / (DeltaTotalWait + DeltaCpuTime) where:
■ DeltaTotalWait: difference of 'sum of time waited for all wait events in v$system_
■ DeltaCpuTime: difference of 'select value from v$sysstat where name='CPU used
by this session' between sample end and start
User Action
Investigate further into which specific wait events are responsible for the bulk of the
wait time. Individual wait events may identify unique problems within the database.
Diagnosis will be tailored where appropriate through drilldowns specific to individual
wait events.
write complete waits (%)

The session is waiting for a buffer to be written. The write is caused by normal aging
or a cross instance call.
A user wants to modify a block that is part of DBWR's current write batch. When
DBWR grabs buffers to write, it marks them as 'being written'. All the collected buffers
are then written to disk. The wait 'write complete waits' implies we wanted a buffer
while this flag was set. The flags are cleared as each buffer is written.
Metric Summary

Consecutive
9.2.0.x waiting on the 'write
complete waits'
event.
Database 2-181
Wait by Session Count
Data Source
(DeltaWriteCompleteWaitsTime/DeltaServiceTime)*100 where:
■ DeltaWriteCompleteWaitsTime: difference of 'sum of time waited for sessions of
foreground processes on the 'write complete waits' event' between sample end and
start
User Action
Multiple DBWRs, ASYNC_IO and/or increasing the size of the buffer cache may help
reduce waits.
Wait by Session Count

This metric category contains the metrics that represent the number of sessions
waiting on each non-idle wait event. High waiting levels are caused by excessive
contention.
Session Waiting for Event Count

This metric represents the number of sessions waiting on a given wait event at the
sample time.
Metric Summary

Consecutive
8.1.7.4; Every After Every > Not Defined Not Defined 3 %value% sessions
9.0.1.x; Minute Sample are waiting for event
9.2.0.x %event%.
Multiple Thresholds
"Wait Event" object.
If warning or critical threshold values are currently set for any "Wait Event" object,
To specify or change warning or critical threshold values for each "Wait Event" object,

Waits by Wait Class
Data Source
select count(1)
User Action
Evaluate the various types of wait activity using the real-time and historical
performance monitoring capabilities of Enterprise Manager.
Waits by Wait Class

This metric category contains the waits by wait class metrics.
Average Users Waiting Count

This metric represents the average number of users that have made a call to the
database and that are waiting for an event, such as an I/O or a lock request, to
complete. If the number of users waiting on events increases, it indicates that either
more users are running, increasing workload, or that waits are taking longer, for
example when maximum I/O capacity is reached and I/O times increase.
Metric Summary

Consecutive
Version Key Frequency Frequency Operator Threshold Threshold Notification Alert Text
10.1.0.x class: Every 15 After Every > 10 Not 1 Not Defined
"Administrative" Minutes Sample Defined
"Application" Minutes Sample Defined
10.1.0.x class: "Cluster" Every 15 After Every > 30 Not 1 Not Defined
Minutes Sample Defined
10.1.0.x class: "Commit" Every 15 After Every > 30 Not 1 Not Defined
"Concurrency" Minutes Sample Defined
"Configuration" Minutes Sample Defined
10.1.0.x class: "Network" Every 15 After Every > 10 Not 1 Not Defined
10.1.0.x class: "Other" Every 15 After Every > 10 Not 1 Not Defined
10.1.0.x class: Every 15 After Every > Not Not 1 Not Defined
"Scheduler" Minutes Sample Defined Defined
10.1.0.x class: "System Every 15 After Every > Not Not 1 Not Defined
I/O" Minutes Sample Defined Defined
10.1.0.x class: "User I/O" Every 15 After Every > Not Not 1 Not Defined
Minutes Sample Defined Defined
Database 2-183
Waits by Wait Class
Multiple Thresholds
"Wait Class" object.
If warning or critical threshold values are currently set for any "Wait Class" object,
To specify or change warning or critical threshold values for each "Wait Class" object,
User Action
page.
Database Time Spent Waiting (%)

This metric represents the percentage of time that database calls spent waiting for an
event. Although there is no 'correct' value for this metric, it can be used to detect a
change in the operation of a system, for example, an increase in Database Time Spent
Waiting from 50% to 75%. ('No correct value' means that there is no single value that
can be applied to any database. The value is a characteristic of the system and the
applications running on the system.)
Metric Summary

Consecutive
Number of
Version Key Frequency Frequency Frequency Operator Threshold Threshold Notification Alert Text
10.1.0.x class: Every Every 15 After > 30 Not 1 Generated
"Admin Minute Minutes Every Defined By
istrative Sample Database
" Server
"Applic Minute Minutes Every Defined By
ation" Sample Database
Server
"Cluster Minute Minutes Every Defined By
" Sample Database
Server
"Commi Minute Minutes Every Defined By
t" Sample Database
Server
"Concur Minute Minutes Every Defined By
rency" Sample Database
Server

Waits by Wait Class
Table 2–256 (Cont.) Metric Summary Table

Consecutive
Number of
Version Key Frequency Frequency Frequency Operator Threshold Threshold Notification Alert Text
"Config Minute Minutes Every Defined By
uration" Sample Database
Server
"Netwo Minute Minutes Every Defined By
rk" Sample Database
Server
"Other" Minute Minutes Every Defined By
Sample Database
Server
10.1.0.x class: Every Every 15 After > Not Not 1 Generated
"Schedu Minute Minutes Every Defined Defined By
ler" Sample Database
Server
"System Minute Minutes Every Defined Defined By
I/O" Sample Database
Server
"User Minute Minutes Every Defined Defined By
I/O" Sample Database
Server
Database 2-185
Waits by Wait Class

3
Listener
You can use Enterprise Manager to manage Oracle Listener targets. From the
Enterprise Manager Listener home page, you can monitor key metrics that can help
determine the performance and availability of the listener and help you troubleshoot
potential performance problems.
General Status
This metric is a container for a set of metrics that provide general information about
the listener target.
Alias
The alias is an alternative name for the listener. On the Metric Detail page, you can see
the value of this metric only when you select one of the Real Time refresh options. The
alias also appears on the Listener home page.
Metric Summary
Collection
Target Version Frequency
Data Source
This metric is derived from the STATUS command of the Listener Control Utility. For
more information, see the section on Listener Administration in the Oracle Net Services
Administrator's Guide.
User Action
Not applicable.
Security
The value of this metric shows whether or not a password is required to run specific
commands with the Listener Control Utility.
Metric Summary
Listener 3-1
General Status
Collection
Data Source
User Action
Not applicable.
SID List
This metric lists the System Identifiers (SIDs) for the services monitored by the listener.
Metric Summary
Collection
Data Source
The list of SIDs for the listener is stored in the listener.ora configuration file.
User Action
Not applicable.
SNMP Status
This metric indicates whether or not the listener can respond to queries from an
SNMP-based network management system.
Metric Summary
Collection
Data Source
User Action
Not applicable.

General Status
Start Date
This metric represents the day and time when the listener was last started. On the
Metric Detail page, you can see the value of this metric only when you select one of the
Real Time refresh options. This metric also appears on the Enterprise Manager Listener
home page.
Metric Summary
Collection
Data Source
User Action
Not applicable.
TNS Address
This metric displays the protocal, host, and port information for the listener. On the
Metric Detail page, you can see the value of this metric only when you select one of the
Real Time refresh options. The TNS address also appears on the Listener home page.
Metric Summary
Collection
Data Source
The TNS address of the Listener is defined in the listener.ora configuration file. For
more information, see the Oracle Net Services Administrator's Guide.
User Action
Not applicable.
Trace Level
This metric represents the level of tracing currently enabled for the listener. Tracing
can be used to troubleshoot problems with the listener by saving additional
information to the trace file. For more information about the trace levels you can set
for the listener, see the information about the Listener Control Utility in the Oracle Net
Services Reference Manual.
Listener 3-3
Load
On the Metric Detail page, you can see the value of this metric only when you select
one of the Real Time refresh options.
Metric Summary
Collection
Data Source
User Action
Not applicable.
Version
The version of the listener software. On the Metric Detail page, you can see the value
of this metric only when you select one of the Real Time refresh options. This metric
also appears on the Enterprise Manager Listener home page.
Metric Summary
Collection
Data Source
User Action
Not applicable.
Load
This metric is a container for a set of metrics that provide you with information about
the number of connections supported by the Listener over a period of time.
Connections Established (per min)

This metric represents the average number of connections per minute that were
established with the listener.

Response
Metric Summary
Collection
Data Source
This metric is derived from the Listener Control Utility. For more information, see the
section on Listener Administration in the Oracle Net Services Administrator's Guide.
User Action
If you are noticing experiencing performance issues with the database or other services
supported by the listener, review the historical values of this metric to determine
whether or not the performance problems are caused by excessive load on the listener
or host.
Connections Refused (per min)

This metric represents the average number of connections that were refused per
minute. A connection can be refused for a variety of reasons, including situations
where the database or other listener service is down, or if the connection timed out.
Metric Summary
Collection
Data Source
This metric is derived from the Listener Control Utility. For more information, see the
section on Listener Administration in the Oracle Net Services Administrator's Guide.
User Action
If Enterprise Manager reports a high number of refused connections, check the
availability and performance of the database or other services supported by the
listener.
Response
This metric is a container for the Response and Status metrics that provide you with
performance information about the Listener.
Response Time (msec)

This metric represents the time (in milliseconds) that it takes for the Listener to
respond to a network request (ping).
Listener 3-5
Response
Metric Summary

Consecutive
All Every 5 After Every > 80 100 1 Listener response to
Versions Minutes Sample a TNS ping is
%value% msecs
Data Source
The value of this metric is derived using the TNSPING command. For mor
information about the TNSPING command, see the Oracle Net Services Administrator's
Guide.
User Action
If the Listener response time consistently exceeds the threshold, users are likely
experiencing performance issues while accessing the database or other services on this
host. Use the Enterprise Manager Central Console to review other performance
indicators, such as the overall health of your database and the response time of your
hosts and Web Applications.
Status
This metric returns a value of "1" if the Listener is up and running; it returns a 0 if the
Listener is unavailable.
Metric Summary

Consecutive
All Every 5 After Every = Not Defined 0 1 The listener is down:
Versions Minutes Sample %oraerr%.
Data Source
This metric is derived from the STATUS command in the Listener Control Utility. For
more information, see the Oracle Net Services Reference Manual.

Response
User Action
When the listener is down, users cannot access the database or other services on this
host. Review the troubleshooting information in Oracle Net Services Administrator's
Guide.
Listener 3-7
Response

Part II
Host Metrics
Part II contains the metrics associated with the following hosts:

■ Solaris
■ HP
■ Linux
■ HP Tru64
■ IBM AIX
■ Windows
Part II contains the following chapter:
■ Chapter 4, "Host"
4
Host
The host metrics provide description, data source, metric index (where applicable),
and user action information for each metric.
Aggregate Resource Usage Statistics (By Project)

This metric provides data on aggregate resource usage on a per project basis.
This metric is available only on Solaris version 9 and later.
Cumulative CPU Wait Time(Seconds)

The cumulative number of seconds that this process has spent Waiting for CPU over
its lifetime.
Metric Summary

Data Source
Solaris CIM Object Manager
User Action
Cumulative Data Page Fault Sleep Time(Seconds)

The cumulative number of seconds that this process has spent sleeping in Data Page
Faults over its lifetime.
Metric Summary
Host 4-1

Data Source
User Action
Cumulative Major Page Faults

The cumulative number of Major Page Faults engendered by the process over its
lifetime.
Metric Summary

Data Source
User Action
Cumulative Minor Page Faults

The cumulative number of Minor Page Faults engendered by the process over its
lifetime.
Metric Summary

Data Source
User Action

Cumulative Number Character IO (bytes) Read and Written

The cumulative number of character I/O bytes Read and Written by the process over
its lifetime.
Metric Summary

Data Source
User Action
Cumulative Number Of Blocks Read

The cumulative number of blocks Read by the process over its lifetime.
Metric Summary

Data Source
User Action
Cumulative Number Of Blocks Written

The cumulative number of blocks Written by the process over its lifetime.
Metric Summary

Host 4-3
Data Source
User Action
Cumulative Number of Involuntary Context Switches

The cumulative number of Involuntary Context Switches made by the process over its
lifetime.
Metric Summary

Data Source
User Action
Cumulative Number Of Messages Received

The cumulative number of Messages Received by the process over its lifetime.
Metric Summary

Data Source
User Action
Cumulative Number Of Messages Sent

The cumulative number of Messages Sent by the process over its lifetime.

Metric Summary

Data Source
User Action
Cumulative Number of Signals Received

The cumulative number of Signals taken by the process over its lifetime.
Metric Summary

Data Source
User Action
Cumulative Number of System Calls Made

The cumulative number of system calls made by the process over its lifetime.
Metric Summary

Data Source
User Action
Host 4-5
Cumulative Number of Voluntary Context Switches

The cumulative number of Voluntary Context Switches made by the process over its
lifetime.
Metric Summary

Data Source
User Action
Cumulative Project Lock-Wait Sleep Time(Seconds)

The cumulative number of seconds that this process has spent sleeping on User Lock
Waits over its lifetime.
Metric Summary

Data Source
User Action
Cumulative Project Other Sleep Time(Seconds)

The cumulative number of seconds that this process has spent sleeping in all other
ways over its lifetime.
Metric Summary


Data Source
User Action
Cumulative Stop Time(Seconds)

The cumulative number of seconds that this process has spent Stopped over its
lifetime.
Metric Summary

Data Source
User Action
Cumulative Swap Operations

The cumulative number of swap operations engendered by the process over its
lifetime.
Metric Summary

Data Source
User Action
Cumulative System Mode Time (seconds)

The cumulative number of seconds that this process has spent in System mode over its
lifetime.
Host 4-7
Metric Summary

Data Source
User Action
Cumulative System Page Fault Sleep Time(Seconds)

The cumulative number of seconds that this process has spent sleeping in System Page
Metric Summary

Data Source
User Action
Cumulative System Trap Time (seconds)

The cumulative number of seconds that this process has spent in System Traps over its
lifetime.
Metric Summary

Data Source
User Action

Cumulative Text Page Fault Sleep Time(Seconds)

The cumulative number of seconds that this process has spent sleeping in Text Page
Metric Summary

Data Source
User Action
Cumulative User Mode Time (seconds)

The cumulative number of seconds that this process has spent in User mode over its
lifetime.
Metric Summary

Data Source
User Action
Number of Processes Owned by Project

The number of processes owned by the project measured in the aggregate.
Metric Summary

Host 4-9
Data Source
User Action
Project CPU Time (%)

The percent CPU time used by the process.
Metric Summary

Data Source
User Action
Project Process Memory Size (%)

The ratio of the process resident set size to physical memory.
Metric Summary

Data Source
User Action
Project's Total Process Heap Size(KiloBytes)

The total number of KiloBytes of memory consumed by the process heap at the time
that it is sampled.

Metric Summary

Data Source
User Action
Project's Total Process Resident Set Size(KiloBytes)

The resident set size of the process in kilobytes.
Metric Summary

Data Source
User Action
Project's Total Process Virtual Memory Size(KiloBytes)

The size of the process virtual address space in kilobytes.
Metric Summary

Data Source
User Action
Host 4-11
Aggregate Resource Usage Statistics(By User)
Status
The metric indicates whether the host is reachable or not. A host could be unreachable
due to various reasons. The network is down or the Management Agent on the host is
down (which could be because the host itself is shutdown).
User Action
Total Number of Threads in Project's Processes

The number of threads active in the current Process.
Metric Summary

Data Source
User Action

This metric provides data on aggregate resource usage on a per user basis.
Cumulative CPU Wait Time(Seconds)

The cumulative number of seconds that this process has spent Waiting for CPU over
its lifetime.
Metric Summary

Data Source
User Action

Cumulative Data Page Fault Sleep Time(Seconds)

The cumulative number of seconds that this process has spent sleeping in Data Page
Metric Summary

Data Source
User Action
Cumulative Major Page Faults

The cumulative number of Major Page Faults engendered by the process over its
lifetime.
Metric Summary

Data Source
User Action
Cumulative Minor Page Faults

The cumulative number of Minor Page Faults engendered by the process over its
lifetime.
Metric Summary

Host 4-13
Data Source
User Action
Cumulative Number Character IO (bytes) Read and Written

The cumulative number of character I/O bytes Read and Written by the process over
its lifetime.
Metric Summary

Data Source
User Action
Cumulative Number Of Blocks Read

The cumulative number of blocks Read by the process over its lifetime.
Metric Summary

Data Source
User Action
Cumulative Number Of Blocks Written

The cumulative number of blocks Written by the process over its lifetime.

Metric Summary

Data Source
User Action
Cumulative Number of Involuntary Context Switches

The cumulative number of Involuntary Context Switches made by the process over its
lifetime.
Metric Summary

Data Source
User Action
Cumulative Number Of Messages Received

The cumulative number of Messages Received by the process over its lifetime.
Metric Summary

Data Source
User Action
Host 4-15
Cumulative Number Of Messages Sent

The cumulative number of Messages Sent by the process over its lifetime.
Metric Summary

Data Source
User Action
Cumulative Number of Signals Received

The cumulative number of Signals taken by the process over its lifetime.
Metric Summary

Data Source
User Action
Cumulative Number of System Calls Made

The cumulative number of system calls made by the process over its lifetime.
Metric Summary

Data Source

User Action
Cumulative Number of Voluntary Context Switches

The cumulative number of Voluntary Context Switches made by the process over its
lifetime.
Metric Summary

Data Source
User Action
Cumulative Stop Time(Seconds)

The cumulative number of seconds that this process has spent Stopped over its
lifetime.
Metric Summary

Data Source
User Action
Cumulative Swap Operations

The cumulative number of Swap Operations engendered by the process over its
lifetime.
Metric Summary
Host 4-17

Data Source
User Action
Cumulative System Mode Time (seconds)

The cumulative number of seconds that this process has spent in System mode over its
lifetime.
Metric Summary

Data Source
User Action
Cumulative System Page Fault Sleep Time(Seconds)

The cumulative number of seconds that this process has spent sleeping in System Page
Metric Summary

Data Source
User Action

Cumulative System Trap Time (seconds)

The cumulative number of seconds that this process has spent in System Traps over its
lifetime.
Metric Summary

Data Source
User Action
Cumulative Text Page Fault Sleep Time(Seconds)

The cumulative number of seconds that this process has spent sleeping in Text Page
Metric Summary

Data Source
User Action
Cumulative User Lock-Wait Sleep Time(Seconds)

The cumulative number of seconds that this process has spent sleeping on User Lock
Waits over its lifetime.
Metric Summary

Host 4-19
Data Source
User Action
Cumulative User Mode Time (seconds)

The cumulative number of seconds that this process has spent in User mode over its
lifetime.
Metric Summary

Data Source
User Action
Cumulative User Other Sleep Time(Seconds)

The cumulative number of seconds that this process has spent sleeping in all other
ways over its lifetime.
Metric Summary

Data Source
User Action
Number of Processes Owned by User

The number of processes owned by the user measured in the aggregate.

Metric Summary

Data Source
User Action
Total Number of Threads in User's Processes

The number of threads active in the current Process.
Metric Summary

Data Source
User Action
User CPU Time (%)

The percent CPU time used by the process.
Metric Summary

Data Source
User Action
Host 4-21
User Process Memory Size (%)

The ratio of the process resident set size to physical memory.
Metric Summary

Data Source
User Action
User's Total Process Heap Size(KiloBytes)

The total number of kilobytes of memory consumed by the process heap at the time
that it is sampled.
Metric Summary

Data Source
User Action
User's Total Process Resident Set Size(KiloBytes)

The resident set size of the process in kilobytes.
Metric Summary


Buffer Activity
Data Source
User Action
User's Total Process Virtual Memory Size(KiloBytes)

The size of the process virtual address space in kilobytes.
Metric Summary

Data Source
User Action
Buffer Activity
The Buffer Activity metric provides information about OS memory buffer usage. This
metric reports buffer activity for transfers, accesses, and cache (kernel block buffer
cache) hit ratios per second.
The data sources for this metric category include the following:
Host Data Source

Solaris sar command
HP sar command
Linux not available
HP Tru64 table() system call
IBM AIX sar command
Windows not available
Buffer Cache Read Hit Ratio (%)

Represents the number of reads from block devices to buffer cache as a percentage of
all buffer reads.
Data Source
The data sources for this metric include the following:
Host 4-23
Buffer Activity
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command
User Action
Buffer Cache Reads (per second)

Represents the number of reads performed on the buffer cache per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
HP Tru64 not available
IBM AIX sar command
User Action
Buffer Cache Write Hit Ratio (%)

Represents the number of writes from block devices to buffer cache as a percentage of
all buffer writes.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

Buffer Activity
User Action
Buffer Cache Writes (per second)

Represents the number of writes performed on the buffer cache per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command
User Action
Physical I/O Reads (per second)

Represents the number of reads per second from character devices using physical I/O
mechanisms.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command
User Action
Physical I/O Writes (per second)

Represents the number of writes per second from character devices using physical I/O
mechanisms.
Host 4-25
Buffer Activity
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command
User Action
Physical Reads (per second)

Represents the number of reads performed per second from block devices to the
system buffer cache.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command
User Action
Physical Writes (per second)

Represents the number of physical writes from block devices to the system buffer
cache.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available

CPU Usage
Host Data Source

IBM AIX sar command
User Action
CPU Usage
The CPU Usage metric provides information about the percentage of time the CPU
was in various states, for example, idle state and wait state. The metric also provides
information about the percentage of CPU time spent in user and system mode. All
data is per-CPU in a multi-CPU system.
On HP Tru64, this information is available as the cumulative total for all the CPUs and
not for each CPU which is monitored in the Load metric. Hence, this metric is not
available on HP Tru64.
Host Data Source

Solaris kernel statistics (class cpu_stat)
HP pstat_getprocessor() system call
Linux /proc/stat
IBM AIX oracle_kstat() system call
Windows performance data counters
CPU Idle Time (%)

Represents the percentage of time that the CPU was idle and the system did not have
an outstanding disk I/O request. This metric checks the percentage of processor time
in idle mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0,
CPU0, or * (for all CPUs on the system).
Metric Summary

Data Source
Host Data Source

Host 4-27
CPU Usage
Host Data Source

Linux /proc/stat
User Action
CPU Interrupt Time (%)

Represents the percentage of time that the CPU receives and services hardware
interruptions during representative intervals. This metric checks the percentage of
processor time in interrupt mode for the CPU(s) specified by the Host CPU parameter,
such as cpu_stat0, CPU0, or * (for all CPUs on the system).
This metric is available only on Windows.
Metric Summary

Data Source
The data source for this metric are Performance Data counters.
User Action
CPU System Time (%)

Represents the percentage of time that the CPU is running in system mode (kernel).
This metric checks the percentage of processor time in system mode for the CPU(s)
specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on
the system).
Metric Summary

Data Source

CPU Usage
Host Data Source

Linux /proc/stat
User Action
CPU User Time (%)

Represents the portion of processor time running in user mode. This metric checks the
percentage of processor time in user mode for the CPU(s) specified by the Host CPU
parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).
Metric Summary

Data Source
Host Data Source

Linux /proc/stat
User Action
CPU Wait Time (%)

Represents the percentage of time that the CPU was idle during which the system had
an outstanding disk I/O request. This metric checks the percentage of processor time
in wait mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0,
CPU0, or * (for all CPUs on the system).
Host 4-29
Disk Activity
Metric Summary

Data Source
Host Data Source

Linux /proc/stat
User Action
Disk Activity
The Disk Activity metric monitors the hard disk activity on the target being
monitored. For each device on the system, this metric provides information about
access to the device. This information includes: device name, disk utilization, write
statistics, and read statistics for the device.
Host Data Source

Solaris kernel statistics (class kstat_io)
HP sar command
Linux iostat command
Average Disk I/O Service Time (ms)

Represents the sum of average wait time and average run time.
Metric Summary

Disk Activity

Consecutive
All Every 15 After Every > Not Defined Not Defined 6 Average service time
Versions Minutes Sample for disk %keyvalue%
is %value% ms
Multiple Thresholds
"Disk Device" object.
If warning or critical threshold values are currently set for any "Disk Device" object,
To specify or change warning or critical threshold values for each "Disk Device" object,
Data Source
Host Data Source

HP sar command
User Action
This number should be low. A high number can indicate a disk that is slow due to
excessive load or hardware issues. See also the CPU in IO-Wait (%) metric.
Average Disk I/O Wait Time (ms)

Represents the average time spent by the command waiting on the queue for getting
executed.
Metric Summary
Host 4-31
Disk Activity

Consecutive
All Every 15 After Every > Not Defined Not Defined 6 Average wait time
Versions Minutes Sample for disk %keyvalue%
is %value% ms
Multiple Thresholds
Data Source
Host Data Source

HP sar command
User Action
A high figure indicates a slow disk. Use the OS iostat -xn command to check wait time
and service time for local disks and NFS mounted file systems. See also the CPU in
IO-Wait (%) metric.
Average Outstanding Disk I/O Requests

Represents the average number of commands waiting for service (queue length).
Metric Summary

Data Source

Disk Activity
Host Data Source

HP sar command
User Action
Average Run Time (ms)

Represents the average time spent by the command on the active queue waiting for its
execution to be completed.
Metric Summary

Data Source
Host Data Source

HP sar command
User Action
Disk Block Writes (per second)

Represents the number of blocks (512 bytes) written per second.
Metric Summary
Host 4-33
Disk Activity

Data Source
Host Data Source

HP sar command
User Action
Disk Blocks Reads (per second)

Represents the number of blocks (512 bytes) read per second.
Metric Summary

Data Source
Host Data Source

HP not available
User Action
Disk Reads (per second)

Represents the disk reads per second for the specified disk device.

Disk Activity
Metric Summary

Data Source
Host Data Source

HP not available
User Action
Disk Utilization (%)

Represents the amount of disk space utilization as a percentage of capacity.
Metric Summary

Consecutive
All Every 15 After Every > 80 95 6 Disk Utilization for
Versions Minutes Sample %keyValue% is
%value%%%
Multiple Thresholds
Host 4-35
Disk Device Errors
Data Source
Host Data Source

HP sar command
User Action
Disk Writes (per second)

Represents the disk writes per second for the specified disk device.
Metric Summary

Data Source
Host Data Source

HP not available
User Action
Disk Device Errors

The Disk Device Errors metric provides the number of errors on the disk device.
This metric is available only Solaris.

Disk Device Errors
Hard Errors
Represents the error count of hard errors encountered while accessing the disk. Hard
errors are considered serious and may be traced to misconfigured or bad disk devices.
This metric is available only on Solaris.
Metric Summary

Data Source
The data for this column is obtained from the OS iostat -e command.
User Action
Soft Errors
Represents the error count of soft errors encountered while accessing the disk. Soft
errors are synonymous to warnings.
Metric Summary

Data Source
User Action
Total
Represents the sum of all errors on the particular device.
Metric Summary

Host 4-37
File Access System Calls
Data Source
The data for this column is obtained from the OS iostat -e command on the particular
device.
User Action
Transport Errors
Represents the error count of network errors encountered. This generally indicates a
problem with the network layer.
Metric Summary

Data Source
User Action

The File Access System Calls metric provides information about the usage of file access
system calls.
Blocks Read by Directory Search Routine (per second)

Represents the number of file system blocks read per second performing direct lookup.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command
The OS sar command is used to sample cumulative activity counters maintained by

the OS. The data is obtained by sampling system counters once in a five-second

interval. The results are essentially the number of lookuppn() calls made over this
five-second period divided by five.
User Action
iget() Calls (per second)

Represents the number of system iget() calls made per second. iget is a file access
system routine.
Data Source
Host Data Source

Solaris kernel memory structure (class cpu_vminfo)
HP sar command
Linux not available
IBM AIX kernel memory structure (class cpu_vminfo)
User Action
This data is obtained using the OS sar command, which is used to sample cumulative
activity counters maintained by the OS. The data is obtained by sampling system
counters once in a five-second interval. The results are essentially the number of iget()
calls made over this five-second period divided by five.
lookuppn() Calls (per second)

Represents the number of file system lookuppn() (pathname translation) calls made
per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

Host 4-39
Filesystems
interval. The results are essentially the number of lookuppn() calls made over this
User Action
Filesystems
The Filesystems metrics provide information about local file systems on the computer.
Filesystem
Represents the name of the disk device resource.
Metric Summary

Data Source
Host Data Source

Solaris /etc/mnttab file entries
HP bdf command
Linux df command
HP Tru64 df command
IBM AIX /etc/mnttab file entries
User Action
Filesystem Size (MB)

Represents the total space (in megabytes) allocated in the file system.
Metric Summary

Data Source

Filesystems
Host Data Source

Solaris vminfo system
HP bdf command
Linux df command
HP Tru64 df command
IBM AIX stavfs() system call.
Windows Windows API
User Action
Filesystem Space Available (%)

Represents the percentage of total space allocated in the file system.
Metric Summary

Consecutive
All Every 15 After Every < 20 5 1 Filesystem
Versions Minutes 24 Samples %keyValue% has
only %value%%%
available space
Multiple Thresholds
"Mount Point" object.
If warning or critical threshold values are currently set for any "Mount Point" object,
To specify or change warning or critical threshold values for each "Mount Point"
Data Source
Host Data Source

Solaris statvfs() system call
HP bdf command
Linux df command
Host 4-41
Inventory
Host Data Source

HP Tru64 df command
IBM AIX statvfs() system call
Windows Windows API
User Action
Use the OS du -k command to check which directories are taking up the most space
(du -k|sort -rn).
Filesystem Utilization (MB)

Represents the total space, expressed in megabytes, allocated in the file system.
Data Source
The data source for this metric is GetDiskFreeSpaceEx.
User Action
Inventory
The Inventory metric is used for periodic collection of host configuration information.
By default, host configuration is collected every 24 hours.
Kernel Memory
The Kernel Memory metric provides information on kernel memory allocation (KMA)
activities.
This metric is implemented only on Solaris.
Failed Requests for Large Kernel Memory

This metric represents the number of requests for large memory that failed, that is,
requests that were not satisfied.
Data Source
counters once in a five-second interval.
User Action

Kernel Memory
Failed Requests for Oversize Kernal Memory

This metric represents the number of oversized requests made that could not be
satisfied. Oversized memory requests are allocated dynamically so there is no pool for
such requests.
Data Source
User Action
Failed Requests for Small Kernel Memory

This metric represents the number of requests for small memory that failed, that is,
requests that were not satisfied.
Data Source
User Action
KMA Available for Large Memory Requests (Bytes)

This metric represents the amount of memory, in bytes, the kernel memory allocation
(KMA) has for the large pool; the pool used for allocating and reserving large memory
requests.
Data Source
User Action
KMA for Oversize Memory Requests (Bytes)

This metric represents the amount of memory allocated for oversized memory
requests.
Host 4-43
Kernel Memory
Data Source
User Action
KMA for Small Memory Requests

This metric represents the amount of memory, in bytes, the Kernel Memory Allocation
has for the small pool; the pool used for allocating and reserving small memory
requests.
Data Source
User Action
Memory Allocated for Large Memory Requests (Bytes)

This metric represents the amount of memory, in bytes, the kernel allocated to satisfy
large memory requests.
Data Source
User Action
Memory Allocated for Small Memory Requests (Bytes)

This metric represents the amount of memory, in bytes, the kernel allocated to satisfy
small memory requests.
Data Source
User Action

Load
Load
The Load metric provides information about the number of runnable processes on the
system run queue. If this is greater than the number of CPU's on the system, then
excess load exists.
Host Data Source

Solaris kernel statistics
HP pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(),
getutent(), pstat_getvminfo() system calls
Linux uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat
HP Tru64 table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands
IBM AIX oracle_kstat(), getutent(), getproc(), sysconf() system calls
CPU in IO-Wait (%)

Represents the average number of jobs waiting for I/O in the last interval.
Metric Summary

Consecutive
All Every 5 After Every > 40 80 6 CPU I/O Wait is
Versions Minutes Sample %value%%%
Data Source
Host Data Source

Host 4-45
Load
User Action
A high percentage of I/O wait can indicate a hardware problem, a slow NFS server, or
poor load-balancing among local file systems and disks. Check the system messages
log for any hardware errors. Use the iostat -xn command or the nfsstat -c (NFS
client-side statistics) command or both to determine which disks or file systems are
slow to respond. Check to see if the problem is with one or more swap partitions, as
lack of swap or poor disk load balancing can cause these to become overloaded.
Depending on the specific problem, fixes may include: NFS client or server tuning,
hardware replacement, moving applications to other file systems, adding swap space,
or restructuring a file system for better performance.
CPU in System Mode (%)

For UNIX-based platforms, this metric represents the amount of CPU being used in
SYSTEM mode as a percentage of total CPU processing power.
For Windows, this metric represents the percentage of time the process threads spent
executing code in privileged mode.
Metric Summary

Data Source
Host Data Source

User Action
CPU in User Mode (%)

For UNIX-based platforms, this metric represents the amount of CPU being used in
USER mode as a percentage of total CPU processing power.
For Windows, this metric represents the percentage of time the processor spends in the
user mode. This metric displays the average busy time as a percentage of the sample
time.

Load
Metric Summary

Data Source
Host Data Source

User Action
CPU Interrupt Time (%)

Represents the percentage of time the processor spends receiving and servicing
hardware interrupts during sample intervals. This value is an indirect indicator of the
activity of devices that generate interrupts, such as the system clock, the mouse, disk
drivers, data communication lines, network interface cards, and other peripheral
devices. These devices normally interrupt the processor when they have completed a
task or require attention. Normal thread execution is suspended during interrupts.
Most system clocks interrupt the processor every 10 milliseconds, creating a
background of interrupt activity. Suspends normal thread execution during interrupts.
Metric Summary

Consecutive
All Every After Every > 40 80 6 CPU % Interrupt
Versions Minute Sample Time is %value%%%
Host 4-47
Load
Data Source
The data source for this metric is Performance Data counters.
User Action
None
CPU Queue Length

Processor Queue Length is the number of ready threads in the processor queue. There
is a single queue for processor time even on computers with multiple processors. A
sustained processor queue of less than 10 threads per processor is normally acceptable,
dependent on the workload.
Metric Summary

Consecutive
All Every After Every > 10 20 6 CPU Queue Length
Versions Minute Sample is %value%
Data Source
The data source for this metric is Performance Data counters.
User Action
A consistently high value indicates a number of CPU bound tasks. This information
should be corelated with other metrics such as Page Transfer Rate. Tuning the system,
accompanied with additional memory, should help.
CPU Utilization (%)

For UNIX-based platforms, this metric represents the amount of CPU utilization as a
percentage of total CPU processing power available.
For Windows, this metric represents the percentage of time the CPU spends to execute
a non-Idle thread. CPU Utilization (%) is the primary indicator of processor activity.
Metric Summary

Load

Consecutive
All Every 5 After Every > 80 95 6 CPU Utilization is
Data Source
Host Data Source

User Action
Free Memory (%)

Represents the amount of free memory as a percentage of total memory.
Metric Summary

Data Source
Host Data Source

Windows Windows API
Host 4-49
Load
User Action
Longest Service Time (ms)

Represents the maximum of the average service time of all disks. Units are represented
in milliseconds.
Metric Summary

Data Source
Host Data Source

User Action
Memory Page Scan Rate (per second)

For UNIX-based systems, this metric represents the number of pages per second
scanned by the page stealing daemon.
For Windows, this metric represents the rate at which pages are read from or written
to disk to resolve hard page faults. The metric is a primary indicator of the kinds of
faults that cause system-wide delays.
Metric Summary

Load

Consecutive
All Every 5 After Every > Not Defined Not Defined 6 Page scan rate is
Versions Minutes Sample %value% /sec
Data Source
Host Data Source

User Action
If this number is zero or close to zero, then you can be sure the system has sufficient
memory. If scan rate is always high, then adding memory will definitely help.
Memory Utilization (%)

Represents the amount of free memory as a percentage of total memory.
Metric Summary

Consecutive
All Every 5 After Every > 99 Not Defined 6 Memory Utilization
Versions Minutes Sample is %value%%%
Data Source
Host Data Source

Host 4-51
Load
Host Data Source

Windows Windows API
User Action
Page Transfers Rate

Indicates the rate at which pages are read from or written to disk to resolve hard page
faults. It is a primary indicator of the kinds of faults that cause systemwide delays. It is
counted in numbers of pages. It includes pages retrieved to satisfy faults in the file
system cache (usually requested by applications) non-cached mapped memory files.
Metric Summary

Consecutive
All Every After Every > Not Defined Not Defined 6 Page transfers rate is
Versions Minute Sample %value% /sec
Data Source
The data source for this metric is Windows Performance counters.
User Action
High transfer rates indicate a memory contention. Adding memory would help.
Run Queue Length (1 minute average)

Represents the average number of processes in memory and subject to be run in the
last interval. This metric checks the run queue.
Metric Summary

Load

Data Source
Host Data Source

User Action
Check the load on the system using the UNIX uptime or top commands. Also, check
for processes using too much CPU time by using the top and ps -ef commands. Note
that the issue may be a large number of instances of one or more processes, rather than
a few processes each taking up a large amount of CPU time. Kill processes using
excessive CPU time.

Metric Summary

Data Source
Host Data Source

Host 4-53
Load
User Action
excessive CPU time.

Metric Summary

Consecutive
All Every 5 After Every > 10 20 6 CPU Load is
Versions Minutes Sample %value%
Data Source
Host Data Source

User Action
excessive CPU time.
Swap Utilization (%)

For UNIX-based platforms, this metric represents the percentage of swapped memory
in use for the last interval.
For Windows, this metric represents the percentage of page file instance used.

Load
Metric Summary

Consecutive
All Every 5 After Every > 80 95 6 Swap Utilization is
Data Source
Host Data Source

Windows Windows API and Performance data counters
User Action
For UNIX-based platforms, check the swap usage using the UNIX top command or the
Solaris swap -l command. Additional swap can be added to an existing file system by
creating a swap file and then adding the file to the system swap pool. (See
documentation for your UNIX OS). If swap is mounted on /tmp, space can be freed by
removing any junk files in /tmp. If it is not possible to add file system swap or free up
enough space, additional swap will have to be added by adding a raw disk partition to
the swap pool. See UNIX documentation for procedures.
For Windows, check the page file usage and add an additional page file if current
limits are insufficient.
Total I/O (per second)

Represents the rate of I/O (read and write) operations, calculated from all disks.
Metric Summary

Host 4-55
Load
Data Source
Host Data Source

User Action
Total Processes
Represents the total number of processes currently running on the system. This metric
checks the number of processes running on the system.
Metric Summary

Data Source
Host Data Source

User Action
Total Swap, Kilobytes

Total amount of page file space available to be allocated by processes. Paging files are
shared by all processes and the lack of space in paging files can prevent processes from
allocating memory.

Load
Data Source
The data source for this metric are Performance Data counters and Windows API
GlobalMemoryStatusEx.
User Action
Total Users
Represents the total number of users currently logged into the system. This metric
checks the number of users running on the system.
Metric Summary

Data Source
Host Data Source

User Action
Used Swap, Kilobytes

Represents the size in kilobytes of the page file instance used.
Data Source
The data source for this metric are Performance Data counters and Windows API
GlobalMemoryStatusEx.
User Action
Host 4-57
Message and Semaphore Activity
Message and Semaphore Activity

The Message and Semaphore Activity metric provides information about the message
and semaphore activity of the host system being monitored.
msgrcv() System Calls (per second)

Represents the number of msgrcv system calls made per second. The msgrcv system
call reads a message from one queue to another user-defined queue.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux ipcs command
HP Tru64 ipcs command
IBM AIX sar command
User Action
semop() System Calls (per second)

Represents the number of semop system calls made per second. The semop system call
is used to perform semaphore operations on a set of semaphores.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux ipcs command
HP Tru64 ipcs command
IBM AIX sar command
User Action

Network Interfaces
Network Interfaces
The Network Interfaces metric includes input errors and interface collisions on the
network interface. The following network interfaces are supported: le, hme, qfe, ge,
and fddi.
Host Data Source

Solaris kernel memory structures (kstat)
HP netstat, lanscan, and lanadmin commands
Linux netstat command and /proc/net/dev
HP Tru64 netstat command
Network Interface Input Errors (%)

Represents the number of input errors, per second, encountered on the device for
unsuccessful reception due to hardware/network errors. This metric checks the rate of
input errors on the network interface specified by the network device names
parameter, such as le0 or * (for all network interfaces).
Metric Summary

Data Source
Host Data Source

User Action
Use the OS netstat -i command to check the performance of the interface. Also, check
the system messages file for messages relating to duplex setting by using the OS grep
-i command and searching for the word 'duplex'.
Host 4-59
Network Interfaces
Network Interface Collisions (%)

Represents the number of collisions per second. This metric checks the rate of
collisions on the network interface specified by the network device names parameter,
such as le0 or * (for all network interfaces).
Metric Summary

Data Source
Host Data Source

User Action
Network Interface Combined Utilization (%)

Represents the percentage of network bandwidth being used by reading and writing
from and to the network for full-duplex network connections.
Metric Summary

Consecutive
All Every 5 After Every > Not Defined Not Defined 6 Network utilization
Versions Minutes Sample for %keyvalue% is
%value%%%
Multiple Thresholds
"Network Interface Name" object.

Network Interfaces
If warning or critical threshold values are currently set for any "Network Interface
Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Network Interface
Name" object, use the Edit Thresholds page. See the Editing Thresholds topic in the
Data Source
Host Data Source

User Action
Network Interface Output Errors (%)

Represents the number of output errors per second. This metric checks the rate of
output errors on the network interface specified by the network device names
parameter, such as le0 or * (for all network interfaces).
Metric Summary

Data Source
Host Data Source

Host 4-61
Network Interfaces
User Action
Use the OS netstat -i command to check the performance of the interface. Also, check
the system messages file for messages relating to duplex setting by using the OS grep
-i command and searching for the word 'duplex'.
Network Interface Read (MB/s)

Represents the amount of megabytes per second read from the specific interface.
Metric Summary

Data Source
Host Data Source

IBM AIX not available
User Action
Network Interface Read Utilization (%)

Represents the amount of network bandwidth being used for reading from the
network as a percentage of total read capacity.
Metric Summary

Data Source
Host Data Source


Network Interfaces
Host Data Source

User Action
Network Interface Write (MB/s)

Represents the amount of megabytes per second written to the specific interface.
Metric Summary

Data Source
Host Data Source

User Action
Network Interface Write Utilization (%)

Represents the amount of network bandwidth being used for writing to the network
as a percentage of total read capacity.
Metric Summary

Host 4-63
Paging Activity
Data Source
Host Data Source

User Action
Paging Activity
The Paging Activity metric provides the amount of paging activity on the system.
Host Data Source

Solaris kernel statistics (class misc cpu_stat)
HP pstat_getvminfo() system call
Linux sar command
HP Tru64 table() system call and vmstat command
Address Translation Page Faults (per second)

Represents the minor page faults by way of hat_fault() per second. This metric checks
the number of faults for the CPU(s) specified by the Host CPU(s) parameter, such as
cpu_stat0 or * (for all CPUs on the system).
Metric Summary

Data Source
Host Data Source


Paging Activity
Host Data Source

Linux not available
User Action
Cache Faults (per second)

Cache Faults/sec is the rate at which faults occur when a page sought in the file
system cache is not found and must be retrieved from elsewhere in memory (a soft
fault) or from disk (a hard fault). The file system cache is an area of physical memory
that stores recently used pages of data for applications. Cache activity is a reliable
indicator of most application I/O operations. This metric shows the number of faults,
without regard for the number of pages faulted in each operation.
Metric Summary

Data Source
User Action
Copy-on-write Faults (per second)

Copy-on-Write faults/sec is the rate at which page faults are caused by attempts to
write that have been satisfied by coping of the page from elsewhere in physical
memory. This is an economical way of sharing data since pages are only copied when
they are written to; otherwise, the page is shared. This metric shows the number of
copies, without regard for the number of pages copied in each operation.
Metric Summary

Host 4-65
Paging Activity
Data Source
User Action
Demand Zero Faults (per second)

Demand Zero Faults/sec is the rate at which a zeroed page is required to satisfy the
fault. Zeroed pages, pages emptied of previously stored data and filled with zeros, are
a security feature of Windows that prevent processes from seeing data stored by earlier
processes that used the memory space. Windows maintains a list of zeroed pages to
accelerate this process. This metric shows the number of faults, without regard to the
number of pages retrieved to satisfy the fault.
Metric Summary

Data Source
User Action
igets with Page Flushes(%)

Represents the percentage of UFS inodes taken off the freelist by iget which had
reusable pages associated with them. These pages are flushed and cannot be reclaimed
by processes.
Metric Summary

Data Source
Host Data Source

HP not available
Linux not available

Paging Activity
Host Data Source

User Action
Page Faults (per second)

Page Faults/sec is the average number of pages faulted per second. It is measured in
number of pages faulted per second because only one page is faulted in each fault
operation, hence this is also equal to the number of page fault operations. This metric
includes both hard faults (those that require disk access) and soft faults (where the
faulted page is found elsewhere in physical memory.) Most processors can handle
large numbers of soft faults without significant consequence. However, hard faults,
which require disk access, can cause significant delays.
Metric Summary

Data Source
User Action
Page Faults from Software Lock Requests

Represents the number of protection faults per second. These faults occur when a
program attempts to access memory it should not access, receives a segmentation
violation signal, and dumps a core file. This metric checks the number of faults for the
CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on
the system).
Metric Summary

Data Source
Host 4-67
Paging Activity
Host Data Source

HP not available
Linux not available
User Action
Page-in Requests (per second)

For UNIX-based systems, represents the number of page read ins per second (read
from disk to resolve fault memory references) by the virtual memory manager. Along
with Page Outs, this statistic represents the amount of real I/O initiated by the virtual
memory manager. This metric checks the number of page read ins for the CPU(s)
specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the
system).
For Windows, this metric is the rate at which the disk was read to resolve hard page
faults. It shows the number of reads operations, without regard to the number of pages
retrieved in each operation. Hard page faults occur when a process references a page
in virtual memory that is not in working set or elsewhere in physical memory, and
must be retrieved from disk. This metric is a primary indicator of the kinds of faults
that cause systemwide delays. It includes read operations to satisfy faults in the file
system cache (usually requested by applications) and in non-cached mapped memory
files.
Metric Summary

Data Source
Host Data Source

Linux not available

Paging Activity
User Action
Page-out Requests (per second)

For UNIX-based systems, represents the number of page write outs to disk per second.
This metric checks the number of page write outs for the CPU(s) specified by the Host
CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).
For Windows, this metric is the rate at which pages are written to disk to free up space
in physical memory. Pages are written to disk only if they are changed while in
physical memory, so they are likely to hold data, not code. This metric shows write
operations, without regard to the number of pages written in each operation.
Metric Summary

Data Source
The data source for this metric category include the following:
Host Data Source

Linux not available
HP Tru64 vmstat command
User Action
Pages Paged-in (per second)

For UNIX-based systems, represents the number of pages paged in (read from disk to
resolve fault memory references) per second. This metric checks the number of pages
paged in for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or *
(for all CPUs on the system).
For Windows, this metric is the rate at which pages are read from disk to resolve hard
page faults. Hard page faults occur when a process refers to a page in virtual memory
that is not in its working set or elsewhere in physical memory, and must be retrieved
from disk. When a page is faulted, the system tries to read multiple contiguous pages
into memory to maximize the benefit of the read operation.
Metric Summary
Host 4-69
Paging Activity

Data Source
Host Data Source

Linux sar command
User Action
Pages Paged-out (per second)

For UNIX-based systems, represents the number of pages written out (per second) by
the virtual memory manager. Along with Page Outs, this statistic represents the
amount of real I/O initiated by the virtual memory manager. This metric checks the
number of pages paged out for the CPU(s) specified by the Host CPU(s) parameter,
such as cpu_stat0 or * (for all CPUs on the system).
For Windows, this metric is the rate at which pages are written to disk to free up space
in physical memory. Pages are written back to disk only if they are changed in physical
memory, so they are likely to hold data, not code. A high rate of pages output might
indicate a memory shortage. Windows writes more pages back to disk to free up space
when physical memory is in short supply.
Metric Summary

Data Source
Host Data Source

Linux sar command
HP Tru64 vmstat command

Paging Activity
Host Data Source

User Action
Pages Put on Freelist by Page Stealing Daemon (per second)

Represents the number of pages that are determined unused, by the pageout daemon
(also called the page stealing daemon), and put on the list of free pages.
Metric Summary

Data Source
Host Data Source

Linux not available
User Action
Pages Scanned by Page Stealing Daemon (per second)

Represents the scan rate is the number of pages per second scanned by the page
stealing daemon.
Metric Summary

Data Source
Host 4-71
Process, Inode, File Tables Statistics
Host Data Source

Linux not available
User Action
If this number is zero or closer to zero, then you can be sure the system has sufficient
memory. If the number is always high, then adding memory will definitely help.
Transition Faults (per second)

Transition Faults/sec is the rate at which page faults are resolved by recovering pages
that were being used by another process sharing the page, or were on the modified
page list or the standby list, or were being written to disk at the time of the page fault.
The pages were recovered without additional disk activity. Transition faults are
counted in numbers of faults; because only one page is faulted in each operation, it is
also equal to the number of pages faulted.
Metric Summary

Data Source
User Action

The Process, Inode, File Tables Stats metric provides information about the process,
inode, and file tables status.
Host Data Source

Solaris sar command
HP sar command
Linux sar command

Host Data Source

IBM AIX sar command
File Table Overflow Occurrences

Represents the number of times the system file table overflowed, that is, the number of
times that the OS could not find any available entries in the table in the sampling
period chosen to collect the data.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux sar command
IBM AIX sar command

interval.
User Action
Inode Table Overflow Occurrences

Represents the number of times the inode table overflowed, that is, the number of
times the OS could not find any available inode table entries.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
Host 4-73

interval.
User Action
Maximum Size of Inode Table

Represents the maximum size of the inode table.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux sar command
IBM AIX sar command

interval.
User Action
Maximum Size of Process Table

Represents the maximum size of the process table.
Data for this column is not available on Linux.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command


the OS. The data is obtained by sampling once in a five-second interval.
User Action
Maximum Size of System File Table

Represents the maximum size of the system file table.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux sar command
IBM AIX sar command

interval.
User Action
Process Table Overflow Occurrences

Represents the number of times the process table overflowed, that is, the number of
times the OS could not find any process table entries in a five-second interval.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
User Action
Host 4-75
Size of Inode Table

Represents the current size of the inode table.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux sar command
IBM AIX sar command

interval.
User Action
Size of Process Table

Represents the current size of the process table.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux sar command
IBM AIX sar command

the OS. The data is obtained by sampling once in a five-second interval.
User Action
Size of System File Table

Represents the current size of the system file table.

Swap Area Status
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux sar command
IBM AIX sar command

interval.
User Action
Response
Response metrics for hosts.
Status
This metric indicates whether the host is reachable or not. A host could be
unreachable due to various reasons. The network is down or the Management Agent
on the host is down (which could be because the host iteself is shutdown).
User Action
Swap Area Status

The Swap Area Status metric provides the status of the swap memory on the system.
Host Data Source

Solaris swap
HP swapinfo
Linux /proc/swaps
HP Tru64 swapon
IBM AIX lsps
Swap Free
Represents the number of 1K blocks in swap area that is not allocated.
Host 4-77
Swap Area Status
Metric Summary

Data Source
Host Data Source

Solaris swap
HP swapinfo
Linux /proc/swaps
HP Tru64 swapon
IBM AIX lsps
User Action
Check the swap usage using the UNIX top command or the Solaris swap -l command.
Additional swap can be added to an existing file system by creating a swap file and
then adding the file to the system swap pool. (See documentation for your UNIX OS).
If swap is mounted on /tmp, space can be freed by removing any junk files in /tmp. If
it is not possible to add file system swap or free up enough space, additional swap will
have to be added by adding a raw disk partition to the swap pool. See UNIX
documentation for procedures.
Swap Size
Represents the size of the swap file.
Metric Summary

Data Source
Host Data Source

Solaris swap
HP swapinfo
Linux /proc/swaps
HP Tru64 swapon
IBM AIX lsps

Switch/Swap Activity
Host Data Source

User Action
The Switch/Swap Activity metric displays the metric reports on the system switching
and swapping activity.
Host Data Source

Solaris sar command
HP sar command
Linux sar command
IBM AIX sar command
Process Context Switches (per second)

Represents the number of process context switches per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

the OS. Also, the data is obtained by sampling system counters once in a five-second
interval. The results are essentially the number of processes swapped in over this
User Action
Swapins Transfers (per second)

Represents the number of 512-byte units transferred for swapins per second.
Host 4-79
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux sar command

User Action
Swapout Transfers (per second)

Represents the number of 512-byte units transferred for swapouts per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available

User Action
System Swapins (per second)

Represents the number of process swapins per second.

System Calls
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux sar command

User Action
System Swapouts (per second)

Represents the number of process swapouts per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux sar command

User Action
System Calls
The System Calls metric provides statistics about the system calls made over a
five-second interval.
Host 4-81
System Calls
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command
Characters Transferred by Read System Calls (per second)

Represents the number of characters transferred by read system calls (block devices
only) per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

interval. The results are essentially the number of system calls made over this period
divided by the period.
User Action
Characters Transferred by Write System Calls (per second)

Represents the number of characters transferred by write system calls (block devices
only) per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available

System Calls
Host Data Source

IBM AIX sar command

User Action
exec() System Calls (per second)

Represents the number of exec() system calls made per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

User Action
fork() System Calls (per second)

Represents the number of fork() system calls made per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Host 4-83
System Calls
Host Data Source

Linux not available
IBM AIX sar command

User Action
read() System Calls (per second)

Represents the number of read() system calls made per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

User Action
System Calls (per second)

Represents the number of system calls made per second. This includes system calls of
all types.
Data Source

Top Processes
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

User Action
write() System Calls (per second)

Represents the number of write() system calls made per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

User Action
Top Processes
The Top Processes metric is a listing of (up to) 20 processes that include 10 processes
consuming the largest percentage of memory and 10 processes consuming the most
percentage of CPU time. The processes are listed in the order of memory consumption.
Host 4-85
Top Processes
Command and Arguments

Represents the command and all its arguments.
Data Source
Host Data Source

Solaris ps command, for example, ps -efo args
HP ps command, for example, ps -efo args
Linux ps command, for example, ps -efo args
HP Tru64 ps command, for example, ps -efo args
IBM AIX ps command, for example, ps -efo args
User Action
CPU Time for Top Processes

Represents the CPU utilization time in seconds.
Data Source
Host Data Source

Solaris ps command, for example, ps -efo time
HP ps command, for example, ps -efo time
Linux ps command, for example, ps -efo time
HP Tru64 ps command, for example, ps -efo time
IBM AIX ps command, for example, ps -efo time
User Action
CPU Utilization for Top Processes (%)

Represents the percentage of CPU time consumed by the process.
Data Source
Host Data Source

Solaris ps command, for example, ps -efo pcpu
HP ps command, for example, ps -efo pmem

Top Processes
Host Data Source

Linux ps command, for example, ps -efo pcpu
HP Tru64 ps command, for example, ps -efo pcpu
IBM AIX ps command, for example, ps -efo pcpu
User Action
For UNIX-based platforms, check the load on the system using the UNIX uptime or
top commands. Also, check for processes using too much CPU time by using the top
and ps -ef commands. Note that the issue may be a large number of instances of one or
more processes, rather than a few processes each taking up a large amount of CPU
time. Kill processes using excessive CPU time.
Memory Utilization for Top Processes (%)

Represents the percentage of memory consumed by the process.
Data Source
Host Data Source

Solaris ps command, for example, ps -efo pmem
HP ps command, for example, ps -efo pmem
Linux ps command, for example, ps -efo pmem
HP Tru64 ps command, for example, ps -efo pmem
IBM AIX ps command, for example, ps -efo pmem
User Action
Physical Memory Utilization (KB)

Represents the number of kilobytes of physical memory being used.
Data Source
Host Data Source

Solaris kernel memory structure (class vminfo)
HP ps command
Linux ps command
HP Tru64 ps command
IBM AIX kernel memory structure (struct vminfo)
Windows Windows API
Host 4-87
TTY Activity
User Action
Process User ID
Represents the user name that owns the process, that is, the user ID of the process
being reported on.
Data Source
Host Data Source

Solaris ps command, for example, ps -efo user
HP ps command
Linux ps command, for example, ps -efo user
HP Tru64 ps command, for example, ps -efo user
IBM AIX ps command, for example, ps -efo user
Windows Windows API
User Action
Virtual Memory Utilization (KB)

Represents the total size of the process in virtual memory in kilobytes (KB).
Data Source
Host Data Source

Solaris ps command, for example, ps -efo vsz
HP ps command, for example, ps -efo vsz
Linux ps command, for example, ps -efo vsz
HP Tru64 ps command, for example, ps -efo vsz
IBM AIX ps command, for example, ps -efo vsz
Windows Windows API
User Action
TTY Activity
This metric reports tty device activity.

TTY Activity
Incoming Character Interrupts (per second)

Represents the number of received incoming character interrupts per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

interval.
User Action
Input Characters Processed by canon()

Represents the input characters processed by canon() per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

interval.
User Action
Modem Interrupt Rate (per second)

Represents the modem interrupt rate.
Host 4-89
TTY Activity
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

interval.
User Action
Outgoing Character Interrupts (per second)

Represents the number of transmit outgoing character interrupts per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

interval.
User Action
TTY Output Characters (per second)

Represents the number of output characters per second.
Data Source

Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

interval.
User Action
TTY Raw Input (chars/s)

Represents the raw input characters per second.
Data Source
Host Data Source

Solaris sar command
HP sar command
Linux not available
IBM AIX sar command

interval.
User Action

The UDM metric allows you to execute your own scripts. The data returned by these
scripts can be compared against thresholds and generate severity alerts similar to
alerts in predefined metrics. UDM is similar to the Oracle9i Management Agent's UDE
functionality.
Host 4-91
Users
User Defined Numeric Metric

Contains a value if the value type is NUMBER. Otherwise, the value is "", if the value
is STRING.
Data Source
User defined script.
User Action
User Defined String Metric

Contains a value if the value type is STRING. Otherwise, the value is "", if the value is
NUMBER.
Data Source
User defined script.
User Action
Users
The Users metric provides information about the users currently on the system being
monitored.
Number of Logons
Represents the number of times a user with a certain user name is logged on to the
host target.
Data Source
For Solaris, HP, Linux, HP Tru64, and IBM AIX, the number of times a user is logged
on is obtained from the OS w command.
For Windows, the source of information is Windows API.
User Action

Part III
Oracle Application Server Metrics
Part III contains the metrics associated with Oracle Application Server:
Part III contains the following chapters:
■ Chapter 5, "Application Server"
■ Chapter 6, "Discoverer"
■ Chapter 7, "Forms"
■ Chapter 8, "HTTP Server"
■ Chapter 9, "Internet File System"
■ Chapter 10, "JServ"
■ Chapter 11, "OC4J"
■ Chapter 12, "OID LDAP Server"
■ Chapter 13, "Portal"
■ Chapter 14, "Reports Server"
■ Chapter 15, "Single Sign-On Server"
■ Chapter 16, "Web Cache"
■ Chapter 17, "Web Application"
■ Chapter 18, "Wireless"
5
Application Server
Oracle Enterprise Manager gathers performance metrics that provide high-level

information about the status, performance, and availability of your Oracle Application
Server.
Application Response
This category of metrics uses the Application URL to measure the responsiveness and
availability of the application server instance.
Application URL Response Time (seconds)

The Application URL Response Time is measured by automatically and continuously
attempting to access the Application URL. The response time includes the time it takes
to access the URL and for the application server to render and display the Application
URL content.
By the default, when you add an Application Server target, the Application URL is
defined to be the default home page for the Oracle HTTP Server. You can modify the
Application URL by modifying the properties of the Application Server target.
To modify the properties of an Application Server target, select the target on the All
Targets page in the Grid Control Console, and click Configure. On the resulting
Monitoring Configuration page, the Application URL is labeled as URL to measure
application response.
For more information, see the Modifying Target Properties topic in the Enterprise
Manager online help.
Alternatively, you can change the Application URL by clicking Change Application
URL on the Application Server Home page in the Grid Control Console.
Metric Summary
Application Server 5-1

OPMN Process Information Metrics

Consecutive
All Every 5 After Every > Not Defined Not Defined 2 The average
Versions Minutes 12 Samples response time for the
application URL is
%value% seconds
User Action
If the response time of the Availability URL exceeds the threshold, investigate other
related performance metrics, such as the application server Resource Usage metrics, to
review the load on the host computer. Also, check for alerts that may have been
generated by specific application server components, such as the HTTP Server
instance, OC4J instances, or the host computer.
Application URL Status

This metric indicates whether or not the Application URL, which is used to define the
responsiveness of the Application Server, can be accessed successfully. For example, if
the Application URL returns an error, the Application URL Status metric will be down.
A value of one (1) indicates that the Oracle Management Agent can access the
Application URL; a value of zero (0) indicates that the Application URL cannot be
accessed successfully.
For more information, see Application URL Response Time (seconds).
Metric Summary

User Action
If the Application URL Status is down, first verify that the Application URL is a valid
URL that can be used to measure the availability and responsiveness of the application
server instance. If it is a valid URL, especially one that was available previously, the
down status indicates that the Oracle HTTP Server is now unavailable and unable to
render the Application URL.
For more information, see the User Action information for the Application URL
Response Time (seconds) metric.

The OPMN Process Information Metrics provide you with a snapshot of how the
primary components of your application server--as well as specific components of
Oracle Enterprise Manager--are performing. The list provided here will vary,
depending upon the application server components you have installed and configured
for this instance of Oracle Application Server.

Enterprise Manager components that you can monitor by reviewing the OPMN
Process Information Metrics include the Oracle Management Agent (agent), the Oracle
Application Server Control process (console), and the Oracle Management Agent
watchdog process (watchdog).
For more information about the Management Agent watchdog process, see Oracle
Enterprise Manager Advanced Configuration.
Component CPU Usage (%)

This metric represents the percentage of host CPU used by the selected application
server component.
Metric Summary

Consecutive
9.0.4.x Every 5 After Every > Not Defined Not Defined 2 CPU Utilization of
Minutes 12 Samples %name% is
%value%%%
Multiple Thresholds
"Component Name" object.
If warning or critical threshold values are currently set for any "Component Name"
To specify or change warning or critical threshold values for each "Component Name"
User Action
You can use this metric to determine which components are using the most CPU on
your system. If one or more components are consuming a large amount of CPU,
consider changing the component configuration settings to reduce the amount of CPU
consumption.
For information about performance tuning Oracle Application Server components, see
the individual component documentation.
For more information about configuration settings for Enterprise Manager
components, see Oracle Enterprise Manager Advanced Configuration.
Component Memory Usage (%)

This metric represents the percentage of host memory used by the selected application
server component.

Metric Summary

Consecutive
9.0.4.x Every 5 After Every > 80 90 2 Memory Utilization
Minutes 12 Samples of %name% is
%value%%%
Multiple Thresholds
"Component Name" object.
If warning or critical threshold values are currently set for any "Component Name"
To specify or change warning or critical threshold values for each "Component Name"
User Action
You can use this metric to determine which components are using the most memory
on your system. If one or more components are consuming a large amount of memory,
consider changing the component configuration settings to reduce the amount of
memory consumption.
Component Memory Usage (MB)

This metric represents the memory usage in megabytes for the selected component.
Metric Summary

User Action
You can use this metric to determine which components are using the most memory
on your system. If one or more components are consuming a large amount of memory,
consider changing the component configuration settings to reduce the amount of
memory consumption.

Component Start Time (ms since epoch)

This metric is for internal use only.
Metric Summary

User Action
None.
Component Up Time (ms)

Metric Summary

User Action
None.
Component Up/down Status

This metric indicates whether the component is up or down. A value of one (1)
indicates that the component is up and running; a value of zero (0) indicates that the
component is down.
For more information about how Enterprise Manager determines the availability of an
Oracle Application Server or Enterprise Manager component, see the About
Availability topic in the Enterprise Manager online help.
Metric Summary

User Action
None.

Free Memory (%)

This metric shows you the percentage of memory that is free on the application server
host. The amount of free memory available can help you determine whether or not the
system is ready to handle a heavier load.
Note: You can view the value of this metric for each of the application server
components. However, the value of this metric applies to the memory for the host
where the application server is running. As a result, the value is the same for all the
components that are running on the host.
Metric Summary

User Action
If the percentage of Free Memory is low, compare this metric value to Component
Memory Usage (%), which shows the percentage of memory used by each of the
application server components. You can then identify which components are using the
most memory on the system.
To troubleshoot memory issues, check the list of top processes to determine which
system processes are using the most memory. For more information, see the Viewing
Host Target Performance Information topic in the Enterprise Manager online help.
Free Memory (MB)

This metric shows you the amount of memory (in megabytes) that are free on the
application server host. The amount of free memory available can help you determine
whether or not the system is ready to handle a heavier load.
Metric Summary

User Action
Compare to Component Memory Usage (MB), which shows the amount of memory
being used by the various components on the host. This can help you identify which
components are using the most memory.
In addition, check the list of top processes to determine which system processes are
using the most memory. For more information, see the Viewing Host Target
Performance Information in the Enterprise Manager online help.

Resource Usage
Idle CPU Time (%)

This metric represents the percentage of time that the CPU was idle and the system did
not have an outstanding disk I/O request.
You can also review the CPU Idle time for the host target. For more information,
navigate to the Host home page and click View All Metrics for the host target.
Metric Summary

User Action
If the amount of idle CPU is low, review the Component CPU Usage (%) to identify
which application server components are consuming the most CPU.
In addition, check the Other CPU Usage (%) metric to determine if other processes,
besides those of the application server, are using large amounts of CPU.
Total Memory (MB)

This metric shows you the total physical memory available on the application server
host computer.
This value is also available on the Host home page. To obtain more detailed hardware
information about the host computer, see the Viewing Host Target Overview
Information in the Enterprise Manager online help.
Metric Summary

User Action
None
Resource Usage
This category of metrics contains a set of metrics that provide you with information
about the CPU and Memory being used by the application server.

Resource Usage
CPU Idle Time (%)

This metric shows the percentage of system CPU time that is idle. The amount of idle
CPU time can help you determine whether or not the system is ready to handle a
heavier load.
Metric Summary

User Action
If the amount of idle CPU is low, review the Component CPU Usage (%) metric to
identify which application server components are consuming the most CPU.
In addition, check the Other CPU Usage (%) metric to determine if other processes,
besides those of the application server, are using large amounts of CPU.
CPU Usage (%)

Use this metric to determine the percentage of the host CPU being used by the
application server and all its configured and enabled components.
Metric Summary

Consecutive
All Every 5 After Every > 70 75 2 CPU Utilization is
Versions Minutes 12 Samples %value%%%
User Action
If the CPU Usage for the application server exceeds the alert threshold, check the
individual application server components to see if a particular component is
consuming excessive amounts of CPU. For more information, see the Viewing the
Performance of Your Application Server topic in the Enterprise Manager online help.
Navigate to the host home page and review the top processes to see if you can identify
which processes are consuming the most CPU. For more information, see the Viewing
Host Target Performance Information in the Enterprise Manager online help.
Also, check for alerts that may have been generated by specific application server
components, such as the HTTP Server instance, OC4J instances, or the host computer.

Resource Usage
Free Memory (%)

This metric shows you the percentage of memory that is free on the application server
host. The amount of free memory available can help you determine whether or not the
system is ready to handle a heavier load.
Metric Summary

User Action
Compare to Component Memory Usage (%) to determine which application server
components are using the most memory. Unlike the Free Memory (%) Metric, you can
set thresholds for the Component Memory Usage (%) and Memory Usage (%) metrics
and be alerted when they exceed the threshold.
To troubleshoot memory issues, you can also check the list of top processes to
determine which system processes are using the most memory. For more information,
see the Viewing Host Target Performance Information in the Enterprise Manager
online help.
Free Memory (MB)

This metric shows you the amount of memory (in megabytes) that are free on the
application server host. The amount of free memory available can help you determine
whether or not the system is ready to handle a heavier load.
Metric Summary

User Action
If the free memory on the application server host is too low, review the Component
Memory Usage (%) metrics to determine which application server components are
using the most memory. Unlike the Free Memory (MB) metric, you can set thresholds
for the Component Memory Usage (%) and Memory Usage (%) metrics and be alerted
when they exceed the threshold.
To troubleshoot memory issues, check the list of top processes to determine which
system processes are using the most memory. For more information, see the Viewing
Memory Usage (%)

This metric shows you the percentage of host memory being used by the application
server and its configured and enabled components.

Resource Usage
Metric Summary

Consecutive
All Every 5 After Every > 80 90 2 Memory Utilization
Versions Minutes 12 Samples is %value%%%
User Action
To troubleshoot memory issues, check the memory usage of individual application
server components and then check the list of top processes to determine which system
processes are using the most memory. For more information, see the Viewing Host
Target Performance Information in the Enterprise Manager online help.
Memory Usage (MB)

This metric shows you the amount of memory (in megabytes) being used by the
application server and its configured and enabled components.
Metric Summary

User Action
Compare this metric with Memory Usage (%), which measures the percentage of host
memory being used by the application server. Unlike the Memory Usage (MB) metric,
you can set a threshold for the Memory Usage (%) metric and be alerted when it
exceeds its threshold.
To troubleshoot memory issues, check the memory usage of individual application
server components and then check the list of top processes to determine which system
processes are using the most memory. For more information, see the Viewing Host
Target Performance Information in the Enterprise Manager online help.
Other CPU Usage (%)

This metric shows the amount of CPU owned and used by host processes, other than
the application server and its configured and enabled components. If you are having
problems with CPU usage on the application server host computer, this metric can
help you determine whether or not the application server is causing the problem.
Metric Summary

Resource Usage

User Action
which processes are consuming the most CPU. For more information, see the Viewing
Other Memory Usage (%)

This metric shows the percentage of host memory in use by other processes or
applications, other than the application server and its configured and enabled
components. If you are having problems with memory usage on the application server
host computer, this metric can help you determine whether or not the application
server is causing the problem.
Metric Summary

User Action
which processes are consuming the most memory. For more information, see the
Viewing Host Target Performance Information in the Enterprise Manager online help.
Other Memory Usage (MB)

This metric shows the amount of memory (in megabytes) currently in use by other
processes or applications, other than the application server and its configured and
enabled components. If you are having problems with memory usage on the
application server host computer, this metric can help you determine whether or not
the application server is causing the problem.
Metric Summary

User Action
Viewing Host Target Performance Information in the Enterprise Manager online help.

Response
Total Memory (MB)

This metric shows you the total physical memory available on the application server
host computer.
Metric Summary

9.0.2.x and 9.0.3.x Every 5 Minutes
User Action
None.
Response
This category contains the UpDown Status metric, which indicates whether the
Application Server is up or down.
UpDown Status
This metric indicates whether or not all the enabled Application Server components
are up and running. For example, if one OC4J instance is down, the UpDown Status
will be down even if the other application server components are up and running. The
status of the Application Server appears in the General section of the Application
Server home page in the Grid Control Console.
Metric Summary

Consecutive
All Every 5 After Every = Not Defined 0 1 The application
Versions Minutes 12 Samples server instance is
down
User Action
If the UpDown Status is down, verify whether the entire application server is down or
a subset of the application server components is down. In other words, if one OC4J
instance is down, the UpDown status will appear as down, even if the rest of the other
application server components are up and running.
If the application server instance is down, you can restart the application server by
clicking Administer on the Application Server home page in the Grid Control
Console.

Response
To investigate why the server is down, check for alerts that may have been generated
by the application server or by specific server components, such as the HTTP Server
instance, OC4J instances, or the host computer.
If you have shut down a particular application server component to save memory,
consider disabling the component so its UpDown Status will not affect the overall
status of the application server. For more information, see the Disabling and Enabling
Components topic in the Enterprise Manager online help.

Response

6
Discoverer
OracleAS Discoverer is a business intelligence tool for analyzing data and is a key
component of Oracle Application Server OracleAS). Discoverer provides an integrated
business intelligence solution comprising a set of intuitive ad-hoc query, reporting,
analysis, and Web-publishing tools. These tools enable non-technical users to gain
immediate access to information from data marts, data warehouses, and online
transaction processing systems. OracleAS Discoverer integrates seamlessly with
OracleAS Portal, enabling rapid deployment of Discoverer workbooks and worksheets
to Web portals.
Discoverer Components
This metric displays the total CPU and memory consumption for all current sessions
created by each Discoverer component (i.e. Discoverer Plus, Discoverer Viewer or
Discoverer Portlet Provider).
Note that the total CPU and memory consumption displayed here is only for the
sessions and does not include the CPU and memory consumption of the servlets for
these components. This metric also displays the total number of sessions created by
the component.
CPU Usage (%)

The total CPU usage for the sessions created by the each Discoverer UI component.
The total CPU usage does not include the CPU usage for the servlets of these
components. For CPU usage of servlets check the Discoverer application page under
the OC4J_BI_Forms home page.
Metric Summary

User Action
Memory Usage (MB)

The total memory usage for the sessions spawned by the given UI component. The
total memory usage does not include the memory usage for the servlets of these
Discoverer 6-1
Discoverer Plus Sessions
components. For memory usage of servlets check the Discoverer application page
under the OC4J_BI_Forms home page.
Metric Summary

User Action
Number of Sessions
The total number of Discoverer sessions created by the given component.
Metric Summary

User Action
Discoverer Plus Sessions

This metric displays information about all the Discoverer sessions created by
Discoverer Plus. The information included for each session is the session ID, the OS
Process ID, the memory usage of the session, the CPU usage for the session, the
database and EUL to which the session is connected and if SSO is turned on, the SSO
user using the session.
Component Type
The Discoverer UI component that started the particular session (i.e. Discoverer Plus,
Discoverer Viewer or Discoverer Portlet Provider.
User Action
CPU Usage (%)

The percentage CPU usage for this session.
User Action

Discoverer Portlet Provider Sessions
DBUser@DB - EUL
The database user, database name and EUL for this session.
User Action
Memory Usage (MB)

The amount of memory used in megabytes for this session.
User Action
OS Process ID
The operating system process ID for this session.
User Action
SSO User
The name of the single sign-on user for this session.
User Action
Discoverer Portlet Provider Sessions

Discoverer Portlet Provider. The information included for each session is the session
ID, the OS Process ID, the memory usage of the session, the CPU usage for the session,
the database and EUL to which the session is connected and if SSO is turned on, the
SSO user using the session.
Component Type
Discoverer Viewer or Discoverer Portlet Provider
User Action
CPU Usage (%)

User Action
Discoverer 6-3
Discoverer Sessions
DBUser@DB - EUL
User Action
Memory Usage (MB)

User Action
OS Process ID
User Action
SSO User
If SSO (i.e. single sign-on) is enabled for Discoverer, this column identifies the SSO
user that is using the current session. The SSO user is generally only meaningful for
Discoverer Plus and Discoverer Viewer components, where SSO users are using the
sessions interactively. For the Discoverer Portlet Provider, the SSO user may not be
meaningful, since Discoverer Portlet Provider runs queries in the background, and a
query could run as a given SSO user even when that SSO user is not currently logged
in.
User Action
Discoverer Sessions
This metric displays information about all the Discoverer Server sessions currently
running on server machine. It includes the following information: the session ID, the
OS Process ID, the Discoverer UI Component (i.e. Discoverer Plus, Discoverer Viewer
or Discoverer Portlet Provider) that created the session, the memory usage of the
session, the CPU usage for the session, the database and EUL to which the session is
connected and if single sign-on (SSO) is turned on, the SSO user using the session.
Component Type
Discoverer Viewer or Discoverer Portlet Provider.
User Action

Discoverer Sessions
CPU Usage (%)

The percentage of CPU used for all Discoverer sessions.
User Action
DBUser@DB - EUL
The database user, the database and the EUL that the session is connected to. The
format is databaseuser@database - EUL.
User Action
Memory Usage (MB)

The amount of memory used (in megabytes) for all Discoverer sessions.
User Action
OS Process ID
The operating system process ID for the given session.
User Action
Private Memory Usage (MB)

The amount of memory used (in megabytes) for all Discoverer sessions.
User Action
Shared Memory Usage (MB)

The amount of shared memory used (in megabytes) for all Discoverer sessions.
User Action
SSO User
user that is using the current SSO user. The SSO user is generally only meaningful for
in.
Discoverer 6-5
Discoverer Viewer Sessions
User Action
Discoverer Viewer Sessions

Discoverer Viewer. The information included for each session is the session ID, the OS
Process ID, the memory usage of the session, the CPU usage for the session, the
database and EUL to which the session is connected and if SSO is turned on, the SSO
user using the session.
Component Type
Discoverer Viewer or Discoverer Portlet Provider
User Action
CPU Usage (%)

User Action
DBUser@DB - EUL
User Action
Memory Usage (MB)

User Action
OS Process ID
User Action
SSO User
user that is using the current session. The SSO user is generally only meaningful for

Total Discoverer CPU Usage
in.
User Action
Response
This metric is derived directly from the OPMN tree. It reports the Up/Down Status of
Discoverer (i.e. the OAD process).
UpDown Status
This metric displays information that identifies whether the Discoverer Services: OAD,
OSAgent and Discoverer Preferences, are up or down. Since all the services are started
and stopped as a single entity, this metric only reports the status of the OAD.
Metric Summary

Consecutive
All Every 5 After Every = Not Defined 0 1 The Discoverer
Versions Minutes 12 Samples instance is down
User Action
Total Discoverer CPU Usage

This metric displays the total CPU percentage used by all Discoverer sessions running
on the machine at a given time. The total CPU usage does not include the CPU usage
of the servlets for Discoverer Plus, Viewer or Portlet Provider. For the CPU usage of
these servlets, please navigate to the Discoverer application page from the OC4J_BI_
Forms home page in the EM standalone console.
Total Discoverer CPU Usage (%)

The total CPU percentage used by all Discoverer sessions running on the machine at a
given time. The total CPU usage does not include the CPU usage of the servlets for
Discoverer Plus, Viewer or Portlet Provider. For the CPU usage of these servlets, please
navigate to the Discoverer application page from the OC4J_BI_Forms home page in
the EM standalone console.
Discoverer 6-7
Total Discoverer Memory Usage
Metric Summary

Consecutive
All Every 5 After Every > Not Defined Not Defined 2 CPU Usage is
User Action
Total Discoverer Memory Usage

This metric displays the total memory used by all Discoverer sessions running on the
machine at a given time. The total memory usage does not include the memory usage
of the servlets for Discoverer Plus, Viewer or Portlet Provider. For the memory usage
of these servlets, please navigate to the Discoverer application page from the OC4J_BI_
Forms home page in the EM standalone console.
Total Discoverer Memory Usage (MB)

The total memory usage for all Discoverer sessions as explained in the description of
the metric.
Metric Summary

Consecutive
All Every 5 After Every > Not Defined Not Defined 2 Memory Usage is
User Action
Total Number Of Discoverer Plus Sessions

This metric displays the total number of Discoverer sessions on the machine created by
Discoverer Plus at any given time.

Total Number Of Discoverer Sessions
Total Number Of Discoverer Plus Sessions

The total number of Discoverer sessions on the machine created by Discoverer Plus at
any given time.
Metric Summary

User Action
Total Number Of Discoverer Portlet Provider Sessions

Discoverer Portlet Provider at any given time.
Total Number Of Discoverer Portlet Provider Sessions

The total number of Discoverer sessions on the machine created by Discoverer Portlet
Provider at any given time.
Metric Summary

User Action

This metric displays the total number of Discoverer sessions running on the machine
at a given time.

The total number of Discoverer sessions running on the machine at a given time.
Metric Summary

Discoverer 6-9
Total Number Of Discoverer Viewer Sessions
User Action

Discoverer Viewer at any given time.

The total number of Discoverer Sessions on the machine created by Discoverer Viewer
at any given time.
Metric Summary

User Action

7
Forms
There are various metrics which can be used to monitor Forms Services.
Load
The Load category provides information about the present Load generated by Forms
processes.
Total CPU (%)

This metric is calculated from the total amount of CPU being used by all the Forms
processes.
By default, the thresholds for this metric are not defined The value for the thresholds
can be edited as required.
Metric Summary

Consecutive
All Every After Every > Not Defined Not Defined 1 CPU Utilization is
Versions Minute 12 Samples %value%%%
Data Source
The value of this metric is calculated using operating system specific commands.
User Action
Total Memory (%)

This metric is calculated from the total amount of private and shared memory being
used by all the Forms processes.
Forms 7-1
Response
By default, this metric has a critical threshold of 90 and a warning threshold of 80. A
critical alert is generated when the metric value exceeds the critical threshold value 1
time. A warning alert is generated when the metric value exceeds the warning
threshold value 1 time. The value for the thresholds can be edited as required.
Metric Summary

Consecutive
All Every After Every > 80 90 1 Memory Utilization
Versions Minute 12 Samples is %value%%%
Data Source
The value of this metric is calculated using operating system specific commands.
User Action
Total number of users

This metric reports the total number of Forms sessions being monitored by Enterprise
Manager.
Metric Summary

All Versions Every Minute
Data Source
This value of this metric is based on the number of Forms processes executing on the
host.
The current value of this metric can also be seen under Response and Load on the
Forms Overview Page.
User Action
Response
The Response category provides information about the responsiveness of the Forms
Servlet.

Response
ResponseTime(ms)
This metric displays the response time in milliseconds for the Oracle Forms Servlet.
By default, this metric has a critical threshold of 1000 and a warning threshold of 500.
A critical alert is generated when the metric value exceeds the critical threshold value
1 time. A warning alert is generated when the metric value exceeds the warning
threshold value 1 time. The value for the thresholds can be edited as required.
Metric Summary

Consecutive
All Every After Every > 500 1000 1 The Forms Listener
Versions Minute 12 Samples response time is
unacceptable.
Data Source
The value of this metric is obtained by measuring the response to the Servlet URL
shown on the Forms Overview Page.
User Action
Status
By default, this metric has a critical threshold of 0 indicating that the Forms Servlet is
unreachable. A critical alert is generated when the metric value equals the critical
threshold value once. It is advisable that this threshold be left at the default value.
Metric Summary

Consecutive
All Every After Every = Not Defined 0 1 The Forms instance
Versions Minute 12 Samples is not accessible.
Forms 7-3
Response
Data Source
The value of this metric is obtained by measuring the availability of the Servlet URL
shown on the Forms Overview Page.
The current value of this metric can also be seen under Response and Load on the
Forms Overview Page.
User Action
Check whether the OC4J_BI_Forms oc4j instance has been started and if so that the
application forms90app.ear has been deployed successfully.

8
HTTP Server
The Oracle Enterprise Manager Grid Control Console can be used to manage Oracle
HTTP Server. You can use the All Metrics page for an HTTP Server target in the Oracle
Enterprise Manager Grid Control Console to view the metrics that have been collected
for that target by the Oracle Management Agent.
Host Metrics
Metrics for the host on which the HTTP Server is running.
Name
This is the host name.
User Action
None.
modplsql_Cache Metrics
The metrics in this metric category are for internal use only.
Customers should not take any action based on the values for the metrics in this metric
category.
cacheStatus.value
Metric Summary
Collection
9.0.2.x and Every 5 Minutes
9.0.3.x; 9.0.4.x
User Action
Customers should not take any action based on the values for this metric.
HTTP Server 8-1

hits.count, ops
Metric Summary
Collection
9.0.3.x; 9.0.4.x
User Action
hits.percentage
Metric Summary
Collection
9.0.3.x; 9.0.4.x
User Action
modplsql
Metric Summary
Collection
9.0.2.x and 9.0.3.x; Every 5 Minutes
9.0.4.x
User Action
Name

Metric Summary
Collection
9.0.4.x
User Action
newMisses.count, ops
Metric Summary
Collection
9.0.4.x
User Action
newMisses.percentage
Metric Summary
Collection
9.0.4.x
User Action
requests.count
Metric Summary
HTTP Server 8-3

modplsql_HTTPResponseCodes Metrics
Collection
9.0.4.x
User Action
staleMisses.count, ops
Metric Summary
Collection
9.0.4.x
User Action
staleMisses.percentage
Metric Summary
Collection
9.0.4.x
User Action
This metric category is for internal use only.
Customers should not take any action based on the values for the metrics in this
category.
HTTP 200s

Metric Summary
Collection
9.0.4.x
User Action
HTTP 200s percentage

Metric Summary
Collection
9.0.4.x
User Action
HTTP 300s Resolved

Metric Summary
Collection
9.0.4.x
User Action
HTTP 300s resolved percentage

Metric Summary
HTTP Server 8-5

Collection
9.0.4.x
User Action
HTTP 400s
Metric Summary
Collection
9.0.4.x
User Action

Metric Summary

Consecutive
9.0.2.x Every 5 After Every > Not Defined Not Defined 2 HTTP 400 response
and Minutes 12 Samples codes are %value%
9.0.3.x; %
9.0.4.x
Multiple Thresholds
"Full Name" object.
If warning or critical threshold values are currently set for any "Full Name" object,

To specify or change warning or critical threshold values for each "Full Name" object,
User Action
HTTP 500s
Metric Summary
Collection
9.0.4.x
User Action

Metric Summary

Consecutive
9.0.2.x Every 5 After Every > Not Defined Not Defined 2 HTTP 500 response
and Minutes 12 Samples codes are %value%
9.0.3.x; %
9.0.4.x
Multiple Thresholds
"Full Name" object.
If warning or critical threshold values are currently set for any "Full Name" object,
To specify or change warning or critical threshold values for each "Full Name" object,
HTTP Server 8-7

modplsql_RequestGroupingSQLErrorList Metrics
User Action
Total HTTP responses

Metric Summary
Collection
9.0.4.x
User Action
This metric category is for internal use only.
Customers should not take any action based on the values for the metrics in this
category.
errorCount.count
Metric Summary
Collection
9.0.4.x
User Action
lastErrorDate.value
Metric Summary
Collection
9.0.4.x

User Action
lastErrorRequest.value
Metric Summary
Collection
9.0.4.x
User Action
lastErrorText.value
Metric Summary
Collection
9.0.4.x
User Action
Name
Metric Summary
Collection
9.0.4.x
User Action
HTTP Server 8-9

modplsql_RequestLast10SQLErrorList Metrics
modplsql_RequestLast10SQLErrorList Metrics
The metrics in this metric category are for internal use only.
Customers should not take any action based on the values for the metrics in this metric
category.
errorDate.value
Metric Summary
Collection
9.0.4.x
User Action
errorRequest.value
Metric Summary
Collection
9.0.4.x
User Action
errorText.value
Metric Summary
Collection
9.0.4.x
User Action

OHS Module Metrics
Name
Metric Summary
Collection
9.0.4.x
User Action
OHS General Metrics

This metric category includes metrics that provide general information about Oracle
HTTP Server.
Start Time (ms since Epoch)

This metric contains the start time of the HTTP Server. It is represented in milliseconds
since the Unix epoch.
The Unix epoch is January 1, 1970.
Metric Summary
Collection
9.0.4.x
User Action
OHS Module Metrics

Contains metrics about Oracle HTTP Server (OHS) modules.
Active Requests for a Module

The number of requests currently being processed by this module's handler.
Metric Summary
HTTP Server 8-11

OHS Process Metrics
Collection
User Action
Request Handling Throughput, for a Module (requests per second)

This rate metric tells you the number of requests handled per second by this module
during the last interval. The interval is the period of time specified as the collection
frequency for this metric.
Metric Summary
Collection
User Action
This metric helps you determine the frequency of requests currently being served by
the module.
If the request handling throughput is very low, either there is no activity on the Web
server for the module, or there is something else going on that is preventing the
module from processing requests.
Request Handling Time, for a Module (seconds)

This metric shows the average time (in seconds) it took the module to handle a request
during the last interval. The interval is the period of time specified as the collection
Metric Summary
Collection
User Action
OHS Process Metrics

This metric category contains metrics about DMS processes.

OHS Server Metrics
Heap Usage (MB)

Displays (in MB) the total amount of heap space used since the server was started.
Metric Summary

Consecutive
9.0.2.x Every 5 After Every > Not Defined Not Defined 2 Heap Usage is
and Minutes 12 Samples %value%MB
9.0.3.x;
9.0.4.x
User Action
OHS Server Metrics

The metrics in this metric category display information about Oracle HTTP Server.
Active HTTP Connections

This metric shows the number of open HTTP connections.
Metric Summary

Consecutive
All Every 5 After Every > 7500 8000 2 The number of active
Versions Minutes 12 Samples connections is
%value%
User Action
Active HTTP Requests

The number of requests currently being serviced.
HTTP Server 8-13

OHS Server Metrics
Metric Summary

Consecutive
All Every 5 After Every > 7500 8000 2 The number of active
Versions Minutes 12 Samples requests is %value%
User Action
Busy Processes
The number of child servers that are busy.
Metric Summary
Collection
9.0.4.x
User Action
Connection Duration (seconds)

This metric shows the average time (in seconds) a connection was open during the last
interval. The interval is the period of time specified as the collection frequency for this
metric. A connection remains open until all of the requests that it is handling have
been completed.
Metric Summary
Collection
User Action

OHS Server Metrics
Error Rate (%)

The percentage of requests that encountered errors during the last interval. The
interval is the period of time specified as the collection frequency for this metric.
Metric Summary

Consecutive
9.0.2.x Every 5 After Every > 1 1.5 2 The percentage of
and Minutes 12 Samples requests that
9.0.3.x; resulted in errors is
9.0.4.x %value%%%
User Action
Use the Enterprise Manager Application Server Control Console to examine the errors
in this HTTP Server's error log file. For information about viewing HTTP Server error
logs in the Enterprise Manager Application Server Control, see the "About the HTTP
Server Log Files" topic in the Enterprise Manager Application Server Control help
system.
Idle Processes
The number of child servers that are ready.
Metric Summary
Collection
9.0.4.x
User Action
Percentage of Busy Processes

Shows the percentage of Oracle HTTP Server child processes that are currently
servicing requests.
Metric Summary
HTTP Server 8-15

OHS Server Metrics

Consecutive
9.0.2.x Every 5 After Every > 85 90 2 The percentage of
and Minutes 12 Samples processes that are
9.0.3.x; busy handling
9.0.4.x requests is
%value%%%
User Action
To tune the percentage of Oracle HTTP Server child processes that are currently
servicing requests, you can change the values for the MaxClients, MinSpareServers,
and MaxSpareServers directives.
You can change the value of the MaxClients directive by modifying the value of the
Maximum Requests Processed Simultaneously field on the HTTP Server Server
Properties page in the Enterprise Manager Application Server Control Console. See the
"Modifying Server Properties" topic in the Enterprise Manager Application Server
Control help system for more information about accessing the HTTP Server Server
Properties page in the Enterprise Manager Application Server Control Console. Click
Help on the HTTP Server Server Properties page for more information about using
that page.
The MinSpareServers and MaxSpareServers directives can be modified on the
Advanced Server Properties page in the Enterprise Manager Application Server
Control Console. See the "Editing the Server Configuration Files" topic in the
Enterprise Manager Application Server Control help system for more information
about accessing the HTTP Server Advanced Server Properties page in the Enterprise
Manager Application Server Control Console. Click Help on the HTTP Server
Advanced Server Properties page for more information about using that page to edit
the directives in the httpd.conf file.
For more information about the MaxClients, MinSpareServers, and MaxSpareServers
directives, go to the Apache HTTP Server Documentation section of the
http://www.apache.org Web site, then navigate to the Directives information.
Request Processing Time (seconds)

This metric shows the average time it took to process a request during the last interval.
The interval is the period of time specified as the collection frequency for this metric.
Metric Summary

OHS Server Metrics

Consecutive
Versions Minutes 12 Samples processing time for a
request is %value%
seconds
User Action
Request Throughput (requests per second)

This rate metric tells you the number of requests per second serviced during the last
metric.
This metric tells you how much of a load this HTTP Server is handling.
Metric Summary
Collection
User Action
Response Data Processed (KB per response)

This metric tells you the average size of a response (in KB) during the last interval. The
Metric Summary

Consecutive
9.0.2.x Every 5 After Every > Not Defined Not Defined 2 The average size of a
and Minutes 12 Samples request is
9.0.3.x; %value%KB
9.0.4.x
HTTP Server 8-17

OHS Virtual Host Metrics
User Action
Response Data Throughput (KB per second)

This metric tells you the amount of response data (in KB/seconds) processed by
Oracle HTTP Server during the last interval. The interval is the period of time
specified as the collection frequency for this metric.
Metric Summary
Collection
9.0.4.x
User Action
This metric can help you identify changes in the volume of information being served
by the HTTP Server over time.

The metrics in this metric category provide virtual host information.
Active Requests for a Virtual Host

Total number of active requests currently being processed by the virtual host.
Metric Summary

Consecutive
9.0.2.x Every 5 After Every > 7500 8000 2 The number of active
and Minutes 12 Samples requests for virtual
9.0.3.x; host %name% is
9.0.4.x %value%
Multiple Thresholds
"Name" object.

User Action
Request Processing Time for a Virtual Host (seconds)

This metric shows the average amount of time it took the virtual host to process one
request during the last interval. The interval is the period of time specified as the
collection frequency for this metric.
Metric Summary

Consecutive
9.0.2.x Every 5 After Every > Not Defined Not Defined 2 The average
and Minutes 12 Samples processing time for a
9.0.3.x; request for virtual
9.0.4.x host %name% is
%value% seconds
Multiple Thresholds
"Name" object.
User Action
Request Throughput for a Virtual Host (requests per second)

This rate metric tells you the number of requests per second serviced by the virtual
host during the last interval. The interval is the period of time specified as the
This metric tells you how much of a load this virtual host is handling.
Metric Summary
HTTP Server 8-19

Collection
9.0.4.x
User Action
Response Data Processed for a Virtual Host (KB per response)

This metric tells you the average size of a response (in KB) during the last interval. The
Metric Summary

Consecutive
9.0.2.x Every 5 After Every > Not Defined Not Defined 2 The average size of a
and Minutes 12 Samples request for virtual
9.0.3.x; host %name% is
9.0.4.x %value%KB
Multiple Thresholds
"Name" object.
User Action
Response Data Throughput for a Virtual Host (KB per second)

This metric tells you the amount of response data (in KB/second) processed by the
virtual host during the last interval. The interval is the period of time specified as the
Metric Summary

Resource Usage
Collection
9.0.4.x
User Action
This metric can help you identify changes in the volume of information being served
by the virtual host over time.
Virtual Host Type

The type of virtual host, either IP_DEFAULT, NAME_DEFAULT, IP_BASED, or
NAME_BASED.
Metric Summary
Collection
User Action
None.
Process Metrics
Metrics for processes.
Host
This is the name of the host on which the process is running.
User Action
Name
This is the process name.
User Action
None.
Resource Usage
The metrics in this metric category provide information about CPU and memory
usage.
CPU Idle Time (%)

Displays the percentage of system CPU time that is idle.
HTTP Server 8-21

Resource Usage
Metric Summary
Collection
9.0.4.x
User Action
CPU Usage (%)

Shows the percentage of the CPU usage by Oracle HTTP Server.
Metric Summary

Consecutive
9.0.2.x Every 5 After Every > Not Defined Not Defined 2 CPU Utilization is
and Minutes 12 Samples %value%%%
9.0.3.x;
9.0.4.x
User Action
Free Memory (%)

Shows the percentage of free physical memory for the system.
Metric Summary
Collection
9.0.4.x
User Action

Resource Usage
Free Memory (MB)

Shows the amount of free physical memory (in MB) for the system.
Metric Summary
Collection
9.0.4.x
User Action
Memory Usage (%)

Shows the percentage of the physical memory used by Oracle HTTP Server.
Metric Summary

Consecutive
9.0.2.x Every 5 After Every > 80 90 2 Memory Utilization
and Minutes 12 Samples is %value%%%
9.0.3.x;
9.0.4.x
User Action
Memory Usage (MB)

Shows the amount of physical memory (in MB) being used by Oracle HTTP Server.
Metric Summary
Collection
9.0.4.x
HTTP Server 8-23

Resource Usage
User Action
Other CPU Usage (%)

Shows the percentage of the CPU owned and used by host processes other than Oracle
HTTP Server. If you are having problems with CPU usage on the HTTP Server host
computer, this metric can help you determine whether or not HTTP Server is causing
the problem.
Metric Summary
Collection
9.0.4.x
User Action
Navigate to the host Home page and review the top processes to see if you can identify
which processes are consuming the most CPU. For more information, see the "Viewing
Host Target Performance Information" in the Enterprise Manager online help.

This metric shows the percentage of host memory in use by processes and applications
other than Oracle HTTP Server. If you are having problems with memory usage on the
HTTP Server host computer, this metric can help you determine whether or not the
HTTP Server is causing the problem.
Metric Summary
Collection
9.0.4.x
User Action
"Viewing Host Target Performance Information" in the Enterprise Manager online
help.

Shows the physical memory usage (in MB) by processes and applications other than
Oracle HTTP Server. If you are having problems with memory usage on the HTTP
Server host computer, this metric can help you determine whether or not HTTP Server
is causing the problem.

Response
Metric Summary
Collection
9.0.4.x
User Action
which processes are consuming the most memory. For more information, see "Viewing
Total Memory (MB)

Shows the amount of physical memory (in MB) for the system.
Metric Summary
Collection
9.0.4.x
User Action
Response
Contains metrics that provide basic information about the HTTP Server.
UpDown Status
Shows whether the HTTP Server is up or down.
Metric Summary

Consecutive
All Every After Every = Not Defined 0 1 The HTTP Server
Versions Minute 60 Samples instance is down
HTTP Server 8-25

Response
User Action
If the HTTP Server is down, start it using the Home page for the HTTP Server in the
Enterprise Manager Application Server Control Console.

9
Internet File System
Internet File System is the base target type for Oracle Content Management SDK (Oracle
CM SDK) and Oracle Files. An Oracle CM SDK target or a Oracle Files target is
comprised of all the local Oracle CM SDK or Oracle Files processes for one domain.
There are two kinds of processes:
■ Domain Controller: Provides runtime management for the entire domain.
■ Node: Runs protocol servers, agents, or servlets.
You can use Oracle Enterprise Manager to monitor and manage these processes.
Application URL Timing

The Application URL Timing category provides responsiveness information for the URL
of the primary Web application running on the local host. It reports the availability
and the response time of the URL.
Application URL Response Time (seconds)

This metric provides the response time of a URL. In particular, it returns the total
elapsed time (in seconds) that it took to download the contents of that URL. The URL's
contents include both the base page source and any frames or images in the page.
Metric Summary

Consecutive
All Every 5 After Every > 2.0 3.0 2 The average
web application is
%value% seconds
User Action
Internet File System 9-1

Document Statistics
Application URL Status

This metric returns the availability of a URL:
■ 0 - The URL is not available.
■ 1 - The URL is available.
By default, this metric has a critical threshold of 0 and a warning threshold of
NotDefined. A critical alert is generated when the metric value equals the critical
threshold value 1 time. A warning alert is generated when the metric value equals the
warning threshold value 1 time. Do not change the threshold value for this metric.
Metric Summary

Consecutive
All Every 5 After Every = Not Defined 0 1 The web application
Versions Minutes 12 Samples is down
User Action
Document Statistics
The Document Statistics category provides basic document statistics for documents in
the target's repository. It reports the total document count, the total document content
size, and the average document content size.
Average Document Size (bytes)

This metric reports the average content size of the documents in the target Oracle CM
SDK or Oracle Files repository.
Metric Summary
Collection
User Action

Documents By MIME Type
Total Number of Documents

This metric reports the total number of documents in the target Oracle CM SDK or
Oracle Files repository.
Metric Summary
Collection
User Action
Total Size of Documents (bytes)

This metric reports the total content size of the documents in the target Oracle CM
SDK or Oracle Files repository.
Metric Summary
Collection
User Action
Documents By MIME Type

The Documents By MIME Type category provides document statistics grouped by
MIME type, for documents in the target's repository. It reports the number of
documents and the total content size for each MIME type.
Documents
This metric reports the total number of documents for a given MIME type.
Metric Summary
Collection
User Action

Domain Response
Size of Documents (bytes)

This metric reports the total content size of all the documents belonging to a given
MIME type.
Metric Summary
Collection
User Action
Domain Response
The Domain Response category provides status information about the Oracle CM SDK
or Oracle Files domain, the Node processes, and the Domain Controller process.
Domain Controller Status

This metric defines the status of the Domain Controller process as a number. The
possible values are:
■ 0 (Down) - The Domain Controller process is down or unconnectable.
■ 1 (Up) - The Domain Controller process is up.
Metric Summary

Consecutive
All Every 5 After Every = Not Defined 0 1 The domain
Versions Minutes 12 Samples controller is not
started
User Action
Node Status
This metric defines the status of the Node processes as a number. The possible values
are:
■ 0 (Down) - One or more of the Node processes in the domain are down.

Domain Response
■ 0.5 (Unknown) - The status of the Node processes in the domain is unknown, most
likely due to the Domain Controller process being down or unconnectable.
■ 1 (Up) - All of the Node processes in the domain are up.
Metric Summary

Consecutive
All Every 5 After Every = 0.5 0 1 %NodeStatusMessag
Versions Minutes 12 Samples e%
User Action
Node Status Message

This metric provides detailed status messages about Oracle CM SDK or Oracle Files
Node processes. For example, it displays the Node names for all Node processes that
are down.
Metric Summary
Collection
User Action
Status
This metric defines the overall status of the Oracle CM SDK or Oracle Files domain as
a number. The possible values are:
■ 0 (Down) - All of the processes in the domain are down.
■ 0.5 (Unknown) - The status of the processes in the domain is unknown, most likely
due to the Domain Controller process being down or unconnectable
■ 1 (Up) - One or more of the processes in the domain are up.
Metric Summary

Load Balanced Application URL Timing


Consecutive
All Every 5 After Every = 0.5 0 1 The domain of
Versions Minutes 12 Samples %target% is either
down or status
unknown
User Action
Load Balanced Application URL Timing

The Load Balanced Application URL Timing category provides responsiveness
information for the load balanced URL of the primary Web application of the Oracle
CM SDK or Oracle Files domain. It reports the availability and the response time of the
load balanced URL.
Load Balanced Application URL Response Time (seconds)

This metric provides the response time of a URL. In particular, it returns the total
elapsed time (in seconds) that it took to download the contents of that URL. The URL's
contents include both the base page source and any frames or images in the page.
Metric Summary

Consecutive
All Every 5 After Every > 2.0 3.0 2 The average
load balanced web
application is
%value% seconds
User Action
Load Balanced Application URL Status

This metric returns the availability of a URL:
■ 0 - The URL is not available.

Node Statistics
■ 1 - The URL is available.

By default, this metric has a critical threshold of 0 and a warning threshold of
NotDefined. A critical alert is generated when the metric value equals the critical
threshold value 1 time. A warning alert is generated when the metric value equals the
warning threshold value 1 time. Do not change the threshold value for this metric.
Metric Summary

Consecutive
All Every 5 After Every = Not Defined 0 1 The load balancer or
Versions Minutes 12 Samples the web application
is down
User Action
Node Statistics
The Node Statistics category provides basic statistics on all the Nodes of the target
Oracle CM SDK or Oracle Files domain. It reports the hostname and IP address,
session count, Java VM thread count, the Java VM total/free/used memory for each
Node.
Host Name and IP

This metric reports the hostname and the IP address of a given Oracle CM SDK or
Oracle Files Node process.
Metric Summary
Collection
User Action
JVM Free Memory (%)

This metric reports the percentage of the Java VM free memory over the total memory
of a given Oracle CM SDK or Oracle Files Node process.

Node Statistics
Metric Summary

Consecutive
All Every 5 After Every < 15.0 10.0 5 The Java VM free
Versions Minutes 12 Samples memory is low in
%NodeName% on
%HostNameIP%
Multiple Thresholds
"Node Name" object.
If warning or critical threshold values are currently set for any "Node Name" object,
To specify or change warning or critical threshold values for each "Node Name" object,
User Action
JVM Free Memory (MB)

This metric reports the Java VM free memory (in MB) of a given Oracle CM SDK or
Metric Summary
Collection
User Action
JVM Threads
This metric reports the Java VM thread count of a given Oracle CM SDK or Oracle
Files Node process.
Metric Summary

Node Statistics
Collection
User Action
JVM Total Memory (MB)

This metric reports the Java VM total memory (in MB) of a given Oracle CM SDK or
Metric Summary
Collection
User Action
JVM Used Memory (MB)

This metric reports the Java VM used memory (in MB) of a given Oracle CM SDK or
Metric Summary
Collection
User Action
Sessions
This metric reports the session count of a given Oracle CM SDK or Oracle Files Node
process.
Metric Summary
Collection

Resource Usage
User Action
Resource Usage
The Resource Usage category provides the CPU usage and the memory usage for local
Oracle CM SDK or Oracle Files processes. It reports the following:
■ CPU usage percentage
■ CPU usage percentage of other processes
■ CPU idle percentage
■ Physical memory usage (in MB)
■ Physical memory usage percentage
■ Total physical memory (in MB)
CPU Idle (%)

This metric returns the CPU idle percentage for the local host.
Metric Summary
Collection
User Action
CPU Other (%)

This metric returns the CPU usage percentage for all processes other than the given
process group.
Metric Summary
Collection
User Action
CPU Usage (%)

This metric returns the CPU usage percentage for the given process group.

Resource Usage
Metric Summary

Consecutive
All Every 5 After Every > 70 75 2 CPU Utilization for
Versions Minutes Sample %keyvalue% is
%value%%%
Multiple Thresholds
"Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" object,
To specify or change warning or critical threshold values for each "Process Name"
User Action
Memory Usage (%)

This metric returns the physical memory usage percentage for the given process
group.
Metric Summary

Consecutive
Versions Minutes Sample for %keyvalue% is
%value%%%
Multiple Thresholds

Response
User Action
Memory Usage (MB)

This metric returns the physical memory usage (in MB) for the given process group.
Metric Summary
Collection
User Action
Total Memory (MB)

This metric returns the total physical memory (in MB) on the local host.
Metric Summary
Collection
User Action
Response
The Response category provides the overall status of all the local Oracle CM SDK or
Oracle Files processes for the current target.
Status
This metric defines the overall status of the Oracle CM SDK or Oracle Files local
processes as a number. The possible values are:
■ 0 (Down) - All of the local processes are down.
■ 0.5 (Unknown) - The status of the local processes is unknown, most likely due to
the Domain Controller being down or unconnectable.

Sessions By Server (Node)
■ 1 (Up) - One or more of the local processes are up.

By default, this metric has a critical threshold of 0 and a warning threshold of 0.5. A
critical alert is generated when the metric value equals the critical threshold value 1
time. A warning alert is generated when the metric value equals the warning
threshold value 1 time. Do not change the threshold values for this metric.
Metric Summary

Consecutive
All Every 5 After Every = 0.5 0 1 %target% is either
Versions Minutes 12 Samples down or status
unknown
User Action
Sessions By Server (Domain)

The Sessions By Server (Domain) category provides basic session information for the
target Oracle CM SDK or Oracle Files domain. It reports the session count grouped by
Oracle CM SDK or Oracle Files Server type.
Sessions By Server
This metric reports the session count for a given Oracle CM SDK or Oracle Files Server
type in the domain.
Metric Summary
Collection
User Action
Sessions By Server (Node)

The Sessions By Server (Node) catogory provides basic session information for each
Oracle CM SDK or Oracle Files Node in the target domain. For each Node, it reports
the hostname, IP address, and session count grouped by Oracle CM SDK or Oracle
Files Server type.

Users
Host Name and IP

This metric reports the hostname and the IP for a given Oracle CM SDK or Oracle Files
Node process.
Metric Summary
Collection
User Action
Sessions By Server
This metric reports the session count for a given Oracle CM SDK or Oracle Files Node
process and a given Oracle CM SDK or Oracle Files Server type.
Metric Summary
Collection
User Action
Users
The Users category provides basic statistics for all Oracle CM SDK or Oracle Files users
in the target's repository, including users with limited quota and users with unlimited
quota. It reports the following:
■ Total number of users
■ Total number of users with limited quota
■ Total number of users with unlimited quota
■ Total consumed quota for all users
■ Total consumed quota for users with limited quota
■ Total consumed quota for users with unlimited quota
■ Average consumed quota for all users
■ Average consumed quota for users with limited quota
■ Average consumed quota for users with unlimited quota

Users
All Users
This metric reports the total number of users in Oracle CM SDK or Oracle Files.
Metric Summary
Collection
User Action
Average Consumed Quota By All Users (bytes)

This metric reports the average amount of quota consumed by all Oracle CM SDK or
Oracle Files users.
Metric Summary
Collection
User Action
Average Consumed Quota By Limited Users (bytes)

This metric reports the average amount of quota consumed by Oracle CM SDK or
Oracle Files users with limited quota.
Metric Summary
Collection
User Action
Average Consumed Quota By Unlimited Users (bytes)

This metric reports the average amount of quota consumed by Oracle CM SDK or
Oracle Files users with unlimited quota.

Users
Metric Summary
Collection
User Action
Consumed Quota By All Users (bytes)

This metric reports the total amount of quota consumed by all Oracle CM SDK or
Oracle Files users.
Metric Summary
Collection
User Action
Consumed Quota By Limited Users (bytes)

This metric reports the total amount of quota consumed by Oracle CM SDK or Oracle
Files users with limited quota.
Metric Summary
Collection
User Action
Consumed Quota By Unlimited Users (bytes)

Files users with unlimited quota.
Metric Summary

Users (With Limited Quota)
Collection
User Action
Users With Limited Quota

This metric reports the total number of Oracle CM SDK or Oracle Files users with
limited quota.
Metric Summary
Collection
User Action
Users With Unlimited Quota

This metric reports the total number of Oracle CM SDK or Oracle Files users unlimited
quota.
Metric Summary
Collection
User Action

The Users (With Limited Quota) category provides basic statistics for Oracle CM SDK or
Oracle Files users with limited quota. It reports the following:
■ Total number of users with limited quota
■ Total quota allocated to users with limited quota
■ Total quota consumed by users with limited quota
■ Average quota allocated to users with limited quota
■ Percentage of consumed quota over allocated quota for users with limited quota

Average Allocated Quota (bytes)

This metric reports the average amount of quota allocated to Oracle CM SDK or Oracle
Metric Summary
Collection
User Action
Average Consumed Quota (bytes)

This metric reports the average quota consumed by Oracle CM SDK or Oracle Files
users with limited quota.
Metric Summary
Collection
User Action
Consumed (%)
This metric reports the percentage of the overall consumed quota over the overall
allocated quota for Oracle CM SDK or Oracle Files users with limited quota.
Metric Summary
Collection
User Action
Total Allocated Quota (bytes)

This metric reports the total amount of quota allocated to Oracle CM SDK or Oracle

Metric Summary
Collection
User Action
Total Consumed Quota (bytes)

Metric Summary
Collection
User Action

This metric reports the total number of Oracle CM SDK or Oracle Files users with
limited quota.
Metric Summary
Collection
User Action


10
JServ
These metrics provide information about the health of the JServ target.
Response
This metric provides the status of JServ, that is, whether it is up or down.
Status
Displays the present condition of JServ. There are three possible conditions:
■ Unknown: Enterprise Manager cannot communicate with JServ
■ Up: JServ is running
■ Down: JServ is not running
Metric Summary

Consecutive
All Every After Every = Not Defined 0 1 The JServ instance is
Versions Minute 60 Samples down
User Action
JServ 10-1
Response

11
OC4J
The Oracle Enterprise Manager Grid Control Console can be used to manage Oracle
Application Server Containers for J2EE (OC4J). You can use the All Metrics page for an
OC4J target in the Oracle Enterprise Manager Grid Control Console to view the
metrics that have been collected for that target by the Oracle Management Agent.
Application Metrics for OC4J Instances

Metrics for applications within the OC4J instance.
Application - Delta EJB Method Execution Time (seconds)

Metric Summary
Collection
User Action
Customers should not take any action based on the value of this metric.
Application - Delta EJB Method Invocations

Metric Summary
Collection
User Action
OC4J 11-1
Application - Delta Request Processing Time (seconds)

Metric Summary
Collection
User Action
Application - Delta Requests Completed

Metric Summary
Collection
User Action
Application - Delta Servlet, JSP and EJB Time (seconds)

Metric Summary
Collection
User Action
Application - Requests Completed since Startup

The number of servlets and JSPs executed by this application since startup.
Metric Summary

Collection
User Action
Application - Total EJB Method Execution Time (seconds)

The total amount of time it took to execute EJB methods for this application.
Metric Summary
Collection
User Action
Application - Total EJB Method Invocations

The total number of times that EJB methods were invoked for this application.
Metric Summary
Collection
User Action
Application - Total Request Processing Time (seconds)

The total amount of time it took to execute servlets and JSPs for this application.
Metric Summary
Collection
User Action
OC4J 11-3
OC4J All Instances Metrics
Application - Total Servlet, JSP and EJB Time (seconds)

The total amount of time it took to execute servlets, JSPs, and EJB methods for this
application.
Metric Summary
Collection
User Action
OC4J All Instances Metrics

Metrics for all OC4J instances.
OC4J Instances - Active Sessions

The number of active HTTP sessions used by all OC4J instances in the application
server.
Metric Summary
Collection
User Action
OC4J Instances - Request Processing Time (seconds)

The average amount of time it took to execute servlets and JSPs for all OC4J instances
in the application server during a recent interval. The interval is the period of time
specified as the collection frequency for this metric.
Metric Summary
Collection
User Action

OC4J Application Metrics
OC4J Instances - Requests Per Second

The rate at which servlets and JSPs are being invoked for all OC4J instances in the
application server during a recent interval. The interval is the period of time specified
as the collection frequency for this metric.
Metric Summary
Collection
User Action

Metrics for the application.
Application - Active EJB Methods

The number of EJB methods that are currently being executed by this application.
Metric Summary

Consecutive
All Every 5 After Every > Not Defined Not Defined 2 The number of active
Versions Minutes 12 Samples EJB methods for
application %name%
is %value%
Multiple Thresholds
"Application Name" object.
If warning or critical threshold values are currently set for any "Application Name"
To specify or change warning or critical threshold values for each "Application Name"
User Action
OC4J 11-5
Application - Active Requests

The number of servlets and JSPs currently being executed by this application.
Metric Summary

Consecutive
Versions Minutes 12 Samples servlets and JSPs for
application %name%
is %value%
Multiple Thresholds
User Action
Application - Active Sessions

The number of active HTTP sessions used by the application.
Metric Summary

Consecutive
Versions Minutes 12 Samples sessions for
application %name%
is %value%

Multiple Thresholds
User Action
Application - EJB Method Execution Rate (per second)

The rate at which EJB methods are currently being executed by this application.
Metric Summary
Collection
User Action
Application - EJB Method Execution Time (seconds)

The time it took to execute EJB methods for this application over a recent interval. The
Metric Summary

Consecutive
Versions Minutes 12 Samples execution time for an
EJB method for
application %name%
is %value% seconds
Multiple Thresholds
OC4J 11-7
User Action
Application - Request Processing Time (seconds)

The average amount of time it took to execute servlets and JSPs from this application
during a recent interval. The interval is the period of time specified as the collection
Metric Summary

Consecutive
servlet or JSP for
application %name%
is %value% seconds
Multiple Thresholds
User Action
Application - Requests Per Second

The rate at which servlets and JSPs are being invoked for this application during a
recent interval. The interval is the period of time specified as the collection frequency
for this metric.

OC4J EJB Metrics
Metric Summary
Collection
User Action
OC4J EJB Metrics

Metrics for EJBs.
EJB - Active Methods

The number of EJB methods that are currently being executed for this EJB.
Metric Summary

Consecutive
Versions Minutes 12 Samples EJB methods for EJB
%name%, EJB
module %oc4j_ejb_
module%,
application %oc4j_
ear% is %value%
Multiple Thresholds
unique combination of "EJB Name", "EJB Module Name", and "Application Name"
objects.
If warning or critical threshold values are currently set for any unique combination of
"EJB Name", "EJB Module Name", and "Application Name" objects, those thresholds
can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination
of "EJB Name", "EJB Module Name", and "Application Name" objects, use the Edit
Thresholds page. See the Editing Thresholds topic in the Enterprise Manager online
help for information on accessing the Edit Thresholds page.
User Action
OC4J 11-9
OC4J EJB Metrics
EJB - Method Execution Rate (per second)

The rate at which EJB methods are currently being executed for this EJB during a
for this metric.
Metric Summary
Collection
User Action
EJB - Method Execution Time (seconds)

The time it took to execute EJB methods for this EJB during a recent interval. The
Metric Summary

Consecutive
EJB method for EJB
%name%, EJB
module %oc4j_ejb_
module%,
application %oc4j_
ear% is %value%
seconds
Multiple Thresholds
unique combination of "EJB Name", "EJB Module Name", and "Application Name"
objects.
"EJB Name", "EJB Module Name", and "Application Name" objects, those thresholds
of "EJB Name", "EJB Module Name", and "Application Name" objects, use the Edit

OC4J EJB Module Metrics
User Action
Type of EJB
The type of the EJB: entity or session.
Metric Summary
Collection
User Action
None.

Metrics for EJB modules.
EJB Module - Active Methods

The number of EJB methods that are currently being executed by this EJB module.
Metric Summary

Consecutive
Versions Minutes 12 Samples EJB methods for EJB
module %name%,
application %oc4j_
ear% is %value%
Multiple Thresholds
unique combination of "EJB Module Name" and "Application Name" objects.
"EJB Module Name" and "Application Name" objects, those thresholds can be viewed
on the Metric Detail page for this metric.
of "EJB Module Name" and "Application Name" objects, use the Edit Thresholds page.
OC4J 11-11
See the Editing Thresholds topic in the Enterprise Manager online help for information
on accessing the Edit Thresholds page.
User Action
EJB Module - Method Execution Rate (per second)

The rate at which EJB methods are currently being executed for this EJB module
Metric Summary
Collection
User Action
EJB Module - Method Execution Time (seconds)

The time it took to execute EJB methods for this EJB module during a recent interval.
Metric Summary

Consecutive
EJB method for EJB
module %name%,
application %oc4j_
ear% is %value%
seconds
Multiple Thresholds
unique combination of "EJB Module Name" and "Application Name" objects.
"EJB Module Name" and "Application Name" objects, those thresholds can be viewed

OC4J Instance Metrics
of "EJB Module Name" and "Application Name" objects, use the Edit Thresholds page.
User Action

Metrics for the OC4J instance.
OC4J Instance - Active EJB Methods

The number of EJB methods that are currently being executed by this OC4J instance.
Metric Summary

Consecutive
Versions Minutes 12 Samples EJB methods is
%value%
User Action
OC4J Instance - Active Requests

The number of servlets and JSPs currently being executed by this OC4J instance.
Metric Summary

Consecutive
Versions Minutes 12 Samples servlets and JSPs is
%value%
OC4J 11-13
User Action
OC4J Instance - Active Sessions

The number of active HTTP sessions used by the OC4J instance.
Metric Summary

Consecutive
Versions Minutes 12 Samples sessions is %value%
User Action
OC4J Instance - Active Transactions

The number of transactions that are currently open for this OC4J instance.
Metric Summary

Consecutive
Versions Minutes 12 Samples transactions is
%value%
User Action
OC4J Instance - EJB Method Execution Rate (per second)

The rate at which EJB methods are currently being executed by this OC4J instance

Metric Summary
Collection
User Action
OC4J Instance - EJB Method Execution Time (seconds)

The time it took to execute EJB methods for this OC4J instance over a recent interval.
Metric Summary

Consecutive
EJB method is
%value% seconds
User Action
OC4J Instance - Heap Usage (MB)

The amount of heap space used by the OC4J instance.
Metric Summary

Consecutive
All Every 5 After Every > Not Defined Not Defined 2 Heap Usage is
Versions Minutes 12 Samples %value%MB
OC4J 11-15
User Action
OC4J Instance - Open JDBC Connections

The number of JDBC connections open by applications that are part of the OC4J
instance.
Metric Summary

Consecutive
Versions Minutes 12 Samples JDBC connections is
%value%
User Action
OC4J Instance - Request Processing Time (seconds)

The average amount of time it took to execute servlets and JSPs for this OC4J instance
Metric Summary

Consecutive
servlet or JSP is
%value% seconds
User Action

OC4J JSP Metrics
OC4J Instance - Requests Per Second

The rate at which servlets and JSPs are being invoked for this OC4J instance during a
for this metric.
Metric Summary
Collection
User Action
OC4J Instance - Start Time (ms since Epoch)

The time that the OC4J instance was started. It is represented in milliseconds since the
Unix epoch.
The Unix epoch is January 1, 1970.
Metric Summary
Collection
User Action
OC4J JSP Metrics

Metrics for JSPs.
Is multi-threaded?
Indicates whether or not this JSP is multi-threaded. The value of this metric will be
either TRUE or FALSE.
Metric Summary
Collection
OC4J 11-17
OC4J JSP Metrics
User Action
JSP - Active Instances (STM only)

The number of active instances of this JSP.
STM means single threaded model. This metric is only for single threaded JSPs, not
multi-threaded JSPs.
Metric Summary
Collection
User Action
JSP - Active Requests

The number of clients that are currently executing this JSP.
Metric Summary

Consecutive
Versions Minutes 12 Samples %name% JSPs for
web module %oc4j_
web_module%,
application %oc4j_
ear% is %value%
Multiple Thresholds
unique combination of "JSP Name", "Web Module Name", and "Application Name"
objects.
"JSP Name", "Web Module Name", and "Application Name" objects, those thresholds
of "JSP Name", "Web Module Name", and "Application Name" objects, use the Edit

OC4J JSP Metrics
User Action
JSP - Available Instances (STM only)

The number of available instances to execute this JSP.
STM means single threaded model. This metric is only for single threaded JSPs, not
multi-threaded JSPs.
Metric Summary
Collection
User Action
JSP - Client Processing Time (seconds)

The total time spent executing the client code for this JSP since this OC4J instance was
started.
Metric Summary

Consecutive
Versions Minutes 12 Samples processing time for
JSP %name%, web
module %oc4j_web_
module%,
application %oc4j_
ear% is %value%
seconds
Multiple Thresholds
unique combination of "JSP Name", "Web Module Name", and "Application Name"
objects.
OC4J 11-19
OC4J Servlet Metrics
"JSP Name", "Web Module Name", and "Application Name" objects, those thresholds
of "JSP Name", "Web Module Name", and "Application Name" objects, use the Edit
User Action
JSP - Requests Per Second

The rate at which this JSP has been invoked by clients during a recent interval. The
Metric Summary
Collection
User Action

Metrics for servlets.
Servlet - Active Requests

The number of clients that are currently executing this servlet.
Metric Summary

Consecutive
Versions Minutes 12 Samples %name% servlets for
web module %oc4j_
web_module%,
application %oc4j_
ear% is %value%

Multiple Thresholds
unique combination of "Servlet Name", "Web Module Name", and "Application Name"
objects.
"Servlet Name", "Web Module Name", and "Application Name" objects, those
of "Servlet Name", "Web Module Name", and "Application Name" objects, use the Edit
User Action
Servlet - Client Processing Time (seconds)

The average amount of time it took to execute the client code for this servlet during a
for this metric.
Metric Summary

Consecutive
Versions Minutes 12 Samples processing time for
servlet %name%,
web module %oc4j_
web_module%,
application %oc4j_
ear% is %value%
seconds
Multiple Thresholds
unique combination of "Servlet Name", "Web Module Name", and "Application Name"
objects.
"Servlet Name", "Web Module Name", and "Application Name" objects, those
of "Servlet Name", "Web Module Name", and "Application Name" objects, use the Edit
OC4J 11-21
OC4J Web Module Metrics
User Action
Servlet - Requests Per Second

The rate at which the servlet has been invoked by clients during a recent interval. The
Metric Summary
Collection
User Action

Metrics for OC4J web modules.
Web Module - Active Requests

The number of servlets and JSPs currently being executed by this web module.
Metric Summary

Consecutive
Versions Minutes 12 Samples servlets and JSPs for
web module
%name%,
application %oc4j_
ear% is %value%
Multiple Thresholds
unique combination of "Web Module Name" and "Application Name" objects.
"Web Module Name" and "Application Name" objects, those thresholds can be viewed

of "Web Module Name" and "Application Name" objects, use the Edit Thresholds page.
User Action
Web Module - Active Sessions

The number of active HTTP sessions used by this web module.
Metric Summary

Consecutive
Versions Minutes 12 Samples sessions for web
module %name%,
application %oc4j_
ear% is %value%
Multiple Thresholds
User Action
Web Module - Class Load Time (seconds)

The average time to load the classes for this web module during the last interval. The
Metric Summary
OC4J 11-23
Collection
User Action
Web Module - Client Time (seconds)

The average time spent executing client code for this web module during the last
metric.
Metric Summary
Collection
User Action
Web Module - Request Processing Time (seconds)

The average amount of time it took to execute servlets and JSPs for this web module
Metric Summary

Consecutive
servlet or JSP for
web module
%name%,
application %oc4j_
ear% is %value%
seconds
Multiple Thresholds

Resource Usage
User Action
Web Module - Requests Per Second

The number of servlets and JSPs processed by this web module since OC4J was
started.
Metric Summary
Collection
User Action
Resource Usage
Metrics for OC4J instance resource usage.
CPU Idle Time (%)

The percentage of idle CPU time.
Metric Summary
Collection
User Action
CPU Usage (%)

The percentage of the CPU time used by the OC4J instance.
OC4J 11-25
Resource Usage
Metric Summary

Consecutive
All Every 5 After Every > Not Defined Not Defined 2 CPU Utilization is
User Action
Free Memory (%)

The percentage of memory available.
Metric Summary
Collection
User Action
Free Memory (MB)

The amount of free memory on the system.
Metric Summary
Collection
User Action
Memory Usage (%)

The percentage of memory used by the OC4J instance.

Resource Usage
Metric Summary

Consecutive
User Action
Memory Usage (MB)

The amount of memory used by the OC4J instance.
Metric Summary
Collection
User Action
Other CPU Usage (%)

Shows the percentage of the CPU owned and used by host processes other than the
OC4J instance. If you are having problems with CPU usage on the OC4J host
computer, this metric can help you determine whether or not the OC4J instance is
causing the problem.
Metric Summary
Collection
User Action
which processes are consuming the most CPU. For more information, see "Viewing
OC4J 11-27
Resource Usage

This metric shows the percentage of host memory in use by processes and applications
other than the OC4J instance. If you are having problems with memory usage on the
OC4J host computer, this metric can help you determine whether or not the OC4J
instance is causing the problem.
Metric Summary
Collection
User Action

Shows the physical memory usage (in MB) by processes and applications other than
the OC4J instance. If you are having problems with memory usage on the OC4J host
computer, this metric can help you determine whether or not the OC4J instance is
causing the problem.
Metric Summary
Collection
User Action
Total Memory (MB)

The total amount of memory available.
Metric Summary
Collection

Response
User Action
Response
Response metrics for OC4J.
UpDown Status
Shows whether the OC4J server is up or down. If the value is 1, OC4J is up. If the
value is 0, it is down.
Metric Summary

Consecutive
All Every After Every = Not Defined 0 1 The OC4J instance is
Versions Minute 60 Samples down
User Action
If the OC4J instance is down, restart it using the Home page for the OC4J instance in
the Enterprise Manager Application Server Control Console.
OC4J 11-29
Response

12
OID LDAP Server
Oracle Enterprise Manager can be used to manage Oracle Internet Directory Server.
You can also use Enterprise Manager to view the metrics collected by Oracle Internet
Directory Server, Replication Server and Directory Integration Server.
(Critical Events)Security Events

This metric provides information about critical security events that occured in OID
LDAP servers.
Event Name
Shows the name of the event that occured.
User Action
None.
Event Result
Shows the result e.g. success, failure of the event that occured.
User Action
None.
Event Time
Shows the date and time stamp (in UTC) of the event occurence.
User Action
None.
Instance Number
Shows the OID LDAP server instance number for which this metric is collected.
User Action
None.
OID LDAP Server 12-1

(Critical Events)System Resource Events
Process ID
Shows the OID LDAP server instance number's process ID for which this metric is
collected.
User Action
None.
Sample ID
Shows an unique ID associated with the metric collection.
User Action
None.
User DN
Shows the identity of the user who logged into OID LDAP server and performed the
operation that triggered the event.
User Action
None.
(Critical Events)System Resource Events

This metric provides information about critical system resource events that occured in
OID LDAP servers.
Event Name
Shows the name of the event that occured.
User Action
None.
Instance Number
User Action
None.
Last Event Time

Shows the date and time stamp (in UTC) of last occurence of the event.
User Action
None.
Number of Event Occurence

Shows the number of times the event that occured.

(Resource Statistics)LDAP Server and System Memory
User Action
None.
Process ID
collected.
User Action
None.
Sample ID
User Action
None.
(Resource Statistics)LDAP Server and System Memory

This metric provides information about system memory and OID LDAP servers'
memory growth.
Date and Time Stamp

Shows the date and time stamp (in UTC) of the metric collection.
User Action
None.
Instance Number
User Action
None.
LDAP Server's average memory growth (%)

Shows the % memory growth of the OID LDAP server instance at the end of metric
collection periodicity.
User Action
Specific to your deployment.
Sample ID
User Action
None.

(Resource Statistics)LDAP Server's Data Base Usage
System's Total Free Physical Memory (KB)

Shows the free physical system memory (in KB) at the end of metric collection
periodicity.
User Action
(Resource Statistics)LDAP Server's Data Base Usage

This metric provides information about data base usage by OID LDAP servers.
Active Data Base Sessions

Shows the number of active database sessions of the OID LDAP server instance at the
end of metric collection periodicity.
User Action
Date and Time Stamp

User Action
None.
Instance Number
User Action
None.
Open Data Base Sessions

Shows the number of open database sessions of the OID LDAP server instance at the
end of metric collection periodicity.
User Action
Sample ID
User Action
None.

Configuration sets of LDAP Server
Configuration sets of LDAP Server

This metric provides information about configuration sets of OID LDAP servers. The
configuration parameters for OID LDAP server instances are stored in a directory
entry called a configuration set entry, or configset. A configuration set entry holds the
configuration parameters for a specific instance of the OID LDAP server.
Configuration set number

Shows an unique ID representing a configuration set.
User Action
None.
Max concurrent DB conn

Shows the OID LDAP server's maximum number of concurrent database connections.
User Action
None.
Non SSL port number

Shows the OID LDAP server's non-SSL mode default port. Its default value is 389.
User Action
None.
Number of server process

Shows the OID LDAP server's number of server processes to start.
User Action
None.
SSL authentication type

Shows SSL authentication type. You can use this to configure OID LDAP server with
no-authentication, one-way or two-way authentication by setting its value to 1, 32 or
64 respectively. Its default value is 1(no authentication).
User Action
None.
SSL enabled
Shows the OID LDAP server's flag for enabling or disabling SSL. You can use this to
configure OID LDAP server with non-SSL, SSL or both non-SSL and SSL modes by
setting its value to 0, 1 or 2 respectively. Its default value is 0 (non-SSL).
User Action
None.

Directory Integration Profiles
SSL port number

Shows the OID LDAP server's SSL mode default port. Its default value is 636.
User Action
None.
SSL Version
Shows SSL version. Its default value is 3.
User Action
None.
SSL wallet URL

Shows the location of the Oracle wallet. This must be set for both client and server. For
example this parameter could be set as file:/home/my_dir/my_wallet for UNIX, and
as file:C:\my_dir\my_wallet for Windows.
User Action
None.
Directory Integration Profiles

This metric provides basic status information about various DIP profiles configured in
the system.
Execution Errors
Shows the last error which have been encountered (if any) during the execution of the
integration profile.
Execution Status
Shows the current execution status of the integration profile.
Last Applied Change Number

Shows the Last ChangeNumber in OID which has been successfully synced /
propagated to the other end.
Last Execution Time

Shows the time when the profile was last executed by the DIP server.
Operation
Shows the Name of the integration profile as configured by the user. For provisioning
profiles, it shows the application and the appropriate identity realm of interest for
which the application needs provisioning events.

LDAP Entry Cache Hit Ratio
Schedule (secs)
Shows the scheduling interval of the integration profiles. DIP server executes the
profiles as per this scheduling interval.
State
Shows the state of the integration profile. (ENABLED / DISABLED).
Type
Shows the Type of the integration profile. (Synchronization Or Provisioning).
Directory Integration Server

This metric provides information about various DIP server instances running against
this OID.
Directory Integration Server Host

Shows the machine on which this DIP server is executing.
Downtime Count
Shows the number of times the DIP server wnet down unexpectedly.
Instance
Shows the instance Number of the Directory Integration Server.
LDAP Server
Shows the LDAP server against which this DIP server is executing.
Start Time
Shows the time when this DIP server started up.
LDAP All Instance IDs

This metric provides information about the OID LDAP server instances performing
metric collection.
Instance Number
Shows the OID LDAP server instance number performing metric collection.
User Action
None.
LDAP Entry Cache Hit Ratio

This metric provides information about performance of entry cache in OID LDAP
servers.

LDAP Load and Response
Date and Time Stamp

User Action
None.
Instance Number
User Action
None.
Process ID
collected.
User Action
None.
Sample ID
User Action
None.
Server Entry Cache Hit Ratio

Shows in percentage the entry cache hit ratio in OID LDAP server at the end of metric
collection periodicity.
User Action
LDAP Load and Response

This metric provides information about total number of LDAP operations in progress
and average LDAP operation response time in OID LDAP servers.
Date and Time Stamp

User Action
None.
Instance Number

LDAP Logon Session Statistics
User Action
None.
Sample ID
User Action
None.
Server Average Response Time (in Milliseconds)

Shows over the course of time period of metric collection, the average response time in
(milli seconds) of an LDAP operation in the OID LDAP server.
User Action
Server Load
Shows the number of LDAP operations in progress in the OID LDAP server at the end
of metric collection periodicity.
User Action
LDAP Logon Session Statistics

This metric provides information about total LDAP sessions established with OID
LDAP servers.
Date and Time Stamp

User Action
None.
Instance Number
User Action
None.
Sample ID
User Action
None.

LDAP Operations profile
Total LDAP Logon Sessions

Shows the number of LDAP sessions established with OID LDAP server at the end of
metric collection periodicity.
User Action
LDAP Operations profile

This metric provides information about LDAP operations completed by OID LDAP
servers.
Completed Add Operations

Shows over the course of time period of metric collection, the total number of LDAP
Add operations completed by the OID LDAP server instance.
User Action
Completed Compare Operations

Compare operations completed by the OID LDAP server instance.
User Action
Completed Delete Operations

Delete operations completed by the OID LDAP server instance.
User Action
Completed Login Operations

Bind operations completed by the OID LDAP server instance.
User Action
Completed Modify Operations

Modify operations completed by the OID LDAP server instance.
User Action

LDAP Server Total Memory Usage
Completed Search Operations

Search operations completed by the OID LDAP server instance.
User Action
Date and Time Stamp

User Action
None.
Instance Number
User Action
None.
Sample ID
User Action
None.
LDAP Server Response

For Oracle internal use only.
Status
Shows whether any OID LDAP server is up or not.
User Action
Total Number
Shows total number of OID LDAP servers up and running.
User Action
None.
LDAP Server Total Memory Usage

This metric provides information about total virtual memory usage by OID LDAP
servers.

LDAP Server Total User Sessions
Total Size (in KB)

Shows total virtual memory usage by OID LDAP servers.
User Action
LDAP Server Total User Sessions

This metric provides information about total LDAP user sessions currently established
with OID LDAP servers.
Total Users Sessions

Shows total LDAP user sessions currently established with OID LDAP server.
User Action
Running instances of LDAP Replication Server

This metric provides information about running instance of LDAP Replication server.
Config Set
Shows the LDAP replication server configuration set associated with the running
instance.
User Action
None.
Downtime Count
Shows since the time instance was first started, the number of times the instance went
down and was restarted by OID monitor daemon.
User Action
None.
Instance
Shows the running instance number.
User Action
None.
Oracle Directory Server

Shows the host name of the OID LDAP server to which the replication server connects.
User Action
None.

Running instances of LDAP Server
Start Time
Shows the time when the instance was first started.
User Action
None.
Running instances of LDAP Server

This metric provides information about running instances of OID LDAP servers.
Config Set Number

Shows the OID LDAP server configuration set associated with the running instance.
User Action
None.
Downtime Count
Shows since the time instance was first started, the number of times the instance went
down and was restarted by OID monitor daemon.
User Action
None.
Host Name
Shows the host name of the running instance.
User Action
None.
Instance Number
Shows the running instance number.
User Action
None.
Port Number
Shows the port number of the running instance.
User Action
None.
Up Since
Shows the time when the instance was first started.

Stopped instances of LDAP Server
User Action
None.
Stopped instances of LDAP Server

This metric provides information about instances of OID LDAP server which were
started earlier and are stopped now.
Config Set Number

Shows the OID LDAP server configuration set associated with the stopped instance.
User Action
None.
Host Name
Shows the host name of the stopped instance.
User Action
None.
Instance Number
Shows the instance number.
User Action
None.

13
Portal
You can use Oracle Enterprise Manager to monitor and manage OracleAS Portal.
Database Instance
The Database Instance metric provides information about the Oracle Database where
the OracleAS Portal schema is running.
Instance Name
The name of the Oracle Database where the OracleAS Portal schema is running.
Metric Summary
Collection
Data Source
This is obtained by selecting instance_name from the v$instance table.
User Action
Start Time
Shows the time the Oracle Database was last started.
Metric Summary
Collection
Data Source
This is obtained by selecting startup_time from the v$instance table.
Portal 13-1
Database Portlet Metrics
User Action
Version
The version of the Oracle Database being used.
Metric Summary
Collection
Data Source
This is obtained by selecting version from the v$instance table.
User Action
Specific to your site

The Database Portlet metric allows you to analyze the performance of individual
database portlets. For more information about database portlets, refer to the OracleAS
Portal Developer Kit (PDK) documentation at
http://portalstudio.oracle.com.
Additional OracleAS Portal documentation is also available in the documentation
section on Portal Center at http://portalcenter.oracle.com.
Cache Hits
The number of times database portlet content has been serviced by the cache.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Count of HTTP 200 Response codes

The number of successful requests, i.e. HTTP Response and Error Code: 200.

Metric Summary
Collection
Data Source
Not applicable.
User Action

The number of incomplete requests, i.e. HTTP Response and Error Code: 400.
Metric Summary
Collection
Data Source
Not applicable.
User Action

The number of unsuccessful server errors, i.e. HTTP Response and Error Code: 500.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Error Code: 500 typically means something is wrong with the server, check that the
server hosting the database portlet is accessible.
Portal 13-3
Count of requests which timed out

The number of requests to this database portlet that timed out.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Count of Resolved HTTP 300 Response codes

Note: A portlet that is initially redirected with a 300 response code, may get logged as
a 200 response code if it successfully returns content.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Count of Unresolved HTTP 300 Response codes

The number of unresolved redirects, i.e. HTTP Response and Error Code: 300.
Of those portlets that returned an HTTP Response Code of 300, this indicates how
many redirected requests remain unresolved. For example, an unresolved request gets
redirected to another address, that returns an unresolved error code.
Metric Summary
Collection

Data Source
Not applicable.
User Action
Database Portlet Average Time (msec)

The average time (msec) to request this database portlet.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Database Portlet Maximium Time (msec)

The maximum time (msec) to request this database portlet.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Database Portlet Minimum Time (msec)

The minimum time (ms) to request this database portlet.
Metric Summary
Portal 13-5
Collection
Data Source
Not applicable.
User Action
Last Response Code

The http response code of the last database portlet serviced by the provider.
Metric Summary
Collection
Data Source
Not applicable.
User Action
If this response code is not in the 200 or 300 range, there may be an issue with this
provider not providing content to the portal.
Requests
The number of requests made to this database portlet.
Metric Summary
Collection
Data Source
Not applicable.
User Action

Database Providers Metrics

The Database Providers metric allows you to analyze the performance of database
providers. For more information about Database Providers, refer to the OracleAS
Cache Hits
The number of times the database providers content has been serviced by the cache.
Metric Summary
Collection
Data Source
Not applicable.
User Action

Metric Summary
Collection
Data Source
Not applicable.
User Action

Metric Summary
Portal 13-7
Collection
Data Source
Not applicable.
User Action

Metric Summary
Collection
Data Source
Not applicable.
User Action

The number of requests that timed out.
Metric Summary
Collection
Data Source
Not applicable.
User Action

The number of successful resolved requests, i.e. HTTP Response and Error Code: 300.

Metric Summary
Collection
Data Source
Not applicable.
User Action

Metric Summary
Collection
Data Source
Not applicable.
User Action
Database Provider Portlets Average Time (msec)

The average time (in ms) to request database portlets.
Metric Summary
Portal 13-9

Consecutive
All Every 15 After Every > 4000 4500 1 The slowest average
Versions Minutes 12 Samples portlet response
timing for this
provider is
unacceptable.
Multiple Thresholds
"Provider Name" object.
If warning or critical threshold values are currently set for any "Provider Name" object,
To specify or change warning or critical threshold values for each "Provider Name"
Data Source
Not applicable.
User Action
Database Provider Portlets Maximium Time (msec)

The maximum time (in ms) to request database portlets.
Metric Summary

Consecutive
All Every 15 After Every > 6000 10000 1 The maximum
timing for this
provider is
unacceptable.
Multiple Thresholds

Data Source
Not applicable.
User Action
Database Provider Portlets Minimum Time (msec)

The minimum time (in ms) to request database portlets.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Database Provider Status

Indicates whether a specific database provider has a problem.
Metric Summary

Consecutive
All Every 15 After Every = Not Defined DOWN 1 The last response
Versions Minutes 12 Samples code from the a
portlet serviced by
this provider is
down.
Portal 13-11
Multiple Thresholds
Data Source
Not applicable.
User Action
If the status is 'down', it indicates that at least one of the portlets serviced by this
provider's last HTTP response code was unsuccessful. Investigate the provider to
determine what is causing the fault.
Offline
Indicates whether the database provider is currently offline.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Percentage of Database Provider HTTP 500 Response codes

The percentage of Database Provider requests that returned HTTP 500 response codes,
i.e. unsuccessful server errors.
Metric Summary

General Page Engine Metrics

Consecutive
All Every 15 After Every > 10 15 1 The percentage of
Versions Minutes 12 Samples portlet requests
returning
unsuccessful is
unacceptable for this
provider.
Multiple Thresholds
Data Source
Not applicable.
User Action
Requests
The number of requests serviced by this database provider.
Metric Summary
Collection
Data Source
Not applicable.
User Action

The General Page Engine metric allows you to analyze the performance of your
portal's Parallel Page Engine.
Portal 13-13
Average Queue Length

The average number of requests in the Parallel Page Engine internal portal content
request queue, since middle tier startup.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Average Time in Page Engine Queue (msec)

The average time (in ms) content requests have spent in the Parallel Page Engines
internal request queue.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Cache Hits
The number of requests for fully cached pages that resulted in content being returned
from the cache since middle tier startup.
Metric Summary
Collection

Data Source
Not applicable.
User Action
Percentage of Requests that were serviced by the cache

The percentage of requests for cacheable, fully assembled pages that resulted in a
cache hit.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Percentage of Requests Timing Out in the Page Engine Queue

The percentage of OracleAS Portal content requests that have timed out in the Parallel
Page Engine's internal request queue.
Metric Summary

Consecutive
All Every 10 After Every > 10 15 1 The percentge of
Versions Minutes 12 Samples requests that have
timed out in the
internal request
queue is
unacceptable.
Data Source
Not applicable.
Portal 13-15
User Action
Requests for cache enabled pages

The number of requests for cached enabled pages since middle tier startup.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Requests to the Cache

The number of requests for cacheable, fully assembled pages since middle tier startup.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Total Page Requests

The total number of requests for OracleAS Portal pages since middle tier startup.
Metric Summary
Collection

Page Engine Response Code Metrics
Data Source
Not applicable.
User Action

The Page Engine Response Code metrics provide HTTP response code information.
Percentage of http 200 responses

The percentage of portlets returning a 200 HTTP Response code - Successful Request.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Percentage of http 300 Resolved responses

The percentage of portlets returning a 300 HTTP Response code that were resolved. Of
those portlets that returned an HTTP Response Code of 300, how many were
redirected resolved.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Portal 13-17
Percentage of http 300 Unresolved responses

The percentage of portlets returning a 300 HTTP Response code that were unresolved.
Metric Summary
Collection
Data Source
Not applicable.
User Action

The percentage of portlets returning a 400 HTTP Response code - Unsuccessful
Request Incomplete.
Metric Summary
Collection
Data Source
Not applicable.
User Action

The percentage of portlets returning a 500 HTTP Response code - Unsuccessful Server
Errors.
Metric Summary
Collection

Data Source
Not applicable.
User Action
Timeouts
The number of timeouts registered by the Parallel Page Engine.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Total http 200 responses

The number of successful requests to portlets, i.e. HTTP Response and Error Code:
200.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Total http 300 Resolved responses

The number of successful resolved requests to portlets, i.e. HTTP Response and Error
Code: 300.
Portal 13-19
Metric Summary
Collection
Data Source
Not applicable.
User Action
Total http 300 Unresolved responses

The number of unresolved redirects from portlet requests, i.e. HTTP Response and
Error Code: 300.
Metric Summary
Collection
Data Source
Not applicable.
User Action

The number of incomplete requests to portlets, i.e. HTTP Response and Error Code:
400.
Metric Summary
Collection
Data Source
Not applicable.

User Action

Metric Summary
Collection
Data Source
Not applicable.
User Action
Total requests
The total number of portlets requested by the Parallel Page Engine.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Unresolved Redirects
The number of Unresolved Redirects registered by the Parallel Page Engine.
Metric Summary
Collection
Portal 13-21
Portal Homepage Metric
Data Source
Not applicable.
User Action
Portal Homepage Metric

The response of a request to the OracleAS Portal default home page.
Homepage Download (msec)

The time (in ms) to download the OracleAS Portal home page.
Metric Summary

Consecutive
All Every 5 After Every > 2000 3000 1 The Portal Instance
Versions Minutes 12 Samples homepage
performance is
unacceptable.
Data Source
Not applicable.
User Action
Status
Indicates whether or not the OracleAS Portal home page has been called successfully.
The status value '1' indicates success.
Metric Summary

Response Metric

Consecutive
All Every 5 After Every = Not Defined 0 1 The Portal instance
Versions Minutes 12 Samples is not accessible.
Data Source
Not applicable.
User Action
Portal Metadata Repository Version Metric

The Portal Metadata Repository Version Metric indicates the version of OracleAS
Portal that is currently running.
Portal Metadata Repository Version

The version of OracleAS Portal that is currently running.
Not applicable.
Metric Summary
Collection
User Action
Response Metric
The response of two requests to test the status of OracleAS Portal.
Status
Indicates whether or not OracleAS Portal is functioning.
The status is based on the success of two URL calls, one to a test package via mod_
plsql and the other to the Parallel Page Engine (PPE):
■ mod_plsql ping to:
<protocol>://<host>:<port>/pls/<DAD>/htp.p?cbuf=Test
■ PPE ping to: <protocol>://<host>:<port>/portal/page
Portal 13-23
Syndication Server Status Metric
Metric Summary

Consecutive
All Every 5 After Every = Not Defined 0 1 The Portal instance
Versions Minutes 12 Samples is not accessible.
Data Source
Not applicable.
User Action
Syndication Server Status Metric

The Syndication Server Status Metric provides status information for the Syndication
Server.
Syndication Server Status

If the status value is '1', the Syndication Server is available.
Metric Summary

Consecutive
All Every 10 After Every = Not Defined 0 1 The Syndication
Versions Minutes 12 Samples Server is not
accessible.
Data Source
Not applicable.
User Action

Ultra Search Status Metric
Top Level Monitoring Status Metric

The Top Level Monitoring Status Metric indicates whether or not the services required
by OracleAS Portal to monitor the portal instance are up and running.
Top Level Monitoring Status

Indicates whether or not the services required by OracleAS Portal to adequately
monitor the portal instance are running. The status value '1' indicates the services are
running OK.
The test involves an HTTP ping check on the monitoring witness servlet. This also
tests the DMS servlet and therefore, the ability to obtain OracleAS Portal DMS based
metrics, such as the Provider, Portlet and Page Engine metrics.
By default, a critical or warning threshold value (or both) is set for this metric column.
Alerts are generated when threshold values are reached. You can edit these threshold
values, if required.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Ultra Search Status Metric

The Ultra Search Status Metric provides status information for Oracle Ultra Search.
Ultra Search Status

If the status value is '1', users can login to the Ultra Search administration tool via SSO
in an Oracle Internet Directory (OID) enabled database tier environment.
Metric Summary
Portal 13-25
Web Portlet Metrics

Consecutive
All Every 10 After Every = Not Defined 0 1 Ultra Search is not
Versions Minutes 12 Samples accessible.
Data Source
Not applicable.
User Action
Web Portlet Metrics

The Web Portlet Metric allows you to analyze the performance of individual Web
provider portlets. For more information about Web providers, refer to the OracleAS
Cache Hits
The number of times the portlet's content has been serviced by the cache.
Metric Summary
Collection
Data Source
Not applicable.
User Action

Metric Summary

Web Portlet Metrics
Collection
Data Source
Not applicable.
User Action

Metric Summary
Collection
Data Source
Not applicable.
User Action

Metric Summary
Collection
Data Source
Not applicable.
User Action

Portal 13-27
Web Portlet Metrics
Metric Summary
Collection
Data Source
Not applicable.
User Action

Metric Summary
Collection
Data Source
Not applicable.
User Action

Metric Summary
Collection
Data Source
Not applicable.

Web Portlet Metrics
User Action
Last Response Code

The HTTP response code of the last portlet serviced by the provider.
Metric Summary
Collection
Data Source
Not applicable.
User Action
If this response code is not in the 200 or 300 range, this provider may not be providing
content to OracleAS Portal.
The administrator should check that the machine hosting the provider is accessible,
and the specific Provider on that machine is working by using the PDK Java test page.
Requests
The number of requests made to this Web portlet.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Web Portlet Average Time (msec)

The average time (in ms) to request this Web portlet.
Metric Summary
Portal 13-29
Web Providers Metrics
Collection
Data Source
Not applicable.
User Action
Web Portlet Maximium Time (msec)

The maximum time (in ms) to request this Web portlet.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Web Portlet Minimum Time (msec)

The minimum time (in msec) to request this Web portlet.
Metric Summary
Collection
Data Source
Not applicable.
User Action

The Web Providers metric allows you to analyze the performance of Web providers.

For more information about Web providers, refer to the OracleAS Portal Developer Kit
(PDK) documentation at http://portalstudio.oracle.com.
Cache Hits
The number of times the Provider's content has been serviced by the cache.
Metric Summary
Collection
Data Source
Not applicable.
User Action

The number of successful requests to portlets, i.e. HTTP Response and Error Code:
200.
Metric Summary
Collection
Data Source
Not applicable.
User Action

The percentage of portlets returning a 400 HTTP Response code - Unsuccessful
Request Incomplete.
Metric Summary
Portal 13-31
Collection
Data Source
Not applicable.
User Action

Metric Summary
Collection
Data Source
Not applicable.
User Action

Metric Summary
Collection
Data Source
Not applicable.
User Action


Metric Summary
Collection
Data Source
Not applicable.
User Action

Metric Summary
Collection
Data Source
Not applicable.
User Action
Offline
Indicates if a Web provider is currently offline.
Metric Summary
Collection
Portal 13-33
Data Source
Not applicable.
User Action
Percentage of Web Provider HTTP 500 Response codes

The percentage of Web Provider requests that returned HTTP 500 response codes, i.e.
unsuccessful server errors.
Metric Summary

Consecutive
All Every 15 After Every > 10 15 1 The percentage of
Versions Minutes 12 Samples portlet requests
returning
unsuccessful is
unacceptable for this
provider.
Multiple Thresholds
Data Source
Not applicable.
User Action
Requests
The number of requests serviced by this Web provider.
Metric Summary

Collection
Data Source
Not applicable.
User Action
Web Provider Portlets Average Time (msec)

The average time (in ms) to request Web provider portlets.
Metric Summary

Consecutive
All Every 15 After Every > 4000 4500 1 The slowest average
timing for this
provider is
unacceptable.
Multiple Thresholds
Data Source
Not applicable.
User Action
Web Provider Portlets Maximium Time (msec)

The maximum time (in ms) to request Web provider portlets.
Portal 13-35
Metric Summary

Consecutive
All Every 15 After Every > 6000 10000 1 The maximum
timing for this
provider is
unacceptable.
Multiple Thresholds
Data Source
Not applicable.
User Action
Web Provider Portlets Minimum Time (msec)

The minimum time (in ms) to request Web provider portlets.
Metric Summary
Collection
Data Source
Not applicable.
User Action

Web Provider Status

Indicates whether a specific Web provider has a problem.
Metric Summary

Consecutive
All Every 15 After Every = Not Defined DOWN 1 The last response
Versions Minutes 12 Samples code from the a
portlet serviced by
this provider is
down.
Multiple Thresholds
Data Source
Not applicable.
User Action
If the status is 'down', it indicates that at least one of the portlets serviced by this
provider's last HTTP response code was unsuccessful. Investigate the provider to
determine what is causing the fault.
Portal 13-37

14
Reports Server
You can use Oracle Enterprise Manager to monitor and manage Oracle Reports Server.
Cluster Information
Provides information about the cluster under which various Reports Servers might be
running.
Current Jobs
Provides the total number of currently running jobs in the Reports Server Cluster Job
Queue.
Failed Jobs
Provides the total number of jobs for the listed Reports Server cluster that were
stopped before completion. This includes cancelled jobs as well as those terminated
with error.
Finished Jobs
Provides the total number of finished jobs currently in the Reports Server cluster.
Response Time (ms)

Provides the average number of milliseconds it takes for the listed Reports Server
cluster to process a request from the client.
Scheduled Jobs
Provides the total number of scheduled jobs currently in the listed Reports Server
Cluster Job Queue.
Current Jobs
Provides information about the currently running jobs in the Reports Server.
Job Name
If you specified a job name in the command line you used to run this job, that name is
listed here. Otherwise, it is the name of the job provided for the "report=" or
"module=" parameter of the job request.
Reports Server 14-1

Engine Information
Output Format
Provides the output format (desformat) specified for this job at runtime.
Output Type
Provides the destination type (destype) specified for this job at runtime.
Owner
Provides the user ID under which this job is running.
Queued At
Provides the date and time this job request was placed in the Job Queue.
Started At
Provides the date and time this job started running.
Status
Provides the status of the current job.
Engine Information
Provides the types and numbers of currently running engines on the selected Reports
Server.
Engines
Provides the total number of this type of engine that is currently running on the
selected Reports Server.
Running
Provides the number of engines currently running (active) in the Reports Server
processing requests.
Failed Jobs
Provides the total number of jobs currently in the selected Reports Server's Job Queue
that were stopped before completion. This includes cancelled jobs as well as those
terminated with error. When this number is higher than 0, it links to the Failed Jobs
Queue, where you can get detail on why a job failed, view the job's trace file, and
resubmit the job.
Finished At
Provides the date and time this job was cancelled or terminated with error.

Finished Jobs
Job Name
If you specified a job name in the command line you used to run this report, that name
is listed here. Otherwise, it is the name of the job provided for the "report=" or
"module=" parameter of the report request.
Output Format
Provides the destination format (desformat) specified for this report at runtime.
Output Type
Owner
Provides the user ID under which this job was run.
Queued At
Started At
Status
Provides the status of the job. Status will either indicate that the job was cancelled by
the user or provide some information on why the job was terminated with error.
Finished Jobs
Provides a detailed look at all successfully completed jobs in the Job Queue on the
selected Reports Server.
Finished At
Provides the date and time this job completed.
Job Name
If you specified a job name in the command line you used to run this report, that name
is listed here. Otherwise, it is the name of the job provided for the "report=" or
"module=" parameter of the job request. Job Name is linked to the output of this job.
Click Job Name to see a Web version of this job's output (fetched from the Reports
Server cache).
Output Format
Provides the destination format (desformat) specified for this job at runtime.
Output Type
Reports Server 14-3

Response
Owner
Provides the user ID under which this job was run.
Queued At
Started At
Status
Provides the finished status of the job. In the Finished Job Queue, Status is always
Finished Successfully.
Response
Provides the average number of milliseconds it takes for the selected Reports Server to
process a request from the client.
Server Status
Indicates whether the server is up or down.
Metric Summary

Consecutive
All Every 5 After Every = Not Defined 0 1 Not Defined
Versions Minutes Sample
Scheduled Jobs
Provides a detailed look at all jobs scheduled to run on the selected Reports Server and
supplies the means of cancelling a scheduled job.
Job Name
Provides a detailed look at all jobs currently running on the selected Reports Server
and supplies the means of cancelling a currently running job.
Last Run At
Provides the time the current job was processed.

Server Information
Next Run At
Provides the time when the current job will run again.
Output Format
Provides the output format (desformat) specified for this job at runtime.
Output Type
Owner
Provides the user ID under which this job is running.
Repeat Interval
Provides the frequency at which the current job is scheduled to run. For example,
daily, monthly, and so on. This setting only appears on the Reports Server Scheduled
Job Queue page.
Server Information
Provides information about the Reports Server, number of engines, and other
parameters related to the Reports Server. This information looks at the entire lifecycle
of the Reports Server for all the requests handled by the Reports Server, while the
Server Performance Data metrics measure the performance of the Reports Server on a
real time basis where the metrics generated are based on the requests handled by the
Reports Server in last 5 minutes.
Active Engines
Provides the number of engines currently running on the selected Reports Server.
Average Elapsed Time (ms)

Provides the time the current job has been running in the Reports Server and has not
yet finished. This metric will be non-zero when a currently running job has been
running longer than the default Elapsed Time Limit (currently at 3 minutes). The
Elapsed Time Limit can be modified by configuring the Reports Server target from
Oracle Enterprise Manager (Grid Control).
Average Response Time (ms)

Provides the average number of milliseconds it takes for the selected Reports Server to
process a request from the client.
Cluster Name
If the selected Reports Server is a member of a server cluster, the cluster name is listed
here.
Current Jobs
Provides the total number of currently running jobs in the Job Queue.
Reports Server 14-5

Server Performance Data
Failed Jobs
Provides the total number of jobs currently in the Job Queue that were stopped before
completion. This includes cancelled jobs as well as those terminated with error.
Failed Ratio (%)

Indicates the health of the Reports Server. This is the ratio of failed jobs to current jobs
(failed jobs / (past jobs + failed jobs)).
Finished Jobs
Provides the total number of jobs that have finished running successfully. When this
number is higher than 0, it links to the Finished Jobs Queue, where you can get more
detail on the finished job, view the job's trace file, view the job result from cache, and
resubmit the job.
Scheduled Jobs
Provides the total number of jobs currently in the Scheduled Jobs Queue. When this
number is greater than 0, it links to the Scheduled Jobs Queue, where you can view
details and canceled the scheduled job.
Since (Start Time)

Provides the date and time the selected Reports Server was last started.
Trace File Name

Provides the Reports Server trace file name.
Trace Mode
Provides the trace mode specified in the Reports Server configuration file for the trace
log file, either Replace (the default) or Append. Trace Replace replaces the existing text
in the trace log file with new information. Trace Append appends new information to
the end of existing trace log file.
Transferred Jobs
In a clustered server environment, provides the total number of jobs transferred
between the selected Reports Server and other cluster members. For example, if the
selected Reports Server receives a request for a job that was run earlier on another
cluster member, the request is transferred to the cluster member that provided the
earlier result and the result is delivered to the client from the cluster member's cache.
Such a transaction would be counted as one transfer within the cluster.
Version
Provides the current version of the Reports Server.

Provides metrics for the jobs processed/requested for the last 5 minutes. Server
Performance Data metrics are similar to Server Information metrics; the Server

Information metrics are examined to generate metrics numbers for the jobs
processed/requested for the last 5 minutes.
Active Engines
Provides the number of engines currently running on the selected Reports Server.
Metric Summary
Collection
Average Elapsed Time to date (ms)

Provides the averaged elasped time for all jobs that have run in the Reports Server in
the last 5 minutes. This metric will be non-zero when any running job runs longer than
the default Elapsed Time Limit (currently at 3 minutes). The Elapsed Time Limit can be
modified by configuring the Reports Server target from Oracle Enterprise Manager
(Grid Control).
Metric Summary
Collection
Cluster Name
If the selected Reports Server is a member of a server cluster, the cluster name is listed
here.
Metric Summary
Collection
Current Job Load

Provides the number of jobs (failed, successful, and currently running) in the Reports
Server for a period of time (5 minutes).
Metric Summary
Reports Server 14-7

Collection
Current Jobs
Provides the total number of currently running jobs in the Job Queue.
Metric Summary
Collection
Failed Jobs
Provides the total number of jobs currently in the Job Queue that were stopped before
completion. This includes cancelled jobs as well as those terminated with error.
Metric Summary
Collection
Job Load
Provides the number of failed and successful jobs processed by the Reports Server in
the last 5 minutes.
Metric Summary
Collection
Scheduled Jobs
Provides the total number of jobs currently in the Scheduled Jobs Queue. When this
number is greater than 0, it links to the Scheduled Jobs Queue, where you can view
details and canceled the scheduled job.
Metric Summary

Collection
Since (Start Time)

Provides the date and time the selected Reports Server was last started.
Metric Summary
Collection
Successful Jobs
Provides the number of successful jobs processed by the Reports Server in the last 5
minutes.
Metric Summary
Collection
Trace File Name

Provides the Reports Server trace file name.
Metric Summary
Collection
Trace Mode
Indicates the trace mode specified in the Reports Server configuration file for the trace
log file, either Replace (the default) or Append. Trace Replace replaces the existing text
in the trace log file with new information. Trace Append appends new information to
the end of existing trace log file.
Metric Summary
Reports Server 14-9

Collection
Transferred Jobs
In a clustered server environment, provides the total number of jobs transferred
between the selected Reports Server and other cluster members. For example, if the
selected Reports Server receives a request for a job that was run earlier on another
cluster member, the request is transferred to the cluster member that provided the
earlier result and the result is delivered to the client from the cluster member's cache.
Such a transaction would be counted as one transfer within the cluster.
Metric Summary
Collection
Version
Provides the current version of the Reports Server.
Metric Summary
Collection

15
Single Sign-On Server
You can use the Single Sign-On Server metrics to monitor load and user activity on the
OracleAS Single Sign-On Server. Statistics are for the previous 24 hours.
Login Server Metrics For The Last 24 Hours

These Login Server metrics provide information about login activity on the OracleAS
Single Sign-On Server over the last 24 hours.
Number of Login Attempts

The total number of login attempts over the last 24 hours.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Number of Successful Login Attempts

The total number of successful login attempts over the last 24 hours.
Metric Summary
Collection
Single Sign-On Server 15-1

Login Server Metrics For The Last 24 Hours
Data Source
Not applicable.
User Action
Number of Unsuccessful Login Attempts

The total number of unsuccessful login attempts over the last 24 hours.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Percentage of Successful Logins

The percentage of successful login attempts over the last 24 hours.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Percentage of Unsuccessful Logins

The percentage of unsuccessful login attempts over the last 24 hours.
Metric Summary

Login Server Metrics For The Last Hour
Collection
Data Source
Not applicable.
User Action

These metrics provide information about login activity on the OracleAS Single
Sign-On Server over the last hour.
Number of Login Attempts

The total number of login attempts over the last hour.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Number of Successful Login Attempts

The total number of successful login attempts over the last hour.
Metric Summary
Collection
Data Source
Not applicable.
User Action

Number of Unsuccessful Login Attempts

The total number of unsuccessful login attempts over the last hour.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Percentage of Successful Logins

The percentage of successful login attempts over the last hour.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Percentage of Unsuccessful Logins

The percentage of unsuccessful login attempts over the last hour.
Metric Summary
Collection
Data Source
Not applicable.

Most Failed Login Users Metrics
User Action
Most Failed Login Users Metrics

The Most Failed Login Users Metrics provide detailed information about each failed
login attempt, including the time when the failure happened and the IP address of the
machine where the user attempted to login.
Frequency
The number of times a user has failed to login during the previous 24 hours.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Subscriber ID
The subscriber ID of the user trying to log in.
Metric Summary
Collection
Data Source
Not applicable.
User Action
Subscriber Name
The subscriber name of the user trying to log in.
Metric Summary

SSO Database Instance Metric
Collection
Data Source
Not applicable.
User Action
SSO Database Instance Metric

The Database Instance metric provides information about the Oracle Database that the
OracleAS Single Sign-On Server schema is running on.
Instance Name
The name of the Oracle Database where the OracleAS Portal schema is running.
Metric Summary
Collection
Data Source
This is obtained by selecting instance_name from the v$instance table.
User Action
Start Time
Shows the time at which the Oracle Database was last started.
Metric Summary
Collection
Data Source
This is obtained by selecting startup_time from the v$instance table.
User Action

SSO Status Metric
Version
The version of the Oracle Database being used.
Metric Summary
Collection
Data Source
This is obtained by selecting version from the v$instance table.
User Action
SSO Status Metric

The SSO Status metrics allow you to monitor the status of the OracleAS Single Sign-On
Server.
Status
Indicates whether the Single Sign-On Server is accessible.
Metric Summary

Consecutive
All Every 5 After Every = Not Defined 0 1 The SSO instance is
Versions Minutes 12 Samples not accessible.
Data Source
This status test involves pinging a package on the Single Sign-On Server schema using
mod_plsql.
User Action
If this status test fails, it indicates that there is an issue with one or more of the
components that the Single Sign-On Server depends on. For example, the Single
Sign-On Server Database Access Descriptor (DAD) may have an incorrect password,
the Oracle HTTP Server may be down, or the Oracle Database the schema is running
on may be unaccessible.

SSO Status Metric

16
Web Cache
You can use Oracle Enterprise Manager to view the overall status of Oracle9IAS Web
Cache. You can also use Enterprise Manager to view Oracle9IAS Web Cache
performance metrics that have been collected by the Oracle Agent.
Cache Performance
This metric serves as a container for the Oracle9iAS Cache Performance metrics.
Allocated Cache Memory (%)

The percentage of the maximum cache size that is allocated to cached objects. The
maximum cache size is configured in the Resource Limits page of OracleAS Web
Cache Manager.
Metric Summary

Consecutive
All Every 5 After Every > 90 99 2 The cache is using
Versions Minutes 12 Samples %value%%% of its
allocated memory
User Action
When the cache size reaches 90 percent, the cache will start forced garbage collection.
Cacheable Misses (% of requests)

The percentage of requests for content which is cachable but was not available in the
cache.
Metric Summary
Web Cache 16-1

Cache Performance
Collection
User Action
Check caching rules configuration in OracleAS Web Cache Manager.
Cached Documents Count

The number of objects stored in the cache, plus the number of objects in transit
through the cache. The number includes objects that have expired or have been
invalidated but which have not been deleted from the cache. For a cache cluster
member, this number represents owned content.
Metric Summary
Collection
User Action
No user action necessary. This metric is intended for informational purposes only.
Compression Savings (%)

The number of bytes that are saved due to in-cache compression as a percentage of the
total number of bytes, before compression, in the documents served.
Metric Summary
Collection
User Action
Data Served (MB/second)

The average number of megabytes served by the cache per second during the current
time period.
Metric Summary

Cache Performance
Collection
User Action
Errors (% of requests)
The percentage of requests that resulted in the cache serving error pages to Web
browsers.
Metric Summary
Collection
User Action
Refer to the specific error being served.
Hit Rate Per Second

The average number of requests served by cache content per second during the
current time period.
Metric Summary
Collection
User Action
If the number of hits is low, then perform the following:
1. Review the caching rules configuration in Oacle9iAS Web Cache Manager.
2. In the Popular Requests page in Oacle9iAS Web Cache Manager, select the Not
Cached from the Filter Documents list to view the most frequent misses.
Hits (% of requests)
The percentage of requests resolved by cache content. This percentage should be high,
except when objects are being invalidated.
Metric Summary
Web Cache 16-3

Cache Performance


Consecutive
All Every 5 After Every < 30 20 3 %value%%% of
Versions Minutes 12 Samples requests were cache
hits
User Action
If the percentage of hits is low, then perform the following:
Invalidated Objects Per Second

The average number of objects invalidated from the cache per second during the
current time period.
Metric Summary
Collection
User Action
The ratio of invalidated objects to invalidation requests can help you determine
invalidation performance.
Invalidation Requests Per Second

The average number of invalidation requests processed by the cache per second
during the current time period.
Metric Summary

Cache Performance

Consecutive
All Every 5 After Every > 100 120 2 The cache
Versions Minutes 12 Samples encountered
%value%
invalidation requests
per second
User Action
Note that if invalidation is frequent, then performance may be effected.
Misses Per Second

The average number of requests per second for cacheable and non-cacheable content
that were not served by the cache during the current time period.
Metric Summary
Collection
User Action
If the number of misses is high, then perform the following:
Network Errors Per Second

The number of error pages that the cache has served per second to Web browsers due
to a network error while connecting, sending, or receiving a response from an origin
server.
Metric Summary
Web Cache 16-5

Cache Performance

Consecutive
All Every 5 After Every > .5 1 2 The cache
%value% network
errors per second
User Action
If the number of network errors is consistently high, then consider improving the
network connection between the cache and origin server.
Noncacheable Misses (% of requests)

The percentage of requests for non-cacheable content that was not served by the cache.
Metric Summary
Collection
User Action
If the number of hits is low, then perform the following:
1. Review the caching rules configuration in OracleAS Web Cache Manager.
2. In the Popular Requests page in OracleAS Web Cache Manager, select the Not
Cached from the Filter Documents list to view the most frequent misses. In
addition, view the Cache Reason for the most frequent requests that were not
cached.
Open Connections
The number of incoming open connections to the OracleAS Web Cache server and
outgoing open connections to the origin servers.
Metric Summary
Collection
User Action

Cache Performance
Partial Page Errors Per Second

to an HTML fragment retrieval problem for a page that supports partial page caching.
This number includes errors returned when an uncaught exception occurs in the cache
during ESI parsing or when the default ESI fragment is served. A default ESI fragment
is served when OracleAS Web Cache is unable to fetch the src specified in an
<esi:include> tag.
Metric Summary

Consecutive
%value% partial
page errors per
second
User Action
If the number of partial-page errors is consistently high, then improve the origin server
side code that generates the ESI pages to catch exceptions.
Refreshes (% of requests)
The percentage of requests that resulted in the cache refreshing content from the origin
servers.
Metric Summary
Collection
User Action
Requests Per Second

The average number of requests served by the cache per second during the current
time period.
Metric Summary
Web Cache 16-7

Cache Performance
Collection
User Action
Site Busy Errors Per Second

The number of error pages that the cache has served per second to Web browsers
when origin server capacity has been reached.
Metric Summary

Consecutive
%value% site busy
errors per second
User Action
If the number of site-busy errors is consistently high, then increase the capacity of the
origin servers in the Origin Server page or OracleAS Web Cache Manager.
Size of Cached Documents (MB)

The size, in megabytes, of the objects currently stored in the cache. For a cache cluster
member, this number is an aggregate of the owned and on-demand objects.
Metric Summary
Collection
User Action
Stale Hits (% of requests)

The percentage of requests resolved by expired or invalidated content in the cache.

Cache Performance
Metric Summary

Consecutive
All Every 5 After Every > 70 80 2 %value%%% of hits
Versions Minutes 12 Samples were stale cache hits
User Action
If the percentage of stale hits is high, then ensure that expired or invalidated pages are
updated from the origin server in a timely fashion. Check the network capacity
between the OracleAS Web Cache computer and the origin server.
Total Errors Per Second

The average number of error pages that the cache has served per second to Web
browsers during the current time period.
Metric Summary
Collection
User Action
Up Since
The time at which the cache was started or restarted.
Metric Summary
Collection
User Action
Web Cache 16-9

ESI Errors
ESI Errors
These metric columns provide information about OracleAS Web Cache EdgeSide
Includes.
ESI Exceptions Not Caught Per Second

to Edge Side Include (ESI) exception errors. These error pages are typically the result
of ESI syntax errors.
Metric Summary
Collection
User Action
If the number of exception errors is consistently high, then improve the origin server
side code that generates the ESI pages to catch exceptions.
Times Default ESI Fragment Served Per Second

The number of default Edge Side Include (ESI) fragments that the cache has served per
second to Web browsers. A default ESI fragment is served when when OracleAS Web
Cache is unable to fetch the src specified in an <esi:include> tag and the alt
attribute, onerror attribute, or the try |attempt |except block are either not
present or fail.
Metric Summary
Collection
User Action
If the number of default ESI fragments is consistently high, then review the ESI code.
Resource Usage
These metric columns provide information about CPU and memory usage.
CPU Idle Time (%)

The percentage of system CPU time that is idle.
Metric Summary

Resource Usage
Collection
User Action
If the load is high, then consider upgrading the cache computer.
Free Memory (%)

The amount of free physical memory, in megabytes, for the system.
Metric Summary
Collection
User Action
Free Memory (MB)

The amount of free physical memory, in megabytes, for the system.
Metric Summary
Collection
User Action
Other CPU Usage (%)

The percentage of the CPU usage by applications other than OracleAS Web Cache.
Metric Summary
Collection
User Action
If CPU usage is high, then consider upgrading the cache computer.
Web Cache 16-11

Resource Usage

The percentage of physical memory used by applications other than OracleAS Web
Cache.
Metric Summary
Collection
User Action

The physical memory usage, in megabytes, by applications other than OracleAS Web
Cache.
Metric Summary
Collection
User Action
Total Memory (MB)

The amount of physical memory, in megabytes, for the system.
Metric Summary
Collection
User Action
Web Cache CPU Usage (%)

The percentage of the CPU that is being used for OracleAS Web Cache. As traffic
increases, CPU utilization increases.

Resource Usage
Metric Summary

Consecutive
All Every 5 After Every > Not Defined Not Defined 2 CPU Utilization is
User Action
Web Cache Memory Usage (%)

The percentage of the physical memory used by OracleAS Web Cache.
Metric Summary

Consecutive
User Action
Web Cache Memory Usage (MB)

The amount of physical memory, in megabytes, that is being used by OracleAS Web
Cache.
Metric Summary
Collection
Web Cache 16-13

Response
User Action
Response
This category indicates whether the OracleAS Web Cache instance is up and running
or down and unavailable.
Status
This metric indicates whether the OracleAS Web Cache instance is up and running or
down and unavailable.
Metric Summary

Consecutive
9.0.4.x Every After Every = Not Defined 0 1 The Webcache
Minute 60 Samples instance is down
User Action
Server Performance
The columns in this metric provide information about the performance of origin
server.
Active Requests
The current number of open connections that the cache has open to the origin server
per second.
Metric Summary
Collection
User Action
If the number is close to the connection limit, then set a larger capacity for the origin
server in the Origin Servers page of OracleAS Web Cache Manager.

Server Performance
Processing Time (seconds)

The average number of seconds used to process a request during the current time
period.
Metric Summary
Collection
User Action
If the number is low, then improve the connection between the cache and origin server,
or upgrade the origin server computer.
Proxy Server
Specifies whether or not the origin server is a proxy server. YES specifies that the
origin server is a proxy server. NO specifies that the origin server is an application
Web sever.
Metric Summary
Collection
User Action
Requests Per Second

The average number of requests served per second during the current time period.
Metric Summary
Collection
User Action
If this number is high, then increase the capacity of this origin server in the Origin
Servers page of OracleAS Web Cache Manager, or load balance the requests among
cache cluster members.
Web Cache 16-15

Server Performance
Status
The current status of the origin server. An up status specifies that the last
communication with the origin server was successful. A down status specifies that the
origin server is down. If this is the last origin server in a single or multiple server
configuration, OracleAS Web Cache continues to forward requests to the origin server.
If this is not the last server, then no new requests will be sent to origin server.
However, OracleAS Web Cache will poll the inactive origin server until it is back
online.
Metric Summary
Collection
User Action

17
Web Application
You can use Oracle Enterprise Manager to view performance and availability metrics
for your Web applications. For more information, see "Introduction to Managing Web
Applications" in the Enterprise Manager online help.
HTTP Content
This metric serves as a container for a set of metrics that provide you with information
about the content of the Web pages you are monitoring, as well as response time
information.
Average Connect Time

This metric measures the average connect time for all pages in the transaction. This is
calculated as: Total Connect Time / Number of Connections Made. The Connect Time
is one of the phases of a transaction that can help you isolate and fix response time
problems.
User Action
The average connect time, when reviewed over a period of time, can indicate whether
network congestion or other connectivity issues are the cause of poor Web application
response time.
Average First Byte Time

This metric measures the average First Byte Time for all pages in the transaction. This
metric is computed as: Total First Byte Time / Number of Requests Made (either to
fetch HTML or content). The First Byte time is one of the phases of a transaction that
can help you isolate and fix response time problems.
User Action
The Average First Byte Time, when reviewed over a period of time, can indicate
whether network congestion or other connectivity issues are the cause of poor Web
application response time.
Average Page Response

A single transaction often accesses multiple Web pages. The Average Page Response
metric calculates the average response time of the pages within a single transaction.
This metric is calculated as: Total Transaction Time / Number of Pages in the
Transaction. For example, if the transaction connects to four different Web pages, this
Web Application 17-1

HTTP Content
metric will calculate the average response time for the four pages each time the
transaction is run.
User Action
If a particular transaction continuously exceeds the Average Page Response threshold,
use the Beacon Data page to test the transaction from other beacons and over a specific
time period. Use this data to pinpoint any trends or specific beacons that generate the
alerts. Display the Beacon Data page by clicking the value of a metric on the
Transaction Performance Page. For more information, see "Monitoring Transaction
Performance" in the Enterprise Manager online help.
Computed Response Time

This metric represents the estimated response time for a client such as a browser, to
fetch all the pages in a transaction. The computed response time is calculated as if the
contents of every page (such as images and HTML style sheets) were fetched in
parallel using multiple threads.
User Action
Use the Calculated Response Time to predict the response time that will be
experienced by your average end user.
Connect Time
Enterprise Manager breaks down each transaction into individual phases.
Performance metrics for each phase of the transaction can help you pinpoint the cause
of a slow response time alert. Connect Time is the first phase of a transaction and
represents the time it takes for a connection to the Web server to be established for all
requests.
User Action
Slow connect time has nothing to do with the content of the page itself. It is likely
caused by a slow network or a busy Web server, which prevents the request from
getting to the Web server in a timely manner.
Content Time
Enterprise Manager breaks down each transaction into indivual phases. Performance
metrics for each phase of the transaction can help you pinpoint the cause of a slow
response time alert. This metric measures the Content Time, which is the amount of
time taken to transfer page content to the browser. Page content includes images and
style sheets, as opposed to the HTML coding for the page.
User Action
Consider reducing the size of images or other contents of the page.
DNS Time
This metric is not supported for this version of Enterprise Manager.
User Action
None.

HTTP Content
First Byte Time

of a slow response time alert. This metric measures the First Byte Time, which is the
total time taken between the last byte of the request sent and the first byte of the
response received by the client for all requests made. This includes the network
latency and the time for the server to respond.
User Action
As with the Connect Time and Redirect Time, this metric can help you pinpoint
whether or not the page content or Web application software is causing the slow
response time, as opposed to the actual time it takes to transfer one byte of information
to the browser.
HTML Bytes
This metric provides information about the amount of data transferred during the
selected transaction. For each transaction, this metric provides the total number of
HTML coding transferred from all the Web pages accessed by the transaction.
User Action
This metric can help you isolate the cause of any performance problems identified by
this transaction. Be sure to consider the number of HTML bytes when you compare the
response time of your Web Application transactions.
HTML Time
response time alert. This metric measures the HTML Time, which is the amount of
time it takes to transfer the HTML coding of the page to the browser. This metric does
not include the time spent transfering images or other page content, for example.
User Action
Slow HTML time could indicate problems with your HTML coding. Check the source
code for your Web Application page to see if there are ways to streamline or improve
the logic of the HTML code.
Page Content Bytes

selected transaction. For each transaction, this metric provides the number of bytes
that represent page content such as images and style sheets.
User Action
this transaction. Be sure to consider the total number of bytes when you compare the
response time of your Web Application transactions. Pages with many images or
complex style sheets will return a high value for the Page Content Bytes metric.

HTTP Content
Page Content Count

This metric is not currently collected by Oracle Enterprise Manager and is for internal
use only.
User Action
None.
Redirect Count
use only.
User Action
None.
Redirect Time
of a slow response time alert. Some pages automatically redirect the HTTP request to
another page. Redirect time represents the total time of all redirects within a
transaction. The time taken to redirect the request can affect the overall response time
of the page.
User Action
Significant time taken to redirect the HTTP request removes the possibility that the
page content or the Web application software is causing a slow response time alert. If
the redirect is causing the performance problems, consider alternative solutions to
sending the user to another HTML page.
Request Count
use only.
User Action
None.
Slowest Page Response

A single transaction often accesses multiple Web pages. This metric indicates the
maximum response time measured for a particular page within a transaction. The
slowest page response time can be monitored for a specific transaction and from a
specific beacon over a period of time.
You can set a threshold for this metric so that Enterprise Manager will generate an
alert if the slowest page response for a particular transaction exceeds a value you
specify when it is run from a specific beacon. For more information, see "Setting
Transaction Intervals and Thresholds" in the Enterprise Manager online help.
User Action
None.

HTTP Content
Status
This metric returns a value of 1 if the selected beacon was successfully able to run the
availability transaction for this Web Application target.
User Action
There are several possible causes to a failed transaction. First, check the availability of
the Web Application and host for the Web Application target. For more information,
see "About Web Application Availability" in the Enterprise Manager online help.
Second, check the availability of the Oracle Agent for this beacon.
Status Description
If the beacon is unable to run the availability transaction successfully, this metric
returns a description of the error that prevented the transaction from running.
User Action
If you are reviewing the metric results from the All Metrics page, review the Value
column of the Status Description table. The error description should offer clues about
why the transaction failed. For more information, see "Displaying the Web Application
All Metrics Page" in the Enterprise Manager online help.
Total Bytes
selected transaction. For each transaction, this metric provides the total number of
bytes transferred from all the Web pages accessed by the transaction.
User Action
this transaction. Be sure to consider the total number of bytes when you compare the
response time of your Web Application transactions.
Total Transaction Time

Total transaction time indicates the overall time spent to process the transaction. This
includes all the phases of the transaction, including Connect Time, Redirect Time, First
Byte Time, HTML Time, and Content Time. This metric calculates total transaction
time by assuming all contents of a page are fetched in a serial manner.
User Action
Use the total response time metric to identify problem pages. After you identify a page
or transaction that's slow to respond to user requests, you can drill down and analyze
each phase of the transaction to isolate and repair the problem.
Transfer Rate
The transfer rate indicates how quickly data is being transferred from the Web server
to the client browser. This is computed as: Total Kilobytes Received / Total Transaction
Time.
User Action
Slow transfer rate can be caused by network congestion or other connectivity issues.

HTTP Response
HTTP Response
This metric is a container for a set of metrics you can use to measure the performance
of your Web Application transactions. It indicates how quickly the pages respond to
user requests.
Average Connect Time

This metric measures the average connect time for all pages in the transaction. This is
calculated as: Total Connect Time / Number of Connections Made. The Connect Time
is one of the phases of a transaction that can help you isolate and fix response time
problems.
User Action
The average connect time, when reviewed over a period of time, can indicate whether
network congestion or other connectivity issues are the cause of poor Web application
response time.
Average First Byte Time

This metric measures the average First Byte Time for all pages in the transaction. This
metric is computed as: Total First Byte Time / Number of Requests Made (either to
fetch HTML or content). The First Byte time is one of the phases of a transaction that
can help you isolate and fix response time problems.
User Action
The Average First Byte Time, when reviewed over a period of time, can indicate
whether network congestion or other connectivity issues are the cause of poor Web
application response time.
Average Page Response

A single transaction often accesses multiple Web pages. The Average Page Response
metric calculates the average response time of the pages within a single transaction.
This metric is calculated as: Total Transaction Time / Number of Pages in the
Transaction. For example, if the transaction connects to four different Web pages, this
metric will calculate the average response time for the four pages each time the
transaction is run.
User Action
If a particular transaction continuously exceeds the Average Page Response threshold,
use the Beacon Data page to test the transaction from other beacons and over a specific
time period. Use this data to pinpoint any trends or specific beacons that generate the
alerts. Display the Beacon Data page by clicking the value of a metric on the
Transaction Performance Page. For more information, see "Monitoring Transaction
Performance" in the Enterprise Manager online help.
Computed Response Time

This metric represents the estimated response time for a client such as a browser, to
fetch all the pages in a transaction. The computed response time is calculated as if the
contents of every page (such as images and HTML style sheets) were fetched in
parallel using multiple threads.

HTTP Response
User Action
Use the Calculated Response Time to predict the response time that will be
experienced by your average end user.
Connect Time
response time alert. Connect Time is the first phase of a transaction and represents the
time it takes for a connection to the Web server to be established.
User Action
Slow connect time has nothing to do with the content of the page itself. It is likely
caused by a slow network or a busy Web server, which prevents the request from
getting to the Web server in a timely manner.
Content Time
response time alert. This metric measures the Content Time, which is the amount of
time taken to transfer page content to the browser. Page content includes images and
style sheets, as opposed to the HTML coding for the page.
User Action
Consider reducing the size of images or other contents of the page.
DNS Time
This metric is not supported for this version of Oracle Enterprise Manager.
User Action
None.
First Byte Time

of a slow response time alert. This metric measures the First Byte Time, which is the
total time taken between the last byte of the request sent and the first byte of the
response received by the server for all requests made. This includes the network
latency and the time for the server to respond.
User Action
As with the Connect Time and Redirect Time, this metric can help you pinpoint
whether or not the page content or Web application software is causing the slow
response time, as opposed to the actual time it takes to transfer one byte of information
to the browser.
HTML Time

HTTP Response
response time alert. This metric measures the HTML Time, which is the amount of
time it takes to transfer the HTML coding of the page to the browser. This metric does
not include the time spent transfering images or other page content, for example.
User Action
Slow HTML time could indicate problems with your HTML coding. Check the source
code for your Web Application page to see if there are ways to streamline or improve
the logic of the HTML code.
Redirect Time
of a slow response time alert. Some pages automatically redirect the HTTP request to
another page. Redirect time represents the total time of all redirects within a
transaction. The time taken to redirect the request can affect the overall response time
of the page.
User Action
Significant time taken to redirect the HTTP request removes the possibility that the
page content or the Web application software is causing a slow response time alert. If
the redirect is causing the performance problems, consider alternative solutions to
sending the user to another HTML page.
Slowest Page Response

A single transaction often accesses multiple Web pages. This metric indicates the
maximum response time measured for a particular page within a transaction. The
slowest page response time can be monitored for a specific transaction and from a
specific beacon over a period of time.
You can set a threshold for this metric so that Enterprise Manager will generate an
alert if the slowest page response for a particular transaction exceeds a value you
specify when it is run from a specific beacon. For more information, see "Setting
Transaction Intervals and Thresholds" in the Enterprise Manager online help.
User Action
This metric (and its accompanying chart when you display the Metric Detail page) can
help you identify what time of day the response time peaked for this particular
transaction and this particular beacon. Understanding the load at particular times of
the day can help you identify unexpected trends and plan for additional hardware or
software resources.
Status
This metric returns a value of 1 if the selected beacon was successfully able to reach the
destination host or run the transaction for a Web Application target.
User Action
There are several possible causes to a failed transaction. First, check the availability of
the Web Application and host for the Web Application target. For more information,
see "About Web Application Availability" in the Enterprise Manager online help.
Second, check the availability of the Management Agent for this Beacon.

HTTP Response
Status Description
If the beacon is unable to run the availability transaction successfully, this metric
returns a description of the error that prevented the transaction from running.
User Action
If you are reviewing the metric results from the All Metrics page, review the Value
column of the Status Description table. The error description should offer clues about
why the transaction failed. For more information, see "Displaying the Web Application
All Metrics Page" in the Enterprise Manager online help.
Total Transaction Time

Total transaction time indicates the overall time spent to process the transaction. This
includes all the phases of the transaction, including Connect Time, Redirect Time, First
Byte Time, HTML Time, and Content Time. This metric calculates total transaction
time by assuming all contents of a page are fetched in a serial manner.
User Action
Use the total transaction time metric to identify problem pages. After you identify a
page or transaction that's slow to respond to user requests, you can drill down and
analyze each phase of the transaction to isolate and repair the problem.
Transfer Rate
The transfer rate indicates how quickly data is being transferred from the Web server
to the client browser. This is computed as: Total Kilobytes Received / Total Transaction
Time.
User Action
Slow transfer rate can be caused by network congestion or other connectivity issues.

HTTP Response

18
Wireless
Oracle Enterprise Manager can be used to manage OracleAS Wireless Server. You can
also use Enterprise Manager to view Oracle Wireless Server metrics that have been
collected by the Oracle Management Agent.
Active User Count Across all Instances

This metric category includes metrics that denote the current number of active
OracleAS Wireless users.
Active Users
This metric denotes the current number of active OracleAS Wireless users.
Metric Summary
Collection
Data Source
Data is populated when a user establishes an OracleAS Wireless session.
User Action
Active User Sessions Across Instances

This metric category includes metrics that denote the number of active OracleAS
Wireless sessions.
Active Sessions
This metric denotes the number of active OracleAS Wireless sessions.
Metric Summary
Wireless 18-1
Average Response Time for the Interval
Collection
Data Source
This metric is populated when a user establishes a wireless session.
User Action
Average Response Time for the Interval

This metric category includes metrics that denote the average response time during
the last five minutes.
Average Response Time (seconds)

This metric denotes the average response time during the last five minutes.
Metric Summary

Consecutive
All Every 5 After Every > 200 500 4 Wireless device
Versions Minutes Sample request response
time is %value% of
baseline.
Data Source
The metric is populated when a user invokes services and gets a response.
User Action
If the alert threshold is reached, it indicates an overload state for OracleAS Wireless
Server. You should tune OracleAS Wireless Server middle tier to relieve the overload.
Response
This metric category includes metrics that denote the (Up or Down) status of OracleAS
Wireless Server.
Status
This metric denotes the (Up or Down) status of the OracleAS Wireless Server.

Status Codes of all components
Metric Summary

Consecutive
All Every 5 After Every = Not Defined 0 1 Wireless status is
Versions Minutes Sample down
Data Source
The metric is populated by the OracleAS Wireless System Management framework
which controls the Start and Stop of OracleAS Wireless processes using opmn controls.
User Action
Services Requested
This metric category includes metrics that denote the number of services invoked
during the last five minutes.
Services Invoked
This metric denotes the number of services invoked during the last five minutes.
Metric Summary
Collection
Data Source
The metric is populated when a user invokes services.
User Action

This metric category includes metrics that denote the (Up or Down) status of OracleAS
Wireless Server.
Wireless 18-3
Status Code
This metric denotes the Up or Down status (1 is Up; 0 is Down). The aggregated values
are plotted to indicate the percentage of time OracleAS Wireless is Up. It also indicates
the Up and Down intervals.
Data Source
The metric is populated by the OracleAS Wireless System Management framework
which controls the Start and Stop of OracleAS Wireless processes using opmn controls.
User Action

Part IV
Oracle Collaboration Suite Metrics
Part IV contains the metrics associated with the Oracle Collaboration Suite.
Part IV contains the following chapters:
■ Chapter 19, "Calendar Applications"
■ Chapter 20, "Calendar Server"
■ Chapter 21, "IMAP Server"
■ Chapter 22, "IMAP Service"
■ Chapter 23, "Mailstore"
■ Chapter 24, "OID Client"
■ Chapter 25, "OVF AQMWI Application"
■ Chapter 26, "OVF FaxIn Application"
■ Chapter 27, "OVF Mailstore"
■ Chapter 28, "OVF Telephony Midtier"
■ Chapter 29, "OVF MWI Service"
■ Chapter 30, "OVF Recording Application"
■ Chapter 31, "OVF Recovery Application"
■ Chapter 32, "OVF Retrieval Application"
■ Chapter 33, "OVF Routing Application"
■ Chapter 34, "OVF Transfer Application"
■ Chapter 35, "POP Server"
■ Chapter 36, "POP Service"
■ Chapter 37, "SMTP IN Server"
■ Chapter 38, "SMTP IN Service"
■ Chapter 39, "SMTP OUT Server"
■ Chapter 40, "SMTP OUT Service"
■ Chapter 41, "Web Conferencing"
■ Chapter 9, "Internet File System" (also part of Oracle Application Server)
■ Chapter 18, "Wireless" (also part of Oracle Application Server)
19
Calendar Applications
Lists the metrics for Oracle Calendar applications.
Calendar Applications DB Size

Monitors the availability of the diskspace where the OCAS/sessiondb and
OCAS/linkdb exist. The threshold is set if availability is less than 10% and 5%
respectively.
% Disk Space Available

respectively.
Metric Summary

Consecutive
All Every 5 After Every < 10 5 1 Not Defined
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "DB
Directory" object.
If warning or critical threshold values are currently set for any "DB Directory" object,
To specify or change warning or critical threshold values for each "DB Directory"
Calendar Applications 19-1

Calendar Applications DB Size
User Action
Filesystem
respectively.
Metric Summary

User Action
Mounted on
respectively.
Metric Summary

User Action
Total Disk Space (Kb)

respectively.
Metric Summary

User Action

Calendar Applications Processes Info
Total Size (Kb)

respectively.
Metric Summary

User Action
Total Space Free (Kb)

respectively.
Metric Summary

User Action
Total Space Used (Kb)

respectively.
Metric Summary

User Action

This metric will list the calendar apps processes:
1. CPU time

2. Memeory usage: Threshold is set for this metric.

3. Elapsed time since start of process.
CPU Time
Lists the Calendar application process information for the CPU time.
Metric Summary

User Action
Elapsed Time
Lists the Calendar application process information for the elapsed time since start of
process.
Metric Summary

User Action
Memory Size (Kb)

Lists the Calendar application process information for the memory usage.
Metric Summary

Consecutive
All Every 5 After Every > Not Defined 50000 1 Not Defined

Response
Multiple Thresholds
"Calendar Process" object.
If warning or critical threshold values are currently set for any "Calendar Process"
To specify or change warning or critical threshold values for each "Calendar Process"
User Action
PID
Lists the Calendar application process information for the PID.
Metric Summary

User Action
Response
Lists the Calendar application process information for the response time in ms.
Response Time
Lists the Calendar application process information for the response time in ms.
Metric Summary

User Action
Status Code
Lists the Calendar application process information for the status.
Threshold is set for this metric if it is not 0.
1. 0= Okay
2. 1= Timed out

Response
3. 2= Most probably the service is down
Metric Summary

Consecutive
All Every 5 After Every = 1 2 1 Not Defined
User Action

20
Calendar Server
This metric will monitor the top 10 calendar processes sorted in descending order on
CPU consumption followed by memory consumption.
Calendar DB Size
This metric will monitor the disk space on which the calendar db resides. A threshold
is set for the availability of this disk space. If the calendar db is mounted on a shared
disk then this metric will not reflect calendar db usage alone but it will reflect the
shared usage of the calendar and all other applications mounted on this disk.
% Disk Space Available

Metric Summary

Consecutive
All Every 5 After Every < 10 5 1 Not Defined
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "DB
Directory" object.
If warning or critical threshold values are currently set for any "DB Directory" object,
To specify or change warning or critical threshold values for each "DB Directory"
Calendar Server 20-1

Calendar DB Size
User Action
Filesystem
Metric Summary

User Action
Mounted on
Metric Summary

User Action
Total Disk Space (MB)

Metric Summary


Calendar DB Size
User Action
Total Size (MB)

Metric Summary

User Action
Total Space Free (MB)

Metric Summary

User Action
Total Space Used (MB)

Metric Summary


Calendar Server Top Processes
User Action
Calendar Server Top Processes

This metric will monitor the top 10 calendar processes sort in descending order on
CPU Time
Metric Summary

User Action
Elapsed Time
Metric Summary

User Action
Memory Size (MB)

Metric Summary

User Action

Connections
PID
Metric Summary

User Action
Connections
Displays the number of calendar connections.
Number of Dedicated Connections

Total number of dedicated connections: Connections made by desktop clients such as
CorporateTime, Oracle Outlook Connector or any calendar SDK based application.
Metric Summary

User Action
Number of Reserved Connections

Total number of reserved connections: connections made by the server internally.
Mainly made by the SNC engine and the CWS. If the calendar server has multiple
nodes then the reserved number of calendar connections should proportional to the
number of node network connections. Threshold is set for this metric if the value is too
low.
Metric Summary

Current Requests in CWS Queue

Consecutive
All Every 5 After Every < Not Defined 2 1 Not Defined
User Action
Number of Shared Connections

Total number of shared connections: Connections made by web based applications.
Metric Summary

User Action
Total Number of Calendar Connections

Total number of shared connections: Connections made by web based applications.
Metric Summary

User Action

Current wireless notification/reminder requests in the queue. Threshold is set for this
metric if it is too high.
Alert Requests
Current wireless notification/reminder requests in the queue. Threshold is set for this

Metric Summary

Consecutive
User Action
Mail Requests
Current mail notification/reminder requests in the queue. Threshold is set for this
Metric Summary

Consecutive
User Action
Replication Requests
Current node-to-node event replications requests in the queue. Threshold is set for this
Metric Summary

CWS Cumulative Queue Stats

Consecutive
User Action
Web Conf. Requests

Current requests for imeeting items in the queue. Threshold is set for this metric if it is
too high.
Metric Summary

Consecutive
User Action

Displays the number of requests in the CWS queue.
Mail Requests Errors

Displays the number of mail requests errors.
Metric Summary


Consecutive
User Action
Mail Requests Processed

Mail notification requests already processed over the past X minutes since the agent
contacted the calendar server.
Metric Summary

User Action
Replication Requests Errors

Displays the number of node-to-node Replication request errors.
Metric Summary

Consecutive
User Action
Replication Requests Processed

Displays the number of node-to-node Replication requests processed.

Metric Summary

User Action
SSR Requests Errors

Displays the number of server side requests errors.
Metric Summary

Consecutive
User Action
SSR Requests Processed

Server Side Reminder requests processed.
Metric Summary

User Action
Wireless Requests Errors

Wireless requests errors processed.
Metric Summary

Response


Consecutive
User Action
Wireless Requests Processed

Wireless notification requests processed.
Metric Summary

User Action
Response
Total transaction time for sending 64Kb of data to the calendar server and receiving a
reply back (tests all nodes). This transaction time includes connecting and
authenticating to the server.
Status
Displays the status of the calendar server. Returns:
Severity status code | Status
where:
■ Severity is: 0-Normal, 1-Warning, 2-Error.
Threshold is set for this metric if it 1 or 2.
■ Status is Up, Down, Partially Up, Inconsistent, and Stand By
■ Up has a Severity 0
■ Partially Up, Stand By have a Severity 1
Partially Up: means that the main daemons (eng, lck) are up but one of the other
daemons maybe down (cws, snc, das)
Stand By: means that the server is shut down but the calendar server manager
CSM is up.

Response Time (64Kb)
■ Down, Inconsistent have Severity 2

Inconsistent: means that either the lck daemon or the main engine is down.
Metric Summary

User Action
Status Code
Displays the status of the calendar server.
Metric Summary

Consecutive
All Every 5 After Every = 1 2 1 Not Defined
User Action

Time Excluding Authentication OH (ms)

Total transaction time excluding authentication time: total transaction time after
subtracting user authentication time.
Metric Summary


User Action
Time Excluding Connection OH (ms)

Total transaction time excluding connection time: total transaction time after
subtracting connection time.
Metric Summary

User Action
Total Transaction Time (ms)

Metric Summary

Consecutive
All Every 5 After Every > 10000 20000 1 Not Defined
User Action


21
IMAP Server
These are the metrics monitored by the IMAP Server target.
Append Details
This metric category contains the metrics associated with the Append command.
Append Average Time

This metric represents the average time in milliseconds for the Append command.
Metric Summary

User Action
Append Count
This metric represents the number of Append commands issued.
Metric Summary

User Action
Append Failure Count

This metric represents the number of failed Append commands.
IMAP Server 21-1

Authenticate Details
Metric Summary

Consecutive
All Every 10 After Every > 300 500 1 The number of failed
Versions Minutes Sample appends are
%value%
User Action
Authenticate Details
This metric category contains the metrics associated with the Authenticate commands.
Authenticate Average Time

This metric represents the average time in milliseconds for the Authenticate command.
Metric Summary

User Action
Authenticate Count
This metric represents the number of Authenticate commands issued.
Metric Summary

User Action

Bytes Transferred
Authenticate Failure Count

This metric represents the number of failed Authenticate commands.
Metric Summary

Consecutive
Versions Minutes Sample authentications are
%value%
User Action
Bytes Transferred
This metric category contains the metrics associated with the transfer of bytes.
Bytes Received By Server

This metric represents the total number of bytes received by the IMAP Server.
Metric Summary

Consecutive
All Every 10 After Every > 10000000 12500000 1 The bytes received
Versions Minutes Sample by the server are
%value%
User Action
Bytes Sent By Server

This metric represents the total number of bytes sent by the IMAP Server.
IMAP Server 21-3

Client Connections
Metric Summary

Consecutive
All Every 10 After Every > 10000000 12500000 1 The bytes sent by the
Versions Minutes Sample server are %value%
User Action
Client Connections
This metric category contains the metrics for the client connections.
Lost Client Connections

This metric represents the total number of lost client connections.
Metric Summary

Consecutive
All Every 10 After Every > 4000 6000 1 The lost connections
Versions Minutes Sample are %value%
User Action
Timed Out Client Connections

This metric represents the total number of timed out client connections.
Metric Summary

Copy Details

Consecutive
All Every 10 After Every > 2000 4000 1 The timed-out
Versions Minutes Sample connections are
%value%
User Action
Total Client Connections

This metric represents the total number of client connections.
Metric Summary

Consecutive
All Every 10 After Every > 4000 6000 1 The total client
Versions Minutes Sample connections are
%value%
User Action
Copy Details
This metric category contains the metrics associated with the Copy commands.
Copy Average Time

This metric represents the average time in milliseconds for the Copy command.
Metric Summary

User Action
IMAP Server 21-5

Examine Details
Copy Count
This metric represents the number of Copy commands issued.
Metric Summary

User Action
Copy Failure Count

This metric represents the number of failed Copy commands.
Metric Summary

Consecutive
Versions Minutes Sample copy operations are
%value%
User Action
Examine Details
This metric category contains the metrics associated with the Examine commands.
Examine Average Time

This metric represents the average time in milliseconds for the Examine command.
Metric Summary


Expunge Details
User Action
Examine Count
This metric represents the number of Examine commands issued.
Metric Summary

User Action
Examine Failure Count

This metric represents the number of failed Examine commands.
Metric Summary

Consecutive
Versions Minutes Sample examines are
%value%
User Action
Expunge Details
This metric category contains the metrics associated with the Expunge commands.
Expunge Average Time

This metric represents the average time in milliseconds for the Expunge command.
Metric Summary
IMAP Server 21-7

Fetch Details

User Action
Expunge Count
This metric represents the number of Expunge commands issued.
Metric Summary

User Action
Expunge Failure Count

This metric represents the number of failed Expunge commands.
Metric Summary

Consecutive
Versions Minutes Sample expunges are
%value%
User Action
Fetch Details
This metric category contains the metrics associated with the Fetch commands.
Fetch Average Time

This metric represents the average time in milliseconds for the Fetch command.

Login Details
Metric Summary

User Action
Fetch Count
This metric represents the number of Fetch commands issued.
Metric Summary

User Action
Fetch Failure Count

This metric represents the number of failed Fetch commands.
Metric Summary

Consecutive
Versions Minutes Sample fetches are %value%
User Action
Login Details
This metric category contains the metrics associated with the Login command.
Login Average Time

This metric represents the average time in milliseconds for the Login command.
IMAP Server 21-9

Login Details
Metric Summary

User Action
Login Count
This metric represents the number of Login commands issued.
Metric Summary

User Action
Login Failure Count

This metric represents the number of failed Login commands.
Metric Summary

Consecutive
Versions Minutes Sample logins are %value%
User Action
Login Success Count

This metric represents the number of succeeded Login commands.
Metric Summary

Logout Details

User Action
Logout Details
This metric category contains the metrics associated with the Logout command.
Logout Average Time

This metric represents the average time in milliseconds for the Logout command.
Metric Summary

User Action
Logout Count
This metric represents the number of Logout commands issued.
Metric Summary

User Action
Logout Failure Count

This metric represents the number of failed Logout commands.
Metric Summary
IMAP Server 21-11

NOOP Details

Consecutive
Versions Minutes Sample logouts are %value%
User Action
NOOP Details
This metric category contains the metrics associated with the NOOP commands.
NOOP Average Time

This metric represents the average time in milliseconds for the NOOP command.
Metric Summary

User Action
NOOP Count
This metric represents the number of NOOP commands issued.
Metric Summary

User Action
NOOP Failure Count

This metric represents the number of failed NOOP commands.
Metric Summary

Pass Details


Consecutive
Versions Minutes Sample noops are %value%
User Action
Pass Details
This metric category contains the metrics associated with the Pass commands.
Pass Average Time

This metric represents the average time in milliseconds for the Pass commands.
Metric Summary

User Action
Pass Count
This metric represents the number of Pass commands issued.
Metric Summary

User Action
Pass Failure Count

This metric represents the number of failed Pass commands.
IMAP Server 21-13

Quit Details
Metric Summary

Consecutive
Versions Minutes Sample pass are %value%
User Action
Quit Details
This metric category contains the metrics associated with the Quit commands.
Quit Average Time

This metric represents the average time in milliseconds for the Quit command.
Metric Summary

User Action
Quit Count
This metric represents the number of Quit commands issued.
Metric Summary

User Action
Quit Failure Count

This metric represents the number of failed Quit commands.

Reset Details
Metric Summary

Consecutive
User Action
Reset Details
This metric category contains the metrics associated with the Reset command.
Reset Average Time

This metric represents the average time in milliseconds for the Reset command.
Metric Summary

User Action
Reset Count
This metric represents the number of Reset commands issued.
Metric Summary

User Action
Reset Failure Count

This metric represents the number of failed Reset commands.
IMAP Server 21-15

Response
Metric Summary

Consecutive
Versions Minutes Sample resets are %value%
User Action
Response
This metric category provides the status of the IMAP Server, that is, whether it is up or
down.
Status
Displays the present condition of IMAP Server.
■ Up (value of 1): IMAP Server is running
■ Down (value of 0): IMAP Server is not running
Metric Summary

Consecutive
Versions Minutes Sample IMAP server
User Action
Retries Details
This metric category contains the metrics associated with the Retries commands.

Stat Details
Retries Average Time

This metric represents the average time in milliseconds for the Retries command.
Metric Summary

User Action
Retries Count
This metric represents the number of Retries commands issued.
Metric Summary

User Action
Retries Failure Count

This metric represents the number of failed Retries commands.
Metric Summary

Consecutive
Versions Minutes Sample retries are %value%
User Action
Stat Details
The metric category contains the metrics associated with the Stat commands.
IMAP Server 21-17

Status Details
Stat Average Time

This metric represents the average time in milliseconds for the Stat command.
Metric Summary

User Action
Stat Count
This metric represents the number of Stat commands issued.
Metric Summary

User Action
Stat Failure Count

This metric represents the number of failed Stat commands.
Metric Summary

Consecutive
Versions Minutes Sample stats are %value%
User Action
Status Details
This metric category contains the metrics associated with the Status commands.

Store Details
Status Average Time

This metric represents the average time in milliseconds for the Status command.
Metric Summary

User Action
Status Count
This metric represents the number of Status commands issued.
Metric Summary

User Action
Status Failure Count

This metric represents the number of failed Status commands.
Metric Summary

Consecutive
User Action
Store Details
This metric category contains the metrics associated with the Store commands.
IMAP Server 21-19

Store Details
Store Average Time

This metric represents the average time in milliseconds for the Store command.
Metric Summary

User Action
Store Count
This metric represents the number of Store commands issued.
Metric Summary

User Action
Store Failure Count

This metric represents the number of failed Store commands.
Metric Summary

Consecutive
User Action

22
IMAP Service
These are the metrics monitored by the IMAP Service target.
Response
This metric category provides the response metrics for the IMAP Service.
Connect Time (ms)

This metric represents the time it took (in milliseconds) to open an SMTP connection.
Metric Summary

Consecutive
All Every 5 After Every > 100 2000 2 Time to connect to
Versions Minutes Sample mail service is
%value% (ms).
User Action
Login Time (ms)

This metric represents the time it took (in milliseconds) to log in to an IMAP Server.
Metric Summary
IMAP Service 22-1

Response

Consecutive
All Every 5 After Every > 2000 5000 2 Login Time is
Versions Minutes Sample %value% (ms).
User Action
Status
Displays the present condition of IMAP Service.
■ Up (value of 1): IMAP Service is running
■ Down (value of 0): IMAP Service is not running
Metric Summary

Consecutive
Versions Minutes Sample IMAP service
User Action
Time to List Folders (ms)

This metric represents the time it took (in milliseconds) to list the e-mail folders.
Metric Summary

Consecutive
All Every 5 After Every > 2000 5000 2 Time to list folders is

Response
User Action
Time to Read Email (ms)

This metric represents the time it took (in milliseconds) to read an e-mail.
Metric Summary

Consecutive
All Every 5 After Every > 2000 5000 2 Time to read an
Versions Minutes Sample email time is
%value% (ms).
User Action
Total Time (ms)

This metric represents the total time (in milliseconds) used to log in to IMAP Server,
connect to the IMAP Server, list the e-mail folders, and read an e-mail.
Metric Summary

Consecutive
All Every 5 After Every > 5000 10000 2 Total Time to read an
Versions Minutes Sample email is %value%
(ms).
User Action
IMAP Service 22-3

Response

23
Mailstore
These are the metrics monitored by the Mailstore target.
Message Queue
This metric category contains the metrics for the message queue.
Length Of All Queues

This metric represents the total number of messages in all the queues.
Metric Summary

Consecutive
All Every 10 After Every > 750 1000 1 The number of new
Versions Minutes Sample messages in the
queue are %value%
User Action
Length of Collect Queue

This metric represents the total number of messages in the Collect queue.
Metric Summary
Collection
Mailstore 23-1
Message Queue
User Action
Length of List Queue

This metric represents the total number of messages in the List queue.
Metric Summary

Consecutive
All Every 10 After Every > 750 1000 1 The length of list
Versions Minutes Sample queue is %value%
User Action
Length of Local Queue

This metric represents the total number of messages in the Local queue.
Metric Summary

Consecutive
All Every 10 After Every > 750 1000 1 The length of local
User Action
Length of Prune Queue

This metric represents the total number of messages in the Prune queue.
Metric Summary

Message Queue
Collection
User Action
Length of Relay Queue

This metric represents the total number of messages in the Relay queue.
Metric Summary

Consecutive
All Every 10 After Every > 750 1000 1 The length of relay
User Action
Length of Submit Queue

This metric represents the total number of messages in the Submit queue.
Metric Summary

Consecutive
All Every 10 After Every > 750 1000 1 The length of submit
User Action
Mailstore 23-3
Response
Messages Being Processed

This metric represents the number of messages being processed.
Metric Summary

Consecutive
All Every 10 After Every > 250 500 1 The number of
Versions Minutes Sample messages in the
queue being
processed are
%value%
User Action
Messages Marked For GC

This metric represents the number of messages being marked for garbage collection.
Metric Summary

Consecutive
All Every 10 After Every > 2000 2500 1 The number of
Versions Minutes Sample messages marked for
garbage collection
are %value%
User Action
Response
This metric category contains the response metrics for Mailstore.
Status
Displays the present condition of the Mailstore.

Response
■ Up (value of 1): Mailstore is running

■ Down (value of 0): Mailstore is not running
Metric Summary

Consecutive
Versions Minutes Sample the database
User Action
Mailstore 23-5
Response

24
OID Client
These are the metrics monitored by the OID (Oracle Internet Directory) client.
Response
This metric category provides the response metrics.
Addressing Search Time (ms)

This metric represents the time it took (in milliseconds) to do an e-mail addressing
search against an LDAP (Lightweight Directory Access Protocol) Server.
Metric Summary

Consecutive
All Every 5 After Every > 2000 4000 2 OID Addressing ing
Versions Minutes Sample search time is
%value% (ms).
User Action
Base Search Time (ms)

This metric represents the time it took (in milliseconds) to do a base search against an
LDAP (Lightweight Directory Access Protocol) Server.
Metric Summary
OID Client 24-1

Response

Consecutive
All Every 5 After Every > 2000 4000 2 OID Base search
Versions Minutes Sample time is %value%
(ms).
User Action
Compare Time (ms)

This metric represents the time it took (in milliseconds) to do a compare operation
against an LDAP (Lightweight Directory Access Protocol) Server. This simulates
logging in LDAP activity.
Metric Summary

Consecutive
All Every 5 After Every > 2000 4000 2 OID Compare op
(ms).
User Action
Messaging Search Time (ms)

This metric represents the time it took (in milliseconds) to do an e-mail message search
against an LDAP (Lightweight Directory Access Protocol) Server.
Metric Summary

Response

Consecutive
All Every 5 After Every > 125 4000 2 OID Messaging
Versions Minutes Sample search time is
%value% (ms).
User Action
Status
Displays the present condition of the OID client.
■ Up (value of 1): OID client is running
■ Down (value of 0): OID client is not running
Metric Summary

Consecutive
Versions Minutes Sample LDAP server
User Action
OID Client 24-3

Response

25
OVF AQMWI Application
Gives status of ovf aqmwi application.
Response
Status
Metric Summary

Consecutive
All Every 3 After Every = Not Defined 0 1 AQMWI Application
Versions Minutes Sample is down
User Action
OVF AQMWI Application 25-1

Response

26
OVF FaxIn Application
Gives status of ovf faxin application.
Response
Gives the status of ovf faxin application.
Status
Gives status of ovf faxin application.
Metric Summary

Consecutive
All Every 3 After Every = Not Defined 0 1 FaxIn Application is
User Action
OVF FaxIn Application 26-1

Response

27
OVF Mailstore
Provides the status of the backend mailstore database.
Activity Time
This is the key column. The key is the type of activity. Examples of activity types are
login time, play message time, user password.
Activity User Count

Number of users who performed that activity in the last five minutes.
Metric Summary

User Action
Average Response Time

Sum of response time divided by number of user.
Metric Summary

Consecutive
All activity_ Every 5 After Every > 2000 2500 1 The vm average
Versions name: Minutes Sample play message time
"PLAY_ is %value%
MSG"
OVF Mailstore 27-1

Database Login Time
Multiple Thresholds
"Voicemail Activity" object.
If warning or critical threshold values are currently set for any "Voicemail Activity"
To specify or change warning or critical threshold values for each "Voicemail Activity"
Manager onling help for information on accessing the Edit Thresholds page.
User Action
Sum of Response Time

Total response time for all the users for a particular activity for the last five minutes.
Metric Summary

User Action
Database Login Time

Divides the amount of time it takes to login to database into intervals. Gives the
number of users whose database login times fits into each interval.
DB Login Time User Count

Number of users for each interval.
Metric Summary

Consecutive
All response_ Every 5 After Every > 1 5 1 The DB login time
Versions duration: Minutes Sample is greater than 2000
">2000" for %value% users

Listen To Message Time
Multiple Thresholds
"Response Duration (msec)" object.
If warning or critical threshold values are currently set for any "Response Duration
(msec)" object, those thresholds can be viewed on the Metric Detail page for this
metric.
To specify or change warning or critical threshold values for each "Response Duration
(msec)" object, use the Edit Thresholds page. See the Editing Thresholds topic in the
Enterprise Manager onling help for information on accessing the Edit Thresholds
page.
User Action
Delivery Time
Provides a measurement of the mail delivery times.
Elapsed Time (msec)

Provides a measurement of the mail delivery times.
Metric Summary

Consecutive
All Every 5 After Every > 300000 600000 1 The voicemail
Versions Minutes Sample delivery time is
%value%
User Action

Divides the amount of time it takes to listen to messages into intervals. Gives the
number of users whose listen times fits into each interval.
Listen Time User Count

Number of users for each interval.
OVF Mailstore 27-3

Response
Metric Summary

Consecutive
All response_ Every 5 After Every > 1 5 1 The play message
Versions duration: Minutes Sample time is greater than
">10000" 10000 for %value%
users
Multiple Thresholds
metric.
page.
User Action
Response
Status
Metric Summary

Consecutive
Versions Minutes Sample the database

User Login Time
User Action
User Login Time

Divides the login time into intervals. Eg, 0-100ms, 100-200ms,200 - 300ms. Gives the
number of users whose login time fits into each interval. Eg, It took 8 users 0-100ms to
login, 3 users 100-200ms, and 1 user 200-300ms. This type of metric is common in OVF
and repeated several times below.
User Count for Login Time

Displays the number of users for each interval.
Metric Summary

Consecutive
All response_ Every 5 After Every > 1 5 1 The response
Versions duration: Minutes Sample duration is > 10000
">10000" for %value% users
Multiple Thresholds
metric.
page.
User Action
OVF Mailstore 27-5

User Login Time

28
OVF Telephony Midtier
You can use Enterprise Manager to view metrics for the Oracle Voicemail and Fax
telephony midtier.
Number of Callers
This category provides metrics about the number of callers.
Current Number of Callers

This metric shows the number of callers at the current time.
Metric Summary

User Action
Total Number of Callers

This metric shows the total number of callers since the startup of the machine.
Metric Summary

User Action
Response
This category contains metrics about the response of the Oracle Voicemail and Fax
telephony midtier machine's telephony subsystem.
OVF Telephony Midtier 28-1

Response
Status
This metric shows the status of the Oracle Voicemail and Fax telephony midtier
machine's telephony subsystem.
Metric Summary

Consecutive
All Every 3 After Every = Not Defined 0 1 Voicemail Server
User Action

29
OVF MWI Service
MWI Service.
Response
MWI Service.
Status
This metric shows the status of the Oracle Voicemail and Fax MWI Service.
Metric Summary

Consecutive
All Every 3 After Every = Not Defined 0 1 MWI Service is
User Action
OVF MWI Service 29-1

Response

30
OVF Recording Application
recording application.
Activity Total Time

This category contains metrics about the number of users performing each activity,
total time spent in each activity, and the average time spent in each activity for the last
five minutes.
Recording Activity Total Response Time

The total time (in milliseconds) spent performing the activity for the last five minutes.
Metric Summary

User Action
Recording Activity User Count

The number of users performing the activity for the last five minutes.
Metric Summary

User Action
OVF Recording Application 30-1

Caller Greeting Wait Time
Recording Avg Response Time

The average time (in milliseconds) it took to perform the activity for the last five
minutes.
Metric Summary

Consecutive
Versions name: Minutes Sample recording
"GREETING" message time is
%value%
Multiple Thresholds
"Voicemail Activity" object.
If warning or critical threshold values are currently set for any "Voicemail Activity"
To specify or change warning or critical threshold values for each "Voicemail Activity"
User Action
Caller Greeting Wait Time

This category contains metrics about the time callers had to wait for a greeting.
Num Users waiting for Greeting

The number of users waiting for a greeting in each five minute interval.
Metric Summary

Response

Consecutive
All response_ Every 5 After Every > 1 5 1 The user greeting
Versions duration: Minutes Sample time is more than
">10000" 10000ms for
%value% users
Multiple Thresholds
"Duration (msec)" object.
If warning or critical threshold values are currently set for any "Duration (msec)"
To specify or change warning or critical threshold values for each "Duration (msec)"
User Action
Response
recording application.
Response Status
This metric shows the status of the Oracle Voicemail and Fax recording application.
Metric Summary

Consecutive
All Every 3 After Every = Not Defined 0 1 Recording
Versions Minutes Sample Application is down
User Action
OVF Recording Application 30-3

Response

31
OVF Recovery Application
recovery application.
Response
recovery application.
Status
This metric shows the status of the Oracle Voicemail and Fax recovery application.
Metric Summary

Consecutive
All Every 3 After Every = Not Defined 0 1 Recovery
User Action
OVF Recovery Application 31-1

Response

32
OVF Retrieval Application
retrieval application.
Activity Total Time

This category contains metrics about the total amount of time it took to perform the
activity, the total number of users performing the activity, and the average time it takes
to perform the activity.
Examples of activities are play message times and user password times.
Retrieval Avg Response Time

The average time it took to perform the activity in the last 5 minute interval.
Metric Summary

Consecutive
Versions name: Minutes Sample User Password
"USER_ time is %value%
PWD"
Multiple Thresholds
"Retrieval Voicemail Activity" object.
If warning or critical threshold values are currently set for any "Retrieval Voicemail
Activity" object, those thresholds can be viewed on the Metric Detail page for this
metric.
To specify or change warning or critical threshold values for each "Retrieval Voicemail
Activity" object, use the Edit Thresholds page. See the Editing Thresholds topic in the
OVF Retrieval Application 32-1

Database Login Time
User Action
Retrieval Number of Users

The number of users performing the activity in the last 5 minute interval.
Metric Summary

User Action
Retrieval Sum of Response Time

The total amount of time it took to perform the activity in the last five minutes.
Metric Summary

User Action
Database Login Time

This category contains metrics about the amount of time it took users to login to the
database.
DB Login Time User Count

The number of users waiting to login to the database in each 5 minute interval.
Metric Summary


Consecutive
All response_ Every 5 After Every > 1 5 1 The DB login time
Versions duration: Minutes Sample is more than
">2000" 2000ms for
%value% users
Multiple Thresholds
metric.
User Action

This category contains metrics about the amount of time users had to wait to listen to a
message.
Listen Time User Count

The number of users waiting to listen to messages in each 5 minute interval.
Metric Summary

Consecutive
All response_ Every 5 After Every > 1 5 1 The play message
Versions duration: Minutes Sample time is more than
">10000" 10000ms for
%value% users
Multiple Thresholds

Response
metric.
User Action
Response
retrieval application.
Status
This metric shows the status of the Oracle Voicemail and Fax retrieval application.
Metric Summary

Consecutive
All Every 3 After Every = Not Defined 0 1 Retrieval
User Action
User Login Time

This category contains metrics about the amount of time users had to wait to login.
Login Time User Count

Number of users waiting to login in each five minute interval.
Metric Summary

User Login Time

Consecutive
All response_ Every 5 After Every > 1 5 1 The retrieval time
Versions duration: Minutes Sample is more than
">10000" 10000ms for
%value% users
Multiple Thresholds
metric.
User Action

User Login Time

33
OVF Routing Application
routing application.
Response
routing application.
Status
This metric shows the status of the Oracle Voicemail and Fax routing application.
Metric Summary

Consecutive
All Every 3 After Every = Not Defined 0 1 Routing Application
User Action
OVF Routing Application 33-1

Response

34
OVF Transfer Application
transfer application.
Response
transfer application.
Status
This metric shows the status of the Oracle Voicemail and Fax transfer application.
Metric Summary

Consecutive
All Every 3 After Every = Not Defined 0 1 Transfer Application
User Action
OVF Transfer Application 34-1

Response

35
POP Server
You can use Enterprise Manager to view metrics for a POP Server.
Response
This category contains metrics about the response of a POP Server.
Status
This metric shows the status of the POP Server.
The value of the metric is 1 if the server is up, and 0 if the server is down.
Metric Summary

Consecutive
Versions Minutes Sample POP server
User Action
POP Server 35-1

Response

36
POP Service
You can use Enterprise Manager to view metrics for a POP service.
Response
This category contains metrics about the response of a POP service.
Connect Time (ms)

Time (in milliseconds) to open a POP connection.
Metric Summary

Consecutive
%value% (ms).
User Action
Login Time (ms)

Time (in milliseconds) for a user to login to the POP service.
Metric Summary
POP Service 36-1

Response

Consecutive
All Every 5 After Every > 2000 5000 2 Login Time is
User Action
Status
This metric shows the status of the POP service.
The value of the metric is 1 if the service is up, and 0 if the service is down.
Metric Summary

Consecutive
Versions Minutes Sample POP service
User Action
Time to Read Email (ms)

Time (in milliseconds) to read a short email.
Metric Summary

Consecutive
All Every 5 After Every > 2000 5000 2 Reading an email
(ms).

Response
User Action
Total Time (ms)

The total time (in milliseconds) to open a POP connection, login, and read a short
email message.
Metric Summary

Consecutive
All Every 5 After Every > 5000 10000 2 Total Time to read an
(ms).
User Action
POP Service 36-3

Response

37
SMTP IN Server
You can use Enterprise Manager to view metrics for an SMTP IN Server.
Bytes Transferred
This category contains metrics about bytes transmitted.
Bytes Transmitted
The total number of bytes transmitted.
Metric Summary

Consecutive
All Every 10 After Every > 10000000 125000000 1 The current number
Versions Minutes Sample of bytes transmitted
are %value%
User Action
Client Connections
This category contains metrics about client connections.
Current Client Connections

The current number of client connections.
Metric Summary
SMTP IN Server 37-1

Client Connections


Consecutive
Versions Minutes Sample of client connections
are %value%
User Action
Current SMTP Connections

The current number of inbound SMTP connections.
Metric Summary

Consecutive
All Every 10 After Every > 1000 1500 1 The current inbound
Versions Minutes Sample SMTP connections
are %value%
User Action
Total Inbound SMTP Connections

The total number of inbound SMTP connections.
Metric Summary

Messages

Consecutive
All Every 10 After Every > 1000 1500 1 The total number of
Versions Minutes Sample inbound SMTP
connections are
%value%
User Action
Messages
This category contains metrics about SMTP messages.
Current number of messages deferred

The current number of messages deferred.
Metric Summary

Consecutive
Versions Minutes Sample of messages deferred
are %value%
User Action
Total number of messages deferred

The total number of messages deferred.
Metric Summary
SMTP IN Server 37-3

Response

Consecutive
Versions Minutes Sample messages deferred
are %value%
User Action
Total number of messages transmitted

The total number of messages transmitted.
Metric Summary

Consecutive
Versions Minutes Sample messages
transmitted are
%value%
User Action
Response
This category contains metrics about the response of an SMTP IN Server.
Status
This metric shows the status of the SMTP IN Server.
Metric Summary

Response

Consecutive
Versions Minutes Sample SMTP server
User Action
SMTP IN Server 37-5

Response

38
SMTP IN Service
You can use Enterprise Manager to view metrics for an SMTP IN Service.
Response
This category contains metrics about the response of an SMTP IN Service.
Connect Time (ms)

Time (in milliseconds) to open an SMTP connection.
Metric Summary

Consecutive
%value% (ms).
User Action
Status
This metric shows the status of the SMTP IN Service.
Metric Summary
SMTP IN Service 38-1

Response

Consecutive
Versions Minutes Sample SMTP service
User Action
Time To Send Email(ms)

Time (in milliseconds) to send a short email.
Metric Summary

Consecutive
All Every 5 After Every > 2000 5000 2 Time to send email is
User Action
Total Time (ms)

Total time (in milliseconds) to open an SMTP connection and send a short email.
Metric Summary

Consecutive
All Every 5 After Every > 2000 5000 2 Total Time to send
(ms).

Response
User Action
SMTP IN Service 38-3

Response

39
SMTP OUT Server
You can use Enterprise Manager to view metrics for an SMTP OUT Server.
Bytes Transferred
This category contains metrics about bytes transferred.
Bytes Sent By Server

The total number of bytes transmitted by the SMTP OUT Server.
Metric Summary

Consecutive
All Every 10 After Every > 10000000 12500000 1 Bytes sent by the
Versions Minutes Sample server are %value%
User Action
Messages
This category contains metrics about SMTP messages.
Messages Queued
The messages queued awaiting to be sent out to the Internet.
Metric Summary
SMTP OUT Server 39-1

Messages


Consecutive
All Every 10 After Every > 1000 1500 1 The total messages
Versions Minutes Sample queued are %value%
User Action
Messages Sent to DL
The number of messages sent to distribution lists.
Metric Summary

Consecutive
All Every 10 After Every > 1000 1500 1 The total messages
Versions Minutes Sample sent are %value%
User Action
Messages Transmitted
The total number of messages transmitted.
Metric Summary

Outbound SMTP Connections

Consecutive
All Every 10 After Every > 1000 1500 1 The total message
Versions Minutes Sample transmitted are
%value%
User Action
Outbound SMTP Connections

This category contains metrics about outbound SMTP connections.
Current Outbound SMTP Connections

The current number of outbound SMTP connections.
Metric Summary

Consecutive
All Every 10 After Every > 2000 2500 1 The current
Versions Minutes Sample outbound SMTP
connections are
%value%
User Action
Total Outbound SMTP Connections

The total number of outbound SMTP connections.
Metric Summary
SMTP OUT Server 39-3

Response

Consecutive
All Every 10 After Every > 2000 2500 1 The total outbound
Versions Minutes Sample SMTP connections
are %value%
User Action
Response
This category contains metrics about the response of an SMTP OUT Server.
Status
This metric shows the status of the SMTP OUT Server.
Metric Summary

Consecutive
All Every 10 After Every = Not Defined 0 1 No SMTP OUT
Versions Minutes Sample server running
User Action

40
SMTP OUT Service
You can use Enterprise Manager to view metrics for an SMTP OUT Service.
Response
This category contains metrics about the response of an SMTP OUT Service.
Status
This metric shows the status of the SMTP OUT Service.
Metric Summary

Consecutive
All Every 5 After Every = Not Defined 0 1 No SMTP OUT
Versions Minutes Sample service running
User Action
SMTP OUT Service 40-1

Response

41
Web Conferencing
You can use Enterprise Manager to view metrics for a Web Conference target.
Process Information
This category contains CPU and memory utilization metrics for all the Web Conference
processes.
CPU Idle (%)

Percentage of CPU time spent doing nothing.
Metric Summary

User Action
CPU Other (%)

The percentage of CPU time used by all the other processes.
Metric Summary

User Action
CPU Usage (%)

Percentage of the CPU used by this process.
Web Conferencing 41-1

Process Information
Metric Summary

Consecutive
All Every 5 After Every > Not Defined Not Defined 1 CPU used over
Versions Minutes 12 Samples %value%
Multiple Thresholds
User Action
Free Physical Memory (MB)

Amount of free memory (in MB).
Metric Summary

User Action
Page Size (Bytes)

The size of the page (in bytes)
Metric Summary


Response
User Action
Physical Memory Percentage

The percentage of physical memory used by this process.
Metric Summary

User Action
Physical Memory Usage (MB)

Memory used by this process (in MB).
Metric Summary

User Action
Total Physical Memory Usage (MB)

Total memory used (in MB).
Metric Summary

User Action
Response
This category contains metrics about the response of an Web Conference application.

Service Usage
Status
Reports the overall status of the Web Conference application. A value of 1 indicates the
application is up. A value of 0 indicates the application is down.
Metric Summary

Consecutive
All Every 15 After Every = Not Defined 0 1 Failed to run imtctl.
User Action
Service Usage
This category contains metrics about the number of meetings occurring and the
number of users participating in those meetings as an aggregate.
Active Clients
Number of users currently using Web Conference.
Metric Summary

Consecutive
All Every 15 After Every > Not Defined Not Defined 1 Active Clients over
User Action
Active Sessions
The number of meetings currently taking place.

Service Usage
Metric Summary

Consecutive
All Every 15 After Every > Not Defined Not Defined 1 Active Sessions over
User Action
Memory Used KB
Memory being used currently (in KB).
Metric Summary

Consecutive
All Every 15 After Every > Not Defined Not Defined 1 Memory used over
User Action
Total Memory KB
Total memory used (in KB).
Metric Summary

User Action

Service Usage
Total Sessions
Total number of meetings since this instance of Web Conference began.
Metric Summary

Consecutive
All Every 15 After Every > Not Defined Not Defined 1 Total Sessions over
User Action

Part V
Metrics Specific to Enterprise Manager
Part V contains the metrics that are specific to Enterprise Manager.

Part V contains the following chapters:
■ Chapter 42, "Agent"
■ Chapter 43, "Beacon"
■ Chapter 44, "OMS and Repository"
42
Agent
The oracle_emd target is a representation of the machine running the Oracle

Management Agent. The Oracle Management Agent is the Management Agent used
by Oracle Enterprise Manager. This target type exposes useful information required to
monitor the performance of the Management Agent.
Most of the help topics in this helpset use the term Management Agent to refer to the
Oracle Management Agent.
Agent Process Statistics

The EMD Process Statistics provides information about the performance and resource
consumption of the Management Agent process. This metric is collected by default on
an interval of 1038 seconds. A value that can be changed in the default collection for
the oracle_emd target.
CPU Usage (%)

The CPU Usage metric provides the CPU consumption as a percentage of CPU time at
any given moment in time. The number is a summation of the CPU consumption of
the Management Agent process and any of its child processes (and their child
processes and so on). Child processes are sometimes created by the Management
Agent in the course of evaluating a metric or running a job.
Metric Summary

Consecutive
All Every 1038 After Every > 10 20 4 Agent CPU
Versions Hours Sample consumption is
%value%%%
Data Source
The source for this metric is the UNIX ps command.
Agent 42-1
User Action
A large CPU consumption will cause the entire system to slow down. The cause could
be the Management Agent process itself or any of its child processes. To analyze what
is causing the problem, use the Solaris "top" system command and look out for any
Perl or Java processes that seem to be consuming excessive CPU (%).
Number Files Open

This metric records the number of files currently opened by the Management Agent
process. The file types that constitute this number are: regular files, links, sockets,
directories and name pipes.
Metric Summary

Consecutive
All Every 1038 After Every > 800 900 2 Number files opened
Versions Hours Sample by Agent is
%value%
Data Source
The source of this information is the UNIX pfiles command.
User Action
Number Threads Created

This metric shows the number of threads currently created by the Management Agent
process.
Metric Summary
Collection
Data Source
The source of this metric is the UNIX ps command.
User Action

Process ID
The process ID is the process ID of the Management Agent.
Metric Summary
Collection
Data Source
The source of this is the Perl getppid function.
User Action
Resident Memory Utilization (%)

The Resident Memory Utilization is the physical memory usage as a percentage of
total memory available.
Metric Summary

Consecutive
All Every 1038 After Every > 20 30 1 Agent resident
Versions Hours Sample memory utilization
is %value%%%
Data Source
The source of this information is the UNIX ps system command.
User Action
Resident Memory Utilization (KB)

This metric represents the amount of physical memory usage by the Management
Agent process and all of its child processes in KB.
Metric Summary
Agent 42-3


Consecutive
All Every 1038 After Every > 128000 256000 1 Agent resident
Versions Hours Sample memory utilization
in KB is %value%
Data Source
The source of this data is the UNIX ps system command.
User Action
The default warning and critical threshold values for this metric are set higher than
what is expected to be necessary in many cases. You will probably want to lower the
warning and critical thresholds to values that work well for the number and types of
targets that are being monitored by the Management Agent.
Virtual Memory Utilization (KB)

The Virtual Memory Utilization (VMU) metric provides a sum of the VMU usage of
the Management Agent and all of its child processes (and their child processes and so
on). Child processes are sometimes created by the Management Agent in the course of
evaluating a metric or running a job.
Metric Summary
Collection
Data Source
The source of this information is the UNIX ps system command.
User Action
Large virtual memory utilization will also slow the system down. Use the Solaris "top"
command to see what processes are consuming this memory. Look out for Perl and
Java processes as well as the obvious emdaemon process (the Management Agent
process itself.)
Virtual Memory Utilization Growth (%)

Virtual memory utilization growth (%) shows the percentage growth of the virtual
memory percentage usage of the Management Agent process. For example: if at time
t1 (t1 < t2) the usage was a% and at time t2 it was b%, the growth % would be
((b-1)/a)%.

Response
Metric Summary

Consecutive
All Every 1038 After Every > .5 2 3 Agent Virtual
Versions Hours Sample Memory Growth is
%value%%%
Data Source
The source of the raw information is the UNIX ps command. From this, we calculate
an average over four interval periods and use this as our comparison percentage (that
is, how much has the virtual memory usage grown as a percentage of this average.
User Action
Response
The Response metric reports on the availability of the Management Agent.
Status
This metric has a value of 1 if the Management Agent is up and running.
Metric Summary

Consecutive
All Every 168 After Every = Not Defined 0 1 Not Defined
Versions Hours Sample
Data Source
Not applicable.
Agent 42-5
Upload Statistics
User Action
If the value of this metric is not 1, the Management Agent is down and contact with
the Management Agent will not exist. In such situations, the Management Agent may
need to be restarted.
Upload Statistics
The Upload Statistics metrics present information on the state of the upload manager
and its performance.
Last Successful Upload

Displays the last time an attempt was made to upload data to the repository and this
attempt was successful.
Metric Summary
Collection
Data Source
The source of this metric is the Management Agent itself.
User Action
If the difference between this time and the current time is big, then there is likely to be
a problem uploading data to the repository. This may be due to a bad network or
problems on the repository end. Check the emd.trc file in the log directory for upload
messages.
Number of Files to Upload

This metric shows the number of XML files that are in the $ORACLE_
HOME/sysman/emd/upload directory waiting to be uploaded to the repository.
Metric Summary
Collection
Data Source
The source of this information is the Management Agent itself.
User Action
A large number of files in this directory probably indicates that there is a problem
uploading files to the repository. Check the emd.trc file for upload errors and act

User Identification
appropriately. The cause may also be a bad network or problems on the repository
end.
Size of Files to Upload (MB)

The Size of Files to Upload metric presents the sum of the sizes of all XML files in the
upload directory of the Management Agent.
Metric Summary
Collection
Data Source
User Action
If this metric is large, check the upload directory. If this directory has very few files, it
may be they are large. If it has many files, there may be a problem uploading data to
the repository. This may be due to a bad network, bad repository or Management
Agent. Check the emd.trc file in the log directory for upload error messages.
Upload Rate (KB/sec)

The upload rate is the average rate in KB/sec at which data is uploaded to the
repository.
Metric Summary
Collection
Data Source
User Action
If the rate is zero or close to zero, there may be problems uploading data or collecting
data (because if collections stop for some reason, we have nothing to upload). Check
the log files for collection and upload messages.
User Identification
These metrics provide information about the user running the Management Agent.
Agent 42-7
User Identification
Group Name
The name of the group the Management Agent is running under.
Metric Summary
Collection
Data Source
The source of this metric is the UNIX id command.
User Action
Location
The Location metric shows the directory home of the Management Agent.
Metric Summary
Collection
Data Source
The source of this information is the ORACLE_HOME environment variable.
User Action
Other Groups
This metric lists the other groups the Management Agent user belongs to.
Metric Summary
Collection
Data Source
The source of this metric is the UNIX "id" command.

User Limit Info
User Action
User Name
The User Name metric provides information on the user that started the Management
Agent process.
Metric Summary
Collection
Data Source
The source of this data is the UNIX id command.
User Action
User Limit Info

The metrics in the User Limit Info category provide information about the system
resources available to the Management Agent.
CoreDump (blocks)
The CoreDump metric shows the maximum size of a core dump file in 512 Kbytes
blocks. A value of unlimited means that the only limit is the file system limit.
Metric Summary
Collection
Data Source
The source of this information is the UNIX ulimit command.
User Action
This metric shows the maximum size (in 512 Kbyte blocks) of a core dump file. To
decrease or increase this limit, use the UNIX ulimit system command.
Data (kbytes)
This metric shows the maximum size of the Management Agent's heap in Kbytes.
Agent 42-9
User Limit Info
Metric Summary
Collection
Data Source
The source for this information is the UNIX ulimit system command.
User Action
This metric shows the maximum heap size (in kbytes) made available to the
Management Agent. To decrease or increase this limit, use the UNIX ulimit system
command.
File (blocks)
The File metric lets you know the size of the largest single file allowed by the system
the Management Agent is running on. The unit is 512 Kbyte blocks. A value of
"unlimited" means that the limit is the file system limit.
Metric Summary
Collection
Data Source
The source for this information is the UNIX ulimit system command.
User Action
This metric shows the maximum file size (in blocks) allowed by the system that the
Management Agent is running on. To decrease or increase this limit, use the UNIX
ulimit system command.
NoFiles (descriptors)
The NoFiles metric shows the maximum number of file descriptors that the process
can have.
Metric Summary
Collection

User Limit Info
Data Source
The source of this information is the UNIX system call ulimit.
User Action
If this limit is small (compared to the operating system maximum), it can be changed
for the Management Agent process.
Stack (kbytes)
This metric displays the maximum size of the Management Agent's stack in Kbytes.
Metric Summary
Collection
Data Source
The source for this information is the UNIX ulimit command.
User Action
This metric shows the maximum size (in kbytes) of the Management Agent's stack. To
decrease or increase this limit, use the UNIX ulimit system command.
Time (seconds)
The time metric represents, in seconds, the maximum CPU seconds made available to
the Management Agent process by the system it is running on. A value of "unlimited"
means that the CPU time available to the Management Agent is unrestricted.
Metric Summary
Collection
Data Source
This information is obtained using the UNIX ulimit system command.
User Action
This metric shows the maximum CPU time (in seconds) made available to the
Management Agent. To decrease or increase this limit, use the UNIX ulimit system
command.
Agent 42-11
User Limit Info
Virtual Mem (kbytes)

The Virtual Mem metric shows the maximum virtual memory size that can be
occupied by the Management Agent process. If this value is "unlimited" then the only
limit is the operating system limit.
Metric Summary
Collection
Data Source
The source of this information is the UNIX ulimit system command.
User Action
If the value of the Virtual Mem metric is too high or too low, you can change the
restriction on virtual memory use by the Management Agent process using the limit
UNIX command.

43
Beacon
You can use Oracle Enterprise Manager to view performance and availability metrics
for your Beacon targets. For more information, see About Beacons in the Enterprise
Manager online help.
ICMP Echo Response

This category of Beacon metrics provide you with data gathered as the result of an
Internet Control Message Protocol (ICMP) ping of the target beging monitored by the
Beacon.
Average Time (ms)

This metric represents the average time required to send an Internet Control Message
Protocol (ICMP) ping to the selected host or network component and receive a valid
response.
This Beacon target metric is shows up in the following locations:
■ On the Network Test page when you click Performance on the Beacon home page
and then use the Test section of the page to test the connection to a host or other
network component
■ In the Network Watch List on the Performance property page of the Beacon home
page
■ On the Beacon Data page when you click a metric in the Network Watch List
When you add a host or other network component to the Network Watch list for a
Beacon, you can set warning and critical threshold values for this metric. For more
information, see Using Beacons to Monitor Network Component Availability in the
Enterprise Manager online help.
Data Source
The UNIX ping command.
User Action
Use this metric to check the network response time for a particular host or other
network component. For example, add a host to the Network Watch list on the
Performance property page of the Beacon home page. At predefined intervals, the
Beacon will ping the host and register the time it takes to receive a response from the
host. If the Average Time (ms) exceeds the threshold you set when creating or editing
the watch list item, an alert will be triggered.
Beacon 43-1
ICMP Echo Response
Last Host
This Beacon metric represents the last node that was reached successfully by an
Internet Control Message Protocol (ICMP) ping of the selected host or network
component while traversing to the final destination.
■ On the Test Response page, which you display when you test a selected item in the
Network Watch List by clicking Test Response on the Beacon Performance page.
■ On the Beacon Data page when you click a metric in the Network Watch List; on
this page the metric is referred to as the Last Successful Host.
Data Source
User Action
If the last host is not your destination node, there may be an indication that problems
may exist between the last host and the destination node.
Number of Hops
This Beacon target metric represents the number of network nodes traversed by the
Internet Control Message Protocol (ICMP) ping of the selected host or network
component.
network component
page
When you add a host or other network component to the Network Watchlist for a
Data Source
User Action
Packets Dropped (%)

This metric represents the percentage of packets that could not reach its destination
during an Internet Control Message Protocol (ICMP) ping of the selected host or other
network component.

HTTP Response
network component
page
When you add a host or other network component to the Network Watchlist for a
Data Source
User Action
A high percentage of dropped packets can indicate a poor network connection. Click
the value of the metric in the Network Watch List to display a chart that shows the
performance of the metric over time. This can help you identify whether the
connection issues are persistent or only intermittent.
Status
This metric indicates whether or not an Internet Control Message Protocol (ICMP)
ping of the selected host or other network component was successful.
network component
page
When you add a host or other network component to the Network Watch list for a
Data Source
User Action
Use this metric to determine the availability of a specific host or other IP component
on your network.
HTTP Response
This category of Beacon metrics provides you with HTTP response data.
Beacon 43-3
HTTP Response
Intermediate Host IP
This metric represents the IP address of all the nodes traversed in order to reach a
destination.
Data Source
The UNIX traceroute command.
User Action
Intermediate Host Name

This metric represents the name of all nodes traversed to reach its destination.
Data Source
User Action
Packet Number
This metric represents the number that identifies a packet in a traceroute.
Data Source
User Action
Round Trip Time

This metric represents the time taken to traverse from the originating node to the
destionation node and back.
Data Source
User Action
Time To Live
This metric represents the maximum number of hops to traverse before declaring an
unsuccessful attempt to reach the destination node.
Data Source

HTTP Response
User Action
Beacon 43-5
HTTP Response

44
OMS and Repository
The OMS and Repository target exposes metrics that are useful for monitoring the
Oracle Enterprise Manager Management Service (OMS) and Management Repository.
Notification Status
This is a Management Agent metric intended to send out of band notifications when
the Notification system is determined to be in a critical state.
DBMS Job Bad Schedule

This metric flags a DBMS job whose schedule is invalid. A schedule is marked 'Invalid'
if it is scheduled for more than one hour in the past, or more than one year in the
future. An invalid schedule means that the job is in serious trouble.
Data Source
The user_jobs.next_time table in the Management Repository.
User Action
If the job schedule is invalid, the DBMS job should be restarted. To do this:
1. Copy down the DBMS Job Name that is down from the row in the table. This
DBMS Job Name is 'yourDBMSjobname' in the following example.
2. Log onto the database as the repository owner.
3. Issue the following SQL statement:
select dbms_jobname from mgmt_performance_names where display_
name='yourDBMSjobname';
4. If the dbms_jobname is 'myjob', then issue the following SQL statement:
select job from all_jobs where what='myjob';
5. Copy down the jobid.
6. Force the job into the broken state so that it can be restarted by specifying the
following DBMS job command and parameters:
dbms_job.broken(jobid,true)
7. Verify that the job has been marked as broken by using this SQL statement:
select what, broken from all_jobs where broken='Y';
You should see the job in the results.
OMS and Repository 44-1

Notification Status
8. Once you've verified that the DBMS job is marked broken, restart the job with the
following DBMS job command and parameters:
dbms_job.run(jobid)
DBMS Job Processing Time, % of Last Hour

The percentage of the past hour the job has been running.
Data Source
The mgmt_system_performance_log table in the Management Repository.
User Action
If the value of this metric is greater than 50%, then there may be a problem with the
job. Check the System Errors page for errors reported by the job. Check the Alerts log
for any alerts related to the job.
DBMS Job UpDown

The down condition equates to the dbms_job "broken" state. The Up Arrow means not
broken.
Data Source
The broken column is from the all_users table in the Management Repository.
User Action
Determine the reason for the dbms job failure. Once the reason for the failure has been
determined and corrected, the job can be restarted through the dbms_job.run
command.
To determine the reason the dbms job failed, take the following steps (replacing myjob
with the displayed name of the down job):
1. Copy down the DBMS Job Name that is down from the row in the table. This
DBMS Job Name is 'yourDBMSjobname' in the following example.
2. Log onto the database as the repository owner.
select dbms_jobname from mgmt_performance_names where display_
name='yourDBMSjobname';
4. If the dbms_jobname is 'myjob', then issue the following SQL statement:
select job from all_jobs where what='myjob';
5. Using the job id returned, look for ORA-12012 messages for this jobid in the alerts
log and trace files and try to determine and correct the problem.
The job can be manually restarted through the following database command:
execute dbms_job.run (jobid);
Files Pending Load

The number of files waiting for the loader to process, sampled every 10 minutes.

Notification Status
Data Source
This metric is obtained using the following query of the mgmt_oms_parameters table
in the Management Repository.
SELECT value FROM mgmt_oms_parameters
where name='loaderFileCount'
User Action
If the Files Pending Load number is increasing steadily over a period of time, you may
consider one of these options:
■ Increasing the number of background threads.
■ Adding another Management Service and pointing some of the Management
Agents to the new Management Service.
Job Dispatcher Job Step Average Backlog

The number of job steps that were ready to be scheduled but could not be because all
the dispatchers were busy.
When this number grows steadily, it means the job scheduler is not able to keep up
with the workload.
Data Source
The value of the mgmt_oms_parameters table in the Management Repository where
the host_url is the host_url of the Management Service and the parameter_name
column is jobStepCount.
User Action
This value is updated by the job dispatcher before its periodic wait. If the graph of this
number increases steadily over time, the user should take one of the following actions:
■ Increase the em.jobs.shortPoolSize, em.jobs.longPoolSize, and
em.jobs.systemPoolSize properties in the web.xml file. The web.xml file
specifies the number of threads allocated to process different types of job steps.
The short pool size should be larger than the long pool size.
Recommended
Property Defaule value value Description
em.jobs.shortPoolSize 10 10 - 50 Steps taking less
than 15 minutes
em.jobs.longPoolSize 8 8 - 30 Steps taking more
than 15 minutes
em.jobs.systemPoolSize 8 8 - 20 Internal jobs (e.g.
agent ping)
■ Add another Management Service on a different host.

Check the job step contents to see if they can be made more efficient.

Notification Status
Job Dispatcher Processing Time, % of Last Hour

The job dispatcher is responsible for scheduling jobs as required. It starts up
periodically and checks if jobs need to be run. If job dispatcher is running more than
the threshold levels, then it is having problems handling the job load.
Data Source
This is the sum of the amount of time the job has run over the last hour from the
mgmt_system_performance_log table in the Management Repository divided by one
hour, multiplied by 100 to arrive at the percent.
User Action
Last Error
Timestamp of the latest error for the job.
Data Source
The mgmt_system_error_log table in the Management Repository.
User Action
Last Load Error

Timestamp from the last error. If the loader is not reading file correctly, the system may
not be receiving data correctly from the Management Agent.
Data Source
The mgmt_system_error_log table in the Management Repository.
User Action
Loader Directory
The directory from which the loader is getting files.
Data Source
where name=’loaderDirectory’
User Action
If the loader directory is out of space, you may want to look for the error files to
investigate the problem.

Notification Status
Loader Name
The unique name of the loader, consisting of the Management Service name separated
by a comma from the loader name on that Management Service.
Data Source
User Action
None. This is the key field for the metric.
Loader Throughput (rows per hour)

This is the number of lines of XML text processed by the loader thread over the past
hour.
Data Source
User Action
If this number continues to rise over time, then the user may want to consider adding
another Management Service or increasing the number of loader threads for this
Management Service. To increase the number of loader threads, add or change the
em.loader.threadPoolSize entry in the emoms.properties file. The default
number of threads is 2. Values between 2 and 10 are common.
Loader Throughput (rows per second)

This is the number of lines of XML text processed by the loader thread per second
averaged over the past hour.
Data Source
User Action
This metric is informational only.
Management Service Status

Shows whether the Management Service is up or down.
Data Source
The mgmt_oms_parameters and mgmt_failover_table tables in the Management
Repository.
User Action
If the Management Service is down, start it.

Notification Status
Message
This metric lists targets for which the Management Agent has not uploaded data in the
past two hours (excluding Management Agent, Beacon and Repository targets).
The alert is generated each time the Message content changes. The Message content
changes each time the list of targets not uploading data changes.
Data Source
The mgmt_current_availability table in the Management Repository.
User Action
Perform the following steps:
1. Determine the Management Agent for the target having problems.
2. Verify that the target collection schedule is under 2 hour interval.
3. Check the agent logs for errors uploading data.
4. Check the Management System Errors page for Loader errors processing
information from the Management Agent concerned.
Next Scheduled Runtime

The next scheduled runtime for the job.
Data Source
The user_jobs.next_date table in the Management Repository.
User Action
Notification Delivery Time

The time it took to deliver a notification, averaged over the past hour.
Data Source
User Action
If the average delivery time is steadily increasing, verify that the notification methods
specified are valid. Remove any unnecessary or out of date notification rules and
schedules.
Notification Processing Time, % of Last Hour

The percentage of the past hour that Notification delivery has been running.
Data Source

Notification Status
User Action
If the average delivery time is steadily increasing, verify that the notification methods
specified are valid. Remove any unnecessary or out of date notification rules and
schedules.
Notification UpDown
Displays whether the notification DBMS job (which processes severities to determine if
notifications are required) is up or down.
Data Source
The user_jobs table in the Management Repository.
User Action
Determine the reason for the DBMS job failure. Once the reason for the failure has
been determined and corrected, the job can be restarted through the dbms_job.run
command.
To determine why the DBMS job failed, take the following steps:
1. Log onto the database as the Management Repository owner.
select job from all_jobs where what like '%CHECK_FOR_SEVERITIES%';
3. Using the job id returned, look for ORA-12012 messages for this jobid in the alerts
log and trace files and try to determine and correct the problem.
4. Issue the following DBMS job command and parameters:
execute dbms_job.run (jobid);
Notifications Processed
The total number of notifications delivered by the Management Service over the
previous 10 minutes.
Data Source
User Action
If the number of notifications processed is continually increasing over several days,
then you may want to consider adding another Management Service.
Notifications Waiting
When this metric becomes critical, an out of band notification will be sent to the
address specified during the installation.
Data Source
This is the sum of the amount of time the job has run over the last hour from the
mgmt_system_performance_log table in the Management Repository divided by one
hour, multiplied by 100 to arrive at the percent.

Notification Status
User Action
Perform the following user actions:
1. Check the Errors page for errors logged by the Notification Delivery dbms job.
2. Check the number of notification rules defined and verify that they are all
necessary, removing those that are not.
3. Verify that the addresses being used for the notifications are correct.
Number of Duplicate Targets

The count of duplicate targets in the Management Repository.
Data Source
The mgmt_duplicate_targets table in the Management Repository.
User Action
Go to the Duplicate Targets page by clicking the Duplicate targets link on the
Management System Overview page. The Duplicate targets link only appears on the
Management System Overview page if there are problems involving duplicate targets.
Resolve the conflict by removing the duplicate target from the conflicting Management
Agent.
Number of Groups
The number of groups defined for Enterprise Manager.
Data Source
The mgmt_targets table in the Management Repository.
User Action
If you have a problem viewing the All Targets page, you may want to check the
number of roles and groups.
Number of Roles
The number of roles defined for Enterprise Manager.
Data Source
The mgmt_roles table in the Management Repository.
User Action
If you have a problem viewing the All Targets page, you may want to check the
number of roles and groups.
Number of Targets
The number of targets defined for Enterprise Manager.
Data Source
The mgmt_targets table in the Management Repository.

Notification Status
User Action
Number of Users
The number of users defined for Enterprise Manager.
Data Source
The sys.dba_role_privs table in the Management Repository.
User Action
Oldest Loader File

This metric shows how long the loader file has been waiting to be processed by the
loader. This is an indicator of the delay from when the Management Agent sends out
information to when the user receives the information.
Data Source
where name=’loaderOldestFile’
User Action
If the oldest loader file is extremely old, you have a loader problem. You may want to
add another Management Service and point some of the Management Agents to the
new Management Service.
Repository Tablespace Used

This is the total number of MB that the Management Repository tablespaces are
currently using.
Data Source
The dba_data_files table in the Management Repository.
User Action
Session Count
A count of the number of sessions between the Management Service and Management
Repository database.
Data Source
The v$session system view.

Notification Status
User Action
Status since
Timestamp of when the Management Service was marked up or down.
Data Source
The mgmt_oms_parameters table in the Management Repository.
User Action
Steps Per Second

The number of job steps processed per second by the job dispatcher, averaged over the
past hour and sampled every 10 minutes.
Data Source
User Action
Targets not providing data

This metric provides a count of the targets that are not uploading data.
Data Source
The mgmt_targets, mgmt_current_availability tables in the Management Repository.
User Action
Throughput Per Second

The number of notifications delivered per second, averaged over the past hour.
Data Source
User Action
Total Loader Runtime in the Last Hour

This is the amount of time in milliseconds that the loader thread has been running in
the past hour.

Response
Data Source
User Action
If this number is steadily increasing along with the Loader Throughput (rows per
hour) metric, then perform the actions described in the User Action section of the help
topic for the Loader Throughput (rows per hour) metric. If this number increases but
the loader throughput does not, check for resource constraints, such as high CPU
utilization by some process, deadlocks in the Management Repository database, or
processor memory problems.
Total Repository Tablespace

The total MB allocated to the Management Repository tablespaces. This will always be
greater than or equal to the space used.
Data Source
The dba_free_space table in the Management Repository.
User Action
Response
This page indicates whether Enterprise Manager is up or down. It contains historical
information for periods in which it was down.
Status
This metric indicates whether the Management Service is up or down. If you cannot
access the Management Repository, you will get an out of band error.
Metric Summary

Consecutive
All Every 5 Not = Not Defined 0 1 %Message%
Versions Minutes Uploaded
Data Source
sysman/admin/scripts/emrepresp.pl
User Action
This metric checks for the following:

Response
■ Is the Management Repository database up and accessible?

If the Management Repository database is down, start it.
■ Is at least one Management Service running?
If a Management Service is not running, start one.

54 - Enterprise Manager Metric Reference Manual

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

54 - Enterprise Manager Metric Reference Manual

Hochgeladen von

Copyright:

Verfügbare Formate

Oracle® Enterprise Manager

Metric Reference Manual

Part No. B12015-01

Copyright © 2004, Oracle. All rights reserved.

Send Us Your Comments .................................................................................................................. xxxix

Preface ................................................................................................................................................................ xli

1 How To Use This Manual

Part I Oracle Database Metrics

Part II Host Metrics

Part III Oracle Application Server Metrics

9 Internet File System

12 OID LDAP Server

15 Single Sign-On Server

Part IV Oracle Collaboration Suite Metrics

25 OVF AQMWI Application

26 OVF FaxIn Application

28 OVF Telephony Midtier

29 OVF MWI Service

31 OVF Recovery Application

32 OVF Retrieval Application

33 OVF Routing Application

34 OVF Transfer Application

39 SMTP OUT Server

40 SMTP OUT Service

Part V Metrics Specific to Enterprise Manager

44 OMS and Repository

Oracle Enterprise Manager Metric Reference Manual, 10g Release 1 (10.1)

This manual is a compilation of the target metrics provided in Oracle Enterprise

Purpose of This Manual

Accessibility of Code Examples in Documentation JAWS, a Windows screen reader,

Accessibility of Links to External Web Sites in Documentation This documentation

Chapter 1, "How To Use This Manual"

Part I, "Oracle Database Metrics"

Part II, "Host Metrics"

Part III, "Oracle Application Server Metrics"

Chapter 5, "Application Server"

Chapter 8, "HTTP Server"

Chapter 9, "Internet File System"

Chapter 10, "JServ"

Chapter 11, "OC4J"

Chapter 12, "OID LDAP Server"

Chapter 13, "Portal"

Chapter 14, "Reports Server"

Chapter 15, "Single Sign-On Server"

Chapter 16, "Web Cache"

Chapter 17, "Web Application"

Chapter 18, "Wireless"

Part IV, "Oracle Collaboration Suite Metrics"

Chapter 19, "Calendar Applications"

Chapter 21, "IMAP Server"

Chapter 22, "IMAP Service"

Chapter 23, "Mailstore"

Chapter 24, "OID Client"

Chapter 25, "OVF AQMWI Application"

Chapter 26, "OVF FaxIn Application"

Chapter 27, "OVF Mailstore"

Chapter 28, "OVF Telephony Midtier"

Chapter 29, "OVF MWI Service"

Chapter 30, "OVF Recording Application"

Chapter 31, "OVF Recovery Application"

Chapter 32, "OVF Retrieval Application"

Chapter 34, "OVF Transfer Application"