How to reset root password on a HP-UX Integrity system

How to reset root password on a HP-UX Integrity system

Login to the console.

Enter the command menu:
MP> CM
Halt the system:
CM> RS
Go back to the MP> prompt by typing CTRL B then go back to the console:
MP> CO

When the system comes back with a series of boot options, highlight the HPUX boot option, click enter and click enter again to interrupt the boot process. Then boot in single user mode:

HPUX> hpux -is
Once the system has come up, you will have to mount the following file systems: /usr, /var, /var/tmp, /opt and /tmp. You will also have to fsck them.
# TERM=vt100
# export TERM

Find out which file systems need to be mounted:
# cat /etc/fstab
Mount the relevant file systems:
# mount /dev/vg00/lvol7 /usrUX:vxfs mount: ERROR: V-3-21268: /dev/vg00/lvol7 is corrupted. needs checking

# fsck /dev/vg00/lvol7log replay in progress
replay complete - marking super-block as CLEAN

# mount /dev/vg00/lvol7 /usr

# mount /dev/vg00/lvol9 /var
UX:vxfs mount: ERROR: V-3-21268: /dev/vg00/lvol9 is corrupted. needs checking

# fsck /dev/vg00/lvol9
log replay in progress
replay complete - marking super-block as CLEAN

# mount /dev/vg00/lvol9 /var

# mount /dev/vg00/lvol11 /var/tmp
UX:vxfs mount: ERROR: V-3-21268: /dev/vg00/lvol9 is corrupted. needs checking

# fsck /dev/vg00/lvol11log replay in progress
replay complete - marking super-block as CLEAN

# mount /dev/vg00/lvol11 /var/tmp

Repeat with /opt and /tmp

Remove root password:
# cd /tcb/files/auth/r
# vi rootRemove the line beginning with :u_pwd
Save the file and exit

# passwd rootType your chosen password. Make sure there is a numeric character.

Reboot the system:
# shutdown -r
NOTE: if your system isn’t a Trusted Computer Base system, there won’t be a /tcb directory. Therefore, you will have to:
# vi /etc/passwdRemove the password field from the root entry and save the file.

Reboot the system:
# shutdown -r
When the system comes back up:
# passwd rootType your chosen password. Make sure there is a numeric character.

SAP* User unlock and Delete

SAP* User unlock

****************************

db2 => update SAPIDS.USR02 set UFLAG=0 where BNAME='SAP*' and MANDT='000'

DB20000I  The SQL command completed successfully.

**************************************

SAP* User Delete

***********************************

db2 => DELETE SAPIDS.USR02  where BNAME='SAP*' and MANDT='000'

DB20000I  The SQL command completed successfully.

db2 =>

Configuring NFS on Solaris 10 for SAP Distributed System

Step 1: enable NFS sever by running the following:

      svcadm -v enable -r network/nfs/server

Step 2: Run the following command to share via NFS

      share -F nfs -o rw /db2

      share –F nfs –o rw /sapmnt

Note: The above share command will not persist over reboots. To persist over reboots, add an entry to /etc/dfs/dfstab

      share -F nfs -o rw /db2

      share –F nfs –o rw /sapmnt

Step 3: Run the following command to mount from the client side:

                # mkdir  /db2

      # mkdir /sapmnt

      mount -F nfs server:/db2 /db2

      mount -F nfs server:/sapmnt /sapmnt

Note: The above mount command will not persist over reboots. To persist over reboots, add the following line in /etc/vfstab

        server:/db2   -   /db2   nfs   -   yes    rw,soft

        server:/sapmnt   -   /sapmnt   nfs   -   yes    rw,soft

         

Creating Remote Client Copy SCC9

Creating Remote Client Copy SCC9

Step by Step Procedure to copy a Client to the Remote SAP Server.

• Logon to destination SAP server

• Use Transaction Code SCC4

• Go to change mode

• Create a new client, assign client number & description as per request

