Oracle 5.0 Reference Manual page 1280

Adding, Removing, or Resizing
when it runs out of space. The increment size can be changed by setting the value of the
innodb_autoextend_increment
Alternatively, you can increase the size of your tablespace by adding another data file. To do this, you
have to shut down the MySQL server, change the tablespace configuration to add a new data file to the
end of
innodb_data_file_path
If your last data file was defined with the keyword autoextend, the procedure for reconfiguring the
tablespace must take into account the size to which the last data file has grown. Obtain the size of
the data file, round it down to the closest multiple of 1024 × 1024 bytes (= 1MB), and specify the
rounded size explicitly in
Remember that only the last data file in the
auto-extending.
As an example, assume that the tablespace has just one auto-extending data file ibdata1:
innodb_data_home_dir =
innodb_data_file_path = /ibdata/ibdata1:10M:autoextend
Suppose that this data file, over time, has grown to 988MB. Here is the configuration line after
modifying the original data file to not be auto-extending and adding another auto-extending data file:
innodb_data_home_dir =
innodb_data_file_path = /ibdata/ibdata1:988M;/disk2/ibdata2:50M:autoextend
When you add a new file to the tablespace configuration, make sure that it does not exist.
create and initialize the file when you restart the server.
Currently, you cannot remove a data file from the tablespace. To decrease the size of your tablespace,
use this procedure:
1. Use to dump all your
mysqldump
2. Stop the server.
3. Remove all the existing tablespace files, including the
keep a backup copy of the information, then copy all the
removing the files in your MySQL installation.
4. Remove any
.frm
5. Configure a new tablespace.
6. Restart the server.
7. Import the dump files.
If you want to change the number or the size of your
The procedure to use depends on the value of
• If
innodb_fast_shutdown
it shuts down without errors (to ensure that there is no information for outstanding transactions in
the log). Copy the old log files into a safe place in case something went wrong during the shutdown
and you need them to recover the tablespace. Delete the old log files from the log file directory, edit
to change the log file configuration, and start the MySQL server again.
my.cnf
log files exist at startup and creates new ones.
InnoDB
• If
innodb_fast_shutdown
mysql> SET GLOBAL innodb_fast_shutdown = 1;
Then follow the instructions in the previous item.
[1237] system variable, which is measured in MB.
[1240], and start the server again.
innodb_data_file_path
innodb_data_file_path
InnoDB
files for tables.
InnoDB
[1241] is not set to 2: Stop the MySQL server and make sure that
[1241] is set to 2: Set
1260
Data and Log Files
InnoDB
[1240]. Then you can add another data file.
tables.
and
ibdata
files to another location before the
ib*
log files, use the following instructions.
InnoDB
innodb_fast_shutdown
innodb_fast_shutdown
[1240] can be specified as
InnoDB
files. If you want to
ib_log
[1241]:
sees that no
mysqld
[1241] to 1:
will