Skip to main content

KBA1036 Troubleshooting Masking Engine Out of Memory Errors



Masking or Profiling job fails with error message - java.lang.OutOfMemoryError: GC overhead limit exceeded or for Oracle the message  is  “Thrown when the Java Virtual Machine cannot allocate an object because it is out of memory and no more memory could be made available by the garbage collector." OutOfMemoryError objects may be constructed by the virtual machine as if suppression were disabled and/or the stack trace was not writable. 


Some jobs need more memory than others, it depends on the number of tables, how many columns you are masking and the type of algorithms assigned to the inventory. The current memory allocation is not enough or the job is configured with too many threads/streams or both. The default memory allocation is 1GB.

Example of Masking Engine -  DMsuite log with out of memory condition from Masking job:


The resolution for this error is to increase the memory allocated to the job and/or to decrease the number of streams and threads which are consuming memory.  Once these changes are made to the memory, rerun the job.

Note: Do not exceed the amount of memory allocated to the VM machine.

Masking Job Screen: To increase or decrease memory configuration parameters use MIN Memory and Max memory boxes on the Masking Job page.

  • Was this article helpful?