how to kill the sap work process SAP and OS Level

From Sap:

Stopping Run-Away or "Bad" Work Processes

1. Log on to any client in the appropriate SAP system.

2. Go to transaction SM50.

3. On the Process Overview screen, find the process which must be

stopped. Place a √ in the □ to the left of the process number

to be stopped by pressing Space. On the top-most menu bar,

click the Process → Cancel without core.

4. Click the blue arrow circle picture-icon to refresh the Process

Overview screen until the stopped process has cleared from the

display.

5. You may now leave the SM50 transaction.

If this does not kill the process, you can go to transaction SM04 and kill the user's session. If this does not kill the process, you can log on to the server, open a Task Manager session, and End the Process. If this does not kill the session, there is an executable in the RUN directory on the server called sapntkill.exe. Run it providing the process ID number. If none of the above work, you have no choice but to "bounce" the SAP instance and/or possibly the serve

From OS Level(HP-UX or SOLARIS):

1)      Login as   <SID>adm

      #ps –ef | grep  <SID>adm

ps -ef |grep idsadm

  idsadm  7310  7309   0 23:00:38 pts/3       0:00 ps -ef

  idsadm  4201     1   0   Mar 17 ?           0:05 /usr/sap/IDS/DVEBMGS00/exe/sapstartsrv pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS0

  idsadm  4254  4212   0   Mar 17 ?           0:13 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  4253  4212   0   Mar 17 ?           0:01 ms.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  4212     1   0   Mar 17 ?           0:00 /usr/sap/IDS/DVEBMGS00/exe/sapstart pf=/usr/sap/IDS/SYS/profile/START_DVEBMGS00

  idsadm  7207  7203   0 22:59:44 pts/3       0:00 -sh

  idsadm  4255  4212   0   Mar 17 ?           0:00 co.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides -F

  idsadm  4256  4212   0   Mar 17 ?           0:00 se.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides -F

  idsadm  4257  4212   0   Mar 17 ?           0:00 ig.sapIDS_DVEBMGS00 -mode=profile pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhi

  idsadm  4258  4257   0   Mar 17 ?           0:42 /usr/sap/IDS/DVEBMGS00/exe/igsmux_mt -mode=profile -restartcount=0 pf=/usr/sap/

  idsadm  4259  4257   0   Mar 17 ?           0:21 /usr/sap/IDS/DVEBMGS00/exe/igspw_mt -mode=profile -no=0 -restartcount=0 pf=/usr

  idsadm  4260  4257   0   Mar 17 ?           0:21 /usr/sap/IDS/DVEBMGS00/exe/igspw_mt -mode=profile -no=1 -restartcount=0 pf=/usr

  idsadm  4263  4254   0   Mar 17 ?           0:02 gwrd -dp pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  4264  4254   0   Mar 17 ?           0:02 icman -attach pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  6221  4254   0   Mar 18 ?          12:47 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  4266  4254   1   Mar 17 ?          50:02 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  4267  4254   1   Mar 17 ?          38:57 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  6095  4254   1   Mar 18 ?          21:34 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  6184  4254   0   Mar 18 ?          16:14 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  6193  4254   1   Mar 18 ?          18:30 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  4271  4254   1   Mar 17 ?          42:12 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  6801  4254   1 10:46:39 ?           7:31 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  5623  4254   1   Mar 18 ?          14:06 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  6158  4254   0   Mar 18 ?           1:52 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  4275  4254   0   Mar 17 ?           0:04 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  4276  4254   0   Mar 17 ?           0:00 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  4277  4254   0   Mar 17 ?           0:16 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  4278  4254   0   Mar 17 ?           0:00 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  4279  4254   0   Mar 17 ?           0:00 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  4280  4254   0   Mar 17 ?           0:08 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  4281  4254   0   Mar 17 ?           0:00 dw.sapIDS_DVEBMGS00 pf=/usr/sap/IDS/SYS/profile/IDS_DVEBMGS00_mhilides

  idsadm  7309  7207   0 23:00:38 pts/3       0:00 grep idsadm

idsadm> dpmon

dpmon=>sapparam(1c): No Profile used.

dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

Dispatcher Queue StatisticsSat Mar 19 17:30:54 2011

===========================

+------+--------+--------+--------+--------+--------+

|  Typ |    now |   high |    max | writes |  reads |

+------+--------+--------+--------+--------+--------+

| NOWP |      0 |     14 |   2000 | 151119 | 151119 |

+------+--------+--------+--------+--------+--------+

|  DIA |      0 |      7 |   2000 | 114521 | 114521 |

+------+--------+--------+--------+--------+--------+

|  UPD |      0 |    102 |   2000 |   2345 |   2345 |

+------+--------+--------+--------+--------+--------+

|  ENQ |      0 |      0 |   2000 |      0 |      0 |

+------+--------+--------+--------+--------+--------+

|  BTC |      0 |      1 |   2000 |      2 |      2 |

+------+--------+--------+--------+--------+--------+

|  SPO |      0 |      3 |   2000 |   3592 |   3592 |

+------+--------+--------+--------+--------+--------+

|  UP2 |      0 |      0 |   2000 |      0 |      0 |

+------+--------+--------+--------+--------+--------+

max_rq_id34311

wake_evt_udp_now0

wake events      total267415,  udp241301 ( 90%),  shm 26114 (  9%)

since last updatetotal267415,  udp241301 ( 90%),  shm 26114 (  9%)

   q - quit

    m - menue

--> m

    Dispatcher-Monitor-Menue

    ------------------------

    d - dispatcher queue statistics

    p - work-process-admin-table

    l - work-process-admin-table (long)

    t - trace level/components for wp

    w - wp_ca blocks

    a - appc_ca blocks

    b - dump binary content of shared memory blocks

    c - comm adm blocks

    m - mbuf status

    s - service buffer status

    v - tm_ad dump

    z - sys_ad dump

    q - quit

--> p

Workprocess TableSat Mar 19 17:31:16 2011

=================

No Ty. Pid      Status  Cause Start Err Sem CPU    Time  Program  Cl  User        

----------------------------------------------------------------------------------

0 DIA     6221 Run           yes     0   0        4             000 SAPSYS      

 1 DIA     4266 Run           yes     0   0        41   SAPLSUGP 000 SAP*        

 2 DIA     4267 Run           yes     0   0        41   SAPLSUGP 000 SAP*        

 3 DIA     6095 Run           yes     0   0        38   SAPLSUGP 000 SAP*        

 4 DIA     6184 Wait          yes     0   0        0                             

 5 DIA     6193 Run           yes     0   0        0             000 SAP*        

 6 DIA     4271 Run           yes     0   0        52   SAPLSUGP 000 SAP*        

 7 DIA     6801 Run           yes     0   0        75   SAPLSUGP 000 SAP*        

 8 DIA     5623 Run           yes     0   0        71   SAPLSUGP 000 SAP*        

 9 DIA     6158 Wait          yes     0   0        0                             

10 UPD     4275 Wait          yes     0   0        0                             

11 ENQ     4276 Wait          yes     0   0        0                             

12 BTC     4277 Stop    ARFC  yes     0   0        402  RSPARAGE 000 SAP*        

13 BTC     4278 Wait          yes     0   0        0                             

14 BTC     4279 Wait          yes     0   0        0                             

15 SPO     4280 Wait          yes     0   0        0                             

16 UP2     4281 Wait          yes     0   0        0                             

    s - stop workprocess

    k - kill workprocess (with core)

    r - enable restart flag (only possible in wp-status "ended")

    q - quit

    m – menue

# k   <PIDnumber: ex: 6193>

Regards,

Alihamed.sa

DB2 9.5 Standard Parameter Settings

>!Version=1.0
This SAP Note is valid for the following system workload classes:

• 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 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.

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 Global Support. 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 that you are connected to the database (<DBSID>) first and then change the parameters using this existing connection. You can view currently active parameters using the following command:

db2 get db cfg for <dbsid> show detail

As of DB2 Version 9.1, the "Self Tuning Memory Manager" (STMM) was introduced. STMM is a memory-tuning feature that simplifies the task of memory configuration by automatically setting values for several memory configuration parameters. When enabled, the memory tuner dynamically adapts the sizes of consumers in the database shared memory (DATABASE_MEMORY). You can run your DB2 V9.5 database either with fixed memory settings or with STMM enabled. The STMM-relevant settings are marked with [STMM=YES] and [STMM=NO], respectively. For more information, see the section about DB2 STMM later in this SAP Note. Generally, we recommend that you use DB2 STMM for single partition systems.

The following markers are used in the parameter recommendation sections:

• [CUST]: Customer individual setting
  
  There is no particular setting required by SAP. The values listed for these parameters are typical default values that you should start with. If required, you can set the parameter differently.

• [DEPR]: Deprecated
  
  The parameter has become obsolete or deprecated with DB2 V9.5 and is ignored by DB2.

• [STMM=YES], [STMM=NO]: Related to the use of DB2's Self Tuning Memory Manager (STMM)

• If you want to use STMM, follow the recommendations marked with [STMM=YES]. Generally, we recommend that you use DB2 STMM for single partition systems.

• If you want to run your database with fixed memory settings, follow the recommendations marked with [STMM=NO].

• [BI=YES], [BI=NO]: Differs depending if your workload is primarily OLAP or OLTP

• If your workload is primarily OLAP-dominated (originating from SAP NetWeaver BW, SAP SRM or SAP SCM), follow the settings marked with [BI=YES].

• In all other cases, follow the recommendations marked with [BI=NO].

• [OS=WINDOWS], [OS=UNIX]: Requires different settings on Windows or UNIX-based database servers:

• If your database server is running on Windows, apply the settings marked with [OS=WINDOWS].

• If your database server is running on Linux, HP-UX, Solaris or AIX, apply the recommendation marked with [OS=UNIX].

