From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [slightly O/T] mysql problems
Date: Wed, 15 Oct 2014 21:40:56 +0100 [thread overview]
Message-ID: <201410152141.06240.michaelkintzios@gmail.com> (raw)
In-Reply-To: <543E6B5F.8050900@fastmail.co.uk>
[-- Attachment #1: Type: Text/Plain, Size: 2318 bytes --]
On Wednesday 15 Oct 2014 13:41:03 Kerin Millar wrote:
> > Database changed
> > mysql> DROP TABLE `website1@002dnew`.`actions`;
>
> Is this a table for which it is also complaining that a corresponding
> tablespace doesn't exist in database `website1@@002dnew`? Your original
> post mentioned only a table named `webform_validation_rule_components`.
Yes, there are loads of tables that it is complaining about. However, the
name of the database mentioned in the logs is not that of the local machine,
but of the remote.
> Whichever table(s) it is complaining about, if you happen to find a
> corresponding .idb file in a different database (sub-directory), you
> might be able to satisfy MySQL by copying it to where it is expecting to
> find it. If that works, you should then be able to drop it.
I lost you here. We have the local database, website_test. In it I can see a
number of tables. I also have other databases for different websites. Where
am I supposed to look for corresponding .idb files?
> Sometimes, directly copying an InnoDB tablespace into place requires a
> more elaborate procedure but I won't muddy the waters by describing said
> procedure just yet.
>
> > ERROR 1051 (42S02): Unknown table 'actions'
> > mysql> DISCARD TABLESPACE `website1@002dnew`.`actions`;
> > ERROR 1064 (42000): You have an error in your SQL syntax; check the
> > manual that corresponds to your MySQL server version for the right
> > syntax to use near 'DISCARD TABLESPACE `website1@002dnew`.`actions`' at
> > line 1
> > =========================
> >
> > I think in mysql-5.5 I should be using DROP TABLESPACE instead?
>
> My mistake. The correct syntax for discarding the tablespace would be:
>
> ALTER TABLE <table> DISCARD TABLESPACE;
>
> I'm stating the obvious here, but be sure not to DROP or DISCARD
> TABLESPACE on a table whose tablespace does exist and for which you do
> not have a backup. Both commands are destructive.
Well, I still have the backup from the live website, I can restore from it if
I have to. However, what I find confusing is that the errors mention the live
website's database name, not the local database. Shouldn't the import
function import the tables into the local database?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-10-15 20:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 18:54 [gentoo-user] [slightly O/T] mysql problems Mick
2014-10-14 19:21 ` Daniel Frey
2014-10-14 21:39 ` Mick
2014-10-14 20:15 ` Kerin Millar
2014-10-14 22:25 ` Mick
2014-10-15 1:14 ` Kerin Millar
2014-10-15 12:05 ` Mick
2014-10-15 12:41 ` Kerin Millar
2014-10-15 20:40 ` Mick [this message]
2014-10-16 6:24 ` J. Roeleveld
2014-10-17 23:17 ` Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201410152141.06240.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox