Need a quick test environment for GBase Database (GBase 8s)? The typical installation method provides a straightforward way to install the database and create an instance without manually configuring every setting.
It is particularly useful for developers, database administrators, and teams performing SQL tests, feature verification, or proof-of-concept (POC) evaluations.
In this guide, we'll walk through the installation process, review the default configuration, and show you how to verify the instance name and port after installation.
1. Run the GBase Database Typical Installation
On a system where the installation package has been prepared and its prerequisites are satisfied, navigate to the directory containing the installer and run ids_install.
For example:
cd /opt
sh ids_install
Follow the installation prompts and select the typical installation options:
1) Install type:
1 - Typical installation (default)
2) Create an instance:
1 - Yes - create an instance (default)
3) Expected user count:
1 - 1 - 100 (default)
2 - 101 - 500
3 - 501 - 1000
4 - 1000+
The exact prompts may vary depending on the installation package.
For a basic test environment, the default selections provide a convenient starting point. The installer can configure the environment and create a database instance automatically, reducing the amount of manual setup required.
After installation, verify that the instance was created successfully and is running before attempting to connect.
2. GBase Database Typical Installation: Default Parameters
A typical GBase Database installation may use the following default settings:
| Parameter | Default value |
|---|---|
| Installation path | /opt/GBASE/gbase |
| Instance name | ol_gbasedbt1210 |
| Port | 30490 |
| Character set | en_US.8859-1 |
These defaults help users get started quickly, but they should not be assumed to suit every environment.
For example, the selected port may conflict with an existing service, and the character set may not meet an application's language or data requirements.
Before using the environment for application testing, confirm that these settings match your test scenario.
3. How to Find the GBase Database Instance Name
After installation, you may need to confirm the instance name recorded in the generated environment configuration.
For the default installation path and instance shown above, run:
cat /opt/GBASE/gbase/ol_gbasedbt1210.ksh | grep GBASEDBTSERVER
This command searches the environment configuration file for the GBASEDBTSERVER setting.
The instance name is important when configuring client connections, setting environment variables, and performing database administration tasks.
If you used a different installation directory or instance name, adjust the file path accordingly.
4. How to Check the GBase Database Port
You can also inspect /etc/services for an entry associated with the instance:
grep 'ol_gbasedbt1210' /etc/services
This helps you locate the corresponding service entry and review the port information recorded there.
Keep in mind that /etc/services is a service-name mapping file; it does not prove that the database is currently listening on that port. For a complete verification, check the active instance configuration and confirm that the database listener is running.
This distinction is useful when troubleshooting connection failures after installation.
5. Is Typical Installation Suitable for Production?
The typical installation method is best treated as a convenient starting point for testing and initial validation.
It is useful for:
- Testing basic database functionality.
- Running SQL statements and checking compatibility.
- Exploring GBase Database features.
- Preparing a temporary development environment.
- Performing an initial POC before a larger deployment.
However, a successful installation does not automatically mean the database is production-ready.
The default character set, en_US.8859-1, may not be appropriate for applications requiring broader language support. Production deployments also need deliberate planning for security, memory allocation, storage, backup and recovery, monitoring, and workload-specific configuration.
Review the requirements for your GBase Database version and application before adopting the default settings in production.
Conclusion
The typical installation method makes GBase Database (GBase 8s) installation more accessible when you need a working test instance quickly.
By running ids_install, accepting the appropriate default options, and verifying the resulting instance configuration, you can move from installation to initial database testing with less manual effort.
The key is to use defaults for convenience without treating them as universal deployment recommendations.
For development, feature testing, and quick validation, typical installation is a practical starting point. For production, review and validate the configuration against your application's requirements before deployment.
Have you used the GBase Database typical installation method, or do you prefer to configure every parameter manually?
Top comments (0)