Preface
This manual describes the functionality and records of JP1/Performance Management - Agent Option for Oracle.
- Organization of this preface
■ Intended readers
This manual describes JP1/Performance Management. The manual is intended for the following readers:
-
Users who wish to design or construct an operation monitoring system.
-
Users who wish to define conditions for collecting performance data.
-
Users who wish to define reports and alarms.
-
Users who wish to use collected performance data to monitor a system.
-
Users who wish to consider or take actions for a system based on monitoring results.
Readers are assumed to be familiar with Oracle and the operation of the system being monitored, and to have a knowledge of the OS.
For details about how to design and run systems that use JP1/Performance Management, also see the following manuals:
-
JP1/Performance Management Planning and Configuration Guide
-
JP1/Performance Management User's Guide
-
JP1/Performance Management Reference
■ Organization of this manual
This manual consists of the following parts, and is a common reference for the following supported OSs: Windows, HP-UX, Solaris, Linux and AIX. Any platform-dependent differences are noted separately in the manual.
- Part 1. Overview
-
This part provides an overview of JP1/Performance Management - Agent Option for Oracle.
- Part 2. Configuration and Operations
-
Part 2 describes how to install and set up JP1/Performance Management - Agent Option for Oracle, and how to run the program in a cluster system.
- Part 3. Reference
-
This part describes the monitoring template, records, and messages of JP1/Performance Management - Agent Option for Oracle.
- Part 4. Troubleshooting
-
This part describes the actions to be taken for errors that might occur during operation of JP1/Performance Management - Agent Option for Oracle.
■ Conventions: Fonts and symbols
Font and symbol conventions are classified as:
-
General font conventions
-
Conventions in syntax explanations
These conventions are described below.
General font conventions
The following table lists the general font conventions:
Font |
Convention |
---|---|
Bold |
Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example, bold is used in sentences such as the following:
|
Italics |
Italics are used to indicate a placeholder for some actual text provided by the user or system. Italics are also used for emphasis. For example:
|
Code font |
A code font indicates text that the user enters without change, or text (such as messages) output by the system. For example:
|
Examples of coding and messages appear as follows (although there may be some exceptions, such as when coding is included in a diagram):
MakeDatabase ... StoreDatabase temp DB32
In examples of coding, an ellipsis (...) indicates that one or more lines of coding are not shown for purposes of brevity.
Conventions in syntax explanations
Syntax definitions appear as follows:
StoreDatabase [A|B] {C|D|E} (database-name ...)
The following table lists the conventions used in syntax explanations.
Example font or symbol |
Convention |
---|---|
StoreDatabase |
The user should enter code-font characters exactly as shown. |
database-name |
In actual commands the user must replace the italics by suitable characters. |
SD |
Bold code-font characters indicate an abbreviation for a command. |
A |
The underlined characters are the system default when you omit all the items enclosed in brackets. Example: [A|B] indicates that the system uses A if you do not specify either A or B. |
| |
Only one of the options separated by a vertical bar can be used at one time. Example: A|B|C indicates A, or B, or C. |
{ } |
One of the items enclosed in braces and separated by a vertical bar must be specified. Example: {C|D|E} indicates that one of the items from C, or D, or E must be specified. |
[ ] |
The item or items enclosed in brackets are optional. Example: [A] indicates the specification of A or nothing. [B|C] indicates the specification of B or C, or nothing. |
... |
The item or items preceding the ellipsis (...) can be repeated. To specify multiple items, use a one-byte space to delimit them. Example: A B ... indicates that B can be specified as many times as necessary after A. |
( ) |
The items enclosed by the parentheses are in the range to which | or ... are applied. |
■ Conventions: Mathematical expressions
The following table lists conventions used in mathematical expressions:
Symbol |
Description |
---|---|
* |
Multiplication sign |
/ |
Division |
■ Conventions: Version numbers
The version numbers of Hitachi program products are usually written as two sets of two digits each, separated by a hyphen. For example:
-
Version 1.00 (or 1.0) is written as 01-00.
-
Version 2.05 is written as 02-05.
-
Version 2.50 (or 2.5) is written as 02-50.
-
Version 12.25 is written as 12-25.
The version number might be shown on the spine of a manual as Ver. 2.00, but the same version number would be written in the program as 02-00.