分区数据库中的runstats。
分区数据库环境中的MQT优于昵称限制。
Restrictions on MQTs over nicknames in a partitioned database environment.
连接器能够并行读写或并行装载分区数据库。
The connector can read and write in parallel and can load partitioned databases in parallel.
图1说明了分区数据库环境中的DB 2架构。
Figure 1 illustrates the DB2 architecture in a partitioned database environment.
用于分区数据库环境的服务器辅助客户机重路由
Server assisted client reroute for partitioned database environments
该连接器能够以并行或序列模式处理分区数据库。
The connector can work with partitioned databases in parallel or sequential mode.
此外，自动存储支持还适用于多分区数据库。
In addition, automatic storage support has been added for multi-partition databases.
通过支持分区数据库和卸载能力，能够同时扩展多个目录
Scale, with support for partitioned databases and ability to unload to multiple directories in parallel
在该例中，分区号是0，因为我们处理的是单分区数据库。
The partition number is 0 in this case because we are dealing with a single-partition database.
在一个非分区数据库中，不需要分区键或分区映射。
In a non-partitioned database, no partitioning key or partitioning map is required.
该实用工具已经在下列平台的单个分区数据库中进行了测试。
The utility was tested in a single partition database on the following platforms.
将DB2UDB应用程序迁移到分区数据库中
分区映射是在分区数据库中控制数据存储位置的一种灵活的方式。
Partitioning maps are a flexible way of controlling where data is stored in a partitioned database.
分区数据库可以维护大量数据，并可以为新的应用程序提供机会。
A partitioned database can maintain very large amounts of data and can open opportunities for new applications.
分段表(在多分区数据库环境中装载实用程序不支持这种表)。
Staging tables (not supported by the load utility in multiple partition database environments).
注意：无法使用IXF文件将导出表装入哈希分区数据库中定义的表。
Note: IXF files cannot be used to load into a table defined in a hash partitioned database.
在分区数据库中，一个表可以分布在一个或多个数据库分区中。
Tables within a partitioned database can be located in one or more database partitions.
多分区数据库分区组只能用属于相同实例的数据库分区来定义。
Multi-partition database partition groups can only be defined with database partitions that belong to the same instance.
每个包含不止一个数据库分区的子集称作多分区数据库分区组。
Each subset that contains more than one database partition is known as a multi-partition database partition group.
通过管理节点来管理分区数据库，它协调了对数据库结构的访问与管理。
The partitioned database is managed through the administration node, which coordinates access to and manages the structure of the database.
每多一个服务器，就意味着将有更多的CPU、内存和更多的磁盘用于分区数据库。
Each additional server means more CPUs, more memory, and more disks for your partitioned database.
db2pdbc：它处理来自远程节点的并行请求。(只用于分区数据库环境中)。
Db2pdbc: Handles parallel requests from remote nodes (used only in a partitioned database environment).
其焦点在应用程序的迁移上，但同时也介绍了针对分区数据库的设计、配置和操作考虑。
The focus is on application migration, but design, configuration, and operational considerations for a partitioned database is also covered.
请参考“分区数据库环境中的MQT优于昵称限制”，了解关于如何处理该限制的提示。
Please follow the "Restrictions on MQTs over nicknames in a partitioned database environment" for tips on how to work around this restriction.
手动地确定前滚一个数据库的正确时间点比较困难，对于分区数据库更是如此。
Manually determining the correct point in time to which to roll forward a database is difficult, particularly for a partitioned database.
有一个隐式的假设：每个表中的行是均匀分布在每个多分区数据库分区组中的所有分区上的。
There is an implicit assumption that the rows of each table are evenly distributed across all the partitions in each multiple-partition database partition group.
分区数据库的编目表只存储在发出CREATEDATABASE命令时所在的那个分区上。
The catalog tables for partitioned databases reside only on the partition from which the CREATE database command was issued.
用户与分区数据库的交互是通过一个数据库分区，即用于那个用户的协调分区创建的。
User interaction with a partitioned database occurs through one database partition, known as the coordinator partition for that user.
在分区数据库环境中，每个数据库可以在一个不同的数据库分区服务器上有它的编目分区。
Each database in a partitioned database environment can have its catalog partition on a different database partition server.
为使分区数据库正常运行，必须在每个数据节点中以相同的方式来配置操作系统环境，包括用户和组。
For the partitioned database to function properly, you must configure the operating system environment, including users and groups, in the same manner on each data node.
应用推荐