BI refresh java export process stuck while creating sdmkit.jar

[Former Member]

HI Experts,

Problem during homogenous system copy during java export

To export JAVA of production into to quality we faced some problems.The cause was that the SDMkit.jar file which is created during Java export can be of maximum 4GB in size but in our case this was greater than 4GB (4.47GB).Therefore,the SDMkit.jar was not being created properly.

We referred to SAP for this and they suggested that either wait for SP17(as there is a limitation with Java API) or try to update components through SDM.

Since SP17 is still not available we tried the to update components through SDM(components with any version).It started fine but got stuck at 68%. Now sp17 released and still sap says these bug has not been fixed.

The problem with the createsdmkitjar command is still not fixed. If the problem is fixed in some SP, the note about the problem 1169806 will be updated. Till that time the only possible workaround is described in the note.

We tried with all work around options as per note 1169806.

Deatils:

Error: Error during command execution Throwable:

com.sap.sdm.app.install.packer.SdmKitJarPacker$PackException Throwable

message: Error while

creating /sapcommon/frodojavaexport/JAVA/SDM/SDMKIT.JAR

invalid entry size

Processing error. Return code: 4

Error: Processing error. Return code: 4

It would be greatful if any one can help us in solving these problem.

[Former Member]

Following the instructions as per the note "1169806" does work. I have re-deployed "ADSSAP.SCA" component with "Update Deployed SDAs/SCAs that have any version" which reduced the SDM repository size in the file system.

You can easily find out the components that have multiple versions by looking into the "SDM Repository".

Then when I exported the JAVA image using "sapinst", the image created was smaller than 4GB in size which I used to build my QAS system.

[former_member235924]

Hello,

did you find a workaround? We are trying to do our first system copy of BI and run into the same issue described in note 1169806.

I haven't tried to redeploy anything as I cannot see this would change anything. And I don't want to try anything unnecessary with our Production BI system.

Thanks,

Ingrid

[Former Member]

SDMKIT.JAR is the file which contains all your java deployments, hence you have to import it , if you have many objects build using Java

I have had the same situation in the past and i redeployed the components seperately using SDM