0% found this document useful (0 votes)
142 views22 pages

Oracle 19c Parameter Recommendations

This SAP note provides parameter recommendations for Oracle databases used in SAP NetWeaver systems, specifically for versions 12c, 18c, and 19c. It emphasizes that these settings are validated for SAP products and may not be applicable to non-SAP applications. Users are advised to regularly check for updates and apply necessary changes, especially after database patches.

Uploaded by

sandeepfromooty
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
142 views22 pages

Oracle 19c Parameter Recommendations

This SAP note provides parameter recommendations for Oracle databases used in SAP NetWeaver systems, specifically for versions 12c, 18c, and 19c. It emphasizes that these settings are validated for SAP products and may not be applicable to non-SAP applications. Users are advised to regularly check for updates and apply necessary changes, especially after database patches.

Uploaded by

sandeepfromooty
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

2021-11-02 2470718

2470718 - Oracle Database Parameter 12.2 / 18c / 19c


Version 50 Type SAP Note
Language English Master Language English
Priority Recommendations / Additional Info Category Consulting
Release Status Released for Customer Released On 24.08.2021
Component BC-DB-ORA ( Oracle )

Please find the original document at [Link] 2470718

Symptom

Oracle Database Parameter

This SAP note contains parameter recommendations for an Oracle database of an SAP Netweaver system.

Validity of Recommendations

The recommendations are valid for Oracle Database 12c Release 2 (12.2), Oracle Database 18c and Oracle
Database 19c.

All parameter recommendations provided in this note are targeted for SAP NetWeaver-based SAP products
and Solutions. Parameter settings are tested in SAP customer systems and proven by customer experience
in these SAP environments. There is no guarantee from our side that these settings work reasonably well for
other non-SAP products and applications.

Note for SAP Manufacturing Execution (SAP ME) on Oracle:

• SAP applications 'SAP ME' and 'SAP MII/MEINT' are based on SAP NetWeaver. For Oracle databases
of these SAP applications please follow this SAP note.
• However, parameter and configuration requirements for 'SAP ME WIP' and 'SAP ME ODS' databases
are different. For these Oracle databases you must follow SAP Note 1405260.

Updates and Changes

Parameter recommendations in this SAP Note are subject to change. It is therefore recommended to
regularly check the latest version of this note and apply the necessary changes to the database, if needed.

Database Patching

Applying a new database patch may affect parameter settings. Whenever new database patches are
released on Oracle Patchdays, this note is reviewed and updated, if necessary. Beyond that, changes will be
made only in exceptional cases for critical Oracle parameters.

Automated Database Parameter Check

You can check whether your SAP database is configured according to the recommendations of this note
using the SQL script from SAP Note 1171650.

Change History (Latest Changes)

This is the list of latest changes. You find the history of older changes (older than a year) archived at the end
of this SAP Note.

Date Reason Change

© 2021 SAP SE or an SAP affiliate company. All rights reserved 1 of 22


2021-11-02 2470718
Added info for "_use_single_log_writer": set for better performance Added info for
"local_listener": set in RAC, ASM or MT environments Added "(SAP_OLAP)" for SAP NW
OLAP specific parameter (SAP BW) Added "(SAP_OLTP)" for SAP NW OLTP specific
2021- parameter (SAP Non-BW) Added "_fix_control"='22387320:ON' Added
Patchday
08-24 "_fix_control"='28708585:ON' Added "_fix_control"='30142527:ON' Added
"_fix_control"='31082719:ON' Added "_fix_control"='31496840:ON' Added
"_fix_control"='31821701:ON' Added "_fix_control"='31961578:ON' Added
"_fix_control"='32107621:ON' Adjusted "_fix_control"='31143146:ON'
2021-
Hotnews Adjusted "_oltp_compress_dbg", Hotnews SAP Note 3076328
07-26
Added "_column_tracking_level" Added "_fix_control"='24561942:ON' Added
"_fix_control"='28173995:ON' (missed to include in 19c 202105 SBP readmes) Added
"_fix_control"='28414968:3' Added "_fix_control"='29385774:ON' Added
"_fix_control"='29867728:ON' (missed to include in 19c 202105 SBP readmes) Added
"_fix_control"='30008456:ON' Added "_fix_control"='30235691:ON' Added
2021- "_fix_control"='30249927:ON' Added "_fix_control"='30470947:ON' Added
Patchday
05-20 "_fix_control"='30483217:ON' Added "_fix_control"='30776676:ON' Added
"_fix_control"='30786641:ON' Added "_fix_control"='31009032:ON' Added
"_fix_control"='31143146:ON' Added "_fix_control"='32014520:ON' Added
"_fix_control"='28234255:3' Adjusted "_fix_control"='28234255:ON' Adjusted
"_fix_control"='28602253:ON' Adjusted "_fix_control"='29302565:ON' Adjusted
"_fix_control"='30537403:ON'
Added "_fix_control"='28999046:ON' Added "_fix_control"='29302565:ON' Added
"_fix_control"='29487407:ON' Removed "_fix_control"='30616738:ON' ([Link].210119
2021-
Patchday SBP 202102 Readme sets '30616738:OFF' which is the default value and therefore
02-18
should not be set explicitly) Adjusted '28602253:ON' Adjusted '29930457:ON' Adjusted
'31444353:1'
Added "_fix_control"='31444353:1' Added "_fix_control"='30616738:ON' Added
2020-
Patchday "_fix_control"='30537403:ON' Added "_fix_control"='28234255:ON' Added
11-30
"_fix_control"='27500916:OFF' (SAP Note 2999193)
2020-
Info Adjusted "_fix_control"='30195773:ON'
09-23
2020-
Info Adjusted "_optimizer_cbqt_or_expansion" (SAP Note 2806210)
09-09
2020-
Patchday Adjusted "_fix_control"='29304314:ON'
08-26
Adjusted "_fix_control"='29930457:ON' Added "_fix_control"='28498976:ON' Added
2020-
Patchday "_fix_control"='29304314:ON' Added "_fix_control"='30195773:ON' Added
08-23
"_fix_control"='30231086:ON'
Adjusted "_fix_control"='27343844:ON' Adjusted "_fix_control"='28835937:ON' Adjusted
2020- "_fix_control"='29450812:ON' Adjusted "_fix_control"='29687220:ON' Added
Patchday
05-15 "_fix_control"='29930457:ON' Added "_enable_ptime_update_for_sys" (SAP Note
2860512) Added "_ipddb_enable" (SAP Note 2919894)
Added "_optimizer_gather_stats_on_conve
2020-
Info ntional_dml", Exadata only Added "_optimizer_use_stats_on_conventi
04-07
onal_dml", Exadata only
2020-
Hotnews Added "_oltp_compress_dbg", Hotnews SAP Note 2719005
04-07

© 2021 SAP SE or an SAP affiliate company. All rights reserved 2 of 22


