Quick Beginnings for DB2 Extended Enterprise Edition for UNIX

Overview of the Migration Process

After you install DB2 Extended Enterprise Edition, any databases that you created with earlier versions of DB2 will not automatically work with the new version of DB2. You must follow the steps in this section to migrate your instances and then to move data from the previous database system to the new one. Although your data is not changed during the process, the database is different from the original one. The differences depend on the type of database system from which you are migrating.

Migrating Single-Partition Databases

After you migrate a single-partition database from an earlier version of DB2, the following changes are made to your database:

The database is relocated from the INSTHOME/INSTNAME directory to the INSTHOME/INSTNAME/NODE0000 directory. A node is created with a default name of NODE0000.

The database is migrated to SMS table space containers. If you are migrating a Version 1.x database, a table space container is created for each segment directory. For example, if you had 16 segment directories before migration, you would have 16 containers in each table space after migration. The following table depicts the segment directories prior to migration and shows two of the resulting table spaces after migration.

Version 1.x Segment Directories	Version 5 Table Space ID 0	Version 5 Table Space ID 5
`segment_dir`	`segment_dir` /SQLT`tablespace_id` .`segment_id`	`segment_dir` /SQLT`tablespace_id` .`segment_id`
SQLS0000 SQLS0001 SQLS0002 . . . SQLS0016	SQLS0000/SQLT0000.0 SQLS0001/SQLT0000.1 SQLS0002/SQLT0000.2 . . . SQLS0016/SQLT0000.16	SQLS0000/SQLT0005.0 SQLS0001/SQLT0005.1 SQLS0002/SQLT0005.2 . . . SQLS0016/SQLT0005.16

Version 1.x
Segment Directories

Version 5
Table Space ID 0

Version 5
Table Space ID 5

segment_dir

segment_dir
/SQLTtablespace_id
.segment_id

segment_dir
/SQLTtablespace_id
.segment_id

SQLS0000
SQLS0001
SQLS0002
.
.
.
SQLS0016

SQLS0000/SQLT0000.0
SQLS0001/SQLT0000.1
SQLS0002/SQLT0000.2
.
.
.
SQLS0016/SQLT0000.16

SQLS0000/SQLT0005.0
SQLS0001/SQLT0005.1
SQLS0002/SQLT0005.2
.
.
.
SQLS0016/SQLT0005.16

If you are migrating a Version 2.x database, there are no changes to the table spaces (SMS table space remain as SMS; DMS table spaces remain as DMS).

The following node groups are created: IBMCATGROUP, IBMDEFAULTGROUP, and IBMTEMPGROUP. For more information, see "Nodegroups and Data Partitioning".
The following table spaces are created for Version 1.x databases that are migrated:

SYSCATSPACE
Belongs to the IBMCATGROUP nodegroup on the catalog node and contains system catalog tables.
TEMPSPACE1
Belongs to the IBMTEMPGROUP nodegroup and is empty.
USERSPACE1
Belongs to the IBMDEFAULTGROUP nodegroup and contains all user tables.

Migrating Partitioned Databases

After you migrate a partitioned database from a previous version of DB2, the following changes are made to your database:

The database is relocated from the INSTHOME/INSTNAME/NODEnnnnn directory to the INSTHOME/INSTNAME/NODEnnnn directory. Note that node number is shorter by one digit.

The database is migrated to SMS table space containers. If you are migrating a database you created using DB2 Parallel Edition Version 1.x, a table space container is created for each segment directory. For example, if you had 16 segment directories before migration, you would have 16 containers in each table space after migration. The following table depicts the segment directories prior to migration and shows two of the resulting table spaces after migration:

Version 1.x Segment Directories	Version 5 Table Space ID 0	Version 5 Table Space ID 5
`segment_dir`	`segment_dir` /SQLT`tablespace_id` .`segment_id`	`segment_dir` /SQLT`tablespace_id` .`segment_id`
SQLS0000 SQLS0001 SQLS0002 . . . SQLS0016	SQLS0000/SQLT0000.0 SQLS0001/SQLT0000.1 SQLS0002/SQLT0000.2 . . . SQLS0016/SQLT0000.16	SQLS0000/SQLT0005.0 SQLS0001/SQLT0005.1 SQLS0002/SQLT0005.2 . . . SQLS0016/SQLT0005.16

Version 1.x
Segment Directories

Version 5
Table Space ID 0

Version 5
Table Space ID 5

segment_dir

segment_dir
/SQLTtablespace_id
.segment_id

segment_dir
/SQLTtablespace_id
.segment_id

SQLS0000
SQLS0001
SQLS0002
.
.
.
SQLS0016

SQLS0000/SQLT0000.0
SQLS0001/SQLT0000.1
SQLS0002/SQLT0000.2
.
.
.
SQLS0016/SQLT0000.16

SQLS0000/SQLT0005.0
SQLS0001/SQLT0005.1
SQLS0002/SQLT0005.2
.
.
.
SQLS0016/SQLT0005.16

One table space is created for each nodegroup. The name of the table space is the same as the name of the nodegroup. In addition to the table spaces that are created for your nodegroups, the following table spaces are created for the three IBM nodegroups (IBMDEFAULTGROUP, IBMCATGROUP, and IBMTEMPGROUP):

IBMCATGROUP
Contains user tables that were in the IBMCATGROUP nodegroup.
IBMDEFAULTGROUP
Contains user tables that were in the IBMDEFAULTGROUP nodegroup.
SYSCATSPACE
Belongs to the IBMCATGROUP nodegroup on the catalog node and contains system catalog tables.
TEMPSPACE1
Belongs to the IBMTEMPGROUP nodegroup and is empty after the migration.
USERSPACE1
Belongs to the IBMDEFAULTGROUP nodegroup and contains all user tables that were in that nodegroup in the originating database.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]