Comments for idError

Comment on Error: 1255 – SQLSTATE: HY000 ER_SLAVE_WAS_NOT_RUNNING by admin

admin — Thu, 07 May 2009 00:45:49 +0000

There are cases when slave threads have successfully started and then later stop, because of inability to connect to the master or read binary logs, etc. In such cases, you will not be given a warning that it has stopped. You may add an UNTIL clause to specify that the slave should start and run until the SQL thread
reaches a given point.

Comment on Error: 1253 – SQLSTATE: 42000 ER_COLLATION_CHARSET_MISMATCH by admin

admin — Thu, 07 May 2009 00:45:29 +0000

This error occurs when you try to use a collation that is not supported for a particular character set. Each character set defines it own collations. Example as follows:
COLLATION ‘utf8_bin’ is not valid for CHARACTER SET ‘binary’
Collation ‘utf8_bin’ is available for character set ‘utf8′ and not for ‘binary’.
Check your database, table and column DDL for setting the CHARSET. Note that it can be set on the database level, the table level and the
column level.

Comment on Error: 1252 – SQLSTATE: 42000 ER_SPATIAL_CANT_HAVE_NULL by admin

admin — Thu, 07 May 2009 00:45:13 +0000

Spatial indexes are created using SPATIAL INDEX statement and are available only for MyISAM tables. Index columns must be NOT NULL and column prefix lenghts are not allowed (in MySQL 5.1). See Spatial Extensions for details at http://dev.mysql.com/doc/refman/5.1/en/spatial-extensions.html.

Comment on Error: 1248 – SQLSTATE: 42000 ER_DERIVED_MUST_HAVE_ALIAS by admin

admin — Thu, 07 May 2009 00:44:53 +0000

Add an alias for each derived table and make sure that you add the alias just after the FROM clause, outside the parentheses () and make sure to use JOIN condition as necessary.

Comment on Error: 1243 – SQLSTATE: HY000 ER_UNKNOWN_STMT_HANDLER by admin

admin — Thu, 07 May 2009 00:44:27 +0000

The following are some instances of this error:
Unknown prepared statement handler (prepared_stmt) given to DEALLOCATE
Unknown prepared statement handler (prepared_stmt) given to EXECUTE
Prepared statements are local to the session. MySQL automatically deallocates these statements when the session is closed. For a detailed workaround, follow these steps:
1. Open a database connection
2. Run the PREPARE statement
3. Set the values of the variable and EXECUTE the query
5. DEALLOCATE the prepared statement
6. Close the database connection

Comment on Error: 1242 – SQLSTATE: 21000 ER_SUBQUERY_NO_1_ROW by admin

admin — Thu, 07 May 2009 00:44:11 +0000

This error occurs for statements having a subquery. Check this example:
SELECT * FROM table1 WHERE column1 = (SELECT column1 FROM table2);
If the subquery in the abover statement returns more than 1 row, an error will be triggered. To fix, you may rewrite the query as follows:
SELECT * FROM table1 WHERE column1 = ANY (SELECT column1 FROM table2);

Comment on Error: 1241 – SQLSTATE: 21000 ER_OPERAND_COLUMNS by admin

admin — Thu, 07 May 2009 00:43:55 +0000

This error can occur when there is issue with your table structure. Check the following:
a. Make sure that when you use IN, your subquery contains only 1 field
b. If you are using LIMIT in the subquery, check if it is allowed in the version of MySQL that you use
c. Use AND instead of COMMAS in your WHERE condition

Comment on Error: 1232 – SQLSTATE: 42000 ER_WRONG_TYPE_FOR_VAR by admin

admin — Thu, 07 May 2009 00:43:28 +0000

An example of this error is when you try to specify the following argument in my.cnf:
max_allowed_packet=16M
Since max_allowed_packet is a numeric dynamic variable which can only take a numeric value and 16M is not a numeric value in SQL context, it resulted to error.
You may check a list of dynamic system variables and their types at http://dev.mysql.com/doc/refman/5.0/en/dynamic-system-variables.html.

Comment on Error: 1229 – SQLSTATE: HY000 ER_GLOBAL_VARIABLE by admin

admin — Thu, 07 May 2009 00:43:06 +0000

MySQL produces this error when GLOBAL (or @@global) is not specified when setting a global variable. To fix, precede the global variable’s name by GLOBAL or @@global.

Comment on Error: 1228 – SQLSTATE: HY000 ER_LOCAL_VARIABLE by admin

admin — Thu, 07 May 2009 00:42:51 +0000

MySQL produces this error when SET GLOBAL is used with a session variable that can only be used with SET SESSION. To be able to set a SESSION variable to the GLOBAL value, use the DEFAULT keyword. The following is the statement that can be used to the set the session value of max_join_size to the global value:
SET max_join_size=DEFAULT;
Just note that not all system variables can be set to DEFAULT.