Beruflich Dokumente
Kultur Dokumente
1
Getting Started Guide
Table of Contents
Welcome
Home Page
Alarms
Drilldowns
Features of Spotlight
10
10
10
10
Predictive Diagnostics
10
11
Install Spotlight
12
Requirements
12
Steps To Install
13
14
14
Uninstall Spotlight
14
Start Spotlight
15
Project Lucy
15
Authorize Spotlight
16
Spotlight Users
17
Spotlight on Oracle
Connect to Oracle Databases
17
20
20
Table of Contents
20
25
26
26
Sessions Panel
27
Host Panel
28
28
SGAPanel
29
30
31
31
39
Spotlight Tools
42
42
Tools |SQLOptimizer
42
43
43
45
45
45
46
46
48
48
48
49
54
Table of Contents
55
Instance Panels
55
56
56
57
57
60
62
Product AuthorizationErrors
62
Connection Problems
63
63
63
64
64
Drilldown Problems
64
64
65
What Happens to The Operating System Drilldown when Connection Is Lost to The
Server?
65
Operating System Statistics Not Reported
65
66
66
67
67
67
68
68
Index
69
1
Welcome
Spotlight on Oracle is Quest Softwares powerful diagnostic and problem-resolution tool for
Oracle databases. Its unique user interface provides you with an intuitive, visual representation of
the activity on your database and operating system.
The numbered labels in the Oracle architecture diagram correspond to the following activities:
1. The client program (for example, SQL*PLUS, Oracle Power Objects, or some other tool)
sends a SELECT statement to the server process.
2. The server process looks in the shared pool for a matching SQL statement. If none is
found, the server process parses the SQL and inserts the SQL statement into the
shared pool.
3. The server process looks in the buffer cache for the data blocks required. If found, the
data block must be moved on to the most recently used end of the Least Recently
Used (LRU) list.
Welcome
4. If the block cannot be found in the buffer cache the server process must fetch it from the
disk file. This requires a disk I/O.
5. The server process returns the rows retrieved to the client process. This may involve some
network or communications delay.
6. When the client issues the UPDATE statement the process of parsing the SQL and
retrieving the rows to be updated must occur. The update statement then changes the
relevant blocks in shared memory and updates entries in the rollback segment buffers.
7. The update statement also makes an entry in the redo log buffer that records the
transaction details.
8. The database-writer background process copies modified blocks from the buffer cache to
the database files. The Oracle session performing the update does not have to wait for
this to occur.
9. When the COMMIT statement is issued the log writer process must copy the contents of
the redo log buffer to the redo log file. The COMMIT statement does not return control to
the Oracle session issuing the commit until this write is complete.
10. If running in ARCHIVELOG mode, the archiver process copies full redo logs to the
archive destination. A redo log is not eligible for re-use until it has been archived.
11. At regular intervals, or when a redo log switch occurs, Oracle performs a checkpoint. A
checkpoint requires all modified blocks in the buffer cache to be written to disk. A redo
log file cannot be re-used until the checkpoint completes.
Recommended Reading
The best information to help you tune and configure Oracle databases can be found online. Use
as your first point of reference web sites such as:
l
Home Page
The Spotlight home page is a visual representation of the status of the major components of the
database. The detail at this level is designed to help you locate and identify bottlenecks as they
develop. Additionally, Spotlight provides tools that allow you to identify and rectify
inefficiency in your databases configuration.
If Spotlight detects that some component of the Oracle database constitutes a performance
bottleneck, the corresponding component generates a visual or auditory alarm. The exact
appearance of the alarm depends on how you have configured alarm severities. When an alarm is
current you can press F1 to display help for the alarm. Clicking the component (on the home
page ) displays the relevant drilldown.
Welcome
See "Spotlight on Oracle Home Page" (page 26) for more information.
The home page display is based on the Oracle database architecture. See "Oracle Architecture
Overview" (page 7) for more information.
Alarms
Spotlight alarms indicate when the Oracle database exceeds acceptable performance thresholds.
See "Spotlight on Oracle Alarms" (page 31) for more information.
Drilldowns
Once a problem is isolated you can display a drilldown page with charts and tables that provide
a detailed breakdown of the underlying statistics.
For example, use the Activity drilldown to display overall efficiency and resource usage. In
particular, the Event waits chart shows the amount of time database sessions spend waiting for
various resources, as well as the amount of CPU being utilized. Efforts at tuning the database are
most likely to succeed when they concentrate on the resources being used most heavily and the
Wait activity topic contains a discussion of the meaning and implications of various wait events.
Other pages help you examine detailed activity. For instance, the Top Sessions drilldown
identifies the users who contribute most to database activity. You can display various details for
these sessions, including the SQL statements, locks and resource usage.
See "Spotlight on Oracle Drilldowns" (page 39) for more information.
10
Welcome
Features of Spotlight
Features Common to Spotlight Applications
Spotlight is designed for ease of installation and use, and offers a range of tools for problem
diagnosis. Features that are common to most Spotlight applications include:
l
Easy installation.
Context-sensitive help.
Calibration.
Common Spotlight technology. Spotlight on Oracle can run within the same Spotlight
console as several other Quest Spotlight products.
The ability to add new Spotlight on Oracle users, and to convert the accounts of existing
Oracle users so they can use Spotlight on Oracle.
Access to a number of other Quest applications for viewing detailed information on the
specified Oracle database.
Predictive Diagnostics
Predictive Diagnostics allows Spotlight to collect and analyze performance metrics for:
l
Database resources as they reach their full capacity and affect database throughput and
concurrency.
When enough performance data is collected, Spotlight may be able to predict the future
performance for individual SQL statements on that database, for potential bottlenecks in the
system, and for database CPU, memory, and disk I/O resources.
11
Welcome
Note: When you start using Predictive Diagnostics, Spotlight will take about 10 days to collect
enough data to make valid predictions on the future performance of the database.
Performing I/O operations on datafiles, redo logs, raw devices, and so on.
Capturing CPU or elapsed timing to support the time model and wait interfaces.
Spotlight uses DTrace to investigate these system calls to calculate where that elapsed time is
being spent.
Install and Configure DTrace scripts
Before you can capture the details of the interaction between Oracle and the Solaris operating
system, you need to Install And Configure DTrace Scripts (page 26).
2
Install Spotlight
Requirements
Windows 7 / Windows Vista / Windows Server 2008 :
Section
Requirement
User Privileges
Folder Permissions
ProgramData\Quest Software\Spotlight
Users\<current user>\AppData\Roaming\Quest
Software\Spotlight
HKEY_LOCAL_
MACHINE\SOFTWARE\Wow6432Node\Quest
Software\Products
HKEY_LOCAL_
MACHINE\SOFTWARE\Wow6432Node\Quest
Software\Spotlight
HKEY_CLASSES_ROOT
13
Install Spotlight
Requirement
User Privileges
Folder Permissions
HKEY_LOCAL_MACHINE\SOFTWARE\Quest
Software\Products
HKEY_LOCAL_MACHINE\SOFTWARE\Quest
Software\Spotlight
HKEY_CLASSES_ROOT
Steps To Install
To install Spotlight from CD:
1. Close all open applications on your PC.
2. Insert the Spotlight Installer CD into your CD-ROM drive.
If the installation program does not start select Windows Start | Run
l
For Spotlight delivered as part of the Toad DBA Suite, enter the command
d:\TOAD DBA Suite for Oracle vvv.exe (where d: is the CD-ROM identifier and
vvv is the Spotlight version).
14
Install Spotlight
To install Spotlight from the downloaded Quest Spotlight installer from the Quest Web site:
1. Close all open applications on your PC.
2. Execute the downloaded installer.
3. Follow the instructions on the screen to complete the installation.
Note:To cancel installation at any time, press Esc or click Cancel.
Uninstall Spotlight
To remove the application and all associated files from your machine, if required.
To uninstall Spotlight
1. Open Windows Control Panel.
2. Select Programs and Features. (On Windows XP select Add/Remove Programs.)
3. Click Spotlight on Oracle | Remove | Yes.
15
Start Spotlight
Start Spotlight
To start Spotlight:
or
On the Windows task bar, click Start | Programs |Quest Software | Spotlight |
Spotlight.
During operation
Spotlight requires write access to the following:
Windows Server 2008, Windows Server
2003, Windows Vista, Windows 7
Users\<current user>\AppData\Roaming\Quest
Software\Shared
Users\<current user>\AppData\Roaming\Quest
Software\Spotlight
Windows XP
You should also verify that you can run the required Oracle client on the Spotlight machine.
Project Lucy
The first time you run Spotlight following install you will be prompted to upload data to Project
Lucy. Project Lucy is a free service provided by Quest Software that analyzes your performance
data, gives you reports and insight into your performance and allows you to compare your
experience to everyone else that uses the service. Performance data is uploaded to Project Lucy
once a day.
Actions
To open the Project Lucy home page, in the Spotlight
Browser click Welcome to Spotlight | Spotlight on the
Web | Project Lucy.
Description
l
16
Start Spotlight
Actions
Description
l
Authorize Spotlight
Spotlight on Oracle is supplied with a time-limited trial key so you may test the product. When
the trial key expires Spotlight on Oracle reverts to a preview mode, which limits access to the
Spotlight on Oracle home page and one connection at a time. If you select to open a drilldown
in preview mode the following message is displayed:
You do not have a license for Spotlight on Oracle that enables
access to this functionality. Please contact Quest Software for
information about obtaining the correct license.
Contact your Quest Software representative to obtain the necessary authorization keys to ensure
Spotlight remains fully functional when the trial key expires.
To enter a new authorization key:
While Spotlight is running
1. Click Help | About Spotlight.
2. Ensure Installed Products is to the front.
3. Locate any Spotlight on Oracle in the list of installed products.
4. Select View / change product license.
5. Click Change this license.
6. Enter the Authorization key.
Notes:
l
The Windows user that updates the authorization key must have administrator access to
the Windows registry and write access to the Console\Licenses sub-folder of the
Spotlight installation folder.
Make sure you enter the authorization key exactly as stated on your Product
Authorization sheet or as provided by your Quest Software distributor. The site message
17
Start Spotlight
is case sensitive. If you enter the authorization key incorrectly, the following message is
displayed: Invalid authorization key
l
If Spotlight is in preview mode and the trial period has not expired, check your computer
system date is set correctly.
Spotlight Users
Spotlight on Oracle connects to the Oracle database through the Spotlight user.
l
You should not use any system accounts. We recommend creating a separate user for
Spotlight or using a personal account.
The Spotlight user must have sufficient privileges, views, and tables to diagnose the
Oracle database. You can view the privileges, views and tables required by Spotlight
users in the Database Objects and Privileges document in the Spotlight installation
folder: \Plug-ins\SoO\.
Convert the account of an existing user on the Oracle database to use Spotlight
Notes:
l
Spotlight users must be configured for each database they are to diagnose.
You cannot configure Spotlight users for a database while Spotlight is diagnosing
that database.
You must have the user ID and password of the DBA that manages the database to which
you are adding the Spotlight user.
Select Don't show this page in future to hide the first page of the Oracle User Wizard.
18
Start Spotlight
Field
Description
Enter the
SQL*Net
connection
string
Enter the database instance on which you wish to create the user.
Enter a DBA user name for that database instance (so that the
Spotlight user and the relevant objects can be created). The user
name requires SYSDBA access.
Enter the
password
Description
User name
Password
Confirm password
Alter system
Description
Spotlight tables
temporary segments
19
Start Spotlight
9. Select the settings Spotlight will use to schedule the Oracle jobs that collect data on SQL
performance and impending bottlenecks.
3
Spotlight on Oracle
Connect to Oracle Databases
1. From the Spotlight Browser select All Connections |Spotlight on Oracle
2. Select the database. If the database is not on the list then add a new connection.
Notes: (Now the database is listed in the Spotlight Browser |Live connections.)
l
Click Set timed statistics now if you are prompted to do so. You see this prompt
when for the Spotlight user the timed_statistics parameter is set to false in the
init.ora file. Spotlight requires this parameter be true for the Spotlight user to
accurately monitor the database. Clicking Set timed statistics now corrects the
problem only if the Spotlight user has Alter System privileges. Ensure the
Spotlight user has sufficient privileges. See "Spotlight Users" (page 17) for more
information.
Spotlight operates at reduced functionality once the initial trial period has expired.
See "Authorize Spotlight" (page 16) for more information.
Ensure you create a Spotlight user with sufficient privileges to diagnose the Oracle
database. See "Spotlight Users" (page 17) for more information.
Ensure the Unix or Windows server on which the Oracle database is installed is
accessible to Spotlight on Oracle. See the Spotlight on Unix or Spotlight on Windows
Getting Started Guide.
21
Spotlight on Oracle
Description
Connection
String
Select the name of the database that you wish to connect to.
Oracle
Username
Enter the Spotlight user name. See "Spotlight Users" (page 17) for
more information.
Note: When selected, the Connection name field resets to this value.
You can then edit the Connection name field if required.
Tip: If you enter a Username that does not exist, Spotlight will
prompt you when you complete this dialog to create a new Spotlight
user.
Oracle
Password
Enter the Spotlight user password. See "Spotlight Users" (page 17) for
more information.
Oracle
Home
22
Spotlight on Oracle
Field
Description
Monitor
ASM
ASM
Connection
String
ASM
Password
Enter the user password for Spotlight to login to the ASM database
instance.
Note:The TNSNAMES entry for the ASM instance must include the
option (UR = A) for the Spotlight connection to work properly.
The user that Spotlight uses to login to the ASM database is SYS.
This is the only user name that can provide access to ASM-specific
information.
Providing SYS access to an ASM instance does NOT create a security
issue for the Oracle database, but you should limit access to the SYS
account to trusted individuals.
Because the SYS password is stored in encrypted format, nonprivileged users can still access Spotlight on Oracle. To do so:
l
Description
Monitor OS
OS Server
23
Spotlight on Oracle
Field
Description
OS Type
Windows
Unix(REXEC)
Unix(SSH)
If you select one of the Unix systems, make sure the SSH or REXEC
daemon is running on the database server and is configured to
receive remote connections. Spotlight supports both SSH1 and SSH2
protocols. Public-key encryption is supported under SSH2 only.
SSH Port
Enter the port number for SSH (secure shell) connection to the
database server. The default value is 22.
Note: Applicable when OSType is Unix(SSH) or Unix(SSH using
Public/Private Keys).
OS
Username
SSH Key
Type
SSH Private
Key
Filename
Locate the filename that contains the private key for the Spotlight
connection.
SSH
Passphrase
OS
Password
Type the user password to login to the database server (if required).
Connect to
OS
Spotlight
24
Spotlight on Oracle
Field
Description
when
starting this
connection
ESX connection details
Note: Requires Server connection details | Monitor OS selected.
Field
Description
Monitor
ESX
ESX
Web
Service
Type or select the URL of the ESX Web Service that manages the
virtual machine.
ESX
Username
ESX
Password
Type the password required to connect the specified user to the ESX
Web Service.
Virtual
Machine
Name
Note: The username specified must have read only permissions for both
the ESX virtual machine and the ESX host that the virtual machine
resides on, or may reside on.
Stealth Collect
StealthCollect is Quest technology designed to collect SQL statements and performance
indicators from Oracle databases and host operating systems without imposing overheads
on the target database itself.
Note: Requires StealthCollect installed. StealthCollect is installed with Performance
Analysis.
Field
Description
Use
StealthCollect
SC Port No.
25
Spotlight on Oracle
Field
Description
and password. (The default StealthCollect username and password
is quest.)
SC Oracle
SID
5. Click Test to verify Spotlight can connect successfully with the details provided.
Note:For connections to virtual machines, testing the connection validates that Spotlight
can connect to the Web Service using the specified username and password combination,
and that the virtual machine exists. It does not check permissions, that the virtual machine
is turned on, or that it is the same machine as the one specified in the Server Connection
Details section.
6. Click Save password details (for this connection) to save all the entered
password details.
The Oracle database and username fields are pre filled in as per the Toad connection.
Security requires that you re-enter your Oracle password.
The default connection name is Toad followed by the name of the Oracle database. You
may choose to replace this with any connection name of your choice. Note that a
limitation of the integration of Toad with Spotlight on Oracle is that this is a new
Spotlight connection, ignoring all other pre-existing Spotlight connections.
You may choose a different Oracle username to connect to Spotlight. For example, in an
environment with multiple database administrators there may be a communal username for
Spotlight connections. Simply replace the filled in Oracle username with the appropriate
Oracle username and password details.
You can enter additional parameters to monitor ASM, the operating system and for
virtualization.
26
Spotlight on Oracle
Spotlight opens at the Home Page or Drilldown relevant to the location in Toad from
where Spotlight was opened.
You are prompted to create a new Spotlight user if the Oracle username has not been
created in Spotlight. See "Spotlight Users" (page 17) for more information.
This Spotlight connection can be found in the Spotlight Connection Manager. It can be
managed the same as any other Spotlight connection. For example, you can close the
connection, edit the connection details and re-open the connection in the Spotlight
Connection Manager.
Caution:When you click on the Spotlight button in Toad to connect to the Oracle database,
a new Spotlight connection to the Oracle database is created, regardless of any pre-existing
Spotlight connections to the Oracle database. To avoid the annoyance of setting up Spotlight
connections in Spotlight that will be set up identically through Toad later, you may choose
to create all connections through Toad if Toad integration is desired.
27
Spotlight on Oracle
Related operating system statistics are grouped together on panels that are connected by a series
of graphical flows and icons. Spotlight updates these flows in real time so you can see how
quickly data is moving through the system. The icons change color as Spotlight alarms are
raised, upgraded, downgraded and canceled.
The panels on the Spotlight on Oracle home page are described in more detail next. For a full
discussion of the panels, see the Spotlight online help.
Tip: Hover the mouse pointer over a panel component for more information.
Sessions Panel
The Sessions panel indicates the status of the Oracle communications
between client and server. Information displayed here includes:
l
The time (in milliseconds) that it takes for the query select user from
dual to be submitted, executed and returned.
Note: The Average Active Sessions gauge is not available for Oracle 9i.
The flows between the Sessions panel and the Server Processes panel represent the rate of data
transfer in both directions across the SQL*NET interface.
28
Spotlight on Oracle
Host Panel
The Host panel shows metrics for the operating system:
l
The amount of memory that has been reclaimed from the virtual
machine by ESX (if applicable).
The flow to the Server Processes panel from the Disk Storage panel represents the rate of direct
physical reads from disk.
The flows between the Server Processes panel and the SGA panel represent the rates of:
29
Spotlight on Oracle
SGAPanel
The SGA panel shows details of specific memory areas within the system
global area (SGA). The SGA is an area of shared or common process memory
that is used to cache frequently used data, SQL statements, procedures and
other structures:
l
The size of the buffer cache and its components. These hold data that
is accessed frequently.
The size of the Java Pool, which caches class definitions, Java
methods and Java objects.
The size of the Large Pool allocation heap, which is used in MTS for
session memory. It can be used by parallel execution and backup
processes.
The size of the redo buffer. This contains redo entries that are
eventually written to the redo log.
The size of the Shared Pool, which caches SQL statements, PL/SQL
programs, object definitions and session memory for MTS sessions.
The size and activity of the result cache (Oracle 11g or later).
The flow between the SGA panel and the Disk Storage panel represents the rate of block
reads from disk.
The flows between the SGA panel and the Background Processes panel represent the rates of:
l
Redo log block writes by the Redo Log Writer (LGWR) process.
30
Spotlight on Oracle
Predictive Diagnostics.
Note: The n value in each process icon indicates the number of processes
there are of that type.
The flows between the Background Processes panel and the Disk Storage
panel represent:
l
The rate at which modified blocks are written from the SGA to disk
by the DBWR processes.
The rate of I/O write operations to the flash recovery area by the
RVWR processes.
The rate at which redo log entries are written to the redo log files by
the LGWR processes.
The rate at which the archiver copies from redo log files to archived
logs.
31
Spotlight on Oracle
Right-click the Disk Storage icon to open Space Manager. See "Tools
|Space Manager" (page 43) for more information.
View details of the statistics that caused the alarm in a Spotlight drilldown page. See
"Spotlight on Oracle Drilldowns" (page 39) for more information.
32
Spotlight on Oracle
Following are the alarms specific to Spotlight on Oracle. For possible solutions to the problems
indicated by these alarms or for information on how to diagnose problems further, see Spotlight
on Oracle alarms in the online help.
Alarm
Description
Agent Status
alarm
Spotlight raises the Agent Status alarm when the status of the EM agent is
down.
OEM is a Web-based database administration and monitoring tool that
manages Oracle components and administers Oracle databases. When
installed and active, OEM communicates with the databases it administers
via a set of EM agent processes under the automated DBSNMP user
account.
Archive
Critical
Failure alarm
Archive
Destination
Failed alarm
Archive
Destination
Failure alarm
Array Fetch
Size alarm
When more than one row is retrieved from an Oracle database in a single
SELECT (an array fetch), the amount of network traffic associated with
SELECT operations is radically reduced. The Array Fetch Size alarm is
raised when the array fetch size for the database may be too low.
ASM Balance
alarm
This alarm indicates that there is unbalanced access to one or more of the
disks in the ASM (Automatic Storage Management) disk group that has
been allocated to the Oracle instance.
ASM Service
Time alarm
This alarm indicates that the average time taken to perform I/O on the
ASM instance has exceeded a specified threshold value. (Service time
represents the response time of a disk plus any wait time experienced
during disk operations.)
ASM Status
alarm
When a Spotlight connection is lost, Spotlight automatically tries to reestablish the connection. The ASM Status alarm indicates that Spotlight is
33
Spotlight on Oracle
Alarm
Description
re-establishing its connection to the ASM diskgroup for the Oracle
instance.
Average
Time to Sync
a Redo Log
Entry alarm
The Average Time to Sync a Redo Log Entry alarm (formerly the Average
Redo Write Time alarm) is activated when the time taken to write redo log
entries exceeds a threshold. Unlike most other Oracle write I/Os, Oracle
sessions must wait for redo log writes to complete before they can
continue processing.
Buffer Busy
Wait alarm
The Buffer Busy Wait alarm occurs when a session cannot access a block
because it is in use by another session. The two most common causes are
insufficient free lists for a table or insufficient rollback segments.
Cache Buffer
Chains Latch
Wait alarm
The Cache Buffer Chains Latch Wait alarm occurs because contention for
the cache buffer chains latch exceeds a threshold.
Cache Buffer
LRU Chains
Latch Wait
alarm
The Cache Buffer LRU Chains Latch Wait alarm occurs because
contention for the cache buffer chains latch exceeds a threshold.
Collection
Status alarm
Spotlight raises the Collection Status alarm when collection of data for the
OEM (Oracle Enterprise Manager) stops. Perhaps the server is running low
on disk space.
The Collection Status alarm often occurs with the Files Pending Upload
Alarm.
Continued
Fetch Rate
alarm
CPU Busy
alarm
The CPU Busy alarm occurs when the total CPU utilization of the system
exceeds a threshold.
CPU
Virtualization
Overhead
alarm
Datafile Read
Time alarm
The Datafile Read Time alarm occurs if the average time for a random
datafile read exceeds a given threshold.
Data Guard
Configuration
34
Spotlight on Oracle
Alarm
Description
Alarm
Dispatchers
Busy alarm
The Dispatchers Busy alarm occurs when all or most dispatcher processes
are busy. In an MTS environment, multiple sessions share a smaller number
of shared server processes. The servers are usually allocated by a smaller
number of dispatcher processes.
Estimated
Shared Pool
Size alarm
This alarm occurs when the Shared Pool is set too small. A possible cause
is the use of literals rather than bind variables in SQL statements. You can
also increase the size of the Shared Pool.
Excessive
RBS
Activities
alarm
The Excessive RBS Activities alarm occurs when there are high rollback
extent/shrink/wrap activities.
Files Pending
Upload alarm
Spotlight raises the Files Pending Upload alarm when a significant number
of XML files are pending upload indicating a problem with the upload
process. The strategy for dealing with this alarm is dependent on the OEM
control. The OEMcontrol is defined in the Spotlight configuration for
OEM.
This alarm may occur in conjunction with the Collection Status Alarm.
Flash Cache
Insert Skip:
DBWR
Overloaded
alarm
The Flash Cache Insert Skip: DBWR Overloaded alarm is raised when the
ratio of insert skips from the DBWR being overloaded exceeds a threshold.
Flash Cache
Read Latency
The Flash Cache Read Latency alarm is raised when the time taken to read
a single block from flash cache exceeds a threshold. This may be caused
by a low performance flash device.
Flash Cache
Write
Complete
Waits
The Flash Cache Write Complete Waits alarm is raised when the ratio of
'write complete waits: flash cache' to DB time exceeds a threshold.
Flashback
Buffer Wait
alarm
The Flashback Buffer Wait alarm indicates that the percentage of available
time spent waiting for the Recovery Writer (RVWR) to write data to the
flashback logs has exceeded a specified threshold.
Flashback
Space Usage
This alarm is raised when the amount of used space in the Flashback
Recovery Area exceeds a threshold.
35
Spotlight on Oracle
Alarm
Description
alarm
Free Buffer
Waits alarm
The Free Buffer Waits alarm occurs when free buffer waits (as a proportion
of total waits) exceeds a threshold.
In Memory
Undo Latch
Wait alarm
Instance
Failed alarm
Insufficient
Flashback
Logs alarm
This alarm fires when the flashback logs in the flashback area do not cover
the amount of time specified in the parameter DB_FLASHBACK_
RETENTION_TARGET.
Job Processes
Busy alarm
The Job Processes Busy alarm occurs when all or most job queue processes
are busy.
Large Pool
Full alarm
This alarm fires when the Large Pool allocation heap is full. The Large
Pool is used in MTS for session memory, and can be used by parallel
execution and backup processes.
Latch Free
Waits alarm
Library
Cache
Latches
alarms
These alarm fire when the time spent waiting on library cache latches or
library cache pin latches exceeds a threshold. Library cache latches (or
mutexes in 10g R2 and above) protect the cached SQL statements and
object definitions held in the library cache within the Shared Pool.
Library
Cache Miss
Rate alarm
The Library Cache Miss Rate alarm occurs when the library cache hit ratio
falls below a given threshold.
Lock Wait
alarm
The Lock Wait alarm occurs when the proportion of time sessions spend
waiting for locks exceeds a threshold.
Log Buffer
Space Wait
alarm
The Log Buffer Space Wait alarm occurs if the amount of time spent
waiting for space in the redo log buffer exceeds a threshold.
Log Switch
Time alarm
The Log Switch Time alarm occurs when the amount of time spent waiting
for log switch events exceeds a threshold.
Low Free
The Low Free Physical RAM alarm occurs when the servers available
36
Spotlight on Oracle
Alarm
Description
Physical
RAM alarm
RAM is low.
Maximum
Queued Time
alarm
The Maximum Queued Time alarm becomes active when a session has
been in the parallel execution queue for longer than the specified
threshold.
Note: Applies only to Oracle 11gR2.
Multithreaded
Server alarm
Nonreclaimable
Flashback
Space alarm
This alarm is raised when the amount of non-reclaimable used space in the
Recovery Area (flashback area) exceeds a threshold. Non-reclaimable files
include archived redo logs, which must be backed up before being deleted.
Oracle
Memory on
Disk alarm
The Oracle Memory on Disk alarm is activated when the amount of guest
physical memory mapped to machine memory is less than the current
combined size of Oracle's SGA and PGA.
Oracle
Parameters for
Predictive
Diagnostics
alarm
Oracle Status
alarm
When a Spotlight connection is lost, Spotlight automatically tries to reestablish the connection. The Oracle Status alarm indicates that Spotlight
is re-establishing its connection to the Oracle instance.
Parallel
Query Server
alarms
The Parallel Query Server alarm occurs when all or most parallel servers
are busy. Parallel server processes perform work to resolve SQL statements
that are being executed in parallel. If all parallel server processes are busy,
parallel SQL may be downgraded, or even executed serially, thus
increasing its execution time. Spotlight can raise these Parallel Query
Server alarms: Parallel Query Servers Busy, Parallel Queries Downgraded,
and Parallel Queries Serialized.
Parse Ratio
alarm
The Parse Ratio alarm is raised when the ratio of parse calls to execute
calls exceeds a threshold.
Note This alarm is initially disabled; see Total Parse Wait Time Ratio
alarm.
37
Spotlight on Oracle
Alarm
Description
Predictive
Diagnostics
alarms
Predictive
Diagnostics
Custom SQL
Error alarm
This alarm indicates that the customized SQL query use to represent
database concurrency within Predictive Diagnostics has returned an error.
Redo
Allocation
and Redo
Copy Latch
Wait alarms
The Redo Allocation and Redo Copy Latch Wait alarms are raised when
there is contention for the redo allocation latch and redo copy latch.
Result Cache
Find/Create
Ratio alarm
When Oracle executes SQL queries, the result cache stores the result sets
of specified queries in shared memory for later use. The Find/Create Ratio
alarm occurs when the rate of find operations on the result cache drops
below the rate of create operations, and indicates that the contents of the
result cache are under-used.
Result Cache
Latch Sleep
Ratio alarm
Spotlight raises the Result Cache Latch Sleep Ratio alarm when the rate of
latch sleeps for the Result Cache latch indicates that there is contention on
the Result Cache latch, where multiple processes are competing to use the
latch and are causing a significant degradation in response time.
Row Cache
objects Latch
Wait
The row cache objects latch protects the contents of the row cache; the
section of the shared pool to cache dictionary information.
Sequential
Read Time
alarm
This alarm fires when the average time that Oracle takes to read a single
block of data typically an index-based lookup is significantly higher
than the average time recorded during calibration.
Sessions
Queued alarm
The Sessions Queued alarm becomes active when the number of sessions
in the parallel execution queue exceeds a threshold.
Note Applies only to Oracle 11gR2.
Shared Pool
Latch Wait
alarm
Shared pool latches control access to the shared pool memory map.
Shared Pool
Lock
Percentage
alarm
This alarm is raised when one user session holds a lock on object(s) in the
Shared Pool for a prolonged period, and causes other sessions to wait on
the same resource. This "blocking lock" happens rarely. When it does
occur, use a SQL query to find the affected sessions.
38
Spotlight on Oracle
Alarm
Description
Shared Server
Converted
into
Dedicated
Server alarm
Spotlight raises an alarm when many shared servers are converted, leaving
too few shared servers to meet the demand. Converted shared servers will
have a status of WAIT(RECEIVE) in v$shared_server.
Status Error
alarm
This alarm is raised when there is a problem with the way the OEM
configuration has been defined in Spotlight. Correct the values entered in
the dialog View | Options | OEM Monitoring.
Temporary IO
Wait Ratio
alarm
Spotlight raises the Temporary IO Wait Ratio alarm when the time spent in
temporary IO waits is too high as a percentage of the time spent
performing user calls on the Oracle database.
Total Parse
Wait Time
Ratio alarm
Spotlight raises this alarm when the amount of time spent parsing SQL
statements as a percentage of the active database time exceeds a level that
may cause latch contention on the shared pool and library cache latches.
Note: The Total Parse Wait Time Ratio alarm is available for Oracle 10.2
and later. When monitoring earlier Oracle systems, consider reactivating
the (disabled) Parse Ratio alarm.
Unarchived
Logs alarm
The Unarchived Logs alarm occurs when the number of unarchived redo
logs exceeds a threshold. If all online logs need archiving, database update
activity can be suspended while the redo log writer waits for the next log
to be archived.
Unix Status
alarm
WMI Status
alarm
Write
Complete
Wait alarm
Spotlight raises the a Write Complete Wait alarm when write complete
waits (as a proportion of total waits) exceed a threshold. Write complete
waits occur when a session tries to modify a block that is currently being
written to disk by the database writer process.
Note: Spotlight on Oracle Data Guard alarms occur in the Alarm Log of the Primary Database
in the Oracle Data Guard environment. See Spotlight on Oracle Data Guard Alarms in the online
help for more information.
39
Spotlight on Oracle
Top Sessions
SQL&Application
Workload
Click
to
open
Description
40
Spotlight on Oracle
Drilldown
Click
to
open
Description
Activity
I/O
Configuration &
Memory
Operating System
Disk Storage
Tuning
ASM
41
Spotlight on Oracle
Drilldown
Analyze Trace
Click
to
open
Description
Predictive
Diagnostics (if
enabled)
Data Guard
42
Spotlight on Oracle
Drilldown
Click
to
open
Description
environment.
Reports
Alarm Log
Spotlight Tools
Tools |Explain Plan
Tools |Explain Plan allows you to determine the execution plan that Oracle applies to a
particular SQL statement. Spotlight on Oracle allows you to view graphical representations of
the execution plan for SQL statements being executed by a user, or for those identified by the
Top SQL Page.
To open the Explain Plan
1. Open a connection to an Oracle Database.
See "Connect to Oracle Databases" (page 20) for more information.
2. Click Tools |Explain Plan.
Tools |SQLOptimizer
SQL Optimizer provides context-sensitive tuning advice for SQL statements based on the Oracle
execution plan and the database structure.
Before you open SQL Optimizer
l
Ensure you have DBA privileges for the database you are diagnosing.
To open SQLOptimizer
1. Open a connection to an Oracle Database.
See "Connect to Oracle Databases" (page 20) for more information.
43
Spotlight on Oracle
Ensure you have DBA privileges for the database you are diagnosing.
Use the Spotlight home page to alert you to any obvious bottlenecks. If Spotlight detects
that some component of Oracle constitutes a performance bottleneck, the corresponding
component generates a visual or auditory alarm. The exact appearance of the alarm
depends on how you have configured alarm severities. When an alarm is current you can
press F1 to display help for the alarm. Clicking the object (in the main window) displays
the relevant drilldown.
See "Spotlight on Oracle Home Page" (page 26) for more information.
Use the Activity drilldown to display overall efficiency and resource usage. In particular,
the Event waits chart shows the amount of time database sessions are spending waiting
for various resources, as well as the amount of CPU being utilized. Tuning efforts are
most likely to succeed if they are concentrated on the resources being used most heavily.
The Wait activity topic contains a discussion of the meaning and implications of various
44
Spotlight on Oracle
wait events.
See "Spotlight on Oracle Drilldowns" (page 39) for more information.
l
Other pages help you examine detailed activity. For instance, the Top Sessions drilldown
shows the users who contribute most to database activity. You can display various details
for these sessions, including the SQL statements, locks and resource usage.
For further information on tuning your database, see the online help.
45
Identify SQL statements whose performance may not scale adequately as data volumes
and SQL execution rates increase.
Identify bottlenecks that may affect database throughput and response time.
Predict when database resources such as CPU, memory and disk I/O are expected to reach
their full capacity, and recommend strategies to enable the database to handle high loads.
Note: It takes about 10 days for Spotlight to collect enough data to make valid predictions on
the future performance of the database.
Set parameters for the CPU, memory and disk I/O resources
available to the database.
46
Predict when and why database resources will run out, what
will cause performance to suffer, and what you need to do to
counter those problems.
Do this...
Predictive Diagnostics
identifies a SQL statement that
may cause problems
Predictive Diagnostics
identifies a bottleneck that may
cause problems
Predictive Diagnostics
identifies a database resource
whose limitations may cause
problems
Requirement
Sample data
SQL
statements
47
Situation
Requirement
SQL statement.
The number of snapshots collected depends on the application workload and
size of the shared pool, the collection interval for snapshots, and the length
of time each snapshot is retained.
Example
If there are 500 eligible SQL statements per snapshot, and snapshots are
collected twice a day, and each snapshot is kept for one year, the disk
storage requirement for SQL statements is:
10MB + (500 x .001MB x 2 x 365) = 375 MB
Impending
bottlenecks
Performance
modeling
Note: Parameters set in View | Options | Predictive Diagnostics and the SQL Statement Trend
Analysis wizard affect the storage requirements for Predictive Diagnostics data. See the online
help more for more information.
48
49
A user should find an Oracle RAC database operationally identical to a database hosted on a
single server. From top to bottom, the important features represented are:
l
Multiple nodes/instances - Oracle instances run on the nodes (host machines) in the
Oracle RAC cluster. Each instance comprises an Oracle System Global Area (SGA)
plus the corresponding Oracle background processes that retain and process Oracle
database requests.
Shared disk subsystem - Database files in Oracle RAC systems are stored on multiple
disks that are shared by all the nodes in the cluster, and all nodes must be able read and
write to those disks.
50
(page 50).
Display this dialog for the current connection is selected in the connection
properties or Verification window, OR
You can use the Connection Details Verification window to view the available
connection data and provide or modify any data (port number, for example) that is
missing or faulty. Refer to the online help for more information.
Add a new connection
1. Ensure you create a Spotlight user with sufficient privileges to diagnose the Oracle RAC.
See "Spotlight Users" in the online help for more information.
2. Click File |Connect
Description
Connection
String
Select the name (the SQL*Net alias) of the Oracle RAC database that
you wish to connect to.
51
Field
Description
Notes:
l
While this can be the name of any instance in the Oracle RAC
cluster, we recommend using the name of the load-balanced
instance the instance whose TNSNAMES entry includes the
option (LOAD_BALANCE = yes)
Oracle
Username
Oracle
Password
Oracle
Home
Description
Monitor
ASM
ASM
Connection
String
52
Field
Description
option (UR = A) for the Spotlight connection to work properly.
ASM
Password
Description
Monitor
OS
OS Server
Windows
Unix(REXEC)
Unix(SSH)
If you select one of the Unix systems, make sure the SSH or REXEC
daemon is running on the database server and is configured to receive
remote connections.
Note:Spotlight supports both SSH1 and SSH2 protocols; public-key
encryption is supported under SSH2 only.
53
Field
Description
SSH Port
Enter the port number for SSH (secure shell) connection to the
database servercluster. The default value is 22.
Note: Applicable when OSType is Unix (SSH) or Unix(SSH using
Public/Private Keys).
OS
Username
SSH Key
Type
SSH
Private
Key
Filename
Locate the filename that contains the private key for the Spotlight
connection.
SSH
Passphrase
OS
Password
54
Oracle RAC database whenever you open the Spotlight on Oracle RAC connection. In
most cases, this should not be necessary.
7. Select Display Connection Details Verification Dialog to display the Connection
Details Verification dialog when you connect to a specified Oracle RAC cluster. The
dialog allows you to specify and test connections to ALL instances in the cluster.
8. Select Save password details to save all the password details that have been entered.
55
This panel shows a combination of Interconnect and Global Cache Service information, and
information about the Oracle RAC database overall. It consists of information aggregated from
queries sent out to the individual instances. This provides information on how well data is being
shared and transferred between nodes in the cluster.
Some information displayed here is easily calculated: for example, the Total Logical Reads
spinner is the sum of the individual Logical Reads values. Other components, such as Cluster
Latency and Cluster Overhead, have a more complex calculation.
Spotlight uses the Global Database label to indicate alarms in one or more Oracle instances that
may affect the performance of the Oracle RAC database as a whole.
The flows between the Interconnect panel and the Instances panel represent the flow of data
from one instance to another across the interconnect.
Instance Panels
This panels show the participating instances of a cluster. Together with separate panels for all
participating instances, this panel provides information on the performance of individual
instances in the cluster.
56
This panel shows information relating to the shared storage subsystem for the Oracle
RAC cluster.
Some of this information is aggregated from queries sent to the individual instances; other
information is obtained from a single query to one of the instances.
The ASM spinner is populated only when ASM (Automatic Storage Management) is being used.
See "Connect to Spotlight on Oracle RAC" (page 49) for more information.
The flows between the I/O Subsystem panel and the individual instances represent the flow of
physical reads and writes between the instances and the physical database.
57
View details of the statistics that caused the alarm in a Spotlight drilldown page. See
"Spotlight on Oracle RAC Drilldowns" (page 60) for more information.
Aggregated alarms within Spotlight on Oracle RAC are the same as the corresponding
alarms in Spotlight on Oracle.
Not all Spotlight on Oracle alarms are aggregated in Spotlight on Oracle RAC.
Description
Archive
Critical
Failure alarm
58
Alarm
Description
by purging or by backing up to an offline medium any archived files
that are not immediately needed.
Archive
Destination
Failed alarm
Archive
Destination
Failure alarm
ASM Status
alarm
When a Spotlight connection is lost, Spotlight automatically tries to reestablish the connection. The ASM Status alarm indicates that Spotlight is
re-establishing its connection to the ASM diskgroup for the Oracle RAC
cluster.
Availability
alarm
This alarm indicates that the instances participating in the cluster are NOT
all currently available for access. The database administrator should
determine why the instances are unavailable, and restart them after taking
the required actions.
(Global)
Cache Miss
Rate alarm
Cluster
Latency
alarm
Spotlight raises the Cluster Latency alarm when cluster latency from all
causes (interconnect, GES, LMS overhead) exceeds a specified threshold.
Cluster latency is defined as the average elapsed time from when a
requesting instance requests a block of data to the time when the
requesting instance receives the block.
Cluster
Overhead
alarm
Spotlight raises the Cluster Overhead alarm when the percentage of time
dedicated to cluster co-ordination activities exceeds a specified threshold.
Cluster overhead is the amount of time spent waiting for cluster related
activities as a percentage of the total time spent waiting for all activities.
Corrupt or
Lost Blocks
alarms
Spotlight raises separate alarms for corrupt and lost blocks when a
specified percentage of the blocks transferred across the interconnect are
corrupted or lost during global cache consistent read requests.
High levels of lost or corrupt blocks should not happen in normal
circumstances. If these alarms fire at all, it indicates either very serious
overloading of the Oracle RAC cluster, or software or hardware faults in
the cluster.
Data Guard
Configuration
59
Alarm
Description
Alarm
Instance
Failed alarm
Load
Imbalance
alarm
This alarm, more specifically known as the Cache Miss Rate alarm or
Global Cache Miss Rate alarm, is raised when the global cache local miss
rate exceeds a specified threshold. This rate is the percentage of time that
a block required for a logical read is located in an inconsistent mode on
ANOTHER instance in the cluster and must be transferred.
No Nodes
Available
alarm
This alarm indicates that Spotlight has lost its connection to the Oracle
RAC cluster, and cannot re-connect to any of the nodes in the cluster.
Check the status of your network connection, your host machines, and
your database instances.
60
Note: Spotlight on Oracle Data Guard alarms occur in the Alarm Log of the Primary Database
in the Oracle Data Guard environment. See Spotlight on Oracle Data Guard Alarms in the online
help for more information.
Click
to
open
Description
Top Sessions
SQL&Application
Workload
Activity
Result Cache
Lock Activity
Server
Rollback
I/O
Configuration &
Memory
Disk Storage
Buffer Cache
Online Redo
Recovery Area
61
Drilldown
Click
to
open
Description
Cluster
ASM
Services
Predictive
Diagnostics (if
enabled)
Data Guard
Alarm Log
4
Troubleshooting Spotlight on Oracle
This section identifies general problems that you may encounter when using Spotlight on Oracle,
and details how to address those problems. If you do not find a solution in this section then
check the Spotlight on Oracle Release Notes.
Product AuthorizationErrors
When first installed, Spotlight can be used with full functionality for a specified trial period.
When the trial period expires, contact your Quest Software representative to obtain an
authorization key to continue. See "Authorize Spotlight" (page 16) for more information.
Notes:
l
Make sure that you enter the authorization key and site message exactly as stated on your
Product Authorization sheet or as provided by your Quest Software distributor. The site
message is case sensitive. If you enter the authorization key incorrectly, the following
message is displayed:
Invalid authorization key
Once the trial period has expired, if an authorization key is not supplied, only the
Spotlight on Oracle home page will be visible. If you click any of the drilldown buttons,
the following message is displayed:
You do not have a license for Spotlight on Oracle that enables access
to this functionality. Please contact Quest Software for information
about obtaining the correct license.
If the trial date has not passed, check that the date on your system is set correctly.
63
Connection Problems
Cannot Connect to Database
Possible cause
Solution
This means that Spotlight cannot access the operating statistics of the (Windows) database
machine. Users must have access to the registry so that Spotlight can retrieve the operating
system statistics. A user account with administrative rights to the target machine will allow this.
64
Drilldown Problems
Alarm Help Displayed Instead of Drilldown
Spotlight can be configured to show the help or jump directly to the related drilldown on
clicking a home-page control.
65
2. Select Reset
3. Select the appropriate frequency.
66
Use the Overhead Management slider to adjust the overall Spotlight load.
View the Global Support Guide for a detailed explanation of support programs, online services,
contact information, policies and procedures. The guide is available at: www.quest.com/support.
This file contains a snapshot of your Spotlight installation. Send this file and your request for
assistance to Quest Software (support@quest.com).
Notes:
l
Support bundles contain information for the active instance only. If you are using
Spotlight to diagnose multiple instances ensure that the correct instance is displayed
before creating the support bundle.
Support bundles cannot be created when the History Browser is open. For further
information on the History Browser, see the Spotlight online help under Concepts
and Features.
68
info@quest.com
Mail:
Web site:
www.quest.com
Refer to our Web site for regional and international office information.
drilldowns
Index
Spotlight on Windows
activity drilldown
9, 40
aggregated alarms
57
43
DSA
31, 42, 57
alarms
9, 31, 56
analyze trace
39
49
array fetch
39
21, 32, 40, 51, 56, 58, 64
23
DTrace
11, 26, 41
E
ESX
24, 28
event waits
explain plan
46
F
ASM
9, 39, 60, 64
fast initialize
63
H
home page
8, 26
ASM drilldown
no data
52
authorize Spotlight
host panel
B
background processes panel flows
29-30
C
configuration and memory drilldown
40,
46
28
I
16
I/O drilldown
40, 46
56
install
12
instance panels
55
55
55
55
20
49
contact support
67
Oracle architecture
7-8
28
48
40
31
28-30
40
54
17, 66
70
Index
P
parse activity
39
permissions
predictive diagnostics
SQL optimizer
42, 46
SSH
23, 52
12-13, 15-16
start Spotlight
15
StealthCollect
24
T
open
45
Toad DBA Suite for Oracle
preview mode
13-14, 25
16
top sessions drilldown
privileges
9, 65
12-13
top SQL drilldown
Spotlight user
39, 46
17
trial key
project lucy
16
15
tuning drilldown
40, 46
R
U
result cache
40
REXEC
uninstall
14
user, Spotlight
17
23, 52
RSA
23
V
S
virtual system
24, 28, 41
28
W
27-28
wait activity
sessions drilldown
39
sessions panel
27
27
20
sga panel
29
waiting events
Windows
28-29
39
31, 43
Spotlight on Windows
drilldowns
43
Spotlight users
17
9
46
23, 52