Originally posted by: Ali_Chouman

Dears,

Im getting an error when trying to execute the WTX map on B2B note that the input is a Database adapter and the output in Database adapter, in out WTX map.

the error is for memory  : 

<mapReturn>50</mapReturn>

<message>Not enough memory to execute map</message>

please advise what should be done to solve this (noting that i think that there should be a place in WTX to modify the shared memory or used memory by WTX).

also one more point which is example i have 1M record in my DB im selecting the 1M and updating same table based on some rules. for 1M its working fine once i increase the number of records to 2M, im getting the error.

Please advise.

Thanks

Originally posted by: @vkprasad_WTX

Hi Ali,

 Try to close all opening applications and also change some properties in your design studio like (Map-->Map settings-->Workspace-->change page size and page count numbers Ex:1024 and 64)

Thanks

Originally posted by: Ali_Chouman

Hi,

i did this i changed it from 64 till 256 and still the same, WTX is too slow also sometimes im getting the memory full issue.

Originally posted by: wtx_genie

Hi Ali,

Please run the dtxpage command at wtx installed directory with map name. it will give approx pagesize and page count values.

Thanks,

WTX_Genie

Originally posted by: Ali_Chouman

Hi Kindly note that im using WTX integration server on AIX where its integrated with B2B i didnt installed the wtx command line.

please advise.

Originally posted by: Semoul

If you still have this issue, please try to set Workspace to "Memory". There is an intermittent memory allocation bug when using Workspace "File" in certain situations.

Originally posted by: paul.brett

When you deploy a map into Sterling Integrator it's important to know that any settings that create files that use 'Map' location will result in files being created in the SI/install/logs folder.

In other words, when the file location setting for the Workspace is set to 'Map', the folder used is the SI/install/logs folder.

So you need to make sure that when you run large transactions, the space allowed in the SI/logs folder filesystem is enough for the Workfiles to be created.

Also when you are running large transactions with multiple records, I would try to execute the map by bursting the inputs so we work on the transaction chunk by chunk and thus avoid this critical memory usage.  Edit your input card settings..  'Fetch As', and set it to 'Burst' instead of 'Integral'.  Then set a number of records to fetch in each burst.  If for example, you have 2,000,000 records to read, I would set the Fetch Unit to 100,000 so the map will burst 20 times.

See the documentation about burst here:

http://www.ibm.com/support/knowledgecenter/SSVSD8_8.4.1/com.ibm.websphere.dtx.md.doc/concepts/c_map_design_Using_Bursts_for_Large_Files.htm
http://www.ibm.com/support/knowledgecenter/SSVSD8_8.4.1/com.ibm.websphere.dtx.md.doc/concepts/c_map_design_Configuring_Bursts.htm

You should also tune your Workspace settings for the map, using the DTXPAGE tool, to find the ideal values, based on your input.

(with thanks to Ejay for the hints)

Thank-you.

Paul.

Follow me on Twitter