Updating DB_KEEP_CACHE parameters

The values in the Recommended_Value fields represent recommended values based on current data and cannot predict future requirements. Define values that reflect expected size and usage relevant for the workflow in your organization.

  1. On the WorkZone Content Server, press Start and type ScanSQL to open the ScanSQL form. You can also press ALT+R in windows to open the Run window and type ScanSQL.
  2. In the ScanSQL form, click SjBase to open the SjBase form.
  3. In the SjBase form, click Tuning to open the Tuning form.
  4. In the Tuning form, click View parameters to open the WorkZone SQL form. The two rows of the DB_KEEP_CACHE parameters are displayed in the lower half of the WorkZone SQL form.
  5. In the Name column > optimizer_index_cost_adj field, change the default value of 100 to 10 to use indexes for searches instead of full table scans.
  6. In the Name column > db_keep_cache_size field, increase the memory allocation of the db_keep_cache in bytes1. It is recommended to increase the size in blocks of 500 megabytes at a time on production databases to ensure the db_keep_cache_size is large enough to contain organic cache growth during normal operations. By setting a larger cache size, you can reduce the number of times have keep incrementally increasing the size. If you are operating a historical database, (a database that only contains historical data for reference and archive purposes), you can use the recommend value instead.
    1You can change how the values are defined in the db_keep_cache_size bytes, kilobytes, megabytes or gigabytes. Please refer to the Oracle Online manual for details.
Tip: You can also use the following SQL statements to display the DB_KEEP_CACHE parameters: SELECT* FROM sjv_$parameter

Note: You can also use the Oracle SQL Developer tool, which is included in a standard WorkZone installation and available on the WorkZone server.