Oratop工具——实时数据库性能监控工具

Oratop工具——实时数据库性能监控工具

原文地址：Oratop工具——实时数据库性能监控工具 作者：realkid4

在任何系统优化过程中，“80/20原则”是我们一定要关注的问题。简单的说，就是我们系统80%的性能问题、现象，都是有少数几个甚至一个问题造成的。这就需要我们面对复杂的系统性能问题的时候，要学会“拨开云雾、蛇打七寸”。

 

落实在Oracle优化过程，同样如此。从10g开始，我们开始频繁接受“Top-xxx”的概念，无论是从OEM（Oracle Enterprise Manager）还是借助AWR事后报告库，解决主要矛盾，发掘主要Top Events就成了我们日常工作不可缺少的部分。

 

实际工作中，对Top的发掘和Oracle动态信息的收集，很多时候还是有点力不从心和滞后之感强烈。Oracle官方的客户服务网站MOS，经常有一些有用的小工具，提供给我们使用。本篇中，我们主要来介绍下Oratop工具的特点和使用。

 

1、Oratop工具简述

 

Oratop源自MOS的一篇文章和工具链接（oratop - utility for near real-time monitoring of databases, RAC and Single Instance [ID 1500864.1]）。从名称上看，Oratop最大特点是支持实时轻量级监控。在Oracle 12c的EM Express之前，OEM还是一个重体积的组件。相比之下，oratop完全适合那些想使用数据库实时监控功能，但是又不愿意启动OEM的用户需要。

 

从功能上看，Oratop主要有三大特点：

 

ü  监控当前的数据库活动；

ü  监控数据库性能；

ü  识别当前阻塞会话和瓶颈会话；

 

目前，Oratop是在MOS上免费下载，分别有32位和64位两个版本。

 

2、软件安装初启动

 

从网站上下载软件之后，是一个命名为oratop.v13.2.1_X8664的可执行程序，注意要区分32位版和64位版。

 

首先，判断适合的Linux版本，并且创建程序目录。Oratop是一个典型的“绿色”软件，不需要安装，只需要给一个运行目录即可。

 

--64位操作系统

[root@localhost ~]# uname -a

Linux localhost.localdomain 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

 

 

[root@localhost ~]# mkdir /oratop

[root@localhost ~]# cd /oratop

[root@localhost /]# cd oratop/

[root@localhost oratop]# ls -l

total 0

[root@localhost oratop]#

 

 

进行目录的权限转换和程序拷贝。为了方便执行，我们最好还要进行一下重命名工作。

 

 

[root@localhost /]# chown -R oracle:oinstall /oratop

[root@localhost /]# su - oracle

[oracle@localhost ~]$ cd /oratop/

[oracle@localhost oratop]$ ls -l

total 92

-rw-r--r--. 1 oracle oinstall 93640 May 17 13:39 oratop.v13.2.1_X8664

 

[root@localhost oratop]# ls -l

total 92

-rw-r--r--. 1 root root 93640 May 17 13:39 oratop.v13.2.1_X8664

 

[oracle@localhost oratop]$ mv oratop.v13.2.1_X8664 oratop

[oracle@localhost oratop]$ ls -l

total 92

-rw-r--r--. 1 oracle oinstall 93640 May 17 13:39 oratop

 

 

注意：使用oratop在环境变量上需要一些额外的配置内容。主要是对于变量LD_LIBRARY_PATH的配置。我们一般都不会去配置这目录，但是oratop要求必须进行配置。

 

配置方法是修改根目录上的.bash_profile文件。

 

 

[oracle@localhost ~]$ vi .bash_profile

 

 

export ORACLE_BASE=/u01/app/oracle

export ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_1

export ORACLE_SID=isis2db

 

export PATH=$PATH:$ORACLE_HOME/bin

 

（篇幅原因，掠过部分内容……）

export LD_LIBRARY_PATH=$ORACLE_HOME/lib

".bash_profile" 36L, 901C written                            

[oracle@localhost ~]$

 

 

[oracle@localhost ~]$ env | grep LIB