• [FP>=nn.nn.nnnn], [FP<=nn.nn.nnnn]: Recommendation is valid for the given range of DB2 levels only

Multiple markers in one line are to be read as logical "AND", that is, the setting is recommended for configurations where all conditions are true.

For example, PARAM1 = 99 [FP<=09.05.0002], [OS=WINDOWS] means that you should set PARAM1=99 only if your DB2 level is up to and including 09.05.0002 (9.5FP2) AND your database server is running on Windows. If your database server is not running on Windows, or if you are using DB2 V9.5 FP3 or higher, do not apply the setting.

Database Manager Configuration Parameters (STMM Not Enabled)

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, enter the following command:
DB2 UPDATE DBM CFG USING <parameter> <value>



List of Parameters:
===================

> CPUSPEED            = <value>              [CUST]
> COMM_BANDWIDTH      = <value>              [CUST]

Note:
CPUSPEED and COMM_BANDWIDTH settings are generated by DB2 during instance creation based on hardware characteristics of your database server. To indicate that DB2 should regenerate the value, you can set the parameters to -1.

> NUMDB                = 8                   [CUST]
> FEDERATED            = NO                  [CUST]
> TP_MON_NAME          = <empty>             [CUST]
> DFT_ACCOUNT_STR      = <empty>             [CUST]
> JDK_PATH              = <path to JDK>       [CUST]

> DIAGLEVEL             = 3
> NOTIFYLEVEL           = 3

> DIAGPATH        = /db2/<DBSID>/db2dump         [OS=UNIX]
  DIAGPATH        = <drive>:\db2\<DBSID>\db2dump [OS=WINDOWS]

> DFT_MON_BUFPOOL       = ON
> DFT_MON_LOCK          = ON
> DFT_MON_SORT          = ON
> DFT_MON_STMT          = ON
> DFT_MON_TABLE         = ON
> DFT_MON_TIMESTAMP     = ON
> DFT_MON_UOW           = ON
> HEALTH_MON            = OFF                 [CUST]

> SYSADM_GROUP          = DB<DBSID>ADM
> SYSCTRL_GROUP         = DB<DBSID>CTL
> SYSMAINT_GROUP        = DB<DBSID>MNT
> SYSMON_GROUP          =                    [CUST]

> CLNT_PW_PLUGIN        =                    [CUST]
> CLNT_KRB_PLUGIN      =                     [CUST]
> GROUP_PLUGIN          =                    [CUST]
> LOCAL_GSSPLUGIN      =                     [CUST]
> SRV_PLUGIN_MODE      = UNFENCED            [CUST]
> SRVCON_GSSPLUGIN_LIST =                     [CUST]
> SRVCON_PW_PLUGIN      =                    [CUST]
> SRVCON_AUTH          = NOT_SPECIFIED       [CUST]
> CLUSTER_MGR          =                     [CUST]

> AUTHENTICATION        = SERVER_ENCRYPT      [CUST]
> CATALOG_NOAUTH        = NO
> TRUST_ALLCLNTS        = YES                 [CUST]
> TRUST_CLNTAUTH        = CLIENT              [CUST]
> FED_NOAUTH            = NO                  [CUST]

> DFTDBPATH            = /db2/<DBSID>        [CUST]

> MON_HEAP_SZ           = AUTOMATIC
> JAVA_HEAP_SZ          = 2048                [CUST]
> AUDIT_BUF_SZ         >= 0

Note:
AUDIT_BUF_SZ = 0 is sufficient if you are not using the DB2 Audit facility. If you want to use DB2 Audit, read SAP Note 1474404.

> INSTANCE_MEMORY      = AUTOMATIC           [STMM=NO]

> AGENT_STACK_SZ      >= 128                 [OS=WINDOWS]
> AGENT_STACK_SZ      >= 1024                [OS=UNIX],[BI=NO]
> SHEAPTHRES            = 0                   [STMM=NO],[CUST]

> DIR_CACHE             = NO

> ASLHEAPSZ             = 16
> RQRIOBLK              = 65000
> UTIL_IMPACT_LIM      = 10                  [CUST]

> AGENTPRI              = SYSTEM
> NUM_POOLAGENTS        = AUTOMATIC

> NUM_INITAGENTS        = 5                   [CUST]
> MAX_COORDAGENTS       = AUTOMATIC
> MAX_CONNECTIONS       = AUTOMATIC

> KEEPFENCED          = YES                  [FP>=09.05.0003]
> KEEPFENCED          = NO                  [FP<=09.05.0002]

Note:
As of DB2 V9.5 FP3 and higher, use KEEPFENCED=YES (as of DB2 V9.5 FP3 DB2_WORKLOAD=SAP enables DB2_AGENT_CACHING_FMP=OFF, which allows an efficient use of KEEPFENCED=YES). On previous Fix Pack levels, set KEEPFENCED=NO.

> FENCED_POOL         >= 10
> NUM_INITFENCED       = 0

> INDEXREC             = RESTART

> TM_DATABASE          = 1ST_CONN             [CUST]
> RESYNC_INTERVAL      = 180                  [CUST]

