Is there a quick way to tell?

 


From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Maurice James Ny
Sent: Wednesday, February 07, 2007 8:06 PM
To: 'User questions and discussions about OTRS.org'
Subject: RE: Database pruning (was: RE: [otrs] Ticket history table full error)

 

How many tickets do you have?

 


From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Jason B. Loven
Sent: Wednesday, February 07, 2007 11:19 AM
To: User questions and discussions about OTRS.org
Subject: Database pruning (was: RE: [otrs] Ticket history table full error)

 

OK… I bit the bullet and did the max_rows change and all seems well.

 

Next question: Is there a way to prune the database or to archive history out of the database to get things down in size? My history file is currently at 4GB after about a year of usage and I’d like to prune that down or at least identify what is taking up the bulk of the data. That seems pretty large considering our low volume of tickets.

 

-Jason

 


From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Jason B. Loven
Sent: Wednesday, February 07, 2007 7:51 AM
To: User questions and discussions about OTRS.org
Subject: [otrs] Ticket history table full error

 

Anyone know how to fix this? We’re running 2.0.4 and I saw this showing up in the cron logs. I’ve disabled cron for now but obviously that’s bad because now we’re having to manually handle the incoming mail queue for our support.

 

Here’s the error…

 

DBD::mysql::db do failed: The table 'ticket_history' is full at /opt/otrs/Kernel/System/DB.pm line 376, <PRODUCT> line 4.

ERROR: OTRS-GenericAgent-10 Perl: 5.8.5 OS: linux Time: Tue Feb  6 21:32:31 2007

 

Here’s the table status…

 

 

mysql> show table status like 'ticket_history'\G

*************************** 1. row ***************************

           Name: ticket_history

         Engine: MyISAM

        Version: 9

     Row_format: Dynamic

           Rows: 40363419

 Avg_row_length: 106

    Data_length: 4294727600

Max_data_length: 4294967295

   Index_length: 3986779136

      Data_free: 0

 Auto_increment: 40382698

    Create_time: 2006-10-13 08:44:28

    Update_time: 2007-02-06 22:23:25

     Check_time: 2007-02-06 23:48:54

      Collation: latin1_swedish_ci

       Checksum: NULL

 Create_options:

        Comment:

1 row in set (0.09 sec)

 

 

From what I’m seeing I need to change the max_rows and avg_row_length parameters for the table but I’d like to hear some opinions before I do that in case it’s a bad thing for otrs.

 

Thank you,
Jason Loven
Manager - Technical Services Department

Computer Associates, Inc.
36 Thurber Blvd, Smithfield RI 02917
Phone: (401)232-2600, Fax: (401)232-7778
Email:
jloven@cainetserv.com
Web: http://www.cainetserv.com/