SAP Note 28457 - DBIF_RSQL_INVALID_REQUEST during cluster access

Symptom:

An ABAP runtime error DBIF_RSQL_INVALID_REQUEST occurs within an R/3 application (for example SE16, when copying clients with RSCLXCOP). The last edited table was a logical cluster table (for example, BSEG or BSET). An entry is found in the system log:
Errors ??? on compression/decompression (c2_mk)
In the respective dev file (dev_db for releases prior to 3.0, dev_w for releases >= 3.0) there is a line
db_rclu2: damaged cluster record, TDE(name BSET, len 14, entrycnt 0)

R3trans terminates when accessing a logical cluster table (for example, BSEG), in the log file (trans.log) you find the text:
db_rclu2: damaged cluster record, TDE(name BSET, len 14,entrycnt 0)
[FILE dbrclu2, LINE ....]
cluster: RFBLG key: .......... [FILE dbrclu2, LINE
....]
DBI LOG (BZW): error ??? on compression/decompression using c2_mkdir
[FILE dbrclu2, LINE ....]
2EETW150 sap_dext called with msgnr "900":
2EETW000 Internal error in DB interface
4 ETW000
2EETW000 ---- db call info ----
2EETW000 function: db_setget
2EETW000 fcode: RT_GET
2EETW000 tabname: BSEG
2EETW000 keylen: 0
2EETW000 key:
2EETW000 ok fetches: 0
2EETW000 last entry:
4 ETW000
4 ETW000 ROLLBACK (...).

There are various other errors whose have the same symptom - the error message "Error on compression / decompression". Specific to this problem is that the error occurs when executing the dbrclu2.c function c2_mkdir() and that it appears as ???:
Error ??? on compression/decompression(c2_mk)
or
error ??? on compression/decompression using c2_mkdir
A further important indication is the specification
db_rclu2: damaged cluster record, TDE(name .., len 14, entrycnt 0)
in dev file or in the R3trans log file.

In contrast to other decompression errors, the data is correct in the database, the error is in the cluster interface. Also, the error is not destructive!

Cause and prerequisites

The record to be read (for example, BSEG-) was written to one update level but in the meantime, a newer release was installed and the number of fields in the table (BSEG) has been increased.
Logical cluster tables have the advantage that appending new fields takes place without problems, no immediate conversion is executed. The conversion is carried out 'on-the-fly' during the first access to physical cluster records which contain old logical records.
Up to and including Release 3.0A, this conversion (within the cluster interface) contains an error which causes the above error in certain cases.

Solution
Corrected in Release 3.0B. If necessary, a patch can be created (R3trans and disp+work must then be exchanged).

For releasse 30A, dw.CAR (contains disp+work and rsyn.bin) and r3trans.Z are available on sapserv3 and sapserv4 in the patch directories
~ftp/permanent/patch/30A/.
See note 19466 about transferring patches.

Additional key words

R3trans, SE16, SE17, clusters, BSEG, BSET, DBIF_RSQL_INVALIDREQUEST