version mimatch
Hi, I had binlogs from the mysql 4 which I was trying to get into mysql3 using the mysqlbinlog utility. Obviously I got the version mismatch error i.e ERROR 1064 at line 8: You have an error in your SQL syntax near 'DEFAULT ROW_FORMAT=DEFAULT' at line 1 My question, is there anywaay to make the logs compatible? Any help/pointer to where to look will be appreicated Thanks --NZ
mysql replication
Hello, Just a small question. I had mysql replication configured on my master and slave server. Due to some issues ( when I was on vacations ), logging on master server was switched off and server restarted. Now my question is that in order to resysnc my master and slave correctly, do I need to copy the master database again to slave and then turn on logging and start slave again, or by just enabling the logging again, slave will resync from last known state. I believe that if the logging on master was switched off, it will have no record of the changes made to database and I will need top recopy the database, but just to confirm or if there is any simpler way. Thanks
mysql dump
Hello every one, I have two questions actually. If there is a database server with couple of databases, and we only want to take the dump of few of them, can we specify a list of those on either mysqldump or mysql prompt ( for any other purpose ).or we have to run the mysqldump command seperately for every database. e.g. mysqldump --database1 database1.sql mysqldump --database2 database2.sql or mysqldump --database1 --database2 database.sql Second, when I am importing a dump file into another server, if that server already has thate database, it gives me an error of saying that the table/column already exists. Is there any switch to over ride that. I'll appreciate if some can please help me on above! Thanks Naufal
mysql dump
Hello everyone, Few conceptual questions which I can't understand. If any one can please gimme a a quicky! Am I correct when I say that mysqldump' only works when the database is up and running? and if it is true can any one please tell me that does taking a dump when a database is running is ok. Also the whats the difference in usage of mysqldump and taking just the backup of the database. Regards Naufal -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql dump
So is it safe to take the dump while database is running. I mean is there any loss of data expected because of taking dump while a database is running. On Nov 13, 2007 2:26 PM, Michael Dykman [EMAIL PROTECTED] wrote: On Nov 13, 2007 2:11 PM, Naufal Sheikh [EMAIL PROTECTED] wrote: Hello everyone, Few conceptual questions which I can't understand. If any one can please gimme a a quicky! Am I correct when I say that mysqldump' only works when the database is up and running? and if it is true can any one please tell me that does taking a dump when a database is running is ok. Also the whats the difference in usage of mysqldump and taking just the backup of the database. Regards Naufal Yes, mysqldump is just a specialized client for MySQL, it performs all of it's operations through a server. Whereas a raw file dump is, well, a raw file dump, mysqldump generates SQL scripts which will recreate your databases, tables and data when piped in to a simple command line client thus: mysqldump -h localhost -u user -p mydatabase mydatabase.sql then, it may be recreated mysql -h otherserver -u user -p databasewhichexists mydatabase.sql (command line examples are for *nix, but windows variants exist) - michael dykman -- - michael dykman - [EMAIL PROTECTED] - All models are wrong. Some models are useful. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql dump
Thank you so much! On Nov 13, 2007 2:40 PM, Craig Huffstetler [EMAIL PROTECTED] wrote: No, but a table lock or two may be expected. This is to PREVENT data loss (which you were also worried about). The mysqldump process will most likely be quick and painless (quick being a relative term, depending on the amount of data in your database(s)). Craig On Nov 13, 2007 2:35 PM, Naufal Sheikh [EMAIL PROTECTED] wrote: So is it safe to take the dump while database is running. I mean is there any loss of data expected because of taking dump while a database is running. On Nov 13, 2007 2:26 PM, Michael Dykman [EMAIL PROTECTED] wrote: On Nov 13, 2007 2:11 PM, Naufal Sheikh [EMAIL PROTECTED] wrote: Hello everyone, Few conceptual questions which I can't understand. If any one can please gimme a a quicky! Am I correct when I say that mysqldump' only works when the database is up and running? and if it is true can any one please tell me that does taking a dump when a database is running is ok. Also the whats the difference in usage of mysqldump and taking just the backup of the database. Regards Naufal Yes, mysqldump is just a specialized client for MySQL, it performs all of it's operations through a server. Whereas a raw file dump is, well, a raw file dump, mysqldump generates SQL scripts which will recreate your databases, tables and data when piped in to a simple command line client thus: mysqldump -h localhost -u user -p mydatabase mydatabase.sql then, it may be recreated mysql -h otherserver -u user -p databasewhichexists mydatabase.sql (command line examples are for *nix, but windows variants exist) - michael dykman -- - michael dykman - [EMAIL PROTECTED] - All models are wrong. Some models are useful. -- 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]
Detecting new records
Hello list. Inorder to do some maintainance, I will be shutting down my production server running mysql4.1. I have already prepared a backup server which is running mysql4 and have imported the current database in it. Though one way of doing things can be to shut down the database on the production server and then take the dump and import it on the backup server and then after shifting has been done to retake the dump from backpserver and import it on the production system. My question is that is there any better way to do this. E.g. If there is a way to detect for new records anmd/or changes made to database, I can just take those changes and export them on the production system. Or can we compare the two databases on seperate servers and then sync them. If some one can please point me to the right direction or give me a pointer on what to look for? Thanks and Regards Naufal
running a second mysql server
Hi List, Though new to mysql server, I was pretty happy with what I was doing till I needed to run another instance of mysql server on the same machine. My first installation is running on port 3307 instead of default which I achieved by adding a port attribute in /etc/my.cnf file. Rest of the /etc/my.cnf file contains the basedir, data dir . logs and pid etc. Now I need to install a second server running on 3306 and all different pid, datadir paths etc... When I install the second version giving all the enw paths to configure and then run mysqld, it always say mysqld is already running. I have tried other ways using the default-files option, changing the cnf file locations and none if it working. I will appreciate any pointers please! Thanks
