cancel
Showing results for 
Search instead for 
Did you mean: 

Error during Java DB export- Attempt to fully materialize LOB data

Former Member
0 Kudos

Hi Experts,

I am trying to take export of a NW 7.3 portal system using SWPM 10 SP09 and in database export phase one of the packages of table J2EE_CONFIGENTRY got aborted due to heap memory issue.

For this I tried increasing the heap memory till 4.5 GB in control.xml and started the SWPM from scratch but it’s still failing.

I have also consulted various notes regarding this

1768708 - Error "java.lang.OutOfMemoryError: Java heap space" during the export

1173398 - jload export fails with OutOfMemoryException

1526647 - IBM i: java.lang.OutOfMemoryError during jload import


I have updated the jvm to 83 and JDBC drivers to 10.5  but still no luck. Please advice.


We have a distributed system with SCS on IBM Mainframes, PAS and AAS on zlinux  and DB2 on a separate box


Thanks in advance

Srikanth

Accepted Solutions (1)

Accepted Solutions (1)

former_member227283
Active Contributor
0 Kudos

Hi,

please increase the heap size in configtool and restart the configtool and try to export again.

If it still not work, then try to set the parameter fullyMateralizeLobData = false and restart the instance and try to export.

Second option will help to understand if there are huge data in form of LOB.

Regards,

Anil Bhandary

Former Member
0 Kudos

Hi Anil,

We tried the second option by adding the value in the secstore URL in configtool, but after saving the changes application is unable to connect to the DB.

Coming to the first option does the changes done in the configtool affect the SWPM execution?

Regards,
Srikanth G

former_member227283
Active Contributor
0 Kudos

Hi Srikant,

While starting the export SWPM reads initial values from Config properties based on which it creates necessary parameter files for performing the export.

Is it working with value fullyMateralizeLobData = yes.

Also can you share what parameter you are passing in Secure store ..

Regards,

Anil

former_member227283
Active Contributor
0 Kudos

Dear Srikant,

SAP note: 2076081 - Jload: special usages


Contains the solution for your problem.


Regards,

Anil

Former Member
0 Kudos

Hi Anil,

We have increase heap memory  as per SAP but it is not worked for me.

Thanks & Regards

Srikanth

Former Member
0 Kudos

Hi Anil,

We are trying add as in the screenshot below in configtool

We didn't try with yes option.

Regards,

Srikanth G

former_member227283
Active Contributor
0 Kudos

Hi Srikant,

Please share what error you are getting after setting the parameter. Share the log of configtool which would have written in configtool folder.

Also try to follow the SAP note: 2076081

Regards,

Anil

Former Member
0 Kudos

Hi anil,

Please find the below:

Regards,

Srikanth

former_member227283
Active Contributor
0 Kudos

Hi Srikant,

Not sure why it is not picking the value as it is recommeded for DB2.

Option we have as:

1. As you have mentioned you have modified the control.XML and restrated from scratch, I would suggest modifiy the Control.XML immeditlay after giving all neccesary input for export. Once Control.XML is modified stop SWPM and start it again by selecting option Restart from Old Run.

2. Pass the parameter for Jload as per the SAP note: 2076081

Regards,

Anil

Former Member
0 Kudos

Hi Anil,

We did the same as mentioned in your point 1 , made the below changes in XML file after launching SWPM for first time and closing it so that it reads control.xml file again..

It has read the XML file also becoz the command used shows the new value 3072m as highlighted below:

Also launched SWPM as mentioned in the note 2076081

I believe it has some issue with Kernel files or JDBC driver files//

Regards,

Srikanth

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi All,

Issue got resolved, its was my mistake..I was using the option "fullyMaterializeLobData=false" in secstore - URL of configtool without closing it with a  " ; " . Due to which we are unable to connect to the DB. After closing the string we successfully exported the DB.


Thanks a ton for your valuable inputs..


Regards,

Srikanth

0 Kudos

Hi Srikanth,

check https://scn.sap.com/thread/3281687

Thanks and Regards,

Anto

former_member185239
Active Contributor
0 Kudos

Dear Basis,

You need to follow the below sapnotes to correct the error

784903 - Export and other DTR operations fail on DB2 with Status 500




774339 - Internal Server Error in DTR


You need to update the database drivers for DB2


With Regards

Ashutosh Chaturvedi

former_member185239
Active Contributor
0 Kudos

Dear Basis,

Disable the fullyMaterializeLobData property by using the parameter fullyMaterializeLobData=false

Default value is true so it is trying to load the whole data at once, if you set the property to false then it will fetch the LOB data in small chunk.

Error during bootstrap:  Attempt to fully ... | SCN

You can also increase the value of heap memory of java system to export the content.

With Regards

Ashutosh Chaturvedi

former_member185239
Active Contributor
0 Kudos

Dear Basis,

Have you try to increase the heap memory in config tool?

Increase the heap memory in configtool and take a restart of sap system and then try to export the content.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Dear Ashutosh,

We already have 6144MB of max Heap allocated :

Do we need to increase it anywhere else ?  Please suggest.

Regards,

Srikanth

former_member185239
Active Contributor
0 Kudos

Hi Srikanth,

Yes , increase the heap size to 8GB until and unless it resolve your issue.

Also go through the java heap dump , to analyze the size.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hello Srikant, Which id you are using to export the dumps via SWPM? root or adm?. Additionally if this is not a production system, try restarting JAVA and then re-run the export. Regards, Vicky

Former Member
0 Kudos

Hi Vicky,

Thanks for the prompt reply !!!

We are using SIDADM user and we have already retried from beginning after restarting the application but again with the same error..

Regards,

Srikanth

Former Member
0 Kudos

Have you tried to perform the same with root user?

Former Member
0 Kudos

Hi Srikanth,

Update the statistics for all the tables RUNSTATS.

Check below link and sapnote - to Disable data source property as mentioned in the error.

IBM Knowledge Center

1512819 - DB2-z/OS: Reducing SAP Java heap consumption for LOBs

Regards,

Prithviraj.