MariaDB ERROR Code 1274
MySQL SQL State HY000
ER_SLAVE_IGNORED_SSL_PARAMS
SSL parameters in CHANGE MASTER are ignored because this MariaDB slave was compiled without SSL support; they can be used later if MariaDB slave with SSL is started
MariaDB ERROR Code 1275
MySQL SQL State HY000
ER_SERVER_IS_IN_SECURE_AUTH_MODE
Server is running in –secure-auth mode, but ‘%s’@’%s’ has a password in the old format; please change the password to the new format
MariaDB ERROR Code 1276
MySQL SQL State HY000
ER_WARN_FIELD_RESOLVED
Field or reference ‘%s%s%s%s%s’ of SELECT #%d was resolved in SELECT #%d

MariaDB ERROR Code 1277
MySQL SQL State HY000
ER_BAD_SLAVE_UNTIL_COND
Incorrect parameter or combination of parameters for START SLAVE UNTIL
MariaDB ERROR Code 1278
MySQL SQL State HY000
ER_MISSING_SKIP_SLAVE
It is recommended to use –skip-slave-start when doing step-by-step replication with START SLAVE UNTIL; otherwise, you will get problems if you get an unexpected slave’s mysqld restart
MariaDB ERROR Code 1279
MySQL SQL State HY000
ER_UNTIL_COND_IGNORED
SQL thread is not to be started so UNTIL options are ignored
MariaDB ERROR Code 1280
MySQL SQL State 42000
ER_WRONG_NAME_FOR_INDEX
Incorrect index name ‘%s’

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1271 to 1280 which performing certain operations against MySQL or MariaDB.

What are MYSQL/MariaDB Errors?

MySQL and MariaDB programs have access to several types of common error information when the server returns an error.

The MYSQL/MariaDB message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:MySQL error code: Call mysql_errno()SQLSTATE value: Call mysql_sqlstate()Error message: Call mysql_error()

Hope this was helpful.

Thanks,SQLServerF1 Team
Information about MYSQL and MariaDB Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

With codeplex shutting down, we have moved SQL Nexus to github with a new release (6.0). Now both Pssdiag/SQLDiag manager and SQL Nexus are on github. Where to get it As you navigate to SQL Nexus, you can download code and released binary files. If you choose to download binary files, you can go to...

SQL Server : large RAM and DB Checkpointing Hi everyone, This post’s purpose is to establish a summary of the specific behaviors with relation to DB Checkpoint that may happen within SQL Server when running with a large quantity of allocated memory and when applicable, how to best address them. SQL Server 2016 improves...

Recently we got an inquiry from a customer who received the following message in errorlog and wanted to know why. [INFO] HkDatabaseTryAcquireUserMemory(): Database ID: [7]. Out of user memory quota: requested = 131200; available = 74641; quota = 34359738368; operation = 1. This is my first time to see this error. As usual, I relied...

Recently I assisted on a customer issue where customer wasn’t able to alter a memory optimized table with the following error Msg 41317, Level 16, State 3, Procedure ddl, Line 4 [Batch Start Line 35]A user transaction that accesses memory optimized tables or natively compiled modules cannot access more than one user database or databases...

In a previous blog, I talked about memory optimized table consumes memory until end of the batch. In this blog, I want to make you aware of cardinality estimate of memory optimized table as we have had customers who called in for clarifications. By default memory optimized table variable behaves the same way as...

I worked on an interesting issue today where a user couldn’t restore a backup. Here is what this customer did: backed up a database from an on-premises server (2008 R2) copied the file to an Azure VM tried to restore the backup on the Azure VM (2008 R2 with exact same build#) But he got...

Recently, I looked an In-Memory OLTP issue with Principal Software Engineer Bob Dorr who is still my office neighbor. After restoring a database that had just one memory optimized table, we dropped the table. Even without any memory optimized tables,number of checkpoint files keep going up every time we issue a checkpoint. For a while,...

In this blog Added per-operator level performance stats for Query Processing, Senior PM in QP talks about extending operator level performance stats. They include stats related to reads, CPU and elapse time. These are very helpful to track down query performance issues. We worked on recent case where we put ActualElapsedms in a good...

In blog “Importance of choosing correct bucket count of hash indexes on a memory optimized table”, I talked about encountering performance issues with incorrect sized bucket count. I was actually investigating an out of memory issues with the following error. Msg 701, Level 17, State 103, Line 11There is insufficient system memory in resource pool...

I was working with a customer to troubleshoot memory optimized table issues. In this scenario, our customer uses a memory optimized table variable. He put 1 million rows of data into the table variable and then process it. Based on what he said, I tried to come up with a repro to see if...