Please see my other blog for Oracle EBusiness Suite Posts - EBMentors

Search This Blog

Note: All the posts are based on practical approach avoiding lengthy theory. All have been tested on some development servers. Please don’t test any post on production servers until you are sure.

Monday, December 06, 2010

Monitoring Oracle 10g RAC with Quest Spotlight on RAC

For a RAC DBA following are the normal questions
  • How is my cluster performing? 
  • How is my Database performance as a whole? 
  • Contention issues disk, io, cluster, interconnect? 
  • Latency problems within HSI (High Speed Interconnects)? Are there poor settings? Are my NIC's are set properly? Or is it a poorly configured RAC? 
  • Inter-node communication issues? Are too many "Hot Blocks" being transferred across nodes due to poor database design? 
  • Poor load balancing?      

If you are curious about the following questions then Spotlight on RAC by Quest Software may be the good choice for you. As I'm also using this product for my questions like above.
This product provides the following classes of functionalities to the RAC DBA.

1- Physical architecture, all of the essential components of a cluster: the individual instances, the interconnect and the I/O subsystem are displayed, including the essential data flows between them. 
The below example runs against my 2-node Windows 2003(64bit) Oracle 10g R2 RAC. 

2- Calculation of diagnostics and presenting them back to the interface as a whole. For instance, you might have latch contention on one node on a 6-node RAC and the aggregate of all the latches might just be fine for your RAC to function adequately. 

3- everal RAC specific alarms(email notification) such as:
  1. Uneven Load Distribution to the instances.
  2. Overhead due to cluster maintenance.
  3. High latency problems within the HSI (High Speed Interconnects).
  4. Excessive HSI communication (might point to partitioning data across nodes, for instance a typical hybrid , meaning OLTP (Online Transaction Processing) /DSS (Decision Support System) might require a data partitioning on the DSS part of that RAC database).
  5. Block Corruption / Orphaned blocks across instances.
  6. OCFS problems / Shared Disk (Whether on SAN/NAS) contention. 

No comments: