cancel
Showing results for 
Search instead for 
Did you mean: 

Memory error while SYSTEM Copy using sapinst

Former Member
0 Kudos

Hi Experts,

I'm trying to do a system copy of portal sp14 from Dev to sanbox. I have exported from Dev and I'm in Sanbox phase 38 of 41 Install Java engine I'm getting following error.

Create SDM directories:

Create SDM home directory:

Directory for SDMHome '/usr/sap/JXD/JC00/SDM/program' doesn't exist yet.

Directory '/usr/sap/JXD/JC00/SDM/program' created

Create SDM root directory:

Directory '/usr/sap/JXD/JC00/SDM/root' created

Extracting packed repository.

Caught OutOfMemoryError

java.lang.OutOfMemoryError

InstallSDM was excecuted with status ERROR.

I thought I could change some heap size or other parameter using configtool, but it looks like it did not create j2ee directory where I could launch configtool.

Is there anyone who has faced this problem or have any idea how to resolve it?

Your answer is really appreciated and important.

Thanks in advance

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Afnan Chawla

Did you solve problem?

How?

I have same problem ...

Edited by: Nikolay Ustinov on Aug 15, 2008 2:05 PM

Former Member
0 Kudos

Nope, I was not able to solve it.

Thanks,

Edited by: Afnan Chawla on Aug 28, 2008 6:49 PM

0 Kudos

Done with changing default value from 64

to 256M in control.xml file. (64 bits)

Restarting sapinst after.

Best Regards

Former Member
0 Kudos

It has to be changed in control file at the following locaton

function readEntriesFromFile(filename,entry) {

// read out file filename and return all lines matching entry

// returns undefined, if file does not or exist or no matching line was found

:66601

case "OS400":

jdkArgs.push('-Xms256M');

jdkArgs.push('-Xmx1536M');

break;

case "OSF1":

jdkArgs.push('-classic');

jdkArgs.push('-Xmx64M');

break;

case "HP-UX":

jdkArgs.push('-Xmx64M');

jdkArgs.push('-XdoCloseWithReadPending');

break;

default:

jdkArgs.push('-Xmx64M');

break;

}

return jdkArgs;

}

Former Member
0 Kudos

Rayi,

My bad I should have looked at the directory. I was able to find the version. Here it is.

Release: 7.00

SP-Number: 14

SP-Patchlevel: 0

What do you suggest?

Thanks,

Former Member
0 Kudos

If you un car the SDM.jar file you will find the file name update.bat/csh and you van have this file in any temp dir and once you run it it will ask you the dir path of update

1) StopServer

2) jstartup mode=standalone

3)goto temp dir and execute ./update

4) /usr/sap/SID/JCXX/SDM/program

5)SDM to jstartup mode=integrated

6) StartServer

Former Member
0 Kudos

Rayi,

I dont see the SDM.jar file.

This is what I see in .../SDM/program directory:> Any suggestion?

META-INF - StartServer.bat - bin - instfiles - sdm.bat - sdm_prep_com.bat - version.txt-

Readme.txt - StartServer.sh - config - lib - sdm.sh - sdm_prep_com.sh-

-RemoteGui.bat- StopServer.bat - doc - log - sdm_jdk.bat - startSDM.bat-

-RemoteGui.sh - StopServer.sh - inBox - saplogging.config -sdm_jdk.sh - startSDM.sh

Thanks,

Edited by: Afnan Chawla on Jul 29, 2008 8:36 PM

Former Member
0 Kudos

Download the 14 stack from the market place you shud find the SDMKIT14.SAR/JAR

Former Member
0 Kudos

george rayi,

Can you please help me out updating SDM and how to check the version? It seems like a solution but i'm kinda blank right now. If you just give me little more information, It would really appreciated.

Thanks,

Former Member
0 Kudos

Afnan-

Check your SDM version i think your SDM is not getting updated during this phase which uses SDM for the deployment this same error i got when i was also doing Refresh/JSPM.

you can manually update your SDM and run again the SAPINST it may work.

Hope this helps you

Edited by: george rayi on Jul 29, 2008 8:17 PM