Creating a table space
Use this notebook to create a table
space at the current server.
Authorities
and privileges
To create a table space:
-
Open the Create table
space window.
-
Enter a valid unique name
for your table space. Once you have entered this name you can select OK
to create your table space and exit the window.
-
Optional: Select the type
of table space that you want to create. If you select to create a nonpartitioned, segmented or
LOB table space, the Partition Management tab on this notebook
is not available.
-
Specify the optional
properties for this table space.
-
Specify the appropriate information to manage
this table space . This information describes the data set
and space
management.
-
If you selected to define a partitioned table space, select the Partition
Management tab to define the optional properties of
each partition.

Related information

Use this page of the notebook to describe
the properties of the space.
- Optional: Select a buffer
pool name. The name must identify an active buffer pool.
-
Optional: Select a lock
size to be used within this table space.
-
Optional: Select the maximum
number of page or row locks that an application process can hold simultaneously
in the table space.
-
Optional: The encoding
scheme or coded character set identifier (CCSID)
is used for the tables
stored in the table space. Select whether
you want to use ASCII or EBCDIC
CCSIDs.
-
Optional: Enter the maximum number of rows that DB2 will consider placing on each data
page (MAXROWS). You can enter a value from
1 to 255, or accept the default of 255.
If
your table space is defined as large object
table space (LOB), the value of MAXROWS
must
be zero.
- Optional: Select whether to set a maximum
size for each partition or data set (DSSIZE). This is only
applicable for LOB table spaces.
-
Optional: Select whether to use the default CLOSE
rule.
-
Optional: This is applicable only for partitioned table spaces.
Check to use selective
partition locking (SPL) when locking a partitioned table space
(LOCKPART
YES).
- Optional: This is applicable only for LOB table spaces. Select the check box
to Write changes to a LOB column in a
LOB table space to the log. You cannot use
this if the auxiliary table in the
table space stored a LOB column that is greater
than 1 gigabyte. For LOB table
spaces, recording column changes to the log
is the default.
- Optional: Select the check box to allow
DB2 to choose where to locate data inserted by the INSERT statement in the
table space based on available space. This
is invalid for LOB table spaces.
[ Return to main task ]

Use this page of the notebook to define the details of the space.
-
Optional: Select whether the data set for the table
space is managed by the user (VCAT).
Then select a catalog name.
-
Optional: If data sets are not to be managed by the user, then
select Managed
by DB2. You can then enter the storage group name.
-
Optional: If you selected to have data sets managed by DB2, you should
enter the minimum primary
space allocation (PRIQTY). This field is not applicable if you selected
data set management by USER.
-
Optional: If you selected to have data sets managed by DB2, you should
enter the minimum secondary
space allocation (SECQTY). This field is not applicable if you selected
data set management by USER.
-
Optional: If you selected to have data sets
managed by DB2, you should
select an ERASE option.
This field is not applicable if you selected
data set management by USER.
- Specify to defer the physical creation of
underlying VSAM data sets until the very
first write operation occurs. The undefined
table space has a DB2 Catalog entry. The
default is to not defer the creation.
-
Optional: Select to choose to manage
the free space (FREEPAGE and PCTFREE) amount.
-
The cached pages
options are for group buffer pools only. This specifies
what table
spaces are written to the group buffer pool
in a data sharing environment.
-
Select whether to compress
data in the rows or not.
- Optional: Select the check box to decide whether DB2 tracks modified pages in the space map pages of the table space
or partition. If you choose to let DB2 track
changes, you could see some improvement in
the performance of incremental image copies.
If you clear the check box, DB2 uses the
LRSN value in each page to determine whether
a page has been changed. This should not
be used for a LOB table space.
[ Return to main task ]

Managing your partitions (for partitioned table spaces
only)
This page of the notebook gives you a table
of information about each partition you define
in the table space. The table has a default
set of parameters for each of the partitions
when it is first opened. The number of partitions
displayed corresponds to the number of partitions
defined on the Table Space notebook page.
- Click the CHANGE button to modify the properties of a partition
you have selected from the table. This opens
the Change Partition Management dialog.
- Click the Reset button to revert the properties of the selected
partitions back to the state at the time
you opened this window.
- Click the Move Up button to reorder the partitions within
the table. For every click of this button,
the partition is moved up, and the corresponding
partition number is changed.
- Click the Move Down button to reorder the partitions within
the table. For every click of this button,
the partition is moved down, and the corresponding
partition number is changed.
[ Return to main task ]