Hi Vlad,

The procedure does not perform DDL. Our test is simply to run the
procedure over a know date range that always fails. We cannot seem to
figure out where it fails at! Everytime we split the procedure into
multiple procedures it won't fail. Only when the code is all run at
once will it fail with the message length error. The error does NOT
occur on FB 2.0.3 CS on linux. But it does under FB 1.5.3 CS, 1.5.4 CS,
and 1.5.5 RC1 CS on linux.

We tried recompiling all stored procedures and all triggers and then
rebooted the whole server to get rid of any cache problems. The
database was set to be online. The procedure still fails with the same
message length error.

Any more ideas from anyone?

-steve

Vlad Khorsun wrote:

>
> > Ok, thanks! We are running the test again. It usually takes about 3-5
> > hours before it fails.
>
> Does this test perform DDL ? Does it fails everytime at the same step ?
>
> Regards,
> Vlad
>
>