Downloading Log Files Using Fusion Middleware Control

Managing Log Files and Diagnostic Data 12-17

12.4.2.2 Specifying Log File Rotation Using WLST

To specify log file rotation using WLST, use the configureLogHandler command. You can specify size-based rotation or time-based rotation. For example, to specify that the log files rotate daily and that they are retained for a week, use the following command: configureLogHandlername=odl-handler, rotationFrequency=daily, retentionPeriod=week To specify that the size of a log file does not exceed 5 MB and rotates when it reaches that size, use the following command: configureLogHandlername=odl-handler, maxFileSize=5M

12.4.3 Setting the Level of Information Written to Log Files

You can configure the amount and type of information written to log files by specifying the message type and level. For each message type, possible values for the message level are from 1 lowest severity through 32 highest severity. Some components support only some of the levels for each message type. Generally, you need to specify only the type; you do not need to specify the level. When you specify the type, Oracle Fusion Middleware returns all messages of that type, as well as the messages that have a higher severity. For example, if you set the message type to WARNING, Oracle Fusion Middleware also returns messages of type INCIDENT_ERROR and ERROR. Table 12–3 describes the message types and the most common levels for each type. Table 12–3 Diagnostic Message Types and Level 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. An example is if Oracle Fusion Middleware cannot process a log file, but you can correct the problem by fixing the permissions on the document. WARNING 1 A potential problem that should be reviewed by the administrator. Examples are invalid parameter values or a specified file does not exist. 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, such as public API entry or exit points. TRACE 16 Detailed trace or debug information that can help Oracle Support diagnose problems with a particular subsystem. 12-18 Oracle Fusion Middleware Administrators Guide The default is NOTIFICATION, level 1. The INCIDENT_ERROR, ERROR, WARNING, and NOTIFICATION with level 1 have no performance impact. For other types and levels, note the following: ■ NOTIFICATION, with level 16: Minimal performance impact. ■ TRACE, with level 1: Small performance impact. You can enable this level occasionally on a production environment to debug problems. ■ TRACE, with level 16: High performance impact. This level should not be enabled on a production environment, except on special situations to debug problems. ■ TRACE, with level 32: Very high performance impact. This level should not be enabled in a production environment. It is intended to be used to debug the product on a test or development environment. Table 12–4 shows the log level mappings among ODL format, Oracle WebLogic Server, and Java. You can configure the message levels using Fusion Middleware Control or WLST commands, as described in the following topics: ■ Configuring Message Levels Using Fusion Middleware Control ■ Configuring Message Levels Using WLST TRACE 32 Very detailed trace or debug information that can help Oracle Support diagnose problems with a particular subsystem. Table 12–4 Mapping of Log Levels Among ODL, Oracle WebLogic Server, and Java ODL WebLogic Server Java OFF OFF 2147483647 - OFF INCIDENT_ERROR:1 EMERGENCY 1100 INCIDENT_ERROR:4 EMERGENCY 1090 INCIDENT_ERROR:14 ALERT 1060 INCIDENT_ERROR:24 CRITICAL 1030 ERROR:1 ERROR 1000 - SEVERE ERROR:7 ERROR 980 WARNING:1 WARNING 900 - WARNING WARNING:7 NOTICE 880 NOTIFICATION:1 INFO 800 - INFO NOTIFICATION:16 DEBUG 700 - CONFIG TRACE:1 DEBUG 500 - FINE TRACE:1 DEBUG 495 TRACE:16 TRACE 400 - FINER TRACE:32 TRACE 300 - FINEST TRACE:32 TRACE 295 Table 12–3 Cont. Diagnostic Message Types and Level Message Type Level Description