Health Check Alert: Purge the eligible records from the FND_CONCURRENT_REQUESTS table
(Doc ID 1095625.1)
Last updated on OCTOBER 07, 2017
Applies to:Oracle Application Object Library
Oracle Concurrent Processing - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Information in this document applies to Any Platform,.
Health Check Category:
This document provides a quick reference explaining the following Health Check Alert:
My Oracle Support provides a proactive health check that automatically detects and notifies you of the existence of this issue before it impacts your business. To leverage this proactive support capability, install the Oracle Configuration Manager (OCM). Information on installing the Oracle Configuration Manager can be found on the Collector tab of My Oracle Support. To view the full portfolio of health checks available, see Note 868955.1
Checks if the number of records in the table FND_CONCURRENT_REQUESTS is at a level that can cause performance issues.
If there are more than 500000 records in the FND_CONCURRENT_REQUESTS table, this can cause performance issues with the concurrent processing sub-system. It is recommended to purge the eligible records.
Follow the below steps to run the 'Purge Concurrent Request and/or Manager Data (FNDCPPUR)' concurrent program to purge eligible records from the FND_CONCURRENT_REQUESTS table. Login as System Administrator, navigate to the Requests form and select 'Purge Concurrent Request and/or Manager Data.' See the System Administrator's Guide - Maintenance for more details.
Oracle Applications System Administrator's Guide - Maintenance