When a table has been reorganized with the reorg utility.
当用REORG实用程序重新组织表时。
At last, a true low-overhead online table reorg capability.
最后，一个真正的低开销在线表格重组功能。
Here are a few things to keep in mind when using partition-level reorg.
在使用分区级别REORG时，要注意以下几个问题。
Before you apply new stats to the database, I recommend you reorg the data first.
在您将新语句应用到数据库之前，我建议您首先重新组织数据。
While the reorg operation is running, execute the following script from another session.
在执行重组操作时，从另一会话执行下列脚本。
In most cases, ALTER SET DATA TYPE requires table reorganization (reorg) because it changes the physical row format.
大多数情况下，ALTERSETDATATYPE需要对表执行重组(reorg)，因为它修改了物理行格式。
Each of these operations: redistribute, table reorg, index create, and runstats require scanning the table data once.
这些操作中：redistribute、table reorg、indexcreate和runstats，每个操作都需要扫描一次表数据。
If you use the offline table reorg or rowcompestimate option in the inspect tool, data in the table is fully compressed.
如果在inspect工具中使用离线table reorg或rowcompestimate选项，则表中的数据将被完全压缩。
Compact on is the default for the redistribute utility, where it performs space compaction much like an offline table reorg does.
COMPACTON是重分发实用程序的默认选项，它像离线table reorg那样执行空间压缩。
In addition, maintenance commands such as reorg and rebind are also included to restore the state of the database after command deployment.
此外，还包括reorg和rebind等维护命令，用于在命令部署后恢复数据库的状态。
With the data returned, you can make a decision on whether you would like to perform an offline table reorg to take advantage of row compression.
利用返回的数据，可以决定是否执行离线table reorg，以利用行压缩。
You can do additional database management, such as performing a reorg on Tivoli Enterprise Console tables, when the tables undergo numerous changes.
还可以进行其他数据库管理，如在对表进行了大量更改时对TivoliEnterpriseconsole表执行reorg命令。
The "Reorg recommended" column identifies the data type alterations that require table reorganization before a table can again be accessed (SQLSTATE 57016).
“需要重组”列表示这种数据类型修改是否要求在访问表之前进行表重组（SQLSTATE 57016）。
The following REORG example reorganizes the customer table using the system temporary tablespace TEMPSAPCE1 as a work area to store the intermediate results.
下列 REORG示例重新组织客户表，并使用系统临时表空间 TEMPSAPCE1作为工作区域以存储中间结果。
When reorganizing XML indexes, database administrators can use the allow write ACCESS clause in the reorg indexes command to allow concurrent writes on the table.
在重组xml索引时，数据库管理员可以通过在REORGINDEXES命令中使用ALLOWWRITEaccess子句允许并发的写操作。
This provided some improvement on the table reorg problem, because you could use these options to perform a partial reorganization in the background without taking the table offline.
这为表重组问题提供了一些改进，因为您可以使用这些选项来在后台执行一个部分重组，而不需要让表处于脱机状态。
Generally, after a redistribution of a database partition group, you need to perform an offline table reorg, index recreation (if necessary), and runstats on the redistributed table.
通常，在数据库分区组重分发之后，需要在重分发的表上执行离线的table reorg、indexrecreation(必要时)和runstats。
In typical warehouse environments, recent data changes frequently while historical data is more or less static and this makes partition level reorg invaluable for reorganizing only the active data.
在典型的数据仓库环境中，最新的数据变化频繁，而历史数据变化相对较小，这使得分区级别的REORG对于针对活动数据的重组尤为重要。
They can increase logging during the REORG process.
会在REORG过程中增加日志。
The REORG USES a sampling technique to build the dictionary.
REORG使用一种抽样技术来建立字典。
The dictionary gets updated for every subsequent REORG operation.
在随后的每次REORG操作中，表字典随之更新。
A third problem can occur when performing RUNSTATS or REORG on your table.
当对表执行RUNSTATS或REORG时，可能出现第三个问题。
The REORG TABLE step between two scenarios will establish the clustering order.
两个场景之间的REORGTABLE步骤将建立聚集顺序。
Both the RUNSTATS and REORG utilities use log files when moving table data around.
当到处移动表数据时，RUNSTATS和REORG实用程序都使用日志文件。
Use this utility after massive changes to the data and possibly after running REORG.
大量更改数据之后或运行REORG之后使用该实用程序。
Extra indexes also add to the CPU consumption of certain DB2 utilities, such as the REORG utility.
额外索引还会增加某些DB2实用工具（比如 REORG 实用工具）的CPU 占用。
This is also why maintenance operations like REORG cannot be performed on an individual local index.
这也是无法对单个本地索引执行类似 REORG维护操作的原因。
REORG will restore a disorganized index to a well-organized state, at a cost of some CPU consumption.
REORG将把一个组织混乱的索引恢复为良好组织状态，但要以一些CPU消耗为代价。
Based on the data and trends you observe, adjust your REORG frequency and PCTFREE number accordingly.
根据当前的数据以及您所观察到的趋势，对REORG的频率和PCTFREE的数字进行相应的调整。
In DB2 9, the default compression dictionary directive for the REORG TABLE command is KEEPDICTIONARY.
在DB 29中，REORGTABLE命令中的默认压缩字典指令是KEEPDICTIONARY。
应用推荐