cancel
Showing results for 
Search instead for 
Did you mean: 

SQL error not occurs again after refresh

0 Kudos

Hello,

I have one SQL statement like following:

       SELECT DISTINCT

         a~objkey AS guid_parent

         b~objkey AS guid_child

       INTO CORRESPONDING FIELDS OF TABLE et_parent_object

       FROM srrelroles AS a

       INNER JOIN crmd_binrel AS r ON a~roleid = r~role_a

       INNER JOIN srrelroles  AS b ON b~roleid = r~role_b

       WHERE a~objkey IS NOT NULL

         AND b~objkey IS NOT NULL

         AND a~objkey IN lt_parents_range.

The parameter lt_parents_range has more than 1000 lines.

First time, when I run this SQL, dump occurs. Like following:

Category                   Installation Errors

Runtime Errors          DBIF_RSQL_SQL_ERROR

Except.                    CX_SY_OPEN_SQL_DB

Date and Time          14.01.2014 10:17:29

Short text                  SQL error "-1114" when accessing table "SRRELROLES".

What happened?       Error Text of the Database: "POS(1) Communication packet too small"

But after refresh UI and execute this SQL again, the dump not happens again.

After one day, everything looks appear again.

Is there anybody knows why?

My environment:

OS: Linux  x86_64

DB: MaxDB 7.8.02.033

NW: 720

Thanks & BR,

Tony

Accepted Solutions (0)

Answers (2)

Answers (2)

Sriram2009
Active Contributor
0 Kudos

Hi liu

Kindly refer the SAP Note   140739 - SQL error -1114 COMMUNICATION PACKET TOO SMALL

Regards

SS

0 Kudos

Hi Sriram,

Thanks for your reply.

Tony

Former Member
0 Kudos

Hi Tony,

-1114: Communication packet too small Locate this document in the navigation structure

Explanation

The SQL statement is so long that not all pieces of information to be exchanged between client and server can be stored in the communication packet provided for this purpose

User Response

Simplify the SQL statement or split it into several SQL statements. If this is not possible, check whether the database parameter PACKET_SIZE can be increased. This parameter indicates the size of the communication packet.

So if you can split it into smaller statements/selects of data. Or else increase parameter PACKET_SIZE.

http://maxdb.sap.com/training/internals_7.6/kernel_parameters_EN_76.pdf

Changing Parameters - MaxDB - SCN Wiki

As for daily recurrence I would guess some kind of cache built up that is cleared by your refreshing action.

Kind Regards,

Johan

0 Kudos

Hi Johan,

Thanks for your reply.

Here is another question:

After this dump occurs, and refresh again, everything looks good. The dump will disappear.

Firstly I guess this is because cache. But after checked those two table, I find that all of those two table are "Buffering not allowed".

Do you know why?

Thanks & BR,

Tony