EBS JVM 内存优化攻略

oacore

[applmgr@appshost01 scripts]$ cd $ADMIN_SCRIPTS_HOME
[applmgr@appshost01 scripts]$ ./adoacorectl.sh status | grep "OC4J:oacore" | awk -F"|" '{print $3}' | while read L ; do ps -fp $L | grep -v PID ; done | awk -F"-X" '{print $2 $3}'
mx512M ms128M
mx512M ms128M
[applmgr@appshost01 scripts]$

[applmgr@appshost01 scripts]$ grep s_oacore_jvm_start_options $CONTEXT_FILE
         ... -server -verbose:gc -Xmx2048M -Xms1024M ...
[applmgr@appshost01 scripts]$

CONTEX_FILE 位置 ： s_oacore_jvm_start_options

或者修改 vi $ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml （临时策略）

form

s_forms_jvm_start_options

oafm

s_oafm_jvm_start_options

opp

Option 1, patching

12i Environments:

1. Please download,review and apply Patch 7687414 in a test environment.
2. Please retest the issue.
3. If the issue is resolved, please migrate the solution as appropriate to other environments.

Option 2, Increase the maximum Java heap size for the OPP to 1024MB (1GB):

Determine what the heap size per OPP process is currently:

select DEVELOPER_PARAMETERS from FND_CP_SERVICES
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = ‘FNDCPOPP’);
-The default should be:

J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m
3. Increase the Heap Space per Process to 1024:

update FND_CP_SERVICES
set DEVELOPER_PARAMETERS =
‘J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m‘
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = ‘FNDCPOPP’);
OR

1. Log into applications with the System Administrator responsibility.
2. Navigate to Concurrent -> Program -> Define
3. Query the XML Publisher Template Re-Generator program
4. Set the following value for the Executable Options : -Xmx1024m
5. Save changes.
6. Retest the program.
   The OPP queue can be Recreated the using $FND_TOP/patch/115/sql/afopp002.sql file as ‘APPLSYS’ user. On running the script you will be prompted for username and password.
   Option 3, Check timeout settings.
   There are two new profiles options that can be used to control the timeouts:
   Profile Option : Concurrent:OPP Response Timeout Internal Name : CONC_PP_RESPONSE_TIMEOUT Description : Specifies the amount of time a manager waits for OPP to respond to its request for post processing.
   Profile Option : Concurrent:OPP Process Timeout Internal Name : CONC_PP_PROCESS_TIMEOUT Description : Specifies the amount of time the manager waits for the OPP to actually process the request.
   Option 4, Configure the XML Publisher Administrator Configuration settings.
   Note: Reports built with large images will require additional space. So please insure there is adequate temp space and your code is optimized when running large reports/templates.
7. As XML Publisher Administrator navigate to Administration->Configuration.
8. Under Temporary Directory pick a temporary file location on your concurrent processing node. This should be at least 5GB or 20x larger than largest XML data file you generate
9. Under FO Processing, set:
   o Use XML Publisher’s XSLT processor set to True
   o Enable scalable feature of XSLT processor set to False
   o Enable XSLT runtime optimization set to True
   Bounce OPP processes.
   Additional Info: Review below Meta link Documents.
   Doc ID 1268217.1
   Doc ID 862644.1]
   Doc ID 1266368.1
   Doc ID 427233.1
   Doc ID 352518.1
   Doc ID 978495.1

参考资料

JVM: Guidelines to Setup the Java Virtual Machine in E-Business Suite 11i and R12 (Doc ID 362851.1)
https://www.cnblogs.com/erpdog/articles/6587099.html