cancel
Showing results for 
Search instead for 
Did you mean: 

Problem during system Copy

Former Member
0 Kudos

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

Accepted Solutions (1)

Accepted Solutions (1)

Reagan
Advisor
Advisor
0 Kudos

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

Former Member
0 Kudos

Hello Reagan,

I had done that but still the same:(

Should I change this  to "var jloadHeap = "-Xmx20480m";" in control.xml file?

Thanks Reza

Reagan
Advisor
Advisor
0 Kudos

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

Former Member
0 Kudos

I did it chang that to 2048 but still the same. I can not attach control.xml file that is to big in ZIP format too.

Thanks Reza

Reagan
Advisor
Advisor
0 Kudos

Stop the SAP system and restart the server.

Start sapinst and check if that helps.

Make sure the control.xml has the correct values.

You can use an xml editor and look for all Heap terms and check their values.

Regards

RB

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Reza,

Can you tell your OS and DB ?

Divyanshu

divyanshu_srivastava3
Active Contributor
0 Kudos
Former Member
0 Kudos

Ok

I will try

Thanks again


Former Member
0 Kudos

Hi Divyanshu,

Thanks,

That is Windows and DB is MSSQL.

THANKS

Reza

divyanshu_srivastava3
Active Contributor
0 Kudos

Then refer the note that I have told you. If this is SQL 2005, then this might work.

Otherwise, increase heap memory.

Stop everything and start again.

Divyanshu

Former Member
0 Kudos

Still the same


Former Member
0 Kudos

The sql server is 2008

The heap memory is :

I have Java  parameter for this system:

-Xms2048M

-XX:MaxNewSize=600M

-XX:NewSize=600M

-XX:MaxPermSize=1024M

-XX:PermSize=1024M

I am going to change that 2048 and see that Works

Thanks

Reza

divyanshu_srivastava3
Active Contributor
0 Kudos

What are the parameters in control.xml ??

That's is what matter's here.

Divyanshu

Former Member
0 Kudos

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 &&

divyanshu_srivastava3
Active Contributor
0 Kudos

How much of memory do you have in your system ?

Can you stop any unwanted process and retry with this phase ?

If you are on JDBC 1.2*, can you update it to version 2 or higher.

Also, did you try with that note ?

Divyanshu

Former Member
0 Kudos

The server have 8 GB RAM and I had  increase heap memory to 200 GB.

I am using Java from SAp E:\usr\sap\DP2\SYS\exe\jvm\NTAMD64\sapjvm_4.1.012\sapjvm_4

Should increas var jloadHeap = "-Xmx2048m"; to 3082?

I have no java install on this server.

Thanks

divyanshu_srivastava3
Active Contributor
0 Kudos

Make it 1536 MB and try start again.

Making it 3 gigs, not sure how can that help.

Stop Everything. Restart.

Upload new jload.log and jload.java

Divyanshu

Former Member
0 Kudos

I will try that,

Thanks Again for help

Reza

Former Member
0 Kudos

Still the same,

I upload this to files,

Thanks Again,

Reza

Reagan
Advisor
Advisor
0 Kudos

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.

1768734 - Error during the import: "java.io.IOException: Data file seems to be in old format (no hea...

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

divyanshu_srivastava3
Active Contributor
0 Kudos

Did you try that parameter - responseBuffering=adaptive

Also try with selectMethod=direct

Make sure that the parameters are written is same way as stated above and in note.

Divyanshu

Former Member
0 Kudos

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

Former Member
0 Kudos

Where are this parameter

Reagan
Advisor
Advisor
0 Kudos

changed URL:  jdbc:sqlserver://PWDF6636:1433;databasename=BIG;responseBuffering=adaptive

If you referring to the above URL then that should be done in the Configtool - Securestore

Regards

RB

divyanshu_srivastava3
Active Contributor
0 Kudos

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

Former Member
0 Kudos

I will try that,

If did not work ,

I will start a new system export.

Thanks

Reza

Former Member
0 Kudos

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

Reagan
Advisor
Advisor
0 Kudos

The export dump will be always compressed.

If the DB size is 25GB then the dump file of size 5GB is alright.

RB

divyanshu_srivastava3
Active Contributor
0 Kudos

Awesome.. so it's clear it wad because of full adaptiveBuffering your export was not working.

If you would have checked and applied that note which was told initially,  you would have fixed it hours before.

Former Member
0 Kudos

Hello,


Thanks for reply and very good help.

I Had increase the memmory (RAM) og this server from 8 GB to 16 GB and increase the heap size to 250 GB and start a new export,

That works fine and the export file was 6.5 GB. I am just finish with import part and every thing working fine.

RB

Reza

Answers (0)