Solution: Check whether JRE is missing. Verify the configured Java path in the environment. Refer to System Requirements for supported Java JDK version.

Solution:

• For no 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, then set the -vm parameter in the configuration file. Refer to the Installing and Configuring Data Studio to set this parameter. This is a prerequisite for running Data Studio.

• For older versions of JRE:

  

  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 Java Runtime Environment (JRE) or Java Development Kit (JDK) that is installed on the system. Incompatible Java bit version installed on the system causes this error. Update the JRE version to 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. Refer to Getting Started for more information.

Solution: Check whether the server is running in the specified IP and port. Check for availability of the specified user by connecting through gsql.

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 database (PostgreSQL), the connection is closed. When the database connection is closed, all the function and procedure tabs, if open, will be closed too.

An error will be displayed and the Object Browser will show the status of the database.

Only the current database will be disconnected. Other databases will remain connected and re-connection is possible.

Re-connect to the database to proceed with execution.

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

Solution: 'Out of Memory' error or 'Java Heap Space' error occurs when Data Studio has used up the maximum allocated Java memory. By default, the configuration file Data Studio.ini (located in the Data Studio install path) contains the entry "-Xmx1200m", where 1200m denotes 1200MB as the maximum Java memory that can be used by Data Studio. The memory usage is based on the size of data fetched by Data Studio.

To resolve this issue, increase the Java memory size to the desired value. For example, update "-Xmx1200m" to "-Xmx2000m" and restart Data Studio. If the updated memory size is used up as well, the same issue might reoccur.

• For 32-bit Data Studio with 8 GB RAM, the value of the Xmx parameter must not exceed 2044 MB; for 64-bit Data Studio with 8 GB RAM, the value of the Xmx parameter must not exceed 6000 MB. The limit may vary based on your current memory usage.

  For example:

  -Xms1024m

  -Xmx1800m

• The maximum file size that Data Studio can support in the SQL Terminal is based on the value of the Xmx parameter in the Data Studio.ini file and available memory.

Solution: Data Studio will disconnect the connection profile. Re-establish the connection and continue execution.

Solution: This could happen due to any of the following reasons:

• Invalid file for Client SSL Certificate and/or Client SSL Key have been selected. In this case, select the correct file and try again. Refer to Adding a Connection on establishing connection.
• Identity of the object in the database could have been changed. In this case, check if the identity of the object has been changed and try again.
• You may have insufficient privileges. Contact the database administrator to obtain appropriate privileges.

Solution: This could happen due to any of the following reasons:

• Invalid file for Client SSL Certificate and/or Client SSL Key have been selected. In this case, select the correct file and try again. Refer to Adding a Connection on establishing connection.
• Identity of the object in the database could have been changed. In this case, check if the identity of the object has been changed and try again.
• You may have insufficient privileges. Contact the database administrator to obtain appropriate privileges.

"Failed to start the program, because MSVCRT100.dll is missing. Try reinstalling the program to solve the problem?"

Solution: This is because the operation requires gs_dump.exe to execute, and it requires the Microsoft VC runtime library msvcrt100.dll.

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

Solution: This could happen if the Profile folder under User Data folder is not available or modified manually. Make sure the Profile folder is present with correct naming convention.

Solution: This could happen if the Profile folder is missing under User Data folder or the folder has been modified. Make sure the Profile folder is present with correct naming convention.

Solution: This can happen if the Preferences folder is not present or renamed. Restart Data Studio to resolve this issue.

Solution: Restart Data Studio.

Solution: All previously edited data will be lost. Close the Edit Table Data window and perform the changes again.

A: This can happen if the settings in Preferences > Query Results is set to include column header. The selected cells includes the column header cells as well. Modify the settings to disable include column header option and try again.

A: Turning off Reuse Connection option creates new session. Created temp tables are available for current session only. Turn on Reuse Connection option to edit temporary tables. Refer to Managing SQL Terminal Connections for more information.

A: When same column is added more than once in multi-sort pop-up table, and Apply is clicked, a notification is displayed as follows. You need to click OK and select the correct column to sort.

A: Following notification is displayed. Once you select a valid column name and click Apply again, this notification is not displayed.

A: Cancelling queries might throw an error in console displaying the table name that is not created. In that case, you are advised to drop that particular table in order to perform operation on a table with the same name.

A: Follow the steps to generate the new security keys.

1. Delete the security folder from Datastudio folder > Userdata > Security folder.
2. Restart Datastudio.
3. New security folder is created and the keys will be regenerated.
4. Saved password will be lost and user should re-enter the password to logon to Datastudio.