On Monday 19 December 2005 08:15, Bruce Carey wrote: > Hi List, > > I have recently had a crash coursh in the fineer points of > db recovery due to a mis-managed server. > > Could someone help me out with advice on the proper syntax > for doing mysqldump? I have a rather large db (4.2GB), and > regular dump files get easily corrupted, so I found out, > plus LONG restore times. My other problem is that many > fields will have \r and \n etc in them, for instance > because we store web content. So, I want to do it in this > format: > > mysqldump --opt --fields-terminated-by='\t' > --fields-optionally-enclosed-by='#*#*#' > --fields-escaped-by='\' --lines-terminated-by='\n\r' > --tab=/Users/theuser/testexport mydb mytable -u root -p
I wanted to try this, but got an error when trying it on my test database. I use the following commands in a script: mysqldump --opt --fields-terminated-by='\t' --fields-optionally-enclosed-by='#*#*#' --fields-escaped-by='\' --tab=/home/dahls/Dump imagedb -u root -p<roots-password> A file called albums.sql was created in the Dump directory, but then I got the following error: mysqldump: Got error: 1: Can't create/write to file '/home/dahls/Dump/albums.txt' (Errcode: 13) when executing 'SELECT INTO OUTFILE' -- Jørn Dahl-Stamnes homepage: http://www.dahl-stamnes.net/dahls/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
