Results 1 to 5 of 5

Thread: Error 127

  1. #1
    Join Date
    May 2006
    Location
    New York City
    Posts
    77
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default Error 127

    Recently, one of my database queries started failing and giving me this error message: "Got error 127 from storage engine". I've tried looking it up but I can't find where this error is documented and I don't know how to fix it. Does anyone here have any insights? Thanks so much.

  2. #2
    Join Date
    May 2006
    Location
    New York City
    Posts
    77
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    so . . . nobody, huh?

  3. #3
    Join Date
    Jun 2005
    Location
    英国
    Posts
    11,876
    Thanks
    1
    Thanked 180 Times in 172 Posts
    Blog Entries
    2

    Default

    It's a bit of a mystery, but try REPAIR TABLE table_name;
    Twey | I understand English | 日本語が分かります | mi jimpe fi le jbobau | mi esperanton komprenas | je comprends français | entiendo español | tôi ít hiểu tiếng Việt | ich verstehe ein bisschen Deutsch | beware XHTML | common coding mistakes | tutorials | various stuff | argh PHP!

  4. #4
    Join Date
    Sep 2005
    Location
    India
    Posts
    1,627
    Thanks
    6
    Thanked 107 Times in 107 Posts

    Default

    This kind of problem reported frequently by the developers especially on tables whose size is very big. A quick look seems to be the size of the data file is the main culprit.

    I found one interesting message from the mySQL forum which points the cause and the remedy. Check the following link.

    http://forums.mysql.com/read.php?88,...7624#msg-77624

    Check the following link for getting more details about this error (the page was in chinese and traslated it using google. The page is already been mentioned in the above message)

    http://translate.google.com/translat...hl=en&ie=UTF-8


    Quote Originally Posted by Twey View Post
    It's a bit of a mystery, but try REPAIR TABLE table_name;
    Some users reported that the REPAIR TABLE cropped their data.

  5. #5
    Join Date
    May 2006
    Location
    New York City
    Posts
    77
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    As it turns out, the table was indeed too big (it was the biggest table in the database with a whopping 16,000 or so rows) and some of the older rows were obsolete so i deleted them. It's working now. I just have to make sure I delete rows out of my database when i don't need them there anymore.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •