connect failed -- CLI2: BADBUFRQ(302): Invalid buffer size

Database
Enthusiast

connect failed -- CLI2: BADBUFRQ(302): Invalid buffer size

Hi,
I have a problem with the buffer size.
I need to run queries with more of 40.000 characters and It return an error message: initiate request failed -- CLI2: BADBUFRQ(302): Invalid buffer size
with req_buf_len = 1024

If I change the size of variable 'req_buf_len = 65536' It return the next error: connect failed -- CLI2: BADBUFRQ(302): Invalid buffer size

Somebody knows how can I resolve this problem??

Thanks and regards.
2 REPLIES
Teradata Employee

Re: connect failed -- CLI2: BADBUFRQ(302): Invalid buffer size

You can send SQL text larger than the request buffer size. And this error does not say the request is too large for the buffer, it says the specified buffer size is not valid. Are you seeing this error in your own CLIv2 application or some Teradata utility?

The largest value you can specify for req_buf_len is 32767 (with maximum_parcel=O, the default) or 65535 (with maximum_parcel=H). The largest value that can actually be used is a bit less, e.g. 65477, due to system overhead. Also, if you are using the extended interface for LOB data, limits are much higher.

Enthusiast

Re: connect failed -- CLI2: BADBUFRQ(302): Invalid buffer size

Thank you very much Fred,

We add the variable maximum_parcel = H, the buffer size = 65535 and we can execute large queries with these changes.

Thanks and regards.