Mysql Error 137 When Fixing Table
4 vB4 Support & Troubleshooting Join us on Facebook, Twitter and YouTube. Welcome to the vBulletin support forums! In the forums you can receive professional support and assistance with any issues you might have with your vBulletin Products. If you are having problems posting in the relevant areas for your software, please see this topic. Announcement Collapse No announcement yet. MySQL Error : 137 when fixing table Collapse X Collapse Posts Latest Activity Search Page of 1 Filter Time All Time Today Last Week Last Month Show All Discussions only Photos only Videos only Links only Polls only Filtered by: Clear All new posts Previous Next fares.ly New Member Join Date: Jan 2010 Posts: 10 #1 [Forum] MySQL Error : 137 when fixing table Sun 25th Apr '10, 4:49pm Hello I got this error when I try to upgrade my forum from 4.0.2 to 4.0.3 PHP Code: DatabaseerrorinvBulletin4.0.2:
InvalidSQL:
ALTERTABLEpost
ADDhtmlstateENUM('off','on','on_nl2br')NOTNULLDEFAULT'on_nl2br';
MySQLError:137whenfixingtable
ErrorNumber:-1
RequestDate:Thursday,April22nd2010@01:11:14AM
ErrorDate:Thursday,April22nd2010@01:12http://www.vbulletin.com/forum/forum/vbulletin-4/vbulletin-4-questions-problems-and-troubleshooting/358724-mysql-error-137-when-fixing-table - Opteron 64-bit, RAM - 4GB, OS - Fedora Core 4, file system for /var/lib/mysql - xfs, MySQL 5.0.9-beta-Max 64-bit. I have this problem bouth on MySQL 5.0.9-beta-Max and "not Max" server. I will have 2 users and they will need SELECT only (no update or delete). At this moment I do not have https://bugs.mysql.com/bug.php?id=12166 any users. I increased all buffers to max but anyway computer never uses more than 3GB of RAM... mostly 1.5GB. my.cnf file: [mysqld] max_allowed_packet = 128M binlog_cache_size = 1M sort_buffer_size = 2048M join_buffer_size = 128M thread_concurrency = 2 query_cache_size = 640M query_cache_limit = 32M thread_stack = 512K tmp_table_size = 640M key_buffer_size = 1024M read_buffer_size = 320M read_rnd_buffer_size = 512M bulk_insert_buffer_size = 640M myisam_sort_buffer_size = 3072M myisam_max_sort_file_size = 300G myisam_max_extra_sort_file_size = 100G Tables are not compressed and do not have any indexes. I need only regular indexes (no primary no fulltext, etc.) Data types are CHAR, VARCHAR and variations of INT. No problems when I run indexing on 2.7GB table: ALTER TABLE ‘TableName’ ADD INDEX (ColumnName); it creates copies of files like: #sql-7ec-21.MYI (1024 bytes originally) #sql-7ec-21.MYD #sql-7ec-21.frm does processing in memory, write index into #sql-7ec-21.MYI, copies those files back to original files: TableName.MYI TableName.MYD TableName.frm NO problems here. When I run indexing on 26GB table (996,010,215 rows): ALTER TABLE ‘TableName’ ADD IN
Connectors More MySQL.com Downloads Developer Zone Section Menu: Documentation Home MySQL 5.7 Reference Manual Preface and Legal Notices General Information Installing and Upgrading MySQL Using MySQL as a Document Store Tutorial MySQL Programs MySQL Server https://dev.mysql.com/doc/refman/5.7/en/myisam-repair.html Administration Security Backup and Recovery Backup and Recovery Types Database Backup Methods Example Backup and Recovery Strategy Establishing a Backup Policy Using Backups for Recovery Backup Strategy Summary Using mysqldump for Backups Dumping Data http://www.heidisql.com/forum.php?t=14177 in SQL Format with mysqldump Reloading SQL-Format Backups Dumping Data in Delimited-Text Format with mysqldump Reloading Delimited-Text Format Backups mysqldump Tips Making a Copy of a Database Copy a Database from one Server mysql error to Another Dumping Stored Programs Dumping Table Definitions and Content Separately Using mysqldump to Test for Upgrade Incompatibilities Point-in-Time (Incremental) Recovery Using the Binary Log Point-in-Time Recovery Using Event Times Point-in-Time Recovery Using Event Positions MyISAM Table Maintenance and Crash Recovery Using myisamchk for Crash Recovery How to Check MyISAM Tables for Errors How to Repair MyISAM Tables MyISAM Table Optimization Setting Up a MyISAM Table mysql error 137 Maintenance Schedule Optimization Language Structure Globalization Data Types Functions and Operators SQL Statement Syntax The InnoDB Storage Engine Alternative Storage Engines High Availability and Scalability Replication MySQL Cluster NDB 7.5 Partitioning Stored Programs and Views INFORMATION_SCHEMA Tables MySQL Performance Schema MySQL sys Schema Connectors and APIs Extending MySQL MySQL Enterprise Edition MySQL Workbench MySQL 5.7 Frequently Asked Questions Errors, Error Codes, and Common Problems Restrictions and Limits Indexes MySQL Glossary Related Documentation MySQL 5.7 Release Notes Download this Manual PDF (US Ltr) - 35.6Mb PDF (A4) - 35.6Mb PDF (RPM) - 34.6Mb EPUB - 8.7Mb HTML Download (TGZ) - 8.4Mb HTML Download (Zip) - 8.5Mb HTML Download (RPM) - 7.3Mb Eclipse Doc Plugin (TGZ) - 9.3Mb Eclipse Doc Plugin (Zip) - 11.4Mb Man Pages (TGZ) - 202.2Kb Man Pages (Zip) - 307.4Kb Info (Gzip) - 3.3Mb Info (Zip) - 3.3Mb Excerpts from this Manual MySQL Backup and Recovery MySQL Globalization MySQL Information Schema MySQL Installation Guide MySQL and Linux/Unix MySQL and OS X MySQL Partitioning MySQL Performance Schema MySQL Replication Using the MySQL Yum Repository MySQL Restrictions and Limitations Security in MySQL MySQL and Solaris Building MySQL from Source Starting and Stopping MySQL MySQL Tutorial MySQL and Wind
Error exporting tables 20 Oct: [Feature Request] SQL Views "data" tab: ... 20 Oct: format SQL->select statement? 19 Oct: BUG - SQL Server column description not ... 19 Oct: Feature Request: Jump to column in Data ... 19 Oct: Calling of stored procedure auto conver ... 19 Oct: 6 errors when loading (importing) an sq ... 19 Oct: Uisng mySQL or importing mySQL 19 Oct: BUG - Showing wrong current database. 19 Oct: BUG - Error retrieving data when table ... 19 Oct: ALT+arrow shortcut breaks when one of t ... 18 Oct: BUG: Kill running query when user doesn ... 18 Oct: Crash when renaming index fields 18 Oct: [enhancement] Background color for a sp ... 18 Oct: BUG: varbinary 17 Oct: Feature Request: Export sql, but one fi ... 17 Oct: [Feature Request] Shortcut navigation t ... 17 Oct: Bug - Mysql Generated Column - STORED n ... DonateHow to donate List of donors HelpRequirements Connecting to a server Command line switches The database tree Creating a table Creating a view Creating a stored procedure Creating a trigger Creating a scheduled event The Data tab Running SQL queries SQL export HeidiSQL portable License Credits Get "SQL Error (137)" when running a query ... New topic Register Log in 3 posts GoranP.se posted 3 years ago in General Hello. I'm connected to a MS SQLExpress 2012. When I try to run a Query that contains a scalar variable, I get this message SQL Error (137). Example query declare @OrderNo varchar(20); Set @OrderNo = '7124476'; select * from tblPaket where OrderNr = @orderNo; If I try to run it in for example SQL Magnament Studio so it OK. Even if I run in my report, (Fast-Report), so it working. Why could I not run this type of questions in HeidiSQL? Please tell me what I'm doing wrong. Otherwise I like this superb tool. Rgs