Managing Logging for Oracle Enterprise Scheduler

You can search for and view log data for individual job requests, as well as set log levels for Oracle Enterprise Scheduler. You can also save job request logs to a file, and trace job requests for additional troubleshooting information.

This section contains the following topics:

Note:

The Oracle WebLogic Server logger (logging.xml) only shows logs written by Oracle Enterprise Scheduler job running in Oracle WebLogic Server. After Oracle Enterprise Scheduler transfers control of running PL/SQL to the PL/SQL process, PL/SQL job logging data is not written to the Oracle Enterprise Scheduler logs as they run in a separate process.

Note:

The procedures in this section assume that your log information is stored in the file system. When you select a job, the View Log Messages button is active. If instead, your log information is stored in a Universal Content Management (UCM) repository, the button is not active and you access the log by clicking on the fnd:attachment component.

Viewing Log Information for the Domain

You can use the Fusion Middleware Control to view log messages for the domain on which Oracle Enterprise Scheduler is deployed.

To view domain logs:

  • From the Scheduling Service menu, select Logs > View Log Messages.

For more information, see the Oracle Fusion Middleware Administrator's Guide.

Viewing Job Request Logs

You can view the log for a particular job request from the Request Details pane.

Note:

On Windows, request log output is formatted as a single line without line breaks.

To view job request logs:

  1. Search for the relevant job requests as described in Searching for a Job Request Using Simple Search
  2. In the table displaying the job request search results, select the job request whose log you want to view.
  3. To view job request details, click the job request ID. Alternatively, click the parent ID associated with the job request to view the details of the job set with which the job is associated.
  4. In the job request details page, select Action and then select Request Log to display log information for the job request.

Viewing Log Messages for Scheduled Job Requests

You can use the Oracle Enterprise Scheduler log messages page to view logging information regarding scheduled job requests.

To view log messages for scheduled job requests with Fusion Middleware Control:

  1. From the navigation pane, expand the farm, and then Scheduling Services.
  2. Select the ESSAPP application for the appropriate Managed Server.
  3. In the Scheduling Service home page, from the Scheduling Service menu, choose Logs and then select View Log Messages.
  4. Search for the relevant log messages using the Date Range, Message Types and Message fields. You can optionally add additional search fields.
  5. You can use the ECID to retrieve more information about a given job request. The Execution Context ID (ECID) is a global unique identifier of the execution of a particular request in which the originating component participates. You can use the ECID to correlate error messages from different components.
  6. By default, when you view the logs for a request, Fusion Middleware Control displays only messages logged in the scope of the Oracle Enterprise Scheduler cluster. If the Oracle Enterprise Scheduler application is not deployed to a cluster, Fusion Middleware Control displays the messages logged in the managed server scope. However, Oracle Enterprise Scheduler propagates the ECID associated with the job request across sub-systems such as SOA, ADF, and so on.

    To view messages logged by other sub-systems, broaden the target scope to display messages logged across the domain or farm. Click Target Log Files and select the target whose log messages you want to view.

Setting Oracle Enterprise Scheduler Log Levels

It is possible to configure Oracle Enterprise Scheduler server logging for an Oracle WebLogic Server by modifying the logging.xml file of that Oracle WebLogic Server. By default, there is no explicit logger entry for Oracle Enterprise Scheduler. Oracle Enterprise Scheduler inherits the logging level and log handlers configured for the parent logger, typically the oracle logger or the root logger.

By default, the log messages for the Oracle Enterprise Scheduler logger can be found in the Oracle WebLogic Server diagnostic log file for that Oracle WebLogic Server. The logging.xml file is located under DOMAIN_HOME/config/fmwconfig/servers/WebLogic_Server_Name, where DOMAIN_HOME is the domain home directory for the Oracle WebLogic Server domain and WebLogic_Server_Name is the name of the Oracle WebLogic Server that uses the logging.xml file.

Table 6-8 shows the Oracle Enterprise Scheduler logger names, log levels and a description for each level.

Table 6-8 Loggers and log levels for Oracle Enterprise Scheduler

Logger Name Log Level Description

oracle.as.ess

SEVERE

Problems encountered by Oracle Enterprise Scheduler runtime in the context of request processing that result in the request errors. Errors include exceptions thrown by the job code, unchecked exceptions when running the job code and exceptions when running Oracle Enterprise Scheduler code.

Problems encountered by Oracle Enterprise Scheduler runtime outside the context of request processing, such as dispatching, system event handling, and so on.

