Bug #78353 | Installation of MySQL 5.6.26 failed due to InnoDB erro | ||
---|---|---|---|
Submitted: | 7 Sep 2015 10:03 | Modified: | 7 Sep 2015 10:45 |
Reporter: | chao ma | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S3 (Non-critical) |
Version: | 5.6.26 | OS: | Windows (Win Server 2008 R2 64-bit) |
Assigned to: | CPU Architecture: | Any |
[7 Sep 2015 10:03]
chao ma
[7 Sep 2015 10:24]
Peter Laursen
Maybe this will help: https://msdn.microsoft.com/en-us/library/windows/desktop/ms681385(v=vs.85).aspx - on error 1455 ERROR_COMMITMENT_LIMIT 1455 (0x5AF) The paging file is too small for this operation to complete. So I think you should either increase the Windows page file or start MySQL with a smaller buffer. Is this machine running with no page file allocation at all, BTW? I know some people do that if they have a lot of RAM (like 32 GB or higher) in order to save disk space. As default Windows will allocate a page file of 1.5 * RAM (what dates back from the days when computers rarely had more than 500MB-1GB of RAM), but you can configure it as you want. My settings on a 32 GB RAM machine (running Win7) is 200 mb at startup allowing it to grow to 1 GB and ii have no such problem It may also simply be the case that your harddrive is almost full and cannot accomodate the page file as it grows. -- Peter -- not an Oracle/MySQL person.
[7 Sep 2015 10:41]
chao ma
I get it!Thank you for your help!! it is no page file allocation at all . I changed my virtual memory, and the service started successfully!
[7 Sep 2015 10:45]
chao ma
thank you very much again!