List Of Few MySQL Error

1000 -SQLSTATE: HY000 (ER_HASHCHK) hashchk
1001 -SQLSTATE: HY000 (ER_NISAMCHK) isamchk
1002 -SQLSTATE: HY000 (ER_NO) NO
1003 -SQLSTATE: HY000 (ER_YES) YES
1004 -SQLSTATE: HY000 (ER_CANT_CREATE_FILE) Can’t create file ‘%s’ (errno: %d)
1005 -SQLSTATE: HY000 (ER_CANT_CREATE_TABLE) Can’t create table ‘%s’ (errno: %d)
1006 -SQLSTATE: HY000 (ER_CANT_CREATE_DB) Can’t create database ‘%s’ (errno: %d)
1007 -SQLSTATE: HY000 (ER_DB_CREATE_EXISTS) Can’t create database ‘%s’; database exists
1008 -SQLSTATE: HY000 (ER_DB_DROP_EXISTS) Can’t drop database ‘%s’; database doesn’t exist
1009 -SQLSTATE: HY000 (ER_DB_DROP_DELETE) Error dropping database (can’t delete ‘%s’, errno: %d)
1010 -SQLSTATE: HY000 (ER_DB_DROP_RMDIR) Error dropping database (can’t rmdir ‘%s’, errno: %d)
1011 -SQLSTATE: HY000 (ER_CANT_DELETE_FILE) Error on delete of ‘%s’ (errno: %d)
1012 -SQLSTATE: HY000 (ER_CANT_FIND_SYSTEM_REC) Can’t read record in system table
1013 -SQLSTATE: HY000 (ER_CANT_GET_STAT) Can’t get status of ‘%s’ (errno: %d)
1014 -SQLSTATE: HY000 (ER_CANT_GET_WD) Can’t get working directory (errno: %d)
1015 -SQLSTATE: HY000 (ER_CANT_LOCK) Can’t lock file (errno: %d)
1016 -SQLSTATE: HY000 (ER_CANT_OPEN_FILE) Can’t open file: ‘%s’ (errno: %d)
1017 -SQLSTATE: HY000 (ER_FILE_NOT_FOUND) Can’t find file: ‘%s’ (errno: %d)
1018 -SQLSTATE: HY000 (ER_CANT_READ_DIR) Can’t read dir of ‘%s’ (errno: %d)
1019 -SQLSTATE: HY000 (ER_CANT_SET_WD) Can’t change dir to ‘%s’ (errno: %d)
1020 -SQLSTATE: HY000 (ER_CHECKREAD) Record has changed since last read in table ‘%s’
1021 -SQLSTATE: HY000 (ER_DISK_FULL) Disk full (%s); waiting for someone to free some space…
1022 - SQLSTATE: 23000 (ER_DUP_KEY) Can’t write; duplicate key in table ‘%s’
1023 -SQLSTATE: HY000 (ER_ERROR_ON_CLOSE) Error on close of ‘%s’ (errno: %d)
1024 -SQLSTATE: HY000 (ER_ERROR_ON_READ) Error reading file ‘%s’ (errno: %d)
1025 -SQLSTATE: HY000 (ER_ERROR_ON_RENAME) Error on rename of ‘%s’ to ‘%s’ (errno: %d)
1026 -SQLSTATE: HY000 (ER_ERROR_ON_WRITE) Error writing file ‘%s’ (errno: %d)
1027 -SQLSTATE: HY000 (ER_FILE_USED) ‘%s’ is locked against change
1028 -SQLSTATE: HY000 (ER_FILSORT_ABORT) Sort aborted
1029 -SQLSTATE: HY000 (ER_FORM_NOT_FOUND) View ‘%s’ doesn’t exist for ‘%s’
1030 -SQLSTATE: HY000 (ER_GET_ERRNO) Got error %d from storage engine
1031 -SQLSTATE: HY000 (ER_ILLEGAL_HA) Table storage engine for ‘%s’ doesn’t have this option
1032 -SQLSTATE: HY000 (ER_KEY_NOT_FOUND) Can’t find record in ‘%s’
1033 SQLSTATE: HY000 (ER_NOT_FORM_FILE) Incorrect information in file: ‘%s’
1034 -SQLSTATE: HY000 (ER_NOT_KEYFILE) Incorrect key file for table ‘%s’; try to repair it
1035 -SQLSTATE: HY000 (ER_OLD_KEYFILE) Old key file for table ‘%s’; repair it!
1036 -SQLSTATE: HY000 (ER_OPEN_AS_READONLY) Table ‘%s’ is read only
1037 -SQLSTATE: HY001 (ER_OUTOFMEMORY) Out of memory; restart server and try again (needed %d bytes)
1038 -SQLSTATE: HY001 (ER_OUT_OF_SORTMEMORY) Out of sort memory; increase server sort buffer size
1039 -SQLSTATE: HY000 (ER_UNEXPECTED_EOF) Unexpected EOF found when reading file ‘%s’ (errno: %d)
1040 -SQLSTATE: 08004 (ER_CON_COUNT_ERROR) Too many connections
1041 -SQLSTATE: HY000 (ER_OUT_OF_RESOURCES) Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use ‘ulimit’ to allow mysqld to use more memory or you can add more swap space
1042 -SQLSTATE: 08S01 (ER_BAD_HOST_ERROR) Can’t get hostname for your address
1043 -SQLSTATE: 08S01 (ER_HANDSHAKE_ERROR) Bad handshake
1044 -SQLSTATE: 42000 (ER_DBACCESS_DENIED_ERROR) Access denied for user ‘%s’@'%s’ to database ‘%s’
1045 -SQLSTATE: 28000 (ER_ACCESS_DENIED_ERROR) Access denied for user ‘%s’@'%s’ (using password: %s)
1046 -SQLSTATE: 3D000 (ER_NO_DB_ERROR) No database selected
1047 -SQLSTATE: 08S01 (ER_UNKNOWN_COM_ERROR) Unknown command
1048 -SQLSTATE: 23000 (ER_BAD_NULL_ERROR) Column ‘%s’ cannot be null
1049 -SQLSTATE: 42000 (ER_BAD_DB_ERROR) Unknown database ‘%s’
1050 -SQLSTATE: 42S01 (ER_TABLE_EXISTS_ERROR) Table ‘%s’ already exists
1051 -SQLSTATE: 42S02 (ER_BAD_TABLE_ERROR) Unknown table ‘%s’
1052 -SQLSTATE: 23000 (ER_NON_UNIQ_ERROR) Column ‘%s’ in %s is ambiguous
1053 -SQLSTATE: 08S01 (ER_SERVER_SHUTDOWN) Server shutdown in progress
1054 -SQLSTATE: 42S22 (ER_BAD_FIELD_ERROR) Unknown column ‘%s’ in ‘%s’
1055 -SQLSTATE: 42000 (ER_WRONG_FIELD_WITH_GROUP) ‘%s’ isn’t in GROUP BY
1056 -SQLSTATE: 42000 (ER_WRONG_GROUP_FIELD) Can’t group on ‘%s’
1057 -SQLSTATE: 42000 (ER_WRONG_SUM_SELECT) Statement has sum functions and columns in same statement
1058 -SQLSTATE: 21S01 (ER_WRONG_VALUE_COUNT) Column count doesn’t match value count
1059 -SQLSTATE: 42000 (ER_TOO_LONG_IDENT) Identifier name ‘%s’ is too long
1060 -SQLSTATE: 42S21 (ER_DUP_FIELDNAME) Duplicate column name ‘%s’
1061 -SQLSTATE: 42000 (ER_DUP_KEYNAME) Duplicate key name ‘%s’
1062 -SQLSTATE: 23000 (ER_DUP_ENTRY) Duplicate entry ‘%s’ for key %d
1063 -SQLSTATE: 42000 (ER_WRONG_FIELD_SPEC) Incorrect column specifier for column ‘%s’
1064 -SQLSTATE: 42000 (ER_PARSE_ERROR) %s near ‘%s’ at line %d
1065 -SQLSTATE: HY000 (ER_EMPTY_QUERY) Query was empty
1066 -SQLSTATE: 42000 (ER_NONUNIQ_TABLE) Not unique table/alias: ‘%s’
1067 -SQLSTATE: 42000 (ER_INVALID_DEFAULT) Invalid default value for ‘%s’
1068 -SQLSTATE: 42000 (ER_MULTIPLE_PRI_KEY) Multiple primary key defined
1069 -SQLSTATE: 42000 (ER_TOO_MANY_KEYS) Too many keys specified; max %d keys allowed
1070 -SQLSTATE: 42000 (ER_TOO_MANY_KEY_PARTS) Too many key parts specified; max %d parts allowed
1071 -SQLSTATE: 42000 (ER_TOO_LONG_KEY) Specified key was too long; max key length is %d bytes
1072 -SQLSTATE: 42000 (ER_KEY_COLUMN_DOES_NOT_EXITS) Key column ‘%s’ doesn’t exist in table
1073 -SQLSTATE: 42000 (ER_BLOB_USED_AS_KEY) BLOB column ‘%s’ can’t be used in key specification with the used table type
1074 -SQLSTATE: 42000 (ER_TOO_BIG_FIELDLENGTH) Column length too big for column ‘%s’ (max = %d); use BLOB instead
1075 -SQLSTATE: 42000 (ER_WRONG_AUTO_KEY) Incorrect table definition; there can be only one auto column and it must be defined as a key
1076 -SQLSTATE: HY000 (ER_READY) %s: ready for connections. Version: ‘%s’ socket: ‘%s’ port: %d
1077 -SQLSTATE: HY000 (ER_NORMAL_SHUTDOWN) %s: Normal shutdown
1078 -SQLSTATE: HY000 (ER_GOT_SIGNAL) %s: Got signal %d. Aborting!
1079 -SQLSTATE: HY000 (ER_SHUTDOWN_COMPLETE) %s: Shutdown complete
1080 -SQLSTATE: 08S01 (ER_FORCING_CLOSE) %s: Forcing close of thread %ld user: ‘%s’
1081 -SQLSTATE: 08S01 (ER_IPSOCK_ERROR) Can’t create IP socket
1082 -SQLSTATE: 42S12 (ER_NO_SUCH_INDEX) Table ‘%s’ has no index like the one used in CREATE INDEX; recreate the table
1083 -SQLSTATE: 42000 (ER_WRONG_FIELD_TERMINATORS) Field separator argument is not what is expected; check the manual
1084 -SQLSTATE: 42000 (ER_BLOBS_AND_NO_TERMINATED) You can’t use fixed rowlength with BLOBs; please use ‘fields terminated by’
1085 -SQLSTATE: HY000 (ER_TEXTFILE_NOT_READABLE) The file ‘%s’ must be in the database directory or be readable by all
1086 -SQLSTATE: HY000 (ER_FILE_EXISTS_ERROR) File ‘%s’ already exists
1087 -SQLSTATE: HY000 (ER_LOAD_INFO) Records: %ld Deleted: %ld Skipped: %ld Warnings: %ld
1088 -SQLSTATE: HY000 (ER_ALTER_INFO) Records: %ld Duplicates: %ld
1089 -SQLSTATE: HY000 (ER_WRONG_SUB_KEY) Incorrect sub part key; the used key part isn’t a string, the used length is longer than the key part, or the storage engine doesn’t support unique sub keys
1090 - SQLSTATE: 42000 (ER_CANT_REMOVE_ALL_FIELDS) You can’t delete all columns with ALTER TABLE; use DROP TABLE instead
1091 -SQLSTATE: 42000 (ER_CANT_DROP_FIELD_OR_KEY) Can’t DROP ‘%s’; check that column/key exists
1092 -SQLSTATE: HY000 (ER_INSERT_INFO) Records: %ld Duplicates: %ld Warnings: %ld
1093 -SQLSTATE: HY000 (ER_UPDATE_TABLE_USED) You can’t specify target table ‘%s’ for update in FROM clause
1094 -SQLSTATE: HY000 (ER_NO_SUCH_THREAD) Unknown thread id: %lu
1095 -SQLSTATE: HY000 (ER_KILL_DENIED_ERROR) You are not owner of thread %lu
1096 -SQLSTATE: HY000 (ER_NO_TABLES_USED) No tables used
1097 -SQLSTATE: HY000 (ER_TOO_BIG_SET) Too many strings for column %s and SET
1098 -SQLSTATE: HY000 (ER_NO_UNIQUE_LOGFILE) Can’t generate a unique log-filename %s.(1-999)
1099 -SQLSTATE: HY000 (ER_TABLE_NOT_LOCKED_FOR_WRITE) Table ‘%s’ was locked with a READ lock and can’t be updated
1100 -SQLSTATE: HY000 (ER_TABLE_NOT_LOCKED) Table ‘%s’ was not locked with LOCK TABLES

