TIL: Fixing “Cannot Find onconfig File” in GBase Database

I recently assisted with diagnosing a GBase Database (GBase 8s) instance that was unable to start. The error message indicated a missing configuration file, but the actual issue stemmed from incorrect environment variables. Checking the environment variables should be one of the first troubleshooting steps after running oninit -ivy.

When the oninit -ivy command produced no output and the log reported "Cannot find onconfig file", it suggested an environment-related problem rather than a missing onconfig file. Despite the onconfig file being present, GBase Database could not find it due to misconfigured environment variables. GBase Database relies on environment variables to locate its installation directory, instance configuration, and connectivity files.

These variables include GBASEDBTDIR, indicating the installation directory; GBASEDBTSERVER, specifying the server name; ONCONFIG, pointing to the configuration file; GBASEDBTSQLHOSTS, defining the connection file; and locale settings. A common mistake leads to setting the GBASEDBTDIR variable incorrectly, often by adding an extra directory level.

To resolve this, verify that the GBase Database executable exists in the specified directory. Additionally, ensure the ONCONFIG variable matches the actual configuration file name located in the GBASEDBTDIR's /etc directory. The GBASEDBTSQLHOSTS variable should point to the correct sqlhosts configuration file, which may not exist if the intended location needs to be verified and recreated.

To expedite troubleshooting, a simple script can check environment variables and files. By confirming GBASEDBTDIR is accurate, oninit exists, ONCONFIG corresponds to the actual configuration filename, and GBASEDBTSQLHOSTS points to the right file, many GBase Database startup failures can be avoided.