Error Codes

This document describes error codes you may encounter when operating CloudBase MySQL Database and their solutions.

Business Error Codes

Business error codes identify business logic errors that occur when the CloudBase platform processes MySQL database operations.

Error Code	Error Message	Description	Solution
AuthFailure.DataSourceOperationAuthFailure	Permission denied. Please check permissions in the permission module.	Permission denied, insufficient database operation permissions	Go to CloudBase Platform/MySQL Database/Permission Management to check and configure permissions
AuthFailure.SetOwnerNotAllowed	Setting user identifier field is not allowed.	Setting user identifier field _openid is not allowed	Remove explicit assignment operations to the _openid field, which is automatically managed by the system
AuthFailure.PermissionNotConfigured	Permission not configured. Please configure proper permissions in the permission module.	Data access permission not configured	Go to CloudBase Platform/MySQL Database/Permission Management to configure corresponding permission rules
AuthFailure.AuthError	Permission error.	Permission verification failed, usually due to missing system-dependent _openid field in custom table	Confirm that the table structure includes the _openid field (VARCHAR type), or disable permission verification
FailedOperation.EmptyDatabaseEndpoint	Database endpoint is empty.	Database connection information is empty	Check if the database instance is started normally and confirm if the connection configuration is correct
FailedOperation.DatabaseConnectError	Failed to establish database connection.	Database connection failed	Check network connection, database instance status, and if username/password are correct
FailedOperation.DatabaseExecSqlError	Execute sql error.	SQL execution failed, please refer to the "MySQL Native Error Codes" section for detailed error information	View complete error information and troubleshoot according to MySQL error codes
FailedOperation.DatabaseSchemaError	Database schema error.	Database schema metadata information is abnormal	Check if the table structure definition is correct, contact customer service for technical support if necessary
FailedOperation.DatabaseBuildSqlError	Build sql error.	SQL construction failed, possibly due to incorrect request parameters or missing metadata information	Check if the request parameter format is correct, contact customer service for technical support if necessary
FailedOperation.DatabaseDataProcessError	Process data error.	Data processing failed	Check if the data format meets requirements, contact customer service for technical support if necessary
ResourceNotFound.InstanceNotFound	Database instance not found.	Database instance does not exist	Confirm if the instance ID is correct, or go to the console to create a new instance
ResourceNotFound.SchemaNotFound	Database schema not found.	Database schema does not exist	Confirm if the database name is correct, or go to the console to create a database
ResourceNotFound.TableNotFound	Table not found.	Data table does not exist	Confirm if the table name is correct, or go to the console to create a data table
UnsupportedOperation.TooManyTables	Number of tables exceeds the limit.	Number of data tables exceeds the limit	Delete unnecessary tables, or contact customer service to apply for expansion
InvalidParameter.ResponseUnacceptableSingleError	Response does not meet the requirement for a single record.	Response data does not meet single record format requirements	Check the Accept parameter setting in the request header to ensure it matches the query result

MySQL Native Error Codes

When the business error code is FailedOperation.DatabaseExecSqlError, the error details will include the native error code returned by the MySQL database. You can determine the error type based on the error code range and consult the MySQL official documentation for detailed explanations.

Error Code Classification Rules

MySQL error codes are classified into the following categories by numerical range:

Server Error

Error Code Range: 1000-1999, 3000-5000+

Error Characteristics: Issues at the database engine, query optimizer, or storage engine level

Typical Example:

Error 1054 (42S22): Unknown column 'username' in 'field list'

Troubleshooting Approach:

• Check if SQL statement syntax is correct
• Confirm if table structure, field names, indexes, etc. exist
• Check if data types match

Client Error

Error Code Range: 2000-2999

Error Characteristics: Issues at the client driver, connection library, or network level

Typical Example:

Error 2003 (HY000): Can't connect to MySQL server on '192.168.1.100'

Troubleshooting Approach:

• Check if network connection is normal
• Confirm if database service is started
• Check firewall and security group configuration

Global Error

Error Code Range: 1-999

Error Characteristics: System-level generic errors

Typical Example:

Error 13 (HY000): Can't settle log file (OS errno 13 - Permission denied)

Troubleshooting Approach:

• Check file system permissions
• Confirm if disk space is sufficient
• Check system resource usage

CynosDB Error

Error Code Range: 9000-9999

Error Characteristics: Tencent Cloud CynosDB product-specific errors

Typical Example:

Error 9449 (08S01): CynosDB serverless instance is resuming, please try connecting again

Error Code Documentation CynosDB Error Code Reference

Official Documentation Reference

Depending on the error code type, you can consult the following MySQL official documentation:

Server Error

MySQL Version	Official Documentation Link
MySQL 8.0	Server Error Reference
MySQL 5.7	Server Error Reference

Client Error

MySQL Version	Official Documentation Link
MySQL 8.0	Client Error Reference
MySQL 5.7	Client Error Reference

Global Error

MySQL Version	Official Documentation Link
MySQL 8.0	Global Error Reference
MySQL 5.7	Global Error Reference

💡 Tip

• When encountering errors, it is recommended to first record the complete error information (including error code, SQLSTATE, and error description)
• Quickly determine the source of the problem (server-side vs client-side) based on the error code range
• Consult the official documentation for the corresponding version to get detailed error explanations and solution suggestions
• If the problem cannot be resolved on your own, you can contact Technical Support for help