Tibero TSC Installation Guide

Transcription

1 Technical Training Tibero TSC Installation Guide

2 Table of Contents 1. Pre-Installation Tasks Configuring the Operating System Installing Linux Creating VM Users Changing Directory Permissions Installing Tibero Installing Tibero Single License Tibero Port Number Policy Test Environment Configuring the Test Environment OS Environment Tibero Binary User Directory Creating Users tsc10, tsc20 Users Port Numbers Changing Directory Permissions Tibero Installation Modifying a Configuration File Extracting a Tibero Binary File Copying a License Data File Location Executing gen_tip.sh Modifying a.tip File Modifying tbdsn.tbr Tibero Standby Cluster Configuration Primary Server Creating a Database Creating Dictionary and Package Modifying the Primary.tip File Standby Server Copying the Primary DB File Modifying a.tip File Applying the Control File

3 Starting in Recovery Mode Starting TSC Checking the Mode Used to Start Standbys Starting the Primary Checking TSC Functions TSC Information Inquiry of the Primary and the Standby Data Copy Switchover Failover

4 Tibero TSC Installation Guide 1. Pre-Installation Tasks The following describes the pre-installation tasks required to build a sample Tibero TSC server Configuring the Operating System Installing Linux Install Linux Centos 6.5 (64-bit) on a virtual machine (virtualbox) Creating VM Users Create 2 users in VM and allocate them to the same group. Install Tibero Single for the two users Changing Directory Permissions Change access permissions to the Tibero directory installation directory of the two users. Use chmod to change directory permissions (root permission). $ chmod -Rf g+rwx [directory name] 1.2. Installing Tibero Installing Tibero Single License Install Tibero Singles to each node. Continue installation until gen_tip. TechNet: Installation files: Downloads Database Tibero Tibero 5.0 Download Linux Download tar.gz for 32 or 64 bit Linux Installation Guide: Technical Knowledge Database Tibero Tibero 5 Installation Guide (English) (TINP003_Tibero 5_Installation Guide_2.1.1_en.pdf) Manual: Downloads Database Tibero Tibero 5.0 Download Manual Request a demo license through TechNet. Click Demo License Request in the main screen of TechNet to open the Demo License Request window. Set the Product field to "Tibero", the Version field to the desired version, and the Edition field to Enterprise. Enter a host name in the Host Name field. The license is sent via . Use the following command or the /etc/hosts file to check the host name. $ uname n Tibero Port Number Policy When Tibero starts, a service port number and other 3 port numbers are assigned. The service port number can be modified by a user. Do not use the service port number and the following three port numbers; those port numbers are reserved. 4

5 For example, if a user changes Tibero service port number to 9000, ports 9001, 9002, and 9003 are automatically assigned when Tibero starts. The following describes the port number policy. Type Description Example Active Service port Special port SSL port TBCM port Used by Tibero to handle user requests and provide responses. (Default value: 8629) Used to handle urgent situations such as Session Full. This port value can be configured by the _LSNR_SPECIAL_PORT parameter in the tip file. (Default value: service port number + 1) Used for secure communication. This port can be configured by the _LSNR_SSL_PORT parameter in the tip file. (Default value: service port number + 2) Used by TBCM. This port can be configured by the CM_PORT parameter in the tip file. (Default value: service port number + 3) 8629 Always 8630 Always 8631 When secure communication is used 8632 When TAC is used 5

6 2. Test Environment VM must be installed before installing Tibero. The following describes the test environment used in this guide Configuring the Test Environment OS Environment Tibero Binary User Directory 2.2. Creating Users tsc10, tsc20 Users Install Linux Centos 6.5 (64-bit) in a virtual machine (virtualbox). Install the Tibero binary for Linux 64-bit (tibero5-bin-5_rel_s1348-linux opt-tested.tar.gz). Create 2 user home directories named tsc10 and tsc20 under the /test directory. tsc10 : Install Primary server tsc20 : Install Standby server # useradd -d /test/tsc10 -g dba tsc10 # useradd -d /test/tsc20 -g dba tsc20 Adds a password for each user # passwd tsc10 Changing password for user tsc10. New password:tibero Retype new password: tibero passwd: all authentication tokens updated successfully. # passwd tsc20 Changing password for user tsc20. New password:tibero Retype new password: tibero passwd: all authentication tokens updated successfully. Creates a DBA group before creating users. - Modify the configuration file to automatically create a home directory when creating a user. # vi /etc/login.defs CREATE_HOME yes 2.3. Port Numbers Primary server (tsc10): 9010 Standby server (tsc20):

