This action might not be possible to undo. Are you sure you want to continue?
Note Language: English Version: 49 Validity:
Valid Since 08.09.2010
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 ).
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: 07/30/2010: 07/30/2010: 12/14/2009:
Updated log recommendations LOGPRIMARY from 20 to 60 LOGSECOND from 40 to 0 CHNGPGS_THRESH from 40 to 20
This SAP Note is valid for the following system workload classes: o o OLTP (for example, SAP ERP and SAP CRM) 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
16.12.2011 Page 1 of 12
that is. apply the recommendation marked with [OS=UNIX]. follow the settings marked with [BI=YES]. Solaris or AIX. o [DEPR]: Deprecated The parameter has become obsolete or deprecated with DB2 V8 and is ignored by DB2.12. 16. [OS=UNIX]: Requires different settings on Windows or UNIX based database servers If your database server is running on Windows. The values listed for these parameters are typical default values that you should start with. The following markers are used in the parameter recommendation sections: o [CUST]: Customer individual setting There is no particular setting required by SAP. - o [BIT=32]. In the navigation frame of the DBA Cockpit. If required. apply the settings marked with [BIT=64] - o [OS=WINDOWS].SAP Note 584952 DB6: DB2 UDB Version 8 Standard Parameter Settings that you are connected to the database (<DBSID>) first and then change the parameters using this existing connection. If your database server is running on Linux. o [BI=YES]. SAP SRM or SAP SCM).6C.nnnn]: Recommendation is valid for the given range of DB2 levels only Multiple markers in one line are to be read as logical "AND". HP-UX. In all other cases. apply the settings marked with [BIT=32] If your database instance is a 64 bit instance. you can set the parameter differently. you can view DB2 parameters using the DBA Cockpit (transaction DBACOCKPIT).nnnn].nn. the setting is recommended for configurations where all conditions are true. follow the recommendations marked with [BI=NO]. - o [FP>=nn. You can view currently active parameters using the following command: db2 get db cfg for <dbsid> show detail Starting with SAP Release 4. [FP<=nn. [BIT=64]: Requires different settings on 32 bit or 64 bit database instances If your database instance is a 32 bit instance. choose Configuration.nn. apply the settings marked with [OS=WINDOWS]. [BI=NO]: Differs depending if your workload is primarily OLAP or OLTP - If your workload is primarily OLAP-dominated (originating from SAP NetWeaver BW.2011 Page 2 of 12 .
do not apply the setting.12. Database Manager Configuration Parameters The following database configuration parameters are grouped according to the output that you receive if you use the following command: db2 GET DBM CFG To update the parameters.0002 (V8FP9) AND your database server is running on Windows.[FP<=08.2011 Page 3 of 12 . If your database server is not running on Windows or if you are using DB2 V8 FP10 or higher. PARAM1 = 99 [FP<=08. To indicate that DB2 should regenerate the value.02.02.0002].0006] Note: This parameter is removed with FP7 > CPUSPEED = <value> [CUST] Note: CPUSPEED is generated by DB2 during instance creation based on hardware characteristics of your database server. enter the following command: DB2 UPDATE DBM CFG USING <parameter> <value> List of Parameters: =================== > MAXTOTFILOP = 16000 [DEPR]. you can set the parameters to -1.SAP Note 584952 DB6: DB2 UDB Version 8 Standard Parameter Settings For example. [OS=WINDOWS] means that you should set PARAM1=99 only if your DB2 level is up to and including 08.01. > > > > > > NUMDB DATALINKS FEDERATED TP_MON_NAME DFT_ACCOUNT_STR JDK_PATH = = = = = = 8 NO NO <empty> <empty> <path to JDK> [CUST] [CUST] [CUST] [CUST] [CUST] [CUST] > DIAGLEVEL > NOTIFYLEVEL > DIAGPATH DIAGPATH > > > > > > > > = 3 = 3 = /db2/<DBSID>/db2dump [OS=UNIX] = <drive>:\db2\<DBSID>\db2dump [OS=WINDOWS] = = = = = = = = ON ON ON ON ON ON ON OFF DFT_MON_BUFPOOL DFT_MON_LOCK DFT_MON_SORT DFT_MON_STMT DFT_MON_TABLE DFT_MON_TIMESTAMP DFT_MON_UOW HEALTH_MON [CUST] > SYSADM_GROUP > SYSCTRL_GROUP > SYSMAINT_GROUP = DB<DBSID>ADM = DB<DBSID>CTL = DB<DBSID>MNT 16.
> DIR_CACHE > ASLHEAPSZ > RQRIOBLK > QUERY_HEAP_SZ > UTIL_IMPACT_LIM > AGENTPRI > MAXAGENTS > NUM_POOLAGENTS = NO = 16 = 65000 >= 2000 = 10 = SYSTEM >= 1024 = <value> [CUST] [CUST] Note: Where <value> = "Number SAP WP" + 10% . AUDIT_BUF_SZ = 0 is sufficient. read SAP Note 1474404. For JAVA Application servers. If you want to use DB2 Audit.2011 Page 4 of 12 .SAP Note 584952 DB6: DB2 UDB Version 8 Standard Parameter Settings > > > > > AUTHENTICATION CATALOG_NOAUTH TRUST_ALLCLNTS TRUST_CLNTAUTH FED_NOAUTH = = = = = SERVER_ENCRYPT NO YES CLIENT NO [CUST] [CUST] [CUST] [CUST] [CUST] > DFTDBPATH = /db2/<DBSID> Note: On UNIX and Linux Platforms /db2/<DBSID> On Windows Platforms <DRIVE>: > MON_HEAP_SZ > JAVA_HEAP_SZ > AUDIT_BUF_SZ >= 128 = 2048 >= 0 [CUST] Note: If you are not using the DB2 Audit facility.12. 16.[BI=NO] [OS=WINDOWS] [OS=WINDOWS] [BI=NO] [BIT=32] Note: Set SHEAPTHRES to "Number SAP WP" multiplied with SORTHEAP but not lower than 20000. > INSTANCE_MEMORY > BACKBUFSZ > RESTBUFSZ > AGENT_STACK_SZ > MIN_PRIV_MEM > PRIV_MEM_THRESH > SHEAPTHRES > SHEAPTHRES = AUTOMATIC = 1024 = 1024 >= 64 = 32 = 1296 >= 20000 <= 60000 [CUST] [CUST] [OS=WINDOWS]. > NUM_INITAGENTS > MAX_COORDAGENTS = 5 = -1 [CUST] Note: This equals MAXAGENTS. minimal the value is 50.
enter the following command: 16. > KEEPFENCED > FENCED_POOL > NUM_INITFENCED > INDEXREC > TM_DATABASE > RESYNC_INTERVAL > > > > SPM_NAME SPM_LOG_FILE_SZ SPM_MAX_RESYNC SPM_LOG_PATH = NO >= 5 = 0 = RESTART = 1ST_CONN = 180 = = 256 = 20 = = sapdb2<DBSID> [CUST] [CUST] [CUST] [CUST] [CUST] [CUST] [CUST] > SVCENAME Note: This entry must be maintained in the "services" file.2011 Page 5 of 12 .12.SAP Note 584952 DB6: DB2 UDB Version 8 Standard Parameter Settings > MAXCAGENTS = -1 Note: this equals MAX_COORDAGENTS > MAX_CONNECTIONS = -1 Note: This equals MAX_COORDAGENTS. > DISCOVER > DISCOVER_INST > MAX_QUERYDEGREE > INTRA_PARALLEL > > > > FCM_NUM_BUFFERS FCM_NUM_RQB FCM_NUM_CONNECT FCM_NUM_ANCHORS = SEARCH = ENABLE = 1 = NO = = = = 4096 AUTOMATIC AUTOMATIC AUTOMATIC [CUST] [CUST] [BI=NO] [BI=NO] [CUST] [CUST] [CUST] [CUST] [CUST] [CUST] [CUST] [CUST] > CONN_ELAPSE > MAX_CONNRETRIES > MAX_TIME_DIFF > START_STOP_TIME = 10 = 5 = 60 = 10 Database Configuration Parameters The following database configuration parameters are grouped according to the output that you receive if you use the following command: db2 GET DBM CFG FOR <dbsid> To update the parameters.
[BI=NO] [BIT=64]. use at least 35000.12. > DATABASE_MEMORY > CATALOGCACHE_SZ > LOGBUFSZ > UTIL_HEAP_SZ > BUFFPAGE = AUTOMATIC >= 2560 >= 1024 >= 10000 >= 10000 Note: The use of this parameter should be superseeded by the "ALTER BUFFERPOOL" SQL Statement (and ST04).SAP Note 584952 DB6: DB2 UDB Version 8 Standard Parameter Settings db2 UPDATE DB CFG FOR <DBSID> USING <parameter> <value> List of Parameters: =================== > DYN_QUERY_MGMT > DISCOVER_DB > > > > > > > > > > > > > DFT_QUERYOPT DFT_DEGREE DFT_SQLMATHWARN DFT_REFRESH_AGE DFT_MTTB_TYPES NUM_FREQVALUES NUM_QUANTILES DL_EXPINT DL_WT_IEXPINT DL_NUM_COPIES DL_TIME_DROP DL_UPPER DL_TOKEN = DISABLE = ENABLE = = = = = = = = = = = = = 5 1 NO 0 SYSTEM 10 20 60 60 1 1 NO MAC0 > DBHEAP >= 25000 Note: On HP-UX. > ESTORE_SEG_SZ > NUM_ESTORE_SEGS = 16000 = 0 Note: Do not use ESTORE on SAP Systems. > > > > > > LOCKLIST LOCKLIST APPGROUP_MEM_SZ APPGROUP_MEM_SZ GROUPHEAP_RATIO APP_CTL_HEAP_SZ >= >= = = = = 10000 20000 40000 128000 25 1600 [BIT=32].2011 Page 6 of 12 .[BI=NO] [BIT=32] [BIT=64] > SHEAPTHRES_SHR > SORTHEAP = SHEAPTHRES >= 2048 [BI=NO] 16.
02.[BI=NO] [BIT=64].25.12. single-partitioned -> 4 Example 2: BW system with 16 CPUs and 4 database partitions -> 4 The minimum value for this parameter is 1 > NUM_IOSERVERS >= 3 Note: Set NUM_IOSERVERS value as follows: max ( # of containers(TBS1).0006] > TRACKMOD > DFT_EXTENT_SZ > MAXAPPLS > AVG_APPLS > MAXFILOP > LOGFILSIZ > LOGPRIMARY > LOGSECOND = ON = 2 = AUTOMATIC = 30 = 1950 = 16380 = 60 = 0 [CUST] [CUST] [BI=NO] [CUST] [CUST] Note: If you want to configure LOGSECOND to a value other than zero.01.) Example: max (10. If you 16.40)=40 If you are using DB2_PARALLEL_IO..2. We recommend that you do not configure less than 4GB log space..2. The primary log files are created at the time of the first database activation or after any change to the log configuration. # of containers (TBS2).2011 Page 7 of 12 .. you need to set NUM_IOSERVERS according to the following formula: max( max over all table spaces ( parallelism setting * max # containers in stripe set] ).SAP Note 584952 DB6: DB2 UDB Version 8 Standard Parameter Settings > STMTHEAP > STMTHEAP > APPLHEAPSZ > PCKCACHESZ > STAT_HEAP_SZ > DLCHKTIME > MAXLOCKS > LOCKTIMEOUT > CHNGPGS_THRESH > NUM_IOCLEANERS >= 4096 >= 5120 >= 3072 >= 5120 >= 15000 = 10000 = 90 = 3600 = 20 >= 1 [CUST] [CUST] [CUST] [CUST] [BIT=32]. 3 ) > > > > INDEXSORT SEQDETECT DFT_PREFETCH_SZ DFT_PREFETCH_SZ = = = = YES YES AUTOMATIC 32 [FP>=08.0000] [FP<=08.[BI=NO] Note: Set NUM_IOCLEANERS to the number of CPUs available per database partition. read SAP Note 1493587 and related SAP FAQ note 1497040. Example 1: CRM system with 4 CPUs.
LOGPRIMARY or LOGSECOND you should check your settings of MAX_LOG and NUM_LOG_SPAN.12. if you have LOGFILSIZ set to 50000 or higher. For HADR settings. otherwise leave empty > AUTO_MAINT 16. LOGPRIMARY or LOGSECOND you must ensure that you have enough space allocated in your LOGPATH. The value unit is percent.com/instguides --> SAP NetWeaver --> SAP NetWeaver 04 --> Operations --> Database-Specific Guides > > > > > AUTORESTART INDEXREC DFT_LOADREC_SES NUM_DB_BACKUPS REC_HIS_RETENTN = = = = = ON RESTART 1 12 60 [CUST] [CUST] [CUST] Note: Set TSM parameters only if you are using TSM. you may want to reduce SOFTMAX from 300 to 100. see SAP Database Administration Guide "IBM DB2 UDB New Log File Managment" at: http://service. > BLK_LOG_DSK_FUL = YES [CUST] Note: This will ensure that DB2 blocks processing in case of an "archiver stuck" > MAX_LOG > NUM_LOG_SPAN = 0 = 0 [CUST] [CUST] Note: After every change of LOGFILSIZ. you may consider to lower the value of SOFTMAX accordingly. > NEWLOGPATH > OVERFLOWLOGPATH > MIRRORLOGPATH = <empty> = = [CUST] [CUST] [CUST] Note: For more information about dual logging. In case you have set LOGFILSIZ to a large value. > LOGRETAIN > USEREXIT = RECOVERY = OFF [CUST] Note: USEREXIT=ON is required if legacy log file management is used. For LOGARCH settings.sap.SAP Note 584952 DB6: DB2 UDB Version 8 Standard Parameter Settings change any of the parameters LOGFILSIZ.2011 = ON [CUST] Page 8 of 12 . USEREXIT=OFF if the new DB2 log file management management is used. For example. > MINCOMMIT > SOFTMAX = 1 = 300 [CUST] Note: SOFTMAX is the threshold for the LSN gap page cleaner trigger. based on the size of one log file (LOGFILSIZ). see SAP Note 409127. see Note 780546 .
You must set the following registry variable(s) unless you receive different instructions from SAP support: > DB2_WORKLOAD > DB2_PARALLEL_IO = SAP = * [FP>=08. do not set other registry variables unless requested by SAP.2011 Page 9 of 12 . For example.UNIQUEINDEX. enter the following command: db2set <PARAMETER> = If a registry variable requires Boolean values as arguments.JOIN [FP=08.02. use the following command: db2set <PARAMETER> = <VALUE> To delete existing settings. the values YES and ON are equivalent and the values NO and OFF are equivalent.SAP Note 584952 DB6: DB2 UDB Version 8 Standard Parameter Settings > > > > > > AUTO_DB_BACKUP AUTO_TBL_MAINT AUTO_RUNSTATS AUTO_STATS_PROF AUTO_PROF_UPD AUTO_REORG = = = = = = OFF ON ON OFF OFF OFF [CUST] [CUST] [CUST] [CUST] Note: For more information about parameter AUTO_REORG. DB2 Registry Variables You can list the DB2 registry settings by entering the following command: db2set -all To alter the DB2 registriy variables.0002] [FP=08.02.12.0002] [CUST] Note: Only set DB2_PARALLEL_IO=* if the following conditions are both met: o o RAID devices are used for the database All tablespaces in the database consist of one single container per stripe set The following setting apply to V8 FP9 only > DB2_SKIPDELETED = NO > DB2_REDUCED_OPTIMIZATION = 4.0002] Note: If you are using the setting DB2_WORKLOAD=SAP. see SAP Note 975352. the exceptions for FP9 are based on 2 registry variables which modify the default SAP-optimized behaviour set through DB2_WORKLOAD=SAP.02. The following individual registry setting apply to Fixpacks lower than V8 16.
a smaller value of 4096 or more might be sufficient.02.0004].[FP<=08. if problems that are related to sort performance occur or if large Infocubes with aggregates are used.02.[FP<=08.[FP<=08. see SAP Note 780546.01.[BI=YES] 16.02.0004].0002] ON [FP<=08.[FP<=08. but there is no negative impact if it is used with Type-2 indexes > DB2_REDUCED_OPTIMIZATION > > > > DB2_MINIMIZE_LISTPREFETCH DB2_INLIST_TO_NLJN DB2_ANTIJOIN DB2_ANTIJOIN = 4 = = = = [FP<=08.0002] Note: It is important that you set this variable.[BI=YES] [BI=YES] Note: For SAP APO/SCM systems.SAP Note 584952 DB6: DB2 UDB Version 8 Standard Parameter Settings FP9 only > DB2_RR_TO_RS = ON [FP<=08. However.02.0003] EXTEND [FP>=08.0002] ON [FP<=08. if still Type-1 indexes exist (after migration to DB2 Version 8).0002] [FP>=08.0002] [FP>=08.02.12.02.02.0002] [FP<=08.0002] Note: For more information. Typical Parameter Settings for SAP NetWeaver Business Warehouse (SAP NetWeaver BW) and All SAP Systems Based on SAP NetWeaver BW: Database Configuration Parameters for OLAP Workloads: ===================================================== > LOCKLIST > LOCKLIST > SORTHEAP >= 20000 >= 40000 >= 15000 [BIT=32].01.02.0002] > DB2_IMPLICIT_UNICODE = ON 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 > DB2_INTERESTING_KEYS > DB2MEMMAXFREE > DB2_OBJECT_TABLE_ENTRIES = ON = ON 2000000 65532 [FP>=08.02.0002] [FP<=08.0002] ON [FP<=08.[BI=YES] [BIT=64]. > STMTHEAP > AVG_APPLS >= 10000 = 3 [BI=YES] [BI=YES] Database Manager Configuration Parameters for OLAP workloads: ============================================================ > AGENT_STACK_SZ >= 128 [OS=WINDOWS].02.2011 Page 10 of 12 . you have to increase the parameter to 15000.02.0004].01.0000].01.
DB2 Registry Variables for OLAP workloads: ============================================================ > DB2_FORCE_FCM_BP = ON [BI=YES]. you should run with INTRA_PARALLEL=NO and MAX_QUERYDEGREE=1 and scale out to multiple database partitions (DPF) to make best use of your CPU power.2011 Page 11 of 12 . if INTRA_PARALLEL = YES > MAX_QUERYDEGREE > MAX_QUERYDEGREE > INTRA_PARALLEL >= 1 <= 4 = NO [BI=YES] [BI=YES] [BI=YES]. you can consider to set INTRA_PARALLEL=YES and MAX_QUERYDEGREE to a value between 2 and 4.SAP Note 584952 DB6: DB2 UDB Version 8 Standard Parameter Settings > SHEAPTHRES >= 40000 [BI=YES] Note: Shared memory for shared sorts is only allocated.[CUST] Note: To be specified.12. only if #(db partitions on one db server) > 1. This variable is only valid on AIX systems. Only in the exceptional case that you have 8 CPU cores or more and only one database partition. no BW-specific configuration of parameters and buffer pools is performed during the installation process.[CUST] Note: In general.x and related APO and SEM products.09. Tablespace Layout and Buffer Pool Recommendations for OLAP workloads: ===================================================================== For BW 2. see SAP Note 546262. the BW technology has become part of SAP NetWeaver.x. Therefore.2010 11:36:14 English Correction with high priority Consulting SV-BO Backoffice Service Delivery The Note is release-independent 16. Header Data Release Status: Released on: Master Language: Priority: Category: Primary Component: Secondary Components: BC-DB-DB6 DB2 Universal Database for Unix / NT Released for Customer 08. With SAP BW 3. BW 3.5. Make sure that you manually perform the necessary adaptations as described in this SAP Note and SAP Note 546262 after finishing the installation.
5 DB6: Additions to upgrade (based) on SAP Web AS 6.20 DB2 V7.2 Parameter settings for SAP Releases 4.SAP Note 584952 DB6: DB2 UDB Version 8 Standard Parameter Settings Related Notes Number 1493932 1493852 1493587 1474404 1329179 1308895 1293475 1250466 1086130 956214 940550 899322 820473 819876 780546 688647 679581 662191 603981 546262 490095 370026 369772 101809 99509 Short Text DB6: How to choose the extent size of DB2 tablespaces DB6: Use of alternate page cleaning DB6: Use of infinite logging or secondary log files DB6: Poor database performance with DB2AUDIT DB6: DB2 V9. SAP SEM DB6: Additional information on upgrading to SAP Web AS 6.2 FixPaks (as of FP9) on Win NT/Win 2000 DB6:Administration & Performance on SAP BW.1/V8.20 DB6: MAXLOCKS settings .7 Standard Parameter Settings DB6: File System for Transaction Log is Full DB6: Transaction Log Full DB6: Perform database administration.2 DB6: SAP BW and SAP NetWeaver BI Administration Tasks DB6: Additional information on upgrading to BW 3.5 Standard Parameter Settings DB6: SQL0443N after upgrade to a new SAP release DB6: Installing FixPak V8.40 DB6: Installing V8.1 Standard Parameter Settings DB6: Snapshot function returns error or hangs DB6: Additional info about upgrade (based) on SAP NW AS 7.2 (up to FP8) on Windows DB6: DB2 9.UNIX and Windows DB6: Analyzing&Improving Buffer Pool Performance 16. SAP SCM. keeping SAP AS running DB6: DB2 9.x/6.2011 Page 12 of 12 .detailed information DB6: Supported Fix Packs IBM DB2 for Linux.10/6.12.0 DB6: Use of new functions in DB2 V8.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.