<< previous page   --   table of contents   --   next page >>
| | | | | | | |
  • Return to Table of Contents
    • Table of Contents
    1. General Information
    2. MySQL Installation
    3. Tutorial Introduction
    4. Database Administration
    5. MySQL Optimisation
    6. MySQL Language Reference
    7. MySQL Table Types
    8. MySQL APIs
    9. Extending MySQL
    Chapter 7:  MySQL Table Types 513 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 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 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 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 data les and logs directories and you will see the les created. The log directory will also contain a small le named `ib_arch_log_0000000000'.  That le resulted from the database creation, after which InnoDB switched o log archiving.  When MySQL is again started, the output will be like the following: ~/mysqlm/sql > mysqld InnoDB: Started mysqld: ready for connections 7.5.3.1  If Something Goes Wrong in Database Creation If InnoDB prints an operating system error in a le operation, usually the problem is one of the following:    You did not create InnoDB data or log directories.    `mysqld' does not have the rights to create les in those directories.    `mysqld' does not read the right `my.cnf' or `my.ini' le, and consequently does not see the options you speci ed.    The disk is full or a disk quota is exceeded.    You have created a subdirectory whose name is equal to a data le you speci ed.    There is a syntax error in innodb_data_home_dir or innodb_data_file_path. If something goes wrong in an InnoDB database creation, you should delete all les created by InnoDB. This means all data les, all log les, the small archived log le, and in the case you already did create some InnoDB tables, delete also the corresponding `.frm' les for these tables from the MySQL database directories.  Then you can try the InnoDB database creation again.
     

    Customer Support CentreMySQL Reference Manual

    Web Hosting Services
    UNIX WEB HOSTING
    MERCHANT ACCOUNTS
    DEDICATED SERVERS
    E-COMMERCE HOSTING
    SUPPORT & FAQ's
    TERMS OF USE
    Domain Services
    DOMAIN
    REGISTRATION
    MANAGE
    YOUR ACCOUNT
    SUPPORT & FAQ's
    TERMS OF USE
    Corporate Info
    ABOUT US
    OUR NETWORK
    CONTACT US
    SITE MAP
    UNIX Web Hosting | Merchant Accounts | Dedicated Hosting | E-Commerce Hosting
    Domain Registration | About Us | Our Network | Contact Us | Site Map
    Our Partners
    Copyright © 2002 Dyntex Group, Inc. All Rights Reserved
  • Return to Table of Contents
    		•
  • Back to top
    • Web Hosting: Manuals & FAQ's
    1. Unix-Based Web Hosting
    2. Unix Dedicated Servers
    3. Windows Dedicated Servers
    4. CuteFTP User’s Guide
    5. CuteHTML User’s Guide
    6. WS_FTP Pro User's Guide
    7. Miva Order User's Guide
    8. Miva Merchant User's Guide