EM은 어려워~
1. <OMS_HOME>/opmn/log: These log files contain the entries for the execution and usage of the OPMN and OPMN-managed processes. The files are described below:
2. <OMS_HOME>/sysman/log: contains the log / trace entries generated during the OMS startup. This will include the details for the repository connection issues. The files updated at startup time are:
For details about troubleshooting the OMS Process Control, refer to:
Note 730308.1: How to Troubleshoot Process Control (start, stop, check status) the 10g Oracle Management Service(OMS) Component in 10 Enterprise Manager Grid Control
Log / Trace files Generated during the OMS Startup
When any of the above methods are used for the OMS startup, the log/trace files will get generated in the following directories:1. <OMS_HOME>/opmn/log: These log files contain the entries for the execution and usage of the OPMN and OPMN-managed processes. The files are described below:
| Log file name | Description |
| ipm.log | Tracks command execution and operation progress of the Process Monitor (PM) portion of the OPMN |
| ons.log | Tracks the execution of the ONS portion of OPMN which is initialized before PM and hence is useful for early OPMN errors. |
| OC4J~home~default_island~1 | Tracks the startup and shutdown of the OC4J home application server component. |
| HTTP_Server~1 | Tracks the startup and shutdown of the HTTP_Server application server component. |
| OC4J~OC4J_EM~default_island~1 | Tracks the startup and shutdown of the OC4J_EM (OMS) application server component. |
| OC4J~OC4J_EMPROV~default_island~1 | Tracks the startup and shutdown of the OC4J_EMPROV application server component. |
| OC4J~OCMRepeater~default_island~1 | Tracks the startup and shutdown of the OCMRepeater application server component. |
| WebCache~WebCache~1 | Tracks the startup and shutdown of the WebCache application server component. |
| WebCache~WebCacheAdmin~1 | Tracks the startup and shutdown of the WebCacheAdmin application server component. |
| opmn.log | Contains output generated by OPMN when the ipm.log and ons.log files are not available. |
| service.log | (on Microsoft Windows only). The service.log displays any error messages generated by OPMN services while interacting with service control manager. |
2. <OMS_HOME>/sysman/log: contains the log / trace entries generated during the OMS startup. This will include the details for the repository connection issues. The files updated at startup time are:
| Log / Trace file name | Description |
| emctl.log | Tracks log messages from the emctl utility. |
| emoms.log | Log messages from the OMS application. By default, the maximum size is set to 20MB after which the file is rotated. |
| emoms.trc | Trace messages from the OMS application. By default, the maximum size is set to 5MB with an index of 10, for file rotation. |
For details about troubleshooting the OMS Process Control, refer to:
Note 730308.1: How to Troubleshoot Process Control (start, stop, check status) the 10g Oracle Management Service(OMS) Component in 10 Enterprise Manager Grid Control
참고:
How to Process Control (start, stop, check status) the 10g Oracle Management Service(OMS)? (Doc ID 298991.1)
Master Note for 10g Grid Control OMS Performance Issues (Doc ID 1161003.1)
How to Process Control (start, stop, check status) the 10g Oracle Management Service(OMS)? (Doc ID 298991.1)
Master Note for 10g Grid Control OMS Performance Issues (Doc ID 1161003.1)