The Intelligent Computation Core loads large result sets into RAM. When a batch exceeds the configured -Xmx (Java) or MaxMemoryPerQuery (C++ runtime), ERDAICC triggers its garbage collector and optimizer. The "fixed" message here is often a false positive; the job fails again on the next large batch.
Below is a proven, platform-agnostic fix strategy derived from over 200 enterprise remediation cases. erdaicc fixed
Before you can claim ERDAICC is fixed, you need to recognize the symptoms: The Intelligent Computation Core loads large result sets