Exit Codes Used in Command Line for /datacompare

If schema comparison is run through the command-line interface, the following exit codes are returned depending on the execution result:

Error Code Description Additional Information
0 Success The operation completed without errors.
2 Execution terminated 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 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 source and the target are identical 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 selected 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 Filter file is corrupted.

Want to Find out More?

Overview

Overview

Take a quick tour to learn all about the key benefits delivered by dbForge Studio for MySQL.
All Features

All features

Get acquainted with the rich features and capabilities of the Studio in less than 5 minutes.
Request a demo

Request a demo

If you consider employing the Studio for your business, request a demo to see it in action.
Ready to start using dbForge Studio for MySQL?