2021-11-02 2470718
2020- Updated "wallet_root" - ASO license required for TDE (ORA_LICENSE) Added
Info
02-27 "tde_configuration" - ASO license required for TDE (ORA_LICENSE)
2020-
Patchday Added "_fix_control"='29687220:ON' Adjusted '28558645:ON' Adjusted '29450812:ON'
02-13
Added "wallet_root" (SAP Note 2591575) Added "tde_configuration" (SAP Note 2591575)
2020-
Info Added "max_pdbs" Updated "db_create_online_log_dest_2" recommendation for Exadata
02-13
Updated "disk_asynch_io" (SAP Note 2799946)
2019-
Info Updated "_partial_comp_enabled" for 19c, Hotnews SAP Note 2780131
12-19
2019-
Info Updated parameter recommendations for Oracle Database 19c
12-18
2019-
Info Added parameter recommendations for Oracle Database 19c
12-12
2019-
Hotnews Added "_partial_comp_enabled", Hotnews SAP Note 2780131
12-09
2019-
Info Added recommendation for SAP Manufacturing Execution (SAP ME)
11-19
2019-
Patchday Added "_enable_ptime_update_for_sys" (SAP Note 2860512)
11-15
2019- Adjusted "_fix_control"='23738304:OFF' resp. '23738304:ON' (SAP Note 2522894) Added
Patchday
11-14 "_fix_control"='27343844:ON' Added "_fix_control"='28602253:ON'
2019-
Patchday Adjusted "_optimizer_cbqt_or_expansion" (SAP Note 2806210)
08-20
2019- Added "_fix_control"='7658097:ON' Added "_fix_control"='29450812:ON' (SAP Note
Patchday
08-15 2806210) Added "_optimizer_cbqt_or_expansion" (SAP Note 2806210)
2019-
Hotnews Added "_in_memory_undo", Hotnews SAP Note 2812178 , non-RAC systems only
07-15
2019-
Patchday Rephrased 18c setting of "_fix_control"='28072567:ON'
06-18
2019- Added parameter recommendations for Oracle Database 18c Added
Patchday
06-05 "_fix_control"='26423085:ON' Added "_fix_control"='28072567:ON'
Removed "_optimizer_batch_table_access_by
2019-
Patchday _rowid" (see SAP Notes 2240098, 2611764) Updated "disk_asynch_io" additional
06-04
information
Added parameter recommendations for Oracle Database 12.2 Added "os_authent_prefix"
Added parameter recommendations for Oracle Database 18c Adjusted "compatible"
2019-
Patchday Adjusted "processes" Added "os_authent_prefix" Added "_disable_directory_link_check"
03-01
Added "_kolfuseslf'" Added "_fix_control"='28558645:ON' Added
"_fix_control"='28835937:ON'
Adjusted "_fix_control"='20107874:OFF' Adjusted "_fix_control"='20107874:ON' Adjusted
2019-
Patchday "_fix_control"='27466597:ON' Added "_fix_control"='26423085:ON' Added
02-21
"_fix_control"='28072567:ON'
Added Hotnews SAP Note 2500176 to parameter
2019-
Hotnews "_ADVANCED_INDEX_COMPRESSION_OPTI
01-22
ONS"
2018- Patchday Adjusted "_fix_control"='20355502:10' (SAP Note 2698967) Added

© 2021 SAP SE or an SAP affiliate company. All rights reserved 3 of 22


2021-11-02 2470718
11-23 "_fix_control"='8932139:ON'
2018-
Patchday Added "_fix_control"='23643560:ON'
10-08
2018-
Patchday Added "_fix_control"='26536320:ON'
10-01
2018-
Patchday Adjusted "_fix_control"='20107874:OFF' Adjusted "_fix_control"='20107874:ON'
06-04
2018- Automated Database Parameter Check Script for 12.2 is available (SAP Note 1171650)
Patchday
06-01 Added "_fix_control"='27466597:ON'
2018- Updated "disk_asynch_io" Added "_fix_control"='25476149:ON' Added
Patchday
02-15 "_fix_control"='27321179:ON' Removed "_fix_control"='14846352:OFF'
2017-
Released Initial version released based on minimum bundle patch version 201711
12-18

Other Terms

[Link], init<SID>.ora, [Link], SPFILE, Server Parameter File

Reason and Prerequisites

Parameter recommendations in this note are valid for SAP products or SAP solutions based on SAP
NetWeaver running on Oracle Database 12c Release 2 ([Link]), Oracle Database 18c or Oracle Database
19c.

This SAP Note is valid for Unix and Windows platforms.

Solution

Overview and General Recommendations

Oracle database parameter settings are stored and configured in the Oracle database server parameter file
(SPFILE, see SAP note 601157). For further information on Oracle database parameters, SPFILE
management and parameter checking for an SAP database see SAP note 2378252.

General Rule

Obsolete or desupported database parameters are not set. As a general rule, database parameters that are
not explicitly mentioned in this SAP note must not be set in an SAP database. Exceptions to this rule are:

1) The parameter is recommended in another SAP note as -temporary- solution or workaround for a
problem.
2) The parameter is required to implement an individual database configuration.

Parameter containing a Path Value

Database parameters with path values are specified with forward slashes '/' for UNIX platforms. On
WINDOWS, you must replace the forward slashes '/' with back slashes '\'.

SAP Application Type (OLTP or OLAP)

Depending on the SAP application an SAP system is either an Online Transaction Processing (OLTP) system
or an Online Analytical Processing (OLAP) system. The database needs to be configured accordingly.

© 2021 SAP SE or an SAP affiliate company. All rights reserved 4 of 22


2021-11-02 2470718

• SAP NW OLTP parameter settings are marked with "(SAP_OLTP)".


• SAP NW OLAP parameter settings are marked with "(SAP_OLAP)".
• In non-cdb databases OLTP or OLAP specific parameters are configured in the SPFILE.
• In multitenant databases OLTP or OLAP specific parameters are configured on PDB level. For more
information see SAP Note 3044733.

The SAP database for an SAP system with mainly BW functions should be configured as an OLAP system:

• SAP Advanced Planning and Optimization (APO)


• SAP Business Warehouse (BW), SAP Business Information Warehouse (BI)
• SAP Strategic Enterprise Management (SEM, SEM-BPS, BW-based SEM-BCS)

The SAP database for an SAP system with mainly non-BW functions should be configured as an OLTP
system:

• Bank Analyzer
• SAP systems with a pure Java stack

The SAP database of an SAP double stack or MCOD system should be configured as an OLTP or OLAP
system, depending on the degree to which you use BW functions (see above).

Memory Parameter (SGA)

Memory parameters and resource parameters such as DB_CACHE_SIZE or DB_WRITER_PROCESSES


must be configured individually. It is not possible to give general recommendations for these type of
parameters. You can determine options for optimization on the basis of a database performance analysis
(see SAP Notes 618868, 619188, 789011). 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).
The "Available Memory" which is referred to in some of the following parameters is the [physical] memory,
that is available and dedicated for the Oracle database instance.

Parameter Check for SAP Database

You can check the database parameter configuration of your SAP database using the SQL script from SAP
Note 1171650.

Minimum Bundle Patch Requirements

For Oracle Database [Link] (see SAP Note 2470660), the following bundle patches or a higher version
must be installed:

Platform Minimum Patch Requirements [Link]


Windows Windows Database Bundle Patch [Link].171130 (PATCHBUNDLE12201P_1711) or later
Unix SAP Bundle Patch November 2017 ([Link].171017 - 201711) or later

For Oracle Database 18c (see SAP Note 2660020), the following bundle patches or a higher version must be
installed:

Platform Minimum Patch Requirements 18c


Windows Windows Database Bundle Patch [Link].190115 or later
Unix SAP Bundle Patch January 2019 ([Link].190115 - 201902) or later

For Oracle Database 19c (see SAP Note 2799900), the following bundle patches or a higher version must be

