- Check the Installation checklist.
- Launch the installation
- Steps for application tiers with multiple file systems (conditional)
- Perform post-requisites
- 12.2+ specific instructions (R12.2+ users only)
- Enable network connectivity to Applaud Cloud
The app uses a database feature called Result Cache to optimize performance. Result Cache:
- Is new in Oracle 11g and improved in 11gR2
- Works on SQL query results (local and distributed)
- Works on PL/SQL function results
- Stores cached data that is shared across executions
- Is automatically marked stale if the underlying data is changed
- Can dramatically increase performance
- Stores the results of queries and function calls
- Uses a slice of the Shared Pool
- Is not affected by flushing the Shared Pool
If Result Cache is not enabled on your database, the installation process would have presented a warning that it needs to be enabled. You should also review the Result Cache recommendations.
Checking the status of Result Cache
To see if Result Cache is enabled or not, you can also run this SQL statement:
SELECT dbms_result_cache.status FROM dual;
Even if result cache is enabled, please ensure you follow the Result Cache recommendations.
You can also retrieve a list of the current result cache parameters:
SQL> show parameter result_cache NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ client_result_cache_lag big integer 3000 client_result_cache_size big integer 0 result_cache_max_result integer 10 result_cache_max_size big integer 100M result_cache_mode string MANUAL result_cache_remote_expiration integer 0
If you wish to obtain a memory report, please run:
Here is a sample report:
Please ensure you follow the Result Cache recommendations; running the above utilities does not ensure the recommended parameters are set correctly.
To enable result cache, you need to set memory_target and shared_pool_size parameters:
|RESULT_CACHE_MAX_SIZE||Values of SHARED_POOL_SIZE, SGA_TARGET, and MEMORY_TARGET||100M or more (depends on the SGA/Memory Target values)|
If you are using sga_target instead of memory_target for managing memory, then check the shared_pool_size and set it to its minimum value to enable result cache.