Installing and Configuring Statspack

With the addition of the Active Workload Repository (AWR) and Active Session History (ASH) in Oracle Database 10g and higher it might seem a little odd to still be talking about Statspack. Both AWR and ASH require an Oracle Diagnostics Pack license which is limited to the Enterprise Edition of the database.

This document will detail the interactive setup of Statspack along with setting up a schedule and job to automate the snapshot collection process.

Installing Statspack

First create the tablespace to hold the Statspack tables.

SQL> create tablespace statspack_data
  2  datafile '/data/oracle/database/11gR2/oradata/scratch/statspack_data01.dbf' size 500M
  3  autoextend on maxsize 2G
  4  extent management local uniform size 1M
  5  segment space management auto;

Tablespace created.


Run the ORACLE_HOME/rdbms/admin/spcreate.sql script to create the PERFSTAT schema. The script runs three scripts: spcuser.sql to create the PERFSTAT user, spctab.sql to create the Statspack tables and synonyms and finally spcpkg.sql to create the statistic gathering packages.

C:\app\oracle\product\11.2.0\dbhome_1\RDBMS\ADMIN>sqlplus / as sysdba

SQL*Plus: Release - Production on Tue Aug 10 09:55:07 2010

Copyright (c) 1982, 2008, Oracle.  All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> @spcreate.sql

Choose the PERFSTAT user's password
Not specifying a password will result in the installation FAILING

Enter value for perfstat_password:

Provide a password for the PERFSTAT user and hit enter.

Choose the Default tablespace for the PERFSTAT user
Below is the list of online tablespaces in this database which can
store user data.  Specifying the SYSTEM tablespace for the user's
default tablespace will result in the installation FAILING, as
using SYSTEM for performance data is not supported.

Choose the PERFSTAT users's default tablespace.  This is the tablespace
in which the STATSPACK tables and indexes will be created.

------------------------------ --------- ----------------------------
EXAMPLE                        PERMANENT
SYSAUX                         PERMANENT *
USERS                          PERMANENT

Pressing <return> will result in STATSPACK's recommended default
tablespace (identified by *) being used.

Enter value for default_tablespace: STATSPACK_DATA

A list of available table spaces will be presented next. Type in the name of the table space created earlier and hit the enter key.

Choose the Temporary tablespace for the PERFSTAT user
Below is the list of online tablespaces in this database which can
store temporary data (e.g. for sort workareas).  Specifying the SYSTEM
tablespace for the user's temporary tablespace will result in the
installation FAILING, as using SYSTEM for workareas is not supported.

Choose the PERFSTAT user's Temporary tablespace.

------------------------------ --------- --------------------------
TEMP                           TEMPORARY *

Pressing <return> will result in the database's default Temporary
tablespace (identified by *) being used.

Enter value for temporary_tablespace:

Next we need to select a temporary table space for the PERFSTAT user. You can hit the enter key to use the default temporary table space. Once you select the temporary table space the PERFSTAT user and all the objects owned by PERFSTAT will be created.

Logs of the execution are written to spcuser.lis, spctab.lis and spcpkg.lis. Providing there are no errors we have successfully installed Statspack.

Taking Snapshots

Taking snapshots is as easy as executing the STATSPACK.SNAP procedure. There are five snap shot levels (0, 5, 6, 7, 10) with 5 being the default. Details of levels can be found in the documentation and from stats$level_description

SQL> select * from stats$level_description;

----------  --------------------------------------------------------------------
         0  This level captures general statistics, including rollback segment, 
            row cache, SGA, system events, background events, session events, 
            system statistics, wait statistics, lock statistics, and Latch 

         5  This level includes capturing high resource usage SQL Statements, 
            along with all data captured by lower levels

         6  This level includes capturing SQL plan and SQL plan usage 
            information for high resource usage SQL Statements, along with all 
            data captured by lower levels

         7  This level captures segment level statistics, including logical and 
            physical reads, row lock, itl and buffer busy waits, along with all 
            data captured by lower levels

        10  This level includes capturing Child Latch statistics, along with 
            all data captured by lower levels


If you want to take a snapshot at a different level you can pass in the desired level using the i_snap_level parameter.

For example the following takes a snapshot at level 7

SQL> exec statspack.snap(i_snap_level => 7);

PL/SQL procedure successfully completed.


If you would like to change the default level from 5 to 7 you can do so with STATSPACK.MODIFY_STATSPACK_PARAMETER using the i_snap_level and i_modify_parameter parameters.

SQL> exec statspack.modify_statspack_parameter(i_snap_level=>7, i_modify_parameter=>’true’);

PL/SQL procedure successfully completed.


Keep in mind that the higher the snapshot levels require more time and resources to execute than the lower snapshot levels.

Automating snapshot collection

Automating the collection of snapshots through out the day provides useful information to aid in detecting the source of performance related issues. Care should be taken that the snapshots are not taken so frequently that the collections become a source of problems and not so far apart that it is difficult to obtain useful information.

Below is a schedule and job to collect Statspack snap shots every 20 minutes. This schedule will make collections at 10, 30 and 50 after the hour. The choice of 10 before and after the hour is used to avoid collecting at the same time AWR data is collected which defaults to every hour.

  3     schedule_name => 'perfstat.statspack_every20',
  4     repeat_interval => 'FREQ=MINUTELY;BYMINUTE=10,30,50');
  7     job_name => 'perfstat.sp_snapshot',
  8     job_type => 'STORED_PROCEDURE',
  9     job_action => 'perfstat.statspack.snap',
 10     schedule_name => 'perfstat.statspack_every20',
 11     comments => 'Statspack collection');
 13    DBMS_SCHEDULER.ENABLE('perfstat.sp_snapshot');
 14  END;
 15  /

