Today, I ran into a familiar problem: dbaccess couldn't connect to GBase Database(GBase 8s). The culprit wasn't a password or an obvious network failure. The hostname configured in sqlhosts didn't match the hostname resolution settings in /etc/hosts.
Here's how I tracked it down.
3 Quick Checks for GBase Database Connection Issues
1. Check the hostname in sqlhosts
cat "$GBASEDBTDIR/etc/sqlhosts.ol_gbasedbt1210"
Look at the hostname field in the connection entry. Make sure it matches the intended server address and instance configuration.
2. Check the system hostname
hostname
Compare the output with the hostname used in sqlhosts. A mismatch is worth investigating, especially after installation or hostname changes.
3. Check hostname resolution
cat /etc/hosts
Confirm that the hostname can resolve to the correct IP address. You can also test resolution directly:
getent hosts your-hostname
Replace your-hostname with the hostname configured in sqlhosts.
The key isn't that all three files or commands must display exactly the same text in every setup. It's that the hostname used by the connection configuration must resolve correctly to the intended server.
Why This Matters
When troubleshooting a GBase Database connection failure, it's tempting to start changing passwords, firewall rules, or network settings.
But if sqlhosts points to a hostname that resolves incorrectly—or doesn't resolve at all—the connection can fail before those other factors become relevant.
Start with the connection entry and hostname resolution. They're quick to verify and can save you from unnecessary troubleshooting.
TIL takeaway: When dbaccess reports a connection error, check sqlhosts and hostname resolution first. If they look correct, move on to instance status, port configuration, network reachability, and credentials.
One small configuration mismatch can look like a much bigger database problem.
