We recommend switching to the latest versions of Edge, Firefox, Chrome or Safari. Using Internet Explorer will result in a loss of website functionality.

Java heap space issue for lookup transformation -- Urgent -- Data3Sixty Analyze

Comments

1 comment

  • Avatar
    Gerry Mullin

    If you don't have any duplicates in your join criteria, can you try replacing the Lookup with a Join? Set it to Left Inner and it should perform the same. I attached 2 screenshots that have a Lookup erroring out similar to your's, whereas the Join did not. I changed my Lookup JvmMaxHeapSize to 4G to give it enough memory to operate without erroring out, but note that I did not have to change the default value on the Join node.

     

    Attached files

    MaxHeapError_on_Lookup.png
    4G_on_Lookup.png

     

    0
    Comment actions Permalink

Please sign in to leave a comment.