Re: InnoDB question(s)

2003-06-10 Thread Nils Valentin
Hi Edward,

Thank you for the reply. I really appreciate the response,but I was thinking 
into a different direction.

I was hoping that perhaps additionally to the normal backup procedure that 
there is a shortcut or a trick which would quickly allow you to fix that 
specific issue (f.e. recover the orginal dbname).

Best regards

Nils Valentin
Tokyo/Japan

2003 6 10  14:55Becoming Digital :
 http://www.innodb.com/ibman.html#Backing_up

 See the section on Forcing Recovery.

 Edward Dudlik
 Becoming Digital
 www.becomingdigital.com


 - Original Message -
 From: Nils Valentin [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Tuesday, 10 June, 2003 01:40
 Subject: InnoDB question(s)



 O.K MySQL List This one is on me,

 a bit funny, a bit strange but with a serious background.
 You are allowed to laugh ;-).

 Assuming that somebody has the clever idea to rename the folder for a
 InnoDB database f.e. on the command line base (mv command for Linux). Now
 the mysqld server startsup and of course he will not be able to access any
 table , data etc. he will get something like below:

 mysql use sam_member_db
 Reading table information for completion of table and column names
 You can turn off this feature to get a quicker startup with -A

 Didn't find any fields in table 'discountplan'
 Didn't find any fields in table 'members'
 Didn't find any fields in table 'rank'
 Didn't find any fields in table 'relations'
 Database changed

 Then he would try to access one of the tables f.e. like this:

 mysql describe members
 - ;
 ERROR 1016: Can't open file: 'members.InnoDB'. (errno: 1)


 1) Is it possible to reconstruct which name the database originally had
 before the folder was renamed on the command line ?

 2) Is it possible to access or release (delete) the captured data related
 to the not anymore useable database ?

 Of course I could step through the log files trying to find the correct
 CREATE DATABASE dbname statement, but having seen the innodb log file
 sizes I would appreciate another solution ;-)


 PS: Didn't happen with serious data, just when fooling around with mysql.

 --

 Valentin Nils
 Internet Technology

  E-Mail: [EMAIL PROTECTED]
  URL: http://www.knowd.co.jp


 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:   
 http://lists.mysql.com/[EMAIL PROTECTED]

-- 

Valentin Nils
Internet Technology

 E-Mail: [EMAIL PROTECTED]
 URL: http://www.knowd.co.jp



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: InnoDB question(s)

2003-06-09 Thread Becoming Digital
http://www.innodb.com/ibman.html#Backing_up

See the section on Forcing Recovery.

Edward Dudlik
Becoming Digital
www.becomingdigital.com


- Original Message - 
From: Nils Valentin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, 10 June, 2003 01:40
Subject: InnoDB question(s)



O.K MySQL List This one is on me,

a bit funny, a bit strange but with a serious background. 
You are allowed to laugh ;-).

Assuming that somebody has the clever idea to rename the folder for a InnoDB 
database f.e. on the command line base (mv command for Linux). Now the mysqld 
server startsup and of course he will not be able to access any table , data 
etc. he will get something like below:

mysql use sam_member_db
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Didn't find any fields in table 'discountplan'
Didn't find any fields in table 'members'
Didn't find any fields in table 'rank'
Didn't find any fields in table 'relations'
Database changed

Then he would try to access one of the tables f.e. like this:

mysql describe members
- ;
ERROR 1016: Can't open file: 'members.InnoDB'. (errno: 1)


1) Is it possible to reconstruct which name the database originally had before 
the folder was renamed on the command line ?

2) Is it possible to access or release (delete) the captured data related to 
the not anymore useable database ?

Of course I could step through the log files trying to find the correct 
CREATE DATABASE dbname statement, but having seen the innodb log file sizes 
I would appreciate another solution ;-)

 
PS: Didn't happen with serious data, just when fooling around with mysql.

-- 

Valentin Nils
Internet Technology

 E-Mail: [EMAIL PROTECTED]
 URL: http://www.knowd.co.jp


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]





-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]