LD_LIBRARY_PATH=/u01/app/oracle/product/11.2.0/dbhome_1/lib

 

 

下面我们来试着执行以下命令。

 

 

[oracle@localhost oratop]$ ./oratop -i 10 / as sysdba

 

oratop: Release 13.2.1 Production on Fri May 17 13:43:34 2013

 

Copyright (c) 2011, Oracle.  All rights reserved.

 

Processing ...（等待片刻……）

 

 

参数-i表示数据刷新间隔，也就是多长实际更新一下页面数据信息。/ as sysdba表示登录本机连接。注意，这也就意味着我们可以远程使用oratop连接到其他服务器上面去。更进一步说，通过远程连接的方法，可以连接到任何版本操作系统上的Oracle服务器的。

 

出现字符界面显示。

 

 

 

oratop 1:  131 isis 13:44:24 up  0.0h,  1 ins,   3G mt,  41 sn,  3 us,   0% db

ID %CU HLD MBPS IORL %FR PGAU ASC ASI ASW ASP   AAS USN  TPS UCPS SSRT DBC DBW

 1  12   0   71   0m  18 161M   1   0   0   0   0.1  41    0   24   3m  94   6

                                                                             

EVENT     (Cumulative)      AVG: TOT WAITS  TIME(s)  AVG_MS PCT  WAIT_CLASS  

DB CPU                                       112868          75              

SQL*Net message from dblink       16794060    14852     0.9  10  Network     

SQL*Net more data from clien        193150     8260    42.8   5  Network     

log file parallel write            1025524     7308     7.1   5  System I/O  

enq: TX - row lock contentio          1289     7248  5622.9   5  Application 

                                                                             

ID   SID  SPID USR PROG  PGA OPN SQLID/BLOCKER  E/T STATUS STE WAIT_EVENT  W/T

 

 

3、初识Oratop

 

从字符界面上看，oratop结果集合分为四个部分，分别为：Header Section、Database Section、DB Events Section和Processes Section。

 

 

Header Section中，包括了连接数据库的总体信息，包括运行多长时间、实例个数（for RAC）、内存大小和数据库占据CPU时间的比例。

 

Database Section中，包括了各个实例（for RAC）下，每个实例的基本参数和复杂信息。如每个实例活动会话个数、每秒的事务数量和内存使用情况等。

 

DB Events Section是从Wait Event角度进行评估。评估排在头几位的等待事件信息，默认情况下，这个度量是累计的，也就是从启动数据库到当前时间。我们可以切换到当前时间模式下。

 

Processes Section是记录下处在Block和Contention状态的连接会话信息。当数据库出现有会话被阻塞的情况，就会记录在这个Section里面。

 

4、丰富的帮助系统

 

Oratop结果显示中，大量使用的简写和缩写，这在一定程度上阻碍我们阅读结果。为此，Oratop开发人员设计了完备功能的帮助体系。

 

在使用-h参数，或者运行过程中按下键盘h，就可以切换到帮助界面。

 

使用h按键

 

 

oratop: Release 13.2.1

------------------------------------------------------------------------------

Dynamic Keys

        d : Toggle Top 5 Wait Events between Real-Time and Cumulative

        f : Toggle between short & long format (for header & Process sections)

        i : Interval Delay time (requires value in seconds)

 

Nomenclature:

        [M] : Signify 1 minute averaged value, else, Real Time

        [F] : denote a Forground (FG) value, else, Background (BG)

------------------------------------------------------------------------------

Acronym Help Menu:

 

HEADER Section    .. [1]

DATABASE Section  .. [2]

DB EVENTS Section .. [3]

PROCESSES Section .. [4]

Quit Help         .. (Q|q)

 

Enter selection Number:

 

 

动态按键（Dynamic Keys）实际上就是在运行过程中，可以动态实时点击，查看不同维度结果的案件。

 

笔者比较喜欢d按键，这样可以从累计Event信息到实时Event信息，把握最新的数据库等待时间状态。

 

 

 

(d) –使用了d动态按键

oratop 1:  376 NBST 14:31:22 up  5.1d,  1 ins,   2G mt, 135 sn,  7 us,   4% db

