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工具时可以覆盖这一默认值。
The default and minimum trace buffer sizes depend on the version of DB2, and the maximum trace buffer size depends on the platform.
缓冲区的默认大小和最小值取决于DB2的版本，跟踪缓冲区的最大值取决于平台。
Trace commands mentioned at the beginning of this topic automatically open trace buffer.
在这个话题的开始提到的跟踪命令自动打开跟踪缓冲区。
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.
收集选项包括打开或关闭跟踪；指定跟踪缓冲区大小；指定或更改跟踪选项；转储跟踪信息；以及清除跟踪缓冲区。
Trace buffer doesn't save top of stack or contents of memory referenced by registers.
跟踪缓冲区并不保存栈顶或由寄存器所指向的内存的内容。
Trace buffer doesn't save top of stack or contents of memory referenced by registers.
跟踪缓冲区并不保存栈顶或由寄存器所指向的内存的内容。
应用推荐