26.07.

2007 Page 1 of 10
Note 830576 - Parameter recommendations for Oracle 10g
Note Language: English Version: 109 Validity: Valid from 10.07.2007
Summary
Symptom
This note contains SAP's recommendations for the configuration of Oracle
Database 10g.
More Terms
init.ora, SPFILE, server parameter file
Cause and Prerequisites
This note contains SAP's recommendations for the optimal configuration of
the Oracle database with Release 10g in SAP environments.
For Oracle Release 9i or lower, refer to Note 124361 and the notes
referenced there.
Note that the recommendations given in this note may be changed. Therefore,
we recommend that you check the latest version of this note once a month
and make the necessary changes.
Previously, some parameter settings for the Oracle database (for example,
for the cost-based optimizer) depended on whether your system was a normal
R/3 system or a BW-based system. As of Oracle 10g, there is a uniform
parameterization recommendation for all systems, which is described in this
note. A few exceptions to this are indicated explicitly.
General recommendations
There are two types of parameters that should not be set in the profile:
1. Parameters that are never changed (except to analyze problems in
diagnosis situations)
2. Derived parameters, which do not normally have to be changed since
the Oracle server automatically calculates reasonable values for them
'Underscore' parameters and events are usually adjusted to a
particular Oracle release. Therefore, after a database upgrade, you should
delete this kind of parameter from the profile (exceptions are listed
below). The DBUA does not remove this type of parameter.
You should delete obsolete initialization parameters from the
profile. When you carry out a database upgrade with the DBUA, obsolete
parameters are automatically removed from the SPFILE (if an SPFILE is
used). When the instance is started, the Oracle alert log also informs you
if obsolete parameters exist. The Oracle upgrade documentation provides a
complete list of those parameters that are obsolete as of 10g. To determine
which obsolete parameters are currently set, proceed as follows:
SELECT NAME FROM V$OBSOLETE_PARAMETER WHERE ISSPECIFIED = 'TRUE';
You should not set any parameters that are not explicitly mentioned in this
26.07.2007 Page 2 of 10
Note 830576 - Parameter recommendations for Oracle 10g
note. Exceptions:
o The parameter is recommended as the solution or workaround for a
problem in another note.
o The parameter is required for implementing an individual
configuration (for example, multiple archiver destinations, check
functions, special memory settings).
Further comments on parameterization:
o For detailed information about the maintenance of parameters with
SFILEs, see Note 601157.
o If several EVENT parameters are specified in init<sid>.ora, they
must appear in consecutive rows.
o You should not set parameters that are indicated with "Do not set!"
and parameters that are not mentioned at all in the note (and for
which there is no individual customer requirements). In this case,
you use the Oracle default value, which then also appears in
V$PARAMETER or in the ST04 parameter overview. This is the intended
behavior. If you want to ensure that a parameter has not been
explicitly set, you can enter the following query (<parameter_name>
in lower case):
SELECT ISDEFAULT FROM V$PARAMETER2
WHERE NAME = '<parameter_name>';
If this returns the TRUE statement, then the parameter has not been
explicitly set.
o You can only optimize memory parameters and resource parameters
such as DB_CACHE_SIZE or DB_WRITER_PROCESSES individually.
Therefore, this note cannot give any general recommendations.
However, you can determine options for optimization on the basis of
a database performance analysis (see Notes 618868, 619188, 789011).
o The parameterization described below is directed towards the use of
the features of the dynamic SGA (Note 617416) and the automatic PGA
administration (Note 619876).
o <SAPDATA_HOME> refers to the value of the environment variable
SAPDATA_HOME.
o Paths are given in UNIX syntax. On WINDOWS, you must replace the
forward slashes ("/") with back slashes ("\").
o The terms OLAP system and OLTP system have the following meaning:
- OLAP system: These are systems with mainly BW functions (BW /
BI, APO with mainly DP usage, SEM-BPS, BW-based SEM-BCS).
- OLTP system: These are systems with mainly non-BW functions.
o Configure systems with a pure Java stack as you would an OLTP
system.
26.07.2007 Page 3 of 10
Note 830576 - Parameter recommendations for Oracle 10g
o Configure double stack systems (that is, systems with both ABAP and
JAVA stacks) as you would an OLTP or OLAP system, depending on
degree to which you use BW functions (see above).
o In individual cases, if you have a system without OLAP, you can
refrain from setting OLAP specific parameters such as
STAR_TRANSFORMATION_ENABLED, _FIX_CONTROL or _INDEX_JOIN_ENABLED to
avoid problems (for example, ORA-04031 due to _FIX_CONTROL, Note
997889) or to use functions (for example, index joins).
Solution
The standard parameter recommendations for Oracle 10.2 are listed below.
They are equally valid for all SAP products. At the end of the list, we
include specific recommendations for specific SAP or Oracle products. You
must consider these as well as the Oracle 10.2 standard recommendations:
Attached to this note is an SQL statement that you can execute using the
RSORADJV report, for example, (or alternatively using tools such as
SQLPLUS), which automatically checks that the current parameter settings
are correct. You can execute the command without changes for OLTP systems.
For OLAP systems, you need to replace "<For OLAP enter: y>" with "y" in
both places.
o Standard parameter recommendation for Oracle 10.2
o Specific settings
- Oracle 10.1
o Notes on the recommended parameters
STANDARD PARAMETER RECOMMENDATIONS FOR ORACLE 10.2
**********************************************
Parameter Recommendation
------------------------------- ------------------------------------
BACKGROUND_DUMP_DEST <SAPDATA_HOME>/saptrace/background
COMMIT_WRITE Do not set
COMPATIBLE 10.2.0
CONTROL_FILES At least three copies on
different disk areas
CONTROL_FILE_RECORD_KEEP_TIME 30 or higher
CORE_DUMP_DEST <SAPDATA_HOME>/saptrace/background
DB_BLOCK_SIZE 8192
DB_CACHE_SIZE Size depends on the available
memory (Notes 789011, 617416)
DB_FILES Larger than the number of data files
to be expected in the short term
DB_FILE_MULTIBLOCK_READ_COUNT Do not set
DB_NAME <db_name>
DB_WRITER_PROCESSES Only set in case of increased
DBWR load (Notes 79341, 789011)
EVENT
"10027 trace name context forever, level 1" (Note 596420)
26.07.2007 Page 4 of 10
Note 830576 - Parameter recommendations for Oracle 10g
"10028 trace name context forever, level 1" (Note 596420)
"10162 trace name context forever, level 1" (Notes 977319,
1040300)
"10183 trace name context forever, level 1" (Note 128648)
"10191 trace name context forever, level 1" (Note 128221)
"10629 trace name context forever, level 32" (Note 869521,
other settings of events 10626 / 10629 also allowed)
"14532 trace name context forever, level 1" (Note 1031682,
>= 10.2.0.2, Fix from Note 1031682 must be implemented)
"38068 trace name context forever, level 100" (Note 176754)
FILESYSTEMIO_OPTIONS SETALL (Note the restrictions from
Note 999524)
LOG_ARCHIVE_DEST <SAPDATA_HOME>/oraarch/<sid>arch
LOG_ARCHIVE_FORMAT %t_%s_%r.dbf
LOG_BUFFER 1048576
LOG_CHECKPOINTS_TO_ALERT TRUE
MAX_DUMP_FILE_SIZE 20000
OPEN_CURSORS 800 (up to a maximum of 2000)
OPTIMIZER_FEATURES_ENABLE Do not set
OPTIMIZER_INDEX_CACHING OLTP: 50
OLAP: Do not set.
OPTIMIZER_INDEX_COST_ADJ OLTP: 20
OLAP: Do not set.
OPTIMIZER_MODE Do not set
PARALLEL_EXECUTION_MESSAGE_SIZE 16384
PARALLEL_MAX_SERVERS #DB-CPU-Cores * 10
PARALLEL_THREADS_PER_CPU 1
PGA_AGGREGATE_TARGET OLTP: 20 % of available memory
OLAP: 40 % of available memory
PROCESSES #ABAP work processes * 2 +
#J2EE server processes *
<max-connections> +
PARALLEL_MAX_SERVERS + 40
QUERY_REWRITE_ENABLED FALSE
RECYCLEBIN OFF
REMOTE_OS_AUTHENT TRUE
REPLICATION_DEPENDENCY_TRACKING FALSE (if no replication
is used)
SESSIONS 2 * PROCESSES
SHARED_POOL_SIZE 400 MB or greater, refer to Note 690241
STAR_TRANSFORMATION_ENABLED TRUE
UNDO_MANAGEMENT AUTO (Note 600141)
UNDO_RETENTION set if required (refer to Note 600141)
UNDO_TABLESPACE PSAPUNDO (Note 600141)
USER_DUMP_DEST <SAPDATA_HOME>/saptrace/usertrace
_B_TREE_BITMAP_PLANS FALSE
_FIX_CONTROL 4728348:OFF (10.2.0.2, if
merge fix 5984705 from Note 981875
is not implemented; see Notes
964858 and 997889)
_INDEX_JOIN_ENABLED FALSE (10.2.0.2, refer to Note
964858)
_IN_MEMORY_UNDO FALSE (up to and including 10.2.0.3, if
fixes from
Notes 980805 and 1013476
are not implemented)
_OPTIM_PEEK_USER_BINDS FALSE (see Note 755342)
_OPTIMIZER_MJC_ENABLED FALSE (Note 176754 (30))
26.07.2007 Page 5 of 10
Note 830576 - Parameter recommendations for Oracle 10g
_SORT_ELIMINATION_COST_RATIO 10 (See Note 176754 (16))
ORACLE 10.1: ADDITIONAL/ALTERNATIVE PARAMETER SETTINGS
*********************************************************
Parameter Recommendation
------------------------------- ------------------------------------
COMPATIBLE 10.1.0
EVENT 10040 (Level 1, Note 899070)
RECYCLEBIN Do not set
_OPTIMIZER_OR_EXPANSION DEPTH (10.1.0.5 or higher, Note 849229)
_PGA_MAX_SIZE Only for BW:
400MB as of PGA_AGGREGATE_TARGET>4G
600MB as of PGA_AGGREGATE_TARGET>8G
800MB as of PGA_AGGREGATE_TARGET>12G
_RECYCLEBIN FALSE
NOTES ON THE RECOMMENDED PARAMETERS
*****************************************
o BACKGROUND_DUMP_DEST
- Path for alert log and background trace files
o 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
598470).
- A value with three parts (such as 10.2.0) rather than five
parts (such as 10.2.0.3.0) is recommended to avoid changing the
parameter as part of a patch set installation.
o CONTROL_FILES
- Path and name of the control files that are used
o CONTROL_FILE_RECORD_KEEP_TIME
- Defines how many days historic data is retained in the control
files
- Historic data is required by RMAN, for example.
- May cause control files to increase in size (see Note 904490)
o CORE_DUMP_DEST
- Path under which core files are stored
o DB_BLOCK_SIZE.
26.07.2007 Page 6 of 10
Note 830576 - Parameter recommendations for Oracle 10g
- Size of an Oracle block
- 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)
o DB_CACHE_SIZE
- Size of the Oracle data buffer (in bytes)
- Optimal size depends on the available memory (see Notes 789011
and 617416)
o DB_FILES
- Maximum number of Oracle data files
o DB_NAME
- Name of the database
o DB_WRITER_PROCESSES
- Number of DBWR processes
o EVENT
- Activation of internal control mechanisms and functions
- To set events in SPFILE, refer also to Note 596423.
- On Oracle 10.1, set the events for 10.1 in addition to, and not
instead of, the events for 10.2.
o 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.
o LOG_ARCHIVE_DEST
- Path/prefix for offline redo logs
o LOG_ARCHIVE_FORMAT
- Name format of the offline redo logs
- To avoid the problems described in Note 132551, it must be
explicitly set to WINDOWS at least.
26.07.2007 Page 7 of 10
Note 830576 - Parameter recommendations for Oracle 10g
o LOG_BUFFER
- Minimum size of the Oracle redo buffer (in bytes)
- 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.
o LOG_CHECKPOINTS_TO_ALERT
- Defines whether checkpoints are to be logged in the alert log
o MAX_DUMP_FILE_SIZE
- Maximum size of Oracle trace files (in operating system blocks)
o OPEN_CURSORS
- Maximum number of cursors opened in parallel by one session
o PARALLEL_EXECUTION_MESSAGE_SIZE
- Defines size of the memory area for parallel query messages (in
bytes)
o PARALLEL_MAX_SERVERS
- Defines the maximum number of parallel query processes (see
Note 651060)
- Based on the number of CPU Cores of the database server
- If the database shares the server with other software (for
example, SAP central instance, other Oracle instances), only
the part of the CPU Cores that is mathematically available to
the database should be considered in the calculation (for
example, 8 CPU Cores, the SAP central instance and the Oracle
database are to share resources 50:50 -> PARALLEL_MAX_SERVERS =
8 * 0.5 * 10 = 40).
o PARALLEL_THREADS_PER_CPU
- Defines the number of parallel query processes that can be
executed in parallel for each CPU
o PGA_AGGREGATE_TARGET
- Checks the available PGA memory (see Notes 789011 and 619876)
o PROCESSES
- Defines the maximum number of Oracle processes that exist in
parallel
- 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.
26.07.2007 Page 8 of 10
Note 830576 - Parameter recommendations for Oracle 10g
- <max-connections> indicates the maximum number of connections
(also called pool size) of the J2EE system DataSource. You can
set the value of this parameter using the VisualAdmin tool or
other J2EE administration tools.
o QUERY_REWRITE_ENABLED
- Defines whether query transformations are also factored in when
the access path is determined
o RECYCLEBIN
- Enables access later on to objects that have already been
dropped
- Not supported by SAP (see Note 105047)
o REMOTE_OS_AUTHENT
- Defines whether TCP database access via OPS$ users is allowed
(see Note 400241)
o REPLICATION_DEPENDENCY_TRACKING
- Defines whether the system has to create replication
information when the database is accessed
- Performance improves if it is deactivated
o 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)
o SHARED_POOL_SIZE
- Defines the size of the Oracle shared pool (see Notes 690241
and 789011)
o STAR_TRANSFORMATION_ENABLED
- Specifies to what extent STAR transformations can be used
o UNDO_MANAGEMENT
- Defines whether automatic undo management is used (see Note
600141)
o UNDO_TABLESPACE
- Defines the undo tablespace to be used (see Note 600141)
o USER_DUMP_DEST
- Path for trace files of Oracle shadow processes
26.07.2007 Page 9 of 10
Note 830576 - Parameter recommendations for Oracle 10g
o _B_TREE_BITMAP_PLANS
- Defines whether data of a B*TREE index can be transformed into
a bitmap display within a database access
o _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.
o _SORT_ELIMINATION_COST_RATIO
- Controls rule-based CBO decision in connection with the
FIRST_ROWS hint and ORDER BY (Note 176754)
Header Data
Release Status: Released for Customer
Released on: 10.07.2007 07:57:34
Priority: Recommendations/additional info
Category: Installation information
Main Component BC-DB-ORA Oracle
The note is not release-dependent.
Related Notes
Number Short Text
1044174 Recommendation for CC 5.x running on Oracle 10G Database
1040300 Wrong values with Star Transformation Hint 9.2.0.8 /10.2.0.2
1031682 ORA-04031 due to shared pool component "mvobj part des"
1013912 FAQ: Oracle BW Performance
1013476 ORA-600 kcbzpbuf_1 during array insert causes corruption
1009332 Central note SAP NetWeaver 2004s Rapid Installer for SPS 11
999524 Oracle 10.2 platform support for Async IO
999126 Performance improvement for star queries
997889 Error ORA-04031 due to "_fix_control"
980805 ORA-600 kdtigetrow-2 w/ array insert leads to corruptions
977319 Incorrect values in Oracle 10.2 (II)
26.07.2007 Page 10 of 10
Note 830576 - Parameter recommendations for Oracle 10g
Number Short Text
964858 Incorrect vals w/ STAR_TRANSFORMATION_ENABLED in Oracle 10.2
960633 Merge Join Cartesian in complex join
948294 AIX JFS2: mount options to use with Oracle 10g
934808 Further configuration of Oracle10g for SAP Enterprise Portal
914177 File system reiserfs Oracle parameter filesystemio_options
900345 Backward Release of ORACLE 10.2 - Upgrade Information
899070 ORA-01406 reported on SELECT against SAP Tables (eg.TRDIR)
848708 Oracle Database Configuration for NWDI server
819830 Oracle Database 10g: Additional Information on upgrade:UNIX
819655 Add. info.: Upgrade to SAP NW 2004s ABAP ORACLE
789011 FAQ: Oracle memory areas
755342 Incorrect execution plans with bind variable peeking
720886 Oracle Database 10g: Integration into the SAP environment
690241 The Shared SQL Area in the Shared Pool and large SQL Stmnts
632556 Oracle 9.2.0.* database parameterization for BW
619876 Oracle9i: Automatic PGA Memory Management
619188 FAQ: Oracle wait events
618868 FAQ: Oracle performance
617416 Oracle9i: Dynamic SGA
601157 Oracle9i: Server Parameter File
600141 Oracle9i: Automatic UNDO Management
596423 Events and SPFILE
596420 System standstill during deadlock (ORA-60)
592393 FAQ: Oracle
378509 Oracle DB parameter setting for APO
192055 Warnings despite correct parameter values
180605 Oracle database parameter settings for BW
176754 Problems with CBO and RBO
132551 Overflow log sequence numbers on NT
128221 Increased memory consumption with Oracle >8.0.X
124361 Oracle parameterization (R/3 >= 4.x, Oracle 8.x/9.x)
79341 Checkpoint not complete
Attachments
File Type File Name Language Size
TXT parameters.txt E 39 KB