Starting sybmigrate

Whether you are running the GUI or the resource file version of sybmigrate, start it with the following relevant command line arguments:

sybmigrate [-v ] [-h ] [-f ]
	[-D 1 | 2 | 3 | 4 ]
	[-I interfaces file ]
	[-r input resource file ]
	[-m setup | migrate | validate | report ]
	[-rn status | space_est | repl | diff | password ]
	[-l log file ]
	[-t output template resource file ]
	[-J client_charset ]
	[-z language ]
	[-T trace_flags ]
	[-Tase trace flags ]
	[-f ]

Where:

• -v – prints the version string and exits.

• -h – prints the help information and syntax usage and exits.

• -f overrides the locking session.

  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.

• -D sets the debug level for sybmigrate. The default debug level is 2.

• -I identifies a specific interfaces file to find server names. If no interfaces file location is designated, for UNIX $SYBASE/interfaces or for Windows %SYBASE%\ini\sql.ini is used.

  You can override sybmigrate, and use the interfaces file by providing the -I argument if the LDAP entry is defined in $SYBASE/$SYBASE_OCS/config/libtcl.cfg on Unix or in %SYBASE%\%SYBASE_OCS%\ini\libtcl.cfg on Windows.

• -r specifies that the resource file mode is to be used in the migration process. If the input resource file is not specified by using the -r parameter, sybmigrate operates in GUI mode.

  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. You can run the entire migration process in the resource file mode, or you can choose to run only parts of in this fashion.

• -m designates the types of operations that are performed:

  • setup – to set up the repository and migration working database, and to migrate the server-wide data.

  • migrate – to perform data and object migration.

  • validate – to validate the migrated objects.

  • report – to run any of the five reports. The reports can be run in the GUI and resource file mode. The available reports are:

    • status – the migrate object status report gives information about objects that have been migrated. To run this report, issue:

      sybmigrate -r resource file -m report -rn
          status
      

    • space_est – use the target database space estimation report to verify that you have sufficient resources allocated to your target database. In the resource file mode, issue the following command to run the space_est report:

      sybmigrate -r resource file -m report -rn
          space_est
      

    • repl – use the replication report to check any explicitly replicated objects that have been migrated, determine the type of replication system, and to produce SQL commands for users to execute on the target Adaptive Server and the Replication Server. To run the repl report, issue:

      sybmigrate -r resource file -m report -rn repl
      

    • diff – checks the objects between the source and target databases. Users can run the report on individual objects, or the entire database, except for server and database information or metadata. You can run the diff report at any time. You do not need to run a setup session to run the diff report. The source and target database name do not need to be the same when running the diff report.

      The diff report provides the following information for the following object types:

      • Server information – compares the master database system catalogs row count between the source and target Adaptive Server. This task is similar to the validation session.

      • Database information – compares the user database system catalogs row count between the source and target Adaptive Server. This task is similar to the validation session.

      • DDL objects – the report displays whether the objects exist on the source or the target Adaptive Servers. If the objects exists in both databases, that object is not displayed in the report.

      • User table data – compares the row count of the user tables in the source and target Adaptive Server. If the table only exists in the source or target databases, the table is not displayed in the report.

  • password – creates a file for the changed passwords. This report can only be run by a System Administrator.

• -rn indicates what type of report to generate. If -rn is not specified, all five reports are run.

• -l indicates a user-defined log file where the output of the migration process is stored. If -l is not used, the logs are stored in $SYBASE/$SYBASE_ASE/init/logs or the working directory.

• -t directs sybmigrate to generate an output template resource file, to be used for subsequent migrations 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 can use -t only in the resource file mode.

• -J specifies the character set to be used for the Adaptive Server connection.

• -z specifies the language to be used for the Adaptive Server connection.

• -T sets command line trace flags. They are:

  • DUMP_SQL – specifies that every query issued by sybmigrate is output to the log file.

  • NO_SORTED_DATA – overrides the default, which specifies that tables with clustered indexes are copied to the target server in order, and the clustered index is recreated using the with_sorted_data option.

  • LEAVE_PTBL_ON_ERROR – specifies that proxy tables are not deleted on failure.

  • SKIP_CONFIG_CHECK – specifies that configuration compatibility checks are not to be performed.

  • SKIP_PARTITION_CHECK – specifies that partition compatibility checks are not to be performed.

  • DUMP_DDL – specifies that DDL commands are to be output to the log file.

  • DUMP_DEPEND_OBJECT – specifies that when the auto_select_dependent_objects option is used, sybmigrate outputs a list of objects added as dependents.

  • ONE_WORK_THREAD – specifies that one work thread is to be used, overriding the current setting for schema creation threads.

  • ALLOW_DATA_AND_INDEX – overrides default behavior, in which indexes are created after all tables are created. Indexes are created as resources become available.

• -Tase is used to run Adaptive Server trace flags (turned on using dbcc traceon) for all Adaptive Server connections opened by sybmigrate. The trace flags should be specified in a comma-separated list.

When you run sybmigrate, there are three phases of the migration process that you must follow: setup, migrate, and validate.