• Logoff from current client.

• Login to newly created client in destination SAP server using the following credentials :

i. Client Number : Newly created one

ii User Id : SAP*

iii Password : PASS

• Use Transaction Code SM59 to create a RFC Connection for client copy if does not exist already.

• RFC Connection should have Target Server as Destination and the test results should say “Connection test OK”

• Use SCC9 Transaction code to go to client copy screen.

• Give profile as per the request.

• Select RFC destination created for the purpose for the source client to client copy

• Use Transaction code SCC3 for monitoring the progress of client copy

___________________________________________________________________

Golden rules for CLIENT Copies

1. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data.

2. Application data (transactional and master) should not be copied without copying configuration data.

3. Client copy requires a valid client as the destination client. Make sure that the client exists in T000 table and you can logon to that client.

4. The transport system and the transport management system of 4.0 are the only proper tool to be use to keep multiple systems in sync by transporting development and customizing changes to another instance.

5. When you copy a client from one system to another, client-independent tables should only be copied if they are not yet modified in the target system.

6. We recommend the users to read all the OSS notes regarding client copy that applies to their SAP release. It is always better to schedule the client copy job in the background for the night run when normal work is not taking place.

7. Always check the database space before performing a client copy.

8. To avoid data inconsistencies all the users working in the source and target clients should logoff from the system.

9. RSCLICHK program should be run in the target system remotely before doing a client export. This program will give information about the missing definitions from the data dictionary in the target. After executing this program and getting successful results you can ensure that the client copy will have no problems. In case some tables are different; you can use SE11 to compare and adjust the table structure in both the system before the client copy. A remote test client copy also can be executed to know the differences between source client and target client.

10. If you are not in release 2.2 then do not use R3trans to copy a client.

Email configuration in sap

When e-mails are transferred using SMTP, the SAP Web Application Server communicates directly with a mail server. No gateway or connector is necessary.
You can use any SMTP-compatible product as a mail server.
The SAP system always transfers the outbound mails to a single mail server. You can set its host address and port number.
The SAP system can receive inbound mails from any number of mail servers. You can reach each client using separate, configurable port numbers. You can address the SAP system or its client most effectively by using an individual subdomain for each client (for example, "crm-prod.company.com"). The assignment of these subdomains to host name and port numbers of the SAP system is defined by the routing rules on the mail servers.
As of Release 6.20, you can also send and receive fax and SMS or paging messages using SMTP. These are packed in e-mails for this purpose. When sending, the mail server refers to the domain of the recipients' addresses, and directs the e-mails either to a internal company fax/SMS server (for example "SMS=+491759628717@sms-server.company.com") or to an external provider (for example, "FAX=+16105954900@fax-provider.com"). When receiving, the fax or SMS server or the provider sends e-mails to addresses with the domain of the SAP system (for example "FAX=+496227751624@crm-prod.company.com").

Configuration

1.     Profile parameter
To be able to use the SMTP functions, you must adjust the profile of the SAP Web Application Server. We recommend that you activate SMTP on all application servers of an SAP system. If this is not the case, the SAPconnect send job may only be scheduled for servers on which SMTP is active. The scheduling is then done by the standard job definition (transaction SM36) rather than by the SAPconnect administration (transaction SCOT, for a description, see 4.c).

2.    

3.    

4.    
For SMTP, you must set the profile parameters listed below. The placeholder <*> stands for a number with which the parameters that can occur several times are numbered sequentially, starting with 0.

a) icm/server_port_<*> = PROT=SMTP,PORT=<port>
This opens a TCP/IP port for receiving mails by the SMTP Plug-In. <port> specifies the number of the port that you should use.  This must not be occupied by any other program on this host (for example, Sendmail usually uses port 25). If no mails (including status notifications) are to be received in this SAP system, <port> can be set to 0.
You can use the TIMEOUT option to define a maximum wait time for a response from the mail server (in seconds).

