A quick post from me, if you running a 11.1.2.2 compact deployment and in particular planning then you may experience performance degradation due to the default ODL logging level setting.
In most circumstances a compact deployment will be used in a Dev, POC, cloud, personal laptop type scenario and the last thing you need is any type of performance issues so updating the logging level is worth implementing.
There is a file called logging.xml which controls the ODL logging parameters and the logging level for all the deployments in the compact managed server.
The file is located in
<MIDDLEWARE_HOME>\user_projects\domains\EPMSystem\fmwconfig\servers\EPMServer0
EPMServer0 is the default managed server name for a compact deployment.
Edit the file and locate the handler name “epmcss-handler”, the logging level is set to a high value of “NOTIFICATION:32” and controls SharedServices_SecurityClient.log
The definition of the most common types of logging levels is as follows
All logs for the compact managed server are located at
<MIDDLEWARE_HOME>\user_projects\domains\EPMSystem\servers\EPMServer0\logs
Update the logger level from “NOTIFICATION:32” to a level 1 type such as “WARNING:1”
Next locate the hander name of “epmreg-handler” which controls registry.log
Update the logger level from “NOTIFICATION:32” to a level 1 type such as “WARNING:1”
Restart the EPMServer managed server and the new logging levels will have taken effect, If at any point an extra degree of logging is required for diagnostics then the level can be updated again.
In most circumstances a compact deployment will be used in a Dev, POC, cloud, personal laptop type scenario and the last thing you need is any type of performance issues so updating the logging level is worth implementing.
There is a file called logging.xml which controls the ODL logging parameters and the logging level for all the deployments in the compact managed server.
The file is located in
<MIDDLEWARE_HOME>\user_projects\domains\EPMSystem\fmwconfig\servers\EPMServer0
EPMServer0 is the default managed server name for a compact deployment.
Edit the file and locate the handler name “epmcss-handler”, the logging level is set to a high value of “NOTIFICATION:32” and controls SharedServices_SecurityClient.log
The definition of the most common types of logging levels is as follows
| Message Type | Level | Description |
| INCIDENT_ERROR | 1 | A serious problem that may be caused by a bug in the product and that should be reported to Oracle Support. Examples are errors from which you cannot recover or serious problems. |
| ERROR | 1 | A serious problem that requires immediate attention from the administrator and is not caused by a bug in the product. |
| WARNING | 1 | A potential problem that should be reviewed by the administrator. |
| NOTIFICATION | 1 | A major lifecycle event such as the activation or deactivation of a primary sub-component or feature. This is the default level for NOTIFICATION. |
| NOTIFICATION | 16 | A finer level of granularity for reporting normal events. |
| TRACE | 1 | Trace or debug information for events that are meaningful to administrators |
| TRACE | 16 | Detailed trace or debug information that can help Oracle Support diagnose problems with a particular subsystem |
| TRACE | 32 | Very detailed trace or debug information that can help Oracle Support diagnose problems with a particular subsystem |
All logs for the compact managed server are located at
<MIDDLEWARE_HOME>\user_projects\domains\EPMSystem\servers\EPMServer0\logs
Update the logger level from “NOTIFICATION:32” to a level 1 type such as “WARNING:1”
Next locate the hander name of “epmreg-handler” which controls registry.log
Update the logger level from “NOTIFICATION:32” to a level 1 type such as “WARNING:1”
Restart the EPMServer managed server and the new logging levels will have taken effect, If at any point an extra degree of logging is required for diagnostics then the level can be updated again.
Some good information there and also some options I did not know about before! Good post :)
ReplyDelete