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

Table 4-14. RAP VIII Recording Every 2 Hours

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

. . . . . . . . .
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

. . . . . . .
16 02/18/2011 12:00noon 100 Entire stack 6 8

Note: N/A = not available.

■ this report should be used for educational and reference purposes only. the report is not a complete report and
the results indicated may vary from environment to environment based on the configuration such as o/s, application, and
infrastructure being deployed.

Note

Conclusion
Testing cannot be ignored under any circumstances. As we discussed earlier, scalability and availability are the
primary benefits of moving to RAC configuration. What if these benefits cannot be achieved? What if the project is
deployed into production and the performance is worse than it was on a single instance non-RAC database? Maybe
the application cannot be made scalable and RAC maybe a bad choice or maybe RAC is not required to achieve
scalability. It cannot be stressed enough how important it is to test the RAC cluster. On several occasions, RAC
deployments have failed after moving into production because they have never been tested. RAP testing from Phase
I thru Phase VIII are allcritical and should be completed for a smooth transition from single instance to a clustered
scalable solution.