Previous: Tips and Tricks:
Tomcat |
Up: Tips and Tricks |
Next: Tips and Tricks:
Proxies |
If you are using MySQL on Windows, you may intermittently encounter an exception similar to
java.sql.SQLException: Can't create/write to file 'C:\WINDOWS\TEMP\#sql_318_0.MYD' (Errcode: 13)
There is a lot of chatter on the web about such errors, without any real clear answers as to what is happening. You'll get an error like this when you try to load content into the SyMBA database, e.g. via UnmarshalPeople, UnmarshalWorkflow or other similar classes.
There are a variety of thoughts as to the reason. Even though MySQL seems to have the permissions to write to the directory in question (as there are other temp files present there when you look), it seems to have a sudden problem with one of the files, namely the one that is mentioned in the exception. A temporary fix is to delete all of the tmp files in that directory. However, this does NOT solve the problem, and it will just occur again. Various forums have suggested defragging your hard disk, changing permissions in directories, and turning off the virus checking in the directory where MySQL keeps its temp files (the directory mentioned in the exception).
We have not found a satisfactory solution to this problem. The following was tried, but in the particular case was not effective.
If you have any problems, please contact symba-devel@lists.sourceforge.net.
Previous: Tips and Tricks:
Tomcat |
Up: Tips and Tricks |
Next: Tips and Tricks:
Proxies |