Exit Codes Used in Command Line for /generatedata
Last modified: October 18, 2023
If data generation 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 has been completed without errors. |
2 | Execution stop | The execution was stopped by Ctrl+Break. |
10 | Command line usage error | The command line was used incorrectly. For example, an incorrect flag or syntax has been used. |
11 | Illegal argument duplication | Some arguments shouldn’t appear more than once. |
20 | Trial expired | The trial period has expired or dbForge Studio hasn’t been activated. |
30 | Project file corrupted | Project file was corrupted |
40 | Server connection fail | Server connection failed. |
103 | Script error | The script was executed with errors. |
105 | Resource unavailable | A file is missing. |
108 | No objects | There are no objects for generation. |
Was this page helpful?
Want to find out more?
Overview
Take a quick tour to learn all about the key benefits delivered by dbForge Studio for MySQL.
All features
Get acquainted with the rich features and capabilities of the tool in less than 5 minutes.
Request a demo
If you consider employing this tool for your business, request a demo to see it in action.