IIRC, sybmigrate will handle all metadata and permissions (grants).
On some versions, sybmigrate may forget users and groups; to
avoid problems, I'd suggest creating groups and users in the
empty target database before running sybmigrate.
sybmigrate pivots on a temporary repository of objects. If the
first run fails, you may run it again, and sybmigrate will only
retry the failed objects; the repository tells sybmigrate which
are the pending objects. This is good if some stored procedures
failed because they had lacking dependencies when sybmigrate
tried to copy them for the first time.
But it seems that sybmigrate cannot migrate databases on same server (Error the source and target ASE servers cannot be the same...)
What about a backup database from Sybase Central? Dump to file. Than drop database delete devices, create new one and new database and from Sybase Central Restore?
I have 1500 Mbyte devices... Dumped database to file (size of file 50 Mbyte)... Created data devices 500 Mbyte....
But during restoreing .. I ve got message: "Backup Server session id is: 11. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 126.96.36.199: Dumpfile name 'my_db072820796C ' section number 1 mounted on disk file 'c:\database_dump'
Data on dump will not fit into current database. Need 1500 Mbyte database."
Data cannot fit? Why? Data are 50 Mb and device is 500 Mb... Why I need 1500 Mb????