cannot CREATE TABLE AS SELECT after moving database data folder to D drive

when the table get's created, that means your database folder should have received a new couple of files with the new table's name.
can you perform a regular insert after rebooting?
can you modify/insert into the other tables normally?

did you already look into the error log files of mysql?

You could move the db back to C:, then use mysqldump to dump it, then reinstall mysql on drive d, then
push the db back in.

Cheers,
za-k/

>when the table get's created, that means your database folder should have received a new couple of files with the new table's name.

the .frm file appears, but that is all

>can you perform a regular insert after rebooting?

yes

>can you modify/insert into the other tables normally?

yes

>did you already look into the error log files of mysql?

I looked at the .err file in the root of the data folder, but nothing appeared there. Is there somewhere else I should look?
 
thanks
Chris

what if you do it in 2 steps:

create table newtable AS select * from oldtable where 1=0;
 
insert into newtable select * from oldtable;

Select allOpen in new window

re:

create table newtable AS select * from oldtable where 1=0;
 
-  I get the same error:

ERROR 2013 (HY000): Lost connection to MySQL server during query

the database is then unavailable for a minute or so - any command (like 'show tables') I get:

ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
ERROR 2003 (HY000): Can't connect to MySQL server on 'localhost' (10061)
ERROR:
Can't connect to the server

then I can connect and the newtable shows when I do 'show tables'.

However, when I do 'describe newtable' I get:

 ERROR 1146 (42S02): Table 'psdb.newtable' doesn't exist

could you try the suggestion of adrpo?
can you attach the my.ini / my.cnf  (clearing security related data)?

I'd prefer not to reinstall the db if I can avoid it. I have not installed mysql before so do not know how difficult this is likely to prove...

here is the my.ini file:


# MySQL Server Instance Configuration File
# ----------------------------------------------------------------------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ----------------------------------------------------------------------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory
# of your server (e.g. C:\Program Files\MySQL\MySQL Server 4.1). To
# make sure the server reads the config file use the startup option
# "--defaults-file".
#
# To run run the server from the command line, execute this in a
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server 4.1\my.ini"
#
# To install the server as a Windows service manually, execute this in a
# command line shell, e.g.
# mysqld --install MySQL41 --defaults-file="C:\Program Files\MySQL\MySQL Server 4.1\my.ini"
#
# And then execute this in a command line shell to start the server, e.g.
# net start MySQL41
#
#
# Guildlines for editing this file
# ----------------------------------------------------------------------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
#
# CLIENT SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]

port=3306

[mysql]

default-character-set=latin1


# SERVER SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
#
[mysqld]

# The TCP/IP Port the MySQL Server will listen on
port=3306


#Path to installation directory. All paths are usually resolved relative to this.
basedir="C:/Program Files/MySQL/MySQL Server 5.0/"

#Path to the database root
#datadir="C:/Program Files/MySQL/MySQL Server 5.0/Data/"
#CJB
datadir="D:/mysql-data/data/"

# The default character set that will be used when a new schema or table is
# created and no character set is defined
default-character-set=latin1

# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB

# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=25

# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=0

# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_cache=256

# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=18M


# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before.  This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=8

#*** MyISAM Specific options

# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method.  This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_max_extra_sort_file_size=100G

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method.  This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=35M

# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=25M

# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K

# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=256K


#*** INNODB Specific options ***


# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
#skip-innodb

# Additional memory pool that is used by InnoDB to store metadata
# information.  If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS.  As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=2M

# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1

# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=1M

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system.  Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=47M

# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=24M

# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=8

#CJB
#minimum length for FULLTEXT SEARCH word - default is 4
ft_min_word_len=2

#CJB
#override FULLTEXT SEARCH stopword file as do not wish to use stopwords
ft_stopword_file=''

#CJB
#use this to timeout sleeps
interactive-timeout=300

Hi,

Try to change this in your settings and see what happens:
query_cache_size=0
to:
query_cache_size=15M

It might be this bug:
http://bugs.mysql.com/bug.php?id=9752
Look at the end.

Cheers,
za-k/

no, still get same error when I change this.

I also tried removing:

interactive-timeout=300

same error

changed:

max_connections=25

to:

max_connections=50

same error

when I do this:

CREATE TABLE newtable AS SELECT * FROM oldtable ORDER BY rating DESC, rating_adj  DESC, image_id DESC;

it runs for 5 minutes or so before I get the error. The order by is so I have rows in the right order for when I later add the FULLTEXT index. The table has 1.5 million rows in it.

I have another server which is less powerful and less ram and it runs fine...

any other ideas?

1. Did you do any other modifications in the .ini file besides
    changing the data directory?
    Just to make sure we don't follow wild quesses here.

2. Have you compared your .ini file with the
    slower server that runs your query fine?

Cheers,
za-k/

Another stupid question:
Is the filesystem the same on drive d: as on drive c:?

Meaning c: NTFS d:NTFS (not VFAT or so).

Cheers,
za-k/

>1. Did you do any other modifications in the .ini file besides
    changing the data directory?
    Just to make sure we don't follow wild quesses here.

- only the FULLTEXT settings at the bottom. All my changes should have CJB above them

>2. Have you compared your .ini file with the
    slower server that runs your query fine?

- they are the same.

>Is the filesystem the same on drive d: as on drive c:?
>Meaning c: NTFS d:NTFS (not VFAT or so).

- both are NTFS

I managed to clear some space on the C drive and have now changed the data directory back to original location the C drive. When I run the CREATE TABLE AS SELECT query I get the same error now! I am now wondering if it it is not due to the move to the d drive, but it was hidden before because the script was failing due to space constraints before whatever is causing the error.

And nothing appears in the error log??

Hi again,

Have you tried running the server with --log?
http://dev.mysql.com/doc/refman/5.0/en/using-log-files.html
Then look in the error log.

Also you could try using
EXPLAIN create table newtable AS select * from oldtable;

I wonder if explain craps out too.

Cheers,
za-k/

>And nothing appears in the error log??

- not in the .err file in the data directory - unless there is another error log elsewhere?

>Have you tried running the server with --log?
http://dev.mysql.com/doc/refman/5.0/en/using-log-files.html
Then look in the error log.

- the log file just shows the CREATE statement then nothing else.
- the .err file shows nothing

>Also you could try using
EXPLAIN create table newtable AS select * from oldtable;

- EXPLAIN CREATE doesn't seem to work - I tried it no another server too and doesn;t work their either.

What version of MySQL has the other server that works for you?
show version();

Do you still have a copy of your data directory on d:?
If not, you should backup and then try to run a
check table oldtable.

CREATE TABLE newtable AS SELECT * FROM oldtable ORDER BY rating DESC, rating_adj  DESC, image_id DESC;

When you do order by mysql will create a temporary table in your temporary directory. Do you have enough space for it? To what is your $TEMP
environment variable set to? Run these in a command line to find out:
echo %TEMP%
echo %TMP%

The connection also gets Lost connection during query if there is a timeout:
See what you timeout is. Write this in your mysql command line:
mysql> show variables like 'wait_%';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| wait_timeout  | 28800 |
+---------------+-------+
1 row in set (0.00 sec)

Cheers,
za-k/

In the end I decided there must be something corrupted soemwhere. I unistalled Mysql, and installed an updated version on the D drive (took 3 attempts!)

Now all works fine. Thanks for your help - still not sure what the actual problem was, but your suggestions led me to the point where it was clear that there was something serioulsy wrong which was not going to be easy to fix.