To improve performance, your database administrator can modify Oracle settings. After any major change of the database contents, update the statistics on the table and the indexes.
| Parameter | Recommended value | Information |
|---|---|---|
| SGA_MAX_SIZE (System Global Area Maximum Size) |
1300M | Specifies the maximum size of the System Global Area for the lifetime of the instance. You get an error message when this parameter is not sufficient to increase the memory of dynamic parameters. |
| DB_CACHE_SIZE | 600M | Refers to the size of the cache of standard blocks. Allocate the largest part of the SGA to database buffers on the IBM® Records Manager database servers. |
| SHARED_POOL_SIZE | 250M | The default value of this parameter after Oracle installation is too small. You can enlarge this setting according to the SGA size, the shared pool contains shared cursors, stored procedures, control structures, and other structures. Larger values improve performance in multiuser systems. Smaller values use less memory. |
| JAVA_POOL_SIZE | 150M | The Java™ pool is set using the JAVA_POOL_SIZE parameter. Unless the Oracle JVM is created for a database, this parameter can be set to zero (JAVA_POOL_SIZE = 0). Otherwise it wastes memory. The Java pool buffer must be set if the Oracle JVM is created in a database. |
| LARGE_POOL_SIZE | 15M | This parameter specifies the size (in bytes) of the large pool allocation heap. The large pool allocation heap is used in shared server systems for session memory, by parallel execution for message buffers, and by backup processes for disk I/O buffers. |
| PROCESSES | >= 150 | Ensure that this value is large enough to accommodate simultaneous sessions for all connections from the WebSphere® Application Server pool, system processes (approximately 10), and any ad hoc user and DBA sessions. |
| PGA_AGGREGATE_TARGET | 700M | This parameter specifies the target aggregate PGA memory available to all server processes attached to the instance. Set this parameter to enable the automatic sizing of SQL working areas used by memory-intensive SQL operators such as sort, group by, hash join, bitmap merge, and bitmap create. |
| WORKAREA_SIZE_POLICY | AUTO | Work areas used by memory-intensive operators are sized automatically, based on the PGA memory used by the system, the target PGA memory set in PGA_AGGREGATE_TARGET, and the requirement of each individual operator. You can specify AUTO only when PGA_AGGREGATE_TARGET is defined. |
| OPEN_CURSORS | >=500 | OPEN_CURSORS specifies the maximum number of open cursors (handles to private SQL areas) a session can have at once. You can use this parameter to prevent a session from opening an excessive number of cursors. |
| UNDO_RETENTION | 10800 | UNDO_RETENTION specifies (in seconds) the low threshold value of undo retention. The system retains undo for at least the time specified in this parameter and automatically tunes the undo retention period to satisfy the undo requirements of the queries. Enlarge this value to 10800 aims to avoid the ORA-01555 error. |
| table space USERS AUTOEXTEND | MAXSIZE= unlimited | By default, this table space is used for storing IBM Records Manager tables and LOBS during the IBM Records Manager database installation. The DBA must set this table space to extend dynamically, without restricting the maximum size. |
| table space INDX AUTOEXTEND | MAXSIZE= unlimited | By default, this table space is used for storing the indexes of the IBM Records Manager tables. The DBA must set this table space to extend dynamically, without restricting the maximum size. |
| table space UNDOTBS1 AUTOEXTEND | MAXSIZE= unlimited | By default, this table space is used for storing IBM Records Manager undo logs. The DBA must set this table space to extend dynamically. |
| table space TEMP FILE SIZE | >= 1 GB | By default, this table space is used for storing IBM Records Manager temporary tables, and sort data. Set the table space set to extend dynamically. |
