Feed Aggregator

1450 - 1499 1550 - 1599

• Error: 1500 SQLSTATE: HY000 (ER_SUBPARTITION_ERROR)

  Message: It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning

• Error: 1501 SQLSTATE: HY000 (ER_CANT_CREATE_HANDLER_FILE)

  Message: Failed to create specific handler file

• Error: 1502 SQLSTATE: HY000 (ER_BLOB_FIELD_IN_PART_FUNC_ERROR)

  Message: A BLOB field is not allowed in partition function

• Error: 1503 SQLSTATE: HY000 (ER_UNIQUE_KEY_NEED_ALL_FIELDS_IN_PF)

  Message: A %s must include all columns in the table’s partitioning function

• Error: 1504 SQLSTATE: HY000 (ER_NO_PARTS_ERROR)

  Message: Number of %s = 0 is not an allowed value

• Error: 1505 SQLSTATE: HY000 (ER_PARTITION_MGMT_ON_NONPARTITIONED)

  Message: Partition management on a not partitioned table is not possible

• Error: 1506 SQLSTATE: HY000 (ER_FOREIGN_KEY_ON_PARTITIONED)

  Message: Foreign key clause is not yet supported in conjunction with partitioning

• Error: 1507 SQLSTATE: HY000 (ER_DROP_PARTITION_NON_EXISTENT) …

1400 - 1449 1500 - 1549

• Error: 1450 SQLSTATE: HY000 (ER_FORBID_SCHEMA_CHANGE)

  Message: Changing schema from ‘%s’ to ‘%s’ is not allowed.

• Error: 1451 SQLSTATE: 23000 (ER_ROW_IS_REFERENCED_2)

  Message: Cannot delete or update a parent row: a foreign key constraint fails (%s)

• Error: 1452 SQLSTATE: 23000 (ER_NO_REFERENCED_ROW_2)

  Message: Cannot add or update a child row: a foreign key constraint fails (%s)

• Error: 1453 SQLSTATE: 42000 (ER_SP_BAD_VAR_SHADOW)

  Message: Variable ‘%s’ must be quoted with
  ...<br>, or renamed

• Error: 1454 SQLSTATE: HY000 (ER_TRG_NO_DEFINER)

  Message: No definer attribute for trigger ‘%s’.’%s’. The trigger will be activated under the authorization of the invoker, which may have insufficient privileges. Please recreate the trigger.

• Error: 1455 SQLSTATE: HY000 (ER_OLD_FILE_FORMAT)

  Message: ‘%s’ has an old format, you should re-create the ‘%s’ object(s)

• Error: 1456 SQLSTATE: HY000 ( …

1350 - 1399 1450 - 1499

• Error: 1400 SQLSTATE: XAE09 (ER_XAER_OUTSIDE)

  Message: XAER_OUTSIDE: Some work is done outside global transaction

• Error: 1401 SQLSTATE: XAE03 (ER_XAER_RMERR)

  Message: XAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistency

• Error: 1402 SQLSTATE: XA100 (ER_XA_RBROLLBACK)

  Message: XA_RBROLLBACK: Transaction branch was rolled back

• Error: 1403 SQLSTATE: 42000 (ER_NONEXISTING_PROC_GRANT)

  Message: There is no such grant defined for user ‘%s’ on host ‘%s’ on routine ‘%s’

• Error: 1404 SQLSTATE: HY000 (ER_PROC_AUTO_GRANT_FAIL)

  Message: Failed to grant EXECUTE and ALTER ROUTINE privileges

• Error: 1405 SQLSTATE: HY000 (ER_PROC_AUTO_REVOKE_FAIL)

  Message: Failed to revoke all privileges to dropped routine

• Error: 1406 SQLSTATE: 22001 (ER_DATA_TOO_LONG)

  Message: Data too long for column ‘%s’ at row %ld

• Error: 1407 SQLSTATE: 42000 (ER_SP_BAD_SQLSTATE)

  Message: Bad SQLSTATE: ‘%s’ …

1300 - 1349 1400 - 1449

• Error: 1350 SQLSTATE: HY000 (ER_VIEW_SELECT_CLAUSE)

  Message: View’s SELECT contains a ‘%s’ clause

• Error: 1351 SQLSTATE: HY000 (ER_VIEW_SELECT_VARIABLE)

  Message: View’s SELECT contains a variable or parameter

• Error: 1352 SQLSTATE: HY000 (ER_VIEW_SELECT_TMPTABLE)

  Message: View’s SELECT refers to a temporary table ‘%s’

• Error: 1353 SQLSTATE: HY000 (ER_VIEW_WRONG_LIST)

  Message: View’s SELECT and view’s field list have different column counts

• Error: 1354 SQLSTATE: HY000 (ER_WARN_VIEW_MERGE)

  Message: View merge algorithm can’t be used here for now (assumed undefined algorithm)

• Error: 1355 SQLSTATE: HY000 (ER_WARN_VIEW_WITHOUT_KEY)

  Message: View being updated does not have complete key of underlying table in it

• Error: 1356 SQLSTATE: HY000 (ER_VIEW_INVALID)

  Message: View ‘%s.%s’ references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them

• Error: 1357 …

1250 - 1299 1350 - 1399

• Error: 1300 SQLSTATE: HY000 (ER_INVALID_CHARACTER_STRING)

  Message: Invalid %s character string: ‘%s’

• Error: 1301 SQLSTATE: HY000 (ER_WARN_ALLOWED_PACKET_OVERFLOWED)

  Message: Result of %s() was larger than max_allowed_packet (%ld) - truncated

• Error: 1302 SQLSTATE: HY000 (ER_CONFLICTING_DECLARATIONS)

  Message: Conflicting declarations: ‘%s%s’ and ‘%s%s’

• Error: 1303 SQLSTATE: 2F003 (ER_SP_NO_RECURSIVE_CREATE)

  Message: Can’t create a %s from within another stored routine

• Error: 1304 SQLSTATE: 42000 (ER_SP_ALREADY_EXISTS)

  Message: %s %s already exists

• Error: 1305 SQLSTATE: 42000 (ER_SP_DOES_NOT_EXIST)

  Message: %s %s does not exist

• Error: 1306 SQLSTATE: HY000 (ER_SP_DROP_FAILED)

  Message: Failed to DROP %s %s

• Error: 1307 SQLSTATE: HY000 (ER_SP_STORE_FAILED)

  Message: Failed to CREATE %s %s

• Error: 1308 SQLSTATE: 42000 (ER_SP_LILABEL_MISMATCH)

  Message: %s with no matching label: %s

• Error: 1309 SQLSTATE: 42000 ( …

1200 - 1249 1300 - 1349

• Error: 1250 SQLSTATE: 42000 (ER_TABLENAME_NOT_ALLOWED_HERE)

  Message: Table ‘%s’ from one of the SELECTs cannot be used in %s

• Error: 1251 SQLSTATE: 08004 (ER_NOT_SUPPORTED_AUTH_MODE)

  Message: Client does not support authentication protocol requested by server; consider upgrading MySQL client

• Error: 1252 SQLSTATE: 42000 (ER_SPATIAL_CANT_HAVE_NULL)

  Message: All parts of a SPATIAL index must be NOT NULL

• Error: 1253 SQLSTATE: 42000 (ER_COLLATION_CHARSET_MISMATCH)

  Message: COLLATION ‘%s’ is not valid for CHARACTER SET ‘%s’

• Error: 1254 SQLSTATE: HY000 (ER_SLAVE_WAS_RUNNING)

  Message: Slave is already running

• Error: 1255 SQLSTATE: HY000 (ER_SLAVE_WAS_NOT_RUNNING)

  Message: Slave already has been stopped

• Error: 1256 SQLSTATE: HY000 (ER_TOO_BIG_FOR_UNCOMPRESS)

  Message: Uncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)

• Error: 1257 SQLSTATE: HY000 (ER_ZLIB_Z_MEM_ERROR)

  Message: …

1150 - 1199 1250 - 1299

  Error: 1200 SQLSTATE: HY000 (ER_BAD_SLAVE)
  Message: The server is not configured as slave; fix in config file or with CHANGE MASTER TO

How does the MySQL error message look like?

  Error: 1201 SQLSTATE: HY000 (ER_MASTER_INFO)
  Message: Could not initialize master info structure; more error messages can be found in the MySQL error log

How does the MySQL error message look like?

  Error: 1202 SQLSTATE: HY000 (ER_SLAVE_THREAD)
  Message: Could not create slave thread; check system resources

How does the MySQL error message look like?

  Error: 1203 SQLSTATE: 42000 (ER_TOO_MANY_USER_CONNECTIONS)
  Message: User %s already has more than 'max_user_connections' active connections

How does the MySQL error message look like?

  Error: 1204 SQLSTATE: HY000 (ER_SET_CONSTANTS_ONLY)
  Message: You may only use constant expressions with SET

How does the MySQL error message look like?

  Error: 1205 SQLSTATE: HY000 (ER_LOCK_WAIT_TIMEOUT)
  Message: Lock wait timeout …

1100 - 1149 1200 - 1249

• Error: 1150 SQLSTATE: HY000 (ER_DELAYED_CANT_CHANGE_LOCK)

  Message: Delayed insert thread couldn’t get requested lock for table %s

• Error: 1151 SQLSTATE: HY000 (ER_TOO_MANY_DELAYED_THREADS)

  Message: Too many delayed threads in use

• Error: 1152 SQLSTATE: 08S01 (ER_ABORTING_CONNECTION)

  Message: Aborted connection %ld to db: ‘%s’ user: ‘%s’ (%s)

  Error: 1153 SQLSTATE: 08S01 (ER_NET_PACKET_TOO_LARGE)
  Message: Got a packet bigger than 'max_allowed_packet' bytes

How does the MySQL error message look like?

  mysql --user=root --max_allowed_packet=128M test < test_dump.sql
  ERROR 1153 (08S01) at line 87: Got a packet bigger than 'max_allowed_packet' bytes

What does the MySQL error message mean?

This MySQL error message means that max_allowed_packet parameter either on client or on server side is too small for the data to be processed.

When does this MySQL error message happen?

This error typically happens when you have set the max_allowed_packet …

1050 - 1099 1150 - 1199

• Error: 1100 SQLSTATE: HY000 (ER_TABLE_NOT_LOCKED)

  Message: Table ‘%s’ was not locked with LOCK TABLES

• Error: 1101 SQLSTATE: 42000 (ER_BLOB_CANT_HAVE_DEFAULT)

  Message: BLOB/TEXT column ‘%s’ can’t have a default value

• Error: 1102 SQLSTATE: 42000 (ER_WRONG_DB_NAME)

  Message: Incorrect database name ‘%s’

• Error: 1103 SQLSTATE: 42000 (ER_WRONG_TABLE_NAME)

  Message: Incorrect table name ‘%s’

• Error: 1104 SQLSTATE: 42000 (ER_TOO_BIG_SELECT)

  Message: The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET SQL_MAX_JOIN_SIZE=# if the SELECT is okay

• Error: 1105 SQLSTATE: HY000 (ER_UNKNOWN_ERROR)

  Message: Unknown error

• Error: 1106 SQLSTATE: 42000 (ER_UNKNOWN_PROCEDURE)

  Message: Unknown procedure ‘%s’

• Error: 1107 SQLSTATE: 42000 (ER_WRONG_PARAMCOUNT_TO_PROCEDURE)

  Message: Incorrect parameter count to procedure ‘%s’

• Error: 1108 SQLSTATE: HY000 ( …

1000 - 1049 1100 - 1149

Error: 1050 SQLSTATE: 42S01 (ER_TABLE_EXISTS_ERROR)

Message: Table ‘%s’ already exists

• Error: 1051 SQLSTATE: 42S02 (ER_BAD_TABLE_ERROR)

  Message: Unknown table ‘%s’

• Error: 1052 SQLSTATE: 23000 (ER_NON_UNIQ_ERROR)

  Message: Column ‘%s’ in %s is ambiguous

• Error: 1053 SQLSTATE: 08S01 (ER_SERVER_SHUTDOWN)

  Message: Server shutdown in progress

• Error: 1054 SQLSTATE: 42S22 (ER_BAD_FIELD_ERROR)

  Message: Unknown column ‘%s’ in ‘%s’

• Error: 1055 SQLSTATE: 42000 (ER_WRONG_FIELD_WITH_GROUP)

  Message: ‘%s’ isn’t in GROUP BY

• Error: 1056 SQLSTATE: 42000 (ER_WRONG_GROUP_FIELD)

  Message: Can’t group on ‘%s’

• Error: 1057 SQLSTATE: 42000 (ER_WRONG_SUM_SELECT)

  Message: Statement has sum functions and columns in same statement

• Error: 1058 SQLSTATE: 21S01 (ER_WRONG_VALUE_COUNT)

  Message: Column count doesn’t match value count

• Error: 1059 SQLSTATE: 42000 (ER_TOO_LONG_IDENT)

  Message: …

1050 - 1099

• Error: 1000 SQLSTATE: HY000 (ER_HASHCHK)

  Message: hashchk

• Error: 1001 SQLSTATE: HY000 (ER_NISAMCHK)

  Message: isamchk

• Error: 1002 SQLSTATE: HY000 (ER_NO)

  Message: NO

• Error: 1003 SQLSTATE: HY000 (ER_YES)

  Message: YES

• Error: 1004 SQLSTATE: HY000 (ER_CANT_CREATE_FILE)

  Message: Can’t create file ‘%s’ (errno: %d)

• Error: 1005 SQLSTATE: HY000 (ER_CANT_CREATE_TABLE)

  Message: Can’t create table ‘%s’ (errno: %d)

  Error: 1006 SQLSTATE: HY000 (ER_CANT_CREATE_DB)
  Message: Can't create database '%s' (errno: %d)

How does the MySQL error message look like?

  mysql> CREATE DATABASE test;
  ERROR 1006 (HY000): Can't create database 'test' (errno: 13)

What does the MySQL error message mean?

The MySQL Server (mysqld process) can, for whatever reason, NOT create a schema/database.

Additional information you can get as follows:

  shell> perror 13
  OS error code  13:  Permission denied

When does this MySQL error message happen?

This MySQL error …

Just a general rule with error messages: Usually they are not as good as they could be. But nevertheless read them carefully. Most of the time they tell you what you need to know…

And an other wisdom: Errors are really errors and they have to be solved. Warnings are warnings and you should investigate if they appear. Do not ignore both of them unless you have clearly understood what you are doing.

With MySQL:

mysql> SHOW WARNINGS

is often your friend! Further sources to find the problems are:

mysql> SHOW SLAVE STATUS<br>G
shell> perror <error_number>
shell> perror --ndb <error_number>

And the MySQL Error log.

MySQL Server Error Codes and Messages

1. MySQL Errors 1000 - 1049
2. MySQL Errors 1050 - 1099
3. MySQL Errors 1100 - 1149
4. MySQL Errors 1150 - 1199
5. MySQL Errors 1200 - 1249
6. MySQL Errors 1250 - 1299
7. MySQL Errors 1300 - 1349
8. MySQL Errors 1350 - 1399
9. MySQL Errors 1400 - 1449
10. MySQL Errors 1450 - 1499
11. MySQL Errors 1500 - 1549
12. MySQL Errors 1550 - 1599
13. MySQL Errors 1600 - 1649 …

FromDual is a support partner of MariaDB plc, Codership Oy and Oracle Corporation. This gives us the opportunity to offer you customized enterprise support subscriptions for your mission-critical MariaDB, Galera or MySQL databases for all three vendors.

Alternatively, we can offer you our remote DBA services (without SLA) or our MariaDB, Galera and MySQL trainings.

MariaDB and MariaDB Cluster Support Subscriptions

• MariaDB Enterprise support subscription: 7x24 support subscription, duration: 1 to 3 years, unlimited number of support cases, subscription per instance, including MaxScale, Connectors and MariaDB Enterprise Server.
• MariaDB Enterprise (Galera) Cluster Support Subscription: 7x24 support subscription, duration: 1 to 3 years, unlimited support cases, subscription per cluster, including, MaxScale, Connectors and MariaDB Enterprise Cluster.
• MariaDB Enterprise Column Store Support Subscription: 7x24 support subscription, duration: 1 to 3 years, unlimited support cases, subscription per instance/module, …

We dug some further with this problem of too big rows. The results you can find below.

Further discussion we had about PBXT MEMORY tables partitioned:

Q: Is there a good case where partitioned PBXT MEMORY tables could make sense?

A: To have some partitions on disk and other in memory could be useful.

Unfortunately MySQL (up to 5.6.1) and MariaDB (up to 5.2.3) do not support mixing different Storage Engines for a partitioned table yet:

ERROR 1497 (HY000): The mix of handlers in the partitions is not allowed in this version of MySQL

Lit: CREATE TABLE

Hi Stewart,

Thanks for your comment. Paul made some similar conclusions:

The problem could be that the fixed length record component is too large. PBXT tries to estimate the average row length of a table when it is created. It then sets the fixed length record component to the estimated average row length value.

If the estimate is not good, you can set it explicitly by setting AVG_ROW_LENGTH.

Optimizing the average row length is explained in my talk.

For the moment you can just try AVG_ROW_LENGTH = 12. This will place all the data in the extended record component, which optimizes memory usage.

So I have to dive into this again and do some more investigations.

Cheers, Oli

Normal PBXT makes guesses as to what rows should be stored fixed format and what varsized.

It is possible that for memory tables, this guess is wrong.

I forget the syntax to change it, but it is possible.

perhaps these default guesses should be different for in memory tables too.

Introduction

In his presentation about PBXT at the DOAG Conference 2010 Paul McCullagh was speaking about memory resident PBXT tables. They will be available in version 1.1 of the PBXT Storage Engine Plugin. Memory resident PBXT tables should have similar characteristics like normal MySQL MEMORY</span> tables</a>. But in addition to the MEMORY tables they are transactional and can handle BLOB</span> and TEXT attributes.

An alternative to this feature would be the MySQL dynamic heap row patches provided by eBay and hosted at code.google.com.

In the following blog article we go through the installation of the PBXT Storage Engine Plugin version 1.1 and how to use PBXT `MEMORY resident tables.

Download

I have not found binaries yet. So we have to compile them ourself. Download is pretty simple:

shell> bzr branch lp:pbxt/1.1

Build

To build the pluggable PBXT Storage Engine we have to do the typical 3 steps: `configure; make; make install. But there are some pitfalls to circumvent:

shell> …

At the DOAG 2010 we found that there are already a lot of Plugins etc. for MySQL available. Therefor it will be a good time to start with a collection of Plugins, UDF’s etc. available.

Because we have done already a collection of MySQL Storage Engines earlier please look there form more information.

Hi Baomin Wang,

After some thinking an talking to some colleagues I found the answer:

When MySQL Cluster writes LCP’s it first writes LCP 1, then LCP 2. After LCP 2 it OVERwrites the LCP 1 again and then overwrites LCP 2 again and so on…

This assures that we have always ONE complete and good LCP from where we can recover in case of a complete Cluster crash.

When we would have only 1 LCP file this cannot be assured.

Regards, Oli