Description:
Yesterday I created a table called Page.
Then I loaded the table with a data-file called Page.txt. The data file was huge having size of 25 GB. I used Load data infile command to load the records.
This load process went on for some hours and then it ended.
I checked the Page table using CHECK TABLE PAGE and status was Ok.
I was able to run some queries also on Page table.
After that i closed Mysqld server.
In the morning I again started Mysql server using the command
mysqld --defaults-file="G:\myproject\data\my.ini"
but could not connect to the server. I am getting error "Can't connect to MySQL server on '127.0.0.1' (10061)"
I changed the innodb_log_file_size to 100M
I check the Error log file and below is the error message
2014-04-25 18:51:33 5384 [Note] Plugin 'FEDERATED' is disabled.
2014-04-25 18:51:33 5384 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
2014-04-25 18:51:33 f0c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-04-25 18:51:33 5384 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-04-25 18:51:33 5384 [Note] InnoDB: The InnoDB memory heap is disabled
2014-04-25 18:51:33 5384 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-04-25 18:51:33 5384 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-04-25 18:51:33 5384 [Note] InnoDB: Not using CPU crc32 instructions
2014-04-25 18:51:33 5384 [Note] InnoDB: Initializing buffer pool, size = 156.0M
2014-04-25 18:51:33 5384 [Note] InnoDB: Completed initialization of buffer pool
2014-04-25 18:51:33 5384 [Note] InnoDB: Highest supported file format is Barracuda.
2014-04-25 18:51:33 5384 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2813636439
2014-04-25 18:51:33 5384 [Note] InnoDB: Database was not shutdown normally!
2014-04-25 18:51:33 5384 [Note] InnoDB: Starting crash recovery.
2014-04-25 18:51:33 5384 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-04-25 18:51:33 5384 [Note] InnoDB: Restoring possible half-written data pages
2014-04-25 18:51:33 5384 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2813636449
InnoDB: Last MySQL binlog file position 0 457513596, file name PRIYA-PC-bin.000106
2014-04-25 18:51:33 5384 [Warning] InnoDB: Resizing redo log from 2*3072 to 2*6400 pages, LSN=2813636449
2014-04-25 18:51:33 5384 [Warning] InnoDB: Starting to delete and rewrite log files.
2014-04-25 18:51:33 5384 [Note] InnoDB: Setting log file .\ib_logfile101 size to 100 MB
InnoDB: Progress in MB: 100
2014-04-25 18:51:34 5384 [Note] InnoDB: Setting log file .\ib_logfile1 size to 100 MB
InnoDB: Progress in MB: 100
2014-04-25 18:51:34 5384 [Note] InnoDB: Renaming log file .\ib_logfile101 to .\ib_logfile0
2014-04-25 18:51:34 5384 [Warning] InnoDB: New log files created, LSN=2813636449
2014-04-25 18:51:34 5384 [Note] InnoDB: 128 rollback segment(s) are active.
2014-04-25 18:51:34 5384 [Note] InnoDB: Waiting for purge to start
2014-04-25 18:51:34 5384 [Note] InnoDB: 5.6.16 started; log sequence number 2813636449
2014-04-25 18:51:34 5384 [Note] Recovering after a crash using PRIYA-PC-bin
************************************************************************
The Bin-logs in the data directory are from PRIYA-PC-bin.000001 uptil PRIYA-PC-bin.000107 (I dont know why it is not reading the last 107 log file)
Please help me to restore my database.
How to repeat:
Load a huge data file in a table and data file should be of 25 gb or more
After the load, shut-down mysql
Start mysql
Not able to establish connection to server.