-

WARNING

Less severe problems encountered by Oracle Enterprise Scheduler runtime during or outside of request processing, which might not cause requests to enter error state.

-

INFO

Messages for request state transitions.

Messages related to work assignment activities.

Messages about batch delete failures.

Start and stop of Oracle Enterprise Scheduler resource adapter.

-

CONFIG

Application endpoint activation and de-activation for Oracle Enterprise Scheduler resource adapter.

  • Request Logging: Oracle Enterprise Scheduler job implementation might write business-specific job request execution log information to the job request log file. This log file is specific to each request, and is automatically enabled by default. For more information about viewing the log file for a job request, see Viewing Job Request Logs.

For information about setting the log levels for Oracle WebLogic Server, see Tracing Oracle Enterprise Scheduler Jobs.

Set the log levels for the Oracle WebLogic Server running Oracle Enterprise Scheduler as described in the Oracle WebLogic Server documentation.

Tracing Oracle Enterprise Scheduler Jobs

Enabling tracing for Oracle Enterprise Scheduler jobs provides additional information regarding job requests, which can then be relayed to Oracle technical support to help solve any Oracle Enterprise Scheduler-related issues.

This section contains the following topics:

Before You Begin

Before enabling tracing, note that tracing log messages may produce a considerable amount of output. By default, traces go to the Oracle WebLogic Server console stdout. If the stdout is re-directed to a file, it may occupy a significant amount of disk space and possibly affect server performance.

To enable tracing for Oracle Enterprise Scheduler jobs, navigate to the Specify Loggers Region:

In the Log Levels tab, from the View dropdown list select Loggers with Persistent Log Level State. Expand the Specify Loggers region toward the bottom of the pane.

  1. In Fusion Middleware Control, in the navigation pane, select WebLogic Domain and then select the domain and server names.

  2. Click the WebLogic Server menu and select Logs and then select Log Configuration.

    The Log Configuration Pane displays.

  3. In the Log Levels tab, from the View dropdown list select Loggers with Persistent Log Level State. Expand the Specify Loggers region toward the bottom of the pane.

  4. Navigate to the Log Configuration pane and expand the Specify Loggers region.

Define the Loggers

Create the following loggers:

  • oracle.as.scheduler.security.internal.SecurityExecutorFactory

  • oracle.as.scheduler.security.internal.SecurityHelper

  1. In the Name text field, enter the name of the logger.

  2. From the Oracle Diagnostic Logging Level (Java Level) dropdown list, select the desired logging level.

  3. Repeat for the second logger name.

Attach the Loggers

Attach the loggers to the Oracle Diagnostic Logging Handler.

  1. In the Log Configuration pane, click the Log Files tab.

  2. From the list of handlers, select odl-handler and click Edit Configuration.

  3. From the Loggers to Associate dropdown list, select the loggers you created and click OK.

Download the Trace File

Download the Trace File

  1. In Fusion Middleware Control, in the navigation pane, select WebLogic Domain and then select the domain and server names.

  2. Click the WebLogic Server menu and select Logs and then select View Log Messages.

    The Log Messages pane displays.

  3. In the Search field, expand the Selected Targets region and select the relevant Oracle Enterprise Scheduler target.

  4. Select the relevant date range, message type and so on, and click Search.

  5. From the list of log messages that displays, select the relevant message.

  6. In the Log File column, click the name of the log file.

    The View Log File pane displays.

  7. Next to the name of the log file, click Download to download the file.

Saving Job Request Logs

It is possible to save job request log data to the server log file. Job request logs are normally stored to Oracle WebCenter Content. However, when setting the log level to FINER, all job request logs are copied to the server log file.

To save job request logs to the server diagnostic file:

  1. In Fusion Middleware Control, in the navigation pane, select WebLogic Domain and then select the domain and server names.
  2. Click the WebLogic Server menu and select Logs and then select Log Configuration.

    The Log Configuration pane displays.

  3. In the Log Configuration pane, click the Log Levels tab.
  4. In the Search text field, search for oracle.as.scheduler. and find the oracle.as.scheduler.security.internal.SecurityExecutorFactory logger.
  5. Set the log level to FINER and click Apply.
  6. Run a diagnostic test, as described in Oracle Fusion Middleware Administrator's Guide. The log messages are now saved to the <server>-diagnostic.log file.

    The logs are saved to the server diagnostic file, <Oracle Enterprise Scheduler server name>-diagnostic.log.