| Error Code | Description | Additional Information |
|---|---|---|
| 0 | Success | The operation was completed without errors. |
| 2 | Stop execution with Ctrl+Break | Execution stopped because of Ctrl+Break. |
| 10 | Command line usage error | The command line was used incorrectly. For example, an incorrect flag or incorrect syntax could be used. |
| 11 | Illegal argument duplication | Some arguments should not appear more than once in a command line. For example, /arg2 depends on /arg1 but you specified /arg2 without specifying /arg1. Alternatively, /arg2 cannot be used with/arg1, but you used them both. |
| 20 | Trial expired | The software trial period expired or the product was not activated. |
| 30 | Project file corrupted | Project file was corrupted. |
| 40 | Server connection fail | Server connection failed. |
| 100 | The databases being compared are identical or no objects have been included | The source and the target being compared are identical. |
| 101 | The source and the target are not identical | The source and the target are not identical. |
| 105 | Resource unavailable | File is missing. |
| 106 | I/O error | Tool attempts to write to a file that already exists and the \force switch has not been set. |
| 107 | Failed to create report | The report was not created. |
| 108 | No objects to compare | There are no objects for comparison. |
| 112 | No objects to sync | Databases are not identical but there are no objects selected for synchronization. |
| 114 | Error reading objects filters file. Object filters are not loaded | This is returned when an error is detected in the filter file. |
Note
The 112 exit code may also occur in the following cases:
- The source and target schemas are identical, which means no differences were detected during the comparison process.
- Filters were applied during the schema comparison, excluding all objects with differences, leaving no objects to synchronize.
- Synchronization options or settings excluded specific object types or changes, leaving no objects to synchronize.
- The comparison was limited to a specific scope, for example, certain tables or schemas, and no differences were found within that scope.