Testing for Scalability - Expert Oracle RAC Performance Diagnostics and Tuning - page 107

Along with the log being maintained in Table 4-12 , screenshots and reports from the LoadRunner, Automatic
Workload Repository (AWR), Automatic Database Diagnostic Monitor (ADDM), and other health check tools should
also be collected and maintained.

Step 4
Similar to Step 3, continue the monitoring and recording of information every 4 hours. Record any kind of issues
encountered. Table 4-13 illustrates an issue with the dataguard configuration. The DR site is not able to keep up with
the redo log ship rates. The apply process is far behind and has created a large gap between the primary and standby
environments. The primary site has switched from redo log shipping to archive log shipping. This is critical in a
production environment and should be minimized.

Table 4-13. RAP PhaseVIII Recording Test Progress

Checkpoint # Checkpoint

Date

Checkpoint
Time

# of
Users

Checkpoint/
Verified
Component

# of Db
Servers

# of App
Servers

Description Status

1 02/16/2011 8:00 am 100 N/A 6 8 Start of RAP VIII Success

2 02/16/2011 12:00 noon 100 Entire stack 6 8 Overall health

of the environment

Good

3
. . . . . . . . . .
. . . . . . . . .
8

02/17/2011 12 :00 noon 100 Entire stack 6 8 Archive log gaps

Apply process
behind
compared to
the redo
switch rates

Warning

Note: N/A = not available.

Step 5
On completion of the 48 hours of successful testing, the results should be recorded in the table (illustrated in
Table 4-14 ) and should be documented. Final conclusions of the tests should be presented/reviewed with the DBA
team and subsequently with the project team. The results of the tests should be the deciding factor to determine if the
environment is ready for prime time production.