Hello Community,
We are struggling with a “Out of Memory : Java Heap Space” error while saving a BLS transaction, since we changed our strategy to use action joiners instead of a BLS transaction using 7 different queries against a giant Informix database. Each query performs grouping and sum calculations on an average of 5 million records views. These views keeps data since 10 years ago. This change on strategy was because the BLS transaction using only queries crashed while reaching some kind of time limit. We suppose that because there was a repeater reading every record of a “father” query and then every record was passing its parameters to other 7 heavy calculation queries reaching this time limit was kind of obvious .
We already increased the amount of memory by 4 gb for the Java Heap Space. After that, we expanded the BLS transaction a little bit by creating some more joiners. But we did not finished creating all joiners needed. We reached again to a memory limit. If you could see our transaction, we are launching in one same block at the beginning of the BLS transaction all 7 queries grouped by the same two keys ( product and center). We use the joiners to link the results of the queries by product and center. As being built , adding joiners step by step, I have tested this BLS transaction and runs very fast!. We suppose all these queries run in parallel. Problem is that we try to save the transaction; the out of memory:java heap space error arise again.
Please help,
We are running a 12.2.4 ( build 80 ) MII platform .