ID %CU HLD MBPS IORL %FR PGAU ASC ASI ASW ASP   AAS USN  TPS UCPS SSRT DBC DBW

 1   2   0    0   0m  17 394M   1   0   0   0   0.0 135    4   71 297u  85  15

                                                                              

EVENT     (Real-Time)       AVG: TOT WAITS  TIME(s)  AVG_MS PCT  WAIT_CLASS  

DB CPU                                         1867         100              

                                                                              

ID   SID  SPID USR PROG  PGA OPN SQLID/BLOCKER  E/T STATUS STE WAIT_EVENT  W/T

 

 

另一部分帮助就是显示对四个section的解释，解释的非常详细，值得读者学习。篇幅原因，这里只显示一份结果。

 

 

Section 1- HEADER (Global information)

   "oratop"  : program name

         : instance_id to which oratop is connected to

        : oratop's SID

     : DB_UNIQUE_NAME

    [M]: Time of most recent stats (hh24:mi:ss)

         : Database Uptime

   
     : Total number of instance(s)

         : Total DB memory cluster wide (SGA+PGA)

      [F]: User sessions (idle & active)

      [F]: Number of distinct users (idle & active)

   <%db>     : %database busy, 0% indicate idle db

 

 

5、复杂应用

 

Oratop的本质和优势在于轻量型和实时。一个很小的程序，可以在自身消耗较小的情况下发现问题。

 

Block and Contentio是Process Section部分重点问题。阻塞是数据库内部资源征用的一种结果，及时发现Blocking和Contention是非常重要的。

 

下面片段是笔者模拟的一个两个会话同时修改一行数据，之后一个会话被阻塞时，oratop监控到的情况。

 

 

锁定等待

                                                                            

ID   SID  SPID USR PROG  PGA OPN SQLID/BLOCKER  E/T STATUS STE WAIT_EVENT  W/T

 1   187 25971 SYS DEDI 908k DEL 1:193:25968    20s ACTIVE WAI enq: TX -   20s

 

 

在信息中，等待Session信息、SQL信息和等待事件信息都是我们进行进一步调优的依据。

 

另外，我们可以在一台Linux上安装oratop，监控连接另一台远程数据库服务器，比如AIX系统。

 

首先，我们需要建立本地连接名。

 

 

[oracle@localhost oratop]$ netca

 

Oracle Net Services Configuration:

Default local naming configuration complete.

    Created net service name: nbstest

Oracle Net Services configuration successful. The exit code is 0

[oracle@localhost oratop]$ tnsping nbstest

 

TNS Ping Utility for Linux: Version 11.2.0.3.0 - Production on 17-MAY-2013 14:06:38

 

Copyright (c) 1997, 2011, Oracle.  All rights reserved.

 

Used parameter files:

 

 

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 10.1.15.66)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = nbstest)))

OK (0 msec)

 

 

监控时候，就是用对应的用户名密码和连接名进行连接。

 

 

 

[oracle@localhost oratop]$ ./oratop -i 10 sys/sys@nbstest as sysdba

 

oratop: Release 13.2.1 Production on Fri May 17 14:07:39 2013

 

Copyright (c) 2011, Oracle.  All rights reserved.

 

 

6、形色参数

 

最后我们介绍一下oratop可以使用的参数。在示例中，我们见到了-i参数。

 

-i参数表示监控间隔。后面一般跟着一个数字，表示每隔几秒钟进行一次数据收集。这个参数要进行选择的，如果太大，很多关键数据不能收集查看。如果设置太少，oratop自身也会造成性能瓶颈。

 

-b批量运行模式。实时数据如果需要输入到一个结果集合文件，供下一步处理使用，可以使用b模式参数。当设置b参数之后，oratop会持续运行，或者在事先设计好的次数后结束。

 

-n设置最大迭代操作次数。

 

-d一改默认是累计事件的统计情况，采用实时统计。

 

 

 

[oracle@localhost oratop]$ ./oratop -i 5 -b -d / as sysdba

 

oratop: Release 13.2.1 Production on Fri May 17 14:59:32 2013

 

