DBIF_RSQL_SQL_ERROR | expired.#[121] Communication link failure

[Former Member]

Hi All,

On our BW production system, we are receiving DBIF_RSQL_SQL_ERROR dumps. Below you can find the information from dump and trace.

The DB is sitting on other host and we have CI + DI(Both have separate host).

There are no notes matching the below error text. Initial investigation looks to be a communication problem between the hosts of CI and DB. But there should be some notes which can help us on these error. If there are any can you please let us know.

From ST22:

Short text

    SQL error in the database when accessing a table.

How to correct the error

    Database error text........: "[121] TCP Provider: The semaphore timeout period

     has expired.#[121] Communication link failure"

    Internal call code.........: "[RSQL/INSR//BIC/B0000420000 ]"

    Please check the entries in the system log (Transaction SM21).

From trace:

C Mon Jul 15 00:34:39 2013

C  NexecParamStmt: line 17270. hr: 0x80004005 Communication link failure

C  sloledb.cpp [NexecParamStmt,line 17270]: Error/Message: (err 121, sev 0), Communication link failure

C  Procname: [##Y4SWLWR019bwp00000035840000158424070036]

C  sloledb.cpp [NexecParamStmt,line 17270]: Error/Message: (err 121, sev 0), TCP Provider: The semaphore timeout period has expired.

C  Procname: [##Y4SWLWR019bwp00000035840000158424070036]

B  ***LOG BY4=> sql error 121    performing INS on table /BIC/B0000 [dbtran#15 @ 7598] [dbtran  7598 ]

B  ***LOG BY0=> [121] TCP Provider: The semaphore timeout period has expired.

[121] Communication link failure [dbtran#15 @ 7598] [dbtran  7598 ]

B  dbtran ERROR LOG (hdl_dbsl_error): DbSl 'INS'

B   RSLT: {dbsl=99, tran=1}

B   FHDR: {tab='/BIC/B0000420000', fcode=130, mode=1, bpb=0, dbcnt=0, crsr=0,

B          hold=0, keep=1, xfer=1, pkg=0, upto=0, init:b=0,

B          init:p=0000000000000000, init:#=0, wa:p=0000000000000000, wa:#=196}

B  dbtran ERROR LOG (hdl_dbsl_error): DbSl 'INS'

B   STMT: {stmt:#=0, bndfld:#=0, prop=0x5, distinct=0, select*=1,

B          fld:#=28, alias:p=0000000000000000, fupd:#=0, tab:#=0, where:#=0,

Regards,

Ravi

[former_member206552]

Hi Ravi,

Are you still having the problem ? if so please update the thread if the problem is solved please paste the solution and close the thread

Best Regards

Marius

[Former Member]

Hi All,

No still on 1 of the system we are observing the dumps.
Sure will update you all on solution.

Regards,

Ravi

[former_member184473]

Hello Ravi,

Do you have the latest components?

Run the following statements (remember to adjust <SID> and <sid>):

SELECT DLLNAME, HOSTNAME, FIRSTDATE, LASTDATE, DLLVERSION, DLLPATH

FROM <SID>.<sid>.MSSDWDLLS

WHERE DLLNAME like 'sql%' or DLLNAME like 'dbmssslib.dll'

GROUP BY DLLNAME, HOSTNAME, DLLVERSION, FIRSTDATE, LASTDATE, DLLPATH

SELECT @@version

Regards,

Eduardo

[Former Member]

Hi Ravi,

Were you able to find a solution for this issue?

Can you update us with any findings you had on this issue

Sunil

[former_member212248]

We are on Windows Server & SQL Server 2008 R2, and experiencing this same error (SQL Error 121 -- where our BW disconnects from SQL Server) ... I see no errors on the SQL Server host (checked Windows and SQL logs), but SAP does report disconnected processes and errors.  Did you ever find a solution to this errors?

[Rob3]

Hi Ravi,

You can validate your network configuration by moving one of the components (CI or DB) and running both on the same host. If everything works correctly, you can try troubleshooting the network connection.

Things to look for include firewall settings, network protocol settings (are the cards running at the same speeds?) on both hosts. And you can validate if both hosts have the same versions of OS patches, etc.

Thanks,

Rob

[Former Member]

Hi,

Check this SAP note :495297

It can be a network error also.

[Former Member]

HI,

What does R3trans -d and R3trans -x show you in the logs?

The error you list mentions a /BIC/* cube/table for BW it seems.

sql error 121    performing INS on table /BIC/B0000 [dbtran#15 @ 7598] [dbtran  7598 ]

Review notes:

1478133 - MS SQL Server: How to analyze connection problems to database server

98678 - SQL Server Connection Issues

208632 - TCP/IP network protocol for MSSQL

Kind Regards,

Johan

[former_member184473]

Hello Ravi,

Is your system updated (DB, client, kernel and DBSL)?

Check note 392892 and check parameters "set working set size", "priority boost" and "network packet size" and disable feature "TCP Chimney Offload".

Regards,

Eduardo Rezende