Skip Headers
Oracle® Enterprise Manager Oracle Application Server Metric Reference Manual
10g Release 2 (10.2)

Part Number B25987-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Feedback

Go to previous page
Previous
Go to next page
Next
View PDF

20 Reports Server

You can use Oracle Enterprise Manager to monitor and manage Oracle Reports Server.

20.1 Cluster Information

Provides information about the cluster under which various Reports Servers might be running. The following table lists the metrics and their descriptions.

Table 20-1 Cluster Information Metrics

Metric Description

Current Jobs

Total number of currently running jobs in the Reports Server Cluster Job Queue

Failed Jobs

Total number of jobs for the listed Reports Server cluster that were stopped before completion. This includes cancelled jobs as well as those terminated with error.

Finished Jobs

Total number of finished jobs currently in the Reports Server cluster

Response Time (ms)

Average number of milliseconds it takes for the listed Reports Server cluster to process a request from the client

Scheduled Jobs

Total number of scheduled jobs currently in the listed Reports Server Cluster Job Queue

Server Name

Lists the names of each of the other Reports Servers that are members of the same cluster that the selected Reports Server belongs to. Click the server's name to hyperlink to the OEM home page for that server.


20.2 Current Jobs

Provides information about the currently running jobs in the Reports Server. The following table lists the metrics and their descriptions.

Table 20-2 Current Jobs Metrics

Metric Description

Id

Unique job identifier assigned to this job by the Reports Server. This number is strictly under the server's control and cannot be reset by a user.

Job Name

If you specified a job name in the command line you used to run this job, that name is listed here. Otherwise, it is the name of the job provided for the "report=" or "module=" parameter of the job request.

Output Format

Output format (desformat) specified for this job at runtime

Output Type

Destination type (destype) specified for this job at runtime

Owner

User ID under which this job is running

Queued At

Date and time this job request was placed in the Job Queue

Started At

Date and time this job started running

Status

Status of the current job


20.3 Engine Information

Provides detailed information about engines currently running on the selected Reports Server and supplies the means of managing them. The following table lists the metrics and their descriptions.

Table 20-3 Engine Information Metrics

Metric Description

Engine ID

Type of engines available for processing jobs on the selected Reports Server

Engines

Total number of this type of engine that is currently running on the selected Reports Server

Idle Time (seconds)

Time (in seconds) that the engine has remained idle since the last job ran

Job Running Time (ms)

Time (in milliseconds) taken to execute the job till now

Jobs Run

Number of jobs that the engine has run till now

Life Remaining (jobs)

Number of jobs that the selected engine can run before which it will be shut down

Name

Lists the name of the various engines available for processing jobs on the selected Reports Server

NLS

NLS value with which the engine is started. If the NLS language for the engine has not been specified in the server configuration file then the value defaults to the Reports Server's NLS

Process ID

Operating System PID of the engine process

Running

Number of engines currently running (active) in the Reports Server processing requests

Running Job ID

ID of the job that is running on this engine. "n/a" indicates that the engine is not running any jobs

Status

Engine's status

Total Idle Time (minutes)

Total time that the selected engine has remained idle between running jobs

Total Running Time (seconds)

Total time taken by the engine to run all the jobs


20.4 Failed Jobs

Provides the total number of jobs currently in the selected Reports Server's Job Queue that were stopped before completion. This includes cancelled jobs as well as those terminated with error. When this number is higher than 0, it links to the Failed Jobs Queue, where you can get detail on why a job failed, view the job's trace file, and resubmit the job.

Table 20-4 Failed Jobs Metrics

Metric Description

Finished At

Date and time this job was cancelled or terminated with error

Id

Unique job identifier assigned to this job by the Reports Server. This number is strictly under the server's control and cannot be reset by a user. When the job includes the generation of a trace file, the value under Id is linked to the trace file for this job. Click Id to view this report's associated trace file

Job Name

If you specified a job name in the command line you used to run this report, that name is listed here. Otherwise, it is the name of the job provided for the "report=" or "module=" parameter of the report request.

Output Format

Destination format (desformat) specified for this report at runtime

Output Type

Destination type (destype) specified for this job at runtime

Owner

User ID under which this job was run.

Queued At

Date and time this job request was placed in the Job Queue

Started At

Date and time this job started running

Status

