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.
Troubleshooting Out of Memory Error
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 may not be enough or the job is configured with too many threads/streams, or both.
Example of Masking Engine - DMsuite log with out of memory condition from Masking job:
To resolve Out of Memory error, the memory allocated to the job must be increased and/or decrease the number of streams and threads which are consuming memory. Rerun the job, once these changes are made to the memory.
To increase or decrease memory configuration parameters use MIN Memory and Max Memory fields on the Create Masking Job page.