Killing INSERT … SELECT Can Corrupt MySQL Table on MyISAM

The MySQL INSERT … SELECT command allows you to insert several rows into a table from various tables. But at times, when you kill the command on MyISAM, you observe that the table gets corrupt. Such type of errors usually occur with large data sets. When you run CHECK TABLE command to check the table for consistency, it reports that the table is unusable as it is corrupt. The table thus corrupted should be restored from backup or you can alternatively use MySQL repair tools that are competent products to allow safe repair of database and its objects.

To illustrate the same, consider that you use a table with name 'a' on MyISAM storage engine'. You execute INSERT … SELECT command and kill it while it is running. After this, you use CHECK TABLE command to perform the sanity check of the table and come across errros similar to:

Table Op Msg_type Msg_text
test.a check warning Table is marked as crashed and last repair failed
test.a check warning Size of indexfile is: 1337344 Should be: 1024
test.a check error Record-count is not ok; is 92522 Should be: 0
test.a check warning Found 92522 key parts. Should be: 0
test.a check error Partition pMin returned error
test.a check error Corrupt

Cause

The error indicates that the table has got corrupt. When you kill the INSERT … SELECT statement, which is being applied on the table with indexes and contains large amount of data, it might get corrupt. This occurs when we disable the indexes for the purpose of fast insert. After the bulk_insert operation is completed, indexes are tried to be re-enabled. While MySQL is re-enabling the indexes, killing the query results into aborting the repair table operation and hence the table gets corrupt.

