GBase Database Typical Install: Frequently Asked Questions

The typical installation of GBase Database (GBase 8s) provides a quick way to create a usable database environment for development and feature validation. However, its default settings and configuration limits can raise questions for new users.

This FAQ covers six common questions about automatic instance creation, default connection settings, character sets, production suitability, and troubleshooting.

Q1: Does the GBase Database Typical Install Create an Instance Automatically?

Yes. In the typical installation workflow described here, the option to create an instance defaults to Yes. When that option remains enabled, the installer creates and initializes the instance as part of the installation process.

This saves time because you don't need to perform every instance-creation step manually.

After installation, verify that the instance started successfully before attempting to connect. A completed installation does not necessarily mean the database is currently online.

Q2: What Are the Default Instance Name and Port?

The typical installation described in this guide uses these defaults:

• Instance name: ol_gbasedbt1210
• Port: 30490

Applications and database utilities must use the correct instance name and connection settings.

These values may differ if the installation package, configuration, or installation method has been customized. Always verify the actual values on your server rather than assuming every GBase Database environment uses identical defaults.

Q3: What Is the Default Character Set?

The typical installation may use:

en_US.8859-1

This character set may be sufficient for some English-language validation tasks, but it may not meet the requirements of applications that process Chinese text.

If your testing involves Chinese data, check the database locale, client locale, and application encoding. Consider a manual or standard installation workflow that supports the required character-set configuration.

Do not assume that changing the terminal's display encoding alone will resolve a database character-set mismatch.

Q4: Can the Typical Installation Be Used for Production?

The official guidance described for this installation method does not recommend the typical installation for production use.

Its main advantage is speed: it simplifies setup and automatically creates an instance, making it useful for quick feature checks, SQL testing, and initial validation.

Production deployments require more deliberate planning, including resource sizing, security configuration, backup and recovery, monitoring, and operational procedures.

A practical approach is to use the typical installation for initial validation and choose an appropriate manual or standard installation method for production requirements.

Q5: How Can I Find the Instance Name and Port?

On a typical installation using the default paths and instance name, inspect the generated environment script:

grep GBASEDBTSERVER /opt/GBASE/gbase/ol_gbasedbt1210.ksh

Then check the service mapping:

grep ol_gbasedbt1210 /etc/services

The first command helps identify the configured server instance name. The second checks the service-to-port mapping.

Remember that /etc/services does not prove that the database is listening on the mapped port. If you need to verify the active listener, run:

ss -tlnp | grep ':30490'

The output depends on the actual system configuration and your permissions.

Q6: What Should I Check If the Connection Fails After Installation?

If a GBase Database connection fails, troubleshoot the problem in a consistent order:

1. Verify the instance name. Confirm that the client uses the correct GBASEDBTSERVER value.
2. Check the port. Ensure the client connection settings match the configured listener port.
3. Confirm the instance status. Run onstat - in the appropriate database environment and check whether the instance is online.
4. Review startup logs. If the instance is not online, inspect the relevant online.log for errors.
5. Check connectivity. If the instance is online, investigate listener configuration, network accessibility, firewall rules, and client settings.

Avoid changing multiple parameters at once. Confirming each layer separately makes it easier to identify the actual cause.

Final Thoughts

The typical installation of GBase Database is designed to reduce setup effort, not to eliminate configuration decisions.

Knowing the default instance name, port, character set, and automatic initialization behavior helps you troubleshoot common issues and choose the right installation method.

Use the typical installation when its defaults meet your validation needs. For production, plan the configuration around your application's requirements and operational standards.

What issue did you encounter first when installing GBase Database: connection settings, character encoding, or instance initialization?