7 2.4. Changing Directory Permissions Grant rwx (reading, writing, and execution) permissions for users in the DBA group that includes tsc10 and tsc20. In an actual environment, this task can be omitted because user names are the same in servers that are physically separated. Before modifying permissions # ls l drwx tsc10 dba drwx tsc20 dba 4096 Mar 14 10:36 tsc Mar 14 10:39 tsc20 After modifying permissions # chmod -Rf g+rwx tsc10 # chmod -Rf g+rwx tsc20 # ls l drwxrwx--- 4 tsc10 dba drwxrwx--- 4 tsc20 dba 4096 Mar 14 10:36 tsc Mar 14 10:39 tsc20 7

8 3. Tibero Installation 3.1. Modifying a Configuration File $ cd /test/tsc10 $ vi.bash_profile Add the following. ### Tibero 5 ENV ### export TB_HOME=/test/tsc10/tibero5 export TB_SID=tsc10 export TB_PROF_DIR=$TB_HOME/bin/prof export PATH=.:$TB_HOME/bin:$TB_HOME/client/bin:$JAVA_HOME:$PATH export LD_LIBRARY_PATH=$TB_HOME/lib:$TB_HOME/client/lib:$LD_LIBRARY_PATH Apply and check the modified configuration file $..bash_profile $ echo $TB_HOME /test/tsc10/tibero5 # cd /test/tsc20 # vi.bash_profile Add the following ### Tibero 5 ENV ### export TB_HOME=/test/tsc20/tibero5 export TB_SID=tsc20 export TB_PROF_DIR=$TB_HOME/bin/prof export PATH=.:$TB_HOME/bin:$TB_HOME/client/bin:$JAVA_HOME:$PATH export LD_LIBRARY_PATH=$TB_HOME/lib:$TB_HOME/client/lib:$LD_LIBRARY_PATH Apply and check the modified configuration file. $..bash_profile $ echo $TB_HOME /test/tsc20/tibero5 3.2 Extracting a Tibero Binary File Extract the Tibero binary file in tsc10 and tsc20. - The tibero5 directory is created under /test/tsc10. $ tar -xvzf tibero5-bin-5_rel_s1348-linux opt-tested.tar.gz $ ls l drwxr-xr-x 8 tsc10 dba 4096 Mar 14 11:26 tibero5 8

9 - The tibero5 directory is created under /test/tsc20. $ tar -xvzf tibero5-bin-5_rel_s1348-linux opt-tested.tar.gz $ ls l drwxr-xr-x 8 tsc10 dba 4096 Mar 14 11:26 tibero Copying a License Copy the license file (license.xml) issued through TechNet to the following path $ pwd /test/tsc10/tibero5/license $ ls l -rwxr-x--- 1 tsc10 dba 479 Mar 14 11:39 license.xml drwxr-xr-x 2 tsc10 dba 4096 Mar 14 11:26 oss_licenses $ pwd /test/tsc20/tibero5/license $ ls l -rwxr-x--- 1 tsc10 dba 479 Mar 14 11:39 license.xml drwxr-xr-x 2 tsc10 dba 4096 Mar 14 11:26 oss_licenses 3.4. Data File Location Creating DB and archive files under $TB_HOME can cause a performance issue. To prevent this issue, save the files to a directory outside of $TB_HOME. In this document, a directory is created under the User directory instead of $TB_HOME to save the DB and archive files. $ pwd /test/tsc10 $ mkdir tbdata $ mkdir arch $ ls arch tbdata tibero5 $ pwd /test/tsc20 $ mkdir tbdata $ mkdir arch $ ls arch tbdata tibero5 9

10 3.5. Executing gen_tip.sh Execute the gen_tip.sh script file. The $TB_SID.tip server configuration file, tbdsn.tbr, and psm_commands are created. $ sh /test/tsc10/tibero5/config/gen_tip.sh Using TB_SID "tsc10" /test/tsc10/tibero5/config/tsc10.tip generated /test/tsc10/tibero5/config/psm_commands generated /test/tsc10/tibero5/client/config/tbdsn.tbr generated. Running client/config/gen_esql_cfg.sh Done. Check whether the tsc10.tip ($TB_SID.tip) file was created. $ find ~/ -name $TB_SID.tip /test/tsc10/tibero5/config/tsc10.tip $ sh /test/tsc20/tibero5/config/gen_tip.sh Using TB_SID "tsc20" /test/tsc20/tibero5/config/tsc20.tip generated /test/tsc20/tibero5/config/psm_commands generated /test/tsc20/tibero5/client/config/tbdsn.tbr generated. Running client/config/gen_esql_cfg.sh Done. Check whether the $TB_SID.tip (tsc20.tip) file was created. $ find ~/ -name $TB_SID.tip /test/tsc20/tibero5/config/tsc20.tip 3.6. Modifying a.tip File Modification: DB NAME / port number / tbdata and arch paths : Set the Primary and the Standby to the same name for DB_NAME. $ vi /test/tsc10/tibero5/config/tsc10.tip Modify tsc10.tip. DB_NAME=tscdata LISTENER_PORT=9010 CONTROL_FILES="/test/tsc10/tbdata/c1.ctl" DB_CREATE_FILE_DEST="/test/tsc10/tbdata" LOG_ARCHIVE_DEST="/test/tsc10/arch" $ vi /test/tsc20/tibero5/config/tsc20.tip Modify tsc20.tip. DB_NAME=tscdata LISTENER_PORT=9020 CONTROL_FILES="/test/tsc20/tbdata/c1.ctl" 10

11 DB_CREATE_FILE_DEST="/test/tsc20/tbdata" LOG_ARCHIVE_DEST="/test/tsc20/arch" 3.7. Modifying tbdsn.tbr If modifying LISTENER_PORT and the DB name, LISTENER_PORT and DB_NAME of $TB_HOME\client\config\tbdsn.tbr must also be modified. In other words, the port number and DB_NAME of the $TB_SID.tip file and the tbdsn.tbr file must match to access the DB. $ vi /test/tsc10/tibero5/client/config/tbdsn.tbr Modify tbdsn.tbr. tsc10=( (INSTANCE=(HOST= ) (PORT=9010) (DB_NAME=tscdata) ) ) $ vi /test/tsc20/tibero5/client/config/tbdsn.tbr Modify tbdsn.tbr. tsc20=( (INSTANCE=(HOST= ) (PORT=9020) (DB_NAME=tscdata) ) ) 11

12 4. Tibero Standby Cluster Configuration 4.1. Primary Server The installation process up to the gen_tip.sh execution and modification and the tbdsn.tbr modification step is similar to that of installing Tibero Single. This following describes how to install Tibero Standby Cluster Creating a Database Create a database using db_cre.sql. Redo Log group: 3 Log mode: ARCHIVELOG db_cre.sql file content create database character set UTF8 logfile group 1 size 20m, group 2 size 20m, group 3 size 20m archivelog datafile 'system001.dtf' size 100m autoextend on next 10m default temporary tablespace temp tempfile 'temp001.dtf' size 100m autoextend on next 10m undo tablespace undo0 datafile 'undo001.dtf' size 200m autoextend on next 10m default tablespace usr datafile 'usr001.dtf' size 100m autoextend on next 10m - Start Tibero in nomount mode. $ tbboot -t nomount Listener port = 9010 Change core dump dir to /test/tsc10/tibero5/bin/prof. Tibero 5 Copyright (c) 2008, 2009, 2011, 2012 Tibero Corporation. All rights reserved. Tibero instance started up (NOMOUNT mode). Connect using tbsql $ tbsql sys/tibero tbsql 5 Copyright (c) 2008, 2009, 2011, 2012 Tibero Corporation. All rights reserved. Connected to Tibero. SQL> Check whether db_cre.sql exists in the execution path. If the file does not exist, copy the file to the path. 12

13 - Once the file is created, DB automatically shuts down. Exit tbsql. SQL>!ls bin client config db_cre.sql instance lib license scripts Database created. File finished Creating Dictionary and Package Execute system.sh in $TB_HOME/scripts to create roles, system users, views, packages, etc. When executing system.sh, passwords for sys and syscat accounts are required. The following are the default passwords. sys: tibero syscat: syscat Enter Y when being asked to create the following each item. Category default system users & roles Profile-related tables APM tables Description For the initial installation, enter Y. For a subsequent installation, enter Y or N. For the initial installation, enter Y. For a subsequent installation, if Y is entered, existing tables are removed and new tables are created. Enter N to avoid creating tables. For the initial installation, enter Y. For a subsequent installation, enter N to maintain APM data or Y for other cases. $ tbboot Listener port = 9010 Change core dump dir to /test/tsc10/tibero5/bin/prof. Tibero 5 Copyright (c) 2008, 2009, 2011, 2012 Tibero Corporation. All rights reserved. Tibero instance started up (NORMAL mode). $ sh /test/tsc10/tibero5/scripts/system.sh Enter SYS password: tibero Enter SYSCAT password: syscat Create default system users & roles?(y/n): y Create system tables related to profile?(y/n): y Register dbms_stats job to Job Scheduler?(Y/N): y Create APM tables?(y/n): y Check whether the items were created successfully. $ cat /test/tsc10/tibero5/instance/tsc10/log/system_init.log. 13

