日志缓冲区满了。
It is the parameter for the log buffer.
它是用于日志缓冲区的参数。
Increase the log buffer size to 256 pages or larger.
将日志缓冲区大小增加到256个页面或更大。
A record reflecting the insert is written to the log buffer.
将反映该insert的一条记录写入到日志缓冲区中。
For non-persistent events and actions, tune the log buffer sizes.
对于非持久化事件和动作，调优调优日志缓存大小。
The log buffer size is defined by the LOGBUFSZ database parameter.
日志缓冲区大小是由LOGBUFSZ数据库参数定义的。
Log records are appended to the end of the used part of the log buffer.
日志记录追加到日志缓冲区中已使用的部分的尾部。
Access to the log buffer is provided at the core through the multi-purpose syslog system call.
多用途的syslog系统调用提供了内核的日志缓冲区访问方法。
The database configuration parameter that defines the size of the log buffer is called LOGBUFSZ.
定义日志缓冲区大小的数据库配置参数为LOGBUFSZ。
The log Buffer is the amount of main memory used to accumulate log records that will be written out to disk.
日志缓冲区是用于存放将要写入磁盘中的日志记录的主存量。
It is important that the log buffer be able to hold the amount of log space used by an average transaction.
使日志缓冲区可以容纳一般事务所使用的日志空间总量是很重要的。
If you wish to change the size of the log buffer for the queue manager you will need to change the value in the registry.
如果您希望更改队列管理器的日志缓冲区大小，将需要在注册表中更改此值。
The default size of the log buffer (LOGBUFSZ) below is normally too small for database systems with many update workloads.
对于具有许多更新工作负载的数据库系统而言，下面日志缓冲区的默认大小(LOGBUFSZ)通常都太小。
Transactions requiring disk I/O, such as flushing dirty pages from the buffer pool or flushing logs from the log buffer, may wait.
要求磁盘I/O 的事务，例如刷新缓冲池中的脏页或者刷新日志缓冲区中的日志，可能需要等待。
Increase the size of the log buffer area if there is considerable read activity on a dedicated log disk, or there is high disk utilization.
如果在某个专用的日志磁盘上存在大量的读活动，或者具有较高的磁盘利用率，就增加日志缓冲区域的大小。
If you wish to change the size of the log buffer for the queue manager you will need to change the value in the queue manager qm.ini file.
如果您希望更改队列管理器的日志缓冲区大小，将需要在队列管理器qm . ini文件中更改此值。
Log records are written first to the log buffer in memory, and then to the log file, most commonly when the log buffer is full or a commit occurs.
日志记录首先被写到内存中的日志缓冲池，然后再写到日志文件，通常是在日志缓冲池已满或者发生了一次提交时写到日志文件的。
The log buffer acts as a staging area in memory to hold log records instead of having the DB2 UDB engine write each log record directly to disk.
日志缓冲区作为内存中的分级区域（staging area）来保存日志记录，而不是让DB2UDB引擎直接将每条日志记录写入磁盘中。
For example, the log buffer writes each transaction to logs and how different log mode can be used to accomplished different modes of backup and recovery.
例如，日志缓冲区将每个事务写到日志，可以使用不同的日志模式来实现不同的备份和恢复模式。
When increasing the value of this parameter, consider the DBHEAP parameter, too, because the log buffer area USES space controlled by the DBHEAP parameter.
当增加这个参数的值时，也要考虑DBHEAP参数，因为日志缓冲区使用的空间由DBHEAP参数所控制。
When increasing the value of the LOGBUFSZ parameter, you should also consider the DBHEAP parameter since the log buffer USES space from the database heap area.
在增加LOGBUFSZ参数的值时，您还应该考虑DBHEAP参数，因为日志缓冲区使用来自数据库堆区域中的空间。
The transaction containing the insert is (eventually) committed, at which point the log buffer record(s) are written to the log disk if they haven't already been.
最后提交包含该insert的事务，如果这时日志缓冲区中的记录还没有被写入日志文件的话，则将这些记录写到日志文件中。
The log buffer holds log records in storage until they are written to hard disk drive. Log records are written to the hard disk drive when one of the following occurs.
日志缓冲区将容纳存储器中的日志记录，直到它们被写回硬盘驱动器。
The choice of buffer size can greatly affect performance when auditing is started since many records may be written to the audit log.
缓冲区大小的选择将在很大程度上影响审计的性能，因为可能要将很多记录写到审计日志中。
Thus, the read operations compete with log writing and the write operation for data pages from the buffer pool.
因而，读操作与日志写和缓冲池中的数据页的写操作之间存在竞争。
The downside of a larger log buffer is that crash recovery can take slightly longer.
较大日志缓冲池的不利之处是，紧急事故恢复所花的时间可能要稍微长一点。
Primary in to files in the staging directory. It immediately acknowledges receipt of the log data buffer to the primary before it actually applies or stages it.
主要服务器将使用暂存目录中的文件，并在实际应用或暂存将保存到主要服务器的日志数据缓存之前，应立即识别对它的接收。
What essentially we can get away with is that log buffer located in database shared memory is the mechanism provided to ensure each transaction is logged to log files.
注意，日志缓冲区位于数据库的共享内存中，这种机制确保每个事务被记录到日志文件中。
But the small buffer size makes it unsuitable for larger quantities of log information, and the logged information isn't stored to disk so it's hard to analyze over a period of time.
但是缓冲区尺寸小造成它不适合更大数量的日志信息，而且记录的信息不能保存到磁盘也使得难以分析一段时间内的性能。
Set the catalog cache, package cache, and log buffer size to an appropriate size to improve performance.
要设置大小适当的目录缓存器、包缓存器和日志缓冲区以提高性能。
应用推荐