Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Jan 2015
Page 2 of 52
CONTENTS
Contents.............................................................................................................................iii
List of Figures....................................................................................................................vi
List of Tables.....................................................................................................................vii
Revision History...............................................................................................................viii
1Overview..........................................................................................................................1
2Strategy of Monitoring.......................................................................................................3
3.1Remote installation............................................................................................5
iii
3.6Monitor IPC/TCPS listener................................................................................8
4Customization.................................................................................................................14
4.2Listener Monitoring..........................................................................................14
4.4Customized SQL.............................................................................................16
4.6Cluster Support...............................................................................................16
4.7Usage of KRZ_SQL_PREFILTER=TRUE/FALSE...........................................16
5FAQ................................................................................................................................18
iv
5.3About RDB_Instance_Info/ASM_Instance attribute groups.............................19
7Problem Determination...................................................................................................35
Appendix............................................................................................................................vi
8Appendix A. How to use Oracle Instant Client for Tivoli Extended Oracle Agent..............vi
References.........................................................................................................................8
v
LIST OF FIGURES
vi
LIST OF TABLES
Oracle Node, Instance Name, Server Name and the Net Service name in the Listener...................1
Compare of Local monitoring and Remote monitoring.....................................................................2
Environment variable for agent timeout.............................................................................12
Environment variables for alert log monitoring..................................................................13
Agent Affinities...................................................................................................................14
vii
REVISION HISTORY
viii
1 Overview
The IBM Tivoli Composite Application Manager Extended Agent for Oracle Database
provides you with the capability to monitor Oracle Database. You can also use the agent to
take basic actions with the Oracle Database.
IBM Tivoli Monitoring is the base software for the Oracle Database Extended agent. The
Oracle Database Extended agent monitors general Oracle database performance, Oracle
RAC performance, Oracle ASM performance, and Data Guard performance.
You can get detail about agents features from web link below:
http://www-
01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1/com.ibm.itcama.doc_7.2.1/oracleext
ended/fac_landing_install.html?cp=SS3JRN_7.2.1.1%2F10-0&lang=en
Oracle Real Application Cluster Database (RAC) support users to access the same data
from multiple instances on different servers. In RAC environment, the instance level
information includes multiple instances information; the database level information has only
one copy.
For example, you can get following information for each instance: Instance Name, SGA,
Session, and Process. The database level information includes Tablespace, Table, Index
and Datafile, such kind of database level information is consistent and shared by all
instances in a RAC environment.
This document will introduce the best practices in using the Oracle Extended Agent to
monitor general Oracle database, RAC database, ASM database or Dataguard database.
The RAC database is installed into two Solaris Sparc servers as two nodes (RAC1 and
RAC2). The listener is running on port 1521 in both two nodes.
The Oracle cluster ware (including ASM) is installed at /opt/oracle/grid, the Oracle
database software is installed at /opt/oracle/db. The Oracle database servers alert
log location is /opt/oracle/base/diag/rdbms/rac1/trace/alert_rac1.log. The Oracle software
version is 11.2.0.1.
The Oracle RAC database myrac is created with two RAC instances, one instance name
is rac1 in the RAC1 node, and the other instance name is rac2 in the RAC2 node.
1
The Oracle ASM database +ASM is created and there are also two instance, one instance
is +asm1 in the RAC1 node, the other is +asm2 in the RAC2 node.
The Oracle Dataguard database is installed into two Solaris Sparc Sun OS 5.10 servers as
Primary Node in the machine sunpri and standby node in the machine sunstd.
Table 1: Oracle Node, Instance Name, Server Name and the Net Service name in the Listener
Oracle Node Type Oracle Instance Name Server Name Net Service Name in
Listener
RAC1 rac1 sol_rac1 myrac
RAC2 rac2 sol_rac2 myrac
ASM1 +ASM1 sol_rac1 +ASM
ASM2 +ASM2 sol_rac2 +ASM
Dataguard Primary oradb sol_dg1 dbpri
Dataguard Standby oradb sol_dg2 dbstd
2
2 Strategy of Monitoring
This chapter introduces the monitoring strategy with the Oracle Database Extended Agent
about the agent capacity, limitation and scalability.
Note: For a RAC environment, we recommend installing the agent into one node of the
RAC environment, and then the agent performs the remote monitoring. The disk
usage for local node can still be monitored; the alert log for remote nodes can be
monitored after mount the alert log directory at the remote node.
We recommend using the Oracle instant client, because the user can always use the latest
version of Oracle Instant Client package which contains the latest Oracle client dynamic
library code fixes. By using the latest Oracle Instant Client, the user does not need to
upgrade the Oracle server in case there are some known bugs in Oracle Client dynamic
library.
Oracle Instant Client can be downloaded from the Oracle web site:
http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html
3
2.3 Database Connection Number per Agent Instance
We suggest each agent instance monitor no more than 10 database connections in case
there are no more than 5 situations or historical collections in one agent.
This will ensure the total request number in an agent instance is less than 50(10
connection * 5 situations/historical collections). If there are more situations or historical
collections, then we suggest reducing the db connection number for each agent instance
and adding more agent instances.
The number of agent instances is affected by ITM limitation. Including other agents, a
maximum of 15 agent instances can be started on a single system by default. This is a
common ITM limitation, but the limitation can be extended by changing agent instances
configuration, pls refer to Resolving the problem in the below ITM technote:
4
3 Agent Installation and Configuration
3.1 Remote installation
The Oracle Database Extended agent supports remote installation and you can install the
agent into a separated remote machine with Oracle servers.
We strongly recommend you apply the latest interim fix 6.3.1.2-TIV-ITM_KRZ-IF0002 if the
agent version is in 06.31.02.00 in your environment, since 6.3.1.2-TIV-ITM_KRZ-IF0002
includes important fixes.
6.3.1-TIV-ITM_EXT-FP0002:
http://www-01.ibm.com/support/docview.wss?uid=swg24035571
6.3.1.2-TIV-ITM_KRZ-IF0002:
http://www-01.ibm.com/support/docview.wss?uid=swg24038442
For the most current information about the latest fix pack or interim fix, see the agents wiki
page:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli
%20Composite%20Application%20Manager/page/Oracle_Extended_Agent
You need to create a soft link from libclntsh.so.11.1 to file libclntsh.so in the Oracle Instant
Client directory.
Note: There is a full step-by-step guide for the Oracle Instant Client downloading in the
Appendix A. How to use Oracle Instant Client for Oracle Database Extended
Agent.
5
3.4 Mount Oracle alert log directory from remote DB server
The agent monitors Oracle alert log by reading alert log file configured in agent instance
configuration item - Oracle Alert Log File Paths (KRZ_LOG_PATHS).
If the agent is installed in the remote server, Oracle alert log directory (for example
/opt/oracle/base/diag) in the Oracle server need to be mounted to the agent
machine.
Step 1) Check if the NFS server is started in the Oracle server, or run the following
command as user root.
# /etc/init.d/nfs.server start
Step 2) Check alert log directory permission in the Oracle server and add the rx
permission for directory recursively to ensure the mount client can access the
mounted alert log files, run the following command as user root.
# chmod -R +rx /opt/oracle/base/diag
Step 3) Share the alert log directory with following command in the Oracle server rac1.
# share -F nfs -o ro=rac1 /opt/oracle/base/diag
Step 4) Create a local directory and mount the remote alert log directory into local
directory.
# mkdir /mnt/rac1
# mount rac1:/opt/oracle/base/diag /mnt/rac1
There are 3 places where the agent tries to read listener.ora and tnsnames.ora:
If you configure the agent instance with Oracle Home (KRZ_ORACLE_HOME), the agent
tries to read listener.ora and tnsnames.ora from KRZ_ORACLE_HOME/network/admin on
Unix or KRZ_ORACLE_HOME\network\admin on Windows.
You can also copy listener.ora and tnsnames.ora files from remote DB server systems or
create self-defined listener.ora and tnsnames.ora files, put them into a directory on the
system where the agent is installed, and configure their directory path into agent instance
configuration item - Net Configuration Files Directories (KRZ_TNS_PATHS). Multi-
directories are allowed to be configured. The agent tries to read listener.ora and
tnsnames.ora from here as well.
6
Following is sample step to create self-defined tnsnames.ora:
Use editor like Vi to create a new file tnsnames.ora file in the server tivsun21 at
/opt/IBM/Tivoli/config directory with following sample lines. The file permission
should be set as rx-rx-rx.
Note: Connection name of TIVRAC must start from the far left of the line; other lines should
NOT start from left of the line.
7
(ADDRESS = (PROTOCOL=tcp)(HOST=sol_dg2)(PORT=1521)
)
(CONNECT_DATA=(SERVICE_NAME=dgstd)
)
)
For TCPS listener monitoring. You need to set TNS_ADMIN environment variable into
agent running environment or agent configuration files. The TNS_ADMIN path need to
include net service configuration file sqlnet.ora, and the sqlnet.ora file need to include
necessary information for TCPS listener monitoring, for example WALLET_LOCATION. If
sqlnet.ora does not include necessary information, the TCPS listener status is shown as
Inactive, and you will see the following error message in agent log file:
"Oracle error at ServerAttach during Net Service checking" error code is:28759
When ask for the input filed of Oracle Home Directory, input a
blank space to make sure there is no valid value for Oracle Home Directory
When ask for the input field of Oracle Instant Client Installation
Directory, input the path where the Oracle Instant Client is extracted.
8
When ask for the input field of Oracle Connection String, input
the tnsnames.ora connection identifier which is defined in the file
/opt/IBM/Tivoli/config/tnsnames.ora, current value is TIVRAC. Or you can input
the full connection string directly.
When ask for the input filed of Oracle alert log file paths, input
the local alert log file full paths which is mounted from remote Oracle servers.
Note: Only letters, Arabic number, underline and minus characters can be used in the
connection name. Other connection name like +asm is invalid.
When ask for the input field of Oracle Connection String, input
the tnsnames.ora connection identifier which is defined in the file
/opt/IBM/Tivoli/config/tnsnames.ora, current value is TIVASM. Or you can input
the full connection string directly.
9
Example Oracle connection string: (default is: ): TIVASM
Note: In Oracle 10g ASM database, a new Oracle user cannot be created in the sqlplus
directly, you need to create the new Oracle user and grant as SYSDBA role in the
RDBMS sqlplus and copy the RDB password file to the ASM password file,
reference the below technote:
When ask for the input field of Oracle Connection String, input
the tnsnames.ora connection identifier which is defined in the file
/opt/IBM/Tivoli/config/tnsnames.ora, current value is TIVDGPRI. Or you can input
the full connection string directly.
10
When ask for the input field of Username, Password and
Role, input the user with SYSDBA role. The user with SYSDBA role is not
mandatory for Dataguard Primary Node,
When ask for the input field of Oracle Connection String, input
the tnsnames.ora connection identifier which is defined in the file
/opt/IBM/Tivoli/config/tnsnames.ora, current value is TIVDGPRI.
11
If the Database Status is not Active or there is not data in the view of Database
Connection, then check the Error Message column and Suggestion column in the
Agent Event workspace.
12
Figure 3: ASM Database Connection
13
4 Customization
4.1 Extend agent timeout
You can set the environment variable below to extend the agent itmeout from default 60
seconds to more.
Variable Description
The Oracle Database Extended agent version 06.31.00.01 and above versions provide
configuration parameters to disable Listener/Net Service monitoring:
Enhancement: INTERNAL
Abstract: Providing the option to control whether monitoring the listener and Oracle net-
service.
Additional Information: The listener monitoring and net-service monitoring are started by
default. We provide the option that if you do not want this monitoring; you can turn off the
related monitoring functions.
Example KRZ_LISTENER_PING_INTERVAL=0
Example KRZ_TNS_PING_INTERVAL=0
If the Oracle home directory is selected during the agent configuration, then agent will load
Listener definition from file $ORACLE_HOME/network/admin/listener.ora and load Net
Service definition from file $ORACLE_HOME/network/admin/tnsnames.ora automatically.
14
If user do not want to monitor all Listener or Net Service from ORA files in the Oracle home
directory and do not want to revise those files too, customer can specify the TNS_PATH
during the agent configuration and create new listener.ora file and tnsnames.ora files in the
new path and only the targeted Listener or Net Service is specified in the new files.
http://www-
01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1/com.ibm.itcama.doc_7.2.1/oracleext
ended/fac_config_agentspecific_customizingoraclealertlog.html?
cp=SS3JRN_7.2.1.1%2F10-0-2-2-6&lang=en
You can set environment variable in the table below for the alert log monitoring.
Variable Description
15
4.4 Customized SQL
To define a customized SQL statement to monitor in the Customized SQL workspace,
reference Info Center:
http://www-
01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1/com.ibm.itcama.doc_7.2.1/oracleext
ended/fac_config_agentspecific_definingsql.html?cp=SS3JRN_7.2.1.1%2F10-0-2-2-
8&lang=en
http://www.ibm.com/support/docview.wss?uid=swg21588392
The prefilter information is usually gotten from situation's formula. When the agent receives
a request from the situation, this condition will be combined into the SQL query.
16
SELECT tablespace_name, tablespace_used_percentage, ... FROM gv$tablespace_table
WHERE tablespace_used_percentage >= 80;
But the agent has problem to handle the situation which has override formula/includes the
original situation's formula condition info. The root cause is that the override formula info
cannot be passed to agent in current ITM agent factory framework.
A situation with formula tablespace_used_percentage >= 80% and the override formula is
tablespace_name = 'TEST' and tablespace_used_percentage >= 50.
Only the formula '>=80%' will be used in the where clause as below, because override
formula info cannot be passed to agent in current ITM agent factory framework:
In above example, agent will only query data from Oracle which matches with original
formula of >=80%, so the other tablespace which matches with override formula will not be
queried and it will not be fired in the TEMS anyway. This is a potential drawback, as it can
cause alerts to be missed.
17
5 FAQ
5.1 The SQL query the agent uses
You can get query the agent uses for most attribute groups from the below file on the
system where the agent is installed.
UNIX:
<CANDLEHOME>/<Arch>/rz/bin/krzsql.xml
WINDOWS:
<CANDLEHOME>\TMAITM6(_x64)\krzsql.xml
Take "ASM Disk Group Capacity" workspace view as example, the corresponding attribute
group is ASM_DiskGroup. Search ID="ASM_DiskGroup" from krzsql.xml, you can get the
query for it:
The agent always use Oracle OCI library API to get the status of net service names.
If the environment variable TNS_ADMIN is NOT set or there is not sqlnet.ora file in
TNS_ADMIN, the agent generates net service configuration file
<Installation_Dir>/logs/<Host_Name>_rz_<Agent_Instance_Name>/sqlnet.ora, for
example,
18
The agent auto-generated sqlnet.ora only contains basic configuration information of net
service.
(DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=orcl)
(CID=(PROGRAM=krzstart)(HOST=tivagent)(USER=root)))
(ADDRESS=(PROTOCOL=TCP)(HOST=rac1.cn.ibm.com)(PORT=1521)))
For agent version 6.31.00.01 and above versions, The RDB_Instance_Info and
ASM_Instance attribute groups were enhanced to show both active and inactive instances.
For inactive instance, the status is shown as OFFLINE. But there is a prerequisite to show
inactive instance, the instance need to be active when the agent instance is started,
otherwise, the agent is unable to save its information into cache and cannot show its
information.
19
6 Oracle Monitoring Concept and Situations
To enable users and applications to view or update data in the database, Oracle must start
a set of processes, called background processes, and must allocate some memory to be
used during database operation. The background processes and memory allocated by
Oracle together make up an instance. An instance must be started to read and write
information to the database. However, having a database is not necessary to run an
instance.
20
Figure 5: Instance Status table in the Instance Overview workspace:
21
Figure 7: Product predefined situations for Oracle Inactive Instance
Tablespace created.
You can navigate to the Tablespace Usage workspace from the Tablespace node.
22
Figure 8: Navigate to Tablespace Usage workspace
Then you can get the usage percentage for all tablespaces like TBS_3 which is created in
the example above.
If the option of AUTOEXTEND for the Tablespace is OFF, Maximum File Size is equal
to the Allocation Size, then %Free_To_Maximum is equal to the %Free_To_Allocated
also.
In the sample Tablespace TBS_3, the Maximum file size is 80M, the Allocation size is10M
and the Used size is 1M. So its %Free_To_Maximum is (80-1)/80*100%=98.75% which is
greater than the %Free_To_Allocated of (10-1)/10*100%=90%.
23
ASM is a vertical integration of both the file system and the volume manager built
specifically for Oracle database files. It extends the concept of stripe and mirrors
everything to optimize performance, while removing the need for manual I/O tuning.
Oracle storage is added and removed from ASM disk groups in units of ASM disks.
ASM disks can be monitored in the ASM Disk Capacity workspace linked from the
Automatic Storage Management node.
Figure 11: ASM Disk Capacity table in the ASM Disk Capacity workspace
RAC is an option that allows multiple concurrent instances to share a single physical
database.
There are several workspaces for the RAC monitoring in the Node of Real Application
Cluster.
24
Figure 12: Navigate to RAC related workspaces from Real Application Cluster node
Oracle provides software to create and manage the Oracle database. The database
consists of physical and logical structures in which system, user, and control information is
stored. The software that manages the database is called the Oracle database server.
Collectively, the software that runs Oracle and the physical database are called the Oracle
database system.
25
Figure 14: Navigate from Database node
Figure 15: Global Resources Consumption table in the Resource Limitation workspace
26
Each Oracle instance you run produces an alert log, which is a sequential log of text
messages pertaining to overall database operations including Oracle startup and
shutdown, major database events such as log archiving and tablespace definition, and
certain categories of errors. Submitting a copy of your alert log data is required in many
problem determination situations. Refer to the Oracle Database Administrator's Guide for
general information on the alert log.
Example below has been simplified by using values selected directly from the V$SYSSTAT
table, rather than over an interval. It is best to calculate the delta of these statistics over an
interval while your application is running, then use them to determine the hit ratio.
27
SQL> SELECT NAME,VALUE FROM V$SYSSTAT
2 WHERE NAME IN ('db block gets from cache', 'consistent gets from cache', 'physical
reads cache');
NAME VALUE
--------------------------------------------- ----------
Using the values in the output of the query, calculate the hit ratio for the buffer cache with
the following formula:
1 - (('physical reads cache') / ('consistent gets from cache' + 'db block gets from cache')
28
Figure 17: Buffer Cache performance table from Cache node
29
Figure 18: Navigate to SGA workspace from Memory node
Figure 19: SGA Usage bar chart in the SGA Detail workspace
There are two different concepts about SGA free memory with the Oracle Database
Extended agent. Here is a clarification of the two attributes, this is normal behavior.
In Figure 20, the "Free Total SGA (MB)" attribute in the "SGA Allocation" attribute group
uses the v$sgastat Oracle performance view. It means the free memory of allocated
memory in the buffer cache, shared pool, etc.
30
Figure 20: Free Total SGA (MB) in the SGA Allocation workspace
In Figure 21, the Free SGA Memory Available (MB)" attribute in the "SGA Usage" attribute
group uses the v$sgainfo Oracle performance view. It means the free SGA memory which
is still not allocated to buffer cache, shared pool, etc.
31
Figure 21: Free SGA Memory Available (MB) in the SGA Usage workspace
32
Figure 22: Top SQL workspace
When two Oracle users are attempting to change the same row, there is a lock contention
with the lock type of TX. A deadlock can occur when two or more Oracle users are waiting
for data locked by each other. Deadlocks prevent some transactions from continuing to
work. Figure below is a hypothetical illustration of two transactions in a deadlock.
33
Figure 24: Two Transaction in a deadlock
In Figure 24, no problem exists at time point A, as each transaction has a row lock on the
row it attempts to update. Each transaction proceeds without being terminated. However,
each tries next to update the row currently held by the other transaction. Therefore, a
deadlock results at time point B, because neither transaction can obtain the resource it
needs to proceed or terminate. It is a deadlock because no matter how long each
transaction waits, the conflicting locks are held.
34
Figure 26: Lock Conflict table with the deadlock record in Lock Contention workspace
35
7 Problem Determination
Troubleshooting: Slow Database Monitoring
http://www-01.ibm.com/support/docview.wss?uid=swg21508178
Question:
Cause:
The oracle database is slow on the system and the agent often times out during
monitoring.
Answer:
http://www-01.ibm.com/support/docview.wss?uid=swg21511760
Question:
How to configure the TOP SQL attribute group historical collection for the RZ agent
Answer:
To configure the historical collection for the TOP SQL attribute group, the user needs to
click on the third tab ("Filters") and fill the requested filters: "begin hour" ,"end hour", "order
by" and "row order". This setting is required to get the historical collection enabled for this
attribute group.
36
Figure 27: History Collection Configuration for TOPSQL
Problem (Abstract):
Symptom:
If the IF0001 has been applied, you can safely ignore the error message for test
connection, as follows.
NLS_NUMERIC_CHARACTERS=.
Try to start this agent, if agent is not started, try next step (2).
NLS_NUMERIC_CHARACTERS=.,
37
Try to start this agent, if agent is not started, please collect the debugging data for the IBM
support investigation as explained at next step (3).
Start agent and send to IBM Support the output of "digup -a" command.
Also, please use "sqlplus" to connect to database directly: issue following SQL and send
the output to the IBM Support
Please send the outputs from all the above SQLs statements to the IBM Support for more
investigation.
Question:
How to remotely monitor the Oracle alert log on AIX with an RZ agent installed on
Windows?
38
Answer:
For monitoring remote alert logs on AIX, UNIX or Linux systems, the file system containing
the logs needs to be locally mounted on the RZ agent machine.
To mount AIX file systems in Windows, you need to install Samba on AIX.
Troubleshooting: Oracle Extended Agent (rz) fails loading Oracle OCI library
Problem (Abstract):
The Oracle Extended Agent is not running properly and produces the error: Loading Oracle
OCI library failed!
Symptom:
The Oracle Extended Agent starts and connects to TEMS but the Agent does not display
Oracle data.
Cause:
This error occurs because the Oracle Extended Agent(rz) can not use the Oracle Client
Interface(OCI) to connect to the Oracle instance.
The Oracle Extended Agent on unix/linux starts the krzagent and then launches the
krzclient process. The krzclient process fails when it tries to connect to the Oracle
database.
Reconfigure the agent and correct Oracle home or Oracle Instant Client Library.
Reconfigure the agent and restart.
39
APPENDIX
http://www.oracle.com/technetwork/database/features/instant-client/index-
097480.html
Step 2) click one suitable platform from list, especially for the 32-bit and 64-bit
platforms.
vi
Instant Client Downloads for Solaris Operating System(SPARC 64-bit)
Step 4) download Instant Client Package - Basic: All files requires to run OCI, OCCI,
and JDBC-OCI applications.
vii
REFERENCES
[Reference List] (Use bibliography format. Style automatically creates a hanging indent when text
runs over to the next line.)
Best Practices for Oracle Monitoring with Oracle Extended Agent.
Copyright IBM Corporation 2009
IBM United States of America
Produced in the United States of America
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM
representative for information on the products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used.
Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be
used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program,
or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of
this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
The following paragraph does not apply to the United Kingdom or any other country where such provisions are
inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PAPER AS IS WITHOUT WARRANTY OF
ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow
disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes may be made periodically to the
information herein; these changes may be incorporated in subsequent versions of the paper. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this paper at any time without notice.
Any references in this document to non-IBM Web sites are provided for convenience only and do not in any manner serve
as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product
and use of those Web sites is at your own risk.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of
this document does not give you any license to these patents. You can send license inquiries, in writing, to:
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent
goals and objectives only.
This information is for planning purposes only. The information herein is subject to change before the products described
become available.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp.,
registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other
companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at
www.ibm.com/legal/copytrade.shtml.
==> The listed trademarks of the following companies require marking and attribution only if you mention any of
them in your paper:
9
Best Practices for Oracle Monitoring with Oracle Extended Agent.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe
Systems Incorporated in the United States, and/or other countries.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now
part of the Office of Government Commerce
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep,
Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States
and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States,
other countries, or both.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is
registered in the U.S. Patent and Trademark Office
UNIX is a registered trademark of The Open Group in the United States and other countries.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both
and is used under license therefrom.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other
countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
10