16.12.2011 Page 1 of 12 SAP Note 584952 - DB6: DB2 UDB Version 8 Standard Parameter Settings Note Language: English Version: 49 Validity: Valid Since 08.09.2010 Summary Symptom You want to set DB2 database and database manager configuration parameters for all SAP releases that are running on DB2 UDB ESE Version 8 (in the following referred to as DB2 V8 ). Other terms EarlyWatch, GoingLive, DB2, ESE, DPF, DB6, dbm, db, registry, Reason and Prerequisites This SAP Note contains recommendations for parameter settings for DB2 V8 Enterprise Server Edition (ESE). History of changes (Decending ordered list since December 2009): 09/08/2010: Updated log recommendations 07/30/2010: LOGPRIMARY from 20 to 60 07/30/2010: LOGSECOND from 40 to 0 12/14/2009: CHNGPGS_THRESH from 40 to 20 Solution This SAP Note is valid for the following system workload classes: o OLTP (for example, SAP ERP and SAP CRM) o OLAP (for example, SAP NetWeaver BW) Specific settings that are required for only one workload type are documented in separate sections at the end of this SAP Note. You can achieve optimal system performance and optimal usability with a correct setup of the DB2 database and of the database manager parameters. Do not deviate from the standard recommendations below unless you feel experienced enough to understand the impact of your changes. The recommendations are intended as an initial configuration. For some parameters load-dependent tuning is required. However, these parameters are specifically marked. In some cases, SAP Active Global Support might advice you to temporarily deviate from the settings documented in this SAP Note to solve a specific problem. In this case, follow the advise from SAP Active GlobalSupport. After the problem has been finally solved by an SAP or DB2 code correction, apply the code correction as soon as possible and re-establish the original settings. Most of the parameters below are dynamic. Changes to the parameters become effective immediately if you use an existing database connection.This means
Transcript
16.12.2011 Page 1 of 12
SAP Note 584952 - DB6: DB2 UDB Version 8 StandardParameter Settings
Note Language: English Version: 49 Validity: Valid Since 08.09.2010
Summary
SymptomYou want to set DB2 database and database manager configuration parametersfor all SAP releases that are running on DB2 UDB ESE Version 8 (in thefollowing referred to as DB2 V8 ).
Other termsEarlyWatch, GoingLive, DB2, ESE, DPF, DB6, dbm, db, registry,
Reason and PrerequisitesThis SAP Note contains recommendations for parameter settings for DB2 V8Enterprise Server Edition (ESE).
History of changes (Decending ordered list since December 2009):
09/08/2010: Updated log recommendations07/30/2010: LOGPRIMARY from 20 to 6007/30/2010: LOGSECOND from 40 to 012/14/2009: CHNGPGS_THRESH from 40 to 20
Solution
This SAP Note is valid for the following system workload classes:
o OLTP (for example, SAP ERP and SAP CRM)
o OLAP (for example, SAP NetWeaver BW)
Specific settings that are required for only one workload type aredocumented in separate sections at the end of this SAP Note.
You can achieve optimal system performance and optimal usability with acorrect setup of the DB2 database and of the database manager parameters.Do not deviate from the standard recommendations below unless you feelexperienced enough to understand the impact of your changes.
The recommendations are intended as an initial configuration. For someparameters load-dependent tuning is required. However, these parameters arespecifically marked.
In some cases, SAP Active Global Support might advice you to temporarilydeviate from the settings documented in this SAP Note to solve a specificproblem. In this case, follow the advise from SAP Active GlobalSupport.After the problem has been finally solved by an SAP or DB2 code correction,apply the code correction as soon as possible and re-establish the originalsettings.
Most of the parameters below are dynamic. Changes to the parameters becomeeffective immediately if you use an existing database connection.This means
16.12.2011 Page 2 of 12
SAP Note 584952 - DB6: DB2 UDB Version 8 StandardParameter Settings
that you are connected to the database (<DBSID>) first and then change theparameters using this existing connection. You can view currently activeparameters using the following command:
db2 get db cfg for <dbsid> show detail
Starting with SAP Release 4.6C, you can view DB2 parameters using the DBACockpit (transaction DBACOCKPIT). In the navigation frame of the DBACockpit, choose Configuration.
The following markers are used in the parameter recommendation sections:
o [CUST]: Customer individual setting
There is no particular setting required by SAP. The values listedfor these parameters are typical default values that you shouldstart with. If required, you can set the parameter differently.
o [DEPR]: Deprecated
The parameter has become obsolete or deprecated with DB2 V8 and isignored by DB2.
o [BI=YES], [BI=NO]: Differs depending if your workload is primarilyOLAP or OLTP
- If your workload is primarily OLAP-dominated (originating fromSAP NetWeaver BW, SAP SRM or SAP SCM), follow the settingsmarked with [BI=YES].
- In all other cases, follow the recommendations marked with[BI=NO].
o [BIT=32], [BIT=64]: Requires different settings on 32 bit or 64 bitdatabase instances
- If your database instance is a 32 bit instance, apply thesettings marked with [BIT=32]
- If your database instance is a 64 bit instance, apply thesettings marked with [BIT=64]
o [OS=WINDOWS], [OS=UNIX]: Requires different settings on Windows orUNIX based database servers
- If your database server is running on Windows, apply thesettings marked with [OS=WINDOWS].
- If your database server is running on Linux, HP-UX, Solaris orAIX, apply the recommendation marked with [OS=UNIX].
o [FP>=nn.nn.nnnn], [FP<=nn.nn.nnnn]: Recommendation is valid for thegiven range of DB2 levels only
Multiple markers in one line are to be read as logical "AND", that is, thesetting is recommended for configurations where all conditions are true.
16.12.2011 Page 3 of 12
SAP Note 584952 - DB6: DB2 UDB Version 8 StandardParameter Settings
For example, PARAM1 = 99 [FP<=08.02.0002], [OS=WINDOWS] means that youshould set PARAM1=99 only if your DB2 level is up to and including08.02.0002 (V8FP9) AND your database server is running on Windows. If yourdatabase server is not running on Windows or if you are using DB2 V8 FP10or higher, do not apply the setting.
Database Manager Configuration Parameters
The following database configuration parameters are grouped according tothe output that you receive if you use the following command:db2 GET DBM CFG
To update the parameters, enter the following command:DB2 UPDATE DBM CFG USING <parameter> <value>
List of Parameters:===================
> MAXTOTFILOP = 16000 [DEPR];[FP<=08.01.0006]
Note:This parameter is removed with FP7
> CPUSPEED = <value> [CUST]
Note:CPUSPEED is generated by DB2 during instance creation based on hardwarecharacteristics of your database server. To indicate that DB2 shouldregenerate the value, you can set the parameters to -1.
> NUMDB = 8 [CUST]> DATALINKS = NO [CUST]> FEDERATED = NO [CUST]> TP_MON_NAME = <empty> [CUST]> DFT_ACCOUNT_STR = <empty> [CUST]> JDK_PATH = <path to JDK> [CUST]
Note:Set NUM_IOCLEANERS to the number of CPUs available per database partition.Example 1: CRM system with 4 CPUs, single-partitioned -> 4Example 2: BW system with 16 CPUs and 4 database partitions -> 4The minimum value for this parameter is 1
> NUM_IOSERVERS >= 3
Note:Set NUM_IOSERVERS value as follows:max ( # of containers(TBS1), # of containers (TBS2),...)Example: max (10,25,2,2,40)=40
If you are using DB2_PARALLEL_IO, you need to set NUM_IOSERVERS accordingto the following formula:max( max over all table spaces ( parallelism setting * max # containers in stripe set] ), 3 )
Note:For more information about dual logging, see SAP Note 409127.
> BLK_LOG_DSK_FUL = YES [CUST]
Note:This will ensure that DB2 blocks processing in case of an "archiver stuck"
> MAX_LOG = 0 [CUST]> NUM_LOG_SPAN = 0 [CUST]
Note:After every change of LOGFILSIZ, LOGPRIMARY or LOGSECOND you should checkyour settings of MAX_LOG and NUM_LOG_SPAN.
> MINCOMMIT = 1
> SOFTMAX = 300 [CUST]
Note:SOFTMAX is the threshold for the LSN gap page cleaner trigger. The valueunit is percent, based on the size of one log file (LOGFILSIZ).In case you have set LOGFILSIZ to a large value, you may consider to lowerthe value of SOFTMAX accordingly. For example, if you have LOGFILSIZ set to50000 or higher, you may want to reduce SOFTMAX from 300 to 100.
> LOGRETAIN = RECOVERY> USEREXIT = OFF [CUST]
Note:USEREXIT=ON is required if legacy log file management is used. USEREXIT=OFFif the new DB2 log file management management is used.For HADR settings, see Note 780546 .For LOGARCH settings, see SAP Database Administration Guide "IBM DB2 UDB -New Log File Managment" at:http://service.sap.com/instguides --> SAP NetWeaver --> SAP NetWeaver 04--> Operations --> Database-Specific Guides
Note:Set TSM parameters only if you are using TSM, otherwise leave empty
> AUTO_MAINT = ON [CUST]
16.12.2011 Page 9 of 12
SAP Note 584952 - DB6: DB2 UDB Version 8 StandardParameter Settings
> AUTO_DB_BACKUP = OFF [CUST]> AUTO_TBL_MAINT = ON [CUST]> AUTO_RUNSTATS = ON [CUST]> AUTO_STATS_PROF = OFF> AUTO_PROF_UPD = OFF> AUTO_REORG = OFF [CUST]
Note:For more information about parameter AUTO_REORG, see SAP Note 975352.
DB2 Registry Variables
You can list the DB2 registry settings by entering the following command:
db2set -all
To alter the DB2 registriy variables, use the following command:
db2set <PARAMETER> = <VALUE>
To delete existing settings, enter the following command:
db2set <PARAMETER> =
If a registry variable requires Boolean values as arguments, the values YESand ON are equivalent and the values NO and OFF are equivalent.
You must set the following registry variable(s) unless you receivedifferent instructions from SAP support:
> DB2_WORKLOAD = SAP [FP>=08.02.0002]> DB2_PARALLEL_IO = * [CUST]
Note:Only set DB2_PARALLEL_IO=* if the following conditions are both met:
o RAID devices are used for the database
o All tablespaces in the database consist of one single container perstripe set
The following setting apply to V8 FP9 only
> DB2_SKIPDELETED = NO [FP=08.02.0002]> DB2_REDUCED_OPTIMIZATION = 4,UNIQUEINDEX,JOIN [FP=08.02.0002]
Note:If you are using the setting DB2_WORKLOAD=SAP, do not set other registryvariables unless requested by SAP. For example, the exceptions for FP9 arebased on 2 registry variables which modify the default SAP-optimizedbehaviour set through DB2_WORKLOAD=SAP.
The following individual registry setting apply to Fixpacks lower than V8
16.12.2011 Page 10 of 12
SAP Note 584952 - DB6: DB2 UDB Version 8 StandardParameter Settings
FP9 only
> DB2_RR_TO_RS = ON [FP<=08.02.0002]
Note:It is important that you set this variable, if still Type-1 indexes exist(after migration to DB2 Version 8), but there is no negative impact if itis used with Type-2 indexes
> DB2_REDUCED_OPTIMIZATION = 4 [FP<=08.02.0002]
> DB2_MINIMIZE_LISTPREFETCH = ON [FP<=08.02.0002]> DB2_INLIST_TO_NLJN = ON [FP<=08.02.0002]> DB2_ANTIJOIN = ON [FP<=08.01.0003]> DB2_ANTIJOIN = EXTEND [FP>=08.01.0004];[FP<=08.02.0002]
> DB2_IMPLICIT_UNICODE = ON [FP<=08.02.0002]
Note:DB2_IMPLICIT_UNICODE is only necessary if you want to install SAP Web AS -J2EE Add-In in a non-Unicode database
> DB2_EVALUNCOMMITTED = ON [FP>=08.01.0004];[FP<=08.02.0002]> DB2_INTERESTING_KEYS = ON [FP>=08.01.0004];[FP<=08.02.0002]
Note:For SAP APO/SCM systems, a smaller value of 4096 or more might besufficient. However, if problems that are related to sort performance occuror if large Infocubes with aggregates are used, you have to increase theparameter to 15000.
Note:In general, you should run with INTRA_PARALLEL=NO and MAX_QUERYDEGREE=1 andscale out to multiple database partitions (DPF) to make best use of yourCPU power.
Only in the exceptional case that you have 8 CPU cores or more and onlyone database partition, you can consider to set INTRA_PARALLEL=YES andMAX_QUERYDEGREE to a value between 2 and 4.
DB2 Registry Variables for OLAP workloads:============================================================
> DB2_FORCE_FCM_BP = ON [BI=YES];[CUST]
Note:To be specified, only if #(db partitions on one db server) > 1.This variable is only valid on AIX systems.
Tablespace Layout and Buffer Pool Recommendations for OLAP workloads:=====================================================================
For BW 2.x, BW 3.x and related APO and SEM products, see SAP Note 546262.With SAP BW 3.5, the BW technology has become part of SAP NetWeaver.Therefore, no BW-specific configuration of parameters and buffer pools isperformed during the installation process. Make sure that you manuallyperform the necessary adaptations as described in this SAP Note and SAPNote 546262 after finishing the installation.
Header Data
Release Status: Released for CustomerReleased on: 08.09.2010 11:36:14Master Language: EnglishPriority: Correction with high priorityCategory: ConsultingPrimary Component: SV-BO Backoffice Service Delivery
Secondary Components:BC-DB-DB6 DB2 Universal Database for Unix / NT
The Note is release-independent
16.12.2011 Page 12 of 12
SAP Note 584952 - DB6: DB2 UDB Version 8 StandardParameter Settings
Related Notes
Number Short Text
1493932 DB6: How to choose the extent size of DB2 tablespaces
1493852 DB6: Use of alternate page cleaning
1493587 DB6: Use of infinite logging or secondary log files
1474404 DB6: Poor database performance with DB2AUDIT
1329179 DB6: DB2 V9.7 Standard Parameter Settings
1308895 DB6: File System for Transaction Log is Full
1293475 DB6: Transaction Log Full
1250466 DB6: Perform database administration, keeping SAP AS running
1086130 DB6: DB2 9.5 Standard Parameter Settings
956214 DB6: SQL0443N after upgrade to a new SAP release
940550 DB6: Installing FixPak V8.1/V8.2 (up to FP8) on Windows
899322 DB6: DB2 9.1 Standard Parameter Settings
820473 DB6: Snapshot function returns error or hangs
819876 DB6: Additional info about upgrade (based) on SAP NW AS 7.0
780546 DB6: Use of new functions in DB2 V8.2
688647 DB6: SAP BW and SAP NetWeaver BI Administration Tasks
679581 DB6: Additional information on upgrading to BW 3.5
662191 DB6: Additions to upgrade (based) on SAP Web AS 6.40
603981 DB6: Installing V8.2 FixPaks (as of FP9) on Win NT/Win 2000
546262 DB6:Administration & Performance on SAP BW, SAP SCM, SAP SEM
490095 DB6: Additional information on upgrading to SAP Web AS 6.20
370026 DB2 V7.2 Parameter settings for SAP Releases 4.x/6.10/6.20
369772 DB6: MAXLOCKS settings - detailed information
101809 DB6: Supported Fix Packs IBM DB2 for Linux,UNIX and Windows
99509 DB6: Analyzing&Improving Buffer Pool Performance
