42 Agent

The oracle_emd target is a representation of the machine running the Oracle Management Agent. The Oracle Management Agent is the Management Agent used by Oracle Enterprise Manager. This target type exposes useful information required to monitor the performance of the Management Agent.

Most of the help topics in this helpset use the term Management Agent to refer to the Oracle Management Agent.

42.1 Agent Process Statistics

The EMD Process Statistics provides information about the performance and resource consumption of the Management Agent process. This metric is collected by default on an interval of 1038 seconds. A value that can be changed in the default collection for the oracle_emd target.

42.1.1 CPU Usage (%)

The CPU Usage metric provides the CPU consumption as a percentage of CPU time at any given moment in time. The number is a summation of the CPU consumption of the Management Agent process and any of its child processes (and their child processes and so on). Child processes are sometimes created by the Management Agent in the course of evaluating a metric or running a job.

42.1.1.1 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 42-1 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 1038 Hours	After Every Sample	>	10	20	4	Agent CPU consumption is %value%%%

42.1.1.2 Data Source

The source for this metric is the UNIX ps command.

42.1.1.3 User Action

A large CPU consumption will cause the entire system to slow down. The cause could be the Management Agent process itself or any of its child processes. To analyze what is causing the problem, use the Solaris "top" system command and look out for any Perl or Java processes that seem to be consuming excessive CPU (%).

42.1.2 Number Files Open

This metric records the number of files currently opened by the Management Agent process. The file types that constitute this number are: regular files, links, sockets, directories and name pipes.

42.1.2.1 Metric Summary

Table 42-2 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 1038 Hours	After Every Sample	>	800	900	2	Number files opened by Agent is %value%

42.1.2.2 Data Source

The source of this information is the UNIX pfiles command.

42.1.2.3 User Action

Specific to your site.

42.1.3 Number Threads Created

This metric shows the number of threads currently created by the Management Agent process.

42.1.3.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 1038 Hours

42.1.3.2 Data Source

The source of this metric is the UNIX ps command.

42.1.3.3 User Action

Specific to your site.

42.1.4 Process ID

The process ID is the process ID of the Management Agent.

42.1.4.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 1038 Hours

42.1.4.2 Data Source

The source of this is the Perl getppid function.

42.1.4.3 User Action

Specific to your site.

42.1.5 Resident Memory Utilization (%)

The Resident Memory Utilization is the physical memory usage as a percentage of total memory available.

42.1.5.1 Metric Summary

Table 42-3 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 1038 Hours	After Every Sample	>	20	30	1	Agent resident memory utilization is %value%%%

42.1.5.2 Data Source

The source of this information is the UNIX ps system command.

42.1.5.3 User Action

Specific to your site.

42.1.6 Resident Memory Utilization (KB)

This metric represents the amount of physical memory usage by the Management Agent process and all of its child processes in KB.

42.1.6.1 Metric Summary

Table 42-4 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 1038 Hours	After Every Sample	>	128000	256000	1	Agent resident memory utilization in KB is %value%

42.1.6.2 Data Source

The source of this data is the UNIX ps system command.

42.1.6.3 User Action

The default warning and critical threshold values for this metric are set higher than what is expected to be necessary in many cases. You will probably want to lower the warning and critical thresholds to values that work well for the number and types of targets that are being monitored by the Management Agent.

42.1.7 Virtual Memory Utilization (KB)

The Virtual Memory Utilization (VMU) metric provides a sum of the VMU usage of the Management Agent and all of its child processes (and their child processes and so on). Child processes are sometimes created by the Management Agent in the course of evaluating a metric or running a job.

42.1.7.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 1038 Hours

42.1.7.2 Data Source

The source of this information is the UNIX ps system command.

42.1.7.3 User Action

Large virtual memory utilization will also slow the system down. Use the Solaris "top" command to see what processes are consuming this memory. Look out for Perl and Java processes as well as the obvious emdaemon process (the Management Agent process itself.)

42.1.8 Virtual Memory Utilization Growth (%)

Virtual memory utilization growth (%) shows the percentage growth of the virtual memory percentage usage of the Management Agent process. For example: if at time t1 (t1 < t2) the usage was a% and at time t2 it was b%, the growth % would be ((b-1)/a)%.

42.1.8.1 Metric Summary

Table 42-5 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 1038 Hours	After Every Sample	>	.5	2	3	Agent Virtual Memory Growth is %value%%%

42.1.8.2 Data Source

