sapnote_0001730855_r3trans_hang.pdf

3
8/14/2019 sapnote_0001730855_R3trans_hang.pdf http://slidepdf.com/reader/full/sapnote0001730855r3transhangpdf 1/3 01.07.2013 Page 1 of 3  SAP Note 1730855 - DB6: Establishing a connection to DB2 is slow, or hanging  Note Language: English Version: 3 Validity: Valid Since 21.06.2013 Summary Symptom You observe the following problems. o The startup procedure of the SAP system, or a single application server, is slow, or hanging. o The following command is slow, or hanging.  R3trans -x Other terms db6 db2luw conlic.bin Reason and Prerequisites This symptom can be caused by several conditions. 1. You are connecting to the database with the "Thin Client" (CLI client). The CLI client is installed on an NFS-mounted file system. One of the daemons related to NFS respond with delay, or do not respond. To identify the problem, use a system tracing utility. For example, run the following command.  truss -d -o r3trans_truss .txt R3trans -x # AIX, Solaris  strace -tt -o r3trans_truss.txt R3trans -x # Linux  tusc -D -o r3trans_trus s.txt R3trans -x # HP-UX In the output file, you will see which file was being accessed when the long delay, or hang occurred. The relevant system calls are fcntl(), or fstatx(). A problem that has been observed several times is that the NFS lock daemon is not working properly. In particular, the following cases have been observed. a) A file lock for a file "conlic.bin" has been requested. This happens with DB2 levels as of DB2 LUW 9.7 FP4 and DB2 LUW 10.1. The file has been invented to fix a problem in DB2 for zOS via APAR IC72892. The location of the file is  [location of CLI driver]/cfgca che/conlic.b in b) A file lock for a file "db2dsdriver.cfg" has been requested. The file exists, but is not used by SAP for DB2 levels up to, and including DB2 LUW 9.7. The location of the file is the following.  [location of CLI driver]/cfg/d b2dsdriver.c fg 2. Current versions of the SAP DbSl for DB6 use an additional Connection attribute when connecting to the database. On the client side, you are running DB2 LUW 9.7 FP3, or higher. A DbSl trace as per SAP note # 31707 shows the delay in the following lines.  & 0| | |DbSlConnectDB6 |SQLGetConnectAttr

Upload: rubenw

Post on 04-Jun-2018

222 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: sapnote_0001730855_R3trans_hang.pdf

8/14/2019 sapnote_0001730855_R3trans_hang.pdf

http://slidepdf.com/reader/full/sapnote0001730855r3transhangpdf 1/3

01.07.2013 Page 1 of 3

  SAP Note 1730855 - DB6: Establishing a connection to DB2is slow, or hanging

 Note Language: English Version: 3 Validity: Valid Since 21.06.2013

Summary

Symptom 

You observe the following problems.

o The startup procedure of the SAP system, or a single application

server, is slow, or hanging.

o The following command is slow, or hanging.

  R3trans -x

Other terms

db6 db2luw conlic.bin

Reason and Prerequisites

This symptom can be caused by several conditions.

1. You are connecting to the database with the "Thin Client" (CLI

client). The CLI client is installed on an NFS-mounted file system.

One of the daemons related to NFS respond with delay, or do not

respond.

To identify the problem, use a system tracing utility. For example,

run the following command.

  truss -d -o r3trans_truss.txt R3trans -x # AIX, Solaris

  strace -tt -o r3trans_truss.txt R3trans -x # Linux  tusc -D -o r3trans_truss.txt R3trans -x # HP-UX

In the output file, you will see which file was being accessed when

the long delay, or hang occurred. The relevant system calls are

fcntl(), or fstatx().

A problem that has been observed several times is that the NFS lock

daemon is not working properly. In particular, the following cases

have been observed.

a) A file lock for a file "conlic.bin" has been requested. This

happens with DB2 levels as of DB2 LUW 9.7 FP4 and DB2 LUW 10.1. The

file has been invented to fix a problem in DB2 for zOS via APAR

IC72892. The location of the file is

  [location of CLI driver]/cfgcache/conlic.bin

b) A file lock for a file "db2dsdriver.cfg" has been requested. The

file exists, but is not used by SAP for DB2 levels up to, and

including DB2 LUW 9.7. The location of the file is the following.

  [location of CLI driver]/cfg/db2dsdriver.cfg

2. Current versions of the SAP DbSl for DB6 use an additional Connection

attribute when connecting to the database.

On the client side, you are running DB2 LUW 9.7 FP3, or higher. A DbSltrace as per SAP note # 31707 shows the delay in the following lines.

  & 0| | |DbSlConnectDB6 |SQLGetConnectAttr

Page 2: sapnote_0001730855_R3trans_hang.pdf

8/14/2019 sapnote_0001730855_R3trans_hang.pdf

http://slidepdf.com/reader/full/sapnote0001730855r3transhangpdf 2/3

01.07.2013 Page 2 of 3

  SAP Note 1730855 - DB6: Establishing a connection to DB2is slow, or hanging

  &+ 0| | | SQL_ATTR_GET_LATEST_MEMBER=''

A system trace with OS tracing tools (truss, strace, tusc) shows the

delay in a network-related system call (like door_call() on Solaris).

Solution

The solution depends on which of the mentioned problems is identified.

1. As the source of the problem is outside DB2, the solution is to find,

and address the NFS problem.

Another solution is to configure the CLI client on local file systems.

Details about the configuration of the CLI client are available on SDN

in the document with title The New DB2 Client Setup in SAPSystems with DB2 for Linux, UNIX, and Windows.

Further options for a solution are based on the individual problem asfollows.

a) On DB2 LUW 9.7, the issue with conlic.bin is addressed in APAR

IC79042, which is available in the CLI driver of DB2 LUW 9.7 FP6. A

possible workaround is to have the CLI driver at a level lower than

FP4.

It will not help to remove the file, as the next connect to DB2

will recreate it.

b) If you move the file db2dsdriver.cfg to a different name, or remove

the file, the problem does not happen any more.

2. The problem seemingly is no DB2 bug, but network-based. However, it

could not be identified yet. The following APARs provide a change in

DB2 that also resolves the problem.

o DB2 LUW 9.7: APAR IC80225 available with FP6

o DB2 LUW 10.1: APAR IC84159 available with FP1

On DB2 LLUW 9.7, a workaround is to stay below DB2 LUW 9.7 FP3 for the

CLI client.

Remarks

o The CLI client must have the same version of DB2 as the DB2 server.

o The CLI client must stay at a Fix Pack level lower, or equal, that

of the DB2 server.

Header Data

Release Status: Released for Customer

Released on: 21.06.2013 09:38:25Master Language: English

Priority: Recommendations/additional info

Page 3: sapnote_0001730855_R3trans_hang.pdf

8/14/2019 sapnote_0001730855_R3trans_hang.pdf

http://slidepdf.com/reader/full/sapnote0001730855r3transhangpdf 3/3

01.07.2013 Page 3 of 3

  SAP Note 1730855 - DB6: Establishing a connection to DB2is slow, or hanging

Category: External error

Primary Component: BC-DB-DB6 DB2 Universal Database for Unix / NT

The Note is release-independent

Related Notes

Number Short Text

101809 DB6: Supported Fix Packs DB2 for Linux, UNIX and Windows

31707 DB6: DBSL trace for performance/error analysis

 Attributes

Attribute Value

Database system DB2 for LINUX, UNIX and

WINDOWS 9.7