RESULT_CACHE_MAX_RESULT specifies the percentage of the entire result cache for the individual results. Both parameters require the ALTER SYSTEM privilege. If remote objects are accessed, the RESULT_CACHE_REMOTE_EXPIRATION parameter can be used to specify how long the result remains in the cache in minutes. This parameter can be set using ALTER SESSION or ALTER SYSTEM. The result cache can then be switched on using the FORCE session setting with the RESULT_CACHE_MODE parameter, using the RESULT_CACHE (MODE FORCE) table attribute, or in fine-grained detail using the RESULT_CACHE hint.
The "RESULT CACHE" operation in the execution plan indicates that the result cache is created for the top SELECT branch or is used in the case of repeated execution. If this is a repeated execution, the execution time has been greatly reduced and " logical reads " (here " consistent gets ") are no longer required.
If you want to activate the bolivia telegram screening result cache in PL/SQL, the developer must modify the PL/SQL slightly. The following examples show the syntax with and without the result cache.
RETURN number
IS
With Result Cache:
CREATE OR REPLACE FUNCTION customer_sales(cust_id_in IN number)
RETURN number result_cache
IS
Marek-Anton Mierzwa (Drägerwerk AG & Co. KgaA) has written an interesting report on this [1] . There he describes how the overall performance of the database was increased enormously after the authentication queries of the rest modules were provided with the PL/SQL result cache.