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:
At the server end you just get:
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?
The question has been closed for the following reason "The question is answered, right answer was accepted" by Justin Willey 27 Mar '11, 16:02
Fixed in 10.0.1.4116 Many thanks to everyone involved in identifying and sorting the problem.
answered 15 Sep '10, 13:23
A couple of quick tests (using comp=yes;pbuf=150k;prows=50, selecting 5000 rows of ~5000 bytes each) worked properly for me. I would recommend that you open an issue with tech support. If you give them a repro, they should be able to help diagnose the problem.
answered 16 Dec '09, 20:49