OCI Listener timeout

 The default timeout values are:

• 300 seconds for TCP listeners.

• 60 seconds for HTTP listeners.

maximum timeout value is 7200 seconds.

XML Publisher Report Bursting Program taking time to start

 Customer Applied solution from:

XML Publisher Report Bursting Program (XDOBURSTREP) Performance Poor While Initializing ( Doc ID 2300674.1 )
SOLUTION: Replace random with urandom by modifying the Concurrent Program Define Execution Option
--All 5 reports completed in acceptable period of time.

This solution may work to resolve the issue.
However customer should still work on cleaning the out and log files as this situation will result in further issues.
Customer will discuss internally to decide if the purging / moving of the out and log (FSS directory) will occur tonight or
be put on hold until the weekend

-------------------- ACTION PLAN DETAILS BELOW---------------------

Customer Applied solution from:
XML Publisher Report Bursting Program (XDOBURSTREP) Performance Poor While Initializing ( Doc ID 2300674.1 )
SOLUTION: Replace random with urandom by modifying the Concurrent Program Define Execution Option
--All 5 reports completed in acceptable period of time.

(1) Responsibility: System Administrator
(2) Navigate to: Concurrent > Program > Define
(3) Query report
(4) Under "Executable" it shows Name = XDODTEXE
and (Options = NULL) or (Options = -Xms512M -Xmx512M)
(5) Update Options to = -Xms512M -Xmx512M -Djava.security.egd=file:/dev/./urandom
* note the space after -Xmx512M and before -Djava.security
(6) Save.
(7) Test using report that was updated



Action Plan From Here:
====================
Customer Actions:
1. Customer working on cleaning the out and log
Per Doc ID 2603009.1 - Concurrent Processing R12.2 : Too Many Concurrent Requests In Pending Status After Migrating To OCI
-- Log and Out files from concurrent processing in FSS directory needs to be restricted to 50000 records only

* Customer discussing internally to decide if the purging / moving of the out and log (FSS directory) will occur tonight or
be put on hold until the weekend 


2. If performance is still unacceptable, please provide the AWR and analyzer, per earlier action plan as follows
2.1> Generate AWR reports for intervals 20-Sep 13:15:to 13:30 , 13:30 to 13:45 . Generate instance level reports from all RAC instances using awrrpt.sql and addmrpt.sql scripts
2.2> Also run analyzer to check settings :
EBS Database Performance and Statistics Analyzer( Doc ID 2126712.1 )
NOTE: It is important that you review saved output file before uploading.
If you ran the Analyzer as a Concurrent Program, make sure to choose 'Web Page, HTML only' for the 'Save as type'.
Do not save as 'Webpage, complete (*.htm,*.html)' as it will be rejected when uploaded to Support. This applies to all Web browsers.