Installing GBase Database(GBase 8s) for the first time can raise questions about Linux users, environment variables, character sets, network connections, and instance startup. This FAQ answers 10 common installation questions and explains how to troubleshoot typical issues without making risky configuration changes.
Q1: Can I install GBase Database(GBase 8s) as the root user?
Answer: Yes. In a typical GBase Database(GBase 8s) installation workflow, use root to install the database software and perform system-level configuration, then switch to the dedicated gbasedbt account to initialize and run the database instance.
Typical Workflow
Step 1: Install the software as root.
Run the installation program according to the instructions provided with your GBase Database(GBase 8s) installation package.
Step 2: Prepare the database environment.
Verify that the required directories, ownership, permissions, and environment variables are configured correctly for the gbasedbt account.
Step 3: Switch to the database user.
su - gbasedbt
Step 4: Initialize the instance.
Run the documented instance initialization command under the gbasedbt account. For example, oninit -ivy may be used when initializing a new instance, provided this matches the procedure for your version and configuration.
Important: Do not run instance initialization commands against an existing database as a troubleshooting shortcut. Confirm the instance state and follow the appropriate startup or recovery procedure.
Q2: Why can't I connect when sqlhosts contains localhost?
Answer: The cause depends on the connection protocol, server configuration, and how the hostname resolves.
In GBase Database(GBase 8s), the sqlhosts entry specifies the server name, connection protocol, host, and service or port. For TCP connections, an entry may look like this:
gbase01 onsoctcp 192.168.1.100 9088
This is an illustrative example, not a universal configuration. Replace the server name, address, and port with the values used by your installation.
When troubleshooting, verify that:
- The client uses the expected server name.
- The host resolves to the correct address.
- The configured protocol matches the intended connection method.
- The server is listening on the configured port.
- Firewall rules allow the connection when connecting remotely.
localhost does not automatically mean a connection will fail. Check the actual sqlhosts configuration and connection error before changing it.
Q3: Can I change the character set after installation?
Answer: It depends on which character set or locale setting you need to change.
GBase Database(GBase 8s) environments may use settings such as DB_LOCALE and CLIENT_LOCALE to control database and client character handling. These settings serve different purposes, and changing a client environment variable does not convert existing database data.
Before making changes:
- Identify the database's current locale and the application's expected encoding.
- Check the requirements for the specific database and client version.
- Test Chinese text insertion and retrieval in a non-production environment.
- Back up important data before performing any migration or conversion.
If an existing database must use a different database locale, creating a new database with the intended configuration and migrating the data may be necessary. Confirm the supported migration procedure first.
Do not assume that changing DB_LOCALE or CLIENT_LOCALE alone will convert an existing database. Choose the locale based on the application's requirements and the character sets supported by the installation.
Q4: Why does oninit produce no obvious output?
Answer: Limited terminal output does not necessarily mean that startup has failed.
Start by checking the instance status:
onstat -
Then inspect the relevant environment variables:
echo "$GBASEDBTDIR"
echo "$ONCONFIG"
If the expected environment is configured, inspect the message log. For example, some installations use a log under the database installation's temporary directory:
tail -50 "$GBASEDBTDIR/tmp/online.log"
The actual log location depends on the configuration. Check the configured message-log path if this file does not exist.
Also verify that you are using the correct database account and configuration file. Avoid repeatedly running initialization commands to troubleshoot a startup problem; first determine the instance's current state and read the error messages.
Q5: What is the default port for GBase Database(GBase 8s)?
Answer: Port 9088 is commonly seen in GBase 8s examples, but the actual port depends on the instance configuration.
Check the configured service or port in sqlhosts and the corresponding network configuration. You can inspect listening TCP ports with:
ss -lntp
If you need to change the port, follow the configuration procedure for your version and ensure the client connection settings match the server.
Changing a port may also require updates to firewall rules, monitoring systems, and application connection strings. Do not assume that every installation uses the same port.
Q6: What should I do if dependency installation fails?
Answer: First, identify the missing package or library instead of installing a large, generic list of dependencies.
On a compatible RPM-based Linux system, you can check whether package repositories are available with:
yum repolist
If the installer reports a missing library, check the exact package name and version required by your GBase Database(GBase 8s) release.
Common troubleshooting steps include:
- Confirming that the operating system version is supported.
- Checking whether the required repositories are enabled.
- Verifying package names for the current distribution.
- Checking library architecture and version compatibility.
- Using approved offline RPM packages when the environment has no internet access.
Do not assume that packages such as Java, development libraries, or terminal libraries are required for every installation. Follow the prerequisites for your specific release.
Q7: Which operating systems does GBase Database(GBase 8s) support?
Answer: Supported operating systems depend on the product release, package, CPU architecture, and vendor certification.
Before installing GBase Database(GBase 8s), verify the official compatibility information for your exact version. Check:
- Linux distribution and release
- CPU architecture
- Required system libraries
- Kernel and runtime prerequisites
- Supported deployment and maintenance configurations
Do not choose an operating system solely because an older installation guide uses it. A distribution that worked for a previous release may not be supported by a newer package.
For production systems, use a supported configuration and confirm the relevant requirements with the official product documentation or vendor support.
Q8: How can I verify that the installation succeeded?
Answer: Verify the instance state, network listener, and database connectivity separately.
Step 1: Check the instance status.
onstat -
Review the output to determine whether the instance is online and operating as expected.
Step 2: Check the network listener.
ss -lntp
Confirm that the expected port is listening. A listening port alone does not prove that database authentication and SQL queries work.
Step 3: Test a database connection.
Use the supported client for your installation, such as dbaccess where available, and connect to the intended database or a designated test database.
Verify that you can execute a simple query with the expected account and permissions.
A successful installation check should cover all three areas: instance status, network connectivity, and an actual database session.
Q9: Where can I download the GBase Database(GBase 8s) installer?
Answer: Start with the official GBase website:
Check the product documentation and download resources available for your version. Access requirements may vary.
Before downloading, confirm the following:
- The correct GBase Database(GBase 8s) product and release
- The target operating system
- The CPU architecture
- Installation prerequisites
- Package integrity and any vendor-provided verification instructions
Keep the installer and its corresponding documentation together so that the installation procedure can be repeated consistently.
Q10: How do I configure automatic startup after installation?
Answer: Use the startup mechanism documented for your GBase Database(GBase 8s) release and operating system.
On a system using systemd, database startup may be integrated with a service unit or a vendor-provided startup script. However, the correct service configuration depends on how the instance starts, the required environment variables, and the expected shutdown procedure.
Before enabling automatic startup, verify:
- The correct database service account.
- The required environment variables and configuration files.
- The documented startup and shutdown commands.
- Service dependencies and startup ordering.
- Behavior after a restart or unexpected shutdown.
Do not copy a generic systemd template into production without validating its ExecStart, ExecStop, process type, and environment settings. An incorrect shutdown command or service definition can interrupt database operations or cause startup failures.
Test automatic startup and shutdown in a non-production environment first, then document the verified procedure for your deployment.
Final Thoughts
Most GBase Database(GBase 8s) installation problems become easier to diagnose when you verify the environment before changing configuration. Check the database account, locale settings, sqlhosts, instance status, and message logs systematically.
For beginners, three habits are especially valuable:
- Follow the documentation for the exact product version.
- Verify each installation stage before moving to the next.
- Diagnose the underlying error before reinstalling or modifying database files.
A careful installation and verification process helps reduce troubleshooting time and makes future deployments more predictable.
Top comments (0)