Pre-migration Considerations

sybmigrate requires allow resource limits to be set to 0.

If metadata already exists on the target server, you cannot migrate server data.

When you create a new SAP ASE server with a different logical page size into which you want to migrate data, you must adequately adjust the size of the database on the target SAP ASE server to accommodate the inbound data. If you are migrating data to an SAP ASE server with a larger logical page size, this is especially important.

Use the space estimation report, space_est, to determine how much space is available on your target database.

To speed the migration process, you can run multiple sessions of sybmigrate within the same server. However, running more than one session of sybmigrate on the same source and target database path is not allowed.

You must manually create segments on the target database before migrating tables and indexes.

The data transfer rate for sybmigrate is configured through CIS bulk insert array size. The default configuration for CIS bulk insert array size is 50 rows. This means that as many as 50 rows of data are buffered by CIS before being transferred to the target SAP ASE server.

To increase throughput, increase the configuration of CIS bulk insert array size to a larger value.

However, increasing CIS bulk insert array size causes the source SAP ASE server to use memory from the operating system for local buffers. This can lead to excessive consumption of operating system memory.

SAP recommends that if you do choose to increase the CIS bulk insert array size default value, you do so modestly. See the CIS documentation for more information.

CIS bulk insert array size has no effect on data throughput if the table being transferred has a text, image, or Java ADT column. When a table has a text, image, or Java ADT column in it, all data is migrated one row at a time, for the duration of the migration of that particular table. Also, no array buffering takes place.

As the data migration is being done using CIS bulk transfer, the value for the configuration parameter CIS packet size on the source SAP ASE server can affect the speed of the data transfer. The recommended value for CIS packet size on the source SAP ASE server is the logical page size (2K, 4K, 8K, or 16K) of the target SAP ASE server.

max packet size allowed on the target SAP ASE server should match the value of CIS packet size on the source SAP ASE server.

For more information on max packet size allowed, see the System Administration Guide.

To maximize the performance of sybmigrate, increase the additional network memory configuration parameter on the target SAP ASE server to a value larger than the default.

For more information on additional network memory, see the System Administration Guide.

All the above considerations affect the max memory configuration parameter. Before migrating your data, make sure that max memory is set to a sufficiently large value.

There are three types of data that are migrated: server data, database data, and user objects. To migrate metadata (the server and database data), the target SAP ASE server must be newly installed so that the migrated metadata does not conflict with any residual data from previous usage.

If you are migrating only user objects, you can use a previously used SAP ASE server. For user data however, the target tables must be empty.

Before migrating data, create the databases into which you want to migrate data on the target SAP ASE server. The databases should have the same name that they have on the source SAP ASE server.

To enable conversion of character sets that do not have an internal SAP ASE conversion routine, configure the target SAP ASE server with enable unicode conversions set to 1.

Determine the size of the named caches and buffer pools on the target SAP ASE server. sybmigrate does not migrate cache configurations. You can use the information that is generated by ddlgen and apply it to the target SAP ASE server, or you can choose to configure larger amounts of memory, in light of the larger page size being used.

However, sybmigrate migrates cache bindings, therefore if the required cache is not in the target SAP ASE server, warnings are generated in the migration log.

Before running sybmigrate, you must install the desired languages on the target SAP ASE server. The default language should be the same on the source and the target SAP ASE server.

If there are user messages on the source SAP ASE server that are not installed on the target SAP ASE server, sybmigrate aborts user message migration and reports an error.

To complete the migration, the source and target SAP ASE servers must have different local server names. Set the local server name, and then restart the servers for the change to take effect.