Solution

Use any of these methods to repair the corrupted MyISAM table:

· You can use the following command to repair:

REPAIR TABLE table_name

Where, table_name is the name of corrupted table

· Use MySQL Recovery tools for achieving best and safe repair results. MySQL Recovery tools are fully-competent database recovery utilities built with powerful scanning technology and easy to use interface.

Tips to resolve Run Time Error 3800 message in MS Access 2002

Tables in MS Access database are the primary storage components to store user's records. While this database component is easy to open, there are possibilities that when you attempt to open the tables, an error message pops up. This error message does not allow you to access any records saved in the tables. In such situations, an ideal way is to restore the tables from an updated backup. But if in case, no backup is available or backup falls short to restore the records, then you will need to use advanced access repair software.

As a practical example, you encounter any of the below error messages when you attempt to view records saved in Finance table:

“Error 3800: AOIndex is not an index in this table.”

Or

“Run-Time Error '3058' Index or
Primary key cannot contain a null value”

You encounter the same error message every time you attempt to open the Finance table. Furthermore, the data stored in the Finance table becomes inaccessible after the above error message appears.

Cause:

The above error message primarily occurs due to damage or corruption of index in system table.

Resolution:

To resolve the above run time error message, you will need to repair the Finance table by using an inbuilt repair utility named “Compact and Repair”. Below are the steps that enable you to repair the table:

