-
When upgrading or performing a new installation of OnBase, utilize a 64-bit version of Oracle to take advantage of additional RAM support.
-
Place the redo log(s) on dedicated disks, or disks that can support writes in less than 10 ms, to eliminate I/O contention with other files. In accordance with Oracle recommendations, RAID 5 is not recommended.
-
Pre-size the OnBase database files so they do not auto-grow. Modify the growth increments to be 100MB for larger files (DBSpaces 1, 2, 6, 9, 2i, 6i, 9i, 10) and 50 MB for all other file groups.
-
Configure Memory Management appropriately to ensure adequate resources available for the Oracle instance as well as the host operating system.
-
The use of Automatic Memory Management, Automatic Shared Memory Management or Manual Memory Management can be decided at the discretion of the DBA. Hyland Software has no preference on which method is used.
-
It is recommended to leave 20% of available memory for the operating system for Windows environments, and 10% of available memory for non-Windows environments.
-
-
Configure the Oracle instance to utilize dedicated server processes.
-
During initial instance creation, configure DB_BLOCK_SIZE parameter to 8192. This cannot be changed after instance creation.
-
Leave the DB_FILE_MULTIBLOCK_READ_COUNT parameter at its default value on initial installation. Monitor system and I/O activity over time to evaluate whether this value should be modified.
-
Leave the OPTIMIZER_INDEX_CACHING parameter at its default value of 0.
-
Configure the OPEN_CURSORS parameter to 300, and increase as necessary. Setting this value higher than needed will not cause no additional system overhead.
-
Configure the OPTIMIZER_MODE parameter to its default value of ALL_ROWS.
-
Configure the CURSOR_SHARING parameter to its default value of EXACT. Changing this parameter to other values can have unexpected performance results.
-
Leave the OPTIMIZER_DYNAMIC_SAMPLING parameter at its default value of 2. With this configuration, Dynamic Sampling (11g) or Dynamic Statistics (12c and higher) will only be considered for statements that query one or more tables with no statistics. Following the recommendation of gathering statistics regularly, this will be adequate for OnBase performance.
-
Disable Automatic Optimizer Statistics Collection. This is a built-in job beginning with 11g that performs automatic gathering of statistics. It is recommended to configure a scheduled process to gather object statistics to ensure adequate sampling of objects using the DBMS_STATS procedure. Creating a scheduled process will allow flexibility on when the procedure is executed, and the objects and sampling rate of what is gathered.
-
If using Oracle 11g and higher, account for the default Password Expiration behavior appropriately. If the default OnBase users' passwords are automatically expired, OnBase may not be accessible to users.
-
If using Oracle 12c or higher, utilize the multitenant architecture for database installation.
-
If using Oracle 12c Release 1, consider Oracle's recommendations surrounding the OPTIMIZER_ADAPTIVE_FEATURES parameter and functionality, outlined in Oracle Support Note #2312911.1
-
Hyland Software does not recommend the use of Oracle's SQL Tuning Advisor, which analyzes query execution plans and can create alternate execution plans or profiles based on those findings. For more information search for Custom Indexes, Tuning Advisors on Community.
-
Configure a scheduled job to verify database integrity on a regular basis.