How to Reduce ASAP Failover (Switch Over) Time? (Doc ID 1996046.1)

Last updated on OCTOBER 04, 2016

Applies to:

Oracle Communications ASAP - Version 7.2.0 and later
Information in this document applies to any platform.

Goal

The following two cases of ASAP HA were tested on production, successfully -

Case 1: Node1 - Instance shutdown
ASAP was using Node 1 to connect to DB. On Node 1 instance shutdown, ASAP successfully switched to Node 2 instance. Though ASAP switch-over was not immediate (nearly a minute) but it was successful.


Case 2: Node 2- OS shutdown (Hardware failure case. Also, similar to bringing listener down)
ASAP was using Node 2 to connect to DB. On Node 2 OS shutdown, ASAP successfully switched to Node 1 instance. Though ASAP switch-over was not immediate (nearly a minute) but it was successful.


PS: ASAP is using two VIPs for DB connection -
DB_CONNECT=(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = xx.xx.xx.xx)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = xx.xx.xx.xx)(PORT = 1521)) (LOAD_BALANCE = NO) (FAILOVER = TRUE) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = asapdb)))


Concern here is that the ASAP switch-over was not immediate (nearly a minute) but it was successful.
Can we reduce this failover time ?
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms