The note suggested by Hemanth is the one to start with.
You mentioned that the system is facing OOM dumps frequently. A quick question. Is the server sized and configured with enough memory for the BI system?
Is this a dual stack or a stand-alone Java stack?
How many server nodes does the Java system have?
What is the heap size assigned for the node(s)?
There is no point in increasing heap parameters when there is lack of physical memory.
The issue is pretty clear in the log you have supplied. The JVM is trying to allocate 600MB and it fails. To fix this issue you need to check if the JVM is updated and the parameter are set correctly.
Additionally based on the log the OOM happens during export operations. You should consider setting the safety belt in the BI system.
Check these notes/KBA.
2069568 - BI Java OOM dumps caused by export operations
1622134 - Safety belt: Results quantity is too large (Excel/PDF)
RB