"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 (`).
Info
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
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.

    • Related Articles

    • How to Connect to MySQL Server

      In the second article of the series uncovering how to get started with MySQL, we talk about the ways of connecting to MySQL Server. You can connect to MySQL Server using MySQL Client, dbForge Studio for MySQL, and MySQL Workbench. In this article, we ...

    • Creating a Connection from External Parameters in dbForge Studio for MySQL

      dbForge Studio for MySQL does not currently support creating or opening connections by passing connection parameters through command-line arguments or Privileged Access Management (PAM) solutions. The workaround described below allows a connection to ...

    • Accessing Server Response Data with TScHttpWebRequest

      When working with TScHttpWebRequest, it's crucial to properly handle potential server errors to access any data returned by the server, even in error scenarios. The HttpException provides valuable information about the server's response in case of an ...

    • SSH Host Key Verification Error in dbForge Studio for MySQL

      Attempting to connect to a server over SSH may fail with the following error message: Can't connect to SSH server: The computed hash verification does not correspond to the received. (code 0) The same connection may work successfully in PuTTY or ...

    • Lost Connection to MySQL Server

      A lost connection to a MySQL server is a common issue and, in most cases, is not related to dbForge tools. It typically occurs due to server settings, network interruptions, or long-running queries. Recommended Solution For official guidance on ...