Review the action plan and warnings
Last modified: January 31, 2023
Action plan
On the Summary tab of the Data Synchronization Wizard, you can also review the action plan of your synchronization.
Action plan comprises the list of synchronization actions in the order they are to be performed.
If you want to see the details of any action, click an arrow button next to it to expand the list.
You can also click Expand all to see the description of all actions.
To locate a required action, you can type the search text in the search box.
Handle synchronization issues
When setting synchronization options, you may configure dbForge Data Compare for PostgreSQL behavior in case an error occurs during the script execution.
If you want to have consistent data, select the Use single transaction checkbox on the General tab of the Data Synchronization wizard. If this option was selected, the entire synchronization script is executed as one single transaction. In case of any error or synchronization canceling, all changes are rolled back.
In case you need, for example, debug the synchronization script, and you don’t want the changes to be rolled back, clear the Use single transaction checkbox. In such a case, the script is executed as multiple transactions. All the changes made by the statements before the one containing an error, will be applied to the database.
Note
To avoid errors when synchronizing data, pay attention to the synchronization warnings. Exclude database objects that can cause errors from the synchronization.
Warnings
Synchronization warnings are displayed on the Summary page of the Data Synchronization Wizard. These warnings are the same as column level Mapping Warnings. But mapping warnings appear regardless of real data differences, they are generated if there are column datatype differences, which may cause errors or data loss in the tables to compare. Synchronization warnings appear only if there are data to be updated or inserted to the target table.
If you encountered synchronization warnings, the synchronization may fail or data loss may occur because of truncation or rounding. If the warning has the Error icon, then the error will certainly occur when executing the synchronization script. To avoid this error, exclude this table or corresponding records from the synchronization by clearing the corresponding checkboxes in the data comparison results grid.
The list of data synchronization warnings
Warning | Description |
---|---|
Keys and indexes warning | Synchronization process may cause loss of disabled keys and indexes. |
Source column allows Nulls which can not be stored in target | Source column X allows Nulls which can not be stored in target column Y, migrating the data may cause an error. |
Conversion is possible, but may fail in case of incompatible data. | Conversion between columns X and Y is possible, but may fail in case of incompatible data. |
Columns have different sizes | Columns X and Y have different sizes, migrating the data may cause truncation. |
Columns have different precisions | Columns X and Y have different precisions, migrating the data may cause overflows. |
Columns have different data format | Columns X and Y have different data format, migrating the data may cause truncation. |
Columns have incompatible types | Columns X and Y have incompatible types. |
Columns have different collations. | Columns X and Y have different collations. |
Foreign key warning | Table X has foreign key to the table Y. Synchronization can fail. |
Foreign key warning | A foreign key might not recover after synchronization. |
Columns are enum types. | Columns X and Y are enum types and may not be conversioned. |
Columns have different precisions and/or scales. | Columns X and Y have different precisions or scales, migrating the data may cause rounding or overflows. |