GBase Database init.ini Parameters Explained: A Practical Configuration Guide

The key to a repeatable GBase Database (GBase 8s) one-click installation is understanding the configuration file behind it: PluginPak/init.ini.

This file centralizes important installation parameters, including the instance name, listening port, installation directory, database locale, and memory settings. By reviewing these values before installation, you can reduce configuration errors and make database deployments more consistent.

In this guide, we'll explain seven commonly used init.ini parameters, highlight potential pitfalls, and share practical recommendations for configuring GBase Database.

1. Example of a GBase Database init.ini Configuration

Here is an example configuration:

USER_OS_PWD    = GBase@123
GBASEDBTSERVER = gbase01
PORT           = 9088
GBASEDBTDIR    = /opt/gbase8s
DB_LOCALE      = zh_CN.utf8
SHM_SIZE       = 0
CHUNK_SIZE     = 5120

These values are examples, not universal production recommendations. Before using them, verify that the parameter names, supported values, units, and behavior match your specific GBase Database installation package.

Security note: The password shown above is for illustration only. Never reuse example credentials in a real deployment.

2. Understanding the Seven Key Parameters

USER_OS_PWD: Operating System User Password

This parameter specifies the password used by the installation script for the relevant operating system account, commonly gbasedbt.

Use a password that complies with your organization's security policy. Avoid hardcoded default credentials in scripts or configuration files shared across environments.

For automated deployments, consider how credentials will be supplied, protected, and rotated. Restrict access to configuration files that contain passwords.

GBASEDBTSERVER: Database Instance Name

GBASEDBTSERVER = gbase01

This parameter identifies the database server instance.

Choose a name that follows your organization's naming conventions and is consistent with the instance configuration used by client applications and database administration tools.

For example, using environment-specific names can make it easier to distinguish development, testing, and production instances.

Before installation, confirm that the instance name is valid for your package and does not conflict with an existing configuration.

PORT: Listening Port

PORT = 9088

The port determines the network endpoint used by clients to connect to the database instance, subject to the server's network configuration.

Before installation, check whether the port is already occupied and whether firewall rules permit the required connections.

After installation, verify the actual listener configuration rather than assuming that the value in init.ini guarantees successful connectivity.

GBASEDBTDIR: Installation Directory

GBASEDBTDIR = /opt/gbase8s

This parameter specifies the installation directory used by the setup process.

Choose a path that fits your filesystem layout, permissions, maintenance procedures, and storage capacity.

For production systems, consider separating database software from database data where supported by the deployment architecture. This can simplify capacity planning, maintenance, and recovery operations.

Do not assume that changing the installation directory automatically relocates every data file. Verify the actual data storage configuration separately.

DB_LOCALE: Database Locale and Character-Set Configuration

DB_LOCALE = zh_CN.utf8

The database locale affects how character data is interpreted and handled. The exact behavior depends on the locale configuration and the database environment.

Select a locale based on application requirements, supported character sets, client configuration, and the language of the data your system must process.

This decision deserves particular attention before creating a production database. Changing locale-related settings after deployment can require significant migration work, depending on the database architecture and the existing data.

Verify that the selected locale is supported by your GBase Database version and is compatible with the client applications.

SHM_SIZE: Shared Memory Configuration

SHM_SIZE = 0

This parameter controls the shared memory setting used by the installation script.

In the installation workflow described here, SHM_SIZE=0 indicates automatic sizing rather than unlimited memory. The script is described as calculating a value based on approximately one-quarter of available memory.

Because automatic sizing behavior can depend on the installer version and its implementation, confirm the calculation in your actual installation script before relying on it.

For production deployments, evaluate shared memory requirements against available system resources and expected workload. An explicit value may provide more predictable resource allocation when supported by the installer.

CHUNK_SIZE: Initial Storage Allocation

CHUNK_SIZE = 5120

This parameter controls a storage allocation size in the installation workflow described here. The example assumes a unit of megabytes, making 5120 equivalent to 5 GiB when interpreted as 5,120 MiB.

Confirm the exact unit and meaning in your installation package: a chunk allocation parameter should not automatically be interpreted as the total database storage capacity.

Before deploying, verify filesystem availability, storage layout, and the actual allocation behavior of the installation script.

3. Two Configuration Mistakes to Avoid

Mistake 1: Treating SHM_SIZE=0 as Unlimited Memory

A value of zero does not necessarily mean that the database can use unlimited memory.

In the workflow described above, zero represents automatic sizing. The actual memory allocation is determined by the script's implementation and the resources it detects.

Always verify the behavior before deploying to systems with different memory capacities.

Mistake 2: Choosing DB_LOCALE Without Planning Ahead

Locale selection affects compatibility between the database, stored data, and client applications.

Changing locale-related settings later can be expensive and may require data conversion, migration, or application changes.

For this reason, evaluate locale requirements before creating the database rather than treating the setting as an ordinary post-installation adjustment.

4. A Practical Pre-Installation Checklist

Before running the GBase Database one-click installation script, review the following:

• [ ] Confirm that the instance name follows your naming convention.
• [ ] Verify that the selected port is available.
• [ ] Check installation-directory permissions and disk capacity.
• [ ] Confirm that the database locale meets application requirements.
• [ ] Review shared memory settings against system resources.
• [ ] Verify the storage allocation parameters and their units.
• [ ] Protect credentials and remove insecure example passwords.

Once the configuration has been reviewed, run the installation command appropriate to your package:

sh install_init.sh

After the script finishes, verify the installation result, instance status, listening port, and relevant configuration values. A successful script execution should be followed by actual connectivity and functionality checks.

Conclusion

Understanding PluginPak/init.ini is essential to making GBase Database installation repeatable and predictable.

The seven parameters covered here affect account credentials, instance identity, network connectivity, installation paths, locale configuration, memory sizing, and storage allocation.

The main principle is simple: a one-click installer automates execution, but it does not replace configuration planning.

Review the parameters, verify the script's behavior, and validate the resulting instance. That is how you turn a convenient GBase Database installation process into a controlled and maintainable deployment workflow.