Table of Contents
This appendix describes how to install Tibero to configure Tibero Active Cluster (hereafter TAC).
Tibero provides a key feature, TACUAC, for scalability and high availability. All instances that are operating in the TAC environment perform transactions through a shared database and access shared data under mutual control for data integrity.
Tibero provides an installer to configure the TAC environment.
For more information on TAC, refer to the "Tibero Administrator's Guide."
Before TAC is configured, verify the following:
System requirements
Tibero installation requirements
IP address and port information
Account synchronization
TAC supports the following platforms and operating systems:
| H/W & S/W Vendor | CPU | OS | Binary Bits |
|---|---|---|---|
| HP | PA-RISC, IA64 | HP-UX 11i | 64 bits |
| SUN | SPARC 9 | Solaris SPARC 9 Solaris SPARC 10 | 64 bits |
| IBM | PPC 5L | AIX 5.3 AIX 6.1 | 64 bits |
| GNU | X86 (Pentium 4 or higher) | Linux kernel 2.6.15, libc 2.3.6 or later | 32 bits, 64 bits |
| IA 64 | LINUX | 64 bits | |
| Microsoft | X86, AMD64(X64) | Windows 2000 Windows 2003 Server Windows 2008 Server Windows 2012 Server Windows XP Windows XP Japan Windows 7 | 32 bits, 64 bits |
H/W requirements for installation are as follows:
| RAM | Swap Space | /tmp Directory Space | HDD Space (Full / Client Only) | Shared Disk Space |
|---|---|---|---|---|
| 1 GB | 1 GB | 300 MB | 400 MB / 300 MB | 1 GB |
An instance of TAC has the same requirements as a standard Tibero. Refer to the installation requirements for Tibero.
For detailed information about pre-installation tasks for Tibero, refer to “Chapter 2. Pre-installation Tasks”.
Prior to 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 TBCM port number are also required.
IP Address
| Classification | Description |
|---|---|
| External IP address | An IP address for external communication. |
| Interconnect IP address | An internal IP address for communication among nodes. |
Port Number
| Classification | Description |
|---|---|
| Listener port number | A port number assigned when each node's Tibero instance starts. |
| TBCM port number | A port number assigned to TBCM for communication among nodes. |
| Interconnect port number | A port number for communication among each node's Tibero instances. |
If the TAC installer is used in a node where the TAC environment is already configured, a feature for automatically adding a node can be used. If this feature is used, the installer automatically installs and sets up Tibero by using scp and ssh commands internally. To accomplish this through account synchronization, the scp and ssh commands need to be set to be used by multiple TAC nodes without a password.
Account synchronization is needed only when the feature for automatically adding a node is used. For information on how to automatically add a node, refer to Section C.3.1, “Automatically Adding a Node”.
The following is the process for synchronizing accounts among nodes.
Create the same user account for each node.
Generate RSA and DSA keys.
Login using the created user account.
Create a folder named .ssh in the user's home folder and grant permissions (chmod 700).
Generate the RSA key with the following command:
/usr/bin/ssh-keygen -t rsa
Generate the DSA key with the following command:
/usr/bin/ssh-keygen -t dsa
Add the keys to an authorized key file.
Check whether an authorized key file (~/.ssh/authorized_keys) exists in the current node. If the file does not exist, create the file with the following command:
touch ~/.ssh/authorized_keys
By using SSH, copy the contents of the RSA and DSA keys to each node's authorized key file.
The following example copies RSA and DSA keys of two nodes (192.123.1.101 and 192.123.1.102) to the current node's authorized key file.
ssh tac@192.123.1.101 cat /home/tac/.ssh/id_rsa.pub >> authorized_keys ssh tac@192.123.1.101 cat /home/tac/.ssh/id_dsa.pub >> authorized_keys ssh tac@192.123.1.102 cat /home/tac/.ssh/id_rsa.pub >> authorized_keys ssh tac@192.123.1.102 cat /home/tac/.ssh/id_dsa.pub >> authorized_keys
By using SCP or SFTP, copy the authorized key file to the .ssh folder of other nodes that do not have an authorized key file yet.
The following example copies the authorized key to the 192.123.1.102 node.
scp authorized_keys 192.123.1.102:/home/tac/.ssh
Change the authority of the authorized key file.
chmod 600 ~/.ssh/authorized_keys
Each node must have an authorized key file that has a public RSA key and a DSA key of all nodes in TAC.
Activate SSH User Equivalency.
Login as the user account from a node in which the Tibero installer will be executed, and then run the following command.
exec /usr/bin/ssh-agent $SHELL $ /usr/bin/ssh-add
Enter passwords for the RSA and DSA keys.
TAC requires shared disk space that all instances can access together.
To execute and operate TAC, at least nine 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/UNDO0.tdf."
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 |
|---|---|
| Control file | {SHARED_DISK_HOME}/c1.ctl (changeable) |
| TBCM file | {SHARED_DISK_HOME}/tbcm.ctl (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}.tdf |
| User tablespace file | {SHARED_DISK_HOME}/usr001.tdf |
| System tablespace file | {SHARED_DISK_HOME}/system001.tdf |
| Temporary tablespace file | {SHARED_DISK_HOME}/temp001.tdf |
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.
Three redo log files
An undo log file
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 a TBCM file can be installed in custom mode so that the user can choose a desired path. However, to change a file name or block size, contact the Tibero technical support team.
If the feature for automatically adding a node is used, configuration information about TAC and Tibero instances that have been installed are automatically collected. Installation files are transferred via the internal network and TAC is automatically configured for easy installation.
Sometimes this feature cannot be used due to problems with an internal network or an account setting. If so, the user needs to enter configuration information about TAC and Tibero in a node and perform a manual installation.
Checking existing information is only necessary if the manual installation method is used. For information about manual installation, refer to Section C.3.1, “Manually Adding a Node”. Note that if user-inputted information differs from existing TAC settings, the system may not function properly.
Before proceeding with manual installation, check the following configuration information for existing TAC and Tibero instances:
| Property | Description |
|---|---|
| TAC SID | The entire TAC database's SID. It must be identical to the existing information. |
| TAC Instance ID | A specific TAC instance's ID. Verify that the ID is unique. |
| TAC Shared Disk Home | A path that serves as a base to save a shared file on a shared disk. It must be identical to existing information. |
| Control File Path | A path to a control file that has TAC information. It must be identical to existing information. |
| TBCM File Path | A path to a TBCM file that has TAC information. It must be identical to existing information. |
| Database Block Size | Must be identical to the BLOCK SIZE of an existing database.. |
The following describes how to install and uninstall Tibero in the TAC environment using two methods: installation using the installer and manual installation.
The installer provides the following features: master node installation, automatic node addition, and manual node addition.
For a master node, Tibero is first installed and then the TAC environment is configured. After installing the master node, another node can be automatically or manually added.
The following is the Tibero installation and TAC configuration process for a master node:
Run the Tibero_DB_5_Linux_x86_32.bin file with the -t option in console mode. This executes the Tibero 5 SP1 installer for TAC.
$./Tibero_DB_5_Linux_x86_32.bin -t
When the installer runs properly, the following will be displayed in the console:
====================================================== Introduction - TAC Mode -------------------------- Tibero TAC Installer will guide you through the installation of Tibero 5 SP1 to build a TAC environment. It is strongly recommended that you quit all programs before continuing with this installation. Respond to each prompt to proceed to the next step in the installation. You may cancel this installation at any time by typing 'quit'. PRESS <ENTER> TO CONTINUE:
Select the desired node type. To install a master node, select 1- First Instance.
====================================================== Select Installation Instance Type -------------------------- Please select the instance type to install. Select a first instance when you build a new TAC system. Select an additional instance when you add an instance to an existing TAC system. -> 1- First Instance <default> 2- Additional Instance (Automatic) 3- Additional Instance (Manual) ENTER THE NUMBER FOR THE INSTANCE TYPE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT :1
Select an installation type. The following instructions describe the Custom installation type.
======================================================
Select Installation Type
--------------------------
Please select the Installation Type to install.
-> 1- Typical <default>
2- Custom
ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS
<ENTER> TO ACCEPT THE DEFAULT :2
A description of each installation type follows:
| Installation Type | Description |
|---|---|
| Typical | Installs with the default Tibero and TAC settings. For information about the default values of Tibero, refer to “Chapter 3. Installation and Uninstallation”. The default TAC values follow. A shared disk's home directory is the base path for TAC files that was entered during installation.
|
| Custom | Installs with a user-selected control file path, TBCM file path, TBCM port number, and Interconnect port number. |
Enter the TAC SID, a unique ID for TAC. (Default: tibero)
====================================================== Tibero Active Cluster SID --------------------------- Please enter the Cluster SID for installing system. Cluster SID (DEFAULT: tibero):tibero
Enter the shared disk's home directory that serves as the base path for TAC files on the shared disk. A control file, tbcm file, and several other files will be located in the directory.
====================================================== Choose TAC Shared Disk Home -------------------------- Please specify a base shared disk path where TAC configuration files are. ENTER AN ABSOLUTE PATH :/dev/tac -> TAC_SHARED_DISK_HOME : /dev/tac Is this correct?(y/n) y
Enter the paths for the control file and the tbcm file. By default the files are named c1.ctl and tbcm.ctl based on the shared disk's home directory.
A user may change the path but these files must be located on the shared disk as they must be accessible to all nodes.
====================================================== Custom Install Configurations for TAC -------------------------- Control File Path (DEFAULT: /dev/tac/c1.ctl): -> CONTROL_FILE_PATH : /dev/tac/c1.ctl Is this correct?(y/n) y TBCM File Path (DEFAULT: /dev/tac/tbcm.ctl): -> TBCM_FILE_PATH : /dev/tac/tbcm.ctl Is this correct?(y/n) y
Enter the number of nodes available for TAC. This is the maximum number of nodes that may be added. (Default: 8) Note that this number cannot be changed after TAC is configured.
====================================================== Maximum Number of TAC Cluster Instances -------------------------- Please enter an available maximum number of cluster instances at this TAC system.. (IMPORTANT! you cannot add instances more than this number.) Maximum Number of the Instances (1-255) (DEFAULT: 8): 8
Enter the ID for the instance that is being installed to distinguish it from other instances in the TAC environment. This ID must be unique. (Default Master node: 0)
====================================================== A Current TAC Instance ID -------------------------- Please enter the TAC instance ID. It is used at TAC environment for identifying this node. (IMPORTANT! This must be 'UNIQUE' comparing with other node's instance IDs.) TAC INSTANCE ID (DEFAULT 'FIRST INSTANCE STRONGLY RECOMMEND': 0) (0-7): 0
Enter the interconnect IP address used to communicate with other instances.
======================================================
An Cluster IP Address
--------------------------
Please enter the cluster IP address for this node to INTERCONNECT with other
TAC nodes.
Cluster IP Address: 192.123.1.101
Enter the interconnect (Cluster) and TBCM port numbers.
====================================================== Custom Install Configurations for TAC Instance -------------------------- Cluster IP Port (DEFAULT: 8634):8634 TBCM Port (DEFAULT: 8639):8639
Enter an instance SID to uniquely identify the Tibero node in the system, then press the <Enter> key.
======================================================
Instance SID
---------------------------
Instance SID is a local system identifier for Tibero instances.
Instance SID (DEFAULT: tac0):tac0
Enter the desired installation path for Tibero , then press the <Enter> key.
====================================================== Choose Install Folder -------------------------- Please specify a base location for Tibero to be installed. Tibero will be installed under TB_HOME directory. -> Default Install Path: /home/user/Tibero/tibero5 ( TB_HOME : /home/user/Tibero/tibero5 ) ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT :/home/tac/Tibero/tibero5 -> TB_HOME : /home/tac/Tibero/tibero5 Is this correct?(y/n) y
The default path is /home/tac/Tibero/tibero5. To modify this path, enter an absolute path.
Tibero will be installed at this location. The property TB_HOME will be set to this value.
The folder name must not include any blank spaces.
Choose whether to install help files, then choose a listener port number, the database block size, total shared memory size, and the DB cache size, and then press the <Enter> key.
====================================================== Custom Install Configurations for Database -------------------------- Do you want to install help files? (y/n) y Listener Port (DEFAULT: 8629) :8629 DATABASE BLOCK SIZE(K) (DEFAULT: 8) :8 Total Shared Memory Size (MB) (DEFAULT: 512M):512 DB Cache Size (MB) (DEFAULT: 128M):128
Select a character set for the database.
Tibero provides 8 character sets (MSWIN949, UTF8, ASCII, EUC-KR, SHIFT-JIS, EUC-JP, EUC-CN, and GBK) by default. Select one of the character sets, then press the <Enter> key to continue.
====================================================== Character Set Configuration -------------------------- Please select the default character set. 1. MSWIN949 <Default> 2. UTF8 3. ASCII 4. EUC-KR 5. SHIFT-JIS 6. EUC-JP 7. EUC-CN 8. GBK > 1
Enter information for the default user accounts (Sys, Syscat, Tibero, and Tibero1) provided for Tibero. For each account, enter the password twice to set and confirm.
====================================================== Account Configuration -------------------------- Please set the password for Administrator Accounts. Sys password : Confirm Sys password : Do you want to use the Sys password for Syscat, Tibero and Tibero1?(y/n) y
A pre-installation summary appears.
Review the chosen installation information, verify the installation path and other information, enter y and then press the <Enter> key to install Tibero.
====================================================== Pre-Installation Summary ------------------------- Please Review the Following Information Before Continuing. Product Name : Tibero 5 SP1 Install Set : Customize(Tibero 5 SP1, help files) TAC SID : tibero Maximum TAC Instance : 8 Thread Number (Node ID) : 0 Local Cluster IP : 192.123.1.101 Local Cluster Port : 8634 TBCM Port : 8639 NODE SID : tac0 Install Folder : /home/tac/Tibero/tibero5 TB_HOME : /home/tac/Tibero/tibero5 Listener Port : 8629 DataBase BLOCK SIZE(K) : 8K DATA FILE PATH : /home/tac/Tibero/tibero5/database/tac0 Shared Memory Size : 512M DB Cache Size : 128M Character Set : MSWIN949 ====================================================== Shared Disk Summary ------------------------- BEFORE YOU CONTINUE, CHECK AND CREATE FILES. SEE MANUAL FOR DETAIL. TAC Shared Disk Home : /dev/tac CONTROL FILE PATH : /dev/tac/c1.ctl TBCM FILE PATH : /dev/tac/tbcm.ctl SYSTEM TABLESPACE PATH : /dev/tac/system001.tdf USER TABLESPACE PATH : /dev/tac/usr001.tdf TEMP TABLESPACE PATH : /dev/tac/temp001.tdf UNDO TABLESPACE PATH : /dev/tac/UNDO0.tdf REDO LOG PATH 1 : /dev/tac/log01.log REDO LOG PATH 2 : /dev/tac/log02.log REDO LOG PATH 3 : /dev/tac/log03.log Is this information correct?(y/n)
If a raw device is used for the shared disk, check if shared files exist on the shared disk before installation. For information about the files, refer to “C.2.5. Checking Shared Disk Type”.
Installing Tibero may take a few minutes. After installation is complete, the following message will be displayed. During installation, software is copied, and links and a database are created.
Installation completed
To complete the installation, press the <Enter> key.
After Tibero installation is complete, a database is created. Once the database is created, modify the user configuration file for the system environment.
The installer gathers information about the node to be added then automatically installs and starts TAC in an environment with an existing TAC.
The following is the process for automatically adding a new Tibero instance to an existing TAC
The installer must be executed in a node where TAC is already installed. The new node is automatically installed based on information from the existing TAC and Tibero. To use this feature, the account synchronization process described in “C.2.4. Checking Account Synchronization” must be completed prior to installation.
Run the Tibero_DB_5_Linux_x86_32.bin file with the -t option n console mode. This executes the Tibero 5 SP1 installer for TAC.
$./Tibero_DB_5_Linux_x86_32.bin -t
After the installer completes, the following will be displayed in the console:
====================================================== Introduction - TAC Mode -------------------------- Tibero TAC Installer will guide you through the installation of Tibero 5 SP1 to build a TAC environment. It is strongly recommended that you quit all programs before continuing with this installation. Respond to each prompt to proceed to the next step in the installation. You may cancel this installation at any time by typing 'quit'. PRESS <ENTER> TO CONTINUE:
Select the desired node type. To automatically add a node, select 2- Additional Instance (Automatic).
====================================================== Select Installation Instance Type -------------------------- Please select the instance type to install. Select a first instance when you build a new TAC system. Select an additional instance when you add an instance to an existing TAC system. -> 1- First Instance <default> 2- Additional Instance (Automatic) 3- Additional Instance (Manual) ENTER THE NUMBER FOR THE INSTANCE TYPE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT :2
Select an installation type. The following is an example of selecting the Custom installation type.
======================================================
Select Installation Type
--------------------------
Please select the Installation Type to install.
-> 1- Typical <default>
2- Custom
ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS
<ENTER> TO ACCEPT THE DEFAULT :2
For information about installation types, refer to Section C.3.1, “Installing a Master Node”.
Enter the password for the SYS account of the existing Tibero.
====================================================== A SYS Account Password -------------------------- Please enter the SYS password for this TAC database. Installer will gather environment information of the TAC by accessing the current database. SYS password: ***** Confirm SYS password: *****
Enter the shared disk's home directory that serves as the base path for TAC files on the shared disk. The path must be the same as the path for the master node.
====================================================== Choose TAC Shared Disk Home -------------------------- Please specify a base shared disk path where TAC configuration files are. ENTER AN ABSOLUTE PATH :/dev/tac -> TAC_SHARED_DISK_HOME : /dev/tac Is this correct?(y/n) y
Enter the interconnect IP address used to communicate with other instances.
======================================================
An Cluster IP Address
--------------------------
Please enter the cluster IP address for this node to INTERCONNECT with other
TAC nodes.
Cluster IP Address: 192.123.1.102
Enter the interconnect (Cluster) and TBCM port numbers.
====================================================== Custom Install Configurations for TAC Instance -------------------------- Cluster IP Port (DEFAULT: 8634):8634 TBCM Port (DEFAULT: 8639):8639
Enter an instance SID to uniquely identify the Tibero node in the system, then press the <Enter> key.
======================================================
Instance SID
---------------------------
Instance SID is a local system identifier for Tibero instances.
Instance SID (DEFAULT: tac1):tac1
Choose whether to install a help file, enter a listener port, total shared memory size, and DB cache size, and then press the <Enter> key.
====================================================== Custom Install Configurations for Database -------------------------- Do you want to install help files? (y/n) y Listener Port (DEFAULT: 8629) :8629 Total Shared Memory Size (MB) (DEFAULT: 512M):512 DB Cache Size (MB) (DEFAULT: 128M):128
A pre-installation summary appears.
Review the chosen installation information, verify the installation path and other information, enter y and then press the <Enter> key to install Tibero .
====================================================== Pre-Installation Summary ------------------------- Please Review the Following Information Before Continuing. Product Name : Tibero 5 SP1 Install Set : Customize(Tibero 5 SP1, help files) TAC SID : tibero Thread Number (Node ID) : 1 Local Cluster IP : 192.123.1.102 Local Cluster Port : 8634 TBCM Port : 8639 NODE SID : tac1 Install Folder : /home/tac/Tibero/tibero5 TB_HOME : /home/tac/Tibero/tibero5 Listener Port : 8629 DataBase BLOCK SIZE(K) : 8K DATA FILE PATH : /home/tac/Tibero/tibero5/database/tac0 Shared Memory Size : 512M DB Cache Size : 128M Character Set : MSWIN949 ====================================================== Shared Disk Summary ------------------------- BEFORE YOU CONTINUE, CHECK AND CREATE FILES. SEE MANUAL FOR DETAIL. TAC Shared Disk Home : /dev/tac CONTROL FILE PATH : /dev/tac/c1.ctl TBCM FILE PATH : /dev/tac/tbcm.ctl UNDO TABLESPACE PATH : /dev/tac/UNDO1.tdf REDO LOG PATH 1 : /dev/tac/log11.log REDO LOG PATH 2 : /dev/tac/log12.log REDO LOG PATH 3 : /dev/tac/log13.log Is this information correct?(y/n)
If a raw device is used for the shared disk, check if the path for the shared files to be added exists on the shared disk prior to installation. For information about these files, refer to “C.2.5. Checking Shared Disk Type”.
Installing Tibero may take a few minutes. After installation is complete, the following will be displayed. During the installation, software is copied, links are created, and a database is created.
Installation completed
To complete the installation, press the <Enter> key.
After Tibero installation is complete, a database is created. Once the database is created, modify the user configuration file for the system environment.
When automatically adding a node isn't possible due to network or account problems, a node can be manually added using user-inputted node and TAC information.
The following is the process for manually adding a new Tibero instance to an existing TAC
The installer must be executed in the node to be added to TAC. To manually add a new node, a user needs to enter information about TAC and Tibero . To collect this information, refer to “C.2.6. Checking the Existing TAC Environment Information”.
Run the Tibero_DB_5_Linux_x86_32.bin file with the -t option in console mode. This executes the Tibero 5 SP1 installer for TAC.
$./Tibero__5_Linux_x86_32.bin -t
After the installer completes, the following will be displayed in the console:
====================================================== Introduction - TAC Mode -------------------------- Tibero TAC Installer will guide you through the installation of Tibero 5 SP1 to build a TAC environment. It is strongly recommended that you quit all programs before continuing with this installation. Respond to each prompt to proceed to the next step in the installation. You may cancel this installation at any time by typing 'quit'. PRESS <ENTER> TO CONTINUE:
Select a desired node type. To manually add a node, select 3- Additional Instance (Manual).
====================================================== Select Installation Instance Type -------------------------- Please select the instance type to install. Select a first instance when you build a new TAC system. Select an additional instance when you add an instance to an existing TAC system. -> 1- First Instance <default> 2- Additional Instance (Automatic) 3- Additional Instance (Manual) ENTER THE NUMBER FOR THE INSTANCE TYPE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT :3
Select an installation type. The following is an example of selecting the Custom installation type.
======================================================
Select Installation Type
--------------------------
Please select the Installation Type to install.
-> 1- Typical <default>
2- Custom
ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS
<ENTER> TO ACCEPT THE DEFAULT :2
For information about installation types, refer to Section C.3.1, “Installing a Master Node”.
Enter the TAC SID, a unique ID for TAC. (Default: tibero)
====================================================== Tibero Active Cluster SID --------------------------- Please enter the Cluster SID for installing system. Cluster SID (DEFAULT: tibero):tibero
Enter the shared disk's home directory that serves as the base path for TAC files on the shared disk. The path must be the same as the path for the master node.
====================================================== Choose TAC Shared Disk Home -------------------------- Please specify a base shared disk path where TAC configuration files are. ENTER AN ABSOLUTE PATH :/dev/tac -> TAC_SHARED_DISK_HOME : /dev/tac Is this correct?(y/n) y
Enter the paths for the control file and the tbcm file. By default, the files are named c1.ctl and tbcm.ctl based on the shared disk's home directory. The path must be the same as the path for the master node.
====================================================== Custom Install Configurations for TAC -------------------------- Control File Path (DEFAULT: /dev/tac/c1.ctl): -> CONTROL_FILE_PATH : /dev/tac/c1.ctl Is this correct?(y/n) y TBCM File Path (DEFAULT: /dev/tac/tbcm.ctl): -> TBCM_FILE_PATH : /dev/tac/tbcm.ctl Is this correct?(y/n) y
Enter the ID of the instance that is being installed to distinguish it from other instances in the TAC environment. This ID must be unique.
====================================================== A Current TAC Instance ID -------------------------- Please enter the TAC instance ID. It is used at TAC environment for identifying this node. (IMPORTANT! This must be 'UNIQUE' comparing with other node's instance IDs.) TAC INSTANCE ID (0-MAX_INSTANCES): 2
Enter the interconnect IP address used to communicate with other instances.
======================================================
An Cluster IP Address
--------------------------
Please enter the cluster IP address for this node to INTERCONNECT with other
TAC nodes.
Cluster IP Address: 192.123.1.101
Enter the interconnect (Cluster) and TBCM port numbers and an Undo tablespace name.
====================================================== Custom Install Configurations for TAC Instance -------------------------- Cluster IP Port (DEFAULT: 8634):8634 TBCM Port (DEFAULT: 8639):8639 Undo Tablespace Name (DEFAULT: UNDO2):UNDO2
Enter an instance SID to distinguish the Tibero node within the system, then press the <Enter> key.
======================================================
Instance SID
---------------------------
Instance SID is a local system identifier for Tibero instances.
Instance SID (DEFAULT: tac2):tac2
Enter the desired installation path for Tibero , then press the <Enter> key.
====================================================== Choose Install Folder -------------------------- Please specify a base location for Tibero to be installed. Tibero will be installed under TB_HOME directory. -> Default Install Path: /home/user/Tibero/tibero5 ( TB_HOME : /home/user/Tibero/tibero5 ) ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT :/home/tac/Tibero/tibero5 -> TB_HOME : /home/tac/Tibero/tibero5 Is this correct?(y/n) y
The default path is /home/tac/Tibero/tibero5. To modify this path, enter an absolute path. Tibero will be installed at this location. The property TB_HOME will be set to this value. The folder name must not include any blank spaces.
The folder name must not include any blank spaces.
Choose whether to install a help file, then enter a listener port, the database block size, total shared memory size, and the DB cache size, and then press the <Enter> key.
====================================================== Custom Install Configurations for Database -------------------------- Do you want to install help files? (y/n) y Listener Port (DEFAULT: 8629) :8629 DATABASE BLOCK SIZE(K) (DEFAULT: 8) :8 Total Shared Memory Size (MB) (DEFAULT: 512M):512 DB Cache Size (MB) (DEFAULT: 128M):128
A pre-installation summary appears. Review the chosen installation information, verify the installation path and other information, enter y and then press the <Enter> key to install Tibero.
If a raw device is used as a shared disk, check if the path for shared files to be added exists on the shared disk prior to installation. For information about the files, refer to “C.2.5. Checking Shared Disk Type”.
In addition, Undo tablespaces and log files should be added to the database in advance. For more information, refer to '10.5 Creating a Database for TAC' in the "Tibero Administrator's Guide."
====================================================== Pre-Installation Summary ------------------------- Please Review the Following Information Before Continuing. Product Name : Tibero 5 SP1 Install Set : Customize(Tibero 5 SP1, help files) TAC SID : tibero TAC Shared Disk Home : /dev/tac CONTROL FILE PATH : /dev/tac/c1.ctl TBCM FILE PATH : /dev/tac/tbcm.ctl Thread Number (Node ID) : 2 Local Cluster IP : 192.123.1.103 Local Cluster Port : 8634 TBCM Port : 8639 NODE SID : tac2 Install Folder : /home/tac/Tibero/tibero5 TB_HOME : /home/tac/Tibero/tibero5 Listener Port : 8629 DataBase BLOCK SIZE(K) : 8K DATA FILE PATH : /home/tac/Tibero/tibero5/database/tac0 Shared Memory Size : 512M DB Cache Size : 128M Character Set : MSWIN949 ====================================================== Shared Disk Summary ------------------------- BEFORE YOU CONTINUE, CHECK AND CREATE FILES. SEE MANUAL FOR DETAIL. TAC Shared Disk Home : /dev/tac CONTROL FILE PATH : /dev/tac/c1.ctl TBCM FILE PATH : /dev/tac/tbcm.ctl UNDO TABLESPACE PATH : /dev/tac/UNDO2.tdf REDO LOG PATH 1 : /dev/tac/log21.log REDO LOG PATH 2 : /dev/tac/log22.log REDO LOG PATH 3 : /dev/tac/log23.log [CAUTION: CREATE LOG] BEFORE YOU CONTINUE, CHECK 'CREATE UNDO TABLESPACE' AND 'ADD LOGFILE' FOR THIS NODE. SEE MANUAL FOR DETAIL. Is this information correct?(y/n)
Installing Tibero may take a few minutes. During the installation, software is copied, links are created, and a database is created. After the installation is complete, the following will be displayed:
Installation completed
To complete the installation, press the <Enter> key.
After Tibero installation is complete, a database is created. Once the database is created, modify the user configuration file for the system environment.
For information on how to manually configure the TAC environment and install Tibero , refer to 'Chapter 10. Tibero Active Cluster' in the "Tibero Administrator's Guide."
The tbcm command can verify if installation was properly completed.
tbcm -s
When the command is run, the status of the whole cluster and each node will be displayed, as below:
======================= LOCAL STATUS =========================== NODE NAME : [101] tbcm@10.0.2.15:8639 CLUSTER MODE : ACTIVE_SHARED (FENCE_OFF) STATUS : SERVICE ACTIVE [CMD_LOCK] INCARNATION_NO : 4 (ACK 4, COMMIT 4) HEARTBEAT PERIOD : 300 ticks (1 tick = 1000000 micro-sec) SERVICE PROBE PERIOD : 10 ticks (expires 10 ticks later) SERVICE DOWN CMD : "/home/tac/Tibero/tibero5/scripts/cm_down_cmd.sh" CONTROL FILE NAME : /dev/tac/tbcm.ctl (512 byte-block) CONTROL FILE EXPIRE : 299 ticks later ======================= CLUSTER STATUS ========================= INCARNATION_NO : 4 (COMMIT 4) FILE HEADER SIZE : 512 bytes ( 512 byte-block ) # of NODES : 1 nodes (LAST_ID = 101) MASTER NODE : [101] tbcm@10.0.2.15:8639 MEMBERSHIP : AUTO (SPLIT) NODE LIST... #0 ( ON) SERVICE ACTIVE ( 512) [101] tbcm@10.0.2.15:8639 ===================== OTHER NODE STATUS ========================
For information on how to use the tbcm command, refer to the "Tibero Administrator's Guide."
There are two methods for uninstalling a node in the TAC environment: console mode and manual mode.
The following is the process for removing a node in console mode:
Close the Tibero instance.
tbdown
Close TBCM.
tbcm -d
Run the following command in $TB_HOME/Uninstall.
$ ./Tibero_Uninstall.bin
When the following message is displayed, enter y and press the <Enter> key to continue.
Please wait a moment... Uninstall Tibero 5 SP1? (y/n) y (100) Tibero uninstalltion completed...
When the Tibero instance is removed, some files such as configuration files are not removed. If the files are not necessary, remove them with the following command:
$ rm –rf $TB_HOME
The following is the process for removing a node in manual mode.
Close Tibero instance.
tbdown
Close TBCM.
tbcm -d
Remove the directory where the Tibero instance is installed as well as its subdirectories.
rm –rf $TB_HOME
The following describes how to resolve issues that can occur after Tibero is installed in the TAC environment.
Error
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.
Error
extracting information from the existing cluster failed
To add a node, an existing node's setting values are necessary. If trying to access an existing node fails, the above message may be displayed.
Resolution
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 and tbboot commands then try to add the node again.
Error
Remote file transfer failed! / Remote configuration export failed!
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.
Error
The tablespace (_APM_TS) ,which is dedicated to APM for APM-related tables, was added in version 5.0 r61295. During the system schema configuration portion of installing and patching, the apm_ts.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 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 APM tablespace.
The same error occurs in a shared disk environment when the property, DB_CREATE_FILE_DEST, is not set correctly.
Resolution
Recreate the _APM_TS tablespace as follows:
Delete the existing tablespace.
SQL> DROP TABLESPACE _APM_TS INCLUDING CONTENTS AND DATAFILES;
Create a new tablespace.
SQL> CREATE TABLESPACE _APM_TS DATAFILE '<_APM_TS path>/apm_ts.dtf' ...;
Execute the following script.
$TB_HOME/scripts/apm.sql $TB_HOME/scripts/pkg_dbms_apm.sql