> > Yes. I've seen this dicussion numerous times in the past and know it > > to be an issue with following the upgrade path. Perhaps I didn't > > follow the previous conversation paths correctly. > > That would be plausible except: > > a. my RT 3.8.1 install is a brand spanking new install. > > b. my RT 3.4.2 install is untouched. > > c. the only thing 'upgraded' about my RT environment is the database > tables.
Yes. This says pretty clearly that you didn't run the tool described in the 'UPGRADING' file in the RT 3.8.1 distribution. > Attachments are corrupted if mail is routed to the 3.8.1 install. They > are not when routed to the 3.4.2 install. > > Matt > > I followed the upgrade documents to the letter in my test environment > with a snapshot of the database. The ALTER tables process might work > well for folks with a smaller data set but with 18GB of data, it takes > four hours to run on a E5310 Xeon with dedicated disks. That is far > too long to have our systems out of production. > > Changing the character set of the database tables from latin to UTF > can be done far more quickly and with less risk by dumping the > database to disk, using sed to alter the dump file, and then > importing. That process is hours faster. > _______________________________________________ > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > Community help: http://wiki.bestpractical.com > Commercial support: [EMAIL PROTECTED] > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com > -- _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com