Got Error 139 From Storage Engine Mysql 5
Contents |
Cluster and HA SupportTokuMX SupportMongoDB SupportContact SupportPercona
Innodb Row Size Too Large
Emergency SupportSupport PoliciesSupport TiersRead MoreConsultingPerformance OptimizationInfrastructure Architecture and DesignHigh AvailabilityUpgrades & MigrationsServer
Mysql Max Row Size
& Database AutomationConsulting PoliciesRead MorePercona Care Software MySQL Database SoftwarePercona ServerPercona XtraDB ClusterPercona XtraBackupPercona TokuDBMySQL Software DocumentationSoftware RepositoriesRead
Mysql Row Size Too Large
MoreMongoDB Database SoftwarePercona Server for MongoDBMongoDB Software 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 row size too large (> 8126) More Solutions BuildHighly Scalable Data InfrastructureHighly Available Data InfrastructureData Infrastructure 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®, OpenS
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 innodb_file_format=barracuda specific table only. BTW, the machine has 24GB memory and Quad-Core CPU. The platform is mysql row limit RHEL 5.5 x64 and mysql-server-5.0.77-4.el5_4.2. *Rob Wultsch *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? Forgot your username? Forum English support forums Installation & update issues Got error 139 from storage engine https://www.limesurvey.org/forum/installation-a-update-issues/59022-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 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 row size first 768 bytes of each blob (text, in this case) in the row. LimeSurvey is configured with $databasetabletype='InnoDB', but it 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. row size too Got error 139 from storage engine 5 years 6 months ago #59026 c_schmitz Offline LimeSurvey Team Posts: 1020 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 will fail. I realize this probably means a significant change to the database schema to fix properly. Is there any plan to do this? Failing that, could the survey admin be warned about this when $databasetabletype='InnoDB' is set? The administrator has disabled public write access. Got error 139 from storage engine 5 years 6 months ago #59063 c_schmitz Offline LimeSurvey Team Posts: 1020 Thank you received: 135 Karma: 97 Actually I am not aware of such a issue at all. The only limitation with InnoDB I know of is that the number of fields in the result table cannot be more than 1000. This