GBase Database: Installed Successfully but Can't Connect? 4 Troubleshooting Steps

You have installed GBase Database (GBase 8s) using the one-click installation script. The installer reports success, but when you try to connect with dbaccess or a JDBC client, the connection fails.

What went wrong?

A successful installation does not necessarily mean the database instance is running, the connection parameters are correct, or the network is ready for client access.

Instead of reinstalling the database immediately, follow these four troubleshooting steps to identify the cause.

1. Check Whether the Database Instance Is Running

Start by checking the instance status. On the database server, run the following command using the appropriate GBase Database environment:

onstat -

This command displays information about the current instance.

If the output indicates that shared memory is not initialized, the instance may not have started successfully.

How to fix it:

Check the installation output and relevant database logs for startup errors before attempting to start the instance.

If the instance has not been initialized and your installation procedure requires initialization, follow the documented initialization process. For an existing, initialized instance that is stopped, use the appropriate startup procedure for your environment.

For example:

oninit

Use initialization options such as -i only when explicitly required by the installation procedure. Initializing an existing instance incorrectly can have serious consequences.

Once startup completes, run onstat - again to verify the instance status.

2. Verify the Instance Name

The instance name is another common source of connection problems.

In the GBase Database one-click installation workflow, the GBASEDBTSERVER parameter in init.ini specifies the instance name. For example:

GBASEDBTSERVER = gbase01

If the configured instance name is gbase01, make sure your environment and client connection properties reference the intended instance.

You can inspect the relevant environment variable with:

echo "$GBASEDBTSERVER"

If the output is empty or differs from your expected instance name, check whether you have loaded the correct account profile and environment configuration.

You can also try launching dbaccess in interactive mode:

dbaccess

The exact connection workflow depends on your environment and whether you are connecting locally or to a remote database.

3. Compare the Port with the Generated JDBC URL

After a successful one-click installation, the console may print a JDBC URL similar to this:

jdbc:gbasedbt-sqli://0.0.0.0:9088/gbasedb:GBASEDBTSERVER=gbase01

This example contains three useful values:

• Port: 9088
• Database name: gbasedb
• Instance name: gbase01

Compare these values with your actual installation configuration and application settings.

If the port in your application differs from the port configured for GBase Database, the connection may fail or reach an unrelated service.

You can check whether port 9088 is listening with:

ss -tlnp | grep ':9088'

If nothing is returned, investigate whether the instance is running, whether it is listening on a different address or port, and whether startup completed successfully.

Important: 0.0.0.0 is generally a bind address, not a destination address for remote clients. Use the database server's reachable IP address or hostname in your JDBC configuration.

4. Verify the Database Environment Variables

Incorrect or missing environment variables can prevent database utilities from finding the expected installation files or instance configuration.

Check these variables:

echo "$GBASEDBTDIR"
echo "$GBASEDBTSERVER"
echo "$ONCONFIG"

Confirm that:

• GBASEDBTDIR points to the correct installation directory.
• GBASEDBTSERVER matches the intended instance name.
• ONCONFIG references the correct configuration file for the instance.

If a value is missing or incorrect, load the appropriate environment profile for the database account and verify the settings against your installation documentation.

Do not assume that variables configured in one shell are automatically available to another user, terminal session, service, or application process.

A Quick Troubleshooting Checklist

When GBase Database installs successfully but connections fail, check the following in order:

1. Instance status: Does onstat - show a running instance?
2. Instance name: Does GBASEDBTSERVER match the intended instance?
3. Port: Is the configured port correct and listening?
4. Environment: Are GBASEDBTDIR, GBASEDBTSERVER, and ONCONFIG set correctly?

If all four checks pass, investigate the specific connection error, authentication settings, database existence, firewall rules, and JDBC driver configuration.

Final Thoughts

For GBase Database (GBase 8s), an installation success message confirms that the installation process completed its reported tasks. It does not guarantee that every connection requirement has been satisfied.

Start with onstat -, verify the instance name, compare the configured port with the JDBC URL, and