Packet Too Large - Unable to Persist

garyg

Can someone tell me what's happening here?

Process:

Step 1 of the Process that allows a User to "PICK FROM" a Subset (BO called Subset, which let's me tag related records to a certain subset to easily pull up a subset of records at a later date).
Step 2 of the Process FINDS records where Subset.SubsetName matches the name of the subset picked in Step 1.
Step 3 of the Process is set to Display a single page report for each returned record using the records found in step 2 above. There are only 68 records returned, but I am getting the following message:

"Unable to persist process context Packet for query is too large (19160036 > 16776192). You can change this value on the server by setting the max_allowed_packet' variable."

I am using MySQL 5.1.

cchappell

I believe I ran into a problem like this last year. My problem was do to storing documents in the database with a file size that was larger than max_allowed_packet entry in mysql.

I would google max_allowed_packet mysql.

I believe you probably need to change mysql.ini entry max_allowed_packet=32M or something like that. 32M being 32 megabytes.

It is probably set at 16M (16 megabytes).

I'm no expert but think this might get you going the right direction.....I tried searching forum....I know this was discussed somewhere but didn't have much luck.

Chris

cchappell

I further investigated my config. In case you want to try.

My config file (my.ini). under the section [mysqld]
I have an entry:

max_allowed_packet = 32M

garyg

Not sure this worked. Now I get a different message.

Unable to persist process context Data truncation: Data too long for column 'LONGDATA' at row 2

aware_support

You have data that is too large for MySQL.

garyg

So will it work under the regular MS SQL Server?

aware_support

What size is the data you are trying to write to the database?

garyg

Not sure. It's just a relatively simple report from the 68 records returned in context. There are some very small thumbnail photos on each record (JPEG), and one very long field for comments (that can be 1500 characters), but other than that, it's just text fields.

garyg

should i send a bsv?

garyg

THIS IS FROM THE LOG, BUT I DON'T KNOW WHAT TO DO ON THE REPORT DESIGN TO FIX IT:

2010-04-07 05:15:53,544 Reply#1 -19 Resuming process 1

Warning : Element bottom reaches outside band area : y=0 height=130 band-height=128

Warning : Element bottom reaches outside band area : y=0 height=131 band-height=128

Warning : Element bottom reaches outside band area : y=50 height=1 band-height=50

2010-04-07 05:16:02,481 ERROR Reply#1 -18 Resumed process SubsetReport has failed. Message is Unable to persist process context Data truncation: Data too long for column 'LONGDATA' at row 2 Sending failure reply

aware_support

The log is fine. What are the rules of your process?

garyg

The rules of the process are at the top of this post. But I don't think the log is fine. When I remove the photo field from my report, save it, then try running this process in operation mode, it works fine. But when I try to insert the photo field back in (which is to display a small JPG...50k or so...in line for each record of the report), the system generates this LONGDATA error. Stumped. I was thinking that perhaps the photo sizes were not fitting into the report photo size, but it appears that they should automatically scale based on settings.

aware_support

It looks like your report gets so huge and your 50K photo is copied so many times that the resulting record can not be saved in the MySQL MediumBlob field. Try reducing the report, removing the photo or use SQL Server, which has larger capacity for blob fields.

garyg

I will try it. Switching to MS SQL Server anyway. Thanks!

garyg

would using "in batches of" do anything?

aware_support

You need to pay for the SQL Server option if you haven't done already...