© 2021 SAP SE or an SAP affiliate company. All rights reserved 5 of 22


2021-11-02 2470718

installed:

Platform Minimum Patch Requirements 19c


Windows Windows Database Bundle Patch [Link].191015 or later
Unix SAP Bundle Patch January 2019 ([Link].191115 - 201911) or later

If no bundle patch is installed (which is not supported), some "_fix_control" values can not be set and you
would see the following error:

ALTER SYSTEM SET "_FIX_CONTROL"='<value>' scope=spfile


*
ERROR at line 1:
ORA-32017: failure in updating SPFILE
ORA-02097: parameter cannot be modified because specified value is invalid

SAP Note Structure

This SAP note is structured into the following sections:

SAP Note Section Explanation


'Database Parameter Settings Valid for all Oracle installation types (Standard, Hidden, EVENT,
(Basic)' _FIX_CONTROL )
'Database Parameter Settings for Valid only for Oracle installations of type Single Instance on file system
SI/FS' (SI/FS), must be set in addition to basic settings
'Database Parameter Settings for Valid only for Oracle installations of type RAC (incl. RAC on Oracle
RAC' Engineered Systems), must be set in addition to basic settings
'Database Parameter Settings for Valid only for Oracle installations on ASM (except Oracle Engineered
ASM' Systems), must be set in addition to basic settings
'Database Parameter Settings for Valid only for Oracle installations on Oracle Engineered Systems, must
Oracle Engineered Systems' be set in addition to basic settings
'Database Parameter Settings for Valid only for specific platforms, must be set in addition to basic
Specific Platforms' settings

Parameter Flags and Properties

In this note, the following flags are used to classify parameters.

Note: Without a flag, the parameter setting is valid for all Oracle releases and for all operating systems /
platforms (Unix and Windows).

Parameter Flag Explanation


WIN <condition> This parameter is valid for Windows Platforms (if <condition> is true).
UNIX <condition> This parameter is valid for UNIX Platforms (if <condition> is true).
(ORA_LICENSE) This parameter requires a certain Oracle license.
(DO_NOT_SET) This parameter must not be set.
This parameter is configured for SAP NW OLTP systems (Multitenant: SAP Note
(SAP_OLTP)
3044733).
(SAP_OLAP) This parameter is configured for SAP NW OLAP systems (Multitenant: SAP Note

© 2021 SAP SE or an SAP affiliate company. All rights reserved 6 of 22


2021-11-02 2470718
3044733).
WIN <ora_rel> This parameter is valid for Oracle Release <rel> on Windows.
UNIX <ora_rel> This parameter is valid for Oracle Release <rel> on Unix.
WIN 12.2 / WIN [Link] This parameter is valid for 12.2 on Windows.
UNIX 12.2 / UNIX
This parameter is valid for 12.2 on Unix.
[Link]
WIN 18 This parameter is valid for 18c on Windows.
UNIX 18 This parameter is valid for 18c on Unix.
WIN 19 This parameter is valid for 19c on Windows.
UNIX 19 This parameter is valid for 19c on Unix.

Database Parameter Settings (Basic)

The table below contains SAP's basic parameter recommendations. These parameters are basic for every
SAP Oracle database, independent of the installation type.

The basic parameters are divided into the following 2 categories: Standard database parameter and Hidden
(underscore) database parameter. Standard parameter are mostly configured by SWPM while hidden
parameters mostly need to be set manually. Especially after applying a new database patch the standard
parameter 'event' and the hidden parameter '_fix_control' need special attention.

Standard Database Parameter

The following database parameters are standard for an SAP database.

Parameter Name Recommended Parameter Value Additional Information


SAP default directory for
audit_file_dest <SAPDATA_HOME>/saptrace/audit
AUDIT_TRAIL files
background_dump_dest - (DO_NOT_SET)
commit_logging - (DO_NOT_SET)
commit_wait - (DO_NOT_SET)
commit_write - (DO_NOT_SET)
(SAP note 1739274) UNIX 12.2
'[Link].0'
WIN 12.2
(SAP note 1739274) UNIX 18 WIN
compatible '18.0.0'
18
(SAP note 1739274) UNIX 19 WIN
'19.0.0'
19
Minimum number of days before a
control_file_record_keep_time 30 or higher record in the CF can be overwritten
(default is 7 days).
(ORA_LICENSE): License required:
Oracle Diagnostic Pack, Oracle
Tuning Pack
control_management_pack_access DIAGNOSTIC+TUNING
'DIAGNOSTICS+TUNING' is the
Oracle default value for this
parameter in the Oracle Enterprise

© 2021 SAP SE or an SAP affiliate company. All rights reserved 7 of 22


2021-11-02 2470718
Edition. If these packs are not
licensed, you must set this
parameter to ‘NONE’.
core_dump_dest - (DO_NOT_SET)
db_block_size 8192 Size of Oracle database block
Size depends on the available
db_cache_size <size of database buffer cache> memory (SAP notes 789011,
617416)
typically > 200 (valid for ASM and
db_files <number of database datafiles>
non-ASM)
db_file_multiblock_read_count - (DO_NOT_SET)
SAP database name (3
db_name <DBNAME> alphanumeric characters, starting
with an alphabetic character)
SAP default directory for diagnostic
diagnostic_dest <SAPDATA_HOME>/saptrace files (incident files, trace files and
log files)
(ORA_LICENSE): License required:
Oracle Multitenant (SAP note
2336881) For single tenant - CDB
with only one PDB - a license for
CDB: TRUE Non-CDB: not set
enable_pluggable_database Oracle multitenant is not needed.
(=FALSE)
For Multitenant - CDB with 2 or
more PDBs - a license for Oracle
Multitenant is needed. For Non-CDB
this parameter must not be set.
filesystemio_options SETALL -
(ORA_LICENSE): License required:
Oracle Advanced Compression
Enables Heat Map and Automatic
heat_map ON Data Optimization (ADO) features.
(SAP Note 2254866) Set
heat_map=ON only if ADO/ILM is
used.
Set this parameter only if parameter
PRIORITY HIGH On
inmemory_size > 0. This parameter
inmemory_clause_default Exadata/SuperCluster: PRIORITY
improves performance and high
HIGH DUPLICATE ALL
availability of the IM column store.
Set this parameter only if parameter
inmemory_size > 0. This parameter
inmemory_max_populate_servers 4 limits the resources for column store
background processing on a
system.
(ORA_LICENSE): License required:
Oracle Database In-Memory A
inmemory_size <Size of the IM Column Store>
value > 0 enables the In-memory
column store
log_archive_format %t_%s_%[Link] SAP default filename format for
© 2021 SAP SE or an SAP affiliate company. All rights reserved 8 of 22
2021-11-02 2470718
archive log files
log buffer size, set according to SAP
log_buffer <size of log buffer>
note 1627481.
Logging checkpoints in the alert log
log_checkpoints_to_alert TRUE provides useful information about
checkpoint frequency.
Limit size of trace files generated by
max_dump_file_size 20000 the Oracle database (Default is
UNLIMITED)
only for container databases (CDB)
with
3 without multitenant license; 3 or
max_pdbs enable_pluggable_database=TRUE;
higher with multitenant license
see Oracle Database 19c License
Guide UNIX 19 WIN 19
nls_length_semantics - (DO_NOT_SET)
open_cursors 800 (up to a maximum of 2000)
(DO_NOT_SET) Desupported in
[Link], replaced by
optimizer_adaptive_features -
'optimizer_adaptive_plans' and
'optimizer_adaptive_statistics'
New parameter in [Link], replaces
optimizer_adaptive_plans FALSE
optimizer_adaptive_features
New parameter in [Link], replaces
optimizer_adaptive_statistics FALSE
optimizer_adaptive_features
(SAP_OLTP): Do not set!
optimizer_dynamic_sampling Multitenant: see SAP Note 3044733
(SAP_OLAP): 6
optimizer_features_enable - (DO_NOT_SET)
optimizer_index_caching - (DO_NOT_SET)
(SAP_OLTP): 20 (SAP_OLAP): Do not
optimizer_index_cost_adj Multitenant: see SAP Note 3044733
set!
optimizer_mode - (DO_NOT_SET)
Only for databases with container
database architecture (CDB,
os_authent_prefix CDB: C##OPS$ Non-CDB: not set
multitenant or singletenant), (SAP
note 2336881)
16384 is the typical default value on
parallel_execution_message_size 16384
most platforms
A value of zero ensures that no
processes that are needed for
parallel_min_servers 0
parallel operations are created at
instance startup.
#DB-CPU-Cores is equivalent to
parallel_max_servers #<DB-CPU-Cores> * 10 'CPU_COUNT' (SQL> show
parameter cpu_count)
parallel_threads_per_cpu 1 -

