Need help?

Our experts have had an average response time of 13.52 minutes in October 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Binary logging error when using AWS DMS with Aurora MySQL

by | Aug 6, 2021

Stuck with binary logging error with AWS DMS while using Aurora MySQL? We can help you!

Here, at Bobcares, we often receive similar requests from our customers as a part of our AWS Support Services.

Today, let’s see how our Support engineers resolve these binary logging errors with AWS DMS.

 

Binary logging error with AWS DMS

 
We will receive the following error message if binary logging is not enabled on the source Aurora MySQL DB writer instance while running an AWS DMS task with Aurora MySQL:

Error Code [10001]: Binary logging must be enabled for the MySQL server
I: System var 'log_bin' = 'OFF'

We must enable binary logging on the source Aurora MySQL DB writer instance to use CDC with an AWS DMS task.

Also, make sure to use the writer instance because reader instances are not supported as a source for CDC operations.
 

How to fix binary logging errors

 
Now let’s see how our Support Engineers fix these binary logging errors.

At first, we have to identify the writer instance and then connect the writer instance with AWS DMS.

Then to confirm that binary logging is enabled, connect to the source Aurora cluster writer instance by using the cluster endpoint.

The command will return as follows:

mysql> show global variables like "log_bin";
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| log_bin | OFF |
+---------------+-------+

Here, the parameter log_bin is set to OFF. That means binary logging is disabled. Then we have to check and confirm the Aurora cluster’s binlog_format parameter is set to ROW. If it isn’t set to ROW, then set this parameter to enable binary logging.

Also, make sure to reboot the instance after the changes come into effect.

After setting the parameter binlog_format, we have to confirm that binary logging is enabled by connecting to the Aurora instance:

mysql> show global variables like "log_bin";
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| log_bin | ON |
+---------------+-------+

After that, make sure that we are using the cluster writer endpoint with AWS DMS, then restart the task.

[Need help to resolve AWS-related errors? We’d be happy to assist]
 

Conclusion

 
To conclude, today we saw how our Support Techs resolve binary logging errors with AWS DMS while using Aurora MySQL.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Reviews

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF