Concurrent manager become up after 3-4 hours after start Oracle Application.

Description:
These two tables FND_ENV_CONTEXT FND_CONCURRENT_REQUESTS grown to 4 GB size . To speed up.

Solution:
1. First Purge and then De-fragmentation to improve the performance of the DML fired on FND_CONCURRENT tables.

Refer Note 1057802.1 for more details.

1.1. Truncation of FND_ENV_CONTEXT

1.1.1. Take a backup of FND_ENV_CONTEXT

1.1.2. Shutdown concurrent manager

1.1.3. Truncate FND_ENV_CONTEXT

1.2. Defragment the tables below to reclaim unused space / improve performance

FND_CONCURRENT_REQUESTS
FND_CONCURRENT_PROCESSES
FND_CRM_HISTORY
FND_TEMP_FILES
FND_LOG_TRANSACTION_CONTEXT

Refer Note 1057802.1 for more details (how to defragment)

2. Start the concurrent manager

Monitor AQ$ tables as well.

The AQ$_FND_CP_GSM_OPP_AQTBL_H is a history table.Ensure you purge at regular interval.

select count(*) from AQ$_FND_CP_GSM_OPP_AQTBL_H;

If the table is grown, then one can purge using DBMS_AQADM.PURGE_QUEUE_TABLE. Refer to: ( Doc ID 1156523.1 )

Tuning Output Post Processor (OPP) to Improve Performance ( Doc ID 1399454.1 )