SQL30081N Communication error

[Former Member]

Yesterday we found "SQL30081N Communication error has been detected" error on some application logs.

This is a central instance.

We already check DB2COMM and SVCNAME and it points to correct values (TCPIP and sapdb2<SID>).

[former_member289242 · Accepted solution]

Hi Rachit,

This issue is known at SAP side and documented in note 1364372. Kindly update the DBSL and validate the issue.

look for lib_dbsl on

    http://service.sap.com/swdc

       Support Packages and Patches

         Search for Support Packages and Patches

If the problem happens again and DBSL cannot be updated, then you could use the following SAP profile parameter to influence the length of the period:

dbs/db6/dbsl_login_timeout_secondary=60

Please ignore the warning that this parameter is unknown.

If that doesn't work then get back to us with db2diag.log.

Best Regards,
Gunjan

[Frank-Martin · Accepted solution]

db2diag.log wont help. A snippet from the dev_w* files including this error may help.

Regards

                Frank

[former_member188883]

Hi Rachit,

Please share detailed logs from db2diag.log file

Also under which circumstances you receive this error message.

Regards,

Deepak Kori

[former_member186228]

Hi Rachit,

Can you provide complete error message.

regards,

Jithin M