Docs Home

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.

🔎 Go to JDK Download

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.

Platform
Packages

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

/etc/sysctl.conf

  • Setting values

Kernel Parameter
Value

kernel.sem

The minimum setting values for SEMMSL, SEMMNS, SEMOPM, and SEMMNI are as follows: – SEMMSL : 2 / Recommnded value : (Total Tibero threads) x 2 – SEMMNS : (Total Tibero thread number) x 2 – SEMOPM : 2(=SEMMSL) / Recommnded value : (Total Tibero threads) x 2 – SEMMNI : (Total Tibero threads)

The maximum values are not limited, and it is recommended to set them high enough.

kernel.shmall

ceil (shmmax/PAGE_SIZE)

kernel.shmmax

Half of physical memory (byte)

kernel.shmmni

4096

fs.nr_open

nofile parameter value or higher

fs.file-max

(nofile parameter) x (WTHR_PROC_CNT + PEP_PROC_CNT) or 67108864

fs.aio-max-nr

1048576

net.ipv4.ip_local_port_range

1024 65000

net.core.rmem_default

The maximum value between 262144 and the current OS setting

net.core.wmem_default

The maximum value between 262144 and the current OS setting

net.core.rmem_max

The maximum value among 67108864, the current OS setting, TCP_RCVBUF_SIZE and _INC_TCP_RCVBUF_SIZE

net.core.wmem_max

The maximum value among 67108864, the current OS setting, TCP_RCVBUF_SIZE and _INC_TCP_RCVBUF_SIZE

Shell limits parameter

  • Configuration file

/etc/security/limits.conf

  • Setting values

Parameter
Description

nofile

Set to (WTHR_PER_PROC * ((total data files in db) + 15)) + (tbsvr process count + 5) + 100, or 3000000.

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

/etc/systemd/logind.conf

  • Setting values

Kernel Parameter
Value

RemoveIPC

No

Note

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

/etc/system

  • Setting values

Kernel Parameter
Value

project.max-sem-ids

(Total Tibero threads) x 2

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

/etc/system

  • Setting values

Kernel Parameter
Value

nofile

Set to (WTHR_PER_PROC * ((total data files in db) + 15)) + (tbsvr process count + 5) + 100, or 3000000.

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.

  1. Create a project.

# projadd -c "tibero" 'user.tibero'

  1. Configure parameters.

# projmod -sK "project.max-shm-memory=(privileged,4294967295,deny)" user.tibero

  1. Reconnect as the user.

# prctl -n project.max-shm-memory -i project user.tibero 
project: 100: user.tibero
NAME	PRIVILEGE	 VALUE	 FLAG	ACTION    RECIPIENT
project.max-shm-memory
        privileged     4.00GB       -   deny              -
        system         16.0EB     max   deny              -

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.

# Check the current configuration.
# lsattr -E -l sys0 -a maxuproc
maxuproc 1024 Maximum number of PROCESSES allowed per user True

# Change the maxuproc value.
# chdev -l sys0 -a maxuproc=16384

Parameter
Description

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

/etc/security/limits

  • Configuration values

Parameter
Recommended Value

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.

# stopsrc -s xntpd
# startsrc -s xntpd -a "-x"

If you want to apply the same option for system restart as well, remove the comment mark for the following in "/etc/rc.tcpip".

start /usr/sbin/xntpd "$src_running" "-x"

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.

uname –n

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.

ping localhost

PreviousInstallation OverviewNextInstallation

Last updated