Oracle parameter file settings

Oracle uses configuration parameters to locate files and specify runtime parameters common to all Oracle products.

When an Oracle program or application requires a conversion for a particular configuration variable, Oracle consults the associated parameter. All Oracle parameters are stored in the registry.

The following parameters are set for the use with IBM® Product Master:

Parameter	Description	Required value
SGA_TARGET	SGA_TARGET specifies the total size of all SGA components. If the SGA_TARGET is specified, then the following memory pools are automatically sized: Buffer cache (DB_CACHE_SIZE) Shared pool (SHARED_POOL_SIZE) Large pool (LARGE_POOL_SIZE) Java™ pool (JAVA_POOL_SIZE) Streams pool (STREAMS_POOL_SIZE)	50% of your physical memory on the DB server, assuming you are using the DB server for Oracle only and Oracle DB is used for Product Master only.
DB_BLOCK_SIZE	The parameter sets the size (in bytes) of an Oracle database block. This value is set at the database creation, and cannot be changed later. DB BLOCK SIZE is critical for the Product Master schema and must be at least 8192. Schema creation fails if the db_block_size is too small.	Required Value: 8192
QUERY_REWRITE_ENABLED	Used to enable or disable query rewriting for materialized views.	Required Value: TRUE
PROCESSES	The parameter specifies the maximum number of operating system user processes that can simultaneously connect to an Oracle Server.	Required value: 200
OPEN_CURSORS	The parameter specifies the maximum number of open cursors a session can have at once, and constrains the PL/SQL cursor cache size, which PL/SQL uses to avoid reparsing statements re-executed by a user.	Required value: 600
LOG_BUFFER	Specifies the amount of memory, in bytes, that are used to buffer redo entries before they are written to a redo log file by LGWR. Redo entries keep a record of changes made to database blocks.	Required value: 5242880
OPTIMIZER_INDEX_CACHING	Adjusts the cost-based optimizer's assumptions for what percentage of index blocks are expected to be in the buffer cache for nested loops joins. This affects the cost of running a nested loop join where an index is used. Setting this parameter to a higher value makes nested loops join look less expensive to the optimizer. Range of values is 0 - 100 percent.	Required value: 90
OPTIMIZER_INDEX_COST_ADJ	Used to tune optimizer performance when too few or too many index access paths are considered. A lower value makes the optimizer more likely to select an index. That is, setting it to 50 percent makes the index access path look half as expensive as normal. Range of Values is 1 - 10000.	Required value: 50
NLS_LANG_SEMANTICS	Used to configure the database, between two values, byte or character length, it enables you to create `CHAR` and `VARCHAR2` columns using either byte or character. For example `Col1 Varchar2(20)`, is 20 bytes with byte length or 20 chars with char length. (20*4 bytes if you have defined UTF8). Existing columns are not affected. The data dictionary always uses byte semantics.	Required value: BYTE (this is the default value for Oracle).