Other Limitations

sybmigrate does not do any special processing for a DTM/XA environment. The status of open transactions and outstanding prepared transactions should be given consideration. If any special handling is required, you must do it manually.

There is no reliable way for sybmigrate to determine the dependency of various objects. sybmigrate does not attempt to create an order in which objects are migrated based on their dependencies on other objects. Views can be dependent upon other views, and they will not be re-created if the view on which they are dependent has not yet been migrated. The migration of stored procedures and triggers may not be successful if the data on which they depend has not yet been migrated. Cross-database dependencies mean that you need to coordinate the migration of related objects. If dependencies are within the selected set, sybmigrate takes care of those dependencies. However, if dependencies exist outside the selected set, you may need to run sybmigrate through migration more than one time. For this reason, you may need to perform some partial retries to successfully complete the data migration.

SAP ASE versions 12.5.3 and later allow you to specify the size and location of a work database on your target server. When migrating a database or server from a source server with SAP ASE versions 12.0 and later but earlier than 12.5.0.1, you must specify the size and location of a work database on the target server.

The name of the source and the target databases must be the same. SQL schema generated by ddlgen may have objects that must be qualified with the source SAP ASE server name.

sybmigrate does not support any kind of auditing for migration activities.

When renaming any of the compiled objects (procs, views, rules, defaults) the object name in syscomments is not updated.

During the migration, the ddlgen query the object from syscomments with the old name in the text. This old name in the text causes problems for sybmigrate during the DDL migration.