TAS Instance Management
This chapter describes how to configure TAS initialization parameters, how to start a TAS instance, how to configure the Tibero initialization parameters for using TAS, and how to create a database.
TAS Initialization Parameter Configuration
First, configure LISTENER_PORT, MAX_SESSION_COUNT, MEMORY_TARGET, and TOTAL_SHM_SIZE
according to the system configuration.
Additionally, configure the following initialization parameters.
INSTANCE_TYPE
String value.
Type: String
Available values: "TIBERO" | "AS" | "ACTIVE_STORAGE"
Default value: "TIBERO"
AS_DISKSTRING
TTAS disk path.
Type: String
Available values: Disk path
Default value: ""
The following are initialization parameter configuration examples.
Using a single disk
Using multiple disks (comma as delimiter)
Using multiple disks with wildcard pattern matching
Using '?' at the beginning of the path to reference TAS home directory
The following are optional initialization parameters.
AS_ALLOW_ON LY_RAW_DISKS
If set to 'N', files in a general file system are recognized as a disk device to be used as a TAS disk.
Type: Boolean
Options: Y | N
Default value: Y
AS_WTHR_CNT
Number of rebalancing threads to create during TAS instance startup. The threads process rebalancing or resynchronization.
Type: Integer
Value: Positive integer
Default value: 10
TAS Instance Management
This section describes how to manage a TAS instance.
Preparations
Configure the TB _SID and TB _HOME environment variables.
Configure the TAS access information in the $TB_HOME/client/config/tbdsn.tbr file to access to tbsql.
Create a tip file for the TAS instance configuration.
At least one disk device is required for using TAS .
To use the TAS clustering function, at least one shared disk is required.
TAS Startup
This section describes the environment configurations needed for starting up a TAS instance using an example file.
The TAS instance that uses a tip file in the following example uses all disk devices in "/devs/disk*" as aTAS disk.
[Example 1] TAS Instance tip File Example
When starting up a TAS instance for the first time, it must be started up in NOMOUNT mode.
Use tbsql to connect to the TAS instance that is running in NOMOUNT mode. Next, create the default disk space by using the CREATE DISKSPACE SQL statement.
The following DDL statement is an example of using the CREATE DISKSPACE clause.
A TAC instance automatically shuts down when the default disk space is created. After a default disk space is created, a TAS instance can be started up in NORMAL mode. Even when an additional disk space is created, the instance does not shut down.
The following example shows the tip file of each required instance when starting up two TAS instances as a cluster. The TAS instances that use this tip file use all the shared disk devices in "/devs/disk*" as a TAS disk. Set CM_PORT to the port number specified in CM_UI_PORT of the CM_TIP file.
[Example 2] TAS Instance Clustering tip File Example: <as0.tip>
[Example 3] TAS Instance Clustering tip File Example: <cm0.tip>
[Example 4] TAS Instance Clustering tip File Example: <as1.tip>
[Example 5] TAS Instance Clustering tip File Example: <cm1.tip>
After starting up a TAS instance in the NOMOUNT mode and creating a disk space, start up TBCM and then add clustering resources as in the following example. When adding the clustering resources, enter '+' followed by the disk path set in AS_DISKSTRING of the tip file for the cfile attribute, so that the path can be recognized as a path for TAS.
[Example 6] Creating a Configuration File for the as Resource: <as0.profile>
Now the TAS instance with a TB_SID of 'as0' can be started up.
Before starting up the TAS instance 'as1', the REDO thread must be added to the instance.
Start up TBCM and add clustering resources as follows. The service resources added when CM_SID=cm0 do not need to be added.
[Example 7] Creating a Configuration File for the as Resource: <as1.profile>
Now the TAS instance 'as1' can be started up.
TAS Shutdown
Run the tbdown command to shut down a TAS instance. tbdown shuts down all Tibero instances currently using that TAS instance.
TAS Binary Replace
To replace the existing binary with a new one when the TAS instance has been already configured, the following must be executed to prevent an incompatibility issue between the old and new versions.
'ds0' is the name of the default disk space.
Tibero Instance Configuration
For a Tibero instance to use a TAS disk space, configure the following initialization parameters in the tip file of Tibero.
USE_ACTIVE_STORAGE
Option to use the Active Storage file. Set to 'Y'.
Type: Boolean
Options: Y | N
Default value: N
AS_ADDR
IP address of a TAS instance that will be used by the Tibero instance.
Type: String
Allowed value: IP address as String
Default value: "127.0.0.1"
AS_PORT
LISTENER_PORT value of a TAS instance that will be used by the Tibero instance.
Type: Integer
Allowed values: 1024 ~ 65535
Default value: 0
The following shows the tip file that is required for running a Tibero instance that uses a TAS instance. The Tibero instance that uses this tip file stores the control file in the disk space named 'ds0'.
[Example 8] Example of a Tibero Instance tip File that uses a TAS instance.
When setting the DB_CREATE_FILE_DEST initialization parameter to "+{disk space name}", if the LOG_ARCHIVE_DEST, PSM_SHLIB_DIR, and JAVA_CLASS_PATH initialization parameters are not configured manually, then the child directories of DB_CREATE_FILE_DEST are set to their default values. Since TAS currently does not support directories, these parameters must be manually configured as in the following example.
The following example shows how to create a Tibero database that uses a TAS file. The paths of the files that make up the database, which are stored in the disk space "ds0", must be specified in the "+DS0/..." format.
[Example 9] Example of the CREATE DATABASE of the Tibero Instance that uses a TAS File
Last updated