Trace buffer doesn't save top of stack or contents of memory referenced by registers.
跟踪缓冲区并不保存栈顶或由寄存器所指向的内存的内容。
Trace commands mentioned at the beginning of this topic automatically open trace buffer.
在这个话题的开始提到的跟踪命令自动打开跟踪缓冲区。
The trace buffer has not been set large enough to hold a complete set of relevant trace events.
跟踪缓冲区设置得不够大，不足以容纳一组完整的相关跟踪事件。
If you are tracing to Shared memory, the size of the trace buffer controls the size of the dump file.
如果是在跟踪共享内存，跟踪缓冲区的大小将控制转储文件的大小。
For performance reasons, the trace facility does not allow you to change the trace buffer size dynamically.
由于性能的原因，跟踪功能不允许动态更改跟踪缓冲区的大小。
The default size for each trace buffer is five Megabytes, but this can be overridden when you run the Tprof tool.
每个追踪缓冲区默认的大小是5MB，不过，当您运行Tprof工具时可以覆盖这一默认值。
Notice that displayed count is dynamical and doesn't account for the old commands discarded from the trace buffer.
注意显示出来的数字是动态的，而且不对已经从跟踪缓冲区中丢弃的指令镜像。
The default and minimum trace buffer sizes depend on the version of DB2, and the maximum trace buffer size depends on the platform.
缓冲区的默认大小和最小值取决于DB2的版本，跟踪缓冲区的最大值取决于平台。
As expected, the dump file (DMP) is approximately 8 MB in size, corresponding to the trace buffer size that was specified on the db2trc command.
与预期一样，转储文件(dmp)大小约为8MB，跟db 2trc命令中指定的缓冲区大小相符。
This collection option stops tracing on demand; all processes suspend tracing, but the contents of the trace buffer are preserved so that they can be dumped later.
这是一个收集选项，它根据需要停止跟踪。这时，所有进程都挂起跟踪，但跟踪缓冲区的内容被保存起来，以便以后转储到文件中。
Collection options include turning a trace on or off; specifying the trace buffer size; specifying or changing trace options; dumping a trace; and clearing the trace buffer.
收集选项包括打开或关闭跟踪；指定跟踪缓冲区大小；指定或更改跟踪选项；转储跟踪信息；以及清除跟踪缓冲区。
With different trace levels set for various registrations, the influx of data into the buffer also depends on the amount of activity in each connection being traced.
通过为各种不同注册设置不同跟踪等级，数据进入缓冲区还依赖于在每个被跟踪的连接中的活动数量。
You can write trace data to a file continuously as an extension to the in-storage trace, but instead of one buffer per thread, at least two buffers per thread are allocated.
可以连续地将跟踪数据写到文件中，作为存储内跟踪的扩展；但是在这种情况下不是为每个线程分配一个缓冲区，而是至少分配两个。
This 8mb buffer holds over 40,000 trace records that can be useful in diagnosing system and transaction work related to optimized local adapter requests.
这个8MB的缓冲区存放超过40,000条跟踪记录，可用于诊断系统和有关优化的本地适配器请求的事务工作。
Depending on trace volume, buffer size, and the bandwidth of the output device, multiple buffers might be allocated to a given thread to keep pace with trace data that is being generated.
根据跟踪量、缓冲区大小和输出设备的带宽，可以将多个缓冲区分配给给定的线程，从而与生成跟踪数据的速度相匹配。
The verbose trace will display data from the parameters of system calls (-x all) and the contents of the buffer for both Read (-r all) and Write (-w all) calls.
详细的跟踪会显示来自系统调用参数的数据(- x all)以及Read (- r all)和Write (- w all)调用的缓冲区的内容。
You might instinctively conclude that setting a more detailed trace level will generate more records and cause the buffer to wrap more quickly.
您可能会本能地断定设置更详细的跟踪等级将生成更多的记录并导致缓冲区得到更快的包装。
In this case, we will trace only the buffer pool services component.
在本例中，我们将只跟踪缓冲池服务组件。
In this case, we will trace only the buffer pool services component.
在本例中，我们将只跟踪缓冲池服务组件。
应用推荐