Tuning of Oracle Parameters
Depending on the size of the Orchestra installation and the number of database connections set in the different database connection pools in the Orchestra application server, Oracle parameters may have to be tuned.
The database must be able to cope with the sum of all database connection pools in Orchestra.
The three most commonly tuned parameters are:
• PROCESSES
• SESSIONS
Should match number of configured connections in the Orchestra database connection pools.
Oracle recommend setting it to PROCESSES x 1.1 + 5
• TRANSACTIONS
Oracle recommends setting it to SESSIONS x 1.1
Example:
ALTER SYSTEM SET PROCESSES=1200 SCOPE=SPFILE;
ALTER SYSTEM SET TRANSACTIONS=1458 SCOPE=SPFILE;
ALTER SYSTEM SET SESSIONS=1325 SCOPE=SPFILE;
Additional parameters to review
Oracle memory
• MEMORY_TARGET
• MEMORY_MAX_TARGET
Example:
ALTER SYSTEM SET MEMORY_TARGET=8000M SCOPE=SPFILE;
ALTER SYSTEM SET MEMORY_MAX_TARGET=10000M SCOPE=SPFILE;
Adaptive log file sync
Oracle 11 introduced an new mechanism to communicate with the log writer, a part of the commit-process. Several Oracle database administrators have experienced a considerable performance gain when they have disabled this new "adaptive log file synchronization".
ALTER SYSTEM SET "_use_adaptive_log_file_sync"= false;
Cursor sharing
Qmatic Orchestra gains additional performance if cursor sharing is set to
ALTER SYSTEM SET CURSOR_SHARING='SIMILAR' SCOPE=SPFILE;