DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH
 

(mysql.info.gz) InnoDB init

Info Catalog (mysql.info.gz) InnoDB start (mysql.info.gz) InnoDB (mysql.info.gz) Using InnoDB tables
 
 15.6 Creating the `InnoDB' Tablespace
 =====================================
 
 Suppose that you have installed MySQL and have edited your option file
 so that it contains the necessary `InnoDB' configuration parameters.
 Before starting MySQL, you should verify that the directories you have
 specified for `InnoDB' data files and log files exist and that the
 MySQL server has access rights to those directories. `InnoDB' cannot
 create directories, only files. Check also that you have enough disk
 space for the data and log files.
 
 It is best to run the MySQL server `mysqld' from the command prompt
 when you create an `InnoDB' database, not from the `mysqld_safe'
 wrapper or as a Windows service. When you run from a command prompt you
 see what `mysqld' prints and what is happening. On Unix, just invoke
 `mysqld'. On Windows, use the `--console' option.
 
 When you start the MySQL server after initially configuring `InnoDB' in
 your option file, `InnoDB' creates your data files and log files.
 `InnoDB' will print something like the following:
 
      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: Doublewrite buffer not found: creating new
      InnoDB: Doublewrite buffer created
      InnoDB: Creating foreign key constraint system tables
      InnoDB: Foreign key constraint system tables created
      InnoDB: Started
      mysqld: ready for connections
 
 A new `InnoDB' database has 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', the 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 look at the data file and log 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 started again, the data files and log files will have been created,
 so the output will be much briefer:
 
      InnoDB: Started
      mysqld: ready for connections
 
 Starting from MySQL 4.1.1, you can add the option
 `innodb_file_per_table' to `my.cnf', and make InnoDB to store each
 table into its own `.ibd' file in a database directory of MySQL.  
 Multiple tablespaces.
 

Menu

 
* Error creating InnoDB       Dealing with `InnoDB' Initialization Problems
 
Info Catalog (mysql.info.gz) InnoDB start (mysql.info.gz) InnoDB (mysql.info.gz) Using InnoDB tables
automatically generated byinfo2html