If a database is already set up and database partition
groups defined for it, db2gpmap gets the distribution
map for the database table or the database partition group from the
catalog partitioned database server.
Authorization
Both of the following authorities:
- Read access to the system catalog tables
- BIND and EXECUTE package privileges on db2gpmap.bnd
Required connection
Before using db2gpmap the database manager must be started and db2gpmap.bnd must be bound to the database. If not already
bound db2gpmap will attempt to bind the file.
Command syntax
>>-db2gpmap--+------------------------+------------------------->
'- -d--+---------------+-'
'-database-name-'
>--+------------------------+----------------------------------->
'- -m--+---------------+-'
'-map-file-name-'
>--+----------------------------------------+------------------->
'- -g--+-------------------------------+-'
'-database-partition-group-name-'
>--+-----------------+--+-----+--------------------------------><
'- -t--table-name-' '- -h-'
Command parameters
- -d database-name
- Specifies the name of the database for which to generate a distribution
map. If no database name is specified, the value of the DB2DBDFT environment variable is used. If DB2DBDFT is not set, the default is the SAMPLE database.
- -m map-file-name
- Specifies the fully qualified file name where the distribution
map will be saved. The default is db2split.map.
- -g database-partition-group-name
- Specifies the name of the database partition group for which to
generate a distribution map. The default is IBMDEFAULTGROUP.
- -t table-name
- Specifies the table name.
- -h
- Displays usage information.
Examples
The following example extracts
the distribution map for a table ZURBIE.SALES in database SAMPLE
into a file called
C:\pmaps\zurbie_sales.map:
db2gpmap -d SAMPLE -m C:\pmaps\zurbie_sales.map -t ZURBIE.SALES