Tibero


Tibero is a relational databases and database management system utility developed by TmaxSoft. TmaxSoft has been developing Tibero since 2003, and in 2008 it was the second company in the world to deliver a shared-disk-based cluster, TAC. The main products are Tibero, Tibero MMDB, Tibero ProSync, Tibero InfiniData and Tibero DataHub.
Tibero, a Relational Database Management System is considered an alternative to Oracle Databases due to its complete compatibility with Oracle products, including SQL.
Tibero guarantees reliable database transactions, which are logical sets of SQL statements, by supporting ACID. Providing enhanced synchronization between databases, Tibero 5 enables reliable database service operation in a multi node environment.
Tibero has implemented a unique Tibero Thread Architecture to address the disadvantages of previous DBMS. As a result, Tibero can make efficient use of system resources, such as CPU and memory, through fewer server processes. This ensures that Tibero offers a combination of performance, stability, and expandability, while facilitating development and administration functions. Additionally, it provides users and developers with various standard development interface to easily integrate with other DBMS and 3rd party tools.
In addition, the block transfer technology has been applied to improve ‘Tibero Active Cluster’- the shared DB clustering technology which is similar to Oracle RAC. Tibero supports self-tuning based performance optimization, reliable database monitoring, and performance management.
In Korea, Tibero has been adopted by more than 450 companies across a range of industries from Finance, Manufacturing and Communication, to the public sector and globally by more than 14 companies, as of July 2011.

TIBERO Products

History

Tibero uses multiple working processes, and each working process uses multiple threads. The number of processes and threads can be changed. User requests are handled by the thread pool, but removes the overhead of the dispatcher, which handles input/output processing. The memory usage and number of OS processes can be reduced by using the thread pool. The number of simultaneous processes can be changed.

Concepts

Tibero has the following three processes:

Listener

Listener receives requests for new connections from clients and assigns them to an available working thread. Listener plays an intermediate role between clients and working threads using an independent executable file, tblistener.

Working process or foreground process

Background processes are independent processes that primarily perform time-consuming disk operations at specified intervals or at the request of a working thread or another background process.
The following are the processes that belong to the background process group:
Monitor Thread (MTHR)
Tibero RDBMS provides distributed database links, data replication, database clustering which is similar to Oracle RAC., parallel query processing, and query optimizer. It conforms with SQL standard specifications and development interfaces and guarantees high compatibility with other types of databases.
Other features include; Row-level locking, multi-version concurrency control, Parallel query processing, and partition table support.

Major features

Distributed Database Links

Tibero RDBMS enables a stable and efficient management of DBMSs and guarantees high-performance transaction processing, using the Tibero Active Cluster technology, which is a failover operation based on a shared disk clustering system environment. TAC allows instances on different nodes to share the same data via the shared disk. It supports stable system operation with the fail-over function, and optimal transaction processing by guaranteeing the integrity of data in each instance’s memory.
TAC is the main feature of Tibero for providing high scalability and availability. All instances executed in a TAC environment execute transactions using a shared database. Access to the shared database is mutually controlled for data consistency and conformity.
Processing time can be reduced because a larger job can be divided into smaller jobs, and then the jobs can be performed by several nodes.
Multiple systems share data files based on shared disks. Nodes act as if they use a single shared cache by sending and receiving the data blocks necessary to organize TAC through a high speed private network that connects the nodes.
Even if a node stops while operating, other nodes will continue their services. This transition happens quickly and transparently.
TAC is a cluster system at the application level. It provides high availability and scalability for all types of applications. So, It is recommended to apply a replication architecture to not only servers but also to hardware and storage devices. This helps improve high availability. Virtual IP is assigned for each node in a TAC cluster. If a node in the TAC cluster has failed, its Public IP cannot be accessed but Virtual IP will be used for connections and for connection failover.

Main components

The following are the main components of TAC.

Cluster Wait-Lock Service (CWS)