Troubleshooting

Solution: Check whether JRE is missing. Verify the Java path in the environment. For details about the supported Java JDK versions, see System Requirements.

Solution:

• Without JRE:

  

  Check whether the Java Runtime Environment (JRE) or Java Development Kit (JDK) version 1.8.0_141 or above with appropriate bit number is installed on the system and Java Home path is set. If there are more than one version of Java installed, set the -vm parameter in the configuration file by referring to Installing and Configuring Data Studio. This is a prerequisite for running Data Studio.

• Old JRE version:

  

  Check the version of Java Runtime Environment (JRE) or Java Development Kit (JDK) that is installed on the system. An older version installed on the system causes this error. Update the JRE to version 1.8.0_141 or above with appropriate bit number.

• Java Incompatibility:

  

  Check the version of the JRE or JDK installed in the system. If the installed Java version is incompatible with the system, this error occurs. Update the JRE to version 1.8.0_141 or above with appropriate bit number.

  You are advised to run the batch file to check compatibility and launch Data Studio. For details, see Quick Start.

Solution:

Solution: Check whether the server is running on the specified IP address and port. Use gsql to connect to a specified user and check the user availability.

Solution: A connection issue that may occur while using Data Studio is explained with an example:

Establish a database connection.

Run the query.

When a connection exception occurs in any one of the databases (PostgreSQL), the connection is closed. When the database connection is closed, all the function and procedure tabs, if open, will be closed too.

The system displays an error message. The Object Browser navigation tree displays the database status.

Only the current database will be disconnected. Other databases remain connected or are reconnected.

Re-connect to the database to proceed with execution.

Solution: Set Preferences > Session Settings > Data Studio Encoding and File Encoding to GBK, so that Chinese characters can be displayed properly.

Solution: When the Data Studio has used up the allocated maximum Java memory, the message "Out of Memory" or "Java Heap Error" is displayed. By default, the Data Studio.ini configuration file (in the Data Studio installation path) contains the entry -Xmx1200m. 1200m indicates 1200 MB, which is the maximum Java memory that can be used by Data Studio. The memory usage of Data Studio depends on the size of data obtained by users during the use of Data Studio.

To solve this problem, you can expand the Java memory size to an ideal value. For example, change -Xmx1200m to -Xmx2000m and restart Data Studio. If the updated memory is used up, the same problem may occur again.

• For the 32-bit Data Studio with 8 GB RAM, the value of Xmx cannot exceed 2044. For the 64-bit Data Studio with 8 GB RAM, the value of Xmx cannot exceed 6000. The upper limit may vary with your current memory usage.

  For example:

  -Xms1024m

  -Xmx1800m

• The maximum file size supported by Data Studio in the SQL Terminal depends on the value of Xmx in the Data Studio.ini file and the available memory.

Solution: Data Studio disconnects from the database specified in the file. Re-establish the connection and continue the operation.

Solution: The possible causes are as follows:

• An invalid client SSL certificate and/or client SSL key file was selected. Select a correct file and try again. For details, see Adding a Connection.
• The identity of the object in the database may have changed. Check whether the identity of the object has changed and try again.
• You do not have the required permissions. Contact the database administrator to obtain required permissions.

Solution: The possible causes are as follows:

• An invalid client SSL certificate and/or client SSL key file was selected. Select a correct file and try again. For details, see Adding a Connection.
• The identity of the object in the database may have changed. Check whether the identity of the object has changed and try again.
• You do not have the required permissions. Contact the database administrator to obtain required permissions.

"Failed to start this program because MSVCRT100.dll is missing. Try reinstalling the program to resolve the problem."

Solution: gs_dump.exe needs to be executed to display or export DDL, which requires the VC runtime library msvcrt100.dll.

To resolve this issue, copy the msvcrt100.dll file from the \Windows\System32 folder to the \Windows\SysWOW64 folder.

Solution: If the Profile folder in the User Data folder is unavailable or has been manually modified, this problem may occur. Ensure that the Profile folder exists and its name meets the requirements.

Solution: If the Profile folder in the User Data folder is lost or manually modified, this problem may occur. Ensure that the Profile folder exists and its name meets the requirements.

Solution: This problem may occur if the Preferences file does not exist or its name has been changed. Restart Data Studio to resolve this issue.

Solution: Restart Data Studio.

Solution: All edited data will be lost. Close the Edit Table Data dialog box and modify the data again.

Solution: This problem occurs if you choose Preferences > Query Results and set the column headers to be included. The selected cells include the column header cells as well. Modify the settings to disable the Include column headers option and try again.

Answer: After the Reuse Connection option is disabled, the tool creates a new session, but the temporary table can be edited only in the existing connection. To edit temporary tables, enable the Reuse Connection option. For details, see Managing SQL Terminal Connections.

Answer: If you add the same column multiple times in the multi-column sorting dialog box and click Apply, the following message is displayed. You need to click OK and select non-duplicate columns for sorting.

Answer: The following message is displayed. You need to set a valid column name and click Apply again. Then, the message is not displayed.

Answer: Canceling a table query that is being executed may cause the console to display the names of tables that are not created. In this case, you are advised to delete the table so that you can perform operations on tables with the same name.

Solution: Perform the following steps to generate a new security key:

1. Choose Datastudio > Userdata and delete the security folder.
2. Restart Data Studio
3. Create a new security folder and generate a new key.
4. Enter the password again to log in to Data Studio.