Status of the job. Status will either indicate that the job was cancelled by the user or provide some information on why the job was terminated with error.


20.5 Finished Jobs

Provides a detailed look at all successfully completed jobs in the Job Queue on the selected Reports Server.

Table 20-5 Failed Jobs Metrics

Metric Description

Finished At

Date and time this job completed

Id

Unique job identifier assigned to this report by the Reports Server. This number is strictly under the server's control and cannot be reset by a user. When the job includes the generation of a trace file, the value under Id is linked to the trace file for this job. Click Id to view this report's associated trace file

Job Name

If you specified a job name in the command line you used to run this report, that name is listed here. Otherwise, it is the name of the job provided for the "report=" or "module=" parameter of the job request. Job Name is linked to the output of this job. Click Job Name to see a Web version of this job's output (fetched from the Reports Server cache).

Output Format

Destination format (desformat) specified for this job at runtime

Output Type

Destination type (destype) specified for this job at runtime

Owner

User ID under which this job was run.

Queued At

Date and time this job request was placed in the Job Queue

Started At

Date and time this job started running

Status

Finished status of the job. In the Finished Job Queue, Status is always Finished Successfully


20.6 Response

Provides the average number of milliseconds it takes for the selected Reports Server to process a request from the client.

20.6.1 Server Status

Indicates whether the server is up or down.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 20-6 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

=


Not Defined

0

1

Not Defined


20.6.2 Server Type

For all target versions, the collection frequency for this metric is every 5 minutes.

20.7 Scheduled Jobs

Provides a detailed look at all jobs scheduled to run on the selected Reports Server and supplies the means of cancelling a scheduled job. The following table lists the metrics and their descriptions.

Table 20-7 Scheduled Jobs Metrics

Metric Description

Id

Unique job identifier assigned to this job by the Reports Server. This number is strictly under the server's control and cannot be reset by a user.

Job Name

If you specified a job name in the command line you used to run this report, that name is listed here. Otherwise, it is the name of the job provided for the "report=" or "module=" parameter of the job request.

Last Run At

Time the current job was processed

Next Run At

Time when the current job will run again

Output Format

Output format (desformat) specified for this job a runtime

Output Type

Destination type (destype) specified for this job at runtime

Owner

User ID under which this job is running

Repeat Interval

Frequency at which the current job is scheduled to run. For example, daily, monthly, and so on. This setting only appears on the Reports Server Scheduled Job Queue page.


20.8 Server Information

Provides information about the Reports Server, number of engines, and other parameters related to the Reports Server. This information looks at the entire life cycle of the Reports Server for all the requests handled by the Reports Server, while the Server Performance Data metrics measure the performance of the Reports Server on a real time basis where the metrics generated are based on the requests handled by the Reports Server in last 5 minutes.

The following table lists the metrics and their descriptions.

Table 20-8 Server Information Metrics

Metric Description

Active Engines

Number of engines currently running on the selected Reports Server.

Average Elapsed Time (ms)

Time the current job has been running in the Reports Server and has not yet finished. This metric will be non-zero when a currently running job has been running longer than the default Elapsed Time Limit (currently at 3 minutes). The Elapsed Time Limit can be modified by configuring the Reports Server target from Oracle Enterprise Manager (Central Console)

Average Response Time (ms)

Average number of milliseconds it takes for the selected Reports Server to process a request from the client.

Cluster Name

If the selected Reports Server is a member of a server cluster, the cluster name is listed here.

Current Jobs

Total number of currently running jobs in the Job Queue.

Failed Jobs

Total number of jobs currently in the Job Queue that were stopped before completion. This includes cancelled jobs as well as those terminated with error.

Failed Ratio (%)

Indicates the health of the Reports Server. This is ratio of failed jobs to past jobs (failed jobs / (finished jobs + failed jobs)).

Finished Jobs

Total number of jobs that have finished running successfully. When this number is higher than 0, it links to the Finished Jobs Queue, where you can get more detail on the finished job, view the job's trace file, view the job result from cache, and resubmit the job.

Maximum Queue Size

Value you have entered for the maximum queue size under the queue element in your Reports Server configuration file (server_name.conf). The queue element specifies the maximum number of jobs that can be held in the Reports server's past job queue. If the maximum is reached, the oldest job(s) are automatically purged to make room for the newest (first in/first out, or FIFO).

