Rusty Weaver <[EMAIL PROTECTED]> wrote: > After upgrading from to 4.0.18 I can no longer access my innodb tables > created under 3.23. I get these errors: > > % mysql -uroot db0 > ... > Didn't find any fields in table 'Employees' > ... > > My database files and .frm files are all present and readable. > No errors in the hostname.err file either. > I tried all the tips in the installation instructions, confirmed proper > file permissions, etc. > > Has anyone encountered this problem? I did not see this issue > discussed, and my only solution was using mysqldump to export > my tables prior to the upgrade, then import after. > > In the install docs I read that mysqldump *may* be required when > jumping to a new release series. Is that definitely the case for > 3.23 -> 4.0.18? I have a large data set and I want to avoid the > downtime for mysqldump. >
Check where your ibdata file is located and specify innodb_data_file_path variable. If innodb_data_file_path isn't specified by default innodb data file is created in the MySQL data dir. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [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]
