isaac_cm Posted September 6, 2007 Share Posted September 6, 2007 Hello, I try to store big html files that contains images in mysql database but after while I get this message "Got error 139 from storage engine" whenever I try to store images I know it something related to row length , I increased it but no result , I tried to change field type from longtext to longblob also I did not get any thing ENGINE=InnoDB DEFAULT CHARSET=utf8 AVG_ROW_LENGTH=200856 ROW_FORMAT=DYNAMIC COMMENT='InnoDB free: 9216 kB'; please advice thanks Quote Link to comment Share on other sites More sharing options...
cmgmyr Posted September 6, 2007 Share Posted September 6, 2007 You have to call your host ASAP. I got this same error a while ago on one of my servers. It happened to be the MySQL log getting too big and filling up a directory (set to 2GB), they had to move the log to a bigger directory and delete the old log. ...The error pretty much means you loaded up your hard drive or something on your hard drive. Quote Link to comment Share on other sites More sharing options...
isaac_cm Posted September 6, 2007 Author Share Posted September 6, 2007 no I store only about 15 page of text contains about medium 5 images and I get this error on my localhost I use IIS and MYSQL server 5.0.21, any idea ? Thanks Quote Link to comment Share on other sites More sharing options...
fenway Posted September 7, 2007 Share Posted September 7, 2007 Show us the table definition. Quote Link to comment Share on other sites More sharing options...
isaac_cm Posted September 7, 2007 Author Share Posted September 7, 2007 My table it was innodb I contact mysql and it is really a bug or a limitation with innodb engine something with the row size any way they said the only solution is to use MYISAM and after I convert my table to this engine I did not get the error , luckily this table dont need foreign keys Thanks Quote Link to comment Share on other sites More sharing options...
fenway Posted September 8, 2007 Share Posted September 8, 2007 My table it was innodb I contact mysql and it is really a bug or a limitation with innodb engine something with the row size any way they said the only solution is to use MYISAM and after I convert my table to this engine I did not get the error , luckily this table dont need foreign keys Thanks So you've "solved" this problem? Quote Link to comment Share on other sites More sharing options...
isaac_cm Posted September 9, 2007 Author Share Posted September 9, 2007 yes finally, I mentioned the solution here so any one face this problem can do what I did , I hope InnoDB don't have this limitation in the future. thanks Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.