© 2021 SAP SE or an SAP affiliate company. All rights reserved 9 of 22


2021-11-02 2470718
OLTP: 20 % of available memory
pga_aggregate_target -
OLAP: 40 % of available memory
PRE_PAGE_SGA determines
whether Oracle reads the entire
SGA into memory at instance
startup. Oracle Default is TRUE. For
pre_page_sga FALSE
SAP NetWeaver installations this
parameter must be set to FALSE.
Reference: Oracle Database
Reference, PRE_PAGE_SGA
(#ABAP work processes * 2) + (#J2EE max. number of OS processes that
server processes * <max-connections> can simultaneously connect to the
) + PARALLEL_MAX_SERVERS + 40 database. UNIX 12.2 WIN 12.2
max. number of OS processes that
can simultaneously connect to the
processes database. UNIX 18 WIN 18 UNIX 19
(#ABAP work processes * 2) + (#J2EE
WIN 19 In 18c, the number of
server processes * <max-connections>
background processes has
) + PARALLEL_MAX_SERVERS + 100
increased compared to 12.2. SQL>
select count(*) from v$process
where background = 1;
query_rewrite_enabled FALSE -
recyclebin OFF -
remote_os_authent - (DO_NOT_SET)
Set to FALSE if Oracle Replication
replication_dependency_tracking FALSE is not used (Oracle default is
TRUE).
sessions 2 * <PROCESSES> -
shared_pool_size 400MB or more (SAP Note 690241)
(SAP_OLTP): Do not set!
star_transformation_enabled Multitenant: see SAP Note 3044733
(SAP_OLAP): TRUE
(ORA_LICENSE): Advanced
Security Option (ASO) Set only if
tde_configuration 'KEYSTORE_CONFIGURATION=FILE'
TDE is used (SAP Note 2591575)
UNIX 18 WIN 18 UNIX 19 WIN 19
undo_retention set if required (SAP Note 1035137)
The Oracle timestamp format in log
and trace files (e.g. [Link]) has
been changed to universal time
uniform_log_timestamp_format FALSE
format. For SAP the old timestamp
format is retained in 12.2.
Reference
user_dump_dest - (DO_NOT_SET)
(ORA_LICENSE): Advanced
Security Option (ASO) Set only if
wallet_root <tde software keystore location>
TDE is used (SAP Note 2591575)
UNIX 18 WIN 18 UNIX 19 WIN 19

© 2021 SAP SE or an SAP affiliate company. All rights reserved 10 of 22


2021-11-02 2470718

Hidden (Underscore) Database Parameter

The following hidden database parameters are standard for an SAP database.

Recommended
Parameter Remark and Explanation
Value
(ORA_LICENSE): License required: Oracle
Advanced Compression All newly created indexes
will be compressed by default (Reference: SAP
_advanced_index_compression_optio Note 2138262). (Hot News 2500176) If you
16
ns upgraded your database to release [Link], you
might have configured this parameter unintentionally
without Oracle license. For more information, see
HOTNEWS 2500176.
Avoid high CPU load due to Optimizer Expression
_column_tracking_level 1
Statisics UNIX 19 WIN 19
Required for patching (catsbp, datapatch) UNIX 18
_disable_directory_link_check TRUE
WIN 18 UNIX 19 WIN 19
(SAP Note 2860512) UNIX [Link].x_date ( date
>= 201908 ) WIN [Link].nP ( n >= 190228 ) UNIX
18.y.0.0.x_date ( y >= 7 and date >= 201908 ) WIN
_enable_ptime_update_for_sys TRUE
[Link] ( y >= 9 and n >= 200114 ) UNIX
19.y.0.0.x_date ( y >= 4 and date >= 201908) WIN
[Link] ( y >= 6 and n >= 200114 )
(Hot News 2812178, non-RAC systems only) UNIX
[Link].x_date ( date <= 201902 ) WIN [Link].nP
_in_memory_undo FALSE ( n < 190228 ) UNIX 18.y.0.0.x_date ( y <= 5 and
date <= 201902 ) WIN [Link] ( y <= 5 and n <
190416 )
_ipddb_enable - (DO_NOT_SET) (SAP Note 2919894)
Required for patching (catsbp, datapatch) UNIX 18
_kolfuseslf TRUE
WIN 18 UNIX 19 WIN 19
(Oracle Support Document 2049516.1), avoid
_log_segment_dump_parameter FALSE dumping parameter info into alert log when [Link]
reaches file size limit
(Oracle Support Document 2049516.1), avoid
_log_segment_dump_patch FALSE dumping patch info into alert log when [Link]
reaches file size limit
(SAP Note 2335159) UNIX 19 (SAP BW
_min_lwt_lt 4 (SAP_OLAP) with in_memory_size > 0) WIN 19
(SAP BW (SAP_OLAP) with in_memory_size > 0)
_mutex_wait_scheme 1 (SAP Note 1588876)
_mutex_wait_time 10 (SAP Note 1588876)
(Hot News 2719005 ) disable oltp array insert
optimization UNIX [Link].x_date ( date = 202002 )
_oltp_compress_dbg 1 UNIX 18.y.0.0.x_date ( y = 9 and date = 202002 )
(Hot News 3076328 ) disable oltp array insert
optimization if Manual Segment Space Management
© 2021 SAP SE or an SAP affiliate company. All rights reserved 11 of 22
2021-11-02 2470718
(MSSM) is still being used UNIX [Link] WIN
[Link] UNIX 18 WIN 18 UNIX 19.y.0.0.x_date ( y
<= 11 and date <= 202105 ) WIN [Link] ( y <=
11 and date <= 210420 )
_optim_peek_user_binds FALSE (SAP Note 755342)
_optimizer_adaptive_cursor_sharin
FALSE -
g
(SAP Note 2806210) UNIX [Link].x_date ( date
<= 201905 ) WIN [Link].nP ( n <= 200414) UNIX
18.y.0.0.x_date ( y <= 6 and date <= 201905 ) WIN
_optimizer_cbqt_or_expansion OFF
[Link] ( y <= 8 and n <= 191015 ) UNIX
19.y.0.0.x_date ( y <= 6 and date <= 202002 ) WIN
[Link] ( y <= 6 and n <= 200114 )
_optimizer_extended_cursor_sharin
NONE -
g_rel
(Hot News 2258559), status info: waiting for bug fix
_optimizer_reduce_groupby_key FALSE
of bug 22610792
_optimizer_use_feedback FALSE -
(Hot News 2780131) Database created with <
Oracle 12.2 and started using Advanced Row
(OLTP Table) Compression with Oracle 11.2 or 12.1
_partial_comp_enabled FALSE
UNIX [Link].x_date ( date <= 201911 ) WIN
[Link] UNIX 18.y.0.0.x_date ( y <= 8 and date <=
201911 ) WIN 18 WIN 19
UNIX 12.2 WIN 12.2 UNIX 18 WIN 18 UNIX 19
(SAP non-BW (SAP_OLTP) or SAP BW
_rowsets_enabled FALSE (SAP_OLAP) with in_memory_size = 0) WIN 19
(SAP non-BW (SAP_OLTP) or SAP BW
(SAP_OLAP) with in_memory_size = 0)
(SAP Note 2335159) UNIX 19 (SAP BW
_rowsets_enabled TRUE (SAP_OLAP) with in_memory_size > 0) WIN 19
(SAP BW (SAP_OLAP) with in_memory_size > 0)
_securefiles_concurrency_estimate 50 (SAP Note 1887235)
Default value of '_spacebg_sync_segblocks' is
TRUE. The parameter
_spacebg_sync_segblocks TRUE '_bug12963364_spacebg_sync_segblo
cks' was first added in [Link] (SAP Note
1888485).
_suppress_identifiers_on_dupkey TRUE -
12c: prevent ORA-00600 (Oracle Support
Document 1957710.1) 12c ... 19c: single lgwr
_use_single_log_writer TRUE
provides better performance than multiple lgwr in
SAP NW environments