Copyright (c) 2011, Oracle.  All rights reserved.

 

 

Processing ...

 

oratop: Release 13.2.1 Production on Fri May 17 14:59:32 2013

 

 

ID   SID  SPID USR PROG  PGA OPN SQLID/BLOCKER  E/T STATUS STE WAIT_EVENT  W/T

 

oratop: Release 13.2.1 Production on Fri May 17 15:00:17 2013

 

oratop 1:  202 isis 15:00:09 up  0.0h,  1 ins,   3G mt,  67 sn,  3 us,   3% db

ID %CU HLD MBPS IORL %FR PGAU ASC ASI ASW ASP   AAS USN  TPS UCPS SSRT DBC DBW

 1   0   0    0   0m  17 183M   1   0   0   0   0.0  67    0    6 286u  60  40

 

EVENT     (Real-Time)       AVG: TOT WAITS  TIME(s)  AVG_MS PCT  WAIT_CLASS  

DB CPU                                         1944         100              

（有省略…..）

oratop: Release 13.2.1 Production on Fri May 17 15:00:27 2013

 

 

7、结论

 

Oratop是一个非常出色的轻量型监控工具，条件运行的话可以尝试一下。

 

oratop - Utility for Near Real-time Monitoring of Databases, RAC and Single Instance (文档 ID 1500864.1)

文档详细信息
 


类型:
状态:
上次主更新:
上次更新:
语言:

SCRIPT
PUBLISHED
2017-4-19
2017-4-19
English日本語???

In this Document

Purpose
Requirements
Configuring
Instructions
 
  Quick Start Guide
Script
Sample Output
References

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.3 to 11.2.0.4 [Release 11.2]
Oracle Database - Enterprise Edition - Version 12.1.0.1 to 12.1.0.2 [Release 12.1]
IBM AIX on POWER Systems (64-bit)
HP-UX PA-RISC (64-bit)
HP-UX Itanium
Linux x86-64
Linux x86
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)

PURPOSE

oratop is a utility similar to the unix OS utility top which gives a overview of database performance and can be used in combination with top to get a more complete overview of system performance 

REQUIREMENTS

Supported Platforms

Linux x86

Linux x86-64

Solaris SPARC-64

Solaris x86-64

AIX (PPC)

HP-UX PARISC*

HP-UX IA

* 11gR2 only

NOTE: oratop on any platform can be used to monitor databases on other platforms.

To monitor databases on other platforms simply define an alias in tnsnames.ora of the Oracle client and connect to the databases remotely as you would with sqlplus

  

Supported Oracle Releases

11gR2 (11.2.0.3, 11.2.0.4)

12cR1 (12.1.0.1, 12.1.0.2)

 

CONFIGURING

oratop is now distributed and integrated with Trace File Analyzer Collector (TFA) along with all the other tools that are a part of the Support Tools Bundle.

So rather than downloading oratop separately the preferred method for obtaining oratop is to download the latest version of TFA.  This integration means 

that anytime TFA is upgraded (PSUs, download from MOS, etc) the latest version of oratop and the other Support Tools of the bundle will also be obtained.

If your Grid Infrastructure version is 11.2.0.4 or 12.1.0.2 then TFA will automatcially be installed.  In either case we recommend that the TFA installation be

upgraded to the latest version available from TFA Collector - Tool for Enhanced Diagnostic Gathering (Doc ID 1513912.1) in order to obtain the Support Tools 

Bundle which was first bundled with TFA version 12.1.2.3.0, as well as various other new features, bug fixes and optimizations.

Download the oratop executable for:

11gR2 on Linux x86-64 here.

11gR2 on SUSE10 Linux x86-64 here.

12c on Linux x86-64 for use with 12c clients here.

11gR2 on Linux x86-32 here.

12c on Linux x86-32 for use with 12c clients here.

11gR2 for Solaris SPARC here.

12c for Solaris SPARC here.

11gR2 for Solaris x86 here.

12c for Solaris x86 here.

11gR2 for AIX here.

12c for AIX here.

11gR2 for HP-UX PARISC here.

