db2se migrate command

The db2se migrate command migrates an spatially-enabled database to Version 9.7. This command is deprecated and will be removed in a future release. Use the db2se upgrade command instead.

This command might drop and re-create spatial indexes to complete the migration, which can take a significant amount of time depending on the sizes of your tables. For example, your indexes will be dropped and re-created if your data is moving from a 32-bit instance to a 64-bit instance.
Tip: Run the db2se migrate command with the option -force 0 and specify a messages file to find out which indexes must be migrated without performing additional migration processing.

Authorization

SYSADM or DBADM authority on the spatially-enabled database that you want to migrate.

Command syntax

db2se migrate command

Read syntax diagramSkip visual syntax diagramdb2se migratedatabase_name -userIduser_id -pwpassword  -tableCreationParameterstable_creation_parameters  -force force_value  -messagesFilemessages_filename

Command parameters

Where:
database_name
The name of the database to be migrated.
-userId user_id
The database user ID which has either SYSADM or DBADM authority on the database that is being migrated.
-pw password
Your user password.
-tableCreationParameters table_creation_parameters
The parameters to be used in the creation of the Spatial Extender catalog tables.
-force force_value
  • 0: Default value. Attempts database migration, but stops if any application-defined objects such as views, functions, triggers, or spatial indexes have been based on Spatial Extender objects.
  • 1: Automatically saves and restores application-defined objects. Saves and restores spatial indexes if necessary.
  • 2: Automatically saves and restores application-defined objects. Saves spatial index information, but does not automatically restore spatial indexes.
-messagesFile messages_filename
The file name containing the report of migration actions. The file name you provide must be a fully-qualified file name on the server.
Tip: Specify this parameter to help you troubleshoot migration problems.
Restriction: You cannot specify an existing file.
You might receive one or more of the following errors during migration:
  • Database is not currently spatially enabled.
  • Database name is not valid.
  • Other connections to the database exist. Cannot be run.
  • Spatial catalog is not consistent.
  • User is not authorized.
  • Password is not valid.
  • Some user objects could not be migrated.