转载自metalink (Doc ID 550615.1)
In this Document
|1. Agent Side Processes |
|2. OMS Side Processes|
|3. Loader Related Parameters in Agent and OMS Configuration Files|
The goal of this document is to provide an overview of the EM 10g Grid Control Loader Process.
The Loader Process is a subsystem of the Grid Control architecture responsible for processing the data collected by Management Agents and uploading it to the Management Server (OMS) and Repository.
The document is aimed at experienced Grid Control Administrators.
You should be familiar with Grid Control concepts, installation, architecture and configuration topics.
The Loader System is responsible for processing the data collected by the agent, and uploading it to the OMS and Repository.
Below you can find a simplified overview of the Loader processes:
1. The Agent stores the data collected and ready to be uploaded in the
2. The Agent uploads the data to the OMS according to specific rules and scheduling
3. The OMS stores the data typically under
4. The OMS sends a response code to the Agent indicating the status of the upload attempt. It may prompt the agent to retry uploading a file if errors were encountered or signal successful processing of the file.
As mentioned above this a simplified version of the process. Let's take a closer look at what happens behind the scenes:
It's worth understanding the contents of the
The files fall into the following categories
Below is a detailed overview of the processes that take place at the Agent side:
Overview of the processes used by the Upload Manager:
|Metadata :||A channel|
|Severity and Blackouts :||B channel|
|Upload-on-fetch Data :||C channel|
|Normal metric data :||D channel|
|External upload on demand:||E channel|
If there are files of a lower category waiting to get uploaded, and a new file of a higher category gets generated, the new file from the higher category will be loaded first.Files pending upload are stored in the
Overview of the Upload Schedule
Once the data has been uploaded by the Agent, the OMS is responsible for processing it and uploading it to the Repository. Below is a high level overview of the processes that take place at the OMS side:
3.1 Agent Side Properties located in the emd.properties configuration file (under
|REPOSITORY_URL||Pointer to the OMS Receiver URL. This is used by the agent to contact the OMS and upload data.|
|UploadFileSize||Maximum size (in Kb) for the XML file to be uploaded to the OMS. Default value is 2048 (2Mb)|
|UploadInterval||Number of minutes to wait before the Agent uploads the XML files to the OMS. Default value is 30 (minutes).|
|UploadMaxBytesXML||Maximum size (in Mb) the upload manager will support in the upload directory before temporarily being disabled. Collections will stop until more free space is available. Default value is 50 (Mb)|
|UploadMaxDiskUsedPct||The maximum amount (in percentages) of disk space that can be used on the EMD filesystem before the metric collection, logging and tracing get disabled.|
|UploadMaxDiskUsedPctFloor||The amount (in percentages) of disk space that can be used on the EMD filesystem before the metric collection, logging and tracing are re-enabled after being disabled previously.|
|UploadMaxNumberXML||The maximum number of files the upload manager will support in the upload directory before temporarily being disabled Default value is 5000.|
|UploadTimeout||Maximum amount of time, in seconds, upload will wait for response from repository before timing out. 0 means infinite. Default value is 1800 (seconds) = 30 minutes.|
|UploadFailBackoffPct||If an upload fails, the agent will backoff by 'UploadFailBackoffPct' percentage more each time for each successive upload failure. For example if the upload is retried at 1 minute, and the next upload attempt fails, the agent will retry again 1 minute and 12 seconds later. Default value is 20 (%).|
|UploadMaxTime||Timeout for uploading a file. The HealthMonitor will abort the EMD process if the UploadManager does not finish uploading one file within this time frame. The unit is in minutes and the default value is 15 (min).|
3.2 OMS Side Properties located in the emoms.properties configuration file (under
|em.loader.maxMetadataThreads||Maximum number of Metadata loader threads the OMS will spawn. Default is 10|
|em.loader.threadPoolSize||Number of threads used for loading data files into the repository. Possible values are in the range of 1 to 10. Default value is 1|
|ReceiveDir||Directory to place the XML files retrieved from the Agents. Default location is $ORACLE_HOME/sysman/recv.|
|em.loader.maxDirectLoadFileSz||This property controls the maximum size in bytes that the loader|
will attempt to load through on direct loads. The default is 5MB (5242880). On a 'big' machine, you might need to increase this. Only increase this parameter when instructed to do so by Oracle Support
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/543979/viewspace-774260/，如需转载，请注明出处，否则将追究法律责任。