On Sun, Apr 12, 2009 at 4:48 PM, Asif Iqbal <[email protected]> wrote:
> On Sun, Apr 12, 2009 at 4:44 PM, Joop van de Wege <[email protected] > > wrote: > >> Asif Iqbal wrote: >> >>> How do I fix it? >>> >>> Have a look at the mysql.sql file in your setup folder of RT or >>> download rt and recreate the table. >>> >>> >>> I do not see any mysql.sql file in the src dir of rt 3.4.5 >>> ./etc/schema.mysql >>> >> Maybe I meant this file. Did you look at the sql file to determine if they >> would be useful?? >> > > I looked at it now. So I can just delete the sessions.MYI, sessions.MYD and > frm files and recreate the sessions table as in the schema? I am assuming it > wont break the RT > mysqlcheck says this btw, [..all OK..] rt3.Users OK rt3.sessions warning : Table is marked as crashed and last repair failed warning : 9 clients are using or haven't closed the table properly warning : Size of indexfile is: 12666880 Should be: 1024 error : Found too long record at 82812800 error : Corrupt > > >> >> Regards, >> >> Joop >> > > > > > -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
_______________________________________________ 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
