2
Post-Installation Configuration

After you have installed the Diagnostics Pack, configure the components listed in the following table:

Components	Where to Find the Information
Advanced Events	"Setting Up Advanced Events"
Capacity Planner	"Setting Up Capacity Planner and Performance Manager"
Performance Manager	"Setting Up Capacity Planner and Performance Manager"
TopSessions	"Setting Up TopSessions"
Trace	"Setting Up Trace"

Setting Up Advanced Events

Before you use Oracle Advanced Events, set up the program as follows:

• Create additional tables, views and public synonyms required for the Advanced Events.

  Refer to "Setting Up TopSessions" for information on what scripts to run.

• If you plan to use the Chained Rows advanced events, the CHAINED_ROWS table must exist in the database. To create the CHAINED_ROWS table:
  1. Log into the database as SYS.

  2. Run the utlchain.sql script. This script is located in the $ORACLE_HOME/RDBMS/ADMIN directory.

Setting Up Capacity Planner and Performance Manager

The following setup tasks are required before you use Oracle Capacity Planner or Oracle Performance Manager:

Configure the Oracle Data Gatherer to collect data

Optionally, enable disk statistics collection on Windows NT

The following setup tasks are required before you use Performance Manager:

Convert any user-defined charts you created with earlier versions of Performance Manager

If you plan to use Performance Manager in a Parallel Server environment, you may need to set up your server using Oracle-supplied SQL scripts.

The following sections describe each of these setup tasks in more detail.

Configuring Oracle Data Gatherer to Collect Data

Performance Manager and Capacity Planner require the use of the data gathering service (also known as the Oracle Data Gatherer). For monitoring operating system data, the Oracle Data Gatherer must be installed on the same node as the operating system you are monitoring. For monitoring other service types, such as databases, the Oracle Data Gatherer can run on the same node as the service you are monitoring, or it can run on a different node, depending upon your configuration.

Refer to the Oracle Intelligent Agent User's Guide for information on how to configure and start the Oracle Data Gatherer.

Enabling Disk Statistics Collection on Windows NT

To collect disk statistics on Windows NT, enable them by typing:

diskperf  -Y 

Disk statistics are enabled the next time the system is restarted. For more information about the DISKPERF tool, refer to the Microsoft Windows NT documentation.

Note: Enabling disk statistics is not required. You can still monitor other operating system statistics with Performance Manager or Capacity Planner even if disk statistics are not enabled.

Converting User-Defined Charts From Previous Releases of Performance Manager

If you created user-defined charts using Performance Manager release 1.5.0 or earlier and want to use them with the current Performance Manager release, you must first convert them to release 1.6.0.

Performance Manager Release 1.6.0 user-defined charts are converted to the current release when you migrate your existing performance data to the Enterprise Manager Release 2.1 repository.

For more information, refer to the following sections.

Note: Release 1.5.5 of Performance Manager did not include the functionality of user-defined charts.:

Converting Performance Manager Release 1.5.0 User-Defined Charts

To convert user-defined charts created using Performance Manager Release 1.5.0 or earlier:

1. Run vmmmig.exe. This executable creates a text file named vtmusr.txt in the $ORACLE_HOME\SYSMAN\ADMIN directory. This text file contains data about the user-defined charts created using Performance Manager release 1.5.0 or earlier. When you run vmmmig.exe, specify the user name, password, and service for the Enterprise Manager repository that contains the user-defined charts that you want to convert, for example:

   vmmmig joseph/password@my_rep
   
   

   Note that my_rep in the previous command line is the service name for the Enterprise Manager repository.