> SPM_NAME             =                      [CUST]
> SPM_LOG_FILE_SZ      = 256                  [CUST]
> SPM_MAX_RESYNC      = 20                   [CUST]
> SPM_LOG_PATH         =                      [CUST]

> SVCENAME            = sapdb2<DBSID>        [CUST]
> DISCOVER            = SEARCH               [CUST]
> DISCOVER_INST        = ENABLE               [CUST]

> MAX_QUERYDEGREE      = 1                    [BI=NO]
> INTRA_PARALLEL      = NO                   [BI=NO]

> FEDERATED_ASYNC      = 0

> FCM_NUM_BUFFERS      = AUTOMATIC
> FCM_NUM_CHANNELS     = AUTOMATIC
> CONN_ELAPSE          = 10                   [OS=UNIX]
> MAX_CONNRETRIES      = 5                    [OS=UNIX]
> MAX_TIME_DIFF        = 60                   [OS=UNIX]

> START_STOP_TIME      = 10                   [CUST]

Database Configuration Parameters (STMM Not Enabled)

The following database configuration parameters are grouped according to the output that you receive if you use the following command:


db2 get db cfg for <dbsid>

To update the parameters, enter the following command:


DB2 UPDATE DB CFG FOR <DBSID> USING <parameter> <value>

List of Parameters:
===================

> ALT_COLLATE          = IDENTITY_16BIT       [CUST]

Note:
This setting applies only to non-Unicode databases!

> DYN_QUERY_MGMT        = DISABLE
> DISCOVER_DB          = ENABLE             [CUST]

> DFT_QUERYOPT          = 5
> DFT_DEGREE            = 1
> DFT_SQLMATHWARN       = NO
> DFT_REFRESH_AGE       = 0
> DFT_MTTB_TYPES        = SYSTEM
> NUM_FREQVALUES        = 10
> NUM_QUANTILES         = 20

> DECFLT_ROUNDING       = ROUND_HALF_EVEN

> SELF_TUNING_MEM      = OFF                 [STMM=NO]
> DATABASE_MEMORY      = COMPUTED            [STMM=NO]
> DB_MEM_THRESH        = 10                  [CUST]
> LOCKLIST            >= 20000               [STMM=NO];[BI=NO]
> MAXLOCKS              = 90                  [STMM=NO];[CUST]
> PCKCACHESZ          >= 5120                [STMM=NO]
> SHEAPTHRES_SHR      >= 20000               [STMM=NO];[BI=NO]

Note:
Set SHEAPTHRES_SHR to the number of your SAP workprocesses multiplied with SORTHEAP but not lower than 20000.

> SORTHEAP            >= 2048                [STMM=NO];[BI=NO]

> DBHEAP                = AUTOMATIC
> CATALOGCACHE_SZ      >= 2560
> LOGBUFSZ             >= 1024
> UTIL_HEAP_SZ         >= 50000
> BUFFPAGE             >= 10000
> STMTHEAP              = AUTOMATIC
> APPLHEAPSZ            = AUTOMATIC
> APPL_MEMORY           = AUTOMATIC
> STAT_HEAP_SZ          = AUTOMATIC

> DLCHKTIME            = 10000              [CUST]
> LOCKTIMEOUT          = 3600               [CUST]

> CHNGPGS_THRESH        = 20                 [CUST]
> NUM_IOCLEANERS        = AUTOMATIC          [CUST]
> NUM_IOSERVERS        = AUTOMATIC          [CUST]
> INDEXSORT             = YES
> SEQDETECT             = YES
> DFT_PREFETCH_SZ       = AUTOMATIC

> TRACKMOD              = ON                 [CUST]
> DFT_EXTENT_SZ        = 2                  [CUST]

> MAXAPPLS              = AUTOMATIC
> AVG_APPLS             = AUTOMATIC
> MAXFILOP            >= 61440              [CUST]

> LOGFILSIZ            = 16380              [CUST]
> LOGPRIMARY           >= 60
> LOGSECOND             = 0

Note:
If you want to configure LOGSECOND to a value other than zero, read SAP Note 1493587 and related SAP FAQ note 1497040.

The primary log files are created at the time of the first database activation or after any change to the log configuration.

We recommend that you do not configure less than 4GB log space. If you change any of the parameters LOGFILSIZ, LOGPRIMARY or LOGSECOND you must ensure that you have enough space allocated in your LOGPATH.

> OVERFLOWLOGPATH      =                    [CUST]
> MIRRORLOGPATH        =                    [CUST]
> BLK_LOG_DSK_FUL      = YES                [CUST]
> BLOCKNONLOGGED        = NO                 [FP>=09.05.0004]

Note:
If you want to set BLOCKNONLOGGED to YES, read SAP Note 1523227 for more information.

> MAX_LOG              = 0                  [CUST]
> NUM_LOG_SPAN          = 0                  [CUST]

