Oracle Enterprise Manager Installation Guide

Performance Pack Configuration

Setting up the Performance Pack Applications
Setting up TopSessions
Setting up Oracle Trace
Setting up Oracle Performance Manager
Setting up Oracle Expert

This chapter describes how the Oracle Performance Pack is set up. It covers:

Setting up the Performance Pack Applications

The Performance Pack applications are set up after you have installed the Oracle Performance Pack.

For information on how each Performance Pack application is set up, see the specific section in this chapter.

Note:
The Performance Pack is a separately licensed and purchased product.

Setting up TopSessions

In order to install the features of Oracle TopSessions, you need to create additional tables and views on each database you want to connect to from TopSessions. In addition, certain SELECT privileges must be granted.

The SMPTSI7x.SQL scripts have been provided to help automate this process. The scripts for each database version are located in the $ORACLE_HOME\SYSMAN\ADMIN directory.

To set up Oracle TopSessions for a database:

1.: From the Oracle Enterprise Manager program group, double-click on the SQL Worksheet icon to launch the tool. For information on starting Oracle Enterprise Manager and tools, see Starting Enterprise Manager Tools on page 3-6.
2.: Use the Login Information dialog box to connect to the managed database as SYS. See the online help or the Oracle Enterprise Manager Administrator's Guide.
3.: Grant SELECT ANY TABLE privileges to each administrator account. This step may be omitted if the account has already been granted the same privileges as SYSTEM.

Attention:
Refer to Repository User Account on page 3-2 for an example of how to grant privileges to an account. Note that when preparing to run the SMPTS17x.SQL script on managed databases, you should log into each database as SYS, as mentioned previously.

4.: Run the SMPTSI7x.SQL script for the managed database.

Attention:
If the SMPTSI7x.SQL script is not run on a managed database, you may see a "Table or View does not exist" message when you try to use Oracle TopSessions.

5.: Exit SQL Worksheet.

Setting up Oracle Trace

Oracle Trace relies on correct client/server configuration. Oracle Trace release 1.3.5 only works against Oracle Server release 7.3.3 and SQL*Net release 2.3.

Oracle Trace also requires:

installation of the Oracle Enterprise Manager agent on nodes where tracing occurs
running the Oracle Enterprise Manager Console because Oracle Trace uses the Oracle Enterprise Manager job subsystem to perform its tasks.

Creating Oracle Trace Repository Tables

All the necessary tables for Oracle Trace are created or updated automatically when any Oracle Enterprise Manager Performance Pack product is started for the first time.

Creating Oracle Trace Formatter Tables

If you had an earlier version of Oracle Trace and you run into problems formatting collections after installing Oracle Trace, make sure that you drop and re-create your formatter tables using the scripts provided with the kit by performing the following steps.

1.: Connect to each database and user account where formatting tables are located.
2.: To drop the older version of the repository, run the otrccatd.sql script.
3.: To drop the formatter tables, run the otrcfmtd.sql script.
4.: To re-create formatter tables, run the otrcfmtc.sql script.

The otrcfmtd.sql and otrcfmtc.sql scripts can be found on both the server and the client. On the client these scripts are in the ORACLE_HOME\otrace7x\admin directory. The otrccatd.sql script is located in the ORACLE_HOME\sysman\admin directory. These scripts should be run from Server Manager.

The formatter table creation script, otrcfmtc.sql, must be run in any database that you want to format data into.

Setting up Oracle Performance Manager

The repository tables required by the Save/Load Charts feature of Oracle Performance Manager are created when the Oracle Enterprise Manager Performance Pack repository is created.

The Performance Manager also uses the Oracle Trace formatter tables to store and playback recorded data. These tables are created in the repository when the repository is created. To create these tables in a different database:

1.: Connect to the database and user account where you want to store the recorded data.
2.: Run the otrcfmtc.sql script to create the Oracle Trace formatter tables.

If you used the recording and playback feature with earlier versions of Oracle Enterprise Manager, you should drop and re-create the formatter tables that were used to record and playback the data. See Creating Oracle Trace Formatter Tables on page 5-3 for instructions on dropping and re-creating formatter tables.

Note:
The Chart FX DLL is required for Oracle Performance Manager. The version that is on the CD Rom has been enhanced and is different from the Chart FX DLL that is shipped by Software FX. The updated version for Oracle Performance Manager is installed in $ORACLE_HOME\BIN.

Using Performance Manager with Parallel Server

To run Performance Manager in a Parallel Server environment, the following must be true:

Two instances must be started, otherwise Performance Manager does not treat the server as a Parallel Server. When Performance Manager knows that a Parallel Server is running, it enables the menu items for Parallel Server.

The following Parallel Server scripts must have been run:

ops_mon.sql
ops_ctab.sql
ops_pack.sql
ops_dbl.sql

: These Parallel Server scripts are provided with the Parallel Server installation. Running these scripts creates performance monitoring tables and views that Performance Manager requires to fetch and display Parallel Server data in charts.

For more information, see the Parallel Server documentation.

Setting up Oracle Expert

When you set up Oracle Expert, review the following sections on creating the repository tables and running the XPVIEW.SQL script.

Creating Oracle Expert Repository Tables

Oracle Expert requires a set of database tables in the Oracle Enterprise Manager repository. These tables store the data associated with each Oracle Expert tuning session.

All the necessary tables are created or updated automatically when any Oracle Enterprise Manager Performance Pack product is started for the first time.

Running XPVIEW.SQL

Before you collect the instance class for a database, run the XPVIEW.SQL script on the database to ensure all instance statistics are collected. After you run the SQL script, Oracle Expert can collect information about the database's shared SQL pool. XPVIEW.SQL only needs to be run once for each database instance.

Copyright © 1996 Oracle Corporation.
All Rights Reserved.