Database Parameter "EVENT" and "_FIX_CONTROL"

Database parameter 'EVENT' and database parameter '_FIX_CONTROL' need special attention:

© 2021 SAP SE or an SAP affiliate company. All rights reserved 12 of 22


2021-11-02 2470718

• SWPM does not configure these database parameters in a new installed SAP database.
• Both parameters are mandatory for an SAP database.
• Both parameters are likely to be updated after a new Bundle Patch (Windows) or SAP Bundle Patch
(Unix) has been applied.
• For Windows platforms the corresponding SQL must be derived from this SAP note.
• For Unix platforms the SBP-specific SQL statement is documented in the corresponding SBP
README.
SQL> ALTER SYSTEM SET EVENT= <value clause>;
SQL> ALTER SYSTEM SET "_FIX_CONTROL"= <value clause>;

Database Parameter "EVENT"

Database parameter 'EVENT' needs some special attention:

• This parameter is not configured by SWPM.


• This parameter is mandatory for an SAP database.
• This parameter is likely to be updated after a new Bundle Patch (Windows) or SAP Bundle Patch
(Unix) has been applied.

Parameter Recommended Value Remark and Explanation


'10027' (SAP Note 596420)
'10028' (SAP Note 596420)
'10142' (SAP Note 1284478)
'10183' (SAP Note 128648)
'10191' (SAP Note 128221)
event '10995 level 2' (SAP Note 1565421)
'38068 level 100' (SAP Note 176754)
'38085' (SAP Note 176754)
'38087' (SAP Note 948197)
'44951 level 1024' (SAP Note 1166242)
'60025' (SAP Note 2393275)

Database Parameter "_FIX_CONTROL"

Database parameter '_FIX_CONTROL' needs some special attention:

• This parameter is not configured by SWPM.


• This parameter is mandatory for an SAP database.
• This parameter is likely to be updated after a new Bundle Patch (Windows) or SAP Bundle Patch
(Unix) has been applied.

Recommended
Parameter Remark and Explanation
Value
_fix_control '5099019:ON' dbms_stats counts leaf blocks correctly
'6055658:OFF' calculate correct join card. with histograms
'6120483:OFF' -
'6399597:ON' (SAP Note 176754), sort group by instead of hash group by
'6430500:ON' avoid that unique index not chosen
© 2021 SAP SE or an SAP affiliate company. All rights reserved 13 of 22
2021-11-02 2470718
'6972291:ON' (SAP Note 1165319), use column group selectivity with hgrm
'7324224:OFF' remove predicates that are redundant because of subtrees
'7658097:ON' disable group-by placement under certain conditions; to reduce parse time
use PGA for bloom filter with broadcast UNIX 12201x_date ( date >= 201811
'8932139:ON'
) WIN [Link].nP ( n >= 181130 ) UNIX 18 WIN 18 UNIX 19 WIN 19
'8937971:ON' correct clause definition dbms_metadata.get_ddl
'9196440:ON' fixes low distinct keys in index stats
'9495669:ON' disable histogram use for join cardinality
'13627489:ON' -
'14255600:ON' -
'14595273:ON' -
'18405517:2' -
(SAP Note 2395585) UNIX 12201x_date ( date < 201805 ) WIN [Link].nP (
'20107874:OFF'
n < 190228 )
(SAP Note 2395585) UNIX 12201x_date ( date >= 201805 ) WIN [Link].nP
'20107874:ON'
( n >= 190228 )
'20355502:10' reduces parse time with OR-expansion (SAP Note 2698967)
enable (ON)/disable (OFF) use of dynamic sampling to estimate the row
'20636003:OFF'
count from a query block
Use HASH UNIQUE with UNION operator when applicable UNIX
'22387320:ON' 19.y.0.0.x_date ( y >= 12 and date >= 202108 ) WIN [Link] ( y >= 12
and n >= 210720 )
'22540411:ON' use Hash group by with Sort ordering as default aggregation method
disjunct predicate lost in star transformation UNIX [Link].x_date ( date >=
'22746853:ON'
201711 ) WIN [Link].nP ( n >= 180116 )
'23197730:ON' high parse time with multiple inlists UNIX 12.2 WIN 12.2
correction to sanity check join cardinality unique index on right UNIX
'23643560:ON'
[Link].x_date ( date >= 201805 ) WIN [Link].nP ( n >= 180531 )
Set this parameter only if Database In-Memory is NOT used (parameter
'23738304:OFF' inmemory_size=0). (SAP Note 2522894) Improvement of 'group by'
placement UNIX 18 WIN 18 UNIX 19 WIN 19
Set this parameter only if Database In-Memory is used (parameter
'23738304:ON' inmemory_size > 0). (SAP Note 2522894) Improvement of 'group by'
placement UNIX 12.2 WIN 12.2
group by is not pushed down to table level for inmemory tables UNIX 12.2
'23738553:ON'
WIN 12.2
VT inline view generation doesn't count duplicates in predicates UNIX
'24561942:ON' 19.y.0.0.x_date ( y >= 11 and date >= 202105 ) WIN [Link] ( y >= 11
and n >= 210420 )
'25476149:ON' impose a limit on memory used by bitmap access paths UNIX 12.2 WIN 12.2
'25643889:ON' query returns ora-00979 but should work
UNIX [Link].x_date ( date >= 201902 ) WIN [Link].nP ( n >= 181016 )
'26423085:ON'
UNIX 18.y.0.0.x_date ( y >= 6 and date >= 201905 ) WIN [Link] ( y >=

© 2021 SAP SE or an SAP affiliate company. All rights reserved 14 of 22


2021-11-02 2470718
6 and n >= 190416 )
Disallow HASH GROUP BY for WiF + uncorrelated select list subquery UNIX
'26536320:ON' [Link].x_date ( date >= 201808 ) WIN [Link].nP ( n >= 180831 ) UNIX 18
WIN 18 UNIX 19 WIN 19
LORE: consider only valid OR-chains for DNF nodes computation (SAP Note
'27321179:ON' 2698967) UNIX [Link].x_date ( date >= 201802 ) WIN [Link].nP ( n >=
180417 ) UNIX 18 WIN 18 UNIX 19 WIN 19
Allow JPPD on query blocks with Key Vector Use operators UNIX
'27343844:ON'
18.y.0.0.x_date ( 8 <= y <= 9 and 201911 <= date <= 202002 )
No adjustment to number of skips with multi-column statistics (SAP Note
'27466597:ON' 2395585) UNIX [Link].x_date ( date >= 201805 ) WIN [Link].nP ( n >=
190228 ) UNIX 18 WIN 18 UNIX 19 WIN 19
Only count one with clause reference from connect by (SAP Note 2999193)
'27500916:OFF'
UNIX 19 WIN 19
Reuse table stats for column if UA view has remote table UNIX
[Link].x_date ( date >= 201902 ) WIN [Link].nP ( n >= 190115 ) UNIX
'28072567:ON'
18.y.0.0.x_date ( y >= 6 and date >= 201905 ) WIN [Link] ( y >= 6 and
n >= 190416 )
Prevent Cartesian Merge Join with partial join predicate pushdown UNIX
18.y.0.0.x_date ( y >= 14 and date >= 202105 ) WIN [Link] ( y >= 14
'28173995:ON'
and n >= 210420 ) UNIX 19.y.0.0.x_date ( y >= 11 and date >= 202105 )
WIN [Link] ( y >= 11 and n >= 210420 )
Allow more cases for interleaving ORE with SU UNIX 19.y.0.0.x_date ( 9 <=
'28234255:ON'
y <= 10 and 202011 <= date <= 202102 )
Allow more cases for interleaving ORE with SU UNIX 19.y.0.0.x_date ( y >=
'28234255:3'
11 and date >= 202105 ) WIN [Link] ( y >= 11 and n >= 210420 )
Expansion with some constant branches;fkr1 in (NOT)EXISTS subquery
'28414968:3' UNIX 19.y.0.0.x_date ( y >= 11 and date >= 202105 ) WIN [Link] ( y >=
11 and n >= 210420 )
Allow legacy OR expansion for DML top query block UNIX 18.y.0.0.x_date ( y
>= 11 and date >= 202008 ) WIN [Link] ( y >= 11 and n >= 200714 )
'28498976:ON'
UNIX 19.y.0.0.x_date ( y >= 7 and date >= 202005 ) WIN [Link] ( y >=
7 and n >= 200414 )
Fix a bad vector group by cardinality estimate with a joined fact UNIX 18 WIN
'28558645:ON'
[Link] ( y >= 9 and n >= 200114 ) UNIX 19 WIN 19
Simplification of multiple OR conditions UNIX [Link].x_date ( date >=
201911 ) WIN [Link].nP ( n >= 200414 ) UNIX 18.y.0.0.x_date ( y >= 8 and
'28602253:ON'
date >= 201911 ) WIN [Link] ( y >= 12 and n >= 201020 ) UNIX 19 WIN
[Link] ( y >= 9 and n >= 201020 )
Aggressively push bloom filter users down into DFO's UNIX 19.y.0.0.x_date (
'28708585:ON'
y >= 12 and date >= 202108 ) WIN [Link] ( y >= 12 and n >= 210720 )
Before calculating multi-parents ensure cardinality > NDV UNIX 18 WIN
'28835937:ON'
[Link] ( y >= 10 and n >= 200414 ) UNIX 19 WIN 19
Bloom filter with broadcast when pushed through table queue UNIX
'28999046:ON' 19.y.0.0.x_date ( y >= 10 and date >= 202102 ) WIN [Link] ( y >= 10
and n >= 210119 )

© 2021 SAP SE or an SAP affiliate company. All rights reserved 15 of 22


2021-11-02 2470718
JPPD index access heuristics correction and fixed index support UNIX
18.y.0.0.x_date ( y >= 14 and date >= 202105 ) WIN [Link] ( y >= 14
'29302565:ON'
and n >= 210420 ) UNIX 19.y.0.0.x_date ( y >= 10 and date >= 202102 )
WIN [Link] ( y >= 10 and n >= 210119 )
Allow legacy OR expansion when number of sub QB exceeds threshold
'29304314:ON' UNIX 19.y.0.0.x_date ( y >= 8 and date >= 202008 ) WIN [Link] ( y >=
8 and n >= 200714 )
Allow LORE when cbqt ore rejected due to sub qb is parametrised UNIX
'29385774:ON' 19.y.0.0.x_date ( y >= 11 and date >= 202105 ) WIN [Link] ( y >= 11
and n >= 210420 )
Allow legacy ORE for exotic query constructs (SAP Note 2806210) UNIX
[Link].x_date ( date >= 201908 ) WIN [Link].nP ( n >= 200114 ) UNIX
'29450812:ON'
18.y.0.0.x_date ( y >= 7 and date >= 201908 ) WIN [Link] ( y >= 9 and
n >= 200114 ) UNIX 19 WIN 19
Streamline traversal of CAST_PSR operator UNIX 19.y.0.0.x_date ( y >= 10
'29487407:ON'
and date >= 202102 ) WIN [Link] ( y >= 10 and n >= 210119 )
Improve costing for indexes with empty statistics UNIX [Link].x_date ( date
>= 202002 ) WIN [Link].nP ( n >= 200714 ) UNIX 18.y.0.0.x_date ( y >= 9
'29687220:ON' and date >= 202002 ) WIN [Link] ( y >= 10 and n >= 200414 ) UNIX
19.y.0.0.x_date ( y >= 6 and date >= 202002 ) WIN [Link] ( y >= 7 and
n >= 200414 )
Do not unset partial JPPD info in additional phase UNIX 18.y.0.0.x_date ( y
>= 14 and date >= 202105 ) WIN [Link] ( y >= 14 and n >= 210420 )
'29867728:ON'
UNIX 19.y.0.0.x_date ( y >= 11 and date >= 202105 ) WIN [Link] ( y >=
11 and n >= 210420 )
Restrict _b_tree_bitmap_plans to single table access paths UNIX
[Link].x_date ( date >= 202008 ) WIN [Link].nP ( n >= 200414 ) UNIX
'29930457:ON' 18.y.0.0.x_date ( y >= 11 and date >= 202008 ) WIN [Link] ( y >= 11
and n >= 200714 ) UNIX 19.y.0.0.x_date ( y >= 7 and date >= 202005 ) WIN
[Link] ( y >= 8 and n >= 200714 )
Maintain original predicate order during transformations UNIX
'30008456:ON' 19.y.0.0.x_date ( y >= 11 and date >= 202105 ) WIN [Link] ( y >= 11
and n >= 210420 )
Fix subquery filter cost based on the number of values cached UNIX
'30142527:ON' 19.y.0.0.x_date ( y >= 12 and date >= 202108 ) WIN [Link] ( y >= 12
and n >= 210720 )
Extend fix of 30231086 to IN subqueries without correlation UNIX
'30195773:ON' 18.y.0.0.x_date ( y >= 11 and date >= 202008 ) UNIX 19.y.0.0.x_date ( y >=
8 and date >= 202008 )
Unnest in absence of index on local column in correlated subquery UNIX
'30231086:ON' 18.y.0.0.x_date ( y >= 11 and date >= 202008 ) UNIX 19.y.0.0.x_date ( y >=
8 and date >= 202008 )
Handle condition operands in aggregates for GBP UNIX 19.y.0.0.x_date ( y
'30235691:ON'
>= 11 and date >= 202105 ) WIN [Link] ( y >= 11 and n >= 210420 )
Use pushed KV selectivity in row estimates UNIX 19.y.0.0.x_date ( y >= 11
'30249927:ON'
and date >= 202105 ) WIN [Link] ( y >= 11 and n >= 210420 )
Take into consideration key count when comparing 2 inlists UNIX
'30470947:ON'
19.y.0.0.x_date ( y >= 11 and date >= 202105 ) WIN [Link] ( y >= 11
© 2021 SAP SE or an SAP affiliate company. All rights reserved 16 of 22
2021-11-02 2470718
and n >= 210420 )
Prune projection lists of VT join backs to temp tables UNIX 19.y.0.0.x_date (
'30483217:ON'
y >= 11 and date >= 202105 ) WIN [Link] ( y >= 11 and n >= 210420 )
Use join/filter selectivity based initial join orders UNIX 19.y.0.0.x_date ( y >=
'30537403:ON'
9 and date >= 202011 ) WIN [Link] ( y >= 11 and n >= 210420 )
Avoid LATERAL view with disjunct filter on LEFT in ROJ UNIX
'30776676:ON' 19.y.0.0.x_date ( y >= 11 and date >= 202105 ) WIN [Link] ( y >= 11
and n >= 210420 )
Relax restriction on JPPD within lateral view UNIX 18.y.0.0.x_date ( y >= 14
and date >= 202105 ) WIN [Link] ( y >= 14 and n >= 210420 ) UNIX
'30786641:ON'
19.y.0.0.x_date ( y >= 11 and date >= 202105 ) WIN [Link] ( y >= 11
and n >= 210420 )
Allow ANSI Rearchitecture for CTAS and INSERT-SELECT UNIX
'31009032:ON' 19.y.0.0.x_date ( y >= 11 and date >= 202105 ) WIN [Link] ( y >= 11
and n >= 210420 )
Enable semi-blocking Hash Join UNIX 19.y.0.0.x_date ( y >= 12 and date >=
'31082719:ON'
202108 ) WIN [Link] ( y >= 12 and n >= 210720 )
Reset expression stats for given object_id/snapshot_id UNIX 19.y.0.0.x_date
'31143146:ON'
( y >= 11 and date >= 202105 ) WIN [Link] ( y >= 12 and n >= 210720 )
Separate fix control for GBP & JPPD under fix 7658097 UNIX
[Link].x_date ( date >= 202011 ) WIN [Link].nP ( n >= 210119 ) UNIX
'31444353:1'
18.y.0.0.x_date ( y >= 12 and date >= 202011 ) UNIX 19.y.0.0.x_date ( y >=
9 and date >= 202011 ) WIN [Link] ( y >= 10 and n >= 210119 )
orrect check for storing of histogram actual value UNIX 19.y.0.0.x_date ( y >=
'31496840:ON'
12 and date >= 202108 ) WIN [Link] ( y >= 12 and n >= 210720 )
Fix outer join selectivity of column group stats UNIX 19.y.0.0.x_date ( y >= 12
'31821701:ON'
and date >= 202108 ) WIN [Link] ( y >= 12 and n >= 210720 )
Prevent non-durable consistent read gets UNIX 19.y.0.0.x_date ( y >= 12
'31961578:ON'
and date >= 202108 ) WIN [Link] ( y >= 12 and n >= 210720 )
Push key vectors through filter rowsources UNIX 19.y.0.0.x_date ( y >= 11
'32014520:ON'
and date >= 202105 ) WIN [Link] ( y >= 11 and n >= 210420 )
Fix multi-column semi join/full outer join selectivity UNIX 19.y.0.0.x_date ( y
'32107621:ON'
>= 12 and date >= 202108 ) WIN [Link] ( y >= 12 and n >= 210720 )

Database Parameter Settings for SI/FS

The table below contains SAP's parameter recommendations for SAP on an Oracle Single Instance database
on file system (SI/FS). Parameters listed here must be set in addition to the basic parameters mentioned
above, or with different value.

Parameter Recommended Value Remark and Explanation


At least 3 copies on different disk
control_files <location of control files>
areas
This parameter is configured in
(ADDRESS = (PROTOCOL=TCP) RAC, ASM or Multitenant
local_listener (HOST=<hostname>) (PORT=<port>)) or databases. This parameter is not
<hostname>:<port> set for Non-RAC, Non-ASM, Non-
CDB. Exception: Windows with
© 2021 SAP SE or an SAP affiliate company. All rights reserved 17 of 22
2021-11-02 2470718
Oracle Fail Safe Reference: SAP
Note 1915325
'LOCATION=<SAPDATA_HOME>/oraarch/ SAP standard location for archive
log_archive_dest_1
<sid>arch' logs
undo_tablespace PSAPUNDO SAP note 600141

Database Parameter Settings for RAC

The table below contains SAP's parameter recommendations for SAP on Oracle Real Application Clusters
(RAC). Parameters listed here must be set in addition to the basic parameters mentioned above, or with
different value.

The column 'RAC Instance' defines whether a parameter is valid for one or all RAC instances: Parameters
marked with '*' are valid for all RAC instances. Parameters marked with '<instance_name>' are instance
specific and must be specified for every RAC instance.

RAC Instance Parameter Recommended Value Remark and Explanation


* cluster_database TRUE Requires license for RAC
cluster_database_instance
* <n> number of RAC instances
s
'LOCATION=<SAPDATA_HOME>/ SAP standard location for
* log_archive_dest_1
oraarch/<sid>arch' archive logs
Name of the scan listener as
* remote_listener //<scan_name>:1521 defined in DNS ($srvctl config
scan)
Example for instance PRD001:
PRD001
<instance_name> instance_name <instancename>
<instancename>=<dbname>+<
instance number>
Example for instance PRD001:
001 SAP Default: 3-digit
<instance_name> instance_number 001
number Used for instance
name
(ADDRESS = (PROTOCOL=TCP)
<instance_name> local_listener (HOST=<hostname_vip>) Use only host vip
(PORT=1521))
Example for instance PRD001:
<instance_name> service_names (<dbname>, <instancename>)
PRD, PRD001
instance number without
<instance_name> thread 1
leading '0's
Example for instance PRD001:
<instance_name> undo_tablespace PSAPUNDO<instance_number> PSAPUNDO001 SAP note
600141

Database Parameter Settings for ASM

The table below contains SAP's parameter recommendations for SAP on Oracle Automatic Storage
Management (ASM). Parameters listed here must be set in addition to the basic parameters mentioned
above, or with different value.

© 2021 SAP SE or an SAP affiliate company. All rights reserved 18 of 22


