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

Depending on the type of application and functionality being tested, users may not fail over. For example, in
a highly insert-intensive application like concurrent manager (CM) in an E-Business Suite (EBS) system that is not
designed to automatically rollback and re-execute the transaction, the CM manager is going to experience an error
message.

Step 3
After making the required fixes to both the ONS and the application connect descriptors, the test was executed again.
Querying the database for connections, it was found that the users were more evenly distributed (see also Table 3-6 ):

INT USERNAME SERVICE_NA FM FT FO STATUS COUNT(*)
---- -------------- ---------- ---------- ------ ---- ---------- --------
1 APPS EBSPRD BASIC SELECT NO INACTIVE 20
APPS EBSWEB BASIC SELECT NO ACTIVE 113
CORBIT CORBIT BASIC SELECT NO ACTIVE 92
DBSNMP SYS$USERS NONE NONE NO ACTIVE 1
SYS SYS$USERS NONE NONE NO ACTIVE 3
2 APPS EBSPRD BASIC SELECT NO INACTIVE 10
APPS EBSWEB BASIC SELECT NO ACTIVE 112
BCIDBA EBSPRD BASIC SELECT NO INACTIVE 3
CORBIT CORBIT BASIC SELECT NO ACTIVE 60
DBSNMP SYS$USERS NONE NONE NO ACTIVE 1
SYS SYS$USERS NONE NONE NO ACTIVE 1
. . . . . . . .
. . . . . . . . .
6 APPS EBSPRD BASIC SELECT NO INACTIVE 9
APPS EBSWEB BASIC SELECT NO INACTIVE 6
APPS EBSWEB BASIC SELECT NO ACTIVE 110
BCIDBA EBSPRD BASIC SELECT NO INACTIVE 4
CORBIT CORBIT BASIC SELECT NO ACTIVE 60
DBSNMP SYS$USERS NONE NONE NO ACTIVE 1
SYS SYS$USERS NONE NONE NO ACTIVE 1

Table 3-6. RAP III—Testing the Application for Availability

Test # Description #of Users Test Case & Functionality Description Statistics Status

1 Baseline test 300 All app servers and

& db servers accessible

Complete

2 Test 1 300 Shutdown abort

instance 2

Users should
fail over

No users failed
over; instance
recovery time =
12 seconds

Error

2(a) Test 1 300 Shutdown abort

instance 2

Users should
fail over

Users failed over;
instance recovery
time = 8 seconds

Complete