SQL Error in the modify statement

[Former Member]

Hi All,

We are facing an SQL error while uploading an archive file. The error is

caused while executing a modify statement which leads to a dump. The

text given in the SM21 logs is

'Database error -1 with SEL access to table SMMW_MCD_DMY_AVE'

The dump generated in ST22 says DBIF_RSQL_SQL_ERROR

Database error text........: "[Microsoft][SQL Native Client]Session Provider:

Connection has been closed by peer [xFFFFFFFF]. "

Any pointers to figure out how to resolve this could be really helpful.

Regards,

Liji

[Former Member]

Hi,

This sounds like internal message 0000062076 2010

which I'm currently working on.

If it is this BUZ-upload problem: ask your system responsible to set the instance profile parameter

dbs/mss/packet_size=8192

After the R3-system is restarted, the transaction should work.

The problem was caused by an UPSERT-command writing a 170 MB BLOB.

UPSERT means: all values for the row are provided. Try first an UPDATE, if this fails with NOT FOUND insert.

This UPDATE, IF NOT FOUND INSERT is send as one batch to the database server.

For SQL Server 9.00, a batch may only

consist of 64K network packets. The default network packet size is 4K. 4K * 64KB == 256 MB.

The 170 MB BLOB is sent twice, so we don't fit in the 64K packets.

This breaks the connection and you get on client side the"Connection has been closed by peer".

On server side you see (SQL Server error log) "A fatal error occurred while reading the input stream from the network. The session will be terminated."

If you want to increase the network packet size used by your db connections in the SAP work processes, you can use the profile parameter

dbs/mss/packet_size.

Maximal setting is 32767. In your case I would recommend 8192.

Best regards,

Guenther

Edited by: Guenther Drach on Jan 7, 2010 3:13 PM

Edited by: Guenther Drach on Jan 7, 2010 3:15 PM