b) is/SMTP/virt_host_<*> = <host>:<port>,<port>,...;
This defines a "virtual mail host" for receiving mails. If all incoming mails (including status notifications) are to be received and processed in a single client of this SAP system, this parameter is not required (an entry is/SMTP/virt_host_0 = *:* is then assumed by default). If you want several clients to be able to receive, you must create a virtual mail host for every client. <host> specifies the name of the host to which incoming mails are addressed. The "*" value can also be specified here if the mail distribution is to occur independently of the addressed host. Important: If the mail is to be distributed according to host names, you must assign different IP addresses to these host names. <port> specifies the number of a port to which incoming mails are addressed. Several ports may be specified for each host, and several hosts (with several ports if necessary) may be specified for each virtual mail host. Important: The parameter line must always be completed with a semicolon (even if only one host is involved).
The assignment of virtual mail hosts to clients is carried out in the SAP system (see 3).

              Example:
With two clients capable of receiving mail, the profile parameters could read as follows (as of Release 6.20):
   icm/server_port_0 = PROT=HTTP,PORT=1080
  icm/server_port_1 = PROT=HTTPS,PORT=1443
  icm/server_port_2 = PROT=SMTP,PORT=25000,TIMEOUT=180
  icm/server_port_3 = PROT=SMTP,PORT=25001,TIMEOUT=180
  is/SMTP/virt_host_0 = *:25000;
   is/SMTP/virt_host_1 = *:25001;

2. User administration (transaction SU01)

a) System user
In each client of an SAP system in which incoming mails (or status notifications for sent mails) are to be received, a system user must be created to process the incoming messages. To do this, use transaction SU01 to create a user of the type "system", and assign the "S_A.SCON" profile to this user.
Important: Contrary to the documentation for user types, users of type "system" are also subject to password expiry, which can prevent the receipt of mails. To avoid this, use user type "service" until a correction of the incorrect behavior of type "system" is available.

b) User addresses
Each individual user who wants to receive e-mails in an SAP system needs an Internet mail address. This is also used as a sender address for sending e-mails. In transaction SU01, enter the Internet mail address of a user in the field "E-Mail" under "Address". As a domain, use the domain of the SAP system client if possible (see "General information" above and 4.a), for example "firstname.lastname@crm-prod.company.com".

3. Client assignment (transaction SICF)
For each client of an SAP system in which incoming mails (or status notifications for sent mails) are to be received, and processed if necessary, you must create an SMTP server in which the assignment to a virtual mail host as well as the logon data is defined. In transaction SICF, an SMTP server (envelope icon) should already be available in every SAP system. This is delivered by SAP. Use this for the first client that you want to be able to receive mails, and create a new SMTP server for every other client. You must make the following settings on the SMTP servers:

a) Host data
For "Profile Parameter Number", enter the sequence number of a parameter is/SMTP/virt_host_<*> from the profile. If you have only one client and did not create such a parameter in the profile, enter 0.

b) Service data
Enter the client into which the mails received using this virtual mail host are to be directed, as well as the logon data (user, password, language) of the service user that was created for inbound mails (see 2.a).

c) Handler list
Enter CL_SMTP_EXT_SAPCONNECT in the first position.

              As of Release 6. 20, you must activate the SMTP server after you create or change it (Service/Virt.Host --> Activate, or right-click).

4. SAPconnect administration (transaction SCOT)
You have to make the SAPconnect settings separately in each client from which e-mails are to be sent or in which e-mails are to be received.

a) Default domain
The domain of this SAP system client is defined here, for example, crm-prod.company.com. It is used for the following purposes:

o  The SMTP Plug-In logs on to the mail server with the domain as ID.

o  The message ID of outgoing mails is created with this domain.

o  If an SAP user who has not entered an Internet mail address in their user master record sends an e-mail, a sender address is generated from the SAP user name and this domain, for example SMITHJ@crm-prod.company.com.

