DBACOCKPIT definition and db2cli.ini

[Former Member]

Hello,

After applying SP24 on Solution Manager, we defined the DBACOCKPIT.

Service name of DB2 is required to be defined, so we define SVCENAME but got SQL1337N The SERVICE "sapdb<SID>" was not found error.

We defined it as 5912(real port number), the error had gone.

We are told to check the db2cli.ini whether there are following entries.

[<SID>]

Database=<SID>

Protocol=tcpip

Hostname=<db host>

Servicename=sapdb2<SID>

My questions are;

1. Do we really have to define the db2cli.ini ?

2. Is there any affection if we defined db2cli.ini ?

Thank you and best regards,

Takae Momose

[Frank-Martin]

Hi,

for secondary connections the connection parameters ( dbname, dbhost, dbport, ... ) can be configured in DBACOCKPIT.

The information is persisted in table DBCON.

If your SAP system is running on DB2 LUW it also needs the connection parameters for the primary database connection.

It depends on your database client setup where this information is stored.

(1)

If your system is using the DB2 runtime client, the information is stored in the database directory and the node directory. You can use the DB2 CLP commands "list database directory" and "list node directory" to view them.

(2)

If your system is using the DB2 CLI driver the information is stored in db2cli.ini ( or alteratively db2dsdriver.cfg ). For the new CLI driver this information replaces the database and node directory information.

Note 1091801 and SDN article

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

provide some more info about the new clinet setup.

Regards

Frank