The primary log size is 1024 4kb pages.
主日志大小为1024个4kb的页面。
This is the primary log used by mashup feed builder and feed creation tools.
这是mashupfeed构建器和feed创建工具使用的主要日志。
A primary log, whether empty or full, requires the same amount of disk space.
无论主日志是空的还是满的，所需的磁盘空间量都是相同的。
Primary log files establish a fixed amount of storage allocated to the recovery log files.
主日志文件建立了一个固定大小的存储空间，这是分配给恢复日志文件的。
The database configuration parameter LOGPRIMARY determines the number of primary log files.
数据库配置参数LOGPRIMARY决定了主日志文件的数量。
The size (number of pages) of each primary log has a direct bearing on database performance.
每个主日志的大小(页数量)对数据库性能有直接影响。
A transaction runs and USES up all five primary log files but is still logging transactions.
事务正在运行，并用完所有五个主日志文件，但仍将记录事务。
However, during a long running transaction, a log full situation may occur, where all the primary logs are active.
但在长期运行的事务期间，可能发生日志已满的情形，在这种情形中，主要日志是活动的。
The minimum number of primary log files you can have is 2 and the maximum is 254 on Windows, or 510 on UNIX systems.
可配置的最小主日志文件个数为2，其最大数目在Windows 上为 254，而在UNIX 系统上为 510 个。
The default number of primary logs files (LOGPRIMARY) is defined as 3, and the number of secondary log files (LOGSECOND) as 2.
主日志文件(LOGPRIMARY)的默认数量是定义为3，而次日志文件(LOGSECOND)则为2。
When the database is initialized, the system allocates a certain number of primary log files of a specified size in the active log directory.
当初始化数据库时，系统会在活动日志目录中分配一定数量、指定大小的主日志文件。
When the primary log files are all full, secondary log files are created on an "as-needed" basis until the maximum number of secondary log files has been created.
当主日志文件都写满时，就会“根据需要”创建辅助日志文件，直到创建了最大数量的辅助日志文件为止。
Secondary log files are allocated one at a time as needed, up to the value of the database configuration parameter LOGSECOND, when the primary log files become full.
当主日志文件用完时，次日志文件会一次按需分配完毕的，最大可分配数据库配置参数LOGSECOND 所指定的值。
This means that upon first connection to the database, the total number of primary logs is equal to the total number of log files residing in the active log directory.
这表示在第一次连接到数据库时，主日志的总数等于驻留在活动日志目录中的日志文件的总数。
In this strategy, once the last primary log file is filled in the log directory, new transactions will be written to the first log file thereby overwriting existing log data.
在此策略中，一旦日志目录中最后一个主日志文件被写满了，就会将新的事务写到第一个日志文件中，从而覆盖现有的日志数据。
When the primary log files become full, the secondary log files (of size logfilsiz) are allocated one at a time as needed, up to a maximum number as controlled by this parameter.
当主日志文件满了时，就会按需要每次分配一个辅助日志文件（大小为logfilsiz），最多达到由该参数控制的最大数量。
To keep a synchronized copy of the database on the standby server, DB2 HADR log files are consistently sent from the primary to the standby to keep the two in sync.
为了在备用服务器上保持数据库的一个同步副本，系统会一致地将DB 2HADR日志文件从主要服务器发送到备用服务器来保持二者的同步。
Once a checkpoint is transferred to the RSS node, it will start staging the log records coming from the primary in a log staging area at RS secondary server.
一旦将检查点传输给rss节点，它会开始将来自主要服务器的日志记录暂存到RS次要服务器上的日志暂存区域中。
Here, log 4 and log 5 that are coming from primary server are staged at RS secondary server.
在这里，来自主要服务器的日志4与日志5都暂存在RS次要服务器上。
The below diagram represents primary and HDR secondary nodes, and steps of working log staging during checkpoint.
下图展示了主要服务器与HDR次要节点，以及日志暂存在检查点期间的工作步骤。
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.
主要服务器将使用暂存目录中的文件，并在实际应用或暂存将保存到主要服务器的日志数据缓存之前，应立即识别对它的接收。
When the server is unblocked, staged logical log files from primary server at RS secondary server are automatically removed after being applied.
解除服务器的阻塞时，将在应用RS次要服务器上来自主要服务器的已暂存逻辑日志文件之后自动删除它。
This time, log in by using the Primary administrative user name (Server user ID) that you entered previously in the WebSphere Application Server configuration section.
这时，通过使用您之前在WebSphere应用程序服务器配置一章中输入的主管理用户名(服务器用户ID)进行登录。
Using the automatic option requires you to specify primary archive log path and fail archive log path.
使用自动选项时要求指定主存档日志路径和故障转移存档日志路径。
The log write at the primary and the send to the standby are performed in parallel on the primary server.
主服务器的日志写入和对于备用服务器的发送在主服务器上是并行执行的。
As in HDR, the primary server sends all its logical log records to the RS secondary server continuously, except now only in an asynchronous manner.
如同在HDR中一样，主服务器不断将其所有的逻辑日志记录发送给RS备用服务器，不过RS使用的异步方式。
The DB2 server would automatically relay log changes from primary to its stand-by server.
DB 2服务器会自动将日志变更从主服务器传递给备用服务器。
Running at both sites are log-capture and apply programs, but in this simplified scenario, data is only replicating one way — from primary to standby.
两个站点均运行日志捕捉和应用程序，但在这个经过简化的场景中，数据仅进行单向复制，即从主站点复制到备用站点。
The standby system does not write the log until it hears from the primary that that the same log is on disk there.
而备用服务器直到从主服务器收到消息，得知它磁盘上具有相同的日志，才写入该日志。
Once the staged logical log records are applied, it continues to resume applying the log records as soon as they are received from the primary.
一旦应用暂存的逻辑日志，只要从主要服务器接收到日志记录，就可以立即恢复应用日志记录。
应用推荐