Search Results status_enab

Overview

SYS.DBMS_RESULT_CACHE is an Oracle Database-supplied PL/SQL package that exposes the server-side administrative and introspection interface for the Server Result Cache. In Oracle E-Business Suite 12.1.1 and 12.2.2, the Result Cache is a shared memory area within the System Global Area (SGA) that stores the results of PL/SQL functions and SQL queries so that repeated executions can be satisfied without re-executing the underlying work. The package is owned by SYS and is classified under the ETRM API classification OTHER, meaning it is a database infrastructure API rather than an EBS application programmatic interface. Its business value in an EBS context is performance: EBS code that opts into result caching — including certain Oracle Applications Technology (ATG) and Oracle Application Framework (OAF) internals, and custom PL/SQL — depends on this package to verify cache health, flush stale entries, and invalidate specific objects when underlying data changes. The package provides status constants such as STATUS_ENAB ('ENABLED'), STATUS_DISA ('DISABLED'), STATUS_BYPS ('BYPASS'), STATUS_SYNC ('SYNC'), and STATUS_CORR ('CORRUPT'), which callers use to determine whether the cache is usable at any point in time.

Key Procedures and Functions

The ETRM metadata documents seventeen procedures and functions. The primary entry points are described below; no signatures are reproduced here.

• STATUS — Returns the current availability state of the Result Cache as a string, mapped to one of the documented constants (DISABLED, ENABLED, BYPASS, SYNC, CORRUPT). It is typically the first call made before relying on cached results.
• FLUSH — Removes objects from the Result Cache. It offers control over whether free memory is retained or released, whether existing statistics are preserved or cleared, and whether the operation applies only to the local instance or to all instances in a RAC cluster. Objects under an active scan are not removed.
• MEMORY_REPORT — Produces a report of cache memory usage, supporting capacity planning and diagnosis of cache pressure within the SGA.
• DELETE_DEPENDENCY — Removes dependency information tracked by the cache for a given object. Result cache entries record their dependency on underlying tables and objects; when data changes, those dependencies must be resolved so that stale results are not served. DELETE_DEPENDENCY supports this maintenance by clearing the recorded dependency relationship.
• INVALIDATE — Marks cached results as invalid, forcing subsequent calls to recompute results rather than return cached values.
• INVALIDATE_OBJECT — Performs the same invalidation at the granularity of a specific object, allowing targeted purging rather than a global flush.
• BYPASS — Temporarily makes the cache unavailable so that participating code executes directly against the database source, bypassing cached results without permanently disabling the cache.

Tables Accessed

The ETRM record for this package documents no tables accessed via APPS synonyms. This is consistent with the nature of DBMS_RESULT_CACHE: it operates on SGA-resident cache structures and on Oracle's internal result cache dictionary tables, which reside in the SYS schema rather than in any EBS application schema. It is not a transactional API and does not read or write EBS business tables such as those in the AP, AR, GL, or PO schemas. Consequently, no EBS data dictionary dependencies are documented against it, and the package is likewise referenced by zero other packages within the ETRM inventory.

Usage Notes

Because DBMS_RESULT_CACHE is a SYS-owned database package, it is not invoked from EBS forms directly. Typical invocation paths include DBA maintenance scripts, database health-check routines, and custom PL/SQL. In EBS environments the package is most often used when an administrator needs to verify whether the Result Cache is enabled (STATUS), clear stale cached results after a data fix or a large concurrent process (FLUSH or INVALIDATE), or trace a stale-read issue back to invalidated objects (DELETE_DEPENDENCY, INVALIDATE_OBJECT). Execution generally requires elevated privileges such as EXECUTE on the package granted through DBA or an equivalent role. On RAC deployments, the global option on flush operations is significant, since each instance maintains its own cache and synchronization state is reflected by the SYNC status. On EBS 12.2.2, where the online patching edition-based redefinition model is in use, the result cache behaves as a database-wide shared component across editions, so cache operations affect all running editions simultaneously. Administrators should therefore exercise care when flushing globally during business hours.