14 $ tbsql sys/tibero SQL> col db_name for a10 ; SQL> select instance_name, db_name,version, status from v$instance; INSTANCE_NAME DB_NAME VERSION STATUS tsc10 tscdata 5 NORMAL SQL> col owner for a10; SQL> select owner from dba_objects where object_name ='DATABASE_PROPERTIES'; OWNER PUBLIC SYSCAT SQL> set lin 200 SQL> col name for a10 SQL> col value for a15 SQL> col comment_str for a40 SQL> select * from database_properties NAME VALUE COMMENT_STR DFLT_PERM_TS USR Name of default permanent tablespace DFLT_TEMP_TS TEMP Name of default temporary tablespace DFLT_UNDO_TS UNDO Name of default undo tablespace NLS_CHARACTERSET UTF8 NLS_NCHAR_CHARACTERSET UTF16 DB_NAME tscdata database name SQL> exit If the items were created successfully, terminate Tibero using tbdown. $ tbdown Modifying the Primary.tip File Set the database information to connect from the Primary to the Standby, and set each Standby type and operation mode. $ vi /test/tsc10/tibero5/config/tsc10.tip Add the following. LOG_REPLICATION_MODE = PROTECTION LOG_REPLICATION_DEST_1 = " :9020 LGWR SYNC" The following are the configuration types for LOG_REPLICATION_MODE. Category PROTECTION Description The Primary must connect to one or more Standbys, which receive Redo log files with LGWR SYNC. When the Primary sends a Redo log file to the Standbys, LGWR must receive at least one successful reply from the Standbys. If LGWR does not receive a successful reply from any 14

15 Standby, the Primary terminates. AVAILABILITY PERFORMANCE The Primary must connect to one or more Standbys, which receive Redo log files with LGWR SYNC. If LGWR does not receive a successful reply from any Standbys, the Primary does not try to send a Redo log file, but it does not terminate. This does not guarantee synchronization of the Primary and the Standbys. However, it can improve system performance. The following are the configuration types for LOG_REPLICATION_DEST_N. Category LGWR SYNC LGWR ASYNC ARCH ASYNC 4.2. Standby Server Description Standbys, which receive Redo log files with this method, operate by receiving information from the Redo buffer of the Primary. Because LGWR SYNC is more frequently used by Standbys to receive Redo log files, this method provides the most data protection but decreases the performance of the Primary. Building the Primary and Standbys with similar hardware specifications is recommended. Standbys receive Redo log files with this method second most frequently. If one or more Standbys, which receive Redo log files with this method, exist, the Primary must operate in ARCHIVELOG mode. If not, a corresponding server normally starts, but corresponding Standbys do not operate. Reference: Tibero Administrator s Guide 8.5. Primary Settings and Operations Copying the Primary DB File Confirm the installed primary server process is down before creating a Standby database. - Copy all files in the tbdata directory of the primary server to the tbdata directory of the Standby server. - If a permission error occurs, grant the group permission to the primary server using chmod. # ps -ef grep tbsvr root :55 pts/3 00:00:00 grep tbsvr # chmod -Rf g+rwx tbdata - Copy the Primary DB files. $ cp -rf /test/tsc10/tbdata/* /test/tsc20/tbdata/ Copy the password file $ cp -rf /test/tsc10/tbdata/.passwd /test/tsc20/tbdata/ Grant permissions # chmod -Rf g+rwx tbdata # chmod -Rf g+rwx arch Verify $ ls al 15

