Hi Steve,

 

Don't know if there is a way to fix that table, but you might not be too concerned. This table holds attachments that customers and agents attach to ticket articles. You might consider storing that in the filesystem instead of the database ("there's a sysconf setting for that" should be the new OTRS motto...) and just discard the contents of that table in the migration. Yes, tickets will lose attachments, but maybe everybody can live with that.

 

 

Lars

 

From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Steve Clark
Sent: Friday, August 19, 2011 8:54 PM
To: User questions and discussions about OTRS.
Subject: Re: [otrs] DATA Corruption

 

On 08/19/2011 02:37 PM, Mik Rose wrote:

Its a postgresdb.  Is there a similar method for postgres?


Mik Rose | Director, IT - Support Services | 
PowerSoft Development Corp

1 (250) 642-0295 x23   http://www.power-soft.com   Live Support

 

 

This e-mail may be privileged and/or confidential, and the sender does not waive

any related rights and obligations. Any distribution, use or copying of this e-mail or the information

it contains by other than an intended recipient is unauthorized.

If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately.

 

On 2011-08-19, at 11:36 AM, Carlos Andrés Gallego Arboleda wrote:



if you dont stop the mysql during the data copy, maybe the DB is corrupted.

 

use this command.

 

mysqlcheck --repair -p otrs 

 

Regards.

 

2011/8/19 Mik Rose <mrose@power-soft.com>

Happy Friday people!

 

I was wondering if anyone had any suggestions on how to resolve this issue...  I am moving otrs to another server and during the backup process I am running into this error

pg_dump: dumping contents of table article_attachment
 
 
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR:  unexpected chunk number 7 (expected 6) for toast value 77281 in pg_toast_57366
 
 
pg_dump: The command was: COPY public.article_attachment (id, article_id, filename, content_size, content_type, content, create_time, create_by, change_time, change_by, content_id, content_alternative) TO stdout;
 
 
pg_dump: *** aborted because of error

 

 

I have tried a vacuum and reindex with no successes.

 

You would be better off posting this to the postgresql-users list.

--
Stephen Clark
NetWolves
Sr. Software Engineer III
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.clark@netwolves.com
http://www.netwolves.com