The table provides a list of exit codes returned by the /schemacompare command.
| Error code | Status | Description |
|---|---|---|
| 0 | Success | Indicates that the operation has been completed without errors. |
| 2 | Execution terminated with Ctrl+Break | Indicates that the operation was manually stopped by the user. |
| 10 | Command-line usage error | Indicates that the syntax doesn’t match the expected command format, required arguments are absent, or unsupported options are used. |
| 11 | Illegal argument duplication | Indicates that the same command-line argument was specified more than once. For example, /arg2 depends on /arg1, but you used /arg2 without providing /arg1. /arg2 can’t be used with/arg1, and you specified them both. |
| 20 | Trial expired | Indicates that the trial period has expired, or the product has not been activated. |
| 30 | Project file corrupted | Indicates that the project file can’t be read or contains invalid data. |
| 40 | Server connection fail | Indicates that dbForge Studio could not connect to the specified server. |
| 100 | The source and the target are identical | Indicates that the comparison found no differences between the source and target. |
| 101 | The source and the target are not identical | Indicates that differences were detected between the source and target. |
| 105 | Resource unavailable | Indicates that a required resource, such as a file, path, or server component, is not accessible. |
| 106 | I/O error | Indicates that an input/output operation failed. |
| 107 | Failed to create report | Indicates that the system could not generate the report file. |
| 108 | No objects to compare | Indicates that the comparison process found no valid objects in the source or target. |
| 112 | No objects to sync | Indicates that there are no changes available to synchronize. |
| 114 | Error reading objects filters file. Object filters are not loaded. | Indicates that the system could not load or parse the object filters 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.