Oracle Parameters and Their Descriptions
Oracle Parameters and Their Descriptions
Oracle Parameters and Their Descriptions
Here are some important Oracle parameters and information in the context of use with SAP
applications.
BACKGROUND_DUMP_DEST
COMPATIBLE
Defines the Oracle version whose features can be used to the greatest extent
As a rule, it must not be reset to an earlier release (see Note SAP 598470).
A value with three parts (such as 10.2.0) rather than five parts (such as 10.2.0.2.0) is
recommended to avoid changing the parameter as part of a patch set installation.
If an ORA-00201 error occurs when you try to convert the value with five parts
10.2.0.2.0 to 10.2.0, you can leave the value 10.2.0.2.0 (independent of the patch set
used).
CONTROL_FILES
CONTROL_FILE_RECORD_KEEP_TIME
Defines how many days historic data is retained in the control files
CORE_DUMP_DEST
DB_BLOCK_SIZE.
Can be set to a value higher than 8K in well-founded individual cases after it has been
approved by SAP Support (see Note 105047)
DB_CACHE_SIZE
Optimal size depends on the available memory (see Notes 789011 and 617416)
DB_FILES
DB_NAME
DB_WRITER_PROCESSES
EVENT
FILESYSTEMIO_OPTIONS
Activation of file system functions (see Note 999524 and Note 793113)
If you previously used a large file system cache (>= 2 * Oracle Buffer Pool), the
performance may get worse after you activated the direct I/O if you set
FILESYSTEMIO_OPTIONS to SETALL. Therefore, it is important that you enlarge the
Oracle buffer pool to replace the file system cache that is no longer available.
HPUX_SCHED_NOAGE
The privileges RTSCHED and RTPRIO must be assigned to the dba group to enable you
to use the functions (see Note 1285599).
LOG_ARCHIVE_DEST
LOG_ARCHIVE_DEST_1
LOG_ARCHIVE_FORMAT
To avoid the problems described in Note 132551, it must be explicitly set to WINDOWS
at least.
LOG_BUFFER
Oracle internally determines the buffer's actual size, so it is normal for "SHOW
PARAMETER LOG_BUFFER" or a SELECT on V$PARAMETER to return values
between 1MB and 16MB.
LOG_CHECKPOINTS_TO_ALERT
MAX_DUMP_FILE_SIZE
A limitation is useful to avoid file system overflows and to reduce the duration of the
dump generation.
OPEN_CURSORS
OPTIMIZER_DYNAMIC_SAMPLING
Level 2 (the default setting for Oracle 10g): Dynamic sampling is performed only if
tables do not have any statistics.
Level 6: As level 2 and includes dynamic sampling of 128 table blocks if literals are used
and there are no bind variables.
OPTIMIZER_INDEX_COST_ADJ
Adjusts the calculated index costs; when there is a value of 20 (percent), index costs are
reduced by a factor of 5, for example.
A value lower than 100 is advisable so that index accesses are preferred instead of full
table scans.
PARALLEL_EXECUTION_MESSAGE_SIZE
Defines size of the memory area for parallel query messages (in bytes)
PARALLEL_MAX_SERVERS
Defines the maximum number of parallel execution processes (see Note 651060)
The number of CPU Cores generally corresponds to the default value for the Oracle
parameter CPU_COUNT. If you are unsure in individual cases, you can use the value of
the parameter CPU_COUNT (for example, in transaction DB26).
If the database shares the server with other software (for example, SAP central instance,
other Oracle instances), you can also select a lower value (for example, 8 CPU Cores, the
SAP central instance and the Oracle database should share resources 50:50 ->
PARALLEL_MAX_SERVERS = 8 * 0.5 * 10 = 40).
PARALLEL_THREADS_PER_CPU
Defines the number of parallel query processes that can be executed in parallel for each
CPU
Influences the DEFAULT level of parallel processing during a parallel execution (see
Note 651060).
PGA_AGGREGATE_TARGET
Checks the available PGA memory (see Notes 789011 and 619876)
PROCESSES
The component relating to ABAP work processes is only relevant in systems with ABAP
stacks. The component relating to J2EE server processes is only relevant in systems with
Java stacks.
<max-connections> indicates the maximum number of connections (also called pool size)
of the J2EE system DataSource (sysDS.maximumConnections). You can set the value of
this parameter using the VisualAdmin tool or other J2EE administration tools.
QUERY_REWRITE_ENABLED
Defines whether query transformations are also factored in when the access path is
determined
RECYCLEBIN
REMOTE_OS_AUTHENT
Defines whether TCP database access via OPS$ users is allowed (see Note 400241)
REPLICATION_DEPENDENCY_TRACKING
Defines whether the system has to create replication information when the database is
accessed
SESSIONS
Defines the maximum number of Oracle sessions that exist in parallel - must be
configured larger than PROCESSES, since single processes can serve several sessions
(for example, in the case of multiple database connections from work processes)
SHARED_POOL_SIZE
Defines the size of the Oracle shared pool (see Notes 690241 and 789011)
STAR_TRANSFORMATION_ENABLED
UNDO_MANAGEMENT
UNDO_TABLESPACE
USER_DUMP_DEST
_B_TREE_BITMAP_PLANS
Defines whether data of a B*TREE index can be transformed into a bitmap display
during a database access.
_BLOOM_FILTER_ENABLED
_DB_BLOCK_NUMA
_ENABLE_NUMA_OPTIMIZATION
_FIX_CONTROL
Note 1454675 describes a problem whereby the _FIX_CONTROL values do not work
despite being displayed correctly in V$PARAMETER.
_CURSOR_FEATURES_ENABLED
With a value of 10 and in connection with fix 6795880, the following is prevented:
sporadic hanging during parsing
_FIRST_SPARE_PARAMETER
This is a generic parameter that can be used for different purposes in certain cases.
With Oracle 10.2.0.4 and fix 6904068, you use this parameter to introduce a break of
1/100 second between two "cursor: pin S" mutex requests instead of continually
executing requests. This may help to avoid critical CPU bottlenecks.
_INDEX_JOIN_ENABLED
Controls whether index joins can be used or not; within an index join, two indices of a
table are directly linked together.
_IN_MEMORY_UNDO
_OPTIM_PEEK_USER_BINDS
Defines whether Oracle takes the contents of the bind variables into account during
parsing
May cause various problems (Notes 755342, 723879) if not set to FALSE.
_OPTIMIZER_BETTER_INLIST_COSTING
If the parameter is set to OFF, long IN lists are evaluated very favorably.
The CBO performs a reasonable cost calculation for IN lists using the value ALL.
Therefore, you should always use the default value ALL (this means that you should not
set the parameter). If the CBO takes incorrect decisions in individual cases, these
incorrect decisions must be analyzed and corrected.
_OPTIMIZER_MJC_ENABLED
_PUSH_JOIN_UNION_VIEW
Controls whether join predicates may be used in a UNION ALL construct beyond the
view boundaries.
_SORT_ELIMINATION_COST_RATIO
Controls rule-based CBO decision in connection with the FIRST_ROWS hint and
ORDER BY (see Note 176754).
_TABLE_LOOKUP_PREFETCH_SIZE
Controls whether table prefetching is used (a value of zero means no table prefetching).