TAC Installation and Uninstallation
This chapter describes how to install Tibero a TAC(Tibero Active Cluster) configuration.
Pre-Installation Tasks
Verify the following before configuring TAC.
System requirements TFor more information about the system requirements for TAC, refer to "System Requirements" in Installation Overview page.
Installation requirements Verify the basic installation requirements in “Pre-installation Tasks” 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
External IP address
IP address for external communication.
Interconnect IP address
Internal IP address for communication among nodes.
Port number
Listener port number
Port number assigned when each node's Tibero instance starts.
CM port number
Port number assigned to CM for communication among nodes.
Interconnect port number
Port number for communication among each node's Tibero instances.
Socket Buffer Settings
Set the socket buffer values of the operating system.
AIX
SB_MAX
4194304
TCP_RECVSPACE
4194304
TCP_SENDSPACE
1048576
Linux
net.core.rmem_max
4194304
net.core.wmem_max
1048576
Solaris
max_buf
4194304
recv_buf
4194304
send_buf
1048576
The sb_max parameter is applicable only to AIX.
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.
Control file
{SHARED_DISK_HOME}/c1.ctl (changeable)
Cluster file for CM
{SHARED_DISK_HOME}/cfile/cls1_cfile(changeable)
Redo log file
{SHARED_DISK_HOME}/log{TAC_INSTANCE_ID}1.log
{SHARED_DISK_HOME}/log{TAC_INSTANCE_ID}2.log
{SHARED_DISK_HOME}/log{TAC_INSTANCE_ID}3.log
Undo log file
{SHARED_DISK_HOME}/UNDO{TAC_INSTANCE_ID}.dtf
User tablespace file
{SHARED_DISK_HOME}/usr001.dtf
System tablespace file
{SHARED_DISK_HOME}/system001.dtf
Temporary tablespace file
{SHARED_DISK_HOME}/temp001.dtf
If these file names cannot be used due to the nature of the hardware, use symbolic links.
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
When using a raw device as the shared disk, each of these shared files is considered as a single individual raw device. Before installation, you need to request the raw device's administrator to create the respective files. Note that each file must have sufficient size with the block size set to 512 and the character type.
The name and path of control files, CM cluster files and resource files can be specified by the user.
Manual Installation
For information about how to manually configure a TAC environment and install Tibero, refer to "Tibero Cluster Manager" and "Tibero Active Cluster" in Tibero Administrator's Guide.
Installation Verification
You can verify whether the installation is successful by running the tbcm command.
The command shows the CM configuration information.
For more information about how to use the tbcm command, refer to "Tibero Cluster Manager" in Tibero Administrator's Guide.
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.
Shut down the Tibero instance.
End TBCM.
Delete the Tibero installation directory as well as all the subdirectories by using the OS's command.
Manual Mode
The following is the process of removing a node manually.
Shut down the Tibero instance.
End TBCM.
Delete the Tibero installation directory as well as all the subdirectories.
Last updated