Validate Memory Guard Thresholds

Oracle recommends that you validate Memory Guard thresholds before the feature becomes enabled by default in a future release. Testing representative workloads helps you identify reports, dashboards, data models, and queries that exceed configured request-level memory limits, so that you can optimize them or work with Oracle Support before the default changes.

The following topics describe Memory Guard, explain its benefits, describe error messages, show how to enable the feature, and explain how to validate your workloads.

About Memory Guard

Memory Guard helps protect Oracle Analytics Cloud from requests that consume excessive memory. When Memory Guard is enabled, Oracle Analytics Cloud monitors the memory used by each request. If a request exceeds the configured memory limit, Oracle Analytics Cloud stops the request and returns an error.

Memory Guard helps maintain system stability during periods of heavy or concurrent workloads by preventing individual requests from consuming excessive memory. Requests that remain within the configured memory limit continue to run normally.

Memory Guard is available as an optional system setting. Oracle recommends that administrators enable Memory Guard and test both representative and critical workloads before the setting is enabled by default. Early testing helps you identify reports, dashboards, data models, and queries that might require optimization before request-level memory limits are enforced by default.

Benefits of Enabling Memory Guard

When Memory Guard is enabled:

  • Requests that exceed configured memory limits stop before they consume excessive system memory.

  • System stability improves during periods of heavy or concurrent workloads because individual requests can't consume excessive memory.

  • Users receive an error message when a request exceeds the configured limit, making the condition easier to identify and investigate.

  • Users can identify reports, dashboards, data models, and queries that might require optimization before Memory Guard becomes enabled by default.

Understand Memory Guard Error Messages

When Memory Guard stops a request, users might see one of the following messages.

Memory Threshold Exceeded

MemoryGuard: Request memory exceeds configured limit

Cause: The request exceeded the configured request-level memory limit. Memory Guard stopped the request to protect system resources.

Action: Review the request to determine whether it can be optimized or simplified. If the request is expected to require more memory, contact Oracle Support for assistance.

Insufficient Resources

Insufficient resources to perform the current operation. The query or operation may need to be modified.

Cause: The request couldn't complete because sufficient memory wasn't available.

Action: Review the query, dashboard, or data model to determine whether it can be optimized. If the issue persists, collect diagnostic information and contact Oracle Support.

Turn Memory Guard On or Off

You enable or disable the Memory Guard system setting through the Advanced Settings page.

  1. In Console, navigate to the Advanced System Settings page.
  2. Set Memory Guard to On to enforce request-level memory limits. See also Memory Guard.
  3. Set Memory Guard to Off to stop enforcing request-level memory limits.

Test Memory Guard Before it's Enabled by Default

Oracle recommend that you test Memory Guard before it becomes enabled by default in the future. Testing helps you identify requests that exceed configured memory limits while you still control when enforcement is enabled.

  1. In Advanced System Settings, set Memory Guard to On.
  2. Run representative workloads, including:
    • Frequently-used reports and dashboards
    • Critical dashboards
    • Ad hoc queries
    • Data models
    • Scheduled workloads
  3. Identify any requests that fail because they exceed the configured memory limit.
  4. Review the error messages and available diagnostic information to identify affected requests.
  5. If you identify workloads that fail unexpectedly, collect diagnostic information and log a Service Request with Oracle Support.

Oracle Support can help investigate the affected requests and determine whether configuration changes, query optimization, or request-level memory threshold adjustments are appropriate for your environment.