Upgrading internal tables from 3.10 (and older) to version 3.16

Upgrading database tables from 3.10 (and older versions) to 3.16

Really old versions of SymmetricDS (3.10.x and older) have router_id column in the sym_data_event table. This column had been removed to optimize storage and processing (in version 3.11).

In order to convert old installations to be compatible with modern code and table structure a manual migration script is necessary. Script must be executed by a DBA during downtime - when no applications are allowed to connect to the database. We recommend testing this migration in a non-Production environment to measure time it takes and test for compatibility.

General sequence of upgrade steps

Stop the SymmetricDS service. Repeat this for all SymmetricDS servers, if the system is clustered.
Turn on single user mode on the database, to prevent other applications from making changes or activating triggers.
Take full database backup.
Run the data migration script (see below) appropriate for the database type and validate results with your support contact.
Turn off single user mode on the database.
Run setup JAR to upgrade SymmetricDS to the modern version (3.16 or later). Repeat this for all SymmetricDS servers, if the system is clustered.
Start the SymmetricDS service and allow some time for table changes to be finalized. Do not(!) start services on other SymmetricDS servers, if the system is clustered, until the first server has completed all database changes to internal tables!

Database engine type-specific migration scripts

PostgreSQL: https://downloads.jumpmind.com/symmetricds/patches/3.16/manual_postgres_schema_upgrade_309-316.sql

Oracle: https://downloads.jumpmind.com/symmetricds/patches/3.16/manual_oracle_schema_upgrade_309-315.sql

MS SQL Server: https://downloads.jumpmind.com/symmetricds/patches/3.16/manual_mssql_schema_upgrade_309-316.sql

Properties ID: 000062 Views: 12 Updated: 17 hours ago

Filed under:

Installation