Error Message Elements •The server sends other error messages to client programs. These indicate issues pertaining only to a particular client. The MySQL client library takes errors received from the server and makes them available to the host client program. •Client-side error messages are generated from within the MySQL client library, usually involving problems communicating with the server. •This message produced during the startup process provides a status or progress indicator: Example server-side error messages written to the error log: 2018-10-28T13:01:32.735983Z 0 [Note] [MY-010303] [Server] Skipping generation of SSL certificates as options related to SSL are specified. 2018-10-02T03:20:39.410387Z 768 [ERROR] [MY-010045] [Server] Event Scheduler: [evtuser@localhost][myschema.e_daily] Unknown database ’mydb’ Example server-side error message sent to client programs, as displayed by the  mysql  client: •This message indicates an issue that requires DBA action: mysql>  SELECT * FROM no_such_table; ERROR 1146 (42S02): Table ’test.no_such_table’ doesn’t exist Example client-side error message originating from within the client library, as displayed by the  mysql client: shell>  mysql -h no-such-host ERROR 2005 (HY000): Unknown MySQL server host ’no-such-host’ (0) Whether an error originates from within the client library or is received from the server, a MySQL client program may respond in varying ways. As just illustrated, the client may display the error message so the user can take corrective measures. The client may instead internally attempt to resolve or retry a failed operation, or take other action. When an error occurs, error information includes several elements: an error code, SQLSTATE value, and message string. These elements have the following characteristics: Error Message Elements •Error code: This value is numeric. It is MySQL-specific and is not portable to other database systems. •The symbol for server error number  1146  is  ER_NO_SUCH_TABLE . •The symbol for client error number  2005  is  CR_UNKNOWN_HOST . Each error number has a corresponding symbolic value. Examples: The set of error codes used in error messages is partitioned into distinct ranges; see Error Code Ranges. Error codes are stable across General Availability (GA) releases of a given MySQL series. Before a series reaches GA status, new codes may still be under development and are subject to change. •SQLSTATE value: This value is a five-character string (for example,  ’42S02’ ). SQLSTATE values are taken from ANSI SQL and ODBC and are more standardized than the numeric error codes. The first two characters of an SQLSTATE value indicate the error class: 5282