FAQ

Installation of the ODC client

1. Q: What items are pre-checked when I install the ODC client?

   A: The following items are pre-checked:

2. Q: How do I view the logs when the installation or startup of the ODC client fails?

   A: You can view the error information in the main.log file. The storage path of the file varies with the OS.

3. Q: What do I do when the installation or startup of the ODC client fails and an error message is returned indicating that a port conflict issue has occurred?

   A: You need to check the process that occupies port 8989, kill the process, and then reinstall or restart the ODC client. If you use ODC V2.3.0 or a later version, this problem will not occur because dynamic ports are used.

1. Q: What do I do when the installation or startup of the ODC client fails and an error message is returned indicating that the Java version is not supported?

   A: You can run the following command to check the Java runtime environment. We recommend that you install JDK 1.8.0 or a later version. If you have installed an earlier version, upgrade JDK, and then restart the computer and reinstall or restart the ODC client.

   java -version
   

1. Q: What do I do when a message appears indicating that the application failed the security check and cannot be installed when I am installing the ODC client?

   A: You can check the security settings of your device and modify the settings to allow the installation.

Connection information

1. Q: How do I back up the connection information in ODC?

   A: If you are using web ODC, you can directly migrate or back up the MetaDB that was created during ODC deployment. If you are using the ODC client, you can back up the odc2.0.mv.db file in the user directory. When you need to restore the connection, you can copy this file to the original directory.

2. Q: What do I do when the execution of an SQL query times out?

   A: When the execution of an SQL query times out, you can manually set the timeout value. In Advanced Configuration on the connection information editing page, you can set SQL Query Timeout Value to a larger value. This configuration item is supported in ODC since V2.2.0. If you are using an earlier version, upgrade to ODC V2.2.0 or a later version.

3. Q: What do I do when an error is returned indicating that the proxyro user does not exist?

   A: You need to set Query SYS Tenant View to a user with the permission to query sys tenant views in Advanced Configuration on the connection information editing page. This configuration item is supported in ODC since V2.2.0. If you are using an earlier version, upgrade to ODC V2.2.0 or a later version.

Command-line window

1. Q: After I connect to a database by using the ODC client on Windows, the connection is stuck and then disconnected, as shown in the following figure. How do I solve this problem?

   

   A: This problem is caused by the lack of the system library files of msvcp120.dll and msvcr120.dll. Please install the official Visual Studio patch.

Encoding

1. Q: What do I do to solve the problem of garbled display for the tenant that uses the GBK character set?

   A: If you are using ODC V2.2.0 or an earlier version, you can modify the values of the following three parameters to utf8mb4 , to ensure that a uniform character set is used in the session:

Data export and import

1. Q: My data import or export task failed, and the following exception is thrown: javax.crypto.BadPaddingException: Given final block not properly padded. What do I do?

   A: This exception is caused because the OBProxy password failed to be decrypted. You can solve this problem in the following three ways:

DDL statement display

1. Q: Why are the displayed statements truncated when I check the DDL statements of a view or table on the view or table management page?

   A: This is because that the DDL tab of the database object management page calls the content of the text field in the all_views table. In versions earlier than OBServer V2.2.70, if the content of the text field in the all_views table is too long, it will be truncated. This problem has been solved in OBServer V2.2.70 and later versions. You can run the SHOW CREATE VIEW/TABLE statement to directly query the complete structure statements of the target view or table.