<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>databases on System Administration, Hosting, Cloud and technologies in between</title>
    <link>https://dmsimard.com/categories/databases/</link>
    <description>Recent content in databases on System Administration, Hosting, Cloud and technologies in between</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 02 Dec 2013 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://dmsimard.com/categories/databases/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Fixing MySQL Fatal Error 1236</title>
      <link>https://dmsimard.com/2013/12/02/fixing-mysql-fatal-error-1236/</link>
      <pubDate>Mon, 02 Dec 2013 00:00:00 +0000</pubDate>
      
      <guid>https://dmsimard.com/2013/12/02/fixing-mysql-fatal-error-1236/</guid>
      <description>It happens.
You have a Master -&amp;gt; Slave MySQL replication and your master crashes for a reason or another.
You&amp;rsquo;re worried about bringing the master back online as soon as possible.
When you finally get it back up, you notice the slave is stopped, complaining about a dreaded error that looks a bit like this:
The binlog file got corrupted when the master database server crashed.
Restoring a backup won&amp;rsquo;t save you, nor will re-importing the database.</description>
    </item>
    
  </channel>
</rss>