The REORG TABLE step between two scenarios will establish the clustering order.
两个场景之间的REORG TABLE步骤将建立聚集顺序。
In DB2 9, the default compression dictionary directive for the REORG TABLE command is KEEPDICTIONARY.
在DB 29中，REORG TABLE命令中的默认压缩字典指令是KEEPDICTIONARY。
Reorg in Progress 0x400 This is a transient state that is only in effect during a reorg operation. Issue a reorg TABLE command.
reorginProgress0x400这是一种只在进行重组(reorg)操作期间才有效的临时状态。
However, it is not so easy for spatial data given that the DB2 REORG TABLE command does not understand spatial indexes due to their complex nature.
然而，如果由于空间索引的复杂性质导致DB 2 REORG TABLE命令不理解空间索引，事情就不会那么容易了。
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作为工作区域以存储中间结果。
This differs from global indexes where each global index has its own object, allowing greater flexibility in table space placement and support for REORG for an individual global index.
这不同于全局索引，每个全局索引有自己的对象，其提供灵活的表空间定位能力，并支持单个全局索引REORG操作。
Because new rows are inserted in the part of the table that contains rows with similar values, data remains clustered without the need to run the REORG utility.
由于新行是插在表中具有近似值的行附近的位置，因此数据仍然是聚合的，而不需要运行REORG实用程序。
Therefore, REORG usually produces a dictionary that is more representative of the data in the entire table space or partition.
因此，REORG常常可以产生更能代表整个表空间或分区中的数据的字典。
In the case of the SIBOWNER table, there's only a single row, so there's no "related data" to try and place close together; it should be relatively apparent why no reorg is required.
在sibowner表的情况下，由于只有单个行，因此不存在需要试验和紧密放在一起的“相关数据”；不需要重组的原因应该是相对明显的。
In DB2 9.1, the compression takes effect only after the table dictionary is built, which is usually during the table REORG phase.
在DB 2 9.1中，只有在建立了表字典之后(表字典通常是在表reorg阶段建立的)，压缩才能生效。
At last, a true low-overhead online table reorg capability.
最后，一个真正的低开销在线表格重组功能。
The "Reorg recommended" column identifies the data type alterations that require table reorganization before a table can again be accessed (SQLSTATE 57016).
“需要重组”列表示这种数据类型修改是否要求在访问表之前进行表重组（SQLSTATE 57016）。
If a table is dropped, its segments become immediately available for reuse at the COMMIT point, without requiring the REORG utility to be executed.
如果一个表被删除，在执行COMMIT之际，它的段就立即可以为其他表所用，而不需要执行REORG实用程序。
The table dictionary is built only when a REORG is performed, after which the data in the table can be compressed.
只有在执行 REORG 的时候才构建表字典，之后便可以压缩表中的数据。
When a table has been reorganized with the reorg utility.
当用REORG实用程序重新组织表时。
The following examples illustrate partition-level REORG on a table that has no global indexes.
以下例子阐明了如何在不含全局索引的表上应用分区级别reorg ？
Both the RUNSTATS and REORG utilities use log files when moving table data around.
当到处移动表数据时，RUNSTATS和REORG实用程序都使用日志文件。
All kinds of DB2 catalog statistics describe the table space condition, and IBM suggests thresholds as to when the REORG should occur. There are many downsides to reorgs.
各种DB 2目录统计信息都描述了表空间状况，IBM建议以REORG会出现的情况作为阈值。
The following REORGCHK command examines whether the REORG is required and also updates the statistics on table bench.customer.
下列REORGCHK命令检查是否需要REORG，并且更新关于表bench .customer的统计信息。
This is accomplished by specifying the COMPRESS YES option in the CREATE TABLESPACE statement, and then executing either the LOAD or REORG utility on the table space.
这是通过在CREATEtablespace语句中指定COMPRESSYES选项，然后对表空间执行LOAD或REORG实用程序来实现的。
In most cases, ALTER SET DATA TYPE requires table reorganization (reorg) because it changes the physical row format.
大多数情况下，ALTERSETDATATYPE需要对表执行重组(reorg)，因为它修改了物理行格式。
A third problem can occur when performing RUNSTATS or REORG on your table.
当对表执行RUNSTATS或REORG时，可能出现第三个问题。
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.
这为表重组问题提供了一些改进，因为您可以使用这些选项来在后台执行一个部分重组，而不需要让表处于脱机状态。
Additionally, DSNACCOX with DB2 10 has specific code to reduce the REORG requirements for table Spaces residing on SSDs.
另外，DB 210的DSNACCOX具有特定的代码来降低对驻留在SSD上的磁盘空间的REORG需求。
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。
The script below will scan for AW fact tables named using the wildcard expression % _measures and scripts ALTER table and REORG commands.
以下脚本将使用通配符表达式% _ MEASURES以及脚本alterTABLE和REORG命令扫描指定的aw事实表。
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选项，则表中的数据将被完全压缩。
Each of these operations: redistribute, table reorg, index create, and runstats require scanning the table data once.
这些操作中：redistribute、table reorg、indexcreate和runstats，每个操作都需要扫描一次表数据。
For other interfaces, the sampling data (used for building the ADC dictionary) remains uncompressed, as seen in Figure 1, until an offline table reorg is performed.
对于其他接口，如图1所示，抽样数据(用于构建adc字典)直到执行离线table reorg时才被压缩。
Compact on is the default for the redistribute utility, where it performs space compaction much like an offline table reorg does.
COMPACTON是重分发实用程序的默认选项，它像离线table reorg那样执行空间压缩。
应用推荐