A manual installation of GBase Database (GBase 8s) gives administrators greater control over installation paths, component selection, and instance configuration. This makes it a useful approach when preparing an environment that must follow specific deployment requirements.
Unlike a typical installation, which prioritizes speed and automatic setup, a custom installation allows you to make more explicit decisions about the database software environment.
This guide walks through the main steps for manually installing GBase Database on Linux, from preparing the operating-system account to running the installation wizard and planning instance initialization.
1. Create the gbasedbt User and Group
First, check whether the gbasedbt group and user already exist.
getent group gbasedbt
id gbasedbt
If they do not exist, create them:
groupadd gbasedbt
useradd -g gbasedbt gbasedbt
passwd gbasedbt
The gbasedbt account is commonly used to own and operate the database instance. Follow the account and privilege requirements documented for your GBase Database release.
Important: The software installation and database instance initialization are distinct operations. Some installation procedures require the root account to install the software, while instance initialization and database operations should use the designated database account. Follow the instructions for your specific package rather than running every command as the same user.
If the account or group already exists, verify its configuration instead of creating duplicates.
2. Create the Installation Directory
Create the target installation directory:
mkdir -p /opt/GBASE/gbase
Set ownership according to the installation procedure:
chown gbasedbt:gbasedbt /opt/GBASE/gbase
Verify the directory permissions:
ls -ld /opt/GBASE/gbase
The example uses /opt/GBASE/gbase as the installation path. You can select a different path if your deployment requirements call for it and the installer supports that choice.
Before proceeding, confirm that the target filesystem has sufficient space and that the required accounts have the appropriate permissions.
3. Extract the GBase Database Installation Package
Move to the directory containing the installation archive. For example, if the package is stored under /opt:
cd /opt
tar -vxf GBase8sV8.8_AEE_3.5.1_3_6a4e30_RHEL6_x86_64.tar
Replace the archive name with the exact filename of your downloaded package.
After extraction, inspect the resulting files:
ls -l
Locate the installation script, typically named ids_install, and check the package documentation for any release-specific prerequisites.
The archive name in this example identifies a particular package build. Confirm that your operating system and CPU architecture are supported by that release before installing it.
4. Start the Installation Wizard
Run the installer using the privileges required by your package's installation guide:
sh ids_install
Follow the prompts carefully. The exact wording and option numbers may vary by release.
The main decisions generally include the following.
Accept the License Agreement
Review the license terms and accept them if you agree to proceed.
Specify the Installation Path
The example uses:
/opt/GBASE/gbase
Confirm that the path matches your directory preparation and deployment plan.
Select Custom Installation
Choose the custom installation option when you need to select individual components and control the installation configuration.
In the example workflow, this is option 2. Verify the actual menu displayed by your installer before selecting it.
Select Functional Components
Choose the components required by your intended deployment.
Depending on the package, these may include the database server, administrative utilities, backup and restore tools, language support, and replication functionality.
Installing every component is not always necessary. Review functional requirements and dependencies before making your selections.
Configure Role Separation
Check the role-separation setting and decide whether it is required by your security or administration model.
The available options depend on the product version and installation package.
Decide Whether to Create an Instance
In the manual installation workflow described here, instance creation is not performed automatically by default.
This allows you to treat software installation and instance initialization as separate stages. Verify the installer's behavior rather than assuming the same defaults apply to every installation method.
5. Prepare for Instance Initialization
After the software installation completes, the database instance still needs to be configured and initialized if the installer did not create it.
Before initialization, review the instance configuration requirements.
Key items to plan include:
- Instance name: Choose a name consistent with your environment's naming conventions.
-
onconfig: Review the configuration parameters required for the intended workload. -
sqlhosts: Configure the connectivity information required by your client and server setup. - Port allocation: Confirm that the selected port is available and consistent with the listener configuration.
- Character set and locale: Choose settings compatible with your application and data requirements.
- Storage and resources: Plan memory, disk layout, and other parameters according to the expected workload.
Do not copy configuration values blindly from another GBase Database instance. Parameters that work for a development machine may be inappropriate for a production server.
Once the configuration is prepared, follow the initialization procedure documented for your GBase Database release. Verify the instance status and review the startup logs before attempting application connections.
6. Verify the Installation
After installation and instance initialization, perform basic checks to confirm that the environment is ready for further testing.
Check the installed files and ownership:
ls -ld /opt/GBASE/gbase
Check the database instance status in the appropriate environment:
onstat -
If the instance is online, verify connectivity using the intended instance name and connection settings.
If startup fails, review the relevant online.log and confirm that the environment variables, configuration files, permissions, and resource settings are correct.
Successful software installation alone does not guarantee that the database instance is running or ready for application use.
Conclusion
Manual installation of GBase Database gives administrators more control over software placement, component selection, and subsequent instance configuration.
The process involves preparing the operating-system account, creating the installation directory, extracting the package, selecting custom installation options, and planning instance initialization separately.
For production deployments, this control is valuable when combined with documented configuration standards, security reviews, and workload-specific testing.
The key principle: Install the components you need, plan the instance before initializing it, and verify the running environment before putting it into service.
Top comments (0)