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 ) 

Guest user/pwd does not exist or match: GUEST/ORACLE1 In Oracle apps R12

Please perform the below steps.

1. Shutdown the EBS services.

2. The only supported way to change the Guest user password is to update the context variable s_guest_pass and run AutoConfig, which runs the AdminAppServer utility internally.

Check your context file for variable s_guest_pass, ensure it has the value ORACLE1 set, if its not set then you need to set it manually.

Note : Restriction on the GUEST User Password : The GUEST User password cannot include the special character "#".

3. Run autoconfig on DB Node and then application node.

4. Execute the below sql again:

select fnd_web_sec.validate_password('GUEST','ORACLE') from dual;

Check whether query output is showing Y.

If no, Please check whether the below error is seen on autoconfig log:

Unable to update GUEST_USER_PWD in database to GUEST/ORACLE - Password was not changed, this point to the DB parameter JAVA_JIT_ENABLED which is set as TRUE.

5. On 11g DB you need to have the below settings for EBS specifically, run the below sql

alter system set JAVA_JIT_ENABLED= FALSE scope = both;

6. Follow the steps 2 and 3 again.

7. Run the below command:

perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile --flush -p 2

7. Check whether the compile completed successfully.

8. Restart the application services.

9. Retest the issue.