Installation in manual mode

1. Prepare the installation file(tar.gz) and license file(license.xml).

1. Create client account.

$ useradd -d /home/tibero7_client -g dba tibero7_client
$ passwd tibero7_client

1. Unzip the binary archive.

$ ls
tibero7-bin-FS02-windows64_2008-269353-20240314021215.zip

$ unzip tibero7-bin-FS02-linux64_3.10-254994.tar.gz

1. Configure the profile.

   Modify the content to suit the environment and add it to the profile of the client server.

```shell
$ vi ~/.bash_profile
export TB_HOME=/home/tibero7_client/tibero7 export TB_SID=tibero
export PATH=$TB_HOME/bin:$TB_HOME/client/bin:$PATH
export   LD_LIBRARY_PATH=$TB_HOME/client/lib:$LD_LIBRARY_PATH

$ source ~/.bash_profile

1. Copy the license file(license.xml) to the directory, $TB_HOME/license.

1. Execute gen_tip.sh.

$ cd $TB_HOME/config

$ sh gen_tip.sh Using TB_SID "tibero"
/home/tibero7_client/tibero7/config/tibero.tip generated
/home/tibero7_client/tibero7/config/psm_commands generated
/home/tibero7_client/tibero7/client/config/tbdsn.tbr generated. 
Running client/config/gen_esql_cfg.sh
Done.

1. Configure the network file (tbdsn). tbdsn.tbr file configures the server connection path, and it is located in $TB_HOME/client/config. Manually configure tbdsn.tbr as the following guide.

$ cd $TB_HOME/client/config

$ ls
gen_esql_cfg.sh tbco_file_id tbdsn.tbr	tbimport_hl.config.default tbpcb.cfg 
tbc_file_id	tbdfdump.cfg tbertl.cfg tbpc.cfg

$ vi tbdsn.tbr 
#------------------------------------------------------------
# /home/tibero7_client/tibero7/client/config/tbdsn.tbr 
# Network Configuration File.
# Generated by gen_tip.sh at 2023. 06. 12. (월) 14:30:16 KST
tibero=(
    (INSTANCE=(HOST=192.168.xxx.xxx) 
              (PORT=8629)
              (DB_NAME=tibero)
     )
)

1. Access to Tibero Server with Tibero Client.

/tbsql tibero/tmax


TmaxTibero Corporation Copyright (c) 2020-. All rights reserved.

Connected to Tibero.

SQL> SELECT
    IPADDR, USERNAME 
FROM
    V$SESSION;	2	3	4

IPADDR
----------------------------------------------------------
USERNAME
-----------------------------------------------------------------------------------
192.168.xxx.xxx
TIBERO

Uninstalling manually

Run $TB_HOME/.installation/Tibero_Uninstaller, which is supported for all platforms.

UNIX

The following is the Tibero manual uninstallation process in a Unix environment.

UNIX 환경에서 수동으로 Tibero를 제거하는 순서에 대한 설명입니다.

1. Shut down Tibero.

tbdown

2. Delete the directory of Tibero as well as all the subdirectories by using the OS's command.

rm –rf $TB_HOME

Pre-Installation Tasks

Verify the following before configuring TAC.

• IP address and port information

• Socket buffer configuration

• Shared disk type

Checking IP Address and Port Information

Before starting installation, check the external IP address and listener port number which are needed by an instance of Tibero.

In addition, the interconnect IP address, interconnect port number, and the CM port number are also required. When using VIP or IP filtering, make sure that IPs are assigned to the same subnet.

IP address

Port number

Socket Buffer Settings

Set the socket buffer values of the operating system.

AIX

Linux

Solaris

Checking Shared Disk Type

TAC requires shared disk space that all instances can access together.

Executing and operating TAC requires at least seven shared files. These files are created based on the parameter {SHARED_DISK_HOME} specified by the user during installation. If necessary,

{TAC_INSTANCE_ID} is attached to the name of the files. For example, if {SHARED_DISK_HOME} is "dev/tac" and {TAC_INSTANCE_ID} is 0, the path of an Undo log file is "dev/tac/UNDO0.dtf."

The following is the list of shared files and their paths required when initially installing nodes.

After the initial installation, additional nodes installation requires the following four shared files for each node. For information on each file's path, see the previous table.

• 3 redo log files

• 1 undo log file

Manual Installation

Installation Verification

You can verify whether the installation is successful by running the tbcm command.

tbcm -s

The command shows the CM configuration information.

CM information
=============================================================== 
CM NAME	            : cm0
CM UI PORT	    : 8635
RESOURCE FILE PATH  : /home/tibero7/cm0_res.crf 
CM MODE	            : GUARD ON, FENCE OFF
LOG LEVEL	    : 2
===============================================================

Uninstallation

There are two methods for uninstalling a node in the TAC environment: console mode and manual mode.

Console Mode

The following is the process of removing a node in console mode.

1. Shut down the Tibero instance.

tbdown

1. End TBCM.

tbcm -d

1. Delete the Tibero installation directory as well as all the subdirectories by using the OS's command.

$ rm –rf $TB_HOME

Manual Mode

The following is the process of removing a node manually.

1. Shut down the Tibero instance.

tbdown

1. End TBCM.

tbcm -d

1. Delete the Tibero installation directory as well as all the subdirectories.

rm –rf $TB_HOME

Linux

This section describes how to configure HugePage in Linux. Root permission is required.

Enabling HugePage

The following describes how to enable HugePage.

1. Check the size of HugePage supported in the current OS.

$ grep Hugepagesize /proc/meminfo 
Hugepagesize:	2048 KB

1. Check the user group ID that runs Tibero.

$ id -a
uid=579(tibero) gid=579(tibero) groups=579(tibero)

1. Apply the groups and number that will allocate HugePage in "/etc/sysctl.conf"

The following is an example of applying the kernel parameter when TOTAL_SHM_SIZE is set to 1024 MB and the size of HugePage supported by the current OS is 2 MB (2048 KB).

$ cat /etc/sysctl.conf
......Omitted......
vm.nr_hugepages=512 
vm.hugetlb_shm_group=579

1. Apply the maximum locked memory value in "/etc/security/limits.conf".

The following is an example of configuring the memlock value.

$ cat /etc/security/limits.conf
......Omitted......
tibero	soft	memlock    1048576
tibero	hard	memlock    1048576

1. Restart the operating system.

The modified HugePage value has been applied.

$ egrep -e HugePages_Total /proc/meminfo 
HugePages_Total: 512 KB

1. Configure the Tibero initialization parameters in the configuration file (.tip).

The following is an example of configuring the initialization parameters.

$ cat tibero.tip
......Omitted......
TOTAL_SHM_SIZE=1G 
USE_HUGE_PAGE=Y

1. Restart the Tibero server.

$ tbdown

Tibero instance terminated (NORMAL mode).

$ tbboot
Listener port = 8629
Change core dump dir to /home/tibero/tibero7/instance/tibero.

Tibero 7

TmaxData Corporation Copyright (c) 2008-. All rights reserved. 
Tibero instance started up (NORMAL mode).

Disabling HugePage

To disable HugePage, restore the values that were modified to enable HugePage to their original values. The modified values can be restored by the same process and order used to enable HugePage.

AIX

AIX uses Large Page instead of HugePage. The benefits of using Large Page are similar to those of HugePage.

Enabling HugePage

The following describes how to enable HugePage.

1. Change the Large Page configuration value of the OS.

AIX internally maintains physical memory pool sizes of 4 KB and 16 MB. The size of this pool can be changed to 16 MB by using the vmo command. The remaining space is automatically allocated to the 4 KB pool. From AIX 5.3 on, Large Page pools are dynamically maintained, so the system does not need to be restarted after changing the size.

First, v_pinshm must be separately configured so that the space in which the shared memory is allocated is not swapped to disk. percent_of_real_memory is the amount of memory that TSM possesses as a percentage of the total memory.

$ vmo r o v_pinshm=1
$ vmo r o maxpin%=percent_of_real_memory

Configure the Large Page pool size. num_of_lage_pages is an integer and is equal to TSM / 16 MB.

$ vmo p o lgpg_regions=num_of_lage_pages o lgpg_size=16 MB

2. Configure user permissions.

According to the security policy, all users (except the root user) must have the CAP_BYPASS_RAC_VMM permission to use Large Page. The permission can be configured by using the chuser command.

$ chuser capabilities=CAP_NUMA_ATTACH,CAP_BYPASS_RAC_VMM,CAP_PROPAGATE <user id>

3. Configure the following Tibero initialization parameters in the environment configuration file (.tip).

The following example configures the initialization parameters.

$ cat tibero.tip
......Omitted......
TOTAL_SHM_SIZE=1G 
USE_HUGE_PAGE=Y

4. Restart the Tibero server.

$ tbdown

Tibero instance terminated (NORMAL mode).

$ tbboot
Listener port = 8629
Change core dump dir to /home/tibero/tibero7/instance/tibero. 

Tibero 7
TmaxData Corporation Copyright (c) 2008-. All rights reserved. 
Tibero instance started up (NORMAL mode).

Disabling HugePage

To disable Large Page, restore the values that were modified to enable Large Page to their original values.

Solaris

The functionality of HugePage can be applied by using the ISM (Intimate Shared Memory) function through Large Page.

The advantages of using ISM are as follows:

• ISM shared memory is automatically locked by the OS when it is created. This ensures that the memory segment is not swapped to disk. It also allows the kernel to use a fast locking mechanism for I/O of the shared memory segment.

• The memory structure used to convert the kernel's virtual memory address into a physical memory address is shared between multiple processes. This sharing reduces CPU consumption and conserves kernel memory space.

• Large Page supported in the system's MMU (Memory Management Unit) is automatically allocated in the ISM memory segment. This allocation improves system performance by conserving memory space for managing pages and by simplifying virtual memory address conversion.

Enabling HugePage

To enable HugePage, configure the server initialization parameter as follows.

The parameter is only valid in Solaris and the default value is Y.

USE_ISM=Y

If this function is turned on, shmget is used to create shared memory and the SHM_SHARED_MMU option is added when attaching with shmat. This function is only applied in the server process and the listener process. The client module that attaches the server's TSM does not use this option. However, if the parameter is not set to Y, change the value to Y and restart the Tibero server.

Disabling HugePage

Set the server initialization parameter _USE_ISM to N and then restart the Tibero server.

_USE_ISM=N

Recommended Settings

Tibero does not restrict the size of HugePage, which can be set within the range allowed by different operating systems.

The recommended settings are as follows:

• For small memory (less than 64GB): 4MB

• For large memory (more than 64GB): 16MB

User Configuration Files

TB_HOME

Issue

If the property TB_HOME is not set or is set improperly, or if the user configuration file is not applied after Tibero is installed, this message may be displayed when trying to connect to the tbSQL utility.

Solution

Check the TB_HOME property in the user configuration file, change the value if necessary, and then apply the file to the system.

LD_LIBRARY_PATH

Issue

If the property LD_LIBRARY_PATH is not set or is set improperly, or if the user configuration file is not applied after Tibero is installed, this message may be displayed when trying to connect to the tbSQL utility.

Solution

Check the LD_LIBRARY_PATH property in the user configuration file, change the value if necessary, and then apply the file to the system.

TB_SID

Issue

If TB_SID is not set, this message may be displayed when the tbboot or tbdown command is executed.

Solution

Check the TB_SID property in the user configuration file, change the value if necessary, and then apply the file to the system.

TAC Installation

The following describes how to resolve issues that can occur after Tibero is installed in a TAC environment.

Adding a Node

Accessing a tip File

Issue

If a configuration file (.tip) cannot be found when a node is added, this message may be displayed.

Solution

Check whether the Tibero instance's $TB_SID.tip exists in the corresponding path by referring to TB_HOME and TB_SID.

Accessing TAC

Issue

To add a node, an existing node's setting values are necessary. If trying to access an existing node fails, this message may be displayed.

Solution

• Check that TB_HOME and TB_SID are set properly.

• Check that the existing node can be accessed through tbsql.

• If an existing node does not work, start the node with the tbcm, tbboot commands then try to add the node again.

Transferring an scp File

Issue

If transferring Tibero installation files to a new node fails, this message may be displayed.

Solution

• Check whether the current node can access the node to be added using ping or ssh.

• If the current node cannot access the node to be added, check the settings for account synchronization, networking, and any firewalls.

TPR-Related Error When Using a TAC Raw Device

Issue

The SYSSUB tablespace, which contains TPR-related tables, was added starting from Tibero 5.0 r61295. During the system schema configuration portion of installing and patching, the syssub001.dtf file is automatically created in the directory $TB_ HOME/database/$TB_SID. However, if the property DB_CREATE_FILE_DEST is set to a specific location, the file is created at that location.

However, in an environment using a TAC raw device, the file is created on the local disk of the node processing the system schema. This results in an error that prevents other nodes from accessing the SYSSUB tablespace. The same error occurs in a shared disk environment when the property, DB_CREATE_FILE_DEST, is not set correctly.

Solution

Recreate the SYSSUB tablespace as follows:

1. Delete the existing tablespace.

1. Create a new tablespace.

1. Execute the following script.

Miscellaneous

Port Number

Issue

This error occurs when the specified port number is already in use when executing the tbboot command.

Solution Check whether the instance is already in use or modify the port number set in the $TB_SID.tip file in $TB_HOME/client/config.

dbtimezone

Recommendation

The dbtimezone is the reference timezone value used for storing the timestamp with local timezone data to database. Since this value is internally processed in the database, it is not recommended to modify it, because this requires unnecessary operations leading to performance degradation.

Overview

This chapter explains the prerequisite and precautions before installing Tibero client, considerations after installation and Tibero client installation methods on Linux.

Document Organization

The guide contains 2 chapters.

Preparations before installing

1. Check available disk space

Before installing Tibero, a minimum of 2GB of free hard disk space is required, with slight differences depending on the install platform. This also includes the minimum hard disk space needed to create a database after installing Tibero.

2. Check JDK installation

To install using the Tibero Client Installer, a version of JDK 1.5.17 or higher must be installed.

[Figure 1] Check JDK installation

3. Preparing the installation file

Go to ‘TechNet’ of Tmax, create account and download the installation file.

When installing manually,

Considerations after installation

After installing Tibero, JDBC is provided to integrate with other solutions.

JDBC

When integrating JDBC, the required driver file can be found from the following paths on the Tibero DB server. The following is an explanation of the driver file’s path based on the server’s operating system. (File path for Unix environments.)

The following is a description of the driver file name for each version of TIbero.

Overview

This document is intended for all database users who want to install or uninstall Tibero®(Tibero).

Required Knowledge

• Database

• RDBMS

• OSs and system environments

• Unix (including Linux)

Document Organization

The guide contains 6 chapters and 7 appendix.

Appendix

Overview

The current enterprise business rapidly expands with the explosive increase of data and the advent of a variety of new environments and platforms. This new business environment requires more flexible and efficient data services, information handling, and data management functions.

Tibero is an enterprise database management system that supports building a database infrastructure on which enterprise business is implemented and provides high performance, high availability, and scalability.

To address limitations of existing databases, Tibero implemented its proprietary Tibero thread architecture. It also uses limited system resources such as CPU and memory efficiently, guarantees high performance and reliability, and provides a convenient development environment and management features.

Tibero, from its very earliest version, has been developed to handle a large number of users and large amounts of data while ensuring reliability and compatibility.

Tibero is a data management solution that manages large amounts of data and guarantees reliable business continuity. It has all of the features needed for an RDBMS environment such as distributed database links, data replication, data clustering, and parallel query processing. Tibero provides thereby an optimal database environment that perfectly meets enterprise needs.

Installation Components

Software Distribution Policy

Tibero software distribution policy is as follows:

• Full Purchase Version: Licensed by the number of CPUs and features.

• Evaluation Version: A license that restricts the trial period and the number of users.

System Requirements

This section describes supported platforms, operating systems, hardware and software requirements.

Supported Platforms and Operating Systems

Tibero supports the following platforms and operating systems.

Hardware

Hardware requirements for installing Tibero are as follows:

For Solaris platforms, refer to the following when setting swap space.

• Recommended setting: twice the physical memory

• User setting: 사용자 설정: (Background process count + Worker process count) * Swap usage per process(300 MB)

Software

Software requirements for installing Tibero are as follows:

Overview

This chapter explains the prerequisite and precautions before installing Tibero client, considerations after installation and Tibero client installation methods on Windows.

Document Organization

The guide contains 2 chapters.

The shared memory in Tibero is divided into fixed memory and shared pool memory as follows:

• Fixed Memory Its size is fixed based on a parameter value set at database startup.

  – Buffer cache (database buffer)

  – Log buffer

  – Others: space for global variables and managing working threads and session information.

• Shared Pool Memory It is dynamically allocated during database operation.

  – DD cache

  – PP cache (library cache)

  – Others

Considerations

Consider the following when calculating the size of the shared memory.

• The size of the shared memory cannot be increased dynamically while the database is running.

• The size of the shared memory must be determined properly based on the usage patterns of the buffer cache and shared pool.

- Buffer Cache

• Determine the size according to the Buffer Cache Hit rate in TPR after executing major workloads.

• If the hit rate is lower than 90%, increase the buffer cache.

- Shared Pool Memory

• Determine the size according to the SHARED POOL MEMORY item in v$sga after executing major workloads.

• If the shared pool usage is too high (insufficient free area), increase the shared pool memory.

• At least 1 MB of the shared pool memory is required for each session.

Calculating the Size

The size of each area in the shared memory can be checked with v$sga.

The size of the shared memory can be set and queried with the following initialization parameters.

Shared Memory

The following example queries the size with the TOTAL_SHM_SIZE parameter.

Buffer Cache

The following example queries the size with the DB_CACHE_SIZE parameter.

• Single mode : ⅔ of TOTAL_SHM_SIZE

• TAC mode : ½ of TOTAL_SHM_SIZE

Log Buffer

The following example queries the size with the LOG_BUFFER parameter. (the default value of LOG_BUFFER is 10 MB.)

Shared Pool Memory

The size can be calculated by subtracting the fixed memory size from the total shared memory size as follows:

• Single mode The total shared pool size must be greater than _MIN_SHARED_POOL_SIZE.

• TAC mode Sufficient space for Cluster Cache Control (CCC) and Cluster Wait-lock Service (CWS) is required. About 25% of a total buffer cache size is used by shared pools.

  The shared pool space excluding space for CCC and CWS must be greater than

  _MIN_SHARED_POOL_SIZE.

The free shared pool size for PP and DD caches must be greater than CCC and CWS spaces.

Preparations before installing

1. Check available disk space

Before installing Tibero, a minimum of 2GB of free hard disk space is required, with slight differences depending on the install platform. This also includes the minimum hard disk space needed to create a database after installing Tibero.

2. Check JDK installation

To install using the Tibero Client Installer, a version of JDK 1.5.17 or higher must be installed.

[Figure 1] Check JDK installation

3. Preparing the installation file

Go to ‘TechNet’ of Tmax, create account and download the installation file.

Considerations after installation

After installing Tibero, JDBC is provided to integrate with other solutions.

JDBC

When integrating JDBC, the required driver file can be found from the following paths on the Tibero DB server. The following is an explanation of the driver file’s path based on the server’s operating system. (File path for Unix environments.)

The following is a description of the driver file name for each version of TIbero.

Tibero can be installed using an installer or manually.

Manual Installation

Tibero can be manually installed in all supported platforms. This is referred to as "manual installation".

UNIX

The following is the manual installation process of Tibero for Unix.

1. Prepare the following two files.

• Binary executable file (tar.gz)

• License file (license.xml)

1. Set the environment variables in the environment configuration files (.bashrc, .bash_profile, .profile, etc.) for each OS user account. The following are examples of environment variables and their values.

1. Extract the compressed binary executable file (tar.gz) to home/tibero/Tibero. Copy the issued license file (license.xml) to the license subdirectory in %TB_HOME%.

2. Enter the following command from the $TB_HOME/config path.

After executing the command, the configuration file (.tip), tbdsn.tbr, and psm_commands.bat are created.

1. Start the Tibero server in 'NOMOUNT Mode'.

1. Connect to the database by using the tbSQL utility. In the following example, the 'sys' account is used to connect to the database.

1. Create a database using the CREATE DATABASE statement. In the following example, a database named 'tibero' is created.

The following describes each setting item in the process.

1. After the database is created, run the tbboot command to restart Tibero.

1. Enter the system.sh script from $TB_HOME/scripts directory to execute the SQL file in the current directory. The SQL file creates roles, system users, views, packages, etc. (The default passwords for the sys and syscat accounts are tibero and syscat, respectively.)

1. After the Tibero installation is complete, the Tibero process starts. To check the process state, execute the following command.

Installation Verification

This section describes how to verify whether Tibero has been successfully installed.

Directory Structure

The following directory structure is created after installing Tibero.

The following are the default directories in Tibero.

bin

Contains Tibero executables and server management utilities. The tbsvr and tblistener files are executables for creating the Tibero, and tbboot and tbdown are used to start up and shut down the Tibero.

client

Contains the following subdirectories.

config

Contains the configuration files for Tibero. The $TB_SID.tip file in this directory contains the environment settings for Tibero.

database

Contains the following subdirectories.

• $TB_SID Contains all database information unless it is configured separately. It includes the metadata and the following file types.

• $TB_SID/java Contains Java EPA class file unless JAVA_CLASS_PATH is defined.

instance

Contains the following subdirectories.

• $TB_SID/audit Contains the audit files that records activities of database users using system privileges or schema object privileges.

• $TB_SID/log Contains system log (slog), DBMS log (dlog), internal log (ilog), listener log (lsnr), and memlog files of Tibero.

System log, DBMS log, internal log, and listener log files are accumulated as the database operates. The maximum size of the log directory can be set, and Tibero deletes old files if the maximum size is reached.

The following are the initialization parameters for a DBMS log file.

• $TB_SID/dump Contains dump files generated because of errors.

• $TB_SID/path Contains the socket files used for interprocess communication in Tibero. The files in this directory must not be read or updated while Tibero is running.

lib

Contains the spatial function library files for Tibero.

license

Contains the Tibero (license.xml). This XML file can be opened using a text editor to check its contents.

The following is the subdirectory.

nls

Contains the following subdirectory.

scripts

Contains various SQL statements used when creating a database in Tibero. It also includes various view definitions that reflect the current state of Tibero.

The following is the subdirectory.

Applying and Verifying User Configuration File

After Tibero is installed, the following properties are added in the user configuration file.

In Unix, when a process is abnormally terminated, virtual memory information remains on the disk. This process is called a core dump. It requires significant amounts of computing resources and temporarily lowers system performance during execution, and the dump files generated in the process take up a large part of disk space. Therefore, this process is not recommended for Tibero.

To disable the core dump feature, add the following command to the configuration file (.profile) of the user account.

Because the user configuration file has been created as previously described does not mean it is actually applied. You need to perform the following to apply the configuration file.

1. Run the following command to apply the configuration file. Valid only in Unix systems (including Linux).

1. To verify whether the configuration file is properly applied, run the following commands.

Startup and Shutdown

Only database administrators (DBAs) are allowed to start up or shut down Tibero.

Startup

Executes the following tbboot command to start up Tibero.

Shutdown

Tibero is shut down by the tbdown command.

You can run the tbdown command along with options as follows:

Connecting to the database with a tbSQL utility

Run the tbsql command.

You can enter user ID and password as follows:

To connect to the database through a listener, enter @ after the user ID and password, and then the alias set specified in the tbdsn.tbr file.

User Accounts

The following user accounts are automatically created upon the installation of Tibero.

Installation in manual mode

1. Prepare the installation file. When you create a folder to install the Tibero client and unzip it, folders are created.

2. Configure the invironment variables.

(1) In Windows, select [Edit system environment variables] -> [Advanced] -> [Environment variables] and configure [System variables].

[Figure 2] Configuring system variables

(2) In the [Environment variable], select [System variables] -> [New] and configure TB_HOME and TB_SID.

[Figure 3] TB_HOME and TB_SID configuration

(3) Unzip the compressed binary executable file(tar.gz) in the directory ‘C:\Tibero'. Then, copy the license file(license.xml) into the subdirectory named “license’ under %TB_HOME%.

(4) After executing tbinstall.vbs, and check the registry registration.

[Figure 4] installation complete message

In the registry (regedit), check whether TB_HOME and TB_SID are registered in the HKEY_LOCAL_MACHINE\SOFTWARE\TmaxTibero\Tibero\tibero path.

[Figure 5] TB_HOME, TB_SID registration check

(5) Execute gen_tip.bat.

(6) Delete any unnecessary folders except ‘bin’ and ‘client’ folders.

(7) Configure the network file(tbdsn).

(8) Access to Tibero Server with Tibero Client.

Uninstallation

1. Execute tbuninstall.vbs and remove it from the registry.

[Figure 6] Uninstallation complete message

1. Delete physical files. Uninstall the Tibero client by deleting the directory in the path set to %TB_HOME%.