Testing for Availability - Expert Oracle RAC Performance Diagnostics and Tuning - page 72

Step 3
Once there, the workload has stabilized and the connections can be seen against the database and the actual test can
begin. For this step of the test, we would need the assistance of the system/network administrator who has access to
the data center to physically pull cables from the interface.

Script: MVRACPDnTap_taftest.sql
INT USERNAME SERVICE_NA FM FT FO STATUS COUNT(*)
---- -------- ---------- ----- ------ ---- -------- --------
1 DBSNMP SYS$USERS NONE NONE NO ACTIVE 1
RAPDWH PRDDB BASIC SELECT NO ACTIVE 385
. . . .. .
.. .. . .

6 DBSNMP SYS$USERS NONE NONE NO ACTIVE 2
RAPDWH PRDDB BASIC SELECT NO ACTIVE 386

The preceding output illustrates connections against six instances and all of them are connected using the
transparent application failover (TAF) policy of BASIC and SELECT .

Step 4
Once the system administrator physically pulls the cable to the interface device, the results should be observed. In this
test scenario, when one HBA cable was pulled, it did not affect the user connections to the database (see Table 3-2 ).

Table 3-2. Test 1 Results Recorded

Test # Host Name Interface Test method Expected

Behavior

Observation /
Result

Status Node1 Node2 Node3

1 Db1 HBA1 Pull Stable

Server

Cluster Stable OK UP UP UP

Script: MVRACPDnTap_taftest.sql
INT USERNAME SERVICE_NA FM FT FO STATUS COUNT(*)
---- --------- ---------- ------- ------ ---- -------- --------
1 DBSNMP SYS$USERS NONE NONE NO ACTIVE 1
RAPDWH PRDDB BASIC SELECT NO ACTIVE 385
. . . .. .
.. .. . .

3 DBSNMP SYS$USERS NONE NONE NO ACTIVE 2
RAPDWH PRDDB BASIC SELECT NO ACTIVE 286
. . . . . .
. . . . . .
6 DBSNMP SYS$USERS NONE NONE NO ACTIVE 2
RAPDWH PRDDB BASIC SELECT NO ACTIVE 386