Pre-installation Tasks
This chapter describes how to perform pre-installation tasks such as verifying hard disk space, installing JDK, and setting kernel parameters for each operating system.
Overview
Before installing Tibero, perform the following tasks.
Verify available disk
Install JDK
Install OS-specific packages
Set OS-specific kernel parameters (shell limits parameters)
Set NTP server
Verify host name, port number, system account, and localhost
Verifying Available Disk Space
Although it slightly depends on which platform you use, installing Tibero requires at least 2 GB of free HW space. This is the minimum space needed to create the database after installation.
For more information about hardware requirements, refer to “System Requirements”.
To verify available free disk space, run the df command on a Unix system.
Installing JDK
To install Tibero, JDK 1.5.17 or a later version must be installed.
You can download JDK from the following link.
If your system does not use Oracle's JDK, find a compatible JDK for your system. (For example, you can download JDK from IBM for AIX.)
You can find instructions to install JDK for different systems at the following link.
🔎 Go to JDK installation for each system
JDK 1.9 or higher versions are not supported currently.
To install a specific vendor's JDK, refer to the respective installation guide provided by the vendor.
Installing Packages
This section describes the packages required for each operating system.
Packages of the following versions or higher must be installed in each package, and the package name or version may differ for each OS and version.
Linux
gcc-3.4.6-11
gcc-c++-3.4.6-11
libgcc-3.4.6-11
libstdc++-3.4.6-11
libstdc++-devel-3.4.6-11
libaio-0.3.105-2
libaio-devel-0.3.105-2
pstack
glibc
Solaris
libCrun.so.1 (SUNW_1.6)
pstack
AIX
procstack
For RHEL 8.1 or higher versions, the following packages must be installed.
Platform
Packages
Linux
ibnsl.so.1
libncurses.so.5
Setting Parameters
The following describes how to set kernel and shell limits parameters for each operating system.
After setting all required parameters, reboot the system.
Linux
Kernel and shell limits parameters for Linux are as follows:
Kernel parameters
Configuration file
Setting values
kernel.sem
10000, 32000, 10000, 10000
kernel.shmall
ceil (shmmax/PAGE_SIZE)
kernel.shmmax
Half of physical memory (byte)
kernel.shmmni
4096
fs.file-max
67108864
fs.aio-max-nr
1048576
net.ipv4.ip_local_port_range
1024 65000
net.core.rmem_default
262144
net.core.wmem_default
262144
net.core.rmem_max
67108864
net.core.wmem_max
67108864
Shell limits parameter
Configuration file
Setting values
nofile
Set to at least MAX_SESSION_COUNT / WTHR_PROC_CNT.
Soft Limit: 65536
Hard Limit: 65536
nproc
Set to at least MAX_SESSION_COUNT+10000.
Soft Limit: 65536
Hard Limit: 65536
For RHEL 7.2 or higher versions, the following kernel parameter settings are required.
Configuration file
Setting values
RemoveIPC
No
Running SELinux in enforce mode may cause a process failure. Therefore, enforce mode is not recommended for Tibero.
Solaris
Kernel and shell limits parameters for Solaris are as follows:
Kernel parameters
Configuration file
Setting values
project.max-sem-ids
Based on the _SEM_ARR parameter value, set to one of the following.
Y: Server's semaphore count + MAX_SESSION_COUNT + 500
N: Greater than or equal to the system default value
process.max-sem-nsems
10000
process.max-sem-ops
200
project.max-shm-memory
4294967295 (half of physical memory)
project.max-shm-ids
100
project.max-lwps
MAX_SESSION_COUNT+10000 or higher
Shell limits parameter
Configuration file
Setting values
nofile
Soft Limit : 65536
Hard Limit : 65536
nproc
Soft Limit : 65536
Hard Limit : 65536
Starting from Solaris 10, it is recommended to manage parameters at the user level by creating a project.
The following example configures parameters for a specific user.
Create a project.
Configure parameters.
Reconnect as the user.
AIX
Kernel and shell limits parameters for AIX are as follows:
Kernel parameters
The only kernel parameter that needs to be changed in the AIX environment is maxuproc, which can be changed using smitty or chdev. The AIX kernel dynamically allocates and reallocates resources to predefined limits as needed, therefore no additional kernel parameter settings are required.
maxuproc
Number of processes started when Tibero boots.
Therefore, the value must be greater than the number of processes to be started by the DB installation user. (Recommended value: 16384)
Refer to the following when calculating the appropriate values depending on your operating environment.
User setting: Worker process counts + Background process counts + System process counts + Additional (100)
Shell Limits parameters
Configuration file
Configuration values
Soft FILE size
-1 (Unlimited)
Soft CPU time
-1 (Unlimited)
Soft DATA segment
-1 (Unlimited)
Soft STACK size
-1 (Unlimited)
Soft Real Memory size
-1 (Unlimited)
Setting NTP Server
During a database operation, somtimes the system clock can be set backwards by the xntpd daemon, causing invalid data output. To prevent this error, synchronize the system clock and then restart the daemon by using the '-x' option.
If you want to apply the same option for system restart as well, remove the comment mark for the following in "/etc/rc.tcpip".
Others
The host name, port number, system account, and localhost must be verified before installing Tibero.
Host name
Verify the host name for requesting a license. Check the /etc/hosts file, or run the following command on the console to verify it.
Port number
Verify the port number when Tibero starts. The default value is 8629.
System account
Verify the system account with which Tibero is installed and operated.
localhost
Use the ping command to verify that the localhost is configured correctly. If it is not configured correctly, modify the /etc/hosts file.
Last updated