title: MYSQLDUMP failing. Couldn't execute 'SHOW TRIGGERS LIKE errors like (Errcode: 13) (6) and (1036)
body: <p>Does anyone know why MYSQLDUMP would only perform a partial backup of a database when run with the following instruction:</p>
  
  <pre><code>"C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqldump" databaseSchema -u root --password=rootPassword &gt; c:\backups\daily\mySchema.dump
  </code></pre>
  
  <p>Sometimes a full backup is performed, at other times the backup will stop after including only a fraction of the database. This fraction is variable.</p>
  
  <p>The database does have several thousand tables totalling about 11Gb. But most of these tables are quite small with only about 1500 records, many only have 150 - 200 records. The column counts of these tables can be in the hundreds though because of the frequency data stored. </p>
  
  <p>But I am informed that the number of tables in a schema in MySQL is not an issue. There are also no performance issues during normal operation.</p>
  
  <p>And the alternative of using a single table is not really viable because all of these tables have different column name signatures.</p>
  
  <p>I should add that the database is in use during the backup.</p>
  
  <p>Well after running the backup with instruction set:</p>
  
  <pre><code>"C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqldump" mySchema -u root --password=xxxxxxx -v --debug-check --log-error=c:\backups\daily\mySchema_error.log &gt; c:\backups\daily\mySchema.dump
  </code></pre>
  
  <p>I get this:</p>
  
  <pre><code>mysqldump: Couldn't execute 'SHOW TRIGGERS LIKE '\_dm\_10730\_856956\_30072013\_1375194514706\_keyword\_frequencies'': Error on delete of 'C:\Windows\TEMP\#sql67c_10_8c5.MYI' (Errcode: 13) (6)
  </code></pre>
  
  <p>Which I think is a permissions problem.</p>
  
  <p>I doubt any one table in my schema is in the 2GB range.</p>
  
  <p>I am using MySQL Server 5.5 on a Windows 7 64 bit server with 8 Gb of memory.</p>
  
  <p>Any ideas?</p>
  
  <p>I am aware that changing the number of files which MySQL can open, the open_files_limit parameter, may cure this matter.</p>
  
  <p>Another possibility is interference from anti virus products as described here:</p>
  
  <p><a href="http://beerpla.net/2010/01/05/how-to-fix-intermittent-mysql-errcode-13-errors-on-windows/" rel="noreferrer">How To Fix Intermittent MySQL Errcode 13 Errors On Windows</a></p>