TIL: How to Read GBase Database Package Names Before Installation

To successfully install a GBase Database package, it is crucial to examine the package filename carefully before initiating the installation process. The filename serves as a compatibility checklist that reveals essential details about the target CPU architecture, operating system family, and Python runtime environment.

When reviewing the package filename, take note of several key components. For instance, in the example package filename "GBase8a_MPP_Cluster-NoLicense-FREE-9.5.3.28.12-redhat8-aarch64.tar.bz2," the various segments provide valuable information. The "GBase8a_MPP_Cluster" indicates the product and deployment type, while "NoLicense-FREE" denotes the edition or licensing designation.

The "9.5.3.28.12" represents the release version, "redhat8" specifies the operating system package family, and "aarch64" identifies the CPU architecture.

Before proceeding with the installation, gather three critical pieces of information from the target server. First, use the command "uname -m" to determine the CPU architecture. Second, employ the command "grep -E '^(NAME|VERSION_ID)' /etc/os-release" to ascertain the operating system identity. Finally, execute "python -V" to identify the Python interpreter selected by the current shell.

Begin the compatibility check by examining the CPU architecture segment of the package filename. Common examples include "x86_64" for platforms like Intel, Hygon, and Zhaoxin; "aarch64" for platforms such as Kunpeng and Phytium; and "Loongson" or "Sunway" for architectures that may necessitate architecture-specific packages and separate arrangements.

To verify the target architecture, run the command "uname -m" on the target machine and compare the result with the architecture specified by the installation package. Incompatible architectures may result in errors like "cannot execute binary file."

Next, verify the operating system package family by confirming the OS identity and kernel using the commands "cat /etc/os-release" and "uname -r." Compare both results with the compatibility matrix for the specific GBase Database release. Be cautious not to assume that two operating systems are interchangeable simply because they share a common upstream distribution.

The package naming rules for a particular release may map supported distributions such as CentOS 8, openEuler, or Kylin V10 to specific package families like "redhat8," while supported CentOS 7 environments use "redhat7." Focus on the exact environment's support rather than assuming a universal rule for every distribution or minor version.

Another critical aspect to verify is the Python runtime compatibility. Some GBase Database installation scripts require Python 2, while others may necessitate Python 3. To check the Python version, run the commands "which python" and "python -V" under the account that will execute the installation. Ensure that the deployment procedure considers both root and the dedicated database user's environments, as the command resolution and documented installation entry point matter.

For the specific public FREE build mentioned in this example, the package is associated with the Python 2 runtime, while a Python 3 build may require a separate package request and licensing arrangement.

Lastly, it is crucial to understand that two GBase Database installation packages can share the same release version but target different environments. Therefore, selecting the newest version is not sufficient; a reliable selection process involves confirming the target CPU architecture, verifying the OS and kernel against the release compatibility matrix, and checking the required Python runtime and package variant.

Record the package filename and verification results for each node to facilitate future troubleshooting and deployment efforts.