Scheduled Jobs

Total number of jobs currently in the Scheduled Jobs Queue. When this number is greater than 0, it links to the Scheduled Jobs Queue, where you can view details and cancel the scheduled job.

Start Time (ms since epoch)

Date and time the selected Reports Server was last started.

Trace File Name

Reports Server trace file name.

Trace Mode

Trace mode specified in the Reports Server configuration file for the trace log file, either Replace (the default) or Append. Trace Replace replaces the existing text in the trace log file with new information. Trace Append appends new information to the end of existing trace log file.

Trace Option

If you have entered an Oracle Trace option in your Reports Server configuration file, server_name.conf this field lists the option(s) entered.

Transferred Jobs

In a clustered server environment, provides the total number of jobs transferred between the selected Reports Server and other cluster members. For example, if the selected Reports Server receives a request for a job that was run earlier on another cluster member, the request is transferred to the cluster member that provided the earlier result and the result is delivered to the client from the cluster member's cache. Such a transaction would be counted as one transfer within the cluster.

Version

Current version of the Reports Server


20.9 Server Performance Data

Provides metrics for the jobs processed/requested for the last 5 minutes. Server Performance Data metrics are similar to Server Information metrics; the Server Information metrics are examined to generate metrics numbers for the jobs processed/requested for the last 5 minutes.

The following table lists the metrics and their descriptions.


Note:

For all target versions, the collection frequency for each metric is every 5 minutes.

Table 20-9 Server Performance Data Metrics

Metric Description

Active Engines

Number of engines currently running on the selected Reports Server

Average Elapsed Time to date (ms)

Provides the averaged elapsed time for all jobs that have run in the Reports Server in the last 5 minutes. This metric will be non-zero when any running job runs longer than the default Elapsed Time Limit (currently at 3 minutes). The Elapsed Time Limit can be modified by configuring the Reports Server target from Oracle Enterprise Manager (Central Console)

Average Response Time (ms)

See Section 20.9.1, "Average Response Time (ms)"

Cluster Name

If the selected Reports Server is a member of a server cluster, the cluster name is listed here

Current Job Load

Number of jobs (failed, successful, and currently running) in the Reports Server for a period of time (5 minutes)

Current Jobs

Total number of currently running jobs in the Job Queue

Failed Jobs

Total number of jobs currently in the Job Queue that were stopped before completion. This includes cancelled jobs as well as those terminated with error.

Failed Ratio (%)

See Section 20.9.2, "Failed Ratio (%)"

Job Load

Number of failed and successful jobs processed by the Reports Server in the last 5 minutes

Maximum Queue Size

Provides the value you have entered for the maximum queue size under the queue element in your Reports Server configuration file (server_name.conf). The queue element specifies the maximum number of jobs that can be held in the Reports server's past job queue. If the maximum is reached, the oldest job(s) are automatically purged to make room for the newest (first in/first out, or FIFO)

Scheduled Jobs

Total number of jobs currently in the Scheduled Jobs Queue. When this number is greater than 0, it links to the Scheduled Jobs Queue, where you can view details and cancel the scheduled job.

Start Time (ms since epoch)

Date and time the selected Reports Server was last started

Successful Jobs

Number of successful jobs processed by the Reports Server in the last 5 minutes

Trace File Name

Reports Server trace file name

Trace Mode

Indicates the trace mode specified in the Reports Server configuration file for the trace log file, either Replace (the default) or Append. Trace Replace replaces the existing text in the trace log file with new information. Trace Append appends new information to the end of existing trace log file.

Trace Option

If you have entered an Oracle Trace option in your Reports Server configuration file, server_name.conf, this field lists the option(s) entered.

Transferred Jobs

In a clustered server environment, provides the total number of jobs transferred between the selected Reports Server and other cluster members. For example, if the selected Reports Server receives a request for a job that was run earlier on another cluster member, the request is transferred to the cluster member that provided the earlier result and the result is delivered to the client from the cluster member's cache. Such a transaction would be counted as one transfer within the cluster.

Version

Current version of the Reports Server


20.9.1 Average Response Time (ms)

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 20-10 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

5000

15000

1

Not Defined


20.9.2 Failed Ratio (%)

The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 20-11 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

All Versions

Every 5 Minutes

After Every Sample

>

25

33

1

Not Defined