PL/SQL procedure successfully completed.


Running a report

There are two types a reports you can run: an Instance report and a SQL Report.

ORACLE_HOME\rdbms\admin\spreport.sql is used to generate an instance level report. For an instance level report the beginning and ending snapshot id and the name of the output report are required.

SQL> @spreport

Current Instance
♀   DB Id    DB Name     Inst Num Instance
----------- ------------ -------- ------------
 1253224498 ORCL                1 orcl

1 row selected.

SP2-0311: string expected but not found

Instances in this Statspack schema

   DB Id    Inst Num DB Name      Instance     Host
----------- -------- ------------ ------------ ------------
 1253224498        1 ORCL         orcl         ODWIN

Using 1253224498 for database Id
Using          1 for instance number

Specify the number of days of snapshots to choose from
Entering the number of days (n) will result in the most recent
(n) days of snapshots being listed.  Pressing <return> without
specifying a number lists all completed snapshots.

Listing all Completed Snapshots

Instance     DB Name        Snap Id   Snap Started    Level Comment
------------ ------------ --------- ----------------- ----- --------------------
orcl         ORCL                 4 10 Aug 2010 13:10     5
                                  5 10 Aug 2010 13:30     5
                                  6 10 Aug 2010 13:50     5
                                  7 10 Aug 2010 14:10     5

Specify the Begin and End Snapshot Ids
Enter value for begin_snap: 4
Begin Snapshot Id specified: 4

Enter value for end_snap: 5
End   Snapshot Id specified: 5

Specify the Report Name
The default report file name is sp_4_5.  To use this name,
press <return> to continue, otherwise enter an alternative.

Enter value for report_name: testreport.txt

Once you enter the name of the output file the Statspack report will be generated to the both the screen and the file.

After viewing the instance report you might want to look deeper at a particular SQL statement from the report. The script ORACLE_HOME/rdbms/admin/sprepsql.sql can be used to generate an SQL report. In addition to the beginning and ending snapshot id and output file name the SQL Hash value is required.

Snapshot maintenance

Remove a snapshot or a range of snapshots using ORACLE_HOME/rdbms/admin/sppurge.sql

SQL> @sppurge

Database Instance currently connected to

   DB Id    DB Name    Inst Num Name
----------- ---------- -------- ----------
 1253224498 ORCL              1 orcl

Snapshots for this database instance

                               Base-  Snap
 Snap Id   Snapshot Started    line? Level Host            Comment
-------- --------------------- ----- ----- --------------- --------------------
       1  10 Aug 2010 12:12:59           5 ODWIN
       2  10 Aug 2010 12:23:23           5 ODWIN
       3  10 Aug 2010 12:50:06           5 ODWIN

sppurge.sql deletes all snapshots ranging between the lower and
upper bound Snapshot Id's specified, for the database instance
you are connected to.  Snapshots identified as Baseline snapshots
which lie within the snapshot range will not be purged.

It is NOT possible to rollback changes once the purge begins.

You may wish to export this data before continuing.

Specify the Lo Snap Id and Hi Snap Id range to purge
Enter value for losnapid: 1
Using 1 for lower bound.

Enter value for hisnapid: 2
Using 2 for upper bound.

Deleting snapshots 1 - 2.

Number of Snapshots purged: 2

Purge of specified Snapshot range complete.


Remove all snapshots using ORACLE_HOME/rdbms/admin/sptrunc.sql

Uninstall Statspack

If you decide you do not need Statspack installed any more you can remove/uninstall Statspack with ORACLE_HOME/rdbms/admin/spdrop.sql. The spdrop.sql needs be dropped by a user with SYSDBA. Remember to remove any jobs you might have created to manage the Statspack environment.

8 thoughts on “Installing and Configuring Statspack”

  1. Hi, I have installed the Statspack. Now I want to review the contents of the spcpkg.lis, spctab.lis and spcusr.lis log files but I don’t know how to access the log files. Can you please advise how to do this for beginners?

  2. nope, i cannot locate the spcpkg.lis ar ORACLE_HOME/rdbms/admin

    I saw spcpkg.sql. Not too sure what is it. Btw i am testing it on windows oracle database.

  3. Hi i am getting below error while generating report
    ERROR at line 1:
    ORA-20200: Begin Snapshot Id 61 does not exist for this database/instance
    ORA-06512: at line 28

    i have checked with some other snap_id’s but result was shown the same as above. please let me know If is ther any way to select correct snap_id to generate the reports.


  4. han, the “.lis” files will be created in the directory from where you opened sqlplus in Windows. Let’s say you opened a DOS command prompt and you landed at C:\Users\han directory. Then you opened sqlplus from there to run “spcreate.sql”. Then your “.lis” files will be in “C:\Users\han” directory. Alternatively, from the SQL prompt, you can type “host dir *.lis” command to see the files listed.

  5. han, “spcpkg.sql” is actually a script that is called by “spcreate.sql” script that you executed for Statspack. The “spcreate.sql” script, in turn, calls “spcusr.sql” script to create the PERFSTAT user, then “spctab.sql” to create a few tables in it, and finally “spcpkg.sql” to create a few packages in it. In PERFSTAT schema, that is. All these 4 scripts are in ORACLE_HOME\rdbms\admin directory. You can open “spcreate.sql” in a text editor and simply read the code to get a better idea of what it is doing and how it is doing that.

  6. Hello just wanted to say thank you for putting this page together. It has been really useful.

Leave a Reply

Your email address will not be published. Required fields are marked *