Note:
After every change of LOGFILSIZ, LOGPRIMARY or LOGSECOND you should check your 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 value unit is percent, based on the size of one log file (LOGFILSZ * page size 4 KB).
In case you have set LOGFILSIZ to a large value, you may consider to lower the value of SOFTMAX accordingly. For example, if you have LOGFILSIZ set to 50000 or higher, you may want to reduce SOFTMAX from 300 to 100.

> LOGRETAIN            = OFF                [DEPR]
> USEREXIT              = OFF                [DEPR]

> HADR_LOCAL_HOST        =                  [CUST]
> HADR_LOCAL_SVC        =                   [CUST]
> HADR_REMOTE_HOST      =                   [CUST]
> HADR_REMOTE_SVC        =                  [CUST]
> HADR_REMOTE_INST      =                   [CUST]
> HADR_TIMEOUT          = 120               [CUST]
> HADR_SYNCMODE          = NEARSYNC          [CUST]
> HADR_PEER_WINDOW      = 0                 [CUST]

> LOGARCHMETH1          = OFF               [CUST]

Note:
For information about the DB2 log manager, see SAP Note 913481.

> LOGARCHOPT1            =                  [CUST]
> LOGARCHMETH2          = OFF               [CUST]
> LOGARCHOPT2            =                  [CUST]
> FAILARCHPATH          =                   [CUST]
> NUMARCHRETRY          = 5                 [CUST]
> ARCHRETRYDELAY        = 20                [CUST]
> VENDOROPT              =                  [CUST]

Note:
You must enable your  production databases for recovery. For more information about the DB2 log manager, see SAP Note 913481.

> AUTORESTART            = ON
> INDEXREC               = RESTART
> LOGINDEXBUILD          = OFF               [CUST]

Note:
If you are using HADR, set LOGINDEXBUILD=ON.

> DFT_LOADREC_SES        = 1                 [CUST]
> NUM_DB_BACKUPS        = 12                [CUST]
> REC_HIS_RETENTN        = 60                [CUST]
> AUTO_DEL_REC_OBJ      = OFF               [CUST]

> TSM_MGMTCLASS          =                  [CUST]
> TSM_NODENAME          =                   [CUST]
> TSM_OWNER              =                  [CUST]
> TSM_PASSWORD          =                   [CUST]

> AUTO_MAINT             = ON
> AUTO_DB_BACKUP        = OFF               [CUST]
> AUTO_TBL_MAINT         = ON
> AUTO_RUNSTATS          = ON
> AUTO_STMT_STATS        = ON
> AUTO_STATS_PROF        = OFF
> AUTO_PROF_UPD          = OFF
> AUTO_REORG            = OFF               [CUST]

Note:
For more information about parameter AUTO_REORG, see SAP Note 975352.

> ENABLE_XMLCHAR         = YES
> WLM_COLLECT_INT        = 0

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> =

You must set the following registry variable(s) unless you receive different instructions from SAP support:

> DB2_WORKLOAD           = SAP

Note:
Make sure that you do not ovewrite DB2_WORKLOAD settings unless SAP support explicitly requests you to do so. Check that the output of the "db2set -all" command does not show any lines that end with "[O]".

> DB2_PARALLEL_IO        = *                [CUST]

Note:
Only set DB2_PARALLEL_IO=* if the following conditions are both met:

• RAID devices are used for the database

• All tablespaces in the database consist of one single container per stripe set

Settings with DB2's Self Tuning Memory Manager (STMM) Enabled

DB2 "Self Tuning Memory Manager" (STMM) simplifies the task of memory configuration by automatically setting values for several memory configuration parameters. When enabled, the memory tuner dynamically distributes available memory resources among the following memory consumers:

• Buffer pools

• Locking memory

• Package cache

• sort memory.

STMM works within the memory limits that are defined by the DATABASE_MEMORY configuration parameter. The value of this parameter can be automatically tuned as well by setting the value of the DATABASE_MEMORY configuration parameter to AUTOMATIC. If the DATABASE_MEMORY configuration parameter is set to a numeric value, the database uses the amount of memory that has been specified, distributing it across the memory consumers as required. If DATABASE_MEMORY is set to COMPUTED, the total amount of DATABASE_MEMORY is computed on the sum of the initial values of the database memory heaps at database startup time.

You can enable the memory consumers for self tuning as follows:

• For bufferpools, use the ALTER BUFFERPOOL statement (specifying the AUTOMATIC keyword) to enable the bufferpool for self tuning

• For locking memory, set LOCKLIST and MAXLOCKS to AUTOMATIC

• For the package cache, set PCKCACHESZ to AUTOMATIC

• For sort memory, set SHEAPTHRES_SHR and SORTHEAP to AUTOMATIC

Changes resulting from self-tuning operations are recorded in memory tuning log files that are located in the "stmmlog" subdirectory. These log files contain summaries of the resource demands from each memory consumer during specific tuning intervals that are determined by timestamps in the log entries.

