Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

Spotlight on Oracle 11.0 - Getting Started Guide

Table of Contents

Welcome to Spotlight Install Spotlight

Multiple Concurrent Installations MSI Installers for Spotlight on Oracle Uninstall Spotlight

Start Spotlight

Authorize Spotlight

Spotlight on Oracle

Connect to an Oracle Database

Oracle Connection Details

Oracle User Wizard

DBA Connection Credentials User Account New Oracle User Select Tablespace Predictive Diagnostics Ready To Configure Oracle User End

Configuring Oracle User for Spotlight Dialog Toad DBA Suite for Oracle Oracle Architecture Overview Spotlight on Oracle Home Page Spotlight on Oracle Alarms Spotlight on Oracle Drilldowns Install And Configure DTrace Scripts Tune Your Oracle Database Predictive Diagnostics Spotlight on Oracle Tools: Explain Plan, SQL Optimizer, Space Manager

Spotlight on Oracle Data Guard

Standby Connections Dialog Spotlight on Oracle Data Guard Home Page Spotlight on Oracle Data Guard Alarms

Spotlight on Oracle RAC

Connect to Spotlight on Oracle RAC

Oracle RAC Connection Details Verify Cluster Connection Details Dialog Connect to an Exadata Storage Server (Cells)

Spotlight on Oracle RAC Home Page Spotlight on Oracle RAC Alarms Spotlight on Oracle RAC Drilldowns

Spotlight on Unix

Configure the Unix System Connect to Unix Systems

Unix Connection Details

Spotlight on Unix Home Page Spotlight on Unix Alarms Spotlight on Unix Drilldowns

Spotlight on Windows

Connect to Windows Systems

Windows Connection Details

Spotlight on Windows Home Page Spotlight on Windows Alarms Spotlight on Windows Drilldowns

Troubleshooting: Connection Problems

Troubleshooting Spotlight on Windows

The Registry ... is not accessible. Connecting As The Logged-in User WMI Connection Problems

Spotlight on Oracle

Corrupt Blocks Alarm

Spotlight raises separate alarms for corrupt and lost blocks. The Corrupt Blocks alarm is raised when the percentage of corrupt blocks exceeds a threshold as a proportion of total global cache consistent read requests. Possible causes for this alarms are:

The Cluster Interconnect has been overloaded by an excessive number of block transfers.
Checksum processes have been disabled, and can no longer identify corrupted blocks.

Possible solutions to these problems are:

To upgrade or reconfigure the cluster interconnect.
To partition tables or segregate application activity to reduce the number of block transfers.

Related Topics

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating

© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center