2021-11-02 2470718
Parameter Recommended Value Remark and Explanation
'+ARCH/<DBNAME>/cntrl<DBNAME>.dbf
' '+DATA/<DBNAME>/cntrl<DBNAME>.dbf At least 3 copies on different
control_files
' '+RECO/<DBNAME>/cntrl<DBNAME>.dbf disk groups
'
db_create_file_dest '+DATA' data files, temp files
online redo log 1st
db_create_online_log_dest_1 '+DATA'
copy/member (~origlog)
online redo log 2nd
db_create_online_log_dest_2 '+RECO'
copy/member (~mirrlog)
Disk group for Fast Recovery
db_recovery_file_dest '+RECO'
Area (FRA)
'LOCATION=+<DGNAME>/<DBNAME>/oraa SAP standard location for
log_archive_dest_1
rch' archive logs for SI and RAC

Database Parameter Settings for Oracle Engineered Systems

The table below contains SAP's parameter recommendations for SAP on Oracle Engineered Systems.
Parameters listed here must be set in addition to the basic or hidden (underscore) parameters mentioned
above, or with different value.

Remark and
Parameter Recommended Value
Explanation
'+DATA/<DBNAME>/cntrl<DBNAME>.dbf
2 copies on different
control_files ' '+RECO/<DBNAME>/cntrl<DBNAME>.dbf
disk groups
'
db_create_file_dest '+DATA' -
online redo log 1st
db_create_online_log_dest_1 '+DATA' copy/member
(~origlog);
online redo log 2nd
copy/member
(~mirrlog); Do not
configure a 2nd
db_create_online_log_dest_2 '+RECO'
member if disk group
‘+DATA’ is configured
with high redundancy
(see white paper)
db_recovery_file_dest '+RECO' -
'LOCATION=+<DGNAME>/<DBNAME>/oraa SAP standard location
log_archive_dest_1
rch' for archive logs
Set according to SAP
note 1627481. On
Oracle Exadata
log_buffer 128M or higher LOG_BUFFER >=
128M On Oracle
SPARC SuperCluster
LOG_BUFFER >=

© 2021 SAP SE or an SAP affiliate company. All rights reserved 19 of 22


2021-11-02 2470718
128M
UNIX 19; set on Oracle
_optimizer_gather_stats_on_conven
FALSE Exadata only; Disable
tional_dml
Real-Time Statistics
UNIX 19; set on Oracle
_optimizer_use_stats_on_conventio
FALSE Exadata only; Disable
nal_dml
Real-Time Statistics

Database Parameter Settings for Specific Platforms

The table below contains platform-specific parameter recommendations for SAP.

Parameter Platform Recommended Value Remark and Explanation


(SAP Note 2799946) If set to 'FALSE': HP-
UX only and only for standard filesystems;
not for OnlineJFS (VxFS 5.x), not for ASM,
not for raw devices, Reference: bug
19825394, See SAP note 798194 If set to
'TRUE': Ensure that HP-UX asynchronous
I/O support is enabled and configured
according to Oracle database
documentation. If not, you might see error
like "ORA-27090: Unable to reserve kernel
resources for asynchronous disk I/O,
Additional information: 2" Reference:
Database Administrator's Reference, D -
Administering Oracle Database on HP-UX,
D.4 - Asynchronous Input-Output If
required, give the device file the operating
system owner and permissions consistent
with those of the Oracle software owner
and OSDBA group (oracle:oinstall or
disk_asynch_io HP-UX FALSE ora<dbsid>:dba). # /usr/bin/chown
oracle:oinstall /dev/async # /usr/bin/chown
ora<dbsid>:dba /dev/async #
/usr/bin/chmod 660 /dev/async For better
understanding how and when you can set
this parameter to false: The default value of
this parameter is TRUE.
[Link]
n/database/oracle/oracle-
database/18/refrn/DISK_AS
YNCH_IO.html If your platform supports
asynchronous I/O to disk, Oracle
recommends that you leave this parameter
set to its default value. In this case, ensure
that HP-UX asynchronous I/O support is
enabled and configured according to Oracle
database documentation. If not, you might
see error like ORA-27090: Unable to
reserve kernel resources for asynchronous
disk I/O For SAP with Oracle database on

© 2021 SAP SE or an SAP affiliate company. All rights reserved 20 of 22


2021-11-02 2470718
HP-UX (only for HP-UX) we allow to set the
parameter to disk_asynch_io=FALSE if the
database files reside on an standard file
system, but not OnlineJFS (VxFS 5.x) With
other words: if your SAP database of
release 12c or later resides on (1) HP-UX
with OnlineJFS (VxFS 5.x) or (2) on ASM or
(3) on a platform other than HP-UX, then
use the Oracle default value (TRUE). Raw
Devices are not supported any more
starting 12c.
By default, '_ENABLE_NUMA_SUPPORT'
is not set (=FALSE) and Oracle NUMA
support (Non Uniform Memory Architecture)
is disabled. Before you enable Oracle
NUMA support in a production system by
setting this parameter to TRUE it is
see MOS note
_enable_numa_support NUMA necessary to run additional (performance)
864633.1
tests: you need to evaluate the
performance before and after enabling
NUMA in a test environment before you go
into production. Additional information can
be found in My Oracle Support note
864633.1.
If "_enable_NUMA_support"=TR
UE then you should also set
"_px_numa_support_enabled
depending on "=TRUE. This is required if you perform
_px_numa_support_enabled NUMA
_enable_numa_support parallel operations like parallel query or
create index under NUMA support. For
details, see Oracle Support Document
1956463.1
hpux_sched_noage HP-UX 178 HP-UX only, without RAC
Linux only Possible values: TRUE, FALSE,
use_large_pages LINUX see SAP note 1672954
ONLY see SAP note 1672954

Appendix

This document refers to

SAP Note/KBA Title

2812178 ORA-00600: internal error code, arguments: [2025] during recovery

2470660 Central Technical Note for Oracle Database 12c Release 2 (12.2)

© 2021 SAP SE or an SAP affiliate company. All rights reserved 21 of 22


2021-11-02 2470718

This document is referenced by

SAP
Title
Note/KBA

1898915 FAQ: Oracle Hidden Parameter - NetWeaver

2968993 BR0978W parameter: COMPATIBLE, value: % (<>°%) in DB13/DBACOCKPIT

2906285 "DUMP FILE SIZE IS LIMITED TO" appears in the Oracle (Incident) Traces

"ORA-00922: missing or invalid option" error in phase


2064052
MAIN_SHDCRE/SUBMOD_SHDDBCLONE/DBCLONE or MAIN_NEWBAS/PARCONV_UPG

192055 BRCONNECT warnings despite correct parameter values

2956661 SAP NetWeaver on Oracle Database Exadata Cloud@Customer

2919894 Oracle Database Parameter "_ipddb_enable"

2335159 Flat cube on BW on Oracle

2847437 Older Versions: SAP Software and Oracle Exadata

2773486 Oracle 12c On Windows: Local SYSDBA Authentication Fails With ORA-1017

2698967 12c: Bad performance due to CBO does not choose OR expansion

2636470 BW Oracle RSRV parameter COMPATIBLE (12.1, 12.2)

1590515 SAP Software and Oracle Exadata

2470660 Central Technical Note for Oracle Database 12c Release 2 (12.2)

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2021 SAP SE or an SAP affiliate company. All rights reserved 22 of 22

You might also like