Re: Errors in import and now zero DB access

Thanks,

Yes, as part of an upgrade, you will need to run this script mentioned in

https://developers.google.com/cloud-sql/docs/upgrade#download

Thanks!

Rob

On Wed, Apr 18, 2012 at 10:49 AM, Ronald Bradford <ronald.bradford@gmail.com> wrote:

FYI, not to overload this email, if you want a new thread for managing bugs etc.

sql> drop schema book2;
5 row(s) affected, 1 warning(s).
sql> show warnings;
+-------+------+--------------------------------------------------------------+
| Level | Code | Message                                                      |
+-------+------+--------------------------------------------------------------+
| Error | 1548 | Cannot load from mysql.proc. The table is probably corrupted |
+-------+------+--------------------------------------------------------------+
1 row in set (0.05 sec)


A side product of loading a mysqldump from MySQL 5.1 into 5.5  (aka a mysql_upgrade step).    I would almost prefer that the mysql meta schema is protected in imports.

Ronald

On Wed, Apr 18, 2012 at 1:47 PM, Ronald Bradford <ronald.bradford@gmail.com> wrote:

Great thanks.
Confirmed.
Will try without the routines.

So the import clearly failed, and you are not continuing on failure, (a.k.a. mysql -f option). Will that be an option? Will there be access to look at import failures, they may for example be acceptable in this case.

FYI, my testing is for my latest book, the print deadline is Monday, so I am rushing to add a new "MySQL in the Cloud" section following hearing about this last week at the MySQL conference.
http://effectivemysql.com/book/backup-recovery/

On Wed, Apr 18, 2012 at 1:42 PM, Rob Clevenger <rcleveng@google.com> wrote:

Hi Ronald.

Try --pass instead of --password.

As for the error, we have a bug where "DELIMITER" isn't supported in import. This should be fixed by the end of the week.

Thanks,

Rob

On Wed, Apr 18, 2012 at 10:26 AM, Ronald Bradford <ronald.bradford@gmail.com> wrote:

em-backupandrecovery:book2