5 Common Reasons Why GBase Database(GBase 8s) Cannot Connect After Installation

Your GBase Database(GBase 8s) instance is online, but dbaccess or a remote client still cannot connect. Before reinstalling the database, check these five common causes: incorrect sqlhosts configuration, firewall restrictions, port conflicts, server name mismatches, and client connection settings.

This troubleshooting guide explains what to check first and how to narrow down GBase Database(GBase 8s) connectivity issues efficiently.

1. Incorrect Hostname in sqlhosts

Typical symptom: Local connections work, but remote connections fail.

The sqlhosts file defines connection information for a database server, including its server name, connection protocol, host, and port.

For example:

gbase01 onsoctcp 192.168.1.100 9088

If the configuration uses localhost or 127.0.0.1, remote clients may be unable to reach the intended network endpoint.

What to check:

• Verify the hostname or IP address in the relevant sqlhosts entry.
• Confirm that the address is reachable from the client machine.
• Check that the server is listening on the expected interface and port.

Use the actual network address and connection settings for your environment. Avoid changing configuration or restarting the instance until you have identified the cause.

2. Firewall Blocking the Database Port

Typical symptom: The GBase Database(GBase 8s) instance is online, but remote connections time out.

A running database does not guarantee that network traffic can reach it. The operating system firewall, network firewall, or cloud security rules may block the database listener port.

Check the firewall status and test connectivity from the remote client:

systemctl status firewalld

nc -vz 192.168.1.100 9088

Replace the example IP address and port with your actual server settings.

If the connection is blocked, review the applicable firewall rules and allow only the required source addresses and destination port. Avoid disabling the firewall as a troubleshooting shortcut.

3. Database Port Conflict

Typical symptom: The instance fails to start correctly, or the expected database port is unavailable.

Another service may already be using the configured port.

Check which process is listening:

ss -lntp | grep ':9088'

Alternatively, use lsof if it is installed.

If a conflict exists, identify the process before taking action. Do not stop an unrelated service simply because it occupies the port.

Depending on your environment, you may need to resolve the conflict or configure GBase Database(GBase 8s) to use an available port. Ensure that the server configuration and client connection entries remain consistent.

4. Server Name Mismatch Between onconfig and sqlhosts

Typical symptom: The instance appears to be running, but client connections fail with a server name or connection configuration error.

GBase Database(GBase 8s) uses instance configuration and connection definitions that must agree with the intended server name.

Review the relevant settings:

grep -E 'DBSERVERNAME|DBSERVERALIASES' \
  "$GBASEDBTDIR/etc/onconfig.gbase01"

cat "$GBASEDBTSQLHOSTS"

The exact configuration file names depend on your installation.

Verify that the server name requested by the client corresponds to a valid server configuration and that the associated connection protocol, host, and port are correct.

Do not change instance identifiers blindly. Confirm the active configuration before making adjustments.

5. Client-Side sqlhosts Misconfiguration

Typical symptom: The database is accessible from the server itself, but a remote application or client cannot connect.

The client may be using a different sqlhosts file or an outdated connection definition.

Check the active environment and client configuration:

echo "$GBASEDBTSQLHOSTS"

Then inspect the file referenced by that variable and verify the server entry.

For remote connections, confirm that:

• The client uses the correct database server name.
• The hostname or IP address is reachable.
• The protocol and port match the server configuration.
• Client environment variables and driver settings are appropriate for the installed version.

A correct server-side configuration cannot compensate for an incorrect client connection definition.

Quick GBase Database(GBase 8s) Diagnostic Script

This basic script checks instance status, the expected listening port, and the configured sqlhosts file.

#!/bin/bash

echo "=== GBase Database(GBase 8s) Diagnostics ==="

echo
echo "1. Instance status"
if command -v onstat >/dev/null 2>&1; then
    onstat - 2>&1 | head -5
else
    echo "onstat not found; check the database environment."
fi

echo
echo "2. Listening port"
if command -v ss >/dev/null 2>&1; then
    ss -lnt | grep ':9088' || echo "Expected port not found."
else
    echo "ss command unavailable."
fi

echo
echo "3. sqlhosts configuration"
if [[ -n "${GBASEDBTSQLHOSTS:-}" &&
      -r "$GBASEDBTSQLHOSTS" ]]; then
    cat "$GBASEDBTSQLHOSTS"
else
    echo "sqlhosts path is unset or file is unreadable."
fi

echo
echo "4. Firewall status"
if command -v systemctl >/dev/null 2>&1; then
    systemctl is-active firewalld 2>/dev/null ||
        echo "firewalld inactive or unavailable."
fi

echo
echo "5. Next step"
echo "Test connectivity from the actual client."
echo "Review database and client logs for detailed errors."

Save the script as check_gbase_connection.sh and run it under an account with the appropriate permissions.

This is a preliminary diagnostic tool, not a complete connection test. Replace port 9088 with the actual configured port. A listening port alone does not prove that database authentication or SQL queries will succeed.

Final Thoughts

When GBase Database(GBase 8s) cannot connect after installation, start with the instance state, then check the listener, network connectivity, sqlhosts, and client configuration. Use the exact error message to narrow down the cause before changing settings.

The key takeaway: An online database instance is only the first step. Reliable connectivity requires consistent server configuration, an accessible network endpoint, and correctly configured clients.

Systematic troubleshooting is usually more effective than reinstalling GBase Database(GBase 8s) without identifying the underlying problem.