16 drwxrwxr-x 3 tsc20 dba 4096 Mar 14 16:21. drwxrwx--- 7 tsc20 dba 4096 Mar 14 15:18.. -rw-rwx--- 1 tsc20 dba Mar 14 16:20 apm_ts.dtf -rw-rwx--- 1 tsc20 dba Mar 14 16:20 c1.ctl -rw-rwx--- 1 tsc20 dba Mar 14 16:20 log001.log -rw-rwx--- 1 tsc20 dba Mar 14 16:20 log002.log -rw-rwx--- 1 tsc20 dba Mar 14 16:20 log003.log -rw-rwxr-- 1 tsc20 dba 24 Mar 14 16:21.passwd drwxrwx--- 2 tsc20 dba 4096 Mar 14 16:20 psm -rw-rwx--- 1 tsc20 dba Mar 14 16:20 system001.dtf -rw-rwx--- 1 tsc20 dba Mar 14 16:20 temp001.dtf -rw-rwx--- 1 tsc20 dba Mar 14 16:20 undo001.dtf -rw-rwx--- 1 tsc20 dba Mar 14 16:20 usr001.dtf Modifying a.tip File $ vi /test/tsc20/tibero5/config/tsc20.tip If the Standby directory path to the backup is different, change the information for the path. - STANDBY_FILE_NAME_CONVERT="Primary absolute path, Standby absolute path" STANDBY_FILE_NAME_CONVERT="/test/tsc10, /test/tsc20" Reference: Tibero Administrator s Guide Setting Up and Operating the Standbys Applying the Control File - After booting the Standby in MOUNT mode and executing the following DDL, the changed path is applied to the control file. $ tbboot t mount Listener port = 9020 Change core dump dir to /test/tsc20/tibero5/bin/prof. Tibero 5 Copyright (c) 2008, 2009, 2011, 2012 Tibero Corporation. All rights reserved. Tibero instance started up (MOUNT mode). $ tbsql sys/tibero tbsql 5 Copyright (c) 2008, 2009, 2011, 2012 Tibero Corporation. All rights reserved. Connected to Tibero. SQL> ALTER DATABASE Standby controlfile; Database altered. SQL> exit Starting in Recovery Mode 16

17 Standbys must be started in Recovery mode. Note that if a Standby is used in NORMAL mode even once, the database is not able to function as a Standby. To prepare the DB to act as a Standby, repeat the previous steps. $ tbdown Tibero instance terminated (NORMAL mode). $ tbboot -t RECOVERY Listener port = 9020 Change core dump dir to /test/tsc20/tibero5/bin/prof. Tibero 5 Copyright (c) 2008, 2009, 2011, 2012 Tibero Corporation. All rights reserved. Tibero instance started up (RECOVERY mode). 17

18 5. Starting TSC 5.1. Checking the Mode Used to Start Standbys - Check again that all Standby servers started in Recovery mode. $ ps -ef grep tbsvr tsc :01 pts/5 00:00:01 tbsvr -n 4 -t RECOVERY -SVR_SID tsc20 tsc :01 pts/5 00:00:00 tbsvr_wt001 -n 4 -t RECOVERY -SVR_SID tsc20 tsc :01 pts/5 00:00:00 tbsvr_wt002 -n 4 -t RECOVERY -SVR_SID tsc20 tsc :01 pts/5 00:00:00 tbsvr_wt003 -n 4 -t RECOVERY -SVR_SID tsc20 tsc :01 pts/5 00:00:00 tbsvr_seqw -n 4 -t RECOVERY -SVR_SID tsc20 tsc :01 pts/5 00:00:00 tbsvr_logw -n 4 -t RECOVERY -SVR_SID tsc20 tsc :01 pts/5 00:00:00 tbsvr_loga -n 4 -t RECOVERY -SVR_SID tsc20 tsc :01 pts/5 00:00:00 tbsvr_ckpt -n 4 -t RECOVERY -SVR_SID tsc20 tsc :01 pts/5 00:00:00 tbsvr_blkw000 -n 4 -t RECOVERY -SVR_SID tsc Starting the Primary $ tbboot Change core dump dir to /test/tsc10/tibero5/bin/prof. Tibero 5 Copyright (c) 2008, 2009, 2011, 2012 Tibero Corporation. All rights reserved. Tibero instance started up (NORMAL mode). 18

