Hello.
May be comments at: http://bugs.mysql.com/bug.php?id=1649 would be helpful for you. Does the altering successful if you executed a FLUSH TABLES before? See: http://dev.mysql.com/doc/mysql/en/merge-table-problems.html Mark Uhrmacher <[EMAIL PROTECTED]> wrote: > Hi Andy, > > I see that. Unfortunately, I have no idea why mysql is trying to create > a symlink to a symlink it just created. Does anyone have any idea why > mysql would do that? > > Thanks, > > Mark > > > Ady Wicaksono wrote: > >> Hi Mark, >> >> There's perror to check what happen, so when you have Error 17 you >> check from your bash shell like this >> >> # perror 17 >> Error code 17: File exists >> >> Gotcha !.... The reason is file exists :) >> >> Good luck >> >> Mark Uhrmacher wrote: >> >>> Hi all, >>> >>> I've been getting a strange error when attempting to add an index to >>> a set tables that make up a merge table. Here is a transcript of the >>> session: >>> >>> mysql> alter table he_access_offline_3 add index status (status); >>> ERROR 25 (HY000): Can't create symlink './Logs/#sql-156e_48d8.MYI' >>> pointing at '/var/lib/mysql/Logs/#sql-156e_48d8.MYI' (Error 17) >>> mysql> alter table he_access_offline_2 add index status (status); >>> ERROR 25 (HY000): Can't create symlink './Logs/#sql-156e_48d8.MYI' >>> pointing at '/var/lib/mysql/Logs/#sql-156e_48d8.MYI' (Error 17) >>> mysql> alter table he_access_offline_1 add index status (status); >>> ERROR 25 (HY000): Can't create symlink './Logs/#sql-156e_48d8.MYI' >>> pointing at '/var/lib/mysql/Logs/#sql-156e_48d8.MYI' (Error 17) >>> >>> What is interesting is that I could create that index on >>> he_access_offline_4 which is also a member of the merge table (called >>> he_access_offline). >>> >>> Doing some research with Google I found someone had a similar problem >>> when they were using symlinks from files in mysql's datadir to the >>> actual location of their data files. In my case the contents of >>> /var/lib/mysql/Logs are actual files and not symlinks. The >>> permissions appear to be set correctly and, in fact, I've created >>> other indexes on these same tables using the same scheme. I'm not >>> sure what has changed. >>> >>> Also, restarting the server doesn't eliminate the problem. >>> >>> System Info: >>> MySQL 4.1.9 on Fedora Core 2. I downloaded the binary from mysql.com. >>> >>> Any ideas? >>> >>> Thanks, >>> >>> Mark >>> >>> >> >> > > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
