Oracle 5.0 Reference Manual page 1253

On Windows, start
window.
When you start the MySQL server after initially configuring
your data files and log files, and prints something like this:
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
At this point
with the usual MySQL client programs like mysql. When you shut down the MySQL server with
mysqladmin
010321 18:33:34
010321 18:33:34
InnoDB: Starting shutdown...
InnoDB: Shutdown completed
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:
InnoDB: Started
mysqld: ready for connections
If you add the
in its own
.ibd
Section 14.2.1.1, "Using Per-Table
14.2.1.4. Dealing with
If prints an operating system error during a file operation, usually the problem has one of the
InnoDB
following causes:
• You did not create the
• does not have access rights to create files in those directories.
mysqld
• cannot read the proper
mysqld
options that you specified.
• The disk is full or a disk quota is exceeded.
• You have created a subdirectory whose name is equal to a data file that you specified, so the name
cannot be used as a file name.
• There is a syntax error in the
innodb_data_file_path
InnoDB
with the
mysqld
has initialized its tablespace and log files. You can connect to the MySQL server
InnoDB
shutdown, the output is like this:
mysqld: Normal shutdown
mysqld: Shutdown Complete
innodb_file_per_table
file in the same MySQL database directory where the
Tablespaces".
Initialization Problems
InnoDB
data file directory or the
InnoDB
my.cnf
innodb_data_home_dir
[1240]
Configuration
[404] option to direct the output to the console
--console
InnoDB
[1241] option to my.cnf,
InnoDB
or option file, and consequently does not see the
my.ini
value.
1233
in your option file,
stores each table
InnoDB
file is created. See
.frm
log directory.
[1240] or
creates
InnoDB