Error 1030 Hy000 Got Error 139 From Storage Engine
Contents |
Cluster and HA
Sqlstate Hy000 General Error 1030 Got Error 28 From Storage Engine
SupportTokuMX SupportMongoDB SupportContact SupportPercona Emergency SupportSupport PoliciesSupport TiersRead got error 139 from storage engine innodb MoreConsultingPerformance OptimizationInfrastructure Architecture and DesignHigh AvailabilityUpgrades & MigrationsServer & Database AutomationConsulting PoliciesRead MorePercona innodb row size too large Care Software MySQL Database SoftwarePercona ServerPercona XtraDB ClusterPercona XtraBackupPercona TokuDBMySQL Software DocumentationSoftware RepositoriesRead MoreMongoDB Database SoftwarePercona Server for MongoDBMongoDB Software
Barracuda Format
DocumentationPercona TokuMXRead MoreOpen Source Database ToolsPercona Monitoring and ManagementPercona ToolkitPercona Monitoring PluginsDatabase Tools DocumentationRead MoreDocumentation LibraryFind all the documentation you need to set up and manage all our products.Read MoreDownloadsRead More Solutions BuildHighly Scalable Data InfrastructureHighly Available Data InfrastructureData Infrastructure
Mysql Max Row Size
AutomationCloud Data StorageDatabase and Infrastructure Architecture and DesignRead MoreFixPerformance Audit, Tuning and OptimizationServer Audit and StabilizationDatabase Server Outage Restoration24 x 7 ExpertiseData RecoveryRead MoreOptimizeDatabase MonitoringApplication and Server Performance OptimizationInfrastructure Review and Design ServicesExpertise On DemandRead MoreManageRemote Managed ServicesProject Management and AdvisorsTrusted Data AdvisorsDatabase BackupRead More Community Data Performance BlogRead from leading data performance experts in Percona's Official blog.Read MoreEventsView all the information about upcoming events and shows where we can meet up!Read MoreForumsAsk Percona database experts for performance help now in our support forums!Read MoreLet's Get SocialTwitterLinkedInGoogle GroupsFacebookRead MoreMySQL 101 Sessions Resources WebinarsPercona offers free webinars about MySQL®, MongoDB®, OpenStack, NoSQL, Percona Toolkit, DBA best practices and more.Read MoreEbooksImportant literature for getting specialized on database management and administration.Read MoreTechnical Present
Joerg, Thanks for your reply. I found out that this error was limitation row length of 8000 bytes on InnoDB. I have check the dump sql file and one particular table is causing error 139. What I did is just to use MyISAM engine rather than InnoDB for a specific table only. BTW, the machine row size too large (> 8126) has 24GB memory and Quad-Core CPU. The platform is RHEL 5.5 x64 and mysql-server-5.0.77-4.el5_4.2. *Rob Wultsch
Innodb Page Size
*and Prabhat Kumar, thanks for your response. Regards, James On Tue, Jul 6, 2010 at 5:19 PM, Joerg Bruehe
contributorsReferencesBlogProfessional partnersHostingSupportTrainingInstallationIntegrationCustomizationSurvey creationTemplate design Log in Log in Log in with TwitterLog in with GoogleLog in with GitHub Forgot Login? Sign up IndexRulesSearchRecent Topics Welcome, Guest Username: Password: Forgot your password? https://www.limesurvey.org/forum/installation-a-update-issues/59022-got-error-139-from-storage-engine Forgot your username? Forum English support forums Installation & update issues Got error 139 from storage engine TOPIC: Got error 139 from storage engine Got error 139 from storage engine 5 years 6 months ago #59022 jamyles Offline Fresh Lemon Posts: 5 Karma: 0 We have an active survey that errors with "Got error got error 139 from storage engine" when trying to update a row. This survey has several text boxes per page. Reading the MySQL documentation, it appears that InnoDB can only handle 8000 bytes per row including the first 768 bytes of each blob (text, in this case) in the row. LimeSurvey is configured with $databasetabletype='InnoDB', but it from storage engine appears it's still trying to do more than InnoDB can handle. Is there a solution to this problem? Switch to MyISAM? LimeSurvey 1.87+ (build 8518) MySQL 5.0.45 using InnoDB Thanks in advance. The administrator has disabled public write access. JavaScript is currently disabled.Please enable it for a better experience of Jumi. Got error 139 from storage engine 5 years 6 months ago #59026 c_schmitz Offline LimeSurvey Team Posts: 1017 Thank you received: 135 Karma: 97 Yeah definately a switch to MyIsam should solve the issue. Best regards Carsten Schmitz LimeSurvey project leader The administrator has disabled public write access. Got error 139 from storage engine 5 years 6 months ago #59061 jamyles Offline Fresh Lemon Posts: 5 Karma: 0 That's what I was figuring. I did some testing, and it doesn't seem there's any way to use more than 9-10 text fields in a single survey. Any time a user fills all of them with 768 or more characters, the UPDATE