Skip to end of metadata
Go to start of metadata


Overview

The RAC system comprises internal network between several nodes.

Therefore when node A is requested to transfer changed data from node B, Node A delivers DB block(changed data) to node B via Inter-Connect Network.

we call it as a Cache Fusion.

Features of ORACLE RAC

  • The plural nodes constituting RAC system have each independent SIDs.

Using Altibase HDB Replication, The replication target servers have different DB_NAME as different nodes.

  •  An independent nodes comprising RAC system share Disk.

In case of the Altibase HDB Replication, it only applies redo logs(xLog) delivered from the remote server over TCP/IP protocol.

  • Application Failover

The Fail-Over feature is provided so that a fault that occurs while a database is providing service can be overcome and service can continue to be provided as though no fault had occurred.

Oracle RAC provides CTF(Connection Time Failover) and TAF(Transparent Application Failover).

Altibase HDB Replication supports CTF and STF 

  1. CTF: When the fault is noted at the time of connection to the DBMS, and connection is made to a DBMS on another available node rather than to the DBMS suffering from the fault, so that service can continue to be provided.
  2. TAF: After a fault occurs while service is being provided after successful connection to the DBMS, reconnection is made to a DBMS on another available node, and session properties are restored, so that the business logic of the user's application can continue to be used. In other words, it is called as STF(Service Time Failover)
  • Load Balancing
  1. Client-Side Connect-Time Load Balancing: This functionality can be done by sending a request for connection among available listener list. As it were, A client attempts to a DB server in a random order.This can be available by setting to "LOAD_BALANCE = ON"  in tnsnames.ora file of the client. If this value is set to off, a client tries to connect to the server listed in the first address of tnsnames.ora                   If failed, the access to the next address will be attempted. 
  2. Server-Side Connect-Time Load Balancing: It is done by setting on the side of server. PMON Process does register service information to Listener automatically.                                                               After then, at the time of client's request for connection, server makes an attempt to connect using the protocol address in the tnsnames.ora file of the client.

How does Application Failover setup

Oracle


Altibase

Icon

To register Fail-Over option, You may choose from the followings. For further information, refer to this page

Connection String in a Client Application

Connection Properties in the Settings File((altibase_cli.ini or odbc.ini file)

  

Connection String of the client application's connection function

  • No labels