GBase Database(GBase 8s) Character Set Troubleshooting: Fix Chinese Garbled Text

Chinese garbled text is a common issue when working with GBase Database(GBase 8s). The cause may be incorrect database locale settings, client encoding mismatches, terminal configuration, or data that was already corrupted during insertion. This guide covers practical checks to help identify and troubleshoot character encoding problems.

1. Understand Common Character Encoding Problems

Before changing any configuration, identify the symptom.

• Chinese text displays as question marks (**????**): The original characters may have been lost during data insertion or conversion.

• Chinese text displays as unreadable symbols: The client and database may be interpreting the same bytes differently.

• Only one application has the problem: The issue may be related to that application's connection or encoding configuration.

• Chinese text displays correctly in one tool but not another: Compare the client environments before changing database settings.

The key is to determine whether the problem occurs during storage, transmission, or display.

2. Check GBase Database(GBase 8s) Locale Settings

Start by checking the environment variables used by the database installation and client tools.

echo "$GBASEDBTDIR"
echo "$LANG"
echo "$LC_ALL"
echo "$CLIENT_LOCALE"
echo "$DB_LOCALE"

These values help identify the current environment configuration. Their availability and expected values depend on the installation and client setup.

You can also inspect the database environment using the relevant GBase Database(GBase 8s) monitoring commands available in your version.

Before changing locale settings, verify the database's existing locale and the locale expected by the application. Do not assume that changing an environment variable will convert existing data or repair text that was stored incorrectly.

3. Check the Client and Terminal Encoding

If Chinese text looks incorrect in a command-line session, check the terminal environment first.

locale
echo "$LANG"

Confirm that the terminal, client application, and database connection use compatible character encodings.

If the problem occurs only in one terminal or database client, test the same query using another client. This helps distinguish a display issue from a database storage issue.

4. Test Chinese Data

Use a small test table in a non-production database to check whether Chinese characters can be inserted, stored, and retrieved correctly.

CREATE TABLE charset_test (
    id INTEGER,
    name VARCHAR(100)
);

INSERT INTO charset_test VALUES (1, '中文测试');

SELECT * FROM charset_test;

If the returned text is incorrect, compare the result across different database clients.

Before running this test, confirm that the target database supports the intended characters and that your session is configured appropriately. Use an existing test table if you do not have permission to create tables.

A successful test does not necessarily prove that all existing data is correct. It only helps narrow down the problem.

5. Check Application and JDBC Connections

For Java applications, review the JDBC connection configuration and the encoding settings supported by your specific GBase Database(GBase 8s) driver.

For example, a connection URL may look like this:

jdbc:gbasedbt-sqli://192.168.1.100:9088/mydb:GBASEDBTSERVER=gbase01

Verify the correct JDBC URL format, connection properties, and supported character set settings against the documentation for your installed GBase Database(GBase 8s) driver. Do not copy connection properties from another driver or version without verification.

If command-line clients display Chinese correctly but a Java application does not, focus on the application's connection configuration and data handling before modifying the database.

6. Quick Troubleshooting Checklist

When troubleshooting Chinese garbled text in GBase Database(GBase 8s), check these items in order:

1. Confirm the database locale and supported character set.

2. Review CLIENT_LOCALE, DB_LOCALE, and related environment settings where applicable.

3. Check the terminal and client application's encoding.

4. Compare query results across different clients.

5. Test inserting and retrieving Chinese text in a test environment.

6. Review application and JDBC driver configuration.

7. Determine whether existing data was already corrupted before attempting any conversion or repair.

Avoid changing locale settings on a production system without understanding the impact and preparing a recovery plan.

Conclusion

Troubleshooting character encoding issues in GBase Database(GBase 8s) starts with identifying where the problem occurs: storage, connection, or display. Check locale settings, compare client behavior, and test with a small amount of Chinese text before making changes.

A systematic approach helps isolate the cause while reducing the risk of disrupting existing data or production services.