The source of the raw information is the UNIX ps command. From this, we calculate an average over four interval periods and use this as our comparison percentage (that is, how much has the virtual memory usage grown as a percentage of this average.

42.1.8.3 User Action

Specific to your site.

42.2 Response

The Response metric reports on the availability of the Management Agent.

42.2.1 Status

This metric has a value of 1 if the Management Agent is up and running.

42.2.1.1 Metric Summary

Table 42-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 168 Hours	After Every Sample	=	Not Defined	0	1	Not Defined

42.2.1.2 Data Source

Not applicable.

42.2.1.3 User Action

If the value of this metric is not 1, the Management Agent is down and contact with the Management Agent will not exist. In such situations, the Management Agent may need to be restarted.

42.3 Upload Statistics

The Upload Statistics metrics present information on the state of the upload manager and its performance.

42.3.1 Last Successful Upload

Displays the last time an attempt was made to upload data to the repository and this attempt was successful.

42.3.1.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 62 Minutes

42.3.1.2 Data Source

The source of this metric is the Management Agent itself.

42.3.1.3 User Action

If the difference between this time and the current time is big, then there is likely to be a problem uploading data to the repository. This may be due to a bad network or problems on the repository end. Check the emd.trc file in the log directory for upload messages.

42.3.2 Number of Files to Upload

This metric shows the number of XML files that are in the $ORACLE_HOME/sysman/emd/upload directory waiting to be uploaded to the repository.

42.3.2.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 62 Minutes

42.3.2.2 Data Source

The source of this information is the Management Agent itself.

42.3.2.3 User Action

A large number of files in this directory probably indicates that there is a problem uploading files to the repository. Check the emd.trc file for upload errors and act appropriately. The cause may also be a bad network or problems on the repository end.

42.3.3 Size of Files to Upload (MB)

The Size of Files to Upload metric presents the sum of the sizes of all XML files in the upload directory of the Management Agent.

42.3.3.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 62 Minutes

42.3.3.2 Data Source

The source of this information is the Management Agent itself.

42.3.3.3 User Action

If this metric is large, check the upload directory. If this directory has very few files, it may be they are large. If it has many files, there may be a problem uploading data to the repository. This may be due to a bad network, bad repository or Management Agent. Check the emd.trc file in the log directory for upload error messages.

42.3.4 Upload Rate (KB/sec)

The upload rate is the average rate in KB/sec at which data is uploaded to the repository.

42.3.4.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 62 Minutes

42.3.4.2 Data Source

The source of this information is the Management Agent itself.

42.3.4.3 User Action

If the rate is zero or close to zero, there may be problems uploading data or collecting data (because if collections stop for some reason, we have nothing to upload). Check the log files for collection and upload messages.

42.4 User Identification

These metrics provide information about the user running the Management Agent.

42.4.1 Group Name

The name of the group the Management Agent is running under.

42.4.1.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 168 Hours

42.4.1.2 Data Source

The source of this metric is the UNIX id command.

42.4.1.3 User Action

Specific to your site.

42.4.2 Location

The Location metric shows the directory home of the Management Agent.

42.4.2.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 168 Hours

42.4.2.2 Data Source

The source of this information is the ORACLE_HOME environment variable.

42.4.2.3 User Action

Specific to your site.

42.4.3 Other Groups

This metric lists the other groups the Management Agent user belongs to.

42.4.3.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 168 Hours

42.4.3.2 Data Source

The source of this metric is the UNIX "id" command.

42.4.3.3 User Action

Specific to your site.

42.4.4 User Name

The User Name metric provides information on the user that started the Management Agent process.

42.4.4.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 168 Hours

42.4.4.2 Data Source

The source of this data is the UNIX id command.

42.4.4.3 User Action

Specific to your site.

42.5 User Limit Info

The metrics in the User Limit Info category provide information about the system resources available to the Management Agent.

42.5.1 CoreDump (blocks)

The CoreDump metric shows the maximum size of a core dump file in 512 Kbytes blocks. A value of unlimited means that the only limit is the file system limit.

42.5.1.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 168 Hours

42.5.1.2 Data Source

The source of this information is the UNIX ulimit command.

42.5.1.3 User Action

This metric shows the maximum size (in 512 Kbyte blocks) of a core dump file. To decrease or increase this limit, use the UNIX ulimit system command.

42.5.2 Data (kbytes)

This metric shows the maximum size of the Management Agent's heap in Kbytes.

42.5.2.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 168 Hours

42.5.2.2 Data Source

The source for this information is the UNIX ulimit system command.

42.5.2.3 User Action

This metric shows the maximum heap size (in kbytes) made available to the Management Agent. To decrease or increase this limit, use the UNIX ulimit system command.

42.5.3 File (blocks)

The File metric lets you know the size of the largest single file allowed by the system the Management Agent is running on. The unit is 512 Kbyte blocks. A value of "unlimited" means that the limit is the file system limit.

42.5.3.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 168 Hours

42.5.3.2 Data Source

The source for this information is the UNIX ulimit system command.

42.5.3.3 User Action

This metric shows the maximum file size (in blocks) allowed by the system that the Management Agent is running on. To decrease or increase this limit, use the UNIX ulimit system command.

42.5.4 NoFiles (descriptors)

The NoFiles metric shows the maximum number of file descriptors that the process can have.

42.5.4.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 168 Hours

42.5.4.2 Data Source

The source of this information is the UNIX system call ulimit.

42.5.4.3 User Action

If this limit is small (compared to the operating system maximum), it can be changed for the Management Agent process.

42.5.5 Stack (kbytes)

This metric displays the maximum size of the Management Agent's stack in Kbytes.

42.5.5.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 168 Hours

42.5.5.2 Data Source

The source for this information is the UNIX ulimit command.

42.5.5.3 User Action

This metric shows the maximum size (in kbytes) of the Management Agent's stack. To decrease or increase this limit, use the UNIX ulimit system command.

42.5.6 Time (seconds)

The time metric represents, in seconds, the maximum CPU seconds made available to the Management Agent process by the system it is running on. A value of "unlimited" means that the CPU time available to the Management Agent is unrestricted.

42.5.6.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 168 Hours

42.5.6.2 Data Source

This information is obtained using the UNIX ulimit system command.

42.5.6.3 User Action

This metric shows the maximum CPU time (in seconds) made available to the Management Agent. To decrease or increase this limit, use the UNIX ulimit system command.

42.5.7 Virtual Mem (kbytes)

The Virtual Mem metric shows the maximum virtual memory size that can be occupied by the Management Agent process. If this value is "unlimited" then the only limit is the operating system limit.

42.5.7.1 Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 168 Hours

42.5.7.2 Data Source

The source of this information is the UNIX ulimit system command.

42.5.7.3 User Action

If the value of the Virtual Mem metric is too high or too low, you can change the restriction on virtual memory use by the Management Agent process using the limit UNIX command.