1. You will need to select Database utilities on the Tools menu, and then click Compact and Repair Database.
2. Next, click the database in the ‘Database to Compact From’ dialog box, and then click Compact.
3. Lastly, you will need to select a correct folder location for the new file in the ‘Compact Database Into’ dialog box, type a unique name for the file, and then click on Save.

But, if in case the above utility falls short to resolve your problem, Access Repair software comes to rescue. Such access database repair utilities incorporate advanced scanning algorithms to repair corrupted or damaged Access database components. These tools are built with highly graphical user-interface and easily understandable even by a home user.

How to Resolve SQL Server Error 8961?

The rows of a SQL Server table are divided into partitions that are numbered from 1 to n. By default all rows are consisted in a single partition, however one can also define the size of partition. All rows of partition are stored as a B-tree or heap structure. The actual data is stored in leaf nodes of leaves (called text data node), while rest other nodes (called text index nodes) are used to store index values for leaf node. But sometimes, you observe table inconsistencies because of mismatch between one or more child nodes and their corresponding parent nodes. As a result, you receive table corruption errors. Such situations need to be resolved using DBCC CHECKDB command, backup or commercial SQL recovery utilities.

You might encounter the following error with your SQL Server database table:

Server: Msg 8961 , Level 23, State

Table error: Object ID O_ID. The text, ntext, or image node at page P_ID1, slot S_ID1, text ID TEXT_ID does not match its reference from page P_ID2, slot S_ID2.

