sybmigrate allows you to convert an SAP ASE server from one page size to another page size, and to migrate between platforms.

The utility is located in:

  • (UNIX platforms) $SYBASE/$SYBASE_ASE/bin/

  • (Windows) %SYBASE%\%SYBASE_ASE%\bin\sybmigrate.bat, as sybmigrate.bat.

Warning!  sybmigrate assumes that the source and target SAP ASE servers will not have any activity during the migration. If objects are created, modified, or deleted during the migration process (setup, migrate, and validate), SAP cannot guarantee migration integrity.


sybmigrate [-v ] [-h ] [-f ]
	[-D 1 | 2 | 3 | 4 ]
	[-I interfaces_file ]
	[-J client_charset ]
	[-l log_file ]
	[-m setup | migrate | validate | report ]
	[-r input_resource_file ]
	[-rn status | space_est | repl | diff | password ]
	[-T trace_flags ]
	[-t output_template_resource_file ]
	[-Tase trace_flags ]
	[-z language ]




  • You can use the sybmigrate utility to migrate an encrypted database just as you would a normal database. When you do, make sure:
    • The master database in the target server has the same database encryption key as the one used for the database you are migrating
    • You configure the target database as an encrypted database that uses the same database encryption key as the database you are migrating.
  • For security purposes, set file permissions at the highest level (preferably 600) for both the sybmigrate resource file and the file that contains the login and password information you are using for migrating logins from the source to the target server.

  • Make sure the allow resource limits configuration parameter is set to 0 before running sybmigrate.

  • You cannot migrate server data if metadata already exists on the target SAP ASE server.

  • If sybmigrate exited a session inappropriately, use -f to override the source and target database binding that is created so that only one session of sybmigrate can run on a source and target database path.

  • If you use the -r parameter, then you also need to use the -m argument to specify the type of operation to perform: setup, migrate, validate, or report. Run the entire migration process in the resource file mode, or run only parts in this fashion.

  • Use -t only in the resource file mode. -t requires that you start sybmigrate using the -r argument specifying the login information. This argument also requires -m to specify what type of resource file is to be generated.

  • You may specify the size and location of a work database on your target server.

  • SAP does not support SAP ASE version 12.5.1. SAP recommends that you upgrade from 12.5.1 to 12.5.4, then from 12.5.4 to 15.5 and later versions. To make the 12.5.1 server visible to the 12.5.4 or later server, use:
    sp_addserver 'servername', local

    Restart SAP ASE to recognize the 12.5.1 server.

  • You can override sybmigrate, and use the interfaces file by providing the -I argument if the LDAP entry is defined in:

    • UNIX – $SYBASE/$SYBASE_OCS/config/libtcl.cfg

    • Windows – %SYBASE%\%SYBASE_OCS%\ini\libtcl.cfg

  • sybmigrate automatically migrates predicated privileges when:
    • ddlgen is called to generate the scheme definitions, including grants, denies, and revokes

    • Data is migrated using CIS and proxy tables.


You must be a Sybase system administrator or log in with the sa_role to use sybmigrate.

If you want any user other than the SA to use sybmigrate, set the cis rpc handling configuration parameter to “1”.

Related concepts
Using sybmigrate to Migrate Data
Utility Commands Reference