1、确定当前系统可以设置的最大值：
Below command will help you to identify the maximum memory heap size than can be allocated to a JVM process.
java -mx[value]m -version
Start with a higher value like 4G or higher and slowly cut down to the maximum allowed value.
举例：
$ java -mx4096m -version
Invalid maximum heap size: -Xmx4096m
The specified size exceeds the maximum representable size.
Could not create the Java virtual machine.
$ java -mx4096m -version
[ERROR] Specified maximum heap size (4GB) is larger than the address space on this platform (4 GB).
Could not create the Java virtual machine.
从上面就知道本系统支持不了4g的大小。
Now lets reduce to a lesser value, viz., 3Gig
$ java -mx3072m -version
java version “1.5.0.04″
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.04-_27_jul_2006_10_52)
Java HotSpot(TM) Server VM (build 1.5.0.04 jinteg:07.27.06-16:18 IA64, mixed mode)
现在可以知道，3g大小是可以支持的。
2、设置java Heap大小的步骤：
First, you need to identify how much is the maximum heap size that you can set. Click here.
Once you had identified the maximum heap size, we need to change the configuration files to make it
permanent.
Step 1: Edit opmn.xml file.
Location : $INST_TOP/ora/10.1.3/opmn/conf/
Open opmn.xml
Search for string Xms or Xmx or module-id=”OC4J”
This search should lead you to below location
‘<’process-type id=”oacore” module-id=”OC4J” status=”enabled” working-dir=”$ORACLE_HOME/j2ee/home”‘>’
‘<’category id=”start-parameters”‘>’
‘<’data id=”java-options” value=”-server -verbose:gc -Xmx512M -Xms128M ……]
The default value for Maximum (-Xmx) and Minimum (-Xms) heap sizes are 512M and 128M respectively.
Again here you have options, you can set both Xms and Xmx has the same value as Xmx if you feel all your sessoins require higher memory or set a lower value for Xms and the maximum value for Xmx. Dont forget to change the values under ‘<’category id=”stop-parameters”‘>’
opmn.xml also contains jvm configurations for other components – oafm & forms.
Step 2: Edit oc4j.properties file.
Location : ($INST_TOP/ora/10.1.3/j2ee/oacore/config)
This step is optional since we had already made changes in opmn.xml but there is no harm in making the change here. This step will come handy for troubleshooting specific components of
Oracle viz., configurator, iSupplier or any other option which heavily utilizes/consumes CPU/memory.
Search for string Xms or Xmx or wrapper.
Option 1: If you find any of the above parameters change the values corresponding to the value you had mentioned in opmn.xml or
even more than that, as long as you dont exceed the maximum heap size limit.
Option 2: If you DO NOT find any of the above parameters, then make an entry like this, under the heading “# Java Object Cache Configuration Parameters”
wrapper.bin.parameters=-Xms[Value]M -Xmx[Value]M -XX:NewSize=256M -XX:MaxNewSize=256M
Step 3: Edit Applications Context file
vi $CONTEXT_FILE
Location: $INST_TOP/appl/admin/SID_hostname.xml
search for string s_oacore_jvm_start_options
Change Xms and Xmx value. Repeat the same step for parameter s_oacore_jvm_stop_options.
Changes made in Step 3 will take effect the next time you run autoconfig, whereas Step 1 & 2 changes will take effect the next time you bounce opmn services, but the values are not permanent in the sense these will be wiped off next time you run autoconfig.
Yes you can preserve the changes by placing it inbetween Begin and End customizations.
You can also increase the Garbage Collection threads parameter (-XX:ParallelGCThreads) to a higher value if you have JDK 1.5 or more than 2 cpus or more memory. For more information on this you can refer to Metalink Note: 362851 – Guidelines to setup the JVM
in Apps Ebusiness Suite 11i and R12.
cheers,
oraclePitStop.