Effect of utilities on objects that have the DEFINE NO attribute
You can run certain online utilities on table spaces or index spaces that were defined with the DEFINE NO attribute. When you specify this attribute, the table space or index space is defined; however, DB2® does not allocate the associated data sets until a row is inserted or loaded into a table in that table space.
You can populate table spaces whose data sets are not yet defined by using the LOAD utility with either the RESUME option or the REPLACE option. Using LOAD to populate these table spaces results in the following actions:
- DB2 allocates the data sets.
- DB2 updates the SPACE column in the catalog table to indicate that data sets exist.
- DB2 loads the specified table space.
For a partitioned table space, all partitions are allocated even if the LOAD utility is loading only one partition. Avoid attempting to populate a partitioned table space with concurrent LOAD PART jobs until after one of the jobs causes all the data sets to be created.
Online utilities that encounter an undefined target object might issue informational message DSNU185I, but processing continues. The following online utilities issue this message when a table space or index space with the DEFINE NO attribute is encountered. The object is not processed.
- CHECK DATA
- CHECK INDEX
- COPY
- MERGECOPY
- MODIFY RECOVERY
- QUIESCE
- REBUILD INDEX
- RECOVER
- REORG INDEX
- REORG TABLESPACE1
- REPAIR, but not REPAIR DBD
- RUNSTATS TABLESPACE INDEX(ALL) 2
- RUNSTATS INDEX 2
- UNLOAD
REORG TABLESPACE processes the object if ROWFORMAT RRF is explicitly specified and the specified target is an entire undefined table space in basic row format. In this case, DB2 updates the row format definition in the catalog and directory. No data sets are defined for the table space.
- RUNSTATS recognizes DEFINE NO objects and updates the catalog's access path statistics to reflect the empty objects.
You cannot use stand-alone utilities on objects whose data sets are not yet defined.