Db2 runtime client or CLI Driver

[Former Member]

Dear experts,

I'm making a checkup of all systems.

I want to check in each system if it is using runtime client or CLI driver and the version it is using. For that I'm using R3trans and then I check the trans.log file.

The problem is that in Java systems, R3trans doesn't work.

How can I make this check in Java stack systems?

regards,

Filipe Vasconcelos

[Former Member · Accepted solution]

Well, I got a very nice document that helped me in my problem.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0e7a584-332b-2b10-0f98-ecbb74050...

[Former Member · Accepted solution]

HI Filipe,

I already metion path for CLI driver. may be below link didint work i think..Thanks for ur document.

Regards

Ashok

[former_member188883]

Hi Fillipe,

For Java based systems you may run configtool to check connection with database.

Regards,

Deepak Kori

[Former Member]

I've run configtool but I can't find any database connection that tells me if it using CLI driver or runtime client.
By the way I also want to know the CLI driver version used.

[Former Member]

Hi Filipe,

DB2 CLI Driver : Now DB2 CLI driver nothing Thin client in DB2.

/sapmnt/SID/global/db6/LINUXX86_64/db6_clidriver in this folder u can find the version of clidriver .

may be this well helpful try to excute this :./chk_thin_client-p inf

Regards

Ashok

[Former Member]

Dear Ashok,

I just have this directory /sapmnt/PEB/global/db6/jdbc

cslpebbp01:pebadm 64> ls -altr

total 16

-rw-r--r--  1 pebadm sapsys  162 Feb 11 08:40 db2cli.ini

drwxr-xr-x  3 pebadm sapsys 4096 Feb 11 08:40 .

drwxr-xr-x 15 pebadm sapsys 4096 Feb 11 09:18 ..

drwxr-xr-x  2 pebadm sapsys 4096 Mar 13 12:23 jdbc

And I don't have any chk_thin_client-p inf

thanks.

regards,

FV

[former_member188883]

Hi Filipe,

As of DB2 LUW V9, remote clients do not need to have the runtime client software installed. Instead, you can install the CLI driver client (Thin Client), which consists of the CLI library, some configuration files, and a small set of executables that assist in problem tracking.

As of SAP NetWeaver 7.0 SP13 and higher, all SAP systems are installed with this setup by default.

To connect to the database, an SAP application server requires the following components:

■ The DB2 CLI libraries for the ABAP stack

■ The JDBC driver for the Java stack

■ The database name and connection port for the primary database

These components add up to the client connectivity. Depending on the setup of your SAP system,

either the old DB2 client connectivity (DB2 Runtime Client) or the new one (DB2 CLI and JDBC driver) might be in use.

DB2 runtime client is mandatory for SAP releases lower than SAP Basis 7.0 and for all SAP systems still running on DB2 UDB Version 8.

Additionally you may refer link http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f03d5fb8-b619-2b10-c383-c6d568728...

To understand database architecture and more information on db2 client connection and configuration.

On SAP application servers both a runtime client and a CLI driver client may exist at the same time. As a default the SAP user environment is not prepared to execute DB2 programs from the CLI driver directory. Therefore, if you need to use these executables, for example to run a DB2 trace, you first need to set up the user environment properly.Refer SAP Note 1486120 - DB6: Data Collection in a CLI driver environment to understand on environment configuration.

Hope this helps.

Regards,

Deepak Kori

[former_member188883]

Hi Filipe,

Hope you have gone through the details shared above in my response and might got a hint how db2 connection works in JAVA based systems.

Regards,

Deepak Kori