"Object Does Not Exist" Error During Data Export from the Command Line (MySQL)

"Object Does Not Exist" Error During Data Export from the Command Line (MySQL)

When exporting data from the command line using the /dataexport utility, the following error may occur:

"Object 'database_name' does not exist"

The database or object exists and can be accessed normally, but the export operation fails.

This issue typically occurs when the database or object name contains uppercase characters (for example, DV_Analytics_JB) and the MySQL server is configured with:

lower_case_table_names = 0

Cause

When lower_case_table_names is set to 0, MySQL treats database and object names as case-sensitive.

If a database or object name is passed to the command-line utility without escaping, the name may be converted to lowercase by the shell environment before it reaches the application. As a result, dbForge Studio attempts to access an object whose name does not match the actual database or table name, causing the export to fail.

Workaround

Enclose the database and object names in backticks (`).

The exact syntax depends on the shell from which the command is executed.

Windows Command Prompt (CMD)

/table `DV_Analytics_JB`.`v_dwse_overzicht`

PowerShell

/table 'DV_Analytics_JB`.`v_dwse_overzicht'

In PowerShell, the backtick character (`) is used as an escape character. Wrapping the entire argument in single quotes ensures that the string is passed to the application without additional interpretation.

Notes

Using backticks is required only when database or object names contain uppercase characters and the MySQL server is configured with lower_case_table_names = 0.

If the object name is entirely lowercase or is specified explicitly in another way, the /table parameter can be used without additional escaping.