19 6. Checking TSC Functions 6.1. TSC Information Inquiry of the Primary and the Standby - Primary server $ tbsql sys/tibero tbsql 5 Copyright (c) 2008, 2009, 2011, 2012 Tibero Corporation. All rights reserved. Connected to Tibero. SQL> col standby_addr for a15 SQL> col type for a10 SQL> col flags for a10 SQL> set lin 100 SQL> select * from v$standby_dest; STANDBY_ADDR TYPE FLAGS SENT_SEQ SENT_BLKNO ACKED_SEQ ACKED_BLKNO :9020 LGWR SYNC CONNECTED Standby server $ tbsql sys/tibero tbsql 5 Copyright (c) 2008, 2009, 2011, 2012 Tibero Corporation. All rights reserved. Connected to Tibero. SQL> ALTER DATABASE open read only; SQL> select * from v$standby; PRIMARY_ADDR STATUS :0 STANDBY, RECOVERY IN PROGRESS 6.2. Data Copy - To test in real-time, change Standby mode as follows. SQL> ALTER DATABASE open read only continue recovery; Database altered. - Create data to test the Primary server. SQL> CREATE TABLESPACE tman_space DATAFILE 'tman_file.dtf' SIZE 10M; SQL> CREATE USER tman IDENTIFIED BY tibero DEFAULT TABLESPACE tman_space; SQL> GRANT create session, create table TO tman; SQL> CONNECT tman/tibero; SQL> CREATE TABLE t1 AS SELECT LEVEL c1 FROM DUAL CONNECT BY LEVEL <= 10; SQL> CREATE TABLE t2 AS SELECT LEVEL c1 FROM DUAL CONNECT BY LEVEL <= 20; 19

20 Check whether the table and data were created. SQL> select count(*) from tman.t1; COUNT(*) SQL> select count(*) from tman.t2; COUNT(*) Check that the data was copied to the Standby server successfully. - Check that the tables and data created in Primary were copied to the Standby server successfully. SQL> select count(*) from tman.t1; COUNT(*) SQL> select count(*) from tman.t2; COUNT(*) Switchover The following describes how to change a Standby into a Primary after shutting down the Primary. - After all Standbys are synchronized with the Primary, the Primary is shut down. $ tbdown -t SWITCHOVER. - If the Standby is in read-only mode, change the mode to Standby mode and then to Open mode. SQL> ALTER DATABASE Standby; Database altered. SQL> ALTER DATABASE open; Reference: Tibero Administrator s Guide Switchover 6.4. Failover If the Primary terminates abnormally or is inaccessible, one of the Standbys can be act as the Primary. To use a Standby as the Primary, shut down the Standby and then boot in NORMAL mode, or run the ALTER DATABASE open statement. The existing Primary cannot be included in a Tibero Standby Cluster as a Primary or as a Standby after a new Primary is operating. Reference: Tibero Administrator s Guide Failover 20

21 Copyright 2014 TmaxData Co., Ltd. All Rights Reserved. Trademarks Tibero RDBMS is a registered trademark of TmaxData Co., Ltd. Other products, titles or services may be registered trademarks of their respective companies. Brazil TmaxSoft Brazil Avenida Copacabana, andar 18 do Forte Empresarial, Alphaville - Barueri, Sao Paulo, SP- Brasil CEP contato.brasil@tmaxsoft.com Contact Information TmaxData can be contacted at the following addresses to arrange for a consulting team to visit your company and discuss your options. Korea TmaxData Co., Ltd 5, Hwangsaeul-ro 329beon-gil, Bundang-gu, Seongnam-si, Gyeonggi-do. South Korea Tel: Fax: info@tmax.co.kr Web (Korean): Technical Support: USA TmaxSoft, Inc. 560 Sylvan Avenue Englewood Cliffs, NJ U.S.A Tel: Fax: info@tmaxsoft.com Web (English): Russia Tmax Russia L.L.C. Grand Setun Plaza, No A204 Gorbunova st.2, Moscow, Tel: +7(495) info.rus@tmaxsoft.com Web (Russian): Singapore Tmax Singapore Pte. Ltd. 430 Lorong 6, Toa Payoh #10-02, OrangeTee Building. Singapore Tel: info.sg@tmaxsoft.com United Kingdom TmaxSoft UK Ltd. Surrey House, Suite 221, 34 Eden Street, Kingston- Upon-Thames, KT1 1ER United Kingdom Tel: + 44-(0) info.uk@tmaxsoft.com Web (English): Japan TmaxSoft Japan Co., Ltd. 5F Sanko Bldg, Mita, Minato-Ku, Tokyo, Japan Tel: Fax: info.jp@tmaxsoft.com Web (Japanese): China TmaxSoft China Co., Ltd. Beijing Silver Tower, RM 1508, 2 North Rd Dong San Huan, Chaoyang District, Beijing, China, China Tel: ~8 Fax: info.cn@tmaxsoft.com Web (Chinese): TN-TRGI-D