MySQL Manual
7 MySQL Table Types
- 7.5
InnoDBTables- 7.5.1 InnoDB Tables Overview
- 7.5.2 InnoDB in MySQL Version 3.23
- 7.5.3 InnoDB Startup Options
- 7.5.4 Creating InnoDB Tablespace
- 7.5.5 Creating InnoDB Tables
- 7.5.6 Adding and Removing InnoDB Data and Log Files
- 7.5.7 Backing up and Recovering an InnoDB Database
- 7.5.8 Moving an InnoDB Database to Another Machine
- 7.5.9 InnoDB Transaction Model
- 7.5.10 Implementation of Multi-versioning
- 7.5.11 Table and Index Structures
- 7.5.12 File Space Management and Disk I/O
- 7.5.13 Error Handling
- 7.5.14 Restrictions on InnoDB Tables
- 7.5.15 InnoDB Change History
- 7.5.16
InnoDBContact Information
7.5.4 Creating InnoDB Tablespace
Suppose you have installed MySQL and have edited `my.cnf' so that it contains the necessary InnoDB configuration parameters. Before starting MySQL you should check that the directories you have specified for InnoDB datafiles and log files exist and that you have access rights to those directories. InnoDB cannot create directories, only files. Check also you have enough disk space for the data and log files.
When you now start MySQL, InnoDB will start creating your datafiles and log files. InnoDB will print something like the following:
~/mysqlm/sql > mysqld InnoDB: The first specified datafile /home/heikki/data/ibdata1 did not exist: InnoDB: a new database to be created! InnoDB: Setting file /home/heikki/data/ibdata1 size to 134217728 InnoDB: Database physically writes the file full: wait... InnoDB: datafile /home/heikki/data/ibdata2 did not exist: new to be created InnoDB: Setting file /home/heikki/data/ibdata2 size to 262144000 InnoDB: Database physically writes the file full: wait... InnoDB: Log file /home/heikki/data/logs/ib_logfile0 did not exist: new to be created InnoDB: Setting log file /home/heikki/data/logs/ib_logfile0 size to 5242880 InnoDB: Log file /home/heikki/data/logs/ib_logfile1 did not exist: new to be created InnoDB: Setting log file /home/heikki/data/logs/ib_logfile1 size to 5242880 InnoDB: Log file /home/heikki/data/logs/ib_logfile2 did not exist: new to be created InnoDB: Setting log file /home/heikki/data/logs/ib_logfile2 size to 5242880 InnoDB: Started mysqld: ready for connections
A new InnoDB database has now been created. You can connect to the MySQL
server with the usual MySQL client programs like mysql.
When you shut down the MySQL server with `mysqladmin shutdown',
InnoDB output will be like the following:
010321 18:33:34 mysqld: Normal shutdown 010321 18:33:34 mysqld: Shutdown Complete InnoDB: Starting shutdown... InnoDB: Shutdown completed
You can now look at the datafiles and logs directories and you will see the files created. The log directory will also contain a small file named `ib_arch_log_0000000000'. That file resulted from the database creation, after which InnoDB switched off log archiving. When MySQL is again started, the output will be like the following:
~/mysqlm/sql > mysqld InnoDB: Started mysqld: ready for connections
Subsections
User Comments
| Posted by Chris Faehl on Friday May 17 2002, @6:24am | [Delete] [Edit] |
Misleading info with regards to
innodb_data_file_path being the only necessary
variable to set.
If innodb_data_home_dir is unset, ./ is used. This
will cause absolute path names used in
innodb_data_file_path to fail.
| Posted by Alan Mead on Wednesday March 5 2003, @8:23am | [Delete] [Edit] |
FWIW, I had to become user mysql ('su - mysql') to start mysqld-max.
