Migration process

The goal of sybmigrate is to provide a means to migrate all objects and user data that exist on the source Adaptive Server. However, when migration takes place, there is some server-wide data that needs to be migrated before any user data or user objects can be migrated to individual databases.

The hierarchy of objects dictates the order in which objects are re-created. Generally, server-wide objects from the master database are created first. Independent objects like default languages and character are migrated to the target server before data from individual databases.

• Overview of the Migration Process
  The migration procedure consists of configuring the source and target Adaptive Servers, setting up the migration paths, migrating objects, and validating the migrated objects.
• Pre-migration Considerations
  You must have the source Adaptive Server and the target Adaptive Server running concurrently when you migrate data from one to the other.
• Configuration and Tuning for Higher Performance
  Depending upon your server resources, you can configure sybmigrate and Adaptive Server for optimal performance.
• Possible Errors to Avoid
  Before beginning the data migration process, sybmigrate checks for the following error conditions. If any of these conditions are detected, the migration procedure is aborted.
• Auto-select Dependent Objects for Migration
  sybmigrate selects dependent objects for migration when you use the auto-select feature.
• Migrating an Archive Database
  sybmigrate does not migrate an archive database if an entire installation is being migrated.
• GUI mode
  You can use either the GUI or the resource file mode for the migration process. You can also elect to run parts of the migration process in GUI mode, and parts of it in resource file mode.
• Resource File Mode
  Make these changes to the resource file mode: