Author: paul
Date: 2008-11-04 19:53:35 +0100 (Tue, 04 Nov 2008)
New Revision: 12285
Log:
r39854@snake-hub: paul | 2008-11-04 11:49:07 -0600
Move a couple InnoDB sections
Modified:
trunk/refman-4.1/se-innodb-core.xml
trunk/refman-5.0/se-innodb-core.xml
trunk/refman-5.1/se-innodb-core.xml
trunk/refman-6.0/se-innodb-core.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35830
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:35291
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:34100
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:39854
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:35289
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:34100
Modified: trunk/refman-4.1/se-innodb-core.xml
===================================================================
--- trunk/refman-4.1/se-innodb-core.xml 2008-11-04 18:27:15 UTC (rev 12284)
+++ trunk/refman-4.1/se-innodb-core.xml 2008-11-04 18:53:35 UTC (rev 12285)
Changed blocks: 2, Lines Added: 179, Lines Deleted: 177; 13668 bytes
@@ -1049,6 +1049,185 @@
</section>
+ <section id="innodb-init">
+
+ <title>Creating the <literal>InnoDB</literal> Tablespace</title>
+
+ <para>
+ Suppose that you have installed MySQL and have edited your
+ option file so that it contains the necessary
+ <literal>InnoDB</literal> configuration parameters. Before
+ starting MySQL, you should verify that the directories you have
+ specified for <literal>InnoDB</literal> data files and log files
+ exist and that the MySQL server has access rights to those
+ directories. <literal>InnoDB</literal> does not create
+ directories, only files. Check also that you have enough disk
+ space for the data and log files.
+ </para>
+
+ <para>
+ It is best to run the MySQL server <command>mysqld</command>
+ from the command prompt when you first start the server with
+ <literal>InnoDB</literal> enabled, not from the
+ <command>mysqld_safe</command> wrapper or as a Windows service.
+ When you run from a command prompt you see what
+ <command>mysqld</command> prints and what is happening. On Unix,
+ just invoke <command>mysqld</command>. On Windows, use the
+ <option>--console</option> option.
+ </para>
+
+ <para>
+ When you start the MySQL server after initially configuring
+ <literal>InnoDB</literal> in your option file,
+ <literal>InnoDB</literal> creates your data files and log files,
+ and prints something like this:
+ </para>
+
+<programlisting>
+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
+</programlisting>
+
+ <para>
+ At this point <literal>InnoDB</literal> has initialized its
+ tablespace and log files. You can connect to the MySQL server
+ with the usual MySQL client programs like
+ <command>mysql</command>. When you shut down the MySQL server
+ with <command>mysqladmin shutdown</command>, the output is like
+ this:
+ </para>
+
+<programlisting>
+010321 18:33:34 mysqld: Normal shutdown
+010321 18:33:34 mysqld: Shutdown Complete
+InnoDB: Starting shutdown...
+InnoDB: Shutdown completed
+</programlisting>
+
+ <para>
+ You can look at the data file and log directories and you see
+ the files created there. The log directory also contains a small
+ file named <filename>ib_arch_log_0000000000</filename>. That
+ file resulted from the database creation, after which
+ <literal>InnoDB</literal> switched off log archiving. When MySQL
+ is started again, the data files and log files have been created
+ already, so the output is much briefer:
+ </para>
+
+<programlisting>
+InnoDB: Started
+mysqld: ready for connections
+</programlisting>
+
+ <para>
+ Starting from MySQL 4.1.1, you can add the option
+ <literal>innodb_file_per_table</literal> to
+ <filename>my.cnf</filename> to make <literal>InnoDB</literal>
+ store each table to its own <filename>.ibd</filename> file in
+ the same MySQL database directory where the
+ <filename>.frm</filename> file is created. See
+ <xref linkend="multiple-tablespaces"/>.
+ </para>
+
+ </section>
+
+ <section id="error-creating-innodb">
+
+ <title>Dealing with <literal>InnoDB</literal> Initialization Problems</title>
+
+ <para>
+ If <literal>InnoDB</literal> prints an operating system error
+ during a file operation, usually the problem has one of the
+ following causes:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ You did not create the <literal>InnoDB</literal> data file
+ directory or the <literal>InnoDB</literal> log directory.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqld</command> does not have access rights to
+ create files in those directories.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqld</command> cannot read the proper
+ <filename>my.cnf</filename> or <filename>my.ini</filename>
+ option file, and consequently does not see the options that
+ you specified.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The disk is full or a disk quota is exceeded.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ You have created a subdirectory whose name is equal to a
+ data file that you specified, so the name cannot be used as
+ a filename.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ There is a syntax error in the
+ <literal>innodb_data_home_dir</literal> or
+ <literal>innodb_data_file_path</literal> value.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ If something goes wrong when <literal>InnoDB</literal> attempts
+ to initialize its tablespace or its log files, you should delete
+ all files created by <literal>InnoDB</literal>. This means all
+ <filename>ibdata</filename> files and all
+ <filename>ib_logfile</filename> files. In case you have already
+ created some <literal>InnoDB</literal> tables, delete the
+ corresponding <filename>.frm</filename> files for these tables
+ (and any <filename>.ibd</filename> files if you are using
+ multiple tablespaces) from the MySQL database directories as
+ well. Then you can try the <literal>InnoDB</literal> database
+ creation again. It is best to start the MySQL server from a
+ command prompt so that you see what is happening.
+ </para>
+
+ </section>
+
</section>
<section id="innodb-parameters">
@@ -1826,183 +2005,6 @@
</section>
- <section id="innodb-init">
-
- <title>Creating the <literal>InnoDB</literal> Tablespace</title>
-
- <para>
- Suppose that you have installed MySQL and have edited your option
- file so that it contains the necessary <literal>InnoDB</literal>
- configuration parameters. Before starting MySQL, you should verify
- that the directories you have specified for
- <literal>InnoDB</literal> data files and log files exist and that
- the MySQL server has access rights to those directories.
- <literal>InnoDB</literal> does not create directories, only files.
- Check also that you have enough disk space for the data and log
- files.
- </para>
-
- <para>
- It is best to run the MySQL server <command>mysqld</command> from
- the command prompt when you first start the server with
- <literal>InnoDB</literal> enabled, not from the
- <command>mysqld_safe</command> wrapper or as a Windows service.
- When you run from a command prompt you see what
- <command>mysqld</command> prints and what is happening. On Unix,
- just invoke <command>mysqld</command>. On Windows, use the
- <option>--console</option> option.
- </para>
-
- <para>
- When you start the MySQL server after initially configuring
- <literal>InnoDB</literal> in your option file,
- <literal>InnoDB</literal> creates your data files and log files,
- and prints something like this:
- </para>
-
-<programlisting>
-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
-</programlisting>
-
- <para>
- At this point <literal>InnoDB</literal> has initialized its
- tablespace and log files. You can connect to the MySQL server with
- the usual MySQL client programs like <command>mysql</command>.
- When you shut down the MySQL server with <command>mysqladmin
- shutdown</command>, the output is like this:
- </para>
-
-<programlisting>
-010321 18:33:34 mysqld: Normal shutdown
-010321 18:33:34 mysqld: Shutdown Complete
-InnoDB: Starting shutdown...
-InnoDB: Shutdown completed
-</programlisting>
-
- <para>
- You can look at the data file and log directories and you see the
- files created there. The log directory also contains a small file
- named <filename>ib_arch_log_0000000000</filename>. That file
- resulted from the database creation, after which
- <literal>InnoDB</literal> switched off log archiving. When MySQL
- is started again, the data files and log files have been created
- already, so the output is much briefer:
- </para>
-
-<programlisting>
-InnoDB: Started
-mysqld: ready for connections
-</programlisting>
-
- <para>
- Starting from MySQL 4.1.1, you can add the option
- <literal>innodb_file_per_table</literal> to
- <filename>my.cnf</filename> to make <literal>InnoDB</literal>
- store each table to its own <filename>.ibd</filename> file in the
- same MySQL database directory where the <filename>.frm</filename>
- file is created. See <xref linkend="multiple-tablespaces"/>.
- </para>
-
- <section id="error-creating-innodb">
-
- <title>Dealing with <literal>InnoDB</literal> Initialization Problems</title>
-
- <para>
- If <literal>InnoDB</literal> prints an operating system error
- during a file operation, usually the problem has one of the
- following causes:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- You did not create the <literal>InnoDB</literal> data file
- directory or the <literal>InnoDB</literal> log directory.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqld</command> does not have access rights to
- create files in those directories.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqld</command> cannot read the proper
- <filename>my.cnf</filename> or <filename>my.ini</filename>
- option file, and consequently does not see the options that
- you specified.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The disk is full or a disk quota is exceeded.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You have created a subdirectory whose name is equal to a
- data file that you specified, so the name cannot be used as
- a filename.
- </para>
- </listitem>
-
- <listitem>
- <para>
- There is a syntax error in the
- <literal>innodb_data_home_dir</literal> or
- <literal>innodb_data_file_path</literal> value.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- If something goes wrong when <literal>InnoDB</literal> attempts
- to initialize its tablespace or its log files, you should delete
- all files created by <literal>InnoDB</literal>. This means all
- <filename>ibdata</filename> files and all
- <filename>ib_logfile</filename> files. In case you have already
- created some <literal>InnoDB</literal> tables, delete the
- corresponding <filename>.frm</filename> files for these tables
- (and any <filename>.ibd</filename> files if you are using
- multiple tablespaces) from the MySQL database directories as
- well. Then you can try the <literal>InnoDB</literal> database
- creation again. It is best to start the MySQL server from a
- command prompt so that you see what is happening.
- </para>
-
- </section>
-
- </section>
-
<section id="using-innodb-tables">
<title>Creating and Using <literal>InnoDB</literal> Tables</title>
Modified: trunk/refman-5.0/se-innodb-core.xml
===================================================================
--- trunk/refman-5.0/se-innodb-core.xml 2008-11-04 18:27:15 UTC (rev 12284)
+++ trunk/refman-5.0/se-innodb-core.xml 2008-11-04 18:53:35 UTC (rev 12285)
Changed blocks: 2, Lines Added: 174, Lines Deleted: 173; 13116 bytes
@@ -946,6 +946,180 @@
</section>
+ <section id="innodb-init">
+
+ <title>Creating the <literal>InnoDB</literal> Tablespace</title>
+
+ <para>
+ Suppose that you have installed MySQL and have edited your
+ option file so that it contains the necessary
+ <literal>InnoDB</literal> configuration parameters. Before
+ starting MySQL, you should verify that the directories you have
+ specified for <literal>InnoDB</literal> data files and log files
+ exist and that the MySQL server has access rights to those
+ directories. <literal>InnoDB</literal> does not create
+ directories, only files. Check also that you have enough disk
+ space for the data and log files.
+ </para>
+
+ <para>
+ It is best to run the MySQL server <command>mysqld</command>
+ from the command prompt when you first start the server with
+ <literal>InnoDB</literal> enabled, not from the
+ <command>mysqld_safe</command> wrapper or as a Windows service.
+ When you run from a command prompt you see what
+ <command>mysqld</command> prints and what is happening. On Unix,
+ just invoke <command>mysqld</command>. On Windows, use the
+ <option>--console</option> option.
+ </para>
+
+ <para>
+ When you start the MySQL server after initially configuring
+ <literal>InnoDB</literal> in your option file,
+ <literal>InnoDB</literal> creates your data files and log files,
+ and prints something like this:
+ </para>
+
+<programlisting>
+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
+</programlisting>
+
+ <para>
+ At this point <literal>InnoDB</literal> has initialized its
+ tablespace and log files. You can connect to the MySQL server
+ with the usual MySQL client programs like
+ <command>mysql</command>. When you shut down the MySQL server
+ with <command>mysqladmin shutdown</command>, the output is like
+ this:
+ </para>
+
+<programlisting>
+010321 18:33:34 mysqld: Normal shutdown
+010321 18:33:34 mysqld: Shutdown Complete
+InnoDB: Starting shutdown...
+InnoDB: Shutdown completed
+</programlisting>
+
+ <para>
+ You can look at the data file and log directories and you see
+ the files created there. When MySQL is started again, the data
+ files and log files have been created already, so the output is
+ much briefer:
+ </para>
+
+<programlisting>
+InnoDB: Started
+mysqld: ready for connections
+</programlisting>
+
+ <para>
+ If you add the <literal>innodb_file_per_table</literal> option
+ to <filename>my.cnf</filename>, <literal>InnoDB</literal> stores
+ each table in its own <filename>.ibd</filename> file in the same
+ MySQL database directory where the <filename>.frm</filename>
+ file is created. See <xref linkend="multiple-tablespaces"/>.
+ </para>
+
+ </section>
+
+ <section id="error-creating-innodb">
+
+ <title>Dealing with <literal>InnoDB</literal> Initialization Problems</title>
+
+ <para>
+ If <literal>InnoDB</literal> prints an operating system error
+ during a file operation, usually the problem has one of the
+ following causes:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ You did not create the <literal>InnoDB</literal> data file
+ directory or the <literal>InnoDB</literal> log directory.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqld</command> does not have access rights to
+ create files in those directories.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqld</command> cannot read the proper
+ <filename>my.cnf</filename> or <filename>my.ini</filename>
+ option file, and consequently does not see the options that
+ you specified.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The disk is full or a disk quota is exceeded.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ You have created a subdirectory whose name is equal to a
+ data file that you specified, so the name cannot be used as
+ a filename.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ There is a syntax error in the
+ <literal>innodb_data_home_dir</literal> or
+ <literal>innodb_data_file_path</literal> value.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ If something goes wrong when <literal>InnoDB</literal> attempts
+ to initialize its tablespace or its log files, you should delete
+ all files created by <literal>InnoDB</literal>. This means all
+ <filename>ibdata</filename> files and all
+ <filename>ib_logfile</filename> files. In case you have already
+ created some <literal>InnoDB</literal> tables, delete the
+ corresponding <filename>.frm</filename> files for these tables
+ (and any <filename>.ibd</filename> files if you are using
+ multiple tablespaces) from the MySQL database directories as
+ well. Then you can try the <literal>InnoDB</literal> database
+ creation again. It is best to start the MySQL server from a
+ command prompt so that you see what is happening.
+ </para>
+
+ </section>
+
</section>
<section id="innodb-parameters">
@@ -1961,179 +2135,6 @@
</section>
- <section id="innodb-init">
-
- <title>Creating the <literal>InnoDB</literal> Tablespace</title>
-
- <para>
- Suppose that you have installed MySQL and have edited your option
- file so that it contains the necessary <literal>InnoDB</literal>
- configuration parameters. Before starting MySQL, you should verify
- that the directories you have specified for
- <literal>InnoDB</literal> data files and log files exist and that
- the MySQL server has access rights to those directories.
- <literal>InnoDB</literal> does not create directories, only files.
- Check also that you have enough disk space for the data and log
- files.
- </para>
-
- <para>
- It is best to run the MySQL server <command>mysqld</command> from
- the command prompt when you first start the server with
- <literal>InnoDB</literal> enabled, not from the
- <command>mysqld_safe</command> wrapper or as a Windows service.
- When you run from a command prompt you see what
- <command>mysqld</command> prints and what is happening. On Unix,
- just invoke <command>mysqld</command>. On Windows, use the
- <option>--console</option> option.
- </para>
-
- <para>
- When you start the MySQL server after initially configuring
- <literal>InnoDB</literal> in your option file,
- <literal>InnoDB</literal> creates your data files and log files,
- and prints something like this:
- </para>
-
-<programlisting>
-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
-</programlisting>
-
- <para>
- At this point <literal>InnoDB</literal> has initialized its
- tablespace and log files. You can connect to the MySQL server with
- the usual MySQL client programs like <command>mysql</command>.
- When you shut down the MySQL server with <command>mysqladmin
- shutdown</command>, the output is like this:
- </para>
-
-<programlisting>
-010321 18:33:34 mysqld: Normal shutdown
-010321 18:33:34 mysqld: Shutdown Complete
-InnoDB: Starting shutdown...
-InnoDB: Shutdown completed
-</programlisting>
-
- <para>
- You can look at the data file and log directories and you see the
- files created there. When MySQL is started again, the data files
- and log files have been created already, so the output is much
- briefer:
- </para>
-
-<programlisting>
-InnoDB: Started
-mysqld: ready for connections
-</programlisting>
-
- <para>
- If you add the <literal>innodb_file_per_table</literal> option to
- <filename>my.cnf</filename>, <literal>InnoDB</literal> stores each
- table in its own <filename>.ibd</filename> file in the same MySQL
- database directory where the <filename>.frm</filename> file is
- created. See <xref linkend="multiple-tablespaces"/>.
- </para>
-
- <section id="error-creating-innodb">
-
- <title>Dealing with <literal>InnoDB</literal> Initialization Problems</title>
-
- <para>
- If <literal>InnoDB</literal> prints an operating system error
- during a file operation, usually the problem has one of the
- following causes:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- You did not create the <literal>InnoDB</literal> data file
- directory or the <literal>InnoDB</literal> log directory.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqld</command> does not have access rights to
- create files in those directories.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqld</command> cannot read the proper
- <filename>my.cnf</filename> or <filename>my.ini</filename>
- option file, and consequently does not see the options that
- you specified.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The disk is full or a disk quota is exceeded.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You have created a subdirectory whose name is equal to a
- data file that you specified, so the name cannot be used as
- a filename.
- </para>
- </listitem>
-
- <listitem>
- <para>
- There is a syntax error in the
- <literal>innodb_data_home_dir</literal> or
- <literal>innodb_data_file_path</literal> value.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- If something goes wrong when <literal>InnoDB</literal> attempts
- to initialize its tablespace or its log files, you should delete
- all files created by <literal>InnoDB</literal>. This means all
- <filename>ibdata</filename> files and all
- <filename>ib_logfile</filename> files. In case you have already
- created some <literal>InnoDB</literal> tables, delete the
- corresponding <filename>.frm</filename> files for these tables
- (and any <filename>.ibd</filename> files if you are using
- multiple tablespaces) from the MySQL database directories as
- well. Then you can try the <literal>InnoDB</literal> database
- creation again. It is best to start the MySQL server from a
- command prompt so that you see what is happening.
- </para>
-
- </section>
-
- </section>
-
<section id="using-innodb-tables">
<title>Creating and Using <literal>InnoDB</literal> Tables</title>
Modified: trunk/refman-5.1/se-innodb-core.xml
===================================================================
--- trunk/refman-5.1/se-innodb-core.xml 2008-11-04 18:27:15 UTC (rev 12284)
+++ trunk/refman-5.1/se-innodb-core.xml 2008-11-04 18:53:35 UTC (rev 12285)
Changed blocks: 2, Lines Added: 174, Lines Deleted: 173; 13116 bytes
@@ -964,6 +964,180 @@
</section>
+ <section id="innodb-init">
+
+ <title>Creating the <literal>InnoDB</literal> Tablespace</title>
+
+ <para>
+ Suppose that you have installed MySQL and have edited your
+ option file so that it contains the necessary
+ <literal>InnoDB</literal> configuration parameters. Before
+ starting MySQL, you should verify that the directories you have
+ specified for <literal>InnoDB</literal> data files and log files
+ exist and that the MySQL server has access rights to those
+ directories. <literal>InnoDB</literal> does not create
+ directories, only files. Check also that you have enough disk
+ space for the data and log files.
+ </para>
+
+ <para>
+ It is best to run the MySQL server <command>mysqld</command>
+ from the command prompt when you first start the server with
+ <literal>InnoDB</literal> enabled, not from the
+ <command>mysqld_safe</command> wrapper or as a Windows service.
+ When you run from a command prompt you see what
+ <command>mysqld</command> prints and what is happening. On Unix,
+ just invoke <command>mysqld</command>. On Windows, use the
+ <option>--console</option> option.
+ </para>
+
+ <para>
+ When you start the MySQL server after initially configuring
+ <literal>InnoDB</literal> in your option file,
+ <literal>InnoDB</literal> creates your data files and log files,
+ and prints something like this:
+ </para>
+
+<programlisting>
+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
+</programlisting>
+
+ <para>
+ At this point <literal>InnoDB</literal> has initialized its
+ tablespace and log files. You can connect to the MySQL server
+ with the usual MySQL client programs like
+ <command>mysql</command>. When you shut down the MySQL server
+ with <command>mysqladmin shutdown</command>, the output is like
+ this:
+ </para>
+
+<programlisting>
+010321 18:33:34 mysqld: Normal shutdown
+010321 18:33:34 mysqld: Shutdown Complete
+InnoDB: Starting shutdown...
+InnoDB: Shutdown completed
+</programlisting>
+
+ <para>
+ You can look at the data file and log directories and you see
+ the files created there. When MySQL is started again, the data
+ files and log files have been created already, so the output is
+ much briefer:
+ </para>
+
+<programlisting>
+InnoDB: Started
+mysqld: ready for connections
+</programlisting>
+
+ <para>
+ If you add the <literal>innodb_file_per_table</literal> option
+ to <filename>my.cnf</filename>, <literal>InnoDB</literal> stores
+ each table in its own <filename>.ibd</filename> file in the same
+ MySQL database directory where the <filename>.frm</filename>
+ file is created. See <xref linkend="multiple-tablespaces"/>.
+ </para>
+
+ </section>
+
+ <section id="error-creating-innodb">
+
+ <title>Dealing with <literal>InnoDB</literal> Initialization Problems</title>
+
+ <para>
+ If <literal>InnoDB</literal> prints an operating system error
+ during a file operation, usually the problem has one of the
+ following causes:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ You did not create the <literal>InnoDB</literal> data file
+ directory or the <literal>InnoDB</literal> log directory.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqld</command> does not have access rights to
+ create files in those directories.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqld</command> cannot read the proper
+ <filename>my.cnf</filename> or <filename>my.ini</filename>
+ option file, and consequently does not see the options that
+ you specified.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The disk is full or a disk quota is exceeded.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ You have created a subdirectory whose name is equal to a
+ data file that you specified, so the name cannot be used as
+ a filename.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ There is a syntax error in the
+ <literal>innodb_data_home_dir</literal> or
+ <literal>innodb_data_file_path</literal> value.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ If something goes wrong when <literal>InnoDB</literal> attempts
+ to initialize its tablespace or its log files, you should delete
+ all files created by <literal>InnoDB</literal>. This means all
+ <filename>ibdata</filename> files and all
+ <filename>ib_logfile</filename> files. In case you have already
+ created some <literal>InnoDB</literal> tables, delete the
+ corresponding <filename>.frm</filename> files for these tables
+ (and any <filename>.ibd</filename> files if you are using
+ multiple tablespaces) from the MySQL database directories as
+ well. Then you can try the <literal>InnoDB</literal> database
+ creation again. It is best to start the MySQL server from a
+ command prompt so that you see what is happening.
+ </para>
+
+ </section>
+
</section>
<section id="innodb-parameters">
@@ -2004,179 +2178,6 @@
</section>
- <section id="innodb-init">
-
- <title>Creating the <literal>InnoDB</literal> Tablespace</title>
-
- <para>
- Suppose that you have installed MySQL and have edited your option
- file so that it contains the necessary <literal>InnoDB</literal>
- configuration parameters. Before starting MySQL, you should verify
- that the directories you have specified for
- <literal>InnoDB</literal> data files and log files exist and that
- the MySQL server has access rights to those directories.
- <literal>InnoDB</literal> does not create directories, only files.
- Check also that you have enough disk space for the data and log
- files.
- </para>
-
- <para>
- It is best to run the MySQL server <command>mysqld</command> from
- the command prompt when you first start the server with
- <literal>InnoDB</literal> enabled, not from the
- <command>mysqld_safe</command> wrapper or as a Windows service.
- When you run from a command prompt you see what
- <command>mysqld</command> prints and what is happening. On Unix,
- just invoke <command>mysqld</command>. On Windows, use the
- <option>--console</option> option.
- </para>
-
- <para>
- When you start the MySQL server after initially configuring
- <literal>InnoDB</literal> in your option file,
- <literal>InnoDB</literal> creates your data files and log files,
- and prints something like this:
- </para>
-
-<programlisting>
-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
-</programlisting>
-
- <para>
- At this point <literal>InnoDB</literal> has initialized its
- tablespace and log files. You can connect to the MySQL server with
- the usual MySQL client programs like <command>mysql</command>.
- When you shut down the MySQL server with <command>mysqladmin
- shutdown</command>, the output is like this:
- </para>
-
-<programlisting>
-010321 18:33:34 mysqld: Normal shutdown
-010321 18:33:34 mysqld: Shutdown Complete
-InnoDB: Starting shutdown...
-InnoDB: Shutdown completed
-</programlisting>
-
- <para>
- You can look at the data file and log directories and you see the
- files created there. When MySQL is started again, the data files
- and log files have been created already, so the output is much
- briefer:
- </para>
-
-<programlisting>
-InnoDB: Started
-mysqld: ready for connections
-</programlisting>
-
- <para>
- If you add the <literal>innodb_file_per_table</literal> option to
- <filename>my.cnf</filename>, <literal>InnoDB</literal> stores each
- table in its own <filename>.ibd</filename> file in the same MySQL
- database directory where the <filename>.frm</filename> file is
- created. See <xref linkend="multiple-tablespaces"/>.
- </para>
-
- <section id="error-creating-innodb">
-
- <title>Dealing with <literal>InnoDB</literal> Initialization Problems</title>
-
- <para>
- If <literal>InnoDB</literal> prints an operating system error
- during a file operation, usually the problem has one of the
- following causes:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- You did not create the <literal>InnoDB</literal> data file
- directory or the <literal>InnoDB</literal> log directory.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqld</command> does not have access rights to
- create files in those directories.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqld</command> cannot read the proper
- <filename>my.cnf</filename> or <filename>my.ini</filename>
- option file, and consequently does not see the options that
- you specified.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The disk is full or a disk quota is exceeded.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You have created a subdirectory whose name is equal to a
- data file that you specified, so the name cannot be used as
- a filename.
- </para>
- </listitem>
-
- <listitem>
- <para>
- There is a syntax error in the
- <literal>innodb_data_home_dir</literal> or
- <literal>innodb_data_file_path</literal> value.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- If something goes wrong when <literal>InnoDB</literal> attempts
- to initialize its tablespace or its log files, you should delete
- all files created by <literal>InnoDB</literal>. This means all
- <filename>ibdata</filename> files and all
- <filename>ib_logfile</filename> files. In case you have already
- created some <literal>InnoDB</literal> tables, delete the
- corresponding <filename>.frm</filename> files for these tables
- (and any <filename>.ibd</filename> files if you are using
- multiple tablespaces) from the MySQL database directories as
- well. Then you can try the <literal>InnoDB</literal> database
- creation again. It is best to start the MySQL server from a
- command prompt so that you see what is happening.
- </para>
-
- </section>
-
- </section>
-
<section id="using-innodb-tables">
<title>Creating and Using <literal>InnoDB</literal> Tables</title>
Modified: trunk/refman-6.0/se-innodb-core.xml
===================================================================
--- trunk/refman-6.0/se-innodb-core.xml 2008-11-04 18:27:15 UTC (rev 12284)
+++ trunk/refman-6.0/se-innodb-core.xml 2008-11-04 18:53:35 UTC (rev 12285)
Changed blocks: 2, Lines Added: 174, Lines Deleted: 173; 13116 bytes
@@ -939,6 +939,180 @@
</section>
+ <section id="innodb-init">
+
+ <title>Creating the <literal>InnoDB</literal> Tablespace</title>
+
+ <para>
+ Suppose that you have installed MySQL and have edited your
+ option file so that it contains the necessary
+ <literal>InnoDB</literal> configuration parameters. Before
+ starting MySQL, you should verify that the directories you have
+ specified for <literal>InnoDB</literal> data files and log files
+ exist and that the MySQL server has access rights to those
+ directories. <literal>InnoDB</literal> does not create
+ directories, only files. Check also that you have enough disk
+ space for the data and log files.
+ </para>
+
+ <para>
+ It is best to run the MySQL server <command>mysqld</command>
+ from the command prompt when you first start the server with
+ <literal>InnoDB</literal> enabled, not from the
+ <command>mysqld_safe</command> wrapper or as a Windows service.
+ When you run from a command prompt you see what
+ <command>mysqld</command> prints and what is happening. On Unix,
+ just invoke <command>mysqld</command>. On Windows, use the
+ <option>--console</option> option.
+ </para>
+
+ <para>
+ When you start the MySQL server after initially configuring
+ <literal>InnoDB</literal> in your option file,
+ <literal>InnoDB</literal> creates your data files and log files,
+ and prints something like this:
+ </para>
+
+<programlisting>
+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
+</programlisting>
+
+ <para>
+ At this point <literal>InnoDB</literal> has initialized its
+ tablespace and log files. You can connect to the MySQL server
+ with the usual MySQL client programs like
+ <command>mysql</command>. When you shut down the MySQL server
+ with <command>mysqladmin shutdown</command>, the output is like
+ this:
+ </para>
+
+<programlisting>
+010321 18:33:34 mysqld: Normal shutdown
+010321 18:33:34 mysqld: Shutdown Complete
+InnoDB: Starting shutdown...
+InnoDB: Shutdown completed
+</programlisting>
+
+ <para>
+ You can look at the data file and log directories and you see
+ the files created there. When MySQL is started again, the data
+ files and log files have been created already, so the output is
+ much briefer:
+ </para>
+
+<programlisting>
+InnoDB: Started
+mysqld: ready for connections
+</programlisting>
+
+ <para>
+ If you add the <literal>innodb_file_per_table</literal> option
+ to <filename>my.cnf</filename>, <literal>InnoDB</literal> stores
+ each table in its own <filename>.ibd</filename> file in the same
+ MySQL database directory where the <filename>.frm</filename>
+ file is created. See <xref linkend="multiple-tablespaces"/>.
+ </para>
+
+ </section>
+
+ <section id="error-creating-innodb">
+
+ <title>Dealing with <literal>InnoDB</literal> Initialization Problems</title>
+
+ <para>
+ If <literal>InnoDB</literal> prints an operating system error
+ during a file operation, usually the problem has one of the
+ following causes:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ You did not create the <literal>InnoDB</literal> data file
+ directory or the <literal>InnoDB</literal> log directory.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqld</command> does not have access rights to
+ create files in those directories.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqld</command> cannot read the proper
+ <filename>my.cnf</filename> or <filename>my.ini</filename>
+ option file, and consequently does not see the options that
+ you specified.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The disk is full or a disk quota is exceeded.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ You have created a subdirectory whose name is equal to a
+ data file that you specified, so the name cannot be used as
+ a filename.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ There is a syntax error in the
+ <literal>innodb_data_home_dir</literal> or
+ <literal>innodb_data_file_path</literal> value.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ If something goes wrong when <literal>InnoDB</literal> attempts
+ to initialize its tablespace or its log files, you should delete
+ all files created by <literal>InnoDB</literal>. This means all
+ <filename>ibdata</filename> files and all
+ <filename>ib_logfile</filename> files. In case you have already
+ created some <literal>InnoDB</literal> tables, delete the
+ corresponding <filename>.frm</filename> files for these tables
+ (and any <filename>.ibd</filename> files if you are using
+ multiple tablespaces) from the MySQL database directories as
+ well. Then you can try the <literal>InnoDB</literal> database
+ creation again. It is best to start the MySQL server from a
+ command prompt so that you see what is happening.
+ </para>
+
+ </section>
+
</section>
<section id="innodb-parameters">
@@ -1906,179 +2080,6 @@
</section>
- <section id="innodb-init">
-
- <title>Creating the <literal>InnoDB</literal> Tablespace</title>
-
- <para>
- Suppose that you have installed MySQL and have edited your option
- file so that it contains the necessary <literal>InnoDB</literal>
- configuration parameters. Before starting MySQL, you should verify
- that the directories you have specified for
- <literal>InnoDB</literal> data files and log files exist and that
- the MySQL server has access rights to those directories.
- <literal>InnoDB</literal> does not create directories, only files.
- Check also that you have enough disk space for the data and log
- files.
- </para>
-
- <para>
- It is best to run the MySQL server <command>mysqld</command> from
- the command prompt when you first start the server with
- <literal>InnoDB</literal> enabled, not from the
- <command>mysqld_safe</command> wrapper or as a Windows service.
- When you run from a command prompt you see what
- <command>mysqld</command> prints and what is happening. On Unix,
- just invoke <command>mysqld</command>. On Windows, use the
- <option>--console</option> option.
- </para>
-
- <para>
- When you start the MySQL server after initially configuring
- <literal>InnoDB</literal> in your option file,
- <literal>InnoDB</literal> creates your data files and log files,
- and prints something like this:
- </para>
-
-<programlisting>
-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
-</programlisting>
-
- <para>
- At this point <literal>InnoDB</literal> has initialized its
- tablespace and log files. You can connect to the MySQL server with
- the usual MySQL client programs like <command>mysql</command>.
- When you shut down the MySQL server with <command>mysqladmin
- shutdown</command>, the output is like this:
- </para>
-
-<programlisting>
-010321 18:33:34 mysqld: Normal shutdown
-010321 18:33:34 mysqld: Shutdown Complete
-InnoDB: Starting shutdown...
-InnoDB: Shutdown completed
-</programlisting>
-
- <para>
- You can look at the data file and log directories and you see the
- files created there. When MySQL is started again, the data files
- and log files have been created already, so the output is much
- briefer:
- </para>
-
-<programlisting>
-InnoDB: Started
-mysqld: ready for connections
-</programlisting>
-
- <para>
- If you add the <literal>innodb_file_per_table</literal> option to
- <filename>my.cnf</filename>, <literal>InnoDB</literal> stores each
- table in its own <filename>.ibd</filename> file in the same MySQL
- database directory where the <filename>.frm</filename> file is
- created. See <xref linkend="multiple-tablespaces"/>.
- </para>
-
- <section id="error-creating-innodb">
-
- <title>Dealing with <literal>InnoDB</literal> Initialization Problems</title>
-
- <para>
- If <literal>InnoDB</literal> prints an operating system error
- during a file operation, usually the problem has one of the
- following causes:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- You did not create the <literal>InnoDB</literal> data file
- directory or the <literal>InnoDB</literal> log directory.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqld</command> does not have access rights to
- create files in those directories.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqld</command> cannot read the proper
- <filename>my.cnf</filename> or <filename>my.ini</filename>
- option file, and consequently does not see the options that
- you specified.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The disk is full or a disk quota is exceeded.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You have created a subdirectory whose name is equal to a
- data file that you specified, so the name cannot be used as
- a filename.
- </para>
- </listitem>
-
- <listitem>
- <para>
- There is a syntax error in the
- <literal>innodb_data_home_dir</literal> or
- <literal>innodb_data_file_path</literal> value.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- If something goes wrong when <literal>InnoDB</literal> attempts
- to initialize its tablespace or its log files, you should delete
- all files created by <literal>InnoDB</literal>. This means all
- <filename>ibdata</filename> files and all
- <filename>ib_logfile</filename> files. In case you have already
- created some <literal>InnoDB</literal> tables, delete the
- corresponding <filename>.frm</filename> files for these tables
- (and any <filename>.ibd</filename> files if you are using
- multiple tablespaces) from the MySQL database directories as
- well. Then you can try the <literal>InnoDB</literal> database
- creation again. It is best to start the MySQL server from a
- command prompt so that you see what is happening.
- </para>
-
- </section>
-
- </section>
-
<section id="using-innodb-tables">
<title>Creating and Using <literal>InnoDB</literal> Tables</title>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r12285 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-6.0 | paul.dubois | 4 Nov |
