I had this problem just this morning and wound up fixing it by changing the innodb data and log file directories to new folders in the .cnf file. This enabled to server to start up (new data and log files were created) and I then restored the data from a dump.
Kathy Mazur Worden > > > -----Original Message----- > > From: Dan Buettner [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, October 18, 2006 2:16 PM > > To: George-Cristian B=EErzan > > Cc: mysql@lists.mysql.com > > Subject: Re: InnoDB messup > > > > Can you just put the files back where they were originally? > > Ordinarily that would be in the path set up in mysql - see SHOW > > VARIABLES LIKE "datadir" > > > > You do need to have your ibdata* files and ib_logfile* files all in > > there, assuming you weren't using the file-per-table setup (if you > > were then I am not sure; haven't tried that one yet myself). > > > > I'd shut down the server process, move everything into place, > > double-check permissions on the files, and then start the mysqld > > server process back up. Hm, I did that, that's what I get after doing it. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]