Before migrating data, indicate your source and target Adaptive Servers and register the paths between the source and target databases they contain. To do this, start sybmigrate with the -m setup command line option, or by selecting “Setup source databases for migration” when you are prompted in the Session Type window.
Indicating your source and target Adaptive Servers
and registering the paths between the source and target databases
The Connect to ASE window allows you to designate the source and the target Adaptive Servers for your migration process.
You can choose from the drop-down menu in the Server fields. The menus provide a list of Adaptive Servers that are located in the default interfaces file ($SYBASE/interfaces on UNIX or %SYBASE%\ini\sql.ini on NT) or in the interfaces file that you specify with the -I command line argument.
If you are not using the interfaces file, you cannot use the -I command line argument; you must specify the source and the target Adaptive Servers in the host:port format.
During the setup phase, you must be logged in to the servers as a System Administrator. Enter “sa” into the Login field, enter your password, and select Connect.
You can run only one session of sybmigrate at
a time. Therefore, if there is another user running sybmigrate on
the same source and target Adaptive Servers, you see the error message “Setup
session lock: Either previous setup exit abnormal or there is another
setup session running. Do you want to override?” You can
override the session lock because it is possible that the previous
session may have crashed or quit prematurely.
Before proceeding with the setup and migration process, verify that there are no other users running sybmigrate. If there is more than one user running sybmigrate simultaneously, Sybase cannot guarantee data integrity.
The Session Type window prompts you to select the type of operation you want to perform. Choose from:
Setup source databases for migration
Migrate database objects and data
Validate the migrated objects and data
Reports – when you select Reports, a Reports type indow displays. You can choose from status, space_est, repl, diff, or password. When you select either the space estimation or the replication report, a Report Paths Window prompts you to select the database paths on which to run the reports.
The Password, Status, and Replications reports are disabled if the setup session has not been completed between the source and target Adaptive Servers.
If you started sybmigrate with the -m option specifying setup, migrate, validate, or reports you do not see this window.
The Setup Paths window prompts you to select the source and target databases located within your source and target Adaptive Servers, so that sybmigrate knows where to put the data from the source Adaptive Server in the target Adaptive Server.
The source and target databases must have identical
names.
The Source Database drop-down list has a list of the databases in your source Adaptive Server.
The Target Database drop-down list has a list of the databases available in the target Adaptive Server. sybmigrate requires that you create the databases in the target Adaptive Server before beginning the migration process.
sybmigrate allows you to set the copy thread, create index thread, and work thread values during the setup, migration, or validate session of migration. The value you assign to each of these properties in the setup session becomes the default value, but you can temporarily override this value in the migrate or validate sessions.
The Copy Thread field tells sybmigrate how many threads to use during the data migration process. There is no limit on the number of threads that you can use, so depending on the amount of data to be migrated and the server resources available, you can increase the number of copy threads to maximize performance.
The Create Index Thread field tells sybmigrate how many create index threads to use when migrating data. There are no limits to how many create index threads you can use, so again, you can increase this number to maximize performance.
Copy thread, and create index thread values are limited
to the resources available to Adaptive Server.
Select the number of copy threads and create index threads for each database path that you create. If you have large and small databases within the same server, you can increase or decrease the number of threads accordingly.
Once you have selected a source and target database, and the number of copy threads and create index threads, click Add Path. Your choices are reflected in Migrate Paths above.
You can create as many paths as desired. If you require additional paths at a later point, you can add new paths by running sybmigrate through the setup mode again. If you run sybmigrate through the setup mode more than once, your original choices are still reflected, and any changes that you make are additions to these choices.
To change the number of copy threads or create index threads after you have added the path to sybmigrate, select the column you want to change and enter the new value. To change the source or target database, select the entire row and delete it. The Reset button on the bottom of the window clears all of the information that you have entered and returns the Setup Paths window to its original state.
When you have finished creating paths, click the Next... button.
The user controls the number of threads used for parallel
table transfer. Every table to be transferred concurrently requires
one server-to-server CIS connection. Consider the ramifications
of this requirement while designing the capacity of your system.
In a simple scenario, the tables to be migrated are non-partitioned. When you migrate non-partitioned tables, a single server-to-server connection is established. This connection consumes one user connection on the source Adaptive Server and one user connection on the target Adaptive Server.
If data migration is performed for n-way partition tables, the data transfer is done in parallel with a n-way degree of parallelism. This requires n worker processes on the source Adaptive Server, and 2n user connections on the target Adaptive Server.
For example, if you have 10 n-way partition tables and decide to use four threads in sybmigrate, configure the source Adaptive Server to have at least four worker processes and eight user connections. Configure the target Adaptive Server to have at least eight user connections.
The Setup Devices window asks you to indicate the size of the repository database and the device on which you want to run sybmigrate.
The Create Database Size field provides you with a default value in megabytes. This default is based on the number of copy and create index threads that you specified in the previous window. The default is the value that is the mandatory minimum value. If you choose to change this value, you can only increase it.
The Use Device field allows you to indicate the device on which you want to create the working database. You can accept the default device, or you can specify another device.
The Repository Database Size field allows you to specify additional space to be allocated to the repository database. When you run sybmigrate in setup mode for the first time, the repository database size is specified for you in megabytes based on information that you have previously entered, and on the contents of the source database. If you run sybmigrate through setup mode again, the number you enter into the Repository Database Size field indicates the number of megabytes by which you want to increase the repository database.
Select the logical device from the Logical Device drop-down list. The logical device is used to create and to alter the repository database. Select a device with ample space for the anticipated size of your repository database.
In the Migrate Server Data field, indicate whether or not to migrate server data. You can choose yes, no, or undecided.
When you choose yes, the server data is migrated at the end of the setup phase. When you subsequently run sybmigrate in the setup phase, you cannot migrate the server data because this task has already been completed.
If you selected “Yes” to migrate server data, an Option... button is enabled. When you click the option button a Login Account dialog box displays.
Use the Login Account Options dialog box to lock or unlock accounts or change the password on the target Adaptive Server.
If you choose no, the server data is not migrated, but you can go back and choose to migrate server data at any time, provided that database migration has not begun.
If you choose undecided, you can go back and choose yes or no at any time. However, when you select undecided, you cannot begin the migration phase. Undecided is a helpful option when you are trying to set up all the information for the migration process, but do not plan on actually migrating data until a later time.
When you have finished setting up the devices, click Setup.
The Setup Progress window displays the progress of the setup phase.
During this time, sybmigrate is creating the repository database, installing the database schema, creating a working database for each selected path, and migrating the server data based on your selection, in that order. If you are running sybmigrate in setup mode a subsequent time, it is creating new paths for data migration. If you do not want to create new paths, there is no reason to run sybmigrate through the setup mode more than once.
You can to view the progress in the log by clicking Show Log. The completion of the setup process is indicated when the Current Task window displays DONE, and when the log shows SETUP_COMPLETE. Click Close to exit the log and the Setup Progress window.
You return to the Connect to ASE window. Select Quit to exit sybmigrate. To begin the migration phase of the data migration process, exit sybmigrate and restart it in the migrate mode.
