Streamlining Debug Logging for Workflow Components to Improve Performance
Last updated on OCTOBER 13, 2016
Applies to:Oracle Workflow - Version 188.8.131.52 to 12.2 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.
Log levels which are set too high can cause issues at several stages in the workflow area. Timeout related errors are often seen when the service component can not open large files on slowly responding systems. In particular, STATEMENT level logging causes gigantic logs and can often obfuscate original errors.
Do not increase the logging level of your system unless you are actively diagnosing an issue with that component. Maintain the log disk spaces to ensure there is plenty of room to archive necessary files.
1. Determine the current logging level of the Mailer and the agent listeners
2. Set the logging level to default levels for best performance:
3. Bounce (stop & start) the workflow service containers (ie Workflow Agent Listener Service, Workflow Mailer Service, Workflow Document Web Services Service) to generate a new log files.
Bouncing the individual workflow components (ie Workflow Notification Mailer, Workflow Java Error Agent Listener, Workflow Deferred Agent Listener, Web Services OUT Agent, etc) will only append to the existing log file.
Verify the current Active Workflow Services Log files using :
select fcq.concurrent_queue_name, fcp.last_update_date,
FROM fnd_concurrent_queues fcq, fnd_concurrent_processes fcp, fnd_lookups flkup
WHERE fcq.concurrent_queue_name in ('WFMLRSVC','WFALSNRSVC','WFWSSVC')
AND fcq.concurrent_queue_id = fcp.concurrent_queue_id
AND fcq.application_id = fcp.queue_application_id
AND lookup_type ='CP_PROCESS_STATUS_CODE'
4. Archive and maintain the $APPLCSF/$APPLLOG space to maintain best performance:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms