Thursday 25 April 2013

How to find OPP log and current maximum Java heap size?



If concurrent program ends in warning due to any OPP service failure, run below sql by passing request id.

The actual error returned by the XML Publisher Core engine is captured in the OPP log file.
One of the easiest way to obtain the OPP log file is to run the below script from the database by providing request_id.

SELECT fcpp.concurrent_request_id req_id, fcp.node_name, fcp.logfile_name
FROM fnd_conc_pp_actions fcpp, fnd_concurrent_processes fcp
WHERE fcpp.processor_id = fcp.concurrent_process_id
AND fcpp.action_type = 6 AND fcpp.concurrent_request_id = &request_id;

===================
SELECT service_id, service_handle, developer_parameters
FROM fnd_cp_services
WHERE service_id = (SELECT manager_type
FROM fnd_concurrent_queues
WHERE concurrent_queue_name = 'FNDCPOPP');


SERVICE_ID SERVICE_
---------- --------
DEVELOPER_PARAMETERS
--------------------------------------------------------------------------------
1080 FNDOPP
J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m

No comments:

Post a Comment