RE: Mysqlhotcopy and incorrect database name error - We must be dense

2003-09-22 Thread Dathan Vance Pattishall
I mean look at the --suffix


- Dathan Vance Pattishall
  - Sr. Programmer and mySQL DBA for FriendFinder Inc.
  - http://friendfinder.com/go/p40688


-->-Original Message-
-->From: Dathan Vance Pattishall [mailto:[EMAIL PROTECTED]
-->Sent: Monday, September 22, 2003 1:26 PM
-->To: 'Gilmore, Jason'; [EMAIL PROTECTED]
-->Subject: RE: Mysqlhotcopy and incorrect database name error - We must
be
-->dense
-->
-->Your not using mysqlhotcopy correctly.
-->
-->/usr/bin/mysqlhotcopy db_name[./table_regex/] [new_db_name |
directory]
-->
-->
-->The problem is this
-->mysqlhotcopy -u root --suffix=091703 staff  /backups
-->look at -u
-->
-->
-->here is a format from inside mysqlhotcopy
-->
-->mysqlhotcopy --method='scp -Bq -i /usr/home/foo/.ssh/identity'
-->--user=root --password=secretpassword \
--> db_1./^nice_table/
[EMAIL PROTECTED]:~/path/to/new_directory
-->
-->
-->
-->
-->- Dathan Vance Pattishall
-->  - Sr. Programmer and mySQL DBA for FriendFinder Inc.
-->  - http://friendfinder.com/go/p40688
-->
-->
-->-->-Original Message-
-->-->From: Gilmore, Jason [mailto:[EMAIL PROTECTED]
-->-->Sent: Monday, September 22, 2003 4:35 AM
-->-->To: [EMAIL PROTECTED]
-->-->Subject: FW: Mysqlhotcopy and incorrect database name error - We
must
-->be
-->-->dense
-->-->
-->-->Good morning,
-->-->
-->-->We're still battling with this; haven't heard back from anyone on
the
-->-->list... Resending one more time in the hopes that it catches
-->somebody's
-->-->eye.
-->-->
-->-->Thanks so much,
-->-->Jason
-->-->
-->-->-Original Message-
-->-->From: Gilmore, Jason
-->-->Sent: Wednesday, September 17, 2003 1:36 PM
-->-->To: [EMAIL PROTECTED]
-->-->Subject: Mysqlhotcopy and incorrect database name error - We must
be
-->-->dense
-->-->
-->-->
-->-->Hi there,
-->-->
-->-->A mysqlhotcopy issue has stumped no less than three of us here
today
-->at
-->-->work, ensuring that the solution is glaringly obvious. We're
trying
-->to
-->-->use mysqlhotcopy to copy a few databases. We want to make a local
-->copy,
-->-->nothing exotic, just want to move the database backups to the
-->directory
-->-->/backups/.
-->-->
-->-->In particular, we're attempting to make use of the following
syntax:
-->-->
-->-->mysqlhotcopy db_name [/path/to/new_directory]
-->-->
-->-->However, we receive an error when executing the following:
-->-->
-->-->%>
-->-->
-->-->The error is:
-->-->"DBI
-->-->connect('../backups/wjgilmore/;host=localhost;mysql_read_default_g
rou
-->p=m
-->-->ysqlhotcopy','root',...) failed: Incorrect database name
'/backups/'
-->at
-->-->./mysqlhotcopy line 747"
-->-->
-->-->In short, what's happening is that mysqlhotcopy thinks that
/backups/
-->is
-->-->a database that we'd like backed-up. Which, according to the
-->following
-->-->syntax form (shown in the mysqlhotcopy page of the MySQL manual):
-->-->
-->-->mysqlhotcopy db_name_1 ... db_name_n /path/to/new_directory
-->-->
-->-->Interestingly, when using a regular expression, the destination
-->-->directory is recognized immediately:
-->-->
-->-->%>mysqlhotcopy jan-2003./^sales/ /backups/
-->-->
-->-->The Juicy details:
-->-->* Redhat 7.2
-->-->* Perl 5.6.1
-->-->* Mysql 4.0.9-gamma (although we've tried mysqlhotcopy on three
-->-->different mysql versions, with no luck)
-->-->* Yes, the user has permission to write to /backups/
-->-->* Yes, the user has select and reload permissions.
-->-->
-->-->Thanks for any insight. This is driving all of us crazy. Also
looked
-->all
-->-->over the newsgroups regarding this, a few individuals have posted
-->-->similar questions, however none were answered.
-->-->
-->-->Best,
-->-->Jason
-->-->
-->-->==
-->-->Jason Gilmore
-->-->Systems Developer
-->-->The Fisher College of Business
-->-->
-->-->340 Mason Hall
-->-->250 W. Woodruff Ave.
-->-->Columbus, Ohio 43210
-->-->The Ohio State University
-->-->
-->-->e: [EMAIL PROTECTED]
-->-->t: 614-292-9754
-->-->
-->-->--
-->-->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]
-->
-->
-->
-->
-->--
-->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]



RE: Mysqlhotcopy and incorrect database name error - We must be dense

2003-09-22 Thread Dathan Vance Pattishall
Your not using mysqlhotcopy correctly.

/usr/bin/mysqlhotcopy db_name[./table_regex/] [new_db_name | directory]


The problem is this
mysqlhotcopy -u root --suffix=091703 staff  /backups
look at -u


here is a format from inside mysqlhotcopy

mysqlhotcopy --method='scp -Bq -i /usr/home/foo/.ssh/identity'
--user=root --password=secretpassword \
 db_1./^nice_table/ [EMAIL PROTECTED]:~/path/to/new_directory




- Dathan Vance Pattishall
  - Sr. Programmer and mySQL DBA for FriendFinder Inc.
  - http://friendfinder.com/go/p40688


-->-Original Message-
-->From: Gilmore, Jason [mailto:[EMAIL PROTECTED]
-->Sent: Monday, September 22, 2003 4:35 AM
-->To: [EMAIL PROTECTED]
-->Subject: FW: Mysqlhotcopy and incorrect database name error - We must
be
-->dense
-->
-->Good morning,
-->
-->We're still battling with this; haven't heard back from anyone on the
-->list... Resending one more time in the hopes that it catches
somebody's
-->eye.
-->
-->Thanks so much,
-->Jason
-->
-->-Original Message-
-->From: Gilmore, Jason
-->Sent: Wednesday, September 17, 2003 1:36 PM
-->To: [EMAIL PROTECTED]
-->Subject: Mysqlhotcopy and incorrect database name error - We must be
-->dense
-->
-->
-->Hi there,
-->
-->A mysqlhotcopy issue has stumped no less than three of us here today
at
-->work, ensuring that the solution is glaringly obvious. We're trying
to
-->use mysqlhotcopy to copy a few databases. We want to make a local
copy,
-->nothing exotic, just want to move the database backups to the
directory
-->/backups/.
-->
-->In particular, we're attempting to make use of the following syntax:
-->
-->mysqlhotcopy db_name [/path/to/new_directory]
-->
-->However, we receive an error when executing the following:
-->
-->%>
-->
-->The error is:
-->"DBI
-->connect('../backups/wjgilmore/;host=localhost;mysql_read_default_grou
p=m
-->ysqlhotcopy','root',...) failed: Incorrect database name '/backups/'
at
-->./mysqlhotcopy line 747"
-->
-->In short, what's happening is that mysqlhotcopy thinks that /backups/
is
-->a database that we'd like backed-up. Which, according to the
following
-->syntax form (shown in the mysqlhotcopy page of the MySQL manual):
-->
-->mysqlhotcopy db_name_1 ... db_name_n /path/to/new_directory
-->
-->Interestingly, when using a regular expression, the destination
-->directory is recognized immediately:
-->
-->%>mysqlhotcopy jan-2003./^sales/ /backups/
-->
-->The Juicy details:
-->* Redhat 7.2
-->* Perl 5.6.1
-->* Mysql 4.0.9-gamma (although we've tried mysqlhotcopy on three
-->different mysql versions, with no luck)
-->* Yes, the user has permission to write to /backups/
-->* Yes, the user has select and reload permissions.
-->
-->Thanks for any insight. This is driving all of us crazy. Also looked
all
-->over the newsgroups regarding this, a few individuals have posted
-->similar questions, however none were answered.
-->
-->Best,
-->Jason
-->
-->==
-->Jason Gilmore
-->Systems Developer
-->The Fisher College of Business
-->
-->340 Mason Hall
-->250 W. Woodruff Ave.
-->Columbus, Ohio 43210
-->The Ohio State University
-->
-->e: [EMAIL PROTECTED]
-->t: 614-292-9754
-->
-->--
-->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]




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



Re: Mysqlhotcopy and incorrect database name error - We must be dense

2003-09-22 Thread Egor Egorov
"Gilmore, Jason" <[EMAIL PROTECTED]> wrote:
> 
> A mysqlhotcopy issue has stumped no less than three of us here today at
> work, ensuring that the solution is glaringly obvious. We're trying to
> use mysqlhotcopy to copy a few databases. We want to make a local copy,
> nothing exotic, just want to move the database backups to the directory
> /backups/.
> 
> In particular, we're attempting to make use of the following syntax:
> 
> mysqlhotcopy db_name [/path/to/new_directory] 
> 
> However, we receive an error when executing the following:
> 
> %>mysqlhotcopy -u root --suffix=091703 staff  /backups

If you use --suffix option you should not specify location, because in this case 
mysqlhotcopy create a new database, f.e. staff091703, in the MySQL data dir. That is 
why you get "incorrect database name" error.

> 
> The error is:
> "DBI
> connect('../backups/wjgilmore/;host=localhost;mysql_read_default_group=m
> ysqlhotcopy','root',...) failed: Incorrect database name '/backups/' at
> ./mysqlhotcopy line 747"
> 
> In short, what's happening is that mysqlhotcopy thinks that /backups/ is
> a database that we'd like backed-up. Which, according to the following
> syntax form (shown in the mysqlhotcopy page of the MySQL manual):
> 
> mysqlhotcopy db_name_1 ... db_name_n /path/to/new_directory
> 
> Interestingly, when using a regular expression, the destination
> directory is recognized immediately:
> 
> %>mysqlhotcopy jan-2003./^sales/ /backups/
> 
> The Juicy details:
> * Redhat 7.2
> * Perl 5.6.1
> * Mysql 4.0.9-gamma (although we've tried mysqlhotcopy on three
> different mysql versions, with no luck)
> * Yes, the user has permission to write to /backups/
> * Yes, the user has select and reload permissions.
> 
> Thanks for any insight. This is driving all of us crazy. Also looked all
> over the newsgroups regarding this, a few individuals have posted
> similar questions, however none were answered.
> 



-- 
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]