11gR2 for HP-UX IA here.

12c for HP-UX IA here.

 

Please download and review the oratop Users Guide for specific instructions on how to configure and run oratop.  A Quick Start Guide is provided in the Instructions section of this Note.

INSTRUCTIONS

Quick Start Guide

Note:   For detailed instructions on how to run oratop please download and review the latest oratop Users Guide.

Running oratop from within TFA Collector

Use the tfactl CLI to set the database context for oratop, ie., the target database that oratop should connect to, eg.,

$ $TFA_HOME/bin/tfactl db orcl       <== set the target database context in TFA for oratop to use

$ $TFA_HOME/bin/tfactl oratop        <== oratop will connect to the orcl database, no need to worry about any of the oratop pre-reqs, TFA takes care of all that

  

OR

Use the tfactl shell to set the database context for oratop, ie., the target database that oratop should connect to, eg.,

$ $TFA_HOME/bin/tfactl              <== invoke the tfactl shell prompt

tfactl> db orcl                     <== set the target database context in TFA for oratop to use 
Set db to orcl
orcl tfactl> oratop

To run oratop in "batch mode" for a spoecific number os snapshots

$ $TFA_HOME/bin/tfactl

tfactl> db orcl
Set db to orcl
orcl tfactl> oratop -bn10         <== this example would run 10 snapshots at the default 5 second interval unless the interval had been changed eg. oratop -i 10 -bn10

Once oratop is invoked and running within the TFA framework its operation is exactly the same as if run standalone with the exception that the database must be running on the node from which the "tfactl oratop" command is executed.  If the database is running remotely on one or more nodes of a RAC cluster, log in one of those nodes and run the "tfactl oratop" command on there after setting the database context.  In other words when oratop is run from within TFA there is no remote database access, a bequeath connection is used instead.  

Another thing to be aware of is that when oratop is run from within the TFA framework in batch mode as in the above example the ouput is automatically redirected to the oratop specific directory in the TFA repository location $TFA_REPOSITORY/supptools/oratop for automatic collection by TFA Collector.  In standalone mode you would need to use the redirection symbol ">" and specify the path and file name for re-direction and TFA would not necessarily know where to collect the resultant file unless it is redirected to one of the know diagnostic directories.


Running oratop standalone

  1. Log in to the system as the Oracle RDBMS software installation owner
  2. Stage the oratop executable on the server on which the tool will be executed.  On a RAC system it is only necessary to stage the executable on one node as it is RAC aware.
  3. Change the name of the executable, eg.
  4. $ mv oratop* oratop
  5. Validate the permissions for oratop are 755 (-rwxr-xr-x). If the permissions are not currently set to 755, set the permissions on oratop as follows: 

    $ chmod 755 oratop

  6. Configure the execution environment as follows (if not already set accordingly)
  7. $ export TERM=xterm  #or vt100

    $ export ORACLE_HOME=<11.2 database home>

    $ export LD_LIBRARY_PATH=$ORACLE_HOME/lib

    $ export PATH=$ORACLE_HOME/bin:$PATH

    $ export ORACLE_SID=  #only needed if connecting to a local database

  8. Invoke the tool to monitor a local database as follows (interval can be any interval in seconds):

    $ ./oratop -i 10 / as sysdba

  9. Non-dba privileged user requires specific grants to use the tool.  See User Guide for grants required.
  10. Databases can be monitored remotely using a tns alias as described in the oratop Users Guide.
  11. $ ./oratop -i 10 username/password@tns_alias

    $ ./oratop -i 10 system/manager@tns_alias

  12. To exit the program simply press the keyboard key "q".  To abort, CTRL-C.

Troubleshooting:

If you receive an error similar to 

./oratop: error while loading shared libraries: libclntsh.so.11.1: cannot open shared object file: No such file or directory

that is an indication that libclntsh.so.11.1 was not found in the path defined in LD_LIBRARY_PATH similar to 

$ export LD_LIBRARY_PATH=$ORACLE_HOME/lib  (ie., the location of libclntsh.so.11.1)

CAUTION

This sample code is provided for educational purposes only, and is not supported by Oracle Support. It has been tested internally, however, we do not guarantee that it will work for you. Ensure that you run it in your test environment before using.

SCRIPT

The tool is a compiled c program.

SAMPLE OUTPUT

Sample workload

REFERENCES

NOTE:1594347.1 - RAC and DB Support Tools Bundle

附件
 

oratop User Guide

Abstract

oratop can be used to monitor Oracle databases (release 11.2 onwards) on any platform but the executable must run on Linux with an Oracle compatible client.  To monitor databases on other platforms simply define an alias in tnsnames.ora of the Linux client and connect to the databases remotely as you would with sqlplus.

INTRODUCTION

The Oracle program named oratop allows users with select privilege to a set of Oracle’s views to monitor 11.2 or higher version of oracle database activities.  It runs dynamically in near real time and provides a live window to a running database.  It is Single instance/ RAC/ ASM aware utility. (see sample snapshot shown in Figure 1 below) Key motivations include:

?         Monitoring current database activities,

?         Database performance,

?         Identifying contentions and bottleneck

Figure 1. oratop text-based user interface (default mode) 

 

ENHANCEMENTS

? SQL Monitoring

? Database Service

? Multitenant Database  (12c oracle  CDB/PDB)

? Active Data Guard

SECTIONS  

The “oratop” displays relevant database activity information presented in four sections.

? Section 1 - HEADER: Global database information

? Section 2 - DATABASS: Database instance Activity

? Section 3 - DB EVENTS: AWR like “Top 5 Timed Events“

? Section 4 – PROCESS/SQL: Processes/SQL information

Specific detail of the various sections data can be obtained using the interactive help (see

Runtime usage Sections Detail below)

CLIENT

Connection method is largely similar to sqlplus.  If it works for sqlplus, then it should work the same for oratop.

Shell environment settings

$ export ORACLE_HOME=<path>

$ export LD_LIBRARY_PATH=$ORACLE_HOME/lib

$ export PATH=$ORACLE_HOME/bin:$PATH

Bequeath[1]

$ export ORACLE_SID=<sid>

Remote server[2]

Options:

?        TNS:  

$ export TNS_ADMIN

-   connect with a TNS alias name as defined intnsnames.ora, or

-   set TWO_TASKto the tns alias and connect without alias name

?        EZConnect

I.  COMMAND LINE MODE

Command line synopsis can be obtained by invoking the utility with “-h” option as shown in Figure 2.

Figure 2. Command line help

Logon

Invocation:

$ oratop [Options] [Logon] Example,

Using Easy Connect (EZConnect) ?    Non-default port oratop system/manager@dbhost:4800/db1.domain.com ?    Default port (1521):

oratop system/manager@dbhost/db1.domain.com

Options

d :  Real-Time Top 5 Wait Events, section 3.

Specifies Wait Events display mode.

Default:  Cumulative

To override the default value

? Command line:  -d ? Runtime:  d

k : “FILE#:BLOCK#” for objects being waited on, process section 4.

Specifies “FILE#:BLOCK#” display mode.

Default:  EVENT/LATCH

To override the default value

? Command line:  -k ? Runtime:  k

m : “MODULE/ACTION”, process section 4. Specifies “MODULE/ACTION” display mode.

Default:  USERNAME/PROGRAM

To override the default value

? Command line:  -m ? Runtime:  m

s :  SQL mode of section 4. Specifies SQL display.

Default: Process mode

To override the default value

? Command line:  -s ? Runtime:  s

c :  Database Service centric mode.

Displays information based on the database service specified in the connect string.

Default: Connection mode

To override the default value ? Command line:  -c ? Runtime:  N/A

f :   Long format, (132 columns) 

Specifies long format for header & process section.

Default: short (80 columns)

To override the default value

? Command line:  -f ? Runtime:  f

p :  Process mode of section 4. process display. Default: Process mode

To override the default value

? Command line:  -p

? Runtime:  p

b :  Batch mode operation.

Runs in sequential frames.  It is useful for sending output to a file. In this mode, oratop will run continuously interrupted only by the user (CTRL-C) or until the iterations limit is reached if it is set with the '-n' command-line option. Default: Text-based user interface

To override the default value ? Command line:  -b ? Runtime:  N/A

n :  Maximum Number of iterations.   (requires a number)

Specifies the maximum number of iterations, or frames, oratop should produce before ending.

Default: infinite

To override the default value ? Command line:  -n ? Runtime:  N/A

t:  Displays tablespace information.

Default: N/A

? Command line:  N/A ? Runtime:  t

a:  Displays  ASM diskgroup information.  (no op for non-ASM)

Default: N/A

? Command line:  N/A ? Runtime:  a

x:  Displays SQL execution plan table.  Requires input of the active SQL sql_id value.

Default: N/A

? Command line:  N/A ? Runtime:  x

i :   Interval delay time. ( requires value in seconds)

Specifies the delay between update refresh.  A short interval delay (<10s) is not guaranteed  for the specified delay.  This is particularly true for a loaded system. 

Default: 5 seconds.

To override the default value

? Command line:  -i < number in seconds> ? Runtime:  i

v :  oratop version number.

Displays version number

Default: N/A

? Command line:  -v ? Runtime:  N/A

h :  Help.

Displays usage or output information.

Default: N/A

? Command line:  -h[elp]

? Runtime:  h

II.  INTERACTIVE MODE

Runtime interactive and detail options can be seen after starting the utility followed by pressing the keyboard key ‘h’.  (See Figure 3)

Figure 3. Runtime Options using help

1.  Interactive Toggle keys

      1.1.       [ d ]  - Section 3 “DB EVENTS” Cumulative( C)/ Real-Time (R/T) modes

See header starting with “EVENT (c)” in Figure 4 below.

Figure 4. Runtime toggle Option ‘d’ (Cumulative/ Real-Time)

      1.2.       [ k ]  - Section 4 Process “EVENT/*LATCH “ and “FILE#:BLK#” columns

Figure 5 below shows column toggling in section 4 when keyboard key “k” is pressed.

Figure 5. Runtime switch Option ‘k’ (process,“& 

 

             
 

        

         

 

            

  

 



    >

    

              

 
 

              

                                                       

>

                                                

                          

         

       

                 

                                                       

 >

 

 

>

 

            

                 

             
 

 

 

 
 

 

 

  

 

  

 

 

 

 

 
    

 

 
   

 

 

 

 

           

    

     

          

<><>

 

    

 

 

   

            

        

        

 

      

      

      

      

      

 

 

  

 

 

 

 

 

 

    
时间： 2024-10-22 09:11:13

Oratop工具——实时数据库性能监控工具的相关文章

现代网络性能监控工具应具备何种技能？

以前,企业网络工程师不得不为各种连接的服务器.应用程序和终端设备提供网络接入和足够的带宽.从OSI模型角度看,这些工具主要关注于1-4层网络.由于通过一个网络的所有流量和数据流都共享全部的带宽和队列资源,更高的OSI层次多少被忽略了. 慢慢地,网络设备变得越来越复杂,现在网络中不同的数据流都可以被识别出来并区别对待.各种服务质量(QoS)和应用层流程成型技术也可用于实现这个目 标.此外,随着对于关键业务应用程序依赖程度越来越高,网络工程师也迫切需要了解OSI模型的更高层次,这样他们才能发现网络.

你值得拥有 —— 25 个 Linux 性能监控工具

你值得拥有 -- 25 个 Linux 性能监控工具 一段时间以来,我们在网上向读者介绍了如何为Linux以及类Linux操作系统配置多种不同的性能监控工具.在这篇文章中我们将罗列一系列使用最频繁的性能监控工具,并对介绍到的每一个工具提供了相应的简介链接,大致将其划分为两类,基于命令行的和提供图形化接口的. 基于命令行的性能监控工具 1. dstat - 多类型资源统计工具 该命令整合了vmstat,iostat和ifstat三种命令.同时增加了新的特性和功能可以让你能及时看到各种的资源使用情况

mysql性能监控工具Innotop简介及配置_Mysql

1.innotop安装 参考官网:http://innotop.googlecode.com/svn/html/installing.html # wget http://innotop.googlecode.com/files/innotop-1.9.0.tar.gz # tar -zxvf innotop-1.9.0.tar.gz # cd innotop-1.9.0 安装INNOTOP工具非常简单,其是由PERL写的,当然需要PERL环境和相关的工具包.在安装之前先要确定你的系统安装了Ti

对应用性能监控工具APM该有怎样的期待？

由于没有有效的性能管理,应用遭遇响应时间延迟,这让顾客愤怒不已,还破坏雇员的生产积极性.试错法排除故障以及可见性低导致断电.这都引发关键业务功能长时间无法使用,中断了销售与生产周期. 内部性能管理工具赶不上运行着的业务应用的步伐.诸如企业资源规划这样复杂的应用,可能添加多个层,诸如云计算接口这样的新软件类型为了维持性能,每年的存储增长超过50%.这些更改使得应用性能监控与管理APM更加困难. 有些IT企业或它们服务的业务,低估了对于有效APM的需求,或者对增加应用性能复杂性的效果感到失望.  

采用云性能监控工具消除IT的盲点

使用公共云并不意味着企业必须牺牲应用程序和工作负载性能的可见性.使用正确的工具集可以给IT一个更全面的场景. 公共云已经成为许多企业IT计划的关键要素.越来越多的企业将他们的应用程序交付给公共云提供商,如亚马逊网络服务公司(AWS)和微软Azure.尽管IT专业人士经常将安全性视为将应用程序保留在内部部署的数据中心的原因,但是性能监控可能是另一个原因,因为组织在业务异地迁移时难以保持可见性.然而,公共云性能监控工具可以帮助克服这些挑战. IT性能监控涉及到通常难以衡量的复杂的交互网络.在私有和公

分析下自己写的SQL Server同步工具的性能和缺陷

分析下自己写的SQL Server同步工具的性能和缺陷 1. C#同步SQL Server数据库Schema 2. C#同步SQL Server数据库中的数据--数据库同步工具[同步新数据]   通过测试我写的同步程序,得出结论: 1.程序第一次调用SQLBulkCopy会耗时较长 2.同步程序放在目标机器在耗时方面相对少些 测试数据: declare @varI varchar(200) set @varI=0 while(@varI<100000) begin set @varI=@varI

Linux Sysstat性能监控工具安装及常见8个命令使用例子

Sysstat,一种常用在Linux系统服务器中的软件工具包,可以用来监控服务器的性能.比如可以监控CPU.硬盘.网络等数据,我们可以用来进行分析服务器的性能和资源的使用效率.老左将在这篇文章中学习.整理Sysstat监控工具包的安装和常用的使用命令.   老左之前并没有使用过这些工具(要学习和基础的知识太多),在这篇文章中就简单的记录Sysstat安装过程和常用的几个命令,同类的软件和工具还是有很多的,具体要根据我们的熟悉和喜欢,以及是否真的需要然后再去选择.   第一.Sysstat工具的安

PHP ~与各加速工具的性能对比~

Xcache简介   前面已经介绍了PHP加速器的原理和功用(参见LAMP架构之PHP-FPM 服务器),xcache作为目前使用广泛的PHP加速器之一,其性能比早期的eAccelerator加速器要优良,故本次就对比一下PHP程序在执行时加速器xcache对其的性能影响.       安装xcache   复制代码 # 安装 tar xf xcache-3.0.3.tar.gz cd xcache-3.0.3 /usr/local/php/bin/phpize # xcache是作为php的外

TestMaker 6.1发布 性能监控工具

TestMaker 6.1此版本添加了Flex 4的支持,Oracle Forms和Java http://www.aliyun.com/zixun/aggregation/5541.html">Applet的支持,新的Results Analysis Charts,包括表格视图,资源监测和交易细节,简单的SSL证书管理,Linux兼容性和MySQL库支持. TestMaker不单单的是完整的测试平台,也是性能监控的工具,它是一个分布式的自动化测试平台,主要对应用程序的性能进行管理和监控.