The excessive memory usage for SQL queries was discovered in a critical database, traced back to internal queries by the FBDA process. Hard parses, which are resource-intensive, were identified as the cause. The issue was detected through SQL plan and memory consumption analysis. A solution involving the use of bind variables and a workaround for the problem were proposed. A bug related to queries without bind variables was identified and it was revealed that a similar issue did not exist in another database using the flashback feature efficiently. The proposed workaround involved removing the quota clause from flashback data archives.