Where, ‘state_number’ might be 1, 2 or 4.

Cause

SQL Server displays error 8961 when it finds mismatch between child node and parent node and corruption in a text object. Specifically, you might infer the exact cause of error message by the ‘state_number’ it is displaying:

State 1: It occurs when timestamps in node and parent don’t match with each other.

State 2: The child node is text data node and has greater size as what is supposed by its parent. It might also occur if the child node is text index node and has different size as what is supposed by its parent.

State 4: The child node is actually a text index node, but its parent supposes it to be a text data node or vice-versa. This might also occur due if the level of child node is different from what is supposed by its parent.

Solution

In order to solve such problems, you should follow these steps:

• Check your system for possible hardware problems

• Restore database from clean backup, if available

• Execute DBCC CHECKDB command without using repair clause if no valid backup is available. Again run DBCC CHECKDB but with the repair clause suggested by the previous check

• Running DBCC CHECKDB causes data loss. Thus, for safe SQL Repair, use third-party database repair applications. These SQL Recovery tools are built with powerful technology to safely scan and repair a damaged SQL Server database.

For More Information Visit: http://sqlrecoverydatabase.blogspot.com/2009_07_01_archive.html

Troubleshooting Sql Server Error 2579

SQL Server database pages are 8 KB in size, each designated with a specific ID. The application uses extents as the basic unit to allocate space for tables and indexes. If these structures suffer any sort of corruption related concerns, you can run DBCC CHECKDB command to detect it. You can deduce the exact cause of the problem from SQL Server log that records all the results of running the command. However, to restore the corrupted table, you will need to use your current backup. But at times, you find issues while restoring from backup because it doesn't exist in valid state. You need to use SQL repair software in such problems to repair the corrupt database and its objects.


Consider an instance, you run DBCC CHECKDB command to check database consistency and come across the below error message in SQL Server error log:

“Table error: Extent P_ID object ID O_ID, index ID I_ID is beyond the range of this database.”

This entry is marked with error ID 2579 and severity level 16.

Cause

Each page ID is referenced in the form- fileId:pageInFile. In the error message above, P_ID is the ID of the affected page in the table. Error 2579 occurs if pageinfile of the extent is found to be greater than the expected physical size of the file with ID fileID specified in the database. The error indicates that the extent has been allocated in an IAM page for the indicated index ID or object.

Solution

Following are the solutions to fix the above problem:

Such errors might be frequent due to hardware related problems. So, you should diagnose the system for the same and remove or replace the faulty hardware.
Restore the database table from backup.
Execute DBCC CHECKDB command to determine the repair clause that should be run to repair the database table. Next, run the suggested repair clause with DBCC CHECKDB command
If applying the above measures is not feasible, you need to use third-party SQL Recovery software. SQL Repair products are commercial tools embedded with high-end scanning algorithms and graphically rich user interface to allow safe and efficient database repair.

SQL Recovery is a premier and popular tool to repair damaged SQL databases that is supportive to SQL Server 2008, 2005 and 2000. With self-descriptive and exceptionally realistic interface, advanced repair options and non-destructive design, it is a fully-featured SQL Recovery utility to repair all database objects. The software is compatible with Windows Vista, XP, 2003, 2000 and NT.