The reason that this error is present in the BG log file is due to an unpublished Oracle bug 6471770.
The scenario can be due to large data sets that cause allocated hash group-bys to allocate memory beyond internal limit for the auto-memory manager of PGA.
Please follow these steps to resolve the issue:
- Backup your Oracle instance and verify the integrity of the backup.
- Login to SQL PLUS as an administrative account.
- Enter the following command: alter system set "_gby_hash_aggregation_enabled"=false scope=both;
- As an alternative you can use "NO_USE_HASH_AGGREGATION" hint within the SQL statement to avoid this issue.
- This issue is resolved in the following patchsets from Oracle: Oracle 10.2.0.5 or Oracle 18.104.22.168.