1.277 RESULT_CACHE_MODE
RESULT_CACHE_MODE specifies when a ResultCache operator is spliced into a query's execution plan.
               
| Property | Description | 
|---|---|
| Parameter type | String | 
| Syntax | 
 | 
| Default value | 
 | 
| Modifiable | 
 | 
| Modifiable in a PDB | Yes | 
| Basic | No | 
| Oracle RAC | Multiple instances can have different values. | 
Values
- 
                        MANUALThe ResultCacheoperator is added only when the query is annotated (that is, hints).
- 
                        FORCEThe ResultCacheoperator is added to the root of allSELECTstatements (when it is valid to do so).Note: FORCEmode is not recommended because the database and clients will attempt to cache all queries, which may create significant performance and latching overhead. Moreover, because queries that call non-deterministic PL/SQL functions are also cached, enabling the result cache in such a broad-based manner may cause material changes to the results.
For the FORCE setting, if the statement contains a NO_RESULT_CACHE hint, then the hint takes precedence over the parameter setting.
                  
See Also:
- 
                           Oracle Database SQL Tuning Guide for more information on how the result cache handles PL/SQL functions before changing the value of this initialization parameter 
- 
                           Oracle Database SQL Language Reference for more information about the NO_RESULT_CACHE hint