MySQL Service Won't Start due to Corrupted Binary Logs
(Doc ID 2250859.1)
Last updated on SEPTEMBER 04, 2024
Applies to:
MySQL Server - Version 5.5 and laterInformation in this document applies to any platform.
Symptoms
On : 5.5 version, Options and Configuration
When attempting to start the MySQL service,
the following error occurs.
ERROR
-----------------------
170330 16:01:33 [ERROR] Binlog has bad magic number; It's not a binary log file that can be used by this version of MySQL
170330 16:01:33 [ERROR] Can't init tc log
170330 16:01:33 [ERROR] Aborting
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Shut down MySQL Server
2. Edit one of the binary logs and change some of the first few bytes
3. Attempt to restart the service
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot start the MySQL service.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |