So this kind of deadlock event monitor should be used with caution.
所以应该谨慎使用。
The answer is that lock timeout reporting builds partly on functionality delivered by deadlock event monitor code.
答案是构建锁定超时报告需要用到死锁事件监视器代码交付的功能。
When a deadlock event monitor is created with the DETAILS HISTORY option, DB2 keeps track of the SQL statements already executed in a transaction.
使用DETAILSHISTORY选项创建死锁事件监视器时，DB 2跟踪已经在事务中执行的sql语句。
If you leave the event condition for event type statement field empty, the DB2 statement event monitor is started for the whole monitored database.
如果让eventconditionfor eventtypestatement框空着，就对整个数据库启动db2语句事件监视器。
A deadlock event monitor with statement history capabilities affects all applications and increases the monitor heap usage by the DB2 database manager.
带有语句历史功能的死锁事件监视器适用于所有应用程序，会增加DB 2数据库管理程序对监视器堆的大量使用。
Note that the event monitor information is very detailed, and it will quickly grow in size if many fast SQL statements are executed in a short time.
注意，事件监视器信息十分详细，如果短时间内执行了许多快速的sql语句，那么事件监视器的信息量就会快速增长。
Because this event monitor causes a lot of overhead on the monitored instance, these processes to create SQL reports should be started with consideration.
因为这个事件监视器会给监视的实例带来很大开销，所以在启动创建SQL报告的过程时要仔细考虑。
You should always start by setting only DB2_CAPTURE_LOCKTIMEOUT=ON, and activate a deadlock event monitor with the DETAILS HISTORY option only if required.
您应该始终首先设置 DB2_CAPTURE_LOCKTIMEOUT=ON，然后只在必要的时候使用DETAILSHISTORY选项激活死锁事件监视器。
To format the data about the deadlock event that the lock event monitor collects and write it to a plain text file, call the db2evmonfmt utility again.
为了格式化锁事件监控器收集的死锁事件数据，并将其写到普通文本文件中，再次调用db 2evmonfmt工具。
It reads the SQL statements executed from the event monitor tables and runs the Explain utility for each statement to generate the corresponding access plan.
它将读取从事件监控器表执行的sql语句，然后对每个语句运行Explain实用程序以生成对应的访问计划。
There are two primary tools, each serving a different purpose, with which you can access database monitor information: the snapshot monitor and event monitors.
有两个主要工具，用途不一，有了它们您就可以访问数据库监控信息：快照监控器和事件监控器。
If you want to start the event monitor only for specific applications, specify an event condition in the CREATE event monitor statement syntax shown in Figure 30.
如果希望只为特定的应用程序启动事件监视器，那么用CREATEEVENT monitor语句语法指定事件条件，见图30。
It showed, by example, how you can use the lock event monitor to collect information about any kind of concurrency issue: deadlocks, lock-timeouts, and lock-waits.
本文通过实例演示了如何使用锁事件监控器来收集所有种类的并发性问题：死锁、锁超时及锁等待。
Click the Options TAB, and specify the database, the partition you are interested in, and the elapsed time the DB2 statement event monitor should run to collect data.
单击options选项卡，指定数据库、感兴趣的分区和db2语句事件监视器应该运行的时间。
You would use the Queries process if for a multi-partition monitored instance for which you want to collect SQL event monitor data for multiple partitions simultaneously.
对于多分区实例，可以使用查询过程同时收集多个分区的SQL事件监视器数据。
Before turning on the event monitor, you can set up the profiler to include optional event monitor elements by choosing optional elements. These optional elements include.
打开事件监视器之前，您可以设置概要分析器(profiler)，通过选择可选元素来包含可选的事件监视器元素。
The SQL baseline must be captured during the test and not after, as done for the reports on aggregated data, because a DB2 statement event monitor is started to capture the data.
必须在测试期间捕捉SQL基线，而不是像聚合数据报告那样在测试之后捕捉，这是因为要启动db2语句事件监视器来捕捉数据。
Use the database system monitor to help you tune this configuration parameter using information from the snapshot data (or event monitor) about write activity from a buffer pool.
使用数据库系统监视器，利用有关从缓冲池进行写操作的快照数据(或事件监视器)信息来帮助您调优该配置参数。
This article has shown a procedure that you can use to automatically generate table functions that report event monitor elements captured as an XML document in a relational format.
本文已经显示了一个过程，您可以使用该过程自动生成表函数，其以关系格式报告以XML文档形式捕获的事件监控器元素。
In IBM DB2 9.7, both the activity and statistics event monitors have a DETAILS_XML monitor element that stores an XML document which contains a wealth of activity and system metrics.
在IBMDB 2 9.7中，活动和统计事件监控器都具有DETAILS_XML监控器元素，该元素存储包含大量活动和系统指标的XML文档。
This invocation will create an activity event monitor and collect detailed activity information including section explain and section actuals for the specified query in badquery.sql.
这个调用会创建一个活动事件监视器，并收集详细的活动信息，包括在 badquery.sql 中指定的片段解释和片段实绩。
Performance Warehouse saves historical monitoring data consisting of DB2 snapshot data, DB2 event monitor data, and configuration data over a long period of time (long-term history).
PerformanceWarehouse保存的历史监控数据由较长时间的(长期历史)DB 2快照数据、DB2事件监控数据和配置数据组成。
If the test you want to take a baseline on is running at night, you can schedule the report generation and the collection of SQL event monitor data by the DB2 statement event monitor.
如果要建立基线的测试在夜间运行，那么可以调度db2语句事件监视器对SQL事件监视器数据的收集和报告生成过程。
The event monitor converts the configuration information and the event data retrieved from the event queue table into a self-describing event message in a common base event (CBE) format.
这个事件监视器能将配置信息和从事件队列表所查询的事件数据转换到一个自解释的通用基础事件(CBE)格式事件消息中。
The option to turn on the SQL Statement event monitor is not practical because of the overheard involved and the potential performance penalty a high transaction environment could incur.
用于打开SQL语句事件监视器的选项并不实用，由于涉及的开销和潜在的性能损失，会导致一个高事务环境。
The event monitor fetches event data from the event queue table based on the configuration data, converts the events into JMS messages, and puts the JMS messages on a JMS event queue.
事件监视器能根据配置数据从事件队列表取出事件数据，将事件转换成JMS消息，然后将 JMS 消息放回到一个 JMS 事件队列中。
A user name and password for a user who has sufficient privileges to start and operate a statement event monitor as well as to create a schema where the SQL Profiler holds its local data.
某用户的用户名和口令，该用户拥有足够的权限启动和操作语句事件监视器，以及创建模式，而SQLProfiler将在该模式中保存其本地数据。
One common usage of event monitor in the MDM Server environment is deadlock event monitoring to understand and resolve excessive deadlocks that sometimes happen in an MDM Server database.
MDMServer环境中事件监控器的一个常见用途是死锁事件监控，用于了解和解决 MDM Server 数据库中偶尔发生的过度死锁（excessive deadlocks）。
If you use the long-term history, start a DB2 statement event monitor to collect SQL event monitor data and to store the collected data in the performance database of the performance Expert server.
如果使用长期历史，可以启动db2语句事件监视器来收集SQL事件监视器数据，并把收集的数据存储到PerformanceExpert服务器的性能数据库中。
Memory is allocated from the monitor heap when you perform database monitoring activities such as taking a snapshot, turning on a monitor switch, resetting a monitor, or activating an event monitor.
当执行数据库监视活动时，将从监视堆分配内存，这些活动包括拍摄快照、打开监视器开关、重置监视器或激活一个事件监视器。
应用推荐