b) Nodes
There are different types of node in SAPconnect:

o  SMTP nodes (for the SMTP function of the SAP application server)

o  HTTP nodes (for paging or SMS providers using Web services, as of 6.20)

o  RFC nodes (for old RFC-compatible e-mail/fax/paging gateways)

                       There is always a single SMTP node in each client. It is created automatically by the system and cannot be deleted. It is configured as follows (double-click on the node name):

o  Select "Node in use".

o  Under "Mail Host" and "Mail Port", specify the mail server to which outbound mails are to be transferred.

o  Select "Set" for "Internet".

o  Specify address areas of recipient addresses that are to be reached using these nodes (usually "*" if all e-mails are to be sent using SMTP).

o  For "Output Formats for SAP Documents", the following is recommended:
   SAPscript / Smart Forms      PDF
   ABAP List                    HTM
   Business Object / Link        HTM
   RAW Text                      TXT

                       If fax messages are also to be sent using SMTP:

o  Select "Set" for "Fax".

o  Specify address areas of recipient addresses that are to be reached using these nodes (usually "*" if all faxes are to be sent using SMTP).

o  For "Output Formats for SAP Documents", the following is recommended:
   SAPscript / Smart Forms      PDF
   ABAP List                    PDF
   Business Object / Link        TXT
   RAW Text                      TXT

o  For "Conversion into Internet Address", enter the domain of the fax server or fax provider. The local part of the Internet address is generated automatically by the system. The address then has the form "FAX=+recipientnumber@domain".

                       If paging or SMS messages are also to be sent using SMTP:

o  Select "Set" for "Pager(SMS)".

o  Specify address areas of recipient addresses that are to be reached using these nodes (usually "*" if all paging or SMS messages are to be sent using SMTP).

o  For "Conversion into Internet Address", enter the domain of the paging or SMS server or paging or SMS provider. The local part of the Internet address is generated automatically by the system. The address then has the form "SMS=+recipientnumber@domain".

                       Important: To be able to use paging or SMS in the SAP system, names must be defined for the messaging services to be used (e.g. "SMS"). You can do this using transaction SA14.

c) Send job
E-mails that are sent from an SAP application are merely put into a queue. A periodically running background process, the SAPconnect send job, takes the e-mails from the queue and sends them by Internet. This job can be scheduled from SAPconnect administration as follows:

o  Choose "View" --> "Jobs". Check whether a job is already scheduled (displayed as a calendar icon).

o  Choose "Job" --> "Create", and specify a job name.

o  Place the cursor on the "SAP&CONNECTALL" variant, and choose "Schedule Job".

o  Choose "Schedule periodically".

o  Specify a time interval (for example, 10 minutes), and choose "Create".

d) Receiving
With the settings made so far, SAP users can already receive e-mails in their inbox in the Business Workplace (transaction SBWP) at the address entered in the user master record.
If, on receipt of e-mails to a specific address or with specific contents (for example XML documents), you want a program that processes these e-mails to start automatically, you can configure this under "Settings" --> "Inbound Processing".
If, on receipt of e-mails to a specific address or from a specific sender, you want these to be directed automatically to another recipient or a distribution list, you can configure this under "Settings" --> "Inbound Distribution".

5. Settings on the mail server (SAP-external configuration)
To be able to receive mails in the SAP system, you need to set your mail server so that certain mail addresses are forwarded to one or several SAP systems or clients. For this purpose, you need to define routing rules that assign a mail host and/or port to address areas (generic address parts, usually the domain), for example:
      *@crm-prod.company.com  -->  SAPWASHost:25000
      *@crm-test.company.com  -->  SAPWASHost:25001
For more information about the exact setting procedure, see the mail server documentation. Note 546147 describes where the documentation can be found for the Microsoft Exchange 2000 Server, and what to do if your mail server does not allow routing to ports other than port 25.

Regards,

Alihamed.sa

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.