Databases originating from SESAM/SQL V2.x will be automatically migrated when they are accessed for the first time by a DBH of SESAM/SQL V9.1. In the event of migration the CCSN of a database from SESAM/SQL < V5.0 is changed to the value _NONE_. Spaces included in the logical data saving will be placed in the “copy pending” state by the migration. It is advisable to make a SESAM backup copy with COPY CATALOG OFFLINE. The first statement can also be COPY CATALOG_SPACE OFFLINE. The user spaces can be saved later on with COPY SPACE.
Replications cannot be migrated. They must be created.
SESAM backup copies cannot be migrated. They must be created.
SESAM backup copies from SESAM/SQL as of V2.x can be opened for reading in SESAM/SQL V9.1. Databases originating from SESAM/SQL V1.x can only be migrated with the utility statement MIGRATE.Logging files from SESAM/SQL V9.0 cannot be processed in SESAM/SQL V9.1. RECOVER [USING] on the basis of a backup from SESAM/SQL V9.0 is therefore not possible in SESAM/SQL V9.1.
However, it is possible to reset to a backup from SESAM/SQL as of V2.x with RECOVER SPACE ... TO. In this case the backup is not migrated, but after being read in the space thus created is migrated to SESAM/SQL V9.1. The space is placed in the “copy pending” state and must be saved.
It is also possible to reset an entire database to a backup from SESAM/SQL as of V3.1 in several stages. Because the catalog space is initially in the “copy pending” state after the reset, the catalog space must first of all be saved before the user spaces can be reset.
Reset the catalog space with RECOVER CATALOG_SPACE ... TO. The catalog space is migrated.
Save the catalog space with COPY CATALOG_SPACE.
Reset the user spaces with RECOVER SPACESET, specifying the time stamp of the catalog backup you want to reset to. Individual spaces can also be reset if only these are required.
Save the spaces in the log. Because of the migration during the reset these have been placed in the “copy pending” state.
A return migration from SESAM/SQL V9.1 to SESAM/SQL V9.0 is possible. For this, please contact your service center.
You will find detailed information on the topic of migration in the Release Notice for SESAM/SQL V9.1.