Summary: Find practical answers to common GBase Database(GBase 8s) installation questions, including Linux prerequisites, startup failures, connection errors, character sets, reinstall issues, and installation methods.
Installing GBase Database(GBase 8s) on Linux is straightforward when the environment is properly prepared. This FAQ covers six common questions to help you avoid installation mistakes and troubleshoot problems efficiently.
Q1: What Should I Check Before Installing GBase Database?
Check these items before running the installer:
-
Hostname resolution: Review
/etc/hostsand confirm the system hostname withhostname. - SELinux and firewall: Check security policies and ensure required database ports are accessible.
-
Disk space: Run
df -hand pay particular attention to/tmpand the installation filesystem. - Installation permissions: Confirm the intended installation directory and execution users.
A few pre-installation checks can prevent unnecessary troubleshooting later.
Q2: Why Won't oninit Start?
A port conflict is one possible cause. Check whether the configured database port is already in use:
ss -tlnp | grep 9088
Replace 9088 with the actual configured port.
If an old GBase Database instance is occupying the port, identify the instance and shut it down safely before retrying. onmode -ky shuts down the associated instance, so don't run it without confirming the target.
If the port is available, inspect the startup error and online log for other causes.
Q3: Why Can't dbaccess Connect?
Check whether the hostname and connection settings in sqlhosts are consistent with the system hostname and /etc/hosts.
Also verify the configured port, instance status, and network access rules. A running database does not necessarily mean client connections are configured correctly.
Q4: Why Is Chinese Text Garbled?
Check the database locale and client character set configuration.
A typical installation may use en_US.8859-1 as its default locale, depending on the installation method and configuration. For Chinese-language production workloads, verify that the selected locale supports the required characters.
Plan the character set before creating production databases to avoid costly conversion or migration work later.
Q5: Why Does Reinstallation Fail?
Errors such as “version already exists” may indicate remnants of a previous installation.
Inspect the old installation directory and relevant temporary files under /tmp. Remove only confirmed leftovers after checking that they are not needed by another installation or running process.
Then retry the installation using the appropriate recovery procedure.
Q6: Which GBase Database Installation Method Should I Choose?
Choose the method based on your deployment scenario:
- Typical installation: Convenient for quick validation and basic testing.
- Manual installation: Offers greater control over installation paths and component selection.
- Silent installation: Uses a response file to automate repeatable or batch deployments.
For production environments, review the installation parameters and validate the resulting configuration rather than relying solely on default settings.
Final Thoughts
These six questions cover several recurring GBase Database installation and troubleshooting scenarios. Checking the environment first, validating configuration carefully, and documenting recovery steps can make deployments more consistent and easier to maintain.
Which installation issue would you add to this FAQ?
Top comments (0)