Show Related--Storage groups

When you select a storage group from the contents pane and select Show Related for that object, the Show Related dialog lists any objects with first-level dependencies on that storage group. These objects can be: databases, indexes, tables, table spaces. You can view second-level dependencies by selecting Show Related for each object with a first-level dependency.

If you alter the storage group (available from the Control Center) to add or remove volumes from a storage group, the changes you make to the volume list have no effect on existing storage. Changes take effect when new objects are defined or when you use the reorganize, recover, or load with replace option utilities (available from the Control Center) on existing objects.

Databases, Indexes, Table spaces

A storage group cannot be dropped if it is used by any table space or index space. If you try to drop a table space or index space that is using the storage group the statement will fail.

Dropping a default storage group: If you drop the default storage group of a database, the database no longer has a legitimate default. You must then specify USING in any statement that creates a table space or index in the database. You must do this until you either:

• Create another storage group (available from the Control Center) with the same name, or
• Designate another default storage group (available from the Control Center) for the database.

Changing the name of a storage group impacts the databases, indexes, and table spaces that belong to it. If you want to change the high level qualifier for a storage group you must follow these steps:

1. Remove all table spaces and index spaces from the storage group by converting the data sets temporarily to user-managed data sets. Stop each database that has data sets you are going to convert. Convert to user-managed data sets (available from the Control Center. For table spaces see the Table Space Management page in the Alter Table Space dialog. For index spaces see the Index Space Management page in the Alter Index dialog.).
2. Drop the storage group (available from the Control Center). The drop succeeds only if all the objects that referenced this storage group are dropped or converted to user-managed.
3. Re-create the storage group using the correct volumes and the new alias (available from the Control Center).
4. Using the MVS utility IDCAMS, rename the data sets for the index spaces and table spaces to use the new high-level qualifier. If your table space or index space spans more than one data set, be sure to rename those data sets also.
5. Convert the data sets back to DB2-managed data sets, using the new DB2 storage group.
6. Start each database.
7. Verify the success of the procedure by displaying the database (select Display from the Databases folder in the Control Center).
8. Using SQL, verify that you can access the data.

To move data to a new storage group without using reorganize or recover utilities:

1. Stop the database.
2. Move the data, using DSN1COPY or a non-DB2 facility.
3. Alter the index or alter the table space to use the new integrated catalog facility, catalog name, or DB2 storage group name.
4. Start the database.

To move data to a new storage group using, reorganize, recover, or rebuild utilities:

1. Create a new storage group (available from the Control Center) using the correct volumes and the new alias.
2. Prevent access to the data sets you are going to move, by stopping the database (available from the Control Center).
3. Alter the table space and alter the index (available from the Control Center) to use the new storage group name.
4. Using the MVS utility IDCAMS, rename the data sets for the index spaces and table spaces to use the new high-level qualifier.
5. Start the database (available from the Control Center) for utility processing only.
6. Use the reorganize or the recover utility on the table space or index space, or use the rebuild utility on the index space.
7. Start the database.

Return to main Show Related help window