Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.3K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 546 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 442 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Is it able to remove data\ibdata1 file from mysql 5.6.30 archive install zip
Hi,
I would like to know why the file ibdata1 is preset in the "data" folder in mysql server archive version 5.6.30 (windows 64 bit, enterprise version).
I removed this file , only keep the folder of "mysql" and "performance_schema", try to start mysqld for the first time, mysqld can still start successfully, and I see a new ibdata1 is generated.
So I have a question, since this file can be generated automatically, why do you need to preset it in data folder?
Best Answer
-
It is the InnoDB table space.
The system tablespace is the storage area for the
InnoDBdata dictionary, the double write buffer, the change buffer, and undo logs. It may also contain table and index data if tables are created in the system table space rather than file-per-table or general tablespaces.The system tablespace can have one or more data files.
Dave Stokes
MySQL Community Manager
Answers
-
It is the InnoDB table space.
The system tablespace is the storage area for the
InnoDBdata dictionary, the double write buffer, the change buffer, and undo logs. It may also contain table and index data if tables are created in the system table space rather than file-per-table or general tablespaces.The system tablespace can have one or more data files.
Dave Stokes
MySQL Community Manager
-
Hi,
I mean the newly downloaded archive version, In the case of mysqld starts for the first time, is ibdata1 file still useful? even without it I can start mysqld without any problem and a new one will be generated.
I just want to know if this file must exists in the nonintall zip archive? For mysqld , when it starts for the first time, it seems this file is not essential and could be generated, so I think probably this file could be removed from nonintall zip archive.
-
Yes, the sever will create the ibdata1 if it does not exist. I am not sure which zip file you are using but the packager may have put it in there to a) save time, b) preload data (example databases), and/or c) just because it was there when they created the zip file.
If it really worries you then delete it.
Dave Stokes
MySQL Community Manager