Tibero 6 - Installation Guide - v2.1.6 - en
Tibero 6 - Installation Guide - v2.1.6 - en
Installation Guide
Tibero 6
All TmaxData Software (Tibero®) and documents are protected by copyright laws and international convention.
TmaxData software and documents are made available under the terms of the TmaxData License Agreement
and this document may only be distributed or copied in accordance with the terms of this agreement. No part of
this document may be transmitted, copied, deployed, or reproduced in any form or by any means, electronic,
mechanical, or optical, without the prior written consent of TmaxData Co., Ltd.
Nothing in this software document and agreement constitutes a transfer of intellectual property rights regardless
of whether or not such rights are registered) or any rights to TmaxData trademarks, logos, or any other brand
features.
This document is for information purposes only. The company assumes no direct or indirect responsibilities for
the contents of this document, and does not guarantee that the information contained in this document satisfies
certain legal or commercial conditions.
The information contained in this document is subject to change without prior notice due to product upgrades or
updates. The company assumes no liability for any errors in this document.
Trademarks
Tibero® is a registered trademark of TmaxData Co., Ltd. Other products, titles or services may be registered
trademarks of their respective companies.
Some modules or files of this product are subject to the terms of the following licenses: OpenSSL, RSA Data
Security, Inc., Apache Foundation, Jean-loup Gailly and Mark Adler, Paul Hsieh's hash
Detailed Information related to the license can be found in the following directory:
${INSTALL_PATH}/license/oss_licenses
Manual Information
Edition: v2.1.6
Table of Contents
About This Document ................................................................................................................. ix
Tibero iii
4.2.1. GUI Mode (Windows) ....................................................................................... 51
4.2.2. Console Mode (Linux) ...................................................................................... 53
4.3. Manual Mode ............................................................................................................. 54
Index .......................................................................................................................................... 87
Tibero v
List of Figures
[Figure 3.1] JVM Error ............................................................................................................... 14
[Figure 3.2] Installation Language Screen ................................................................................... 14
[Figure 3.3] Destination Folder ................................................................................................... 15
[Figure 3.4] Choosing Installation Modules ................................................................................. 16
[Figure 3.5] License .................................................................................................................. 17
[Figure 3.6] Shortcuts ................................................................................................................ 18
[Figure 3.7] Pre-installation Summary ......................................................................................... 18
[Figure 3.8] Pre-installation Progress .......................................................................................... 19
[Figure 3.9] Starting Tibero Instance Wizard ............................................................................... 20
[Figure 3.10] Tibero Wizard ........................................................................................................ 21
[Figure 3.11] Database Identification .......................................................................................... 22
[Figure 3.12] Initialization Parameters ......................................................................................... 23
[Figure 3.13] Account Configuration ........................................................................................... 24
[Figure 3.14] User Defined SQL ................................................................................................. 25
[Figure 3.15] Creating a Database Instance ................................................................................ 26
[Figure 3.16] Creating a Database ............................................................................................. 27
[Figure 4.1] Tibero GUI Uninstallation ......................................................................................... 52
[Figure 4.2] Tibero GUI Uninstalling ............................................................................................ 52
[Figure 4.3] Uninstallation Completed ......................................................................................... 53
[Figure 5.1] Client Installation Start Screen ................................................................................. 55
[Figure 5.2] Client Install Path .................................................................................................... 56
[Figure 5.3] Choosing Client Installation Modules ........................................................................ 56
[Figure 5.4] Client Pre-Installation Summary ............................................................................... 57
[Figure 5.5] Client Installation ..................................................................................................... 58
[Figure 5.6] Client Installation Complete ..................................................................................... 58
[Figure 5.7] Client Uninstallation Start Screen ............................................................................. 59
[Figure 5.8] Client Uninstallation Progress Screen ....................................................................... 60
[Figure 5.9] Client Uninstallation Complete ................................................................................. 60
Tibero vii
About This Document
Intended Audience
®
This document is intended for database users who want to install or uninstall Tibero (hereafter Tibero).
Required Knowledge
This document explains how to install Tibero. To fully understand this guide, users need to have an
understanding of the following.
● Database
● RDBMS
Document Scope
This guide does not contain all the information needed for the actual application or operation of Tibero.
Briefly introduces Tibero and describes the system requirements for installation.
Describes pre-installation tasks including verification of sufficient disk space and configuration of certain
settings.
● Chapter 3: Installation
● Chapter 4: Uninstallation
● Appendix A: Troubleshooting
Describes how to solve problems that may occur after Tibero is installed.
● Appendix D: [Link]
Boldface Emphasis
" " (double quotes) Reference to chapters or sections in the manual, or to other related
documentation
Reference or note
Note
{} Required argument
[] Optional argument
Tibero Describes the tbCLI (Call Level Interface) concept, components, and
program structures, as well as the data types, functions, and error
tbCLIGuide
messages needed to write tbCLI applications.
Tibero Introduces the tbPSM package, a storage procedure module. This guide
also describes the prototypes, parameters, and examples of each
tbPSM Reference Guide
procedure and function included in this package.
Tibero Introduces tbAdmin, a GUI based tool that provides SQL/PSM processing
and system management function for DBAs. This guide also describes
tbAdmin Guide
installation and operation.
Tibero Describes how to install, use, and configure the utilities that handle
database related operations.
Utility Guide
Tibero Describes troubleshooting methods for various errors that may occur
while using Tibero.
Error Reference Guide
Tibero Describes the initialization parameters, data dictionary, and static and
dynamic views used by Tibero .
Reference Guide
Tibero Describes the SQL statements required for creating application programs
or operating a database.
SQL Reference Guide
Tibero Describes the geometry type and spatial procedures and functions of
Tibero and how to use them.
Spatial Reference Guide
Tibero Describes how to create and use the text index provided by Tibero.
Korea
TmaxData Co., Ltd.
45, Jeongjail-ro, Bundang-gu,
Seongnam-si, Gyeonggi-do, 13613
South Korea
Tel: +82-31-8018-1000
Fax: +82-31-8018-1115
Email: tibero@[Link]
Web (Korean): [Link]
TechNet: [Link]
USA
TmaxSoft Inc.
230 West Monroe Street Suite 1950
Chicago, IL 60606
U.S.A
Tel: +1-312-525-8330
Fax: +1-312-525-8340
Email: info@[Link]
Web (English): [Link]
Japan
TmaxSoft Japan Co., Ltd.
5F Sanko Bldg, 3-12-16 Mita, Minato-Ku, Tokyo, 108-0073
Japan
Tel: +81-3-5765-2550
Fax: +81-3-5765-2567
Email: info@[Link]
Web (Japanese): [Link]
Brazil
Tmax Brasil Sistemas E Serviços Ltda.
Av. Copacabana, 177, sala 32~35 Empresarial 18 do Forte
Alphaville Barueri, Sao Paulo, 06472-001
Brazil
Tel: +55-11-4191-3100
Fax: +55(11) 4191-3705 (extension#112)
Email: [Link]@[Link]
Web (Portuguese): [Link]
Russia
Tmax Rus L.L.C.
Leninsky prospekt, 113/1 (Park Place Moscow),
Office 318e, Moscow, 117198
Russia
Tel: +7(495)970-0135
Email: [Link]@[Link]
Web (Russian): [Link]
United Kingdom
TmaxSoft UK Ltd.
215 Knyvett House, Watermans Business Park,
The Causeway, Staines TW18 3BA
United Kingdom
Tel: +44-1784-895005
Email: [Link]@[Link]
Web (English): [Link]
Canada
TmaxSoft Canada, Inc.
2425 Matheson Blvd East, 8th floor,
Unit 825 Mississauga, ON, L4W 5K4
Canada
Tel: +1-905-361-2888
Email: [Link]@[Link]
Web (English): [Link]
India
TmaxSoft Technologies Private Limited
Sobha Alexander Plaza, 3rd Floor,
16/2 Commissariat Road, Bangalore-560025
India
Tel: +91-7619-482-582
Email: [Link]@[Link]
Web (English): [Link]
Turkey
TmaxSoft Co., Ltd. Turkey Liaison Office
Windowist Tower. Eski Buyukdere Cad. No:26,
Maslak 34467 Istanbul
Turkey
Tel: +90-212-214-7345
Email:[Link]@[Link]
Web (English): [Link]
This chapter briefly introduces Tibero and describes the system requirements for installation.
1.1. Overview
The current enterprise business rapidly expanded with the explosive increase of data and the advent of
a variety of 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 make up for the disadvantages of existing DBs, Tibero implemented its own Tibero thread architecture.
It also uses system resources such as CPU and memory efficiently, guarantees high performance and
reliability, and provides a convenient development environment and management features.
Tibero was developed to handle a large number of users and large amounts of data while offering reliability
and compatibility.
Tibero is a data management solution that manages large amounts of data and guarantees reliable
business continuity. Tibero has all of the features needed for an RDBMS environment such as distributed
database links, data replication, data clustering, and parallel query processing.
● Evaluation Version
A license that restricts the trial period and the number of users.
[Link]
AIX 6.1
AIX 7.1
– 64 Bit
Windows 7
– 64 Bit
Windows 7
LINUX/x86 Red Hat Enterprise Linux Compiler supporting C99, JDK 1.5.17 or higher
4 kernel 2.6.9 or higher
LINUX/Itanium Red Hat Enterprise Linux Compiler supporting C99, JDK 1.5.17 or higher
4 kernel 2.6.9 or higher
gcc version 3.4.6 or higher
LINUX/Power8 (Big Red Hat Enterprise Linux Compiler supporting C99, JDK 1.7.0 or higher
/ Little) 7 kernel 3.10.0 or higher
gcc version 4.8.5 or higher
HP-UX/itanium HP-UX 11i v2 (11.23) with Compiler supporting C99, JDK 1.5 or higher for
BUNDLE11i (== HP-UX HP-UX
HP aC++/ANSI C B3910B
11i v2 (B.11.23),
A.06.02
September 2004) 64Bit
kernel
Solaris Solaris 10 64Bit kernel Compiler supporting C99, JDK 1.5.17 or higher
AIX AIX 5L version 5.3 64Bit Compiler supporting C99, JDK 1.5.17 or higher
kernel
IBM XL C/C++ Enterprise
AIX 6.1 64Bit kernel Edition V7.0
Windows Server
2012(64bit Only)
Note
2. For Windows AMD64 (x64), Microsoft Visual C++ 2008 Redistributable Package(x64) and
[Link] Framework 3.5 SP1 must be installed for Tibero to function properly.
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.
2.1. Overview
Before Tibero is installed, the following tasks should be performed.
● Install JDK
Note
For more information about hardware requirements, refer to section “1.3. System Requirements”.
To verify the free disk space, run the df command on a UNIX system, or check the related property of
the hard disk on which Tibero will be installed, on a Windows system.
If Oracle's JDK cannot be used, install an appropriate JDK. For example, the JDKs for HP-UX and AIX
can be downloaded from the HP and IBM websites, respectively.
For JDK installation instructions for each operating system, refer to the following.
[Link]
Note
For JDK installation instructions for each operating system, refer to the following.
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
compat-libstdc++-33-3.2.3-47.3
libaio-0.3.105-2
libaio-devel-0.3.105-2
semmns 32000
semopm 10000
semmni 10000
2.5.2. Solaris
Kernel parameters for Solaris can be set in the /etc/system file.
[Link]-sem-nsems 10000
[Link]-shm-ids 100
[Note]
For Solaris 10 and later versions, it is recommended to manage parameters for each user by creating a
project.
1. Create a project.
2.5.3. HP-UX
Kernel parameters for HP-UX are as follows.
nproc 4096
semmap (semmni+2)
semmni 4096
semmns (semmni*2)
semmnu (nproc-4)
semvmx 32767
shmmni 512
shmseg 120
The kernel parameter values can be verified using the System Administration Manager (SAM).
# /usr/sbin/sam
semaphore = 10000
● Linux
● AIX
● Solaris
# stopsrc -s xntpd
# startsrc -s xntpd -a "-x"
● Host name
Verify the host name when the license is requested. Confirm via the /etc/hosts file, or run the following
command via the console:
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
3.1. Overview
Tibero can be installed manually or through an installer.
The installer is provided in the form of tibero6_<fixset>_<platform>.[bin|exe]. The installer offers two
installation methods:
● Manual
1. Insert the Tibero installation CD into the CD-ROM drive. Double-click on the
tibero6_<fixset>_<platform>.exe file to start the Tibero 6 installer.
[Note]
If the installer is executed in an environment without Java Virtual Machine (JVM), it fails to execute
and the following message is displayed. Check the Java environment of the system where the installer
is executed.
Chapter 3. Installation 13
[Figure 3.1] JVM Error
2. After the installer starts, the following screen is displayed. Select a language and then click [OK].
Installation is available in Korean and English.
The default installation directory is 'C:\TmaxData\tibero6', and it is set to the TB_HOME parameter
in the user configuration file. The directory path cannot include any blank spaces.
To change the home directory, click [Choose...] and then select the desired folder. To restore the
default home directory, click [Restore Default Folder].
Chapter 3. Installation 15
4. Choose the modules to install.
Option Description
ODBC Installs Tibero ODBC driver provider in Tibero ODBC Data Source
Administrator.
32bit / 64bit Bit information of the platform where ODBC or OLE DB is installed.
The location must be an absolute path including the license file name ([Link]). A demo license
file can be downloaded from TechNet. For more information about license files, refer to “1.2.2. Software
Distribution Policy”.
Chapter 3. Installation 17
6. After installing Tibero, choose whether to create shortcuts, and then click [Next].
7. The pre-installation summary screen is displayed. Review the installation details, verify the installation
directory, and then click [Install] to begin the installation.
Chapter 3. Installation 19
9. When the Tibero pre-installation process is complete, an install mode for creating a database instance
can be selected.
Button Description
[Custom] Allows the user to enter detailed information about database creation.
[Typical] Creates a database by using default values except for basic information such as
DB_NAME, PORT, and PASSWORD.
To cancel the installation, click [Quit]. To install Tibero manually, open a Windows command window
while logged in as an administrator and run the wizard through the following command.
– Typical Mode
%TB_HOME%\client\bin\runWizard -m gui -d Y
– Custom Mode
%TB_HOME%\client\bin\runWizard -m gui
Select a language and then click [Next]. Installation is available in Korean and English.
Chapter 3. Installation 21
11. Configure the environment for creating a database, and then click [Next].
Item Description
TB_UP_HOME Path where Tibero binary is installed. TB_UP_HOME is set to the Tibero home
directory.
Listener Port Port number used by the listener. (Default value: 8629)
– SID cannot contain special characters, and the first character cannot be a number.
Parameter Description
TOTAL_SHM_SIZE Total shared memory size that can be used in a database instance.
The user can add, delete, and modify initialization parameters by clicking [Add], [Del], and [Edit],
respectively. To restore the default configuration, click [Restore Default].
Note
For more information about initialization parameters, refer to "Tibero Reference Guide".
Chapter 3. Installation 23
13. Set the Tibero system user password and database settings. Click [Next] to continue.
To add or delete a user-defined SQL script file, click [Add] or [Delete]. The
%TB_UP_HOME%\scripts\example_users.sql script executes by default. This script creates the
following sample user accounts.
Account Description
TIBEROUP Sample user account granted with CONNECT, RESOURCE, and DBA permissions.
TIBERO 1 Sample user account granted with CONNECT, RESOURCE, and DBA permissions.
Chapter 3. Installation 25
15. After configuring the database, review the installation process displayed. If an error occurs during the
installation, then the installation process is rolled back and the installation is terminated.
$ ./tibero6_<FixSet>_Linux_x86_64.bin
Preparing to install...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...
Launching installer...
================================================================
Tibero (created with InstallAnywhere)
-------------------------------------------------------------------------------
Preparing CONSOLE Mode Installation...
================================================================
Chapter 3. Installation 27
Introduction
------------
Welcome to the Installer for Tibero.
3. Choose the Tibero installation directory. Press <ENTER> to use the default directory. To change the
directory, enter the desired directory and then press <ENTER>.
TB_HOME in the user environment configuration file is set to the specified directory. The directory path
cannot include any spaces.
===============================================================================
Specify a home directory
------------------------
===============================================================================
Input a License File
--------------------
Please input a license file with the absolute path.
The demo license can be downloaded at TechNet ([Link]
A demo license file can be downloaded from TechNet. For more information, refer to “1.2.2. Software
Distribution Policy”.
5. The configuration values set by the user during the installation process are displayed on the screen.
Check the values and then click <ENTER>.
Product Name
Tibero
Installation Directory
/home/tibero/TmaxData/tibero6
6. Installation for Tibero will now start. This copies the binary and creates links.
===============================================================================
Installing...
-------------
[==================|==================|========
================================================================
Choose An Install Mode
----------------------
Choose an install mode.
->1- Typical mode
2- Custom mode
ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE
DEFAULT: 2
Mode Description
Typical Creates a database by using default values except for user-configured settings
such as DB_NAME, PORT, and PASSWORD.
8. When the pre-installation process for Tibero is complete, the following message is displayed. Click
<<ENTER>> to terminate the installer.
Chapter 3. Installation 29
================================================================
Install complete
----------------
Congratulations! Tibero has been successfully installed to:
/home/tibero/TmaxData/tibero6
Users can execute the Wizard by running the following command after applying environment variables.
– Typical mode
$ sh $TB_HOME/client/bin/[Link] -m cmd -d Y
– Custom mode
$ sh $TB_HOME/client/bin/[Link] -m cmd
9. To create a Tibero database instance, execute "[Link]". To continue with the installation, click
<<ENTER>>.
$ sh /home/tibero/TmaxData/tibero6/client/bin/[Link]
======================================================
Introduction
--------------------------
Create Tibero Database.
10. Select the Tibero binary installation directory. $TB_HOME is set to the Tibero home directory.
14. Set the initialization parameters for the Tibero database. Skip this step if the install mode is Typical.
======================================================
Initialization Parameter
--------------------------
Enter 'ALL', one of the above options, the parameter number, or the parameter
itself to view the parameters.
PRESS <ENTER> TO PROCEED TO THE NEXT STEP:
Note
For more information about initialization parameters, refer to "Tibero Reference Guide".
======================================================
SYS password
--------------------------
Enter the password for the SYS account.
Chapter 3. Installation 31
PASSWORD :
CONFIRM PASSWORD :
======================================================
Character Set
--------------------------
Select the character set of the database.
0. ASCII
1. EUCKR
->2. MSWIN949
3. UTF8
4. SJIS
......Omitted......
15. EE8ISO8859P2
16. WE8ISO8859P9
17. WE8ISO8859P15
18. CL8KOI8R
19. CL8ISO8859P5
Note
For more information about the character sets supported in Tibero, refer to “Appendix C. Supported
Character Sets”.
======================================================
National Character Set
--------------------------
Select the national character set of the database.
0. UTF8
->1. UTF16
ENTER AN OPTION OR PRESS <ENTER> TO USE THE SELECTED NATIONAL CHARACTER SET:
18. Configure the database settings. Skip this step if the install mode is Typical.
======================================================
MAXDATAFILES
--------------------------
Enter the maximum number of data files to be used in the database.
-> DEFAULT : 100
TABLESPACE
--------------------------
Configure a TABLESPACE.
1. DEFAULT
2. TEMPORARY
3. UNDO
Item Description
MAXDATAFILES Maximum number of data files used in the database. (Default value:
100)
TABLESPACE Tablespace.
19. After creating the database, set additional user-defined scripts to execute. Skip this step if the install
mode is Typical.
======================================================
USER-DEFINED SQL
--------------------------
Add a new USER-DEFINED SQL, or delete one of the following SQL files:
0. /home/install2/tibero6/scripts/example_users.sql
Chapter 3. Installation 33
Account Description
TIBERO Sample user account with CONNECT, RESOURCE, and DBA permissions.
TIBERO1 Sample user account with CONNECT, RESOURCE, and DBA permissions.
20. The database is created with the previously configured settings. If the installation completes successfully,
the database is created.
======================================================
Wizard Process
--------------------------
0 50 100 (%)
|======|======|======|
All processes have been completed successfully.
Thank you.
3.3.1. Windows
The following is the Tibero manual installation process for Windows. The installation requires an
administrator account.
2. Click [Environment Variables] in the [Start] > [Settings] > [Control Panel] > [System] > [Advanced]
tab to set the environment variables. The following are sample environment variables and their values.
TB_HOME C:\Tibero\tibero6
TB_SID tibero
PATH C:\Tibero\tibero6\bin;C:\Tibero\tibero6\client\bin
3. Extract the compressed binary executable file ([Link]) to C:\Tibero. Copy the issued license file
([Link]) to the license subdirectory under %TB_HOME%.
4. Enter the following command from the %TB_HOME%\bin path. The service name may be omitted.
After executing the command, Tibero is registered as a Windows service. The Windows service can
be verified from [Start] > [Settings] > [Control Panel] > [Administrative Tools] > [Service]. Execute
the command prompt by clicking [Run as administrator] from the context menu.
TB_HOME = C:\Tibero\tibero6
TB_SID = tibero
service account = LocalSystem
Tibero_tibero installed successfully.
gen_tip.bat
After executing the command, the environment file (.tip), [Link], and psm_commands.bat are created.
C:\Tibero\tibero6\config>gen_tip.bat
Using TB_SID [tibero]
C:\Tibero\tibero6\config\[Link] generated
C:\Tibero\tibero6\client\config\[Link] generated.
C:\Tibero\tibero6\config\psm_commands.bat generated
Note
1. For more information about how to configure [Link], refer to "Appendix A. [Link]" in "Tibero
Administrator's Guide."
2. For more information about how to configure %TB_SID%.tip, refer to "Appendix A. Example of
Initialization Parameters" in "Tibero Reference Guide."
C:\Tibero\tibero6\bin>tbboot nomount
7. Connect to the database by using the tbSQL utility. In the following example, the 'sys' account is used
to connect to a database.
C:\Tibero\tibero6\bin>tbsql sys/tibero
tbSQL 6
Chapter 3. Installation 35
Copyright (c) 2008, 2009, 2011, 2012 TmaxData Corporation. All rights reserved.
Connected to Tibero.
8. Create a database using the CREATE DATABASE statement. In the following example, a database
named 'tibero' is created. For information about the configuration items, refer to step 18 in “3.2.2.
Console Mode (Linux)”.
Note
For more information about the CREATE DATABASE statement, refer to "Tibero SQL Reference
Guide."
9. After the database is created, use the tbboot command to restart Tibero.
C:\Tibero\tibero6\bin>tbboot
10. Change the default script host to cscript. Otherwise, an alert window is displayed in the user input area
when the vbs file is executed to stall the installation.
11. Enter the [Link] command from the $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.
C:\Tibero\tibero6\scripts>[Link]
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Chapter 3. Installation 37
Note
12. After the Tibero installation is complete, the tblistener and tbsvr processes are executed. To check the
process states, use the [Process] tab in the Windows task administrator.
3.3.2. UNIX
The following is the Tibero manual installation process for UNIX.
2. Set the environment variables in the environment configuration files (.bashrc, .bash_profile, .profile,
etc.) for each OS user account.
export TB_HOME=/home/tibero/Tibero/tibero6
export TB_SID=tibero
export LD_LIBRARY_PATH=$TB_HOME/lib:$TB_HOME/client/lib
export PATH=$PATH:$TB_HOME/bin:$TB_HOME/client/bin
Note
1. The environment variable configuration method varies for each OS. For more information, refer
to each OS guide.
2. Refer to “3.4.2. Applying and Verifying User Configuration File” for a description of each environment
variable.
3. Extract the compressed binary executable file ([Link]) to home/tibero/Tibero. Copy the issued license
file ([Link]) to the license subdirectory in %TB_HOME%.
gen_tip.sh
After executing the command, the environment file (.tip), [Link], and psm_commands.bat are created.
tibero@Tibero:~/Tibero/tibero6/config$ gen_tip.sh
Using TB_SID "tibero"
/home/tibero/Tibero/tibero6/config/[Link] generated
/home/tibero/Tibero/tibero6/config/psm_commands generated
/home/tibero/Tibero/tibero6/client/config/[Link] generated.
Running client/config/gen_esql_cfg.sh
Done.
Tibero6
6. Connect to the database by using the tbSQL utility. In the following example, the 'sys' account is used
to connect to a database.
tbSQL 6
Connected to Tibero.
SQL>
7. Create a database using the CREATE DATABASE statement. In the following example, a database
named 'tibero' is created. For information about the configuration items, refer to step 18 in “3.2.2.
Console Mode (Linux)”.
Chapter 3. Installation 39
national character set UTF16
logfile
group 1 '[Link]' size 100M,
group 2 '[Link]' size 100M,
group 3 '[Link]' size 100M
maxloggroups 255
maxlogmembers 8
noarchivelog
datafile '[Link]' size 100M autoextend on next 100M maxsize unlimited
default temporary tablespace TEMP
tempfile '[Link]' size 100M autoextend on next 100M maxsize unlimited
extent management local autoallocate
undo tablespace UNDO
datafile '[Link]' size 100M autoextend on next 100M maxsize unlimited
extent management local autoallocate;
Database created.
SQL> quit
Disconnected.
Note
For more information about the CREATE DATABASE statement, refer to "Tibero SQL Reference
Guide".
8. After the database is created, use the tbboot command to restart Tibero.
tibero@Tibero:~/Tibero/tibero6/bin$ tbboot
Change core dump dir to /home/tibero6/tibero6/bin/prof.
Listener port = 25010
Tibero 6
9. Enter the [Link] command 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.
tibero@Tibero:~/Tibero/tibero6/scripts$ [Link]
Enter SYS password:
Note
For more information about options provided in [Link](.vbs), refer to “Appendix D. [Link]”.
10. After the Tibero installation is complete, the Tibero process starts. To check the process state, execute
the following command.
Chapter 3. Installation 41
3.4.1. Directory Structure
The following directory structure is created after installing Tibero.
$TB_HOME
+- bin
|
+- client
| |
| +- bin
| +- config
| +- include
| +- lib
| +- ssl
| | |
| | +- certs
| | +- misc
| | +- private
| +- epa
| | |
| | +- java
| | |
| | +- config
| | +- lib
| +- win32
| +- win64
|
+- config
|
+- database
| +- $TB_SID
| |
| +- psm
|
+- instance
| |
| +- $TB_SID
| |
| +- audit
| +- log
| | +- dbmslog
| | +- lsnr
| | +- tracelog
| +- path
|
+- lib
|
The directories shown as $TB_SID in the previous directory structure is replaced by the server SID of the
system environment.
bin
This directory contains Tibero. 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/bin
Utility Description
tbSQL Basic client program for executing SQL queries and checking their results.
T-Up Utility for migrating data to and checking compatibility with Tibero from another
database.
tbExport Utility for writing data to an external file for data migration or logical backup.
tbLoader Utility for loading a large amount of data into the database.
tbpc Utility for converting embedded SQL in a C program to C so that the program can
be compiled by a C compiler.
For more information about the utilities, refer to "Tibero Utility Guide". For the tbpc utility, refer to
"Tibero tbESQL/C Guide".
client/config
This directory contains configuration file for executing a Tibero client program.
client/include
Chapter 3. Installation 43
client/lib
This directory contains the library files for creating a Tibero. For more information, refer to "Tibero
Application Developer's Guide" and "Tibero tbESQL/C Guide".
client/ssl
This directory contains certificate and key files for server security.
client/epa
This directory contains configuration and log files related to external procedures. For more information,
refer to "Tibero External Procedure Guide".
client/win32
client/win64
config
This directory contains the environment configuration files for Tibero. The $TB_SID.tip file in this
directory contains the environment settings for Tibero.
database/$TB_SID
This directory and its subdirectories contain all database information unless it is configured separately.
It includes the metadata and the following file types.
File Description
Log File Contains all data changes for use during data recovery.
database/$TB_SID/psm
This directory contains the tbPSM programs that are compiled in the compiled mode. Note that
currently, Tibero For more information, refer to "Tibero tbPSM Guide".
instance/$TB_SID/audit
This directory contains the audit files that records activities of database users using system privileges
or schema object privileges.
instance/$TB_SID/log
This directory contains the trace, DBMS, event, and listener log files of Tibero.
Trace Log File Used for debugging. This file logs all server activities in detail that can be used
for troubleshooting performance issues or resolve bugs within Tibero.
DBMS Log File Logs more important server activities than the trace log file. It records about
server startup and mode, ddl executions, etc.
EVENT Log File Logs trace logs for configured events. Use tbev to view the logs.
LISTENER Log File Used for debugging Listener objects. It records important activities in Listeners
objects and the logs are used for debugging purposes.
Trace, DBMS, event, and listener log files are accumulated with use and can grow up to the size of
the directory. Old files must be deleted from the directory to not exceed the limit.
The following are the initialization parameters for a DBMS log file.
DBMS_LOG_TOTAL_SIZE_LIMIT Maximum size of the directory where DBMS log files are saved.
TRACE_LOG_TOTAL_SIZE_LIMIT Maximum size of the directory where trace log files are saved.
EVENT_TRACE_TOTAL_SIZE_LIMIT Maximum size of the directory where event log files are saved.
LSNR_LOG_TOTAL_SIZE_LIMIT Maximum size of the directory where listener log files are saved.
instance/$TB_SID/path
This directory 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
This directory contains the spatial function library files for Tibero.
license
This directory contains the Tibero([Link]). This XML file can be opened using a text editor to
check its contents.
license/oss_licenses
This directory contains the open license terms that must be complied with when using Tibero.
Chapter 3. Installation 45
nls/zoneinfo
This directory contains the time zone information file for Tibero.
scripts
This directory contains various SQL statements used when creating a database in Tibero. It also
includes various view definitions that reflect the current state of Tibero.
scripts/pkg
TB_SID SID entered during installation. If not entered, it is set to tibero by default.
LD_LIBRARY_PATH Shared library path for Tibero. All libraries are in $TB_HOME/lib or
$TB_HOME/client/lib, and the environment variable varies by OS type.
– HP-UX: SHLIB_PATH
– AIX: LIBPATH
In UNIX, when a process is abnormally terminated, virtual memory information remains on the disk. This
process is called a core dump. It requires a lot of computing resources and temporarily lowers system
performance during execution, and the created dump file takes up a large amount 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.
ulimit -c 0
Although the user configuration file has been created, this does not mean the file has yet been applied.
To apply the file, do the following.
1. To apply the configuration file, run the following command for UNIX or Linux.
● UNIX
echo $TB_HOME
● Windows
echo %TB_HOME%
Startup
Executes the following tbboot command to start up Tibero
Option Description
-c Option to disable Replication mode when Tibero is set to the replication mode.
– RESETLOGS: Initializes log files when Tibero server is restarted after a media
recovery.
Chapter 3. Installation 47
Termination
Executes the following tbdown command to terminate Tibero
Option Description
– POST_TX: Shuts down the database after all transactions are complete.
– IMMEDIATE: Shuts down the database after forcibly terminating all tasks and
rolling back any running transactions.
tbsql sys/tibero
To connect to a database through a listener, enter @ and the alias set in the [Link] file after the user
ID and password.
tbsql sys/tibero@tibero
SYS User account for database management. Creates and manages system packages,
synonyms, users, roles, virtual tables, sequences, dynamic views, etc.
SYSCAT Creates and manages the static catalog views for database management.
OUTLN Stores SQL hint to re-execute the same query plan for the same SQL.
SYSGIS Creates and manages the tables that are related to GIS (Geographic Information
System).
TIBERO Sample user account that has been granted the CONNECT, RESOURCE and
DBA roles.
TIBERO1 Sample user account that has been granted the CONNECT, RESOURCE and
DBA roles.
Chapter 3. Installation 49
Chapter 4. Uninstallation
4.1. Overview
Tibero
● Manual
1. Run [Start] > [Programs] > [Tibero] > [Tibero 6] > [Uninstall Tibero 6], or run the uninstallaion GUI
screen by running the following file.
%TB_HOME%\.installation\Tibero [Link]
Chapter 4. Uninstallation 51
2. A screen confirming the uninstallation of Tibero is displayed. To uninstall, click [Uninstall].
5. When Tibero is uninstalled, database files are removed but physical files are not. The physical files
must be removed after the uninstallation process is complete.
To remove all files and directories under %TB_HOME%, run the following command in the command
prompt.
C:\>del Tibero
C:\Tibero\*, Do you want to continue(Y/N)? y
$ $TB_HOME/.installation/Tibero_Uninstaller
......Omitted......
===============================================================================
Introduction
------------
Chapter 4. Uninstallation 53
Tibero_Uninstaller will remove the features that were installed during product
installation.
All data files in the TB_HOME directory will be deleted.
Files and folders created after the installation will not be removed.
===============================================================================
Uninstallation Complete
-----------------------
All items of Tibero have been successfully uninstalled.
===============================================================================
PRESS <ENTER> TO CONTINUE:
3. When Tibero is uninstalled, database files are removed but physical files are not. The physical files
must be removed after the uninstallation process is complete.
$ rm -rf Tibero
tbdown
2. – For Windows
rmdir %TB_HOME%
– For Linux
rm –rf $TB_HOME
5.1. Installation
The following is the Tibero client installation process for Windows.
1. Double-click the tibero6_<fixset>_windows_<bit>_client.exe file. The client installer starts and the
following screen is displayed. To cancel the installation process, click [Cancel]. To continue with the
installation, click [Next].
2. After clicking [Next], the following screen is displayed. Select the installation directory.
'C:\Tibero\TiberoClient' is set as the default directory. To change the installation directory, click
[Choose...] and select the desired folder. To restore the default installation directory, click [Restore
Default]. After entering a directory, click [Next] to continue.
If an existing installation directory is selected and overwritten, an unexpected error may occur due
to the version difference.
To install the OLE DB module, the ODBC module must also be selected.
The JDBC driver is installed by default. The following are the available options.
Option Description
ODBC Installs Tibero ODBC driver provider in Tibero ODBC Data Source Administrator.
4. The pre-installation summary screen is displayed. Review the details, verify the installation directory,
and then click [Install] to begin the installation.
To modify the installation information, click [Previous] and then modify the information.
6. When the Tibero client installation is complete, the following screen is displayed. Click [Done] to close
the installer.
Note
The logs genereated duing the Tibero client uninstallation process is not deleted automatically. They
must be deleted manually.
1. Double-click the "{Tibero Client Installation Path}\.installation\Tibero Client [Link]" file. The
following screen is displayed.
6.1. Overview
In Windows and Unix (Linux), multiple instances from different databases can be simultaneously installed.
These instances can share a single Tibero license file and a Tibero binary execution file, but their TB_SID
and environment file (.tip) must be separately configured.
6.2. Windows
The following is the Tibero
The following are the assumed values of the environment variables for the previously installed instance.
TB_HOME C:\Tibero\tibero6
TB_SID tibero1
PATH %TB_HOME%\bin;%TB_HOME%\client\bin
2. Set the TB_SID environment variable for the instance to be installed. Its value must be different from
the TB_SID
set TB_SID=tibero2
3. Enter the following command in the %TB_HOME%\bin directory. The service name can be omitted.
Registered Windows Services can be checked in [Start] > [Settings] > [Control Panel] >
[Administrative Tools] > [Service]. Execute the command prompt by clicking [Run as administrator]
from the context menu.
TB_HOME = C:\Tibero\tibero6
TB_SID = tibero2
service account = LocalSystem
Tibero_tibero installed successfully.
gen_tip.bat
This command creates the environment file (.tip), [Link], and psm_commands.bat.
C:\Tibero\tibero6\config> gen_tip.bat
Using TB_SID [tibero2]
C:\Tibero\tibero6\config\[Link] generated
C:\Tibero\tibero6\client\config\[Link] generated.
C:\Tibero\tibero6\config\psm_commands.bat generated
5. Open the environment file (.tip) created in the %TB_HOME%\config directory. Set LISTENER_PORT
to a value different from the LISTENER_PORT value of any previously installed instance.
......Omitted......
DB_NAME=tibero2
LISTENER_PORT=9629
......Omitted......
Note
6. The subsequent steps of the installation process are the same as in “3.2.1. GUI Mode (Windows)” from
step 6. However, when using the CREATE DATABASE statement to create a database in step 7,
modify the log file or the data file path to match the TB_SID
6.3. Unix
The Tibero
1. Install the Tibero instance by referring to “3.2.2. Console Mode (Linux)” or “3.3.2. UNIX”.
TB_HOME /home/tibero/Tibero/tibero6
TB_SID tibero1
LD_LIBRARY_PATH $TB_HOME/lib:$TB_HOME/client/lib
PATH $PATH:$TB_HOME/bin:$TB_HOME/client/bin
2. Set the TB_SID environment variable for the instance to be installed. Its value must be different from
the TB_SID
export TB_SID=tibero2
gen_tip.sh
This command creates the environment file (.tip), [Link], and psm_commands.bat.
tibero@Tibero:~/Tibero/tibero6/config$ gen_tip.sh
Using TB_SID "tibero2"
/home/tibero/Tibero/tibero6/config/[Link] generated
/home/tibero/Tibero/tibero6/config/psm_commands generated
/home/tibero/Tibero/tibero6/client/config/[Link] generated.
Running client/config/gen_esql_cfg.sh
Done.
4. Open the environment file (.tip) created in the $TB_HOME/config directory. Set LISTENER_PORT
to a value different from the LISTENER_PORT value of any previously installed instance.
DB_NAME=tibero2
LISTENER_PORT=9629
......Omitted......
Note
This chapter describes how to install Tibero to configure TAC(Tibero Active Cluster).
● System requirements
For more information about the system requirements for TAC, refer to “1.3. System Requirements”.
● Installation requirements
Before configuring TACUAC, verify the basic installation requirements in “Chapter 2. Pre-installation
Tasks”.
● IP Address
Classification Description
● Port Number
Listener port number Port number assigned when each node's Tibero instance starts.
Interconnect port number Port number for communication among each node's Tibero instances.
SB_MAX 4194304
TCP_RECVSPACE 4194304
TCP_SENDSPACE 1048576
Note
To execute and operate TAC, at least seven shared files are needed. The files are created based on the
parameter {SHARED_DISK_HOME} entered 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/[Link]."
The following is a list of shared files necessary when a node is originally installed as well as the paths
where the files are created.
File Path
{SHARED_DISK_HOME}/log{TAC_INSTANCE_ID}[Link]
{SHARED_DISK_HOME}/log{TAC_INSTANCE_ID}[Link]
Note
If the above file names cannot be used because of hardware, use symbolic links.
Each additional node after the first needs the following four shared files. For information on each file's
path, see the above table.
Note
If a raw device is used as a shared disk, each shared file above corresponds to a single raw device
file. Prior to installation, a raw device administrator needs to create the corresponding file. Each file's
size should be sufficiently large, its block size must be 512 kilobytes, and the character type must
be set.
A control file and cfile and resource file for CM can be installed in custom mode so that the user can
choose a desired path and name. However, to change a file name or block size, contact the
Tibero technical support team.
tbcm -s
CM information
===============================================================
Note
For information on how to use the tbcm command, refer to 'Chapter 9. Tibero Cluster Manager' in
the "Tibero Administrator's Guide."
7.4. 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 for removing a node in console mode.
tbdown
2. Close TBCM.
tbcm -d
3. Delete all the child directories that include the directory in which Tibero is installed by using the operating
system's command.
$ rm –rf $TB_HOME
Manual Mode
The following is the process for removing a node in manual mode.
tbdown
2. Close TBCM.
3. Remove the directory where the Tibero instance is installed as well as its subdirectories.
rm –rf $TB_HOME
This appendix describes how to solve problems that can occur after Tibero is installed.
A.1.1. TB_HOME
● Problem and Cause
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, the above 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.
A.1.2. LD_LIBRARY_PATH
● Error
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, the above 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.
Appendix A. Troubleshooting 71
A.1.3. TB_SID
● Error
If TB_SID is not set, the above 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.
tip file does not exist / reading tip file failed / malformed tip file
If a configuration file (.tip) cannot be found when a node is added, the above message may be displayed.
● Resolution
Check whether the Tibero instance's $TB_SID.tip exists in the corresponding path by referring to
TB_HOME and TB_SID.
Accessing TAC
● Error
● Resolution
– If an existing node does not work, start the node with the tbcm, tbboot commands then try to add
the node again.
If transferring Tibero installation files to a new node fails, the above message may be displayed.
● Resolution
– 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.
The tablespace (SYSSUB) ,which is dedicated to TPR for TPR-related tables, was added in version
5.0 r61295. During the system schema configuration portion of installing and patching, the [Link]
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 where a TAC raw device is used, 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.
● Resolution
Appendix A. Troubleshooting 73
2. Create a new tablespace.
$TB_HOME/scripts/[Link]
$TB_HOME/scripts/pkg/_pkg_dbms_tpr.tbw
A.3. Miscellaneous
This error occurs when the specified port number is already in use when executing the tbboot command.
● Resolution
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.
B.1. AIX
The method for mounting a CD-ROM in AIX is as follows.
# mkdir /cdrom
mount <option>
<device_name><mount_point>
B.2. HP
The method for mounting a CD-ROM in HP is as follows.
# nohup /usr/sbin/pfs_mountd
& # nohup /usr/sbin/pfsd &
5. Insert a CD.
# /usr/sbin/pfs_mount /SD_CDROM
# /usr/sbin/pfs_umount /SD_CDROM
B.3. LINUX
The method for mounting a CD-ROM in Linux is as follows.
$ su -
Password : *****
# mount <option>
<device_name><mount_point>
# umount <mount_point>
B.4. Solaris
The method for mounting a CD-ROM in Solaris is as follows.
$ ps -e | grep vold
$ eject
# mkdir <mount_point> #
mount <options> <device_name>
<mount_point>
$ tbboot -C
ASCII
CL8ISO8859P5
CL8KOI8R
CL8MSWIN1251
EE8ISO8859P2
EUCKR
......Omitted......
AMERICAN
BRAZILIAN PORTUGUESE
JAPANESE
KOREAN
......Omitted......
The following are the options that can be used with [Link](vbs).
$ [Link] -h
Usage: [Link] [option] [arg]
-h : dispaly usage
-p1 password : sys password
-p2 password : syscat password
-a1 Y/N : create default system users & roles
-a2 Y/N : create system tables related to profile
-a3 Y/N : register dbms stat job to Job Scheduler
-a4 Y/N : create TPR tables
pkgonly : create psm built-in packages only
minonly : create minimum packages only
-sod Y/N : separation of duties
error : print error whenever sql encounters error
Option Description
-p1 password Enters the password of the SYS account. (Default value:
tiberochangepassword)
-p2 password Enters the password of the SYSCAT account. (Default value: syscat)
-a1 Creates a system user and grant permissions. For the initial installation,
select 'Y'.
– N: retain data.
-a2 Creates a table for a profile that can specify the database user password
management policy. For the initial installation, select 'Y'.
– N: retain data.
Appendix D. [Link] 79
Option Description
For more information about the profile, refer to "Chapter 5: User Management
and Database Security" of "Tibero Administrator's Guide".
– N: do not register.
-a4 Creates TRP related tables for regular, automatic collection of statistics.
– N: retain data.
For more information about the APM, refer to "Chapter 14 Tibero Performance
Repository" of "Tibero Administrator's Guide."
minonly Only executes the minimum required scripts to operate the DB. (Not supported
in Windows)
-sod Divides the administrator role into 3 accounts for security purposes.
error Outputs error details to the terminal when an error occurs from a specific
script while executing [Link]. (Not supported in Windows)
This chapter describes how to configure HugePage for each operating system.
E.1. Linux
This section describes how to configure HugePage in Linux. Root permission is required.
$ id -a
uid=579(tibero) gid=579(tibero) groups=579(tibero)
3. Apply the groups and number that will allocate HugePage in "/etc/[Link]".
shmall Group ID that will allocate HugePage. User group ID that runs Tibero.
The following is an example of applying the kernel parameter when TOTAL_SHM_SIZE is set to 1024MB
and the size of HugePage supported by the current OS is 2MB (2048 KB).
$ cat /etc/[Link]
......Omitted......
vm.nr_hugepage=512
vm.hugetlb_shm_group=579
$ cat /etc/security/[Link]
......Omitted......
tibero soft memlock 1048576
tibero hard memlock 1048576
_USE_HUGE_PAGE Y
$ cat [Link]
......Omitted......
TOTAL_SHM_SIZE=1G
_USE_HUGE_PAGE=Y
7. Grant the CAP_IPC_LOCK permission to the $TB_HOME/bin/tbsvr file by using the root permission.
$ su -
Password:
$ setcap CAP_IPC_LOCK+ep tbsvr
$ tbdown
$ tbboot
Listener port = 8629
Change core dump dir to /home/tibero/tibero6/instance/tibero.
E.2. HP-UX
HP-UX uses Large Page instead of HugePage. The function that applies Large Page for shared memory
regions is not separately supported by the OS.
The default page can be configured for the entire system. Use the kctune command to modify the
base_pagesize value (unit: MB) and then restart the computer. However, the HP-UX PARISC OS does
not support this function.
The following is an example of using the kctune command to configure the default page value.
$ kctune base_pagesize=16
E.3. AIX
AIX uses Large Page instead of HugePage. The benefits of using Large Page are similar to those of
HugePage.
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.
Configure the Large Page pool size. num_of_lage_pages is an integer and is equal to TSM / 16 MB.
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.
3. Configure the following Tibero initialization parameters in the environment configuration file (.tip).
TOTAL_SHM_SIZE Must be less than or equal to the size that was allocated for the 16 MB
memory pool.
_USE_HUGE_PAGE Y
$ cat [Link]
......Omitted......
TOTAL_SHM_SIZE=1G
_USE_HUGE_PAGE=Y
$ tbdown
$ tbboot
Listener port = 8629
Change core dump dir to /home/tibero/tibero6/instance/tibero.
Tibero 6
E.4. 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.
_USE_ISM=Y
If this function is turned on, shmget is used to create share 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 configuration value is not Y, change the value to Y and restart the Tibero server.
_USE_ISM=N
A S
AutoMounting, 76 SAM, 10
Software requirements, 4
C Solaris Kernel Parameter Setting, 9
Supported Platform and OS, 3
Character Sets, 77
System Administration Manager, 10
Client Installation, 55
[Link], 79
Control File, 44
D T
T-Up, 43
Data File, 44
tbboot, 43
DBMS Log File, 45
tbExport, 43
tbImport, 43
E
tbLoader, 43
EVENT Log FIle, 45
tbpc, 43
tbSQL, 43
H tbsvr, 43
Hardware Requirements, 4 Tibero, 1
HP-UX Kernel Parameter Setting, 10 Trace Log File, 45
I U
Installation Uninstallation
Console Mode, 27 Console Mode, 53
GUI Mode, 13 GUI Mode, 51
Manual Installation, 34 Manual Mode, 54
Unmount, 76
L User Configuration File, 71
Linux Kernel Parameter Setting, 9
LISTENER Log File, 45 V
Log File, 44 Volume Manager, 76
M
Manual Installation
Installation for Windows, 34
Manual Mode
Installation for Linux, 38
Index 87
The Tibero installation process on Windows using a GUI installer involves executing a setup file from a CD, selecting installation options such as language, home directory, and modules through a series of dialog boxes, and completing the setup by clicking through wizard screens . Conversely, manual setup on UNIX involves pre-installation preparation such as verifying host name and system configuration, extracting a tar.gz file, setting necessary environment variables through command line, and executing shell commands for configuration without a graphical interface . Furthermore, installation on UNIX focuses more on configuring the system according to prerequisites like adjusting kernel parameters and setting paths, which are less emphasized in the Windows GUI process .
To verify the pre-installation system configuration for Tibero, the following steps must be followed: 1. **Verify Host Name and System Requirements**: Confirm the host name via the /etc/hosts file or by using the "uname –n" command. Ensure that the system meets all hardware and software requirements, including sufficient disk space, the proper JDK version, and installation of necessary OS packages . 2. **Verify Port Number and System Account**: Check the default port number (8629) and make sure the correct system account is used for installing and operating Tibero . 3. **Network Configuration**: Ensure that the localhost is correctly set up using the "ping localhost" command, and verify the external IP address and interconnect IP address for communication needs . 4. **Kernel and Buffer Settings**: Configure kernel parameters and socket buffer values as recommended, particularly ensuring that sb_max, TCP_RECVSPACE, and TCP_SENDSPACE settings are optimized for Tibero . 5. **Shared Disk and Resource Files**: If using TAC, confirm the shared disk type and ensure that necessary shared files like control files, redo logs, and undo logs are accessible to all instances . 6. **Environment Variables**: Ensure the TB_HOME and LD_LIBRARY_PATH are set correctly in the user configuration file, as incorrect settings can lead to errors during database access or operations . These verification steps are necessary to ensure the system is properly configured for the installation process, thereby preventing future operational issues with Tibero.
Tibero supports multiple database instances by allowing different instances to share a single binary execution file and license file, while requiring each instance to have a unique TB_SID and environment configuration file (.tip). Installation procedures for different instances involve setting the TB_SID environment variable to a unique value and registering each instance as a separate Windows service . This approach allows efficient resource sharing while maintaining instance isolation.
Considerations for configuring Tibero database initialization parameters include setting various aspects such as control file location, database name, maximum session count, memory settings, and listener port. Control files need an absolute path, and the default database name is 'tibero' . The maximum number of sessions is set with MAX_SESSION_COUNT, and memory allocation is managed through parameters like MEMORY_TARGET and TOTAL_SHM_SIZE . The default listener port is 8629 . Parameters can be categorized as mandatory, optional, static, dynamic, persistent, or adjustable, enabling different levels of configurability . Use the Tibero Reference Guide for detailed parameter information .
Default installation paths during Tibero client installations are set to 'C:\Tibero\TiberoClient'. This default path can be changed by clicking [Choose...] to select a new folder or restored by clicking [Restore Default]. Users must verify the installation directory to avoid selecting an existing path that might contain a different version, which could lead to errors . It is important for users to carefully manage these settings, especially in environments where multiple Tibero instances may coexist, to ensure distinct configuration settings with unique TB_SID values and paths . Additionally, before confirming the installation, users should review all installation details in the pre-installation summary to prevent conflicts . Proper management of the default installation paths reduces the risk of errors and ensures the client is set up in a compatible manner with the existing system infrastructure.
Service ID (SID) for Tibero must be unique on a server, can contain numbers, letters, dashes, and underscores, but cannot start with a number or include special characters . These constraints are important to ensure that each instance of Tibero can be distinctly identified and accessed without conflicts, thus maintaining system integrity and preventing errors during database operations .
The system.sh script in Tibero is a post-installation tool that manages the database configurations by offering multiple options such as setting passwords for system accounts (SYS and SYSCAT), creating system users and roles, setting up tables for user management policies, and registering jobs for database statistics collection. For example, it can automatically create essential database elements like system users and roles, tables for user profiles, and a job schedule for database statistics by setting options such as -a1, -a2, -a3, and -a4 to 'Y' . This script is crucial for applying initial configurations and ensuring that the database is ready for operational use immediately after installation .
During the Tibero client installation, selecting an existing directory for overwriting can cause unexpected errors due to version differences . To mitigate this, ensure to choose a different directory or verify compatibility with the current version. Additionally, when installing the OLE DB module, ensure the ODBC module is also selected, as it is a prerequisite, which can prevent installation issues . Always verify installation details on the pre-installation summary screen and make corrections if necessary before proceeding with the installation .
Using the `tbboot` command is important during the Tibero installation process in several scenarios: 1. Starting the Tibero Server: After installation, the `tbboot` command is used by database administrators to start up the Tibero database server . 2. Selecting Appropriate Boot Modes: The `tbboot` command provides various boot modes like NOMOUNT, MOUNT, NORMAL, READONLY, and others. Each mode serves distinct operational needs such as initiating the database without mounting it, performing media recovery, standard database operations, or setting the database to read-only mode . 3. Recovery Operations: In case of recovery, the `tbboot` command can be used with the "RECOVERY" mode to run a standby database when configuring a Tibero Standby Cluster, which is crucial during failover or replication scenarios . These functionalities provide flexibility and control in managing database processes during and after installation.
The critical steps in setting environment variables for a manual Tibero installation on UNIX are as follows: 1. Prepare necessary files, specifically the binary executable file (tar.gz) and the license file (license.xml). 2. Set environment variables for the OS user accounts in configuration files such as .bashrc, .bash_profile, or .profile. The essential variables include TB_HOME, TB_SID, LD_LIBRARY_PATH, and PATH . Important values include: - export TB_HOME=/home/tibero/Tibero/tibero6 - export TB_SID=tibero - export LD_LIBRARY_PATH=$TB_HOME/lib:$TB_HOME/client/lib - export PATH=$PATH:$TB_HOME/bin:$TB_HOME/client/bin . 3. Extract the tar.gz file to the specified TB_HOME directory and place the license.xml in the license subdirectory within TB_HOME .