Error 6 Hy000 Mysql
Office 2007 Windows error hy000 mysql odbc 5.1 driver access denied for user 2003 Server PHP Date & Time Zend error 2002 hy000 mysql centos Studio Rackspace Rackspace Cloud WordPress ERROR 6 (HY000): Error on delete error 2003 hy000 mysql windows of ‘./database//db.opt' (Errcode: 13) Posted December 14, 2010 in MySql by medialam.Tags: MySql, MySql Server I was trying to drop a database in MySQL today but every time I did I got the error: ERROR 6 (HY000): Error on delete of './database//db.opt' (Errcode: 13) This was due to the fact permissions on the database folder were not allowing MySQL to delete the folder. There are a couple of ways you can fix this, either through the command line by finding the folder in question and changing the permissions to allow the MySQL user permissions, or through your FTP application, I am using WinSCP. Simply navigate to where you store your MySQL databases, right click on the folder in question and set the MySQL user to have read, write and execute permissions. You will now be able to drop the database. « Previous Post Next Post » Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website
Disha Email Updates: Status: Not a Bug Impact on me: None Category:MySQL Server Severity:S3 (Non-critical) Version:5.0.7 Beta OS:Microsoft Windows (Windows) Assigned to: Ingo Strüwing View Add Comment Files Developer Edit Submission View Progress Log Contributions [6 Jul 2005 9:23] Disha Description: If we try to drop a table used in merge table then incorrect error is displayed. How to repeat: 1. Start the MySQL client and connect to the database with valid user and password. 2. Set the delimiter to // 3. Create two tables as follows and insert values in it: create table t1(f1 int, f2 char(10))// create http://www.tech-problems.com/error-6-hy000-error-on-delete-of-databasedb-opt-errcode-13/ table t2(f1 int, f2 char(10))// insert into t1 values(1,'a')// insert into t2 values(2,'b')// 4. Create a merge table as follows and insert values in it: create table t3(f1new int, f2ne2 char(10)) type=merge union=(t1,t2) insert_method=first// insert into t3 values(3,'c')// 5. Now try to delete the base table (that is either t1 or t2) as follows: drop table t1// Expected Results: 1. Appropriate error should be displayed as the table is https://bugs.mysql.com/bug.php?id=11763 used in a merge table. Actual Results: 1. Incorrect error is displayed as follows: "ERROR 6 (HY000): Error on delete of '.\test\t1.MYI' (Errcode: 13)" [17 Jul 2005 19:45] Sergei Golubchik Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.mysql.com/documentation/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Additional info: This is documented as * You can't use DROP TABLE, ALTER TABLE, DELETE FROM without a WHERE clause, REPAIR TABLE, TRUNCATE TABLE, OPTIMIZE TABLE, or ANALYZE TABLE on any of the tables that are mapped into a MERGE table that is ``open.'' If you do this, the MERGE table may still refer to the original table and you get unexpected results. The easiest way to work around this deficiency is to issue a FLUSH TABLES statement to ensure that no MERGE tables remain ``open.'' http://dev.mysql.com/doc/mysql/en/merge-table-problems.html [17 Jul 2005 19:48] Sergei Golubchik The same url also mentions: * DROP TABLE on a table that is in use by a MERGE table does not work on Windows because the MERGE storage engine does the table mapping hidden from the upper layer of MySQL. Because Windows doesn't allow you to delete f
Community Podcasts MySQL.com Downloads Documentation Section Menu: MySQL Forums :: Replication :: Cannot Start Replication on Slave - "cannot find master.info" New http://forums.mysql.com/read.php?26,264592 Topic Advanced Search Cannot Start Replication on Slave - "cannot https://dev.mysql.com/doc/refman/5.6/en/myisam-repair.html find master.info" Posted by: Alex Recarey () Date: May 27, 2009 06:26PM Hello everybody. I have scoured the forums and the web searching to an answer to my problem to no avail. Thank you for taking the time to read about it. I am hy000 mysql using mysql 5.0.32 on Debian etch. I have one server set up as MySQL replication master, with binlog properly configured and working. I have another setup for use as a slave. The slave has a snapshot taken from the master while the master was "FLUSH TABLES WITH READ LOCK". I have noted the bil log error 6 hy000 file and position using the SHOW MASTER STATUS command. I switch to the slave, login, and execute: RESET SLAVE STOP SLAVE CHANGE MASTER TO MASTER_HOST='XXX.XXX.XXX.XXX', MASTER_USER='xxxxx', MASTER_PASSWORD='xxxxxxx', MASTER_LOG_FILE='master-bin.000005 ', MASTER_LOG_POS=18262972; I receive: ERROR 29 (HY000): File '/var/lib/mysql/master.info' not found (Errcode: 13) Yes, the master's binlog file is named master-bin.000005 If i manually create a master.info file, and change the permissions so that they are: -rw-rw---- 1 mysql mysql 0 2009-05-28 02:19 master.info When I put the command RESET SLAVE I get the message: ERROR 6 (HY000): Error on delete of '/var/lib/mysql/master.info' (Errcode: 13) If I directly try the CHANGE MASTER TO command: ERROR 1201 (HY000): Could not initialize master info structure; more error messages can be found in the MySQL error log and the mysql error log shows nothing. I have read the manual countless times, and I have also set up a replication setup successfully between two virtual machines. What am I doing wrong? Thank you for your help. Alex Navigate
Connectors More MySQL.com Downloads Developer Zone Section Menu: Documentation Home MySQL 5.6 Reference Manual Preface and Legal Notices General Information Installing and Upgrading MySQL Tutorial MySQL Programs MySQL Server 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 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 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 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.3 and MySQL Cluster NDB 7.4 Partitioning Stored Programs and Views INFORMATION_SCHEMA Tables MySQL Performance Schema Connectors and APIs Extending MySQL MySQL Enterprise Edition MySQL Workbench MySQL 5.6 Frequently Asked Questions Errors, Error Codes, and Common Problems Restrictions and Limits Indexes MySQL Glossary Related Documentation MySQL 5.6 Release Notes Download this Manual PDF (US Ltr) - 31.1Mb PDF (A4) - 31.1Mb PDF (RPM) - 30.4Mb EPUB - 7.8Mb HTML Download (TGZ) - 7.6Mb HTML Download (Zip) - 7.6Mb HTML Download (RPM) - 6.5Mb Eclipse Doc Plugin (TGZ) - 8.3Mb Eclipse Doc Plugin (Zip) - 10.1Mb Man Pages (TGZ) - 182.5Kb Man Pages (Zip) - 293.8Kb Info (Gzip) - 2.9Mb Info (Zip) - 2.9Mb 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 Windows MySQL Cluster