I am reliably getting this error: Failed to decompress a compressed packet when both COMP=YES and values for PBUF & PROWS are specified in a connection string.

It seems to depend on the relative values of PROWS & PBUF used, and the size of the result set. It seems that once PBUF is more than approx 100k, any value of PROWS more than about 40 will cause the error, with a decent size result set (1000 rows+). There is no problem with any combination of PBUF and PROWS if COMP=NO.

The behaviour is the same on the latest ebf of 9.0.2 and 10.0.1.3680 (server), 10.0.1.3931 (client). I can't find any refrence to a similar problem in the 10.0.1 fix list.

An example of the error from the client log:

18:15:01 [   22] Failed to decompress a compressed packet
18:15:01 [   22] Received bad packet (type: 24, received length: 1062, header length: 1062), disconnecting
18:15:01 [   22] Connection terminated abnormally; error code 100001
18:15:01 [   22] Communication function i_cs_HandleSQLPresError code 5
18:15:01 [   22] Communication function StrmGetInd code 2
18:15:01 [   22] Client disconnected

At the server end you just get:

Connection terminated abnormally

I've found this while testing wide area performance, for which both prefetching and compression are clearly important. I wonder if anyone else has seen something similar?