StreamShift Documentation

Make sure there is no active change data flowing from the source before stopping synchronization. Otherwise some events might not be applied to the target.

MySQL source and target: when doing "Lift and Shift only" migration between two MySQL databases, triggers are migrated automatically to the target database during schema migration. Streamshift drops the triggers before doing the initial data load and recreates them after initial load. Any triggers that refer to tables in a different database will not be recreated properly after initial load.

Oracle sources: when migrating XMLType columns from Oracle, exclude the column from the migration during the customization process to avoid errors during the data migration phase.

SQL Server source and target: when doing "Lift and Shift only" migration between two SQLServer databases, with the target is SQLServer 2019, Streamshift may wrongly report that the foreign key migration has failed. This can be ignored. Streamshift actually migrates foreign keys in this setup.

SQL Server source or target: when both an SSH tunnel and SSL are specified, you may encounter the error Connection Not Made: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Failed to validate the server name in a certificate during Secure Sockets Layer (SSL) initialization."

Oracle sources: StreamShift does not flag schemas or tables with names of more than 30 characters as incompatible (SMS-2233). (Names longer than 30 characters are not supported by LogMiner, the Oracle tool StreamShift uses to capture Oracle CDC.)