Re: How to recreate this file: emd. Or Are you getting any issue while creating dbconsole? Babu Report message to a moderator. I've been recreating the OEM dbconsole Jul 19, PM oracle. TargetListException: No targets. Thanks again. Post complete emca log details Babu Report message to a moderator. Thank you. Tue, 20 July Use the information in Table to locate and modify the Agent logging and tracing properties in the emd.
This makes it easier to identify the process ID of the Management Agent you are monitoring. When the Agent log file reaches this size in kilobytes , the Management Agent copies the logging data to a new rollover file and creates a new emagent.
By the default, the Agent will rollover the log file four times before it deletes any logging data. The number of rollover files is controlled by this property.
When the Agent trace file reach this size in kilobytes , the Management Agent copies the logging data to a new rollover file and creates a new emagent. By the default, the Agent will rollover the trace file four times before it deletes any tracing data.
To modify the amount of information save d in the Management Agent trace file:. Open the emd. Each of these properties controls the level of logging detail for the various subcomponents of the Management Agent. Modify the amount of information that is included in the trace file by replacing the WARN value for each property to one of the values shown in Table Include only critical errors in the trace file.
This setting generates the least amount of tracing data. The trace file will likely grow at a relatively slow rate when you select this logging level. Include debugging information, as well as informational tracing, warning, and critical errors. This setting generates the greatest amount of tracing data. Note: The trace file will likely grow at a relatively fast rate when you select this logging level.
Like the Management Agent log and trace files, the Management Agent fetchlet log and trace files are designed to reach a maximum size before the Management Agent renames or rolls the information to a new file name and starts a new log or trace file. To control the maximum size of the Management Agent fetchlet log and trace files, as well as the number of rollover files:. Open the emagentlogging. When the fetchlet log file reaches this size, the Management Agent copies the logging data to a new rollover file and creates a new emagentfetchlet.
This optional property indicates how many times the Management Agent will rollover the fetchlet log file to a new file name before deleting logging data. Note: Because the log file does not contain as much data as the trace file, it is usually not necessary to create more than one rollover file.
As a result, this entry is not included in the properties file by default. When the fetchlet trace file reaches this size, the Management Agent copies the logging data to a new rollover file and creates a new emagentfetchlet. This property indicates how many times the Management Agent will rollover the trace file to a new file name before deleting tracing data.
By default, the Management Agent will save all critical and warning messages generated by the Management Agent fetchlets to the emagentfetchlet. However, you can adjust the amount of logging information that the fetchlets generate. Change the value of the log4j. OMS log and trace files store important information that support personnel can later use to troubleshoot problems. OMS uses the following six types of log files:.
Oracle Management Service log file emoms. OMS saves information to the log file when it performs an action such as starting or stopping or when it generates an error. The information is saved to emctl. Oracle Management Service trace file emoms. OMS trace file provides an advanced method of troubleshooting that can provide support personnel with even more information about what actions the OMS was performing when a particular problem occurred.
The errors generated during the virtualization of an Enterprise Manager is saved into the emovm log file. The Virtualization Management Pack trace file provides an advanced method of troubleshooting.
Support personnel can use them for debugging the errors related to virtualization operation of an Enterprise Manager. OMS log and trace files increases in size over time as information is written to the files.
However, the files are designed to reach a maximum size. When the files reach the predefined maximum size, the OMS renames or rolls the logging information to a new file name and starts a new log or trace file. This process keeps the log and trace files from growing too large. As a result, you will often see multiple log and trace files in the OMS log directory.
To control the maximum size of the OMS log and OMS trace files, as well as the number of rollover files, run the following command, and specify details as described in Table :. The watchdog process is controlled by the emwd script located in the following directory of the Management Agent home directory:. In today's global economy, it is not uncommon for the systems you manage to reside in multiple locations throughout the world. As Enterprise Manager collects monitoring data from Management Agents running on these remote systems, it is important that the data is correlated accurately.
A software failure on a machine in Ontario, Canada might be the cause of a performance problem on a machine in Hoboken, New Jersey. To correlate this data, it is important that Enterprise Manager obtains the correct time zone for each Management Agent that you install. The following sections describe how the Management Agent obtains the time zone and how to correct the problem if the time zone for a Management Agent is incorrect:. When you install the Management Agent, the software attempts to obtain the current time zone of the host computer.
If successful, the installation procedure updates the agentTZRegion property setting in the following configuration file:. The agentTZRegion property can be set to any of the values listed in the following file, which is installed in the Management Agent home directory:. Sometimes, during the Management Agent installation, the time zone detected by the Agent configuration tool is not recognized by the Management Agent. In other words, the time zone obtained by the configuration tool is not listed in the Management Agent list of supported time zones.
This problem prevents the Management Agent from starting and results in the an error similar to the following:. This error appears in one of the log files shown in Table , depending upon which Enterprise Manager product you are using. Enter the following command in the Management Agent home directory to identify the time zone currently being used by the host computer:. Browse the contents of the supportedtzs.
Set the value of this property to the time zone you identified as closest the host time zone in the supportedtzs. You should now be able to start the Management Agent without generating the error in the log file. Section 7. Similar problems can occur when the Management Agent finds the correct time zone, but the time zone is not recognized by the the Management Service or the database where the Management Repository resides.
When the Management Service does not recognize the time zone established by the Management Agent, Enterprise Manager generates the following error:. Restart the Management Repository database using the more extensive list of time zones in the timezlrg. Specify a new time zone for the Management Agent that the Management Repository database will recognize. The following sections describe configuration changes you can make to the Management Service after you install Enterprise Manager:.
When you install and deploy the Management Service, you associate the Management Service with a Management Repository. The Management Service uses the database host, database system identifier SID , database port, management user, and management password to identify and communicate with the Repository. This repository information is stored in the emoms. The following sections describe how to modify the repository information in the emoms.
To associate the Oracle Management Service with a new repository, you must modify the repository properties saved in the emoms. Locate the emoms.
0コメント