2. Run vmm2vtm.exe. This executable uses the data in the vtmusr.txt file to create user-defined charts in the repository that can be used with Performance Manager release 1.6.0. When you run vmm2vtm.exe, supply a user name, password, and service for the Enterprise Manager V2.x repository and the name of the service under which you want the user-defined charts stored for Performance Manager release 1.6.0, for example:

   vmm2vtm.exe joseph/password@my_rep my_db
   
   

   Note that my_rep in the previous command line is the service name of the Enterprise Manager V2.x repository and my_db is the name of the target service under which you want the user-defined charts stored. In other words, after the previous command is run, all the user-defined charts are converted and stored under the my_db service in the Performance Manager release 1.6.0 tree view.

   If any error messages are generated when you run vmm2vtm.exe, edit the vtmusr.txt file based on the error messages. For example, the error messages may state that there is a problem with a chart or that a chart does not exist. Since the vtmusr.txt file contains a list of the charts, edit the file to remove any problematic charts.

   Then, run vmm2vtm.exe again.

Converting Performance Manager Release 1.6.0 User-Defined Charts

If you created user-defined charts with Performance Manager Release 1.6.0, you can convert those charts for use with the current release of Performance Manager. User-defined charts created with Performance Manager 1.6.0 are converted when you create a new Enterprise Manager repository and migrate your existing performance data to the new repository.

For more information about creating a new Oracle Enterprise Manager repository and migrating your existing data, see the Oracle Enterprise Manager Configuration Guide.

Using Performance Manager in a Parallel Server Environment

To use Performance Manager in a Parallel Server environment, two database instances must be started, otherwise Performance Manager does not treat the server as a Parallel Server.

There are two scenarios for using Performance Manager in an Oracle Parallel Server environment, and different configuration steps for each scenario.

The two scenarios and their configuration steps are:

1. If you are using Performance Manager to monitor an Oracle7 Parallel Server environment, do the following:
   1. Ensure all instances are running.

   2. Run the ops_gdl.sql script. This generates an appropriate ops_dbl.sql file. The ops_dbl.sql file shipped with the product is only an example. The actual contents of ops_dbl.sql depend on your database name, instance names, and the number of instances which exist.

   3. Run the ops_mon.sql script, which runs ops_ctab.sql, ops_dbl.sql, ops_pack.sql to create Performance Manager tables and views to fetch and display Oracle7 Parallel Server data in charts.

      Oracle7 does not have global V$ (GV$) tables; these files install a set of PL/SQL procedures, database links, and O$ tables that are used by Performance Manager in the absence of GV$ tables.

2. If you are using Performance Manager to monitor an Oracle8 Parallel Server environment, you do not need to run any of the Parallel Server scripts. For example, if you use any release of Oracle that has GV$ tables (namely Oracle release 8.0 and later), you do not need to run these scripts.

For more information about Parallel Server scripts, see the Oracle Parallel Server Management User's Guide in the Parallel Server documentation set.

Setting Up TopSessions

To install the features of TopSessions:

Create additional tables and views on each database you want to connect to from TopSessions

Grant certain SELECT privileges

The smptsixx.sql scripts have been provided to help automate this process. The xx in the file name identifies the version of the database against which the script should be run. The script for each database version is located in the $ORACLE_HOME\SYSMAN\ADMIN directory.

Version of the Database	Script to Run
Oracle 7.3.4	smptsi73.sql script
Oracle 8.0	smptsi80.sql script
Oracle 8.1	smptsi81.sql script

When smptsixx.sql is run, it also automatically runs the following two scripts:

• catbloxx.sql

• utlxplxx.sql

These two scripts create in the managed database some additional tables, views, and public synonyms that are required by the Oracle Advanced Events.

To set up TopSessions for a database:

1. Access SQL*Plus Worksheet from the Start menu by following the path: Start=>Programs=>ORACLE_HOME=>DBA Management Pack=>SQLPlus Worksheet.

   Note: ORACLE_HOME represents the Oracle home in which the Diagnostics Pack is installed.

2. Use the Oracle Enterprise Manager Login dialog box to connect to the managed database as SYS.

   For additional information, refer to 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.

   Note that when preparing to run the smptsixx.sql script on managed databases, you should log into each database as SYS, as mentioned previously.

   You can use Security Manager to grant privileges to an account. Refer to the Oracle Enterprise Manager Online Help for detailed information about how to use Security Manager.

4. Run the smptsixx.sql script for the managed database.

   If the smptsixx.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 TopSessions.

5. If the ALL_CATALOG view does not exist on the managed database, run the catalog.sql script on the database from the SYS account. The catalog.sql script is located in the $ORACLE_HOME\RDBMSxx\ADMIN directory.

6. If the AUDIT_ACTIONS view does not exist on the managed database, run the cataudit.sql script on the database from the SYS account. The cataudit.sql script is located in the $ORACLE_HOME\RDBMSxx\ADMIN directory.

7. Exit SQL*Plus Worksheet.

Setting Up Trace

Trace requires that the:

• Oracle Intelligent Agent for Oracle release 7.3.4 or later is installed and running on the nodes that are targets for Trace collections

• Oracle Management Server (OMS) is running, and the nodes on which you want to use Trace have been discovered using the Oracle Enterprise Manager Console.

To successfully use Trace, you must:

• Configure Trace for Oracle8 Server collections

• Configure Trace for Oracle 7.3.4 Server collections

• Create Trace Formatter Tables

Using Trace for Oracle8 Server Collections

If you are using Trace for Oracle8 server collections, you must set the value of the ORACLE_TRACE_ENABLE parameter in your INITsid.ORA file to TRUE.

Using Trace for Oracle 7.3.4 Server Collections

If you are using Trace to collect data from Oracle 7.3.4 server collections, verify the following exist:

• Trace user account: TRACESVR

• Trace stored procedure packages: DBMS_ORACLE_TRACE_AGENT and DBMS_ORACLE_TRACE_USER

If they do not, you must create them by running the otrcsvr.sql script as SYS.

The otrcsvr.sql script is located in $ORACLE_HOME/otrace/admin on UNIX systems and in $ORACLE_HOME\otracexx\admin on Windows NT systems.

The otrcsvr.sql script is run automatically during database installation on most platforms. However, if your server platform is Windows NT, you must run this script manually.

Creating Trace Formatter Tables

If you are using the Trace Collection Services release 8.0.4 or later, the formatter tables are created for you.

The Trace formatter tables are required in managed databases by Trace, which converts and loads a Trace binary file (collection_name.dat) into Oracle tables for access.

Trace data collected from Oracle 7.3.4 and later databases can only be stored in databases that are using the latest Trace formatter tables. Use the vobsh command, which is available only on Windows platforms, to create new formatter tables, delete existing formatter tables, or upgrade earlier versions of formatter tables to the latest version for a database.

The formatter table operations and vobsh commands to perform these operations are described in the following sections. These vobsh commands are unsuccessful if the specified user does not have an account for the specified service. In this case, create an account for the user on the specified service, then enter the vobsh command again.

Creating New Formatter Tables

To create new formatter tables in a database where no formatter tables currently exist, use the vobsh command:

vobsh -c "user/password@service" -o CREATE -p "EPCFMT"

Note that the formatted data stored in formatter tables can grow very large, so the database in which formatter tables are created should have sufficient space to store large amounts of data.

Dropping Existing Formatter Tables

To drop existing formatter tables from a table, use the vobsh command:

vobsh -c "user/password@service" -o DROP -p "EPCFMT"

This command drops any version of formatter tables from the specified database. Note that in addition to dropping the existing formatter tables, vobsh also deletes the formatted data stored in the tables.

Upgrading Formatter Tables

To validate (upgrade) older versions of the formatter tables (which creates, drops, or upgrades the formatter tables as needed), use vobsh command:

vobsh -c "user/password@service" -o VALIDATE -p "EPCFMT"

This command determines what version of the formatter tables the database has and enables you to upgrade them to the new version, if necessary.

Other Configuration Information

If you experience any problems running Trace after completing the configuration instructions in this chapter, refer to the "Troubleshooting Oracle Trace" appendix of the Oracle Enterprise Manager Oracle Trace User's Guide.

---