on 07-31-2014 12:06 PM
Hello All,
I am doing system copy of java installation. During EXport from Java datase, I get this error:
Joload.log file:
Error during export of DAV_CONTENTSTORE
java.lang.OutOfMemoryError: Java heap space (failed to allocate 4944 bytes)
I have Java parameter for this system:
-Xms2048M
-XX:MaxNewSize=600M
-XX:NewSize=600M
-XX:MaxPermSize=1024M
-XX:PermSize=1024M
I have seen SAP note 942766 but no help from that..
Any idea thanks for any help.
Reza
Hello Reza
Modify the control.xml with a higher value for heap and restart sapinst.
Refer this SAP note for assistance.
1173398 - jload export fails with OutOfMemoryException
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes please.
You can also refer this SAP note as it suggests to change var maxHeap size.
1768708 - Error "java.lang.OutOfMemoryError: Java heap space" during the export
Also can you attach the control.xml file please ?
Regards
RB
That is :
}
NW.trace("jmigmon call args: ", jmigmon_callArgs.join());
var jloadHeap = "-Xmx2048m";
if (installer.getInstallationParameter("INSTPARA_PRODUCT") == "BPP") {
jloadHeap = "-Xmx2048m";
}
//for mss we need more...
//case "BPP" is covered by the general coding...
if (this.getDBType().toString().toLowerCase() == NWDB.mss &&
If you have a 64 bit system then 2048 MB is the one to be set and reducing the heap will not help you.
1603093 - SAP JVM 4.1 parameters NetWeaver 2004 and 7.0
If the JDBC drivers are outdated then this can happen.
Open the the control.xml file and check for this entry.
var jloadHeap = "-Xmx2048m";
if (installer.getInstallationParameter("INSTPARA_PRODUCT") == "BPP") {
jloadHeap = "-Xmx2048m";
}
//for mss we need more...
//case "BPP" is covered by the general coding...
if (this.getDBType().toString().toLowerCase() == NWDB.mss && installer.getInstallationParameter("INSTPARA_PRODUCT") != "BPP") {
jloadHeap = "-Xmx2048m";
installer.writeTrace("MSSTRC: changed \"jmigmonHeap\" for mss to... " + jloadHeap.toString());
Try to put all of them in 2048 and restart sapinst.
Regards
RB
Still the same :
for ( var i1 = 0; i1 < this.JloadOption.length; ++i1 )
{
jmigmon_callArgs.push( this.JloadOption[ i1 ] );
}
NW.trace("jmigmon call args: ", jmigmon_callArgs.join());
var jloadHeap = "-Xmx2048";
if (installer.getInstallationParameter("INSTPARA_PRODUCT") == "BPP") {
jloadHeap = "-Xmx2048m";
}
//for mss we need more...
//case "BPP" is covered by the general coding...
if (this.getDBType().toString().toLowerCase() == NWDB.mss && installer.getInstallationParameter("INSTPARA_PRODUCT") != "BPP") {
jloadHeap = "-Xmx2048";
installer.writeTrace("MSSTRC: changed \"jmigmonHeap\" for mss to... " + jloadHeap.toString());
}
Thanks
Reza
If you check this note: 1276704 - jload export fails with java.lang.OutOfMemoryError
It says
For the duration of the export we recommend to extend the URL of the export datasource by the property
responseBuffering=adaptive
Use configtool to do so.
This should avoid the memory problems.
After the export is done switch back to the original URL again.
Example:
original URL:
jdbc:sqlserver://PWDF6636:1433;databasename=BIG
changed URL: jdbc:sqlserver://PWDF6636:1433;databasename=BIG;responseBuffering=adaptive
Usage of configtool:
The configtool is normally located on $(DIR_INSTANCE)\j2ee\configtool
(for example: c:\usr\sap\<SID>\J<nn>\j2ee\configtool).
To start it, execute configtool.bat.
In the emerging popup, after the connect, click on "secure store".
The URL to change can be either directly modified in the "Secure Store Data" tab or the "Connection Pools" tab.
Edit this entry by double-clicking the URL-line and changing the value in the "Value:" line. Save by hitting "Add".
Save the setting by File->Apply Changes or hitting the floppy icon.
You just have to add ;responseBuffering=adaptive and the end of URL.
Now with this parameters the JDBC driver buffers only the amount of data that it needs for the go.
Set this, stop inst and restart again.
If this is not working try with selectMethod=direct in place of responseBuffering parameter.
If this is not working
Divyanshu
Hello,
Thanks for help, after i change the url i could be finish with this System export, but I have 25 GB data on DB system and the size of system copy is just 5 GB. I thing the system copy had di not take all DB data.
Is it possible from 25 DB data from source system the copy data is just 5 GB?
Thanks again Reza
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.