| Oracle(R) Enterprise Manager Getting Started with the Oracle(R) Standard Management Pack Release 2.1 A76910-01 |
|
After you have installed the Standard Management Pack, configure the components listed in the following table:
| Components | Where to Find the Information |
|---|---|
|
Performance Manager |
|
|
TopSessions |
The following setup tasks are required before you use Oracle Performance Manager:
The following sections describe each of these setup tasks in more detail.
Performance Manager requires 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.
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.
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.
To convert user-defined charts created using Performance Manager Release 1.5.0 or earlier:
vmmmig joseph/password@my_rep
Note that my_rep in the previous command line is the service name for the Enterprise Manager repository.
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.
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.
To install the features of TopSessions:
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:
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:
For additional information, refer to the online help or the Oracle Enterprise Manager Administrator's Guide.
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.
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.