If self-tuning memory manager (STMM) is active and DATABASE_MEMORY is set to AUTOMATIC, STMM checks the free memory available on the system and automatically determines how much memory to dedicate to performance heaps for optimal performance. All the performance heaps contribute to the overall DATABASE_MEMORY size. The difference between INSTANCE_MEMORY and DATABASE_MEMORY is available for application memory (APPL_MEMORY) use and is allocated as needed.

When using STMM we recommend that you do the following:

• To assign a dedicated portion of memory to DB2, set INSTANCE_MEMORY to a fixed value.

• To enable self tuning of database shared memory, set DATABASE_MEMORY to AUTOMATIC. Alternatively, you can set DATABASE_MEMORY to a numeric value to assign a fixed region for database shared memory. Do not use DATABASE_MEMORY=COMPUTED with STMM.

STMM is globally controlled by the database manager parameter SELF_TUNING_MEM. If at least two tuneable consumers are available, you activate STMM by setting parameter SELF_TUNING_MEM to ON. Setting parameter SELF_TUNING_MEM to OFF deactivates STMM, regardless if any memory consumers are still enabled for STMM. If STMM is turned off, the consumers will remain at their current size.

You can enable all memory consumers or a subset for STMM. You can deactivate STMM for an individual memory consumer or for all memory consumers at any point in time. For STMM to be active, a minimum of two consumers must be eligible. In general, you should enable all consumers for self-tuning when you activate STMM. This allows DB2 to best distribute the available memory to all consumers.

You can enable individual memory consumers for STMM tuning by setting them to AUTOMATIC. Some consumers are controlled by configuration parameters (DATABASE_MEMORY, LOCKLIST, MAXLOCKS, PCKCACHESZ, SHEAPTHRES_SHR, SORTHEAP). Buffer pools, however, must be explicitely enabled using the following statement:

ALTER BUFFERPOOL <bp_name> SIZE AUTOMATIC

In a distributed database server (DPF) STMM tuning works uniformly. That is, STMM runs on one partition only and propagates parameter changes to all other partitions with SELF_TUNING_MEM enabled. The partition that STMM runs on is determined via the "update stmm tuning dbpartitionnum" command. You can query the currently active STMM partition using the "get stmm tuning dbpartitionnum" command.

Uniform STMM with DPF is typically not suitable for SAP workloads. We recommend that in a distributed database server you only enable STMM tuning on the catalog partition (partition 0). You should tune all other partitions manually. For more information about STMM and DPF, see SAP Note 1132282.

How you activate STMM:

1. Set INSTANCE_MEMORY to a fixed value of least 125000 pages or more using the following command:

db2 update dbm cfg using INSTANCE_MEMORY <value>

2. To enable self tuning for all consumers, update your database manager and database configuration using the following command:

db2 update dbm cfg using SHEAPTHRES 0
db2 update db cfg for <DBSID> using DATABASE_MEMORY AUTOMATIC LOCKLIST AUTOMATIC MAXLOCKS AUTOMATIC PCKCACHESZ AUTOMATIC SORTHEAP AUTOMATIC SHEAPTHRES_SHR AUTOMATIC

3. Enable STMM tuning for all your buffer pools using the following command:

db2 alter bufferpool <bp_name> size AUTOMATIC

4. To activate STMM, enter the following command:

db2 update db cfg for <DBSID> using SELF_TUNING_MEM ON

How you deactivate STMM:

1. To deactivate STMM, enter the following command:

db2 update db cfg for <DBSID> using SELF_TUNING_MEM OFF

2. After you changed SELF_TUNING_MEM to value 'OFF', your database continues to use the settings that were active at the time when STMM was switched off. You can either continue to use these settings or update your configuration to fixed values as needed.

Recommended Database Manager Configuration with STMM Enabled:
=============================================================

> INSTANCE_MEMORY      >= 125000          [STMM=YES]


Recommended Database Configuration with STMM Enabled:
=====================================================

> SELF_TUNING_MEM      = ON              [STMM=YES]
> DATABASE_MEMORY       = AUTOMATIC       [STMM=YES]
> LOCKLIST              = AUTOMATIC       [STMM=YES]
> MAXLOCKS              = AUTOMATIC       [STMM=YES]
> PCKCACHESZ            = AUTOMATIC       [STMM=YES]
> SHEAPTHRES_SHR        = AUTOMATIC       [STMM=YES]
> SORTHEAP              = AUTOMATIC       [STMM=YES]

Typical Parameter Settings for SAP NetWeaver Business Warehouse (SAP NetWeaver BW) and All SAP Systems Based on SAP NetWeaver BW:

Database Manager Configuration Parameters for OLAP workloads:
============================================================

> AGENT_STACK_SZ      >= 4096            [OS=UNIX],[BI=YES]

> MAX_QUERYDEGREE      >= 1               [BI=YES]
> MAX_QUERYDEGREE      <= 4               [BI=YES]
> INTRA_PARALLEL        = NO              [BI=YES];[CUST]

Note:
In general, 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.

Only in the exceptional case that you have 8 CPU cores or more and only one database partition, you can consider to set INTRA_PARALLEL=YES and MAX_QUERYDEGREE to a value between 2 and 4.

Database Configuration Parameters for OLAP Workloads:
=====================================================

> SHEAPTHRES_SHR      >= 40000           [STMM=NO];[BI=YES]

Note:
You should set SHEAPTHRES_SHR to "Number SAP WP" x "SORTHEAP". The value should be at least 40000 pages but no more than max 1/4 of the physical memory that is available for one database partition. We also recommend that you read the IBM DB2 Version 9.5 manuals to understand the dependencies between SHEAPTHRES and SORTHEAP.

> LOCKLIST            >= 40000           [STMM=NO];[BI=YES]
> SORTHEAP            >= 15000           [STMM=NO];[BI=YES]

Note:
For SAP APO/SCM systems, a smaller value of 4096 or more might be sufficient. However, if problems related to sort performance occur or iflarge Infocubes with Aggregates are used, you have to increase the parameter to 15000.

SAP DB2 License Issue or db2 service not starting in db2diag.log

DB2 License Issue

In DB2 , the SAP OEM license has to be applied after 90 days. If you don't apply then the database won't start. The procedure is different from Oracle as you need to log into the DB2 CLP to apply the license. Please find below the procedure:

Windows:

1. Login as db2<SID>
2.Go to Start -> All Programs ->IBM DB2 -> SAPDB2SOL -> Command Line Tools -> Command Window
3. Now apply license here as per SAP Note 816773.Even with db2cmd we were not getting the actual license status.

Db2

Solaris / SOLARIS  /Unix

Updating the DB2 product license key

This task is part of the main task of Setting up a DB2 server after manual installation.

Updating the DB2 product license key is done by running the db2licm command and specifying the license file name for your DB2 product.

You must install a license key on each computer where DB2 is installed.

Procedure

To update your DB2 product license key using root authority:

1. Log in db2<SID>.
2. Update the DB2 product license key with the appropriate command:

License files Copy to  /tmp location

3.  #cd /tmp/licensefiles

4.  #db2licm

It will show License expired or not.

5.  #db2licm -a filename  on SOLARIS

6.  #db2licm -a filename  for all

7.   other UNIX-based operating systems

where filename is the full pathname and filename for the license file that corresponds to the product you have purchased. The license file is located in the /db2/license directory located at the root of your CD-ROM.

For example, on SOLARIS , if the CD-ROM is mounted in the /cdrom directory and the name of the license file is db2dlm.lic, the command should be as follows:

     /usr/opt/db2_09_07/adm/db2licm -a /cdrom/db2/license/db2dlm.lic

The DB2 product license key exists in the following directories dependent on platform:

• For SOLARIS , the product license keys are located in /var/ifor.
• For HP-UX, the product license keys are located in /var/lum.
• For the Solaris operating environment, the product license keys are located in /var/lum.
• For Linux, the product license keys are located in /var/lum.

To update your DB2 product license key as the instance owner:

1. Create the instance environment and become the instance owner.
2. Update your DB2 product license with the appropriate command:
1. On SOLARIS  enter:

b.       /usr/opt/db2_09_07/adm/db2licm -a filename

3. On all other UNIX-based operating systems enter:

3.        /opt/IBM/db2/V8.1/adm/db2licm -a filename

Regards,

Alihamed.sa,

Basis Administrator.

SAP Web Dispatcher Administration

SAP Web Dispatcher Administration

Definition
From SAP Glossary , SAP Web Dispatcher is an SAP solution for load distribution for HTTP(S) requests. If an SAP system consists of multiple instances, the SAP Web Dispatcher receives the requests from the browser and forwards them to the application server that currently has most capacity. This simplifies administration since there is only one entry point (IP address, HTTP(S) port, and so on) to the SAP system.
Administration
Installation
Command for installing webdispatcher :
sapwebdisp pf=<profile file>
Sapwebdisp can also be started using bootstrap options, which then created sapwebdisp.pfl and icmauth.txt if these don't exist :
sapwebdisp -bootstrap
For Windows NT you can install the service with this command :
ntscmgr install sapwebdisp -b <program_path>\sapwebdisp.exe -p "service pf=<profile file> <options>"
To kill sapwebdisp service you can use this command, in Windows :
sapntkill -INT <PID>
In Unix you can use this command to kill the running process:
kill -2 <PID>
Monitoring
You can monitor SAP Web Dispatcher from icmon command line program or Web Interface http://<server with domain>:<SAP Web Dispatcher port>/<admin prefix>. SAP Webdispatcher process is specified in parameter icm/server_port_0 and admin prefix is specified in icm/HTTP/admin_0. Both parameters are specified in profile file.
Useful Command
sapwebdisp -v -> check SAP Web Dispatcher version
sapwebdisp -checkconfig pf=<profile> -> check configuration which connect to certain message server.
Profile parameter
icm/server_port_<x> : port to receive HTTP request
rdisp/mshost : message server host to be accessed
ms/http_port : message server port to be accessed

SAP System Monitoring

SAP System Monitoring

Can you imagine if you have a job to monitor the whole SAP system and also non SAP system? Okay, let's say that you only have 3 system landscapes, that would  be very easy to monitor, check the system one by one. But if you have hundreds of systems, how will you manage the system monitoring? Before we continue to the basic concept for system monitoring, we should answer this question: Why do we need to monitor SAP system? For some of you may be that's a silly question, but for this little question will save your a lot of effort to monitor the system both SAP or non SAP.


The picture above explain the architecture for Central Monitoring. It means we have one system as a central system to maintain all connected agent, which later we call it CCMS Agent. Btw, What does CCMS stands for ? CCMS is Computing Center Management System.  Basically, we can use transaction code :

• RZ20 : Display CCMS architecture as an alert monitor.
• RZ21 : To set the global customizing setting for the alert monitor.

We have several functional principles of the CCMS Agent which are:

• SAPCCMSR. This agent monitors components on which there's no active SAP instance (such as log files, TREX, stand-alone database or operating system components. Now, SAPCCMSR has extended j2ee options to monitor J2EE Engine.
• SAPCCM4X. This agent improves the monitoring of ABAP instance with SAP Basis 4.x or higher. The central monitoring system must have a release status of at least SAP Basis 4.6C. that's why this is called 4X.
• SAPCM3X. This agent allow the monitoring of SAP Instance with SAP basis 3.x through the CCMS monioring architecture.

Now, here's the quick steps to intall and operate remote CCMS Agent:

1. You have central monitoring system (CEN). Create CSMREG user in CEN using SU01.
2. Generate file CSMCONF file in CEN before agent registration. In CEN, call transaction RZ21 and choose Technical Infrastructure -> Configure Central System -> Create CSMCONF Start File for Agents.
3. Download executable CCMS Agent.
4. Installing an Agent. For example we want to install agent on ABAP instance. For Windows: [drive]:\usr\sap\<SysID>\SYS\exe\run\sapccm4x -R pf=<profile path>
   For UNIX: /usr/sap/<SysID>/SYS/exe/run/sapccm4x -R pf=<profile path>
5. During the registration, the system displays specifications from the CSMCONF to you again for confirmation. Confirm the specifications by pressing the ENTER key in each case. You only need to enter two parameters yourself:
   • The password for the administration user in CEN, under which you created the CSMCONF file.
   • The password for the CSMREG user.

That's it. simple isn't it? After you register the agent, after few seconds or may be in minutes you will see the agent status on CEN. Of course this is just a little part for CCMS System monitoring. You can download the full information for SAP System Monitoring using CCMS on the link below. By understanding the concept of this reference, I think you will be a CCMS expert. Enjoy !

Reorganize Table in SAP

Reorganize Table in SAP

Why do we need to reorganize table in SAP system ?
This is the important question before we plan to reorganize table in SAP system. Since Data Management Strategy is the key factor to boost system performance and and to keep data accessibility more efficient, we need to maintain or oraganize the data itself. One of the strategy is to reorg certain table which can impact on system performance. Reorganizing table can also be used to improve database structure, transform dictionary managed to locally managed tablespace, merge data in tablespace from many small files into larger files and perform segments defragmentation.
What types of reorganization is provided by SAP using BR*Tools?
You can perform the following types of reorganization:

• Reorganize tables online
• Check tables for reorganization
• Clean up tables after aborted reorganization
• Convert LONG and LONG RAW fields to CLOB or BLOB online (Oracle 10g or higher)
• Stop reorganization (command-line mode only)
• Suspend reorganization (command-line mode only)
• Resume reorganization (command-line mode only)

What is the procedure to perform reorganization using BR*Tools ?

1. Run BRTOOLS. Choose Segement Management or run from the command prompt brspace –f tbreorg.
2. Enter table name in Table names (table).
3. Choose Reorganize Tables.
4. Set the required option like new destination tablespace or set the parallel thread which will be used to perform reorganization. The more you set the thread, the faster your process will be. But this limited to the CPU specification in OS level.
5. Choose continue to start processing.
6. Check the detail log in s<encoded timestamp>.tbr.

Please take note that this online reorganization will impact on system performance, therefore you need to run this when the system load is low

SAP DB2 RESTORE BACKUP

before restore Database in db2

login as db2<SID>

# db2start

# db2 restore database <SID>    from /<taken backup location>

*******After restore database we need to apply archive logs to database******

#db2 rollforward db  <SID>  to end of logs

********* if there is no logs to apply please enter below command before connect DATABASE or SAP************

#db2 rollforward db <SID> COMPLETE 

Regards,

Alihamed.sa.

DB2 Offline backup SAP ECC 6.0 in Solaris 10

SAP Offline Backup from DB2 V9.7.

log in as db2<sid>  ,

# db2stop   <db2 stop before taking offline  backup>

# db2start   <after stop db restart database>

# db2 connect to <SID>

# db2 backup db SID to /<backup location in linux>

Thanks and Regards ,

Alihamed.sa.