mysql error 87_InnoDB: Operating system error number 87 in a file operation. 错误87的解决方法

# MySQL Server Instance Configuration File#----------------------------------------------------------------------

# Generated bythe MySQL Server Instance Configuration Wizard

#

#

# Installation Instructions

#----------------------------------------------------------------------

#

#On Linux you can copy this file to /etc/my.cnf to setglobal options,

# mysql-data-dir/my.cnf to set server-specific options

# (@localstatedir@ for this installation) or to#~/.my.cnf to set user-specific options.

#

#On Windows you should keep this file inthe installation directory

#of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To# make sure the server reads the configfile use the startup option# "--defaults-file".

#

#To run run the server from the command line, execute this ina

# command line shell, e.g.

# mysqld--defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"

#

#To install the server as a Windows service manually, execute this ina

# command line shell, e.g.

# mysqld--install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"

#

#And then execute this in a command line shell tostart the server, e.g.

# net start MySQLXY

#

#

# Guildlinesfor editing this file#----------------------------------------------------------------------

#

#In this file, you can use all longoptions that the program supports.

#If you want toknow the options a program supports, start the program

#with the "--help" option.

#

# More detailed information about the individual options can also be

# foundinthe manual.

#

#

# CLIENT SECTION

#----------------------------------------------------------------------

#

# The following options will beread byMySQL client applications.

# Note thatonly client applications shipped byMySQL are guaranteed

#to read this section. If you want your own MySQL client program to# honor thesevalues, you need to specify it as an optionduring the

# MySQL client library initialization.

#[client]port=3306

[mysql]

default-character-set=utf8

# SERVER SECTION

#----------------------------------------------------------------------

#

# The following options will beread bythe MySQL Server. Make sure that

# you have installed the server correctly (see above) so it reads this

#file.

#[mysqld]log_bin=on

log=C:\Program Files\MySQL\MySQL Server 5.5\mylog.loglog_output=file# The TCP/IP Port the MySQL Server will listen onport=3306#Pathto installation directory. All paths are usually resolved relative tothis.

basedir="C:/Program Files/MySQL/MySQL Server 5.5/"

#Pathto the databaseroot

datadir="C:/MYSQLDataBase/"

# Thedefault character set that will be used when a new schema or table is# createdand no character set isdefinedcharacter-set-server=utf8

# Thedefault storage engine that will be used when create new tables when

default-storage-engine=INNODB

# The maximum amountofconcurrent sessions the MySQL server will

# allow. Oneof these connections will be reserved for a user with# SUPERprivileges to allow the administrator to login even ifthe

# connection limit has been reached.

max_connections=800# Query cacheis used to cache SELECT results and later returnthem

# without actual executing the same queryonce again. Havingthe query

# cache enabled may resultin significant speed improvements, ifyour

# have a lotof identical queries andrarely changing tables. See the

# "Qcache_lowmem_prunes" status variableto check if the currentvalue

#is high enough for your load.

# Note:In case your tables change very often or ifyour queries are

# textually different every time, the query cache may resultina

# slowdown insteadofa performance improvement.

query_cache_size=58M

# Thenumber of open tables for allthreads. Increasing this value

# increases thenumber of filedescriptors that mysqld requires.

# Therefore you haveto make sure to set the amount of openfiles

# allowedto at least 4096 in the variable "open-files-limit" in# section[mysqld_safe]table_cache=1520# Maximum sizefor internal (in-memory) temporary tables. If a table# grows larger than this value, itis automatically converted to disk# basedtable This limitation is for a single table. There can be many

#ofthem.

tmp_table_size=21M

# How many threads we should keepin a cache for reuse. Whena client

# disconnects, the client's threads are put in the cache if there aren't

# more than thread_cache_size threadsfrombefore. This greatly reduces

# the amountof thread creations needed if you have a lot ofnew

# connections. (Normally this doesn't give a notable performance

# improvement if you have a good thread implementation.)

thread_cache_size=38

#*** MyISAM Specific options

# The maximum size of the temporary file MySQL is allowed to use while

# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.

# If the file-size would be bigger than this, the index will be created

# through the key cache (which is slower).

myisam_max_sort_file_size=100G

# If the temporary file used for fast index creation would be bigger

# than using the key cache by the amount specified here, then prefer the

# key cache method. This is mainly used to force long character keys in

# large tables to use the slower key cache method to create the index.

myisam_sort_buffer_size=21M

# Size of the Key Buffer, used to cache index blocks for MyISAM tables.

# Do not set it larger than 30% of your available memory, as some memory

# is also required by the OS to cache rows. Even if you're notusing

# MyISAM tables, you should stillset it to 8-64M asit will also be

# usedfor internal temporary disktables.

key_buffer_size=9M

# Sizeof the buffer used for doing full table scans ofMyISAM tables.

# Allocated per thread,if a full scan isneeded.

read_buffer_size=64K

read_rnd_buffer_size=256K

# This bufferis allocated when MySQL needs to rebuild the index in# REPAIR, OPTIMZE,ALTER table statements as well as in LOADDATA INFILE

#into an empty table. It is allocated per thread so be careful with# large settings.

sort_buffer_size=256K

#*** INNODB Specific options ***innodb_data_home_dir="C:/MYSQLDataBase/"

#Use this option if you have a MySQL server withInnoDB support enabled

# but you donot plan to use it. This will save memory and disk space#and speed up somethings.

#skip-innodb

# Additional memory pool thatis used by InnoDB tostore metadata

# information.If InnoDB requires more memory forthis purpose it will

# startto allocate it from the OS. As this is fast enough onmost

# recent operating systems, you normally donot need tochange this

# value. SHOW INNODB STATUS will display thecurrentamount used.

innodb_additional_mem_pool_size=7M

#If set to 1, InnoDB will flush (fsync) the transaction logs tothe

#disk at each commit, which offers full ACID behavior. Ifyou are

# willingto compromise this safety, andyou are running small

# transactions, you mayset this to 0 or 2 to reduce disk I/O tothe

# logs. Value0 means that the log is only written to the log file and# thelog file flushed to disk approximately once per second. Value 2# means thelog is written to the log file at each commit, but the log#file is only flushed to disk approximately onceper second.

innodb_flush_log_at_trx_commit=1# The sizeof the buffer InnoDB uses for buffering log data. As soon as# itis full, InnoDB will have to flush it to disk. As it isflushed

#once per second anyway, it does not make sense tohave it very large

# (evenwith longtransactions).

innodb_log_buffer_size=4M

# InnoDB, unlike MyISAM, uses a buffer poolto cache both indexes and# row data. The bigger youset this the less disk I/O is needed to# access datain tables. On a dedicated database server you may setthis

# parameter upto 80% of the machine physical memory size. Do not setit

# too large, though, because competitionofthe physical memory may

# cause pagingin the operating system. Note that on 32bitsystems you

# might be limitedto 2-3.5G of user level memory per process, so do not#setit too high.

innodb_buffer_pool_size=324M

# Sizeof each log file in a log group. You should setthe combined size

#of log files to about 25%-100% of your buffer pool size toavoid

# unneeded buffer pool flush activityon log fileoverwrite. However,

# note that a larger logfile size will increase the time neededforthe

# recovery process.

innodb_log_file_size=65M

#Number ofthreads allowed inside the InnoDB kernel. The optimal value

# depends highlyon the application, hardware as well asthe OS

# scheduler properties. A too high value may leadtothread thrashing.

innodb_thread_concurrency=10innodb_flush_method=normal