Error Codes

Updated on 2025-02-14 GMT+08:00

View PDF

If an error occurs during API calling, no result will be returned. The returned error code can be used to identify the failure cause. If an error occurs in API calling, HTTP status code 4xx or 5xx is returned. The response contains the specific error code and information. If you cannot locate the cause of an error, contact O&M personnel and provide the error code.

Error Response Body Format

If an error occurs during API calling, error code and error message will be displayed. The following shows an error response body:

{
    "error_msg": "Failed to import APIs in the swagger file to API Gateway.",
    "error_code": "lakeformation.00012001"
}

In the response message body, error_code is an error code, and error_msg provides information about the error.

Error Code Description

If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in Error Codes.

For details about LakeFormation error codes, see Table 1.

**Table 1** LakeFormation error codes
Status Code	Error Code	Error Message	Measure
500	00000001	Service error. Please try again later.	Try again later.
400	00000002	Unsupported permission type(s).	Check the entered permission type(s).
400	00000003	The entered content already exist(s).	Check duplicate items and reset them.
400	00000004	Exceeded the maximum number.	Delete unnecessary resources.
400	00000005	The resource not found.	Check whether the resources exist.
400	00000006	Empty list.	Check whether the list is empty.
400	00000007	Cannot be null.	Check whether the value is null.
400	00000008	Unsupported resource(s).	Check the name of resource.
400	00000009	Unsupported resource type(s).	Check the entered permission type.
400	00000010	Unsupported authorization entity type(s).	Check the entered authorization entity type.
400	00000011	The operation table is a non-partitioned table.	Check the entered table type.
400	00000012	Incorrect partition value.	Check whether the number and type of the entered partition key list of the table match those of the entered partition value list.
400	00000013	Incorrect column type(s).	Check whether the entered column type matches the type supported by the official website.
500	00000014	The signature certificate does not exist.	Check whether services on the management plane are available.
400	00000015	Invalid token.	Check whether the token is valid.
400	00000016	Insufficient permissions.	Check whether you have the required permissions.
400	00000017	Empty statistics.	Verify if the statistics are empty or if the statistics type is incorrectly set.
400	00000018	The referenced table information is incomplete when the foreign key is obtained.	To query foreign keys, enter the complete database and table names of the referenced table.
400	00000019	The query parameters cannot coexist.	Ensure that only one of the query parameters is set.
400	00000020	The operation feature is not supported currently.	The operation feature is not supported. Please look out for version updates.
400	00000021	The project to which the token belongs is inconsistent with the project ID in the request address.	Check whether the project ID is correct and whether the token belongs to the project.
400	00000022	The format of the request address is incorrect.	Enter a correct request address.
400	00000023	The token is missing.	Enter a token.
500	00000030	Invalid input parameter(s).	Check the input parameter(s).
400	00000031	Invalid object.	Check the object.
400	00000032	Invalid operation.	Check the operation.
400	00000033	Unknown database.	Check the database.
400	00000034	Unknown partition.	Check the partition.
400	00000035	Unknown table.	Check the table.
400	00000036	The metadata is abnormal.	Check the request.
400	00000037	A maximum of permission subjects are allowed.	Delete some authorizations.
400	00000038	Cluster server certificate will expire.	Replace the certificate and complete the upgrade in a timely manner.
400	00000039	Directory creation failure.	Check the path.
400	00000040	Function does not exist.	Check the function name.
400	00000041	Table filter condition field is invalid.	Modify the table filter field.
400	00000042	Location path is not supported.	Check the input path.
400	00000043	String has SQL injection risks.	Check the input string.
500	00000044	Failed to parse the LakeFormation Admin server certificate.	Rebuild the container.
400	00000045	Path already exists.	Select an empty path.
500	00000046	The process is being stopped.	Wait for the container to finish the restart process.
400	00000047	Failed to delete the catalog because it contains custom databases.	Delete all non-default databases in this catalog.
500	00000048	HiveMetaStore health check failed.	Check the HiveMetaStore service status.
500	00000049	Ranger health check failed.	Check the status of the Ranger service.
500	00000050	OBS health check failed.	Check whether the OBS service is normal and whether the AK/SK for calling OBS has expired.
500	00000051	Failed to create or update database metadata.	Check the SQL statement or database for errors or irregularities.
400	00000052	No default instance ID is configured in project by tenant.	Check whether the default instance ID of the tenant is configured.
400	00000053	Instance does not belong to tenant.	Check whether the instance ID is correct.
400	00000054	Column statistics cannot be created for partitioned tables.	Create or update statistics on the partition.
400	00000055	The data type for the column statistics does not align with that of the column.	Ensure that the data type of the column statistics is consistent with that of the table or partition column.
500	00000056	Protobuf decoding failed.	Reset the data.
500	00000057	The instance is not found.	Enter a correct instance ID.
400	00000058	Failed to collect the account ID during overload control.	Check the account information.
500	00000059	GaussDB health check failed.	Check the status of the GaussDB service.
500	00000060	Flow control is triggered.	Try again later.
400	00000061	Requests cannot be serialized when partitions are created.	Try again later.
400	00000062	Number of entered characters exceeded maximum.	Check the entered characters.
400	00000063	Failed to delete the catalog because it contains databases.	Delete all databases in this catalog.
500	00000064	Failed to delete data from the table.	Check the log stack information.
500	00000065	An error occurred during the aging process of the tables.	Check the data aging configuration.
500	00000066	Failed to execute SQL.	Check whether the syntax of the SQL file is correct.
500	00000067	The MD5 value of the file does not match that of the remote file.	Check whether the SQL file is modified.
400	00000068	The default database cannot be deleted.	Do not delete the default database.
400	00000069	The path cannot coincide .	Check the input path.
400	00000070	The path must be a subpath of the catalog storage location or database storage location list.	Check the input path.
400	00000071	The path must be the subpath of the database storage location or data table storage location list.	Check the input path.
400	00000072	The path must be the subpath of the database storage location or function storage location list.	Check the input path.
500	00000073	An error occurred during the aging process of instance.	Check the data aging configuration.
400	00000074	The path supports only parallel file systems.	Check whether the path is a parallel file system.
500	00000075	Failed to create the recycle bin.	Try again later.
500	00000076	Failed to delete the folder.	Try again later.
500	00000078	Failed to verify the IAM agency.	Check whether an IAM agency is created.
500	00000079	MySQL cannot use the value to process Boolean data.	Check the entered expression.
500	00000080	Incomplete expression.	Try again.
500	00000081	Unsupported data type(s).	Check the entered expression.
500	00000082	Failed to filter partition SQL statements.	Check the entered expression or view logs to locate the error cause.
500	00000083	The column name in the partition is incorrect.	Check the entered expression or view logs to locate the error cause.
500	00000084	Incorrect column type.	Check the entered expression or view logs to locate the error cause.
500	00000085	Failed to update the permission policy of a table or function.	Only table and function authorization are supported.
500	00000086	Failed to create the file in OBS.	Check the path and related permissions, or contact O&M personnel for assistance.
500	00000087	An I/O exception occurred when querying OBS.	Check the path or contact O&M personnel for assistance.
500	00000088	Failed to rename the file in OBS.	Check the path and permission, or contact O&M personnel for assistance.
500	00000089	Failed to obtain the terminal tenant credential.	Contact O&M personnel for assistance.
500	00000090	Failed to insert partition key-value pairs.	Contact O&M personnel for assistance.
500	00000091	Failed to insert partitions.	Contact O&M personnel for assistance.
500	00000092	Failed to update partition key-value pairs.	Contact O&M personnel for assistance.
500	00000093	Failed to update partitions.	Contact O&M personnel for assistance.
500	00000094	Failed to delete data from the partition.	Contact O&M personnel for assistance.
500	00000095	The partition does not support filtering.	Contact O&M personnel for assistance.
500	00000096	The partition name is empty or the format is incorrect.	Check the entered partition name.
500	00000097	Unknown column data type(s).	Check whether the data type matches any of the following: BINARYSTATS, BOOLEANSTATS, DATESTATS, DECIMALSTATS, DOUBLESTATS, LONGSTATS, or STRINGSTATS.
500	00000098	The role relationship type is abnormal.	Check whether the role relationship type matches either GROUP or USER.
500	00000099	Column data type is not supported.	Ensure that the column data type is String or Timestamp.
500	00000100	Failed to obtain the local IP address.	Contact O&M personnel for assistance.
500	00000101	Failed to generate a unique UID because the timestamp bits are used up.	Try again later.
500	00000102	The Hive service is abnormal.	Check status of the Hive service.
400	00000103	Metadata cannot be written unless a new branch is created or the current version is set to the latest version.	Create a branch or set the current version to the latest version.
500	00000104	Ranger does not support resource type.	Check whether the resource type is DATABASE, TABLE, or FUNCTION.
500	00000105	Duplicate Ranger policy.	Check Ranger policies.
500	00000106	Ranger permission type cannot be converted to the LakeCat permission type.	Check the Ranger permission type.
500	00000107	Non-Hive default catalogs cannot be transformed into Ranger source data resources.	Transform the default Hive catalog into Ranger resources.
500	00000108	Range permission type is not supported.	Check whether the Ranger policy matches any of the following: ALL, SELECT, UPDATE, CREATE, DROP, ALTER, READ, WRITE, INDEX, or NULL.
500	00000109	Failed to convert the Ranger authorization entity to an authorization subject domain model.	Check the entered content.
500	00000110	The name of Ranger resource type is not defined.	Define the name of the Ranger resource type.
500	00000111	Failed to obtain the Ranger resource type.	Check the entered content.
500	00000112	The Ranger resource type cannot be converted to the LakeCat resource type.	Check the entered content.
500	00000113	The entered pagination parameter is incorrect.	Check the entered content.
500	00000114	Failed to obtain the permission label.	Contact O&M personnel for assistance.
500	00000115	Failed to add the permission label.	Contact O&M personnel for assistance.
500	00000116	Failed to remove the permission label.	Contact O&M personnel for assistance.
500	00000117	Failed to set the permission label.	Contact O&M personnel for assistance.
500	00000118	Failed to obtain the file permission.	Contact O&M personnel for assistance.
403/500	00000119	IAM parsing failure.	Contact O&M personnel for assistance.
500	00000120	Failed to convert domain model to the metadata resource type.	Check the metadata type.
500	00000121	Failed to obtain the catalog.	Locate the error cause by checking logs.
500	00000122	Table column restriction type is not supported.	Check whether the restriction type for the table column matches any of the following: FOREIGN_KEY, PRIMARY_KEY, CHECK_CSTR, UNIQUE_CSTR, DEFAULT_CSTR, or NOT_NULL_CSTR.
400	00000123	Failed to establish the data source connection.	Check whether the data source parameters are correctly set.
400	00000124	The path does not exist in the OBS parallel file system.	Check whether the path exists in the OBS parallel file system.
400	00000125	Catalog is not empty in OBS.	Check whether the catalog is empty. If it is empty, clear it and try again.
500	00000126	Failed to query bucket.	Try again later.
400	00000127	Unsupported column name(s).	Check whether the column name meets the table format requirements.
400	00000128	An exception occurred during default database authorization.	Check whether the URI of the default database is the same as that of the corresponding catalog to avoid permission expansion.
500	00000129	Failed to execute asynchronous task.	Try again later.
400	00000130	Duplicate external ID(s).	Check whether the entered external ID is duplicate.
400	00000131	The external ID cannot be changed.	Check whether the external ID is changed.
403	00000132	Failed to request this method because the instance has been frozen.	Contact O&M personnel for assistance.
403	00000133	Failed to request this method because the user is frozen.	Contact O&M personnel for assistance.
403	00000134	Failed to request this method because the user is restricted.	Check the account balance or contact O&M personnel for assistance.
500	00000135	Failed to update the bucket lifecycle.	Try again later.
400	00000136	Metadata restoration failed because the metadata has not been deleted.	Check the entered metadata.
403	00000137	The current instance does not support metadata restoration.	Try another instance.
400	00000138	Metadata with the same name exists.	Remove any redundant metadata that has identical names and try again.
400	00000139	Metadata restoration failed because the metadata is being deleted.	Wait until the metadata is deleted and try again.
400	00000140	Metadata deletion failed because the metadata is being restored.	Wait until the metadata restoration is complete and try again.
500	00000141	Failed to restore the folder.	Try again later.
400	00000142	Upper-level metadata is deleted.	Restore the upper-level metadata and try again.
400	00000143	Attempting to restore the metadata with the same name repeatedly is not allowed.	Wait until the restoration for metadata with the same name is complete and try again.
500	00000144	Failed to aggregate the metadata quantity of instance schema.	Wait for the scheduled task to retry.
500	00000145	Failed to update column statistics.	Contact O&M personnel for assistance.
400	00000146	The path of the virtual view chart must be null.	Set the path to null and try again.
500	00000147	External service is abnormal.	Contact O&M personnel for assistance.
400	00000148	The entered obligation information is invalid.	Check whether the entered obligation information contains special characters, such as semicolons (;).
500	00000149	Failed to obtain the OBS bucket.	Contact O&M personnel for assistance.
500	00000150	Failed to create the OBS bucket.	Contact O&M personnel for assistance.
400	00000151	The table lock already exists.	Release the table lock and lock the table again.
404	00000152	The table lock does not exist.	Check the entered lock ID.
400	00000153	Failed to lock the table.	Try again later.
500	00000154	Failed to clear the table lock.	Contact O&M personnel for assistance.
400	00010002	The instance is not in the running state and cannot process the request.	Send the request when the instance is running.
400/404	00010003	The instance does not exist.	Use a correct instance ID.
400	00010004	The entered bucket does not exist.	Check the entered bucket.
400	00010005	The entered protocol version does not exist.	Check the entered protocol version.
400	00010006	The protocol version cannot be empty.	Check the entered protocol version.
400	00010007	The resource clearing task ID does not exist.	Check the task ID.
400	00010008	Duplicate instance name.	Enter another instance name.
400	00010009	No resources found.	Enter correct resource and project IDs.
400	00010010	The entered information is incorrect.	Enter the correct information.
400	00010011	The specification code is invalid.	Enter a correct specification code.
400	00010012	The entered access domain name does not exist.	Check the access domain name.
400	00010013	The access client does not exist.	Check the access client.
400	00010014	The access client name already exists.	Check the name of the access client.
400	00010015	The number of connected clients reaches the upper limit.	Delete idle access clients and re-create them, or contact O&M personnel to increase the upper limit.
400	00010016	The VPC ID must be specified in the default system access mode.	Check the entered VPC ID.
400	00010017	The subnet ID must be specified in the default system access mode.	Check the entered subnet ID.
400	00010018	Access connection is mandatory in the custom access mode.	Check the access connection list.
400	00010019	Only running access clients can be deleted.	Delete the client after its status changes to running.
400	00010020	Subnet conflict. Access clients cannot be repeatedly created on the same subnet.	Select another VPC subnet to create an access client.
400	00010021	The instance in the current state cannot be deleted.	Delete the cluster after the cluster status changes.
400	00010022	The feature is a restricted feature and is open only to whitelisted customers.	Contact O&M personnel to whitelist you.
400	00010023	The time format in the parameter is invalid.	Use a valid time format.
400	00010024	The current tenant has not created an agency and service functions will be abnormal.	Check the maximum number of agencies allowed for the current tenant or contact a user of the current tenant who has the permission to create an agency using IAM.
400	00010025	The quota service failed.	Check whether the updated quota meets requirements.
400	00010026	The tag list contains duplicate keys	Check the keys in the tag list.
400	00010027	The number of tags for a single instance has exceeded the limit.	Check the number of tags corresponding to the instance.
400	00010028	The tag list contains duplicate member values.	Check the member values in the tag list.
400	00010029	Members in the tag list cannot be NULL.	Check the members in the tag list.
400	00010030	Members in the condition list cannot be NULL.	Check the members in the condition list.
400	00010031	Member values in the tag list cannot be NULL.	Check the member values in the tag list.
400	00010032	Member values in the tag list cannot be NULL.	Check the member values in the tag list.
400	00010033	Member values in the condition list cannot be NULL.	Check the member values in the condition list.
400	00010034	System tags cannot be deleted in batches.	Select tags of other types for this operation.
400	00010035	You lack the permission to operate system labels.	Check your permissions.
400	00010036	System labels cannot be empty.	Check system tag parameters.
400	00010037	System labels and labels cannot be used concurrently.	Select either a system tag or a tag.
400	00010038	The request is not authorized.	Check permissions and grant the needed permissions before making requests.
400	00010039	The entered user or tenant information is incorrect.	Enter correct user or tenant information.
400	00010040	The entered configuration name is incorrect.	Enter a correct configuration name and check whether it is a system-level configuration.
400	00010041	VPC conflict. Access clients cannot be repeatedly created in the same VPC.	Select another VPC to create an access client.
400	00010042	Shared instances are not supported.	Create an exclusive instance or contact O&M personnel for assistance.
400	00010043	Failed to create the instance due to insufficient resources.	Contact O&M personnel to check resources.
400	00010044	A user instance in use exists in the cluster.	Release the instances associated with the cluster first.
400	00010045	The cluster does not exist.	Use a correct cluster ID.
400	00010046	The API reaches its traffic limit threshold.	Try again later.
400	00010047	Failed to upgrade the cluster.	Refresh and try again. Check whether the cluster status is normal.
400	00010048	System configuration cannot be modified.	Check the O&M user's operation permission for system configuration.
400	00010049	The parameter is invalid.	Check whether the parameter is valid.
400	00010050	The instance specifications cannot be changed because the instance is not in the running state.	Change the instance specifications after the instance status changes to running.
400	00010051	You lack the permission to send messages.	Check whether the configuration is correct.
400	00010052	The user is not authorized to use LakeFormation.	Approve the LakeFormation service authorization.
400	00010053	The current tenant has instances and the authorization cannot be canceled.	Delete the tenant's all instances (including those in the recycle bin) and cancel the authorization.
400	00010054	The metadata type of a logical multi-tenant cluster cannot be HiveMetaStore.	Change the metadata type.
400	00010055	Only non-shared instances support specification change.	Select a non-shared instance to continue the specification change.
400	00010056	Only scale-out is supported.	Select a higher instance specification.
400	00010057	Failed to set the instance as default because it is already set as the default one.	You do not need to set the instance as the default instance.
400	00010058	Failed to collect the account ID during overload control.	Check the account information.
400	00010059	The access tenant is not authorized.	Check whether the access tenant has been authorized.
400	00010060	The access tenant has been authorized.	Do not repeatedly authorize the access tenant.
400	00010061	Failed to perform this operation because the cluster is not running.	Check the cluster status.
400	00010062	Failed to perform this operation in the current task status.	Check the task status.
400	00010063	The task name already exists.	Check the entered task name.
400	00010064	The number has reached the upper limit.	Delete idle tasks and re-create them, or contact O&M personnel to increase the upper limit.
400	00010065	Failed to perform the risk check.	Check your balance.
400	00010066	Task does not exist.	Check the task ID.
400	00010067	Failed to initialize the task because the number of tasks may have reached the upper limit.	Try again later.
400	00010068	The application in the state cannot be deleted. (The application in the DELETING or DELETED state cannot be deleted.)	The current application is being deleted or has been deleted. Do not repeatedly delete it.
400	00010069	The application does not exist.	Use a correct application ID.
400	00010070	Failed to create a yearly/monthly instance.	Examine the failure cause and try again.
400	00010071	The desired product is not found.	Purchase an available product.
400	00010072	The ID of the desired product is not found.	Try again.
400	00010073	You lack the permission to purchase specification.	Purchase another product.
400	00010074	Yearly/Monthly instances cannot be directly deleted.	Unsubscribe from the service on the service page or in the user center.
400	00010075	The application in the state cannot be updated. Only applications in the STOPPED state can be updated.	Update the application after its status changes to STOPPED.
404	00010076	The application does not exist.	Use a correct application ID.
404	00010077	The application version does not exist.	Use a correct version ID.
404	00010078	The instance is not in the recycle bin.	Wait until the deletion is complete or move the instance to the recycle bin again.
400	00010079	The instance cannot be deleted because it is being restored. Try again later.	Wait until the instance restoration is complete and try again.
400	00010080	Failed to create a yearly/monthly instance.	Create a pay-per-use instance or check the configurations.
400	00010081	Failed to create the application.	Examine the failure cause and try again.
400	00010082	The log file does not exist.	Check whether the configured log storage path contains files.
400	00010083	The job has not been executed.	Ensure that your job has been executed before viewing logs.
400	00010084	The task is running.	Check the task status and try again later.
400	00010085	The task is not running.	Check the task status and try again later.
400	00010086	The QPS specification does not exist.	Check the QPS specifications.
400	00010087	The instance ID of the task cannot be changed.	Modify the task in instance.
404	00010088	No default instance ID is configured for tenant in project.	Click Set as Default on the console to set an instance as the default instance if there is none.
400	00010089	The OBS bucket object does not exist.	Check the OBS address.
400	00010090	The format of the YAML file is incorrect.	Check the format of the YAML file.
400	00010091	The license does not exist.	Check whether the license exists.
400	00010092	No matching license mode.	Check the license mode.
400	00010093	The license bbom is empty.	Check the license bbom.
400	00010094	No matching bbom number.	Check the bbom number.
400	00010095	No matching bbom type.	Check the bbom type.
400	00010096	Failed to parse the license.	Check the content of the license file.
400	00010097	The number of licenses exceeds the upper limit.	Check the license.
400	00010098	The number of licenses is about to exceed the upper limit.	Check the license.
400	00010099	No matching license content.	Check the content of the license file.
400	00010100	No matching bbom.	Check the license bbom.
400	00010101	Does not match the license ESN.	Check the ESN of the license.
400	00010102	The license has expired.	Check whether the license expires.
400	00010103	The task resource is queuing.	Try again later.
400	00010104	The client access mode is not the automatic creation mode.	Check the client access mode.
400	00010105	Failed to create the application version.	Examine the failure cause and try again.
400	00010106	The desired task is not found in instance.	Switch to instance and try again.
400	00010107	Instance to which the desired task belongs is unauthorized.	Try again after instance is authorized.
400	00010108	Instance to which the desired task belongs is deleted.	Restore the deleted instance, or create a task for an existing instance and try again.
400	00010109	The instance cannot be deleted.	Delete all clients of the shared instance and try again.
401	00010110	Failed to verify the SMN message.	Check whether the message content is tampered with.
400	00010111	The task parameter does not exist.	Create or add parameter for the task.
400	00010112	The instance cannot be deleted when a migration task is running.	Stop the task and try again.
409	00010113	The instance is being changed.	Wait for the specification change process to complete.
400	00010114	Only yearly/monthly instances are supported.	Call the correct API by referring to the official website document.
400	00010115	Failed to upgrade the instance specifications.	Check the error cause or contact O&M personnel for assistance.
400	00010116	The entered QPS specification parameter is empty.	Check the input parameter.
400	00010117	Only one QPS specification parameter is required.	Check the input parameter.
400	00010118	The feature is not supported currently.	This feature is currently unavailable. Please await the next version update.
403	00010119	The current instance does not support lifecycle configuration.	Try another instance.
400	00010120	Data source type is not supported.	Check the data source type.
400	00010121	The permission policy type is not supported.	Check the permission policy type.
400	00010122	The network segment of VPC conflicts with that of LakeFormation.	Check the entered VPC network segment.
400	00010123	The network type for metadata migration is incorrect.	Check the migration network type.
400	00010124	The SMN service passed an invalid subscription confirmation or certificate URL.	Enter an HTTPS URL.
400	00010125	The DLF access point is incorrect.	Check the DLF access point.
400	00010126	Instances that are not in the running state or exclusive instances cannot be migrated.	Check the running status of the instance or cluster.
400	00010127	The API access request control item's capacity in the license is insufficient.	Verify the API access request control item's capacity within the license.
400	00010128	The migration object does not exist.	Check the migration object parameters in the task.
400	00010129	Failed to create the instance because the license has expired.	Check the license validity period.
404	00010130	The configured condition does not exist.	Use correct conditions.
500	00012001	Failed to import APIs in the swagger file to the API Gateway.	Check whether the swagger file defined by the API contains format or syntax errors.
500	00012002	Failed to create the API Gateway security group.	Contact O&M personnel for assistance.
500	00012003	Failed to delete the API Gateway security group.	Contact O&M personnel for assistance.
500	00012004	Failed to add API Gateway security rules.	Contact O&M personnel for assistance.
500	00012005	Failed to create API Gateway instances.	Contact O&M personnel for assistance.
500	00012006	Failed to create an API Gateway.	Contact O&M personnel for assistance.
500	00012007	Failed to atomically create an API Gateway.	Contact O&M personnel for assistance.
500	00012008	Failed to roll back the atomically created API Gateway.	Contact O&M personnel for assistance.
500	00012009	Failed to bind the API Gateway to the cluster.	Contact O&M personnel for assistance.
500	00012010	The API Gateway was unable to generate the list of APIs.	Contact O&M personnel for assistance.
500	00012011	Failed to delete the API Gateway.	Contact O&M personnel for assistance.
500	00012012	Failed to add a CCE cluster.	Contact O&M personnel for assistance.
500	00012013	Failed to atomically add a CCE cluster.	Contact O&M personnel for assistance.
500	00012014	Failed to bind the CCE cluster to the LakeFormation cluster.	Contact O&M personnel for assistance.
500	00012015	Failed to check whether the task is created in the CCE cluster.	Contact O&M personnel for assistance.
500	00012016	Failed to configure automatic node scaling for the CCE cluster.	Contact O&M personnel for assistance.
500	00012017	Failed to set the initialization task for the CCE cluster only once.	Contact O&M personnel for assistance.
500	00012018	The one-off initialization task for the CCE cluster failed.	Contact O&M personnel for assistance.
500	00012019	Failed to configure service containers for the CCE cluster.	Contact O&M personnel for assistance.
500	00012020	Failed to add the namespace to the cluster.	Contact O&M personnel for assistance.
500	00012021	Failed to obtain all CCE clusters.	Contact O&M personnel for assistance.
500	00012022	Failed to delete CCE clusters.	Contact O&M personnel for assistance.
500	00012023	Failed to atomically delete CCE clusters.	Contact O&M personnel for assistance.
500	00012024	Failed to check whether the deletion task in the CCE cluster is successful.	Contact O&M personnel for assistance.
500	00012025	Failed to unbind the CCE cluster from the LakeFormation cluster.	Contact O&M personnel for assistance.
500	00012026	Failed to set ConfigMap for the CCE cluster.	Contact O&M personnel for assistance.
500	00012027	Failed to add CCE nodes.	Contact O&M personnel for assistance.
500	00012028	Failed to create all CCE nodes.	Contact O&M personnel for assistance.
500	00012029	Failed to create a LakeFormation cluster.	Contact O&M personnel for assistance.
500	00012030	Failed to create a LakeFormation cluster after the rollback.	Contact O&M personnel for assistance.
500	00012031	Failed to update the LakeFormation cluster ID of the user instance.	Contact O&M personnel for assistance.
500	00012032	Failed to create a VPC.	Contact O&M personnel for assistance.
500	00012033	Failed to make the VPC persistent.	Contact O&M personnel for assistance.
500	00012034	Failed to create a subnet.	Contact O&M personnel for assistance.
500	00012035	Failed to make the subnet persistent.	Contact O&M personnel for assistance.
500	00012036	Failed to create the business_vpcep service.	Contact O&M personnel for assistance.
500	00012037	Failed to make the VPC endpoint service persistent.	Contact O&M personnel for assistance.
500	00012038	Failed to create a single ELB.	Contact O&M personnel for assistance.
500	00012039	Failed to make a single ELB persistent.	Contact O&M personnel for assistance.
500	00012040	Failed to delete a cluster.	Contact O&M personnel for assistance.
500	00012041	Failed to delete the start method of the cluster.	Contact O&M personnel for assistance.
500	00012042	Failed to change the cluster status.	Contact O&M personnel for assistance.
500	00012043	Failed to change the cluster to a deleted state	Contact O&M personnel for assistance.
500	00012044	Failed to delete an instance.	Contact O&M personnel for assistance.
500	00012045	Failed to delete a VPC.	Contact O&M personnel for assistance.
500	00012046	Failed to delete subnet.	Contact O&M personnel for assistance.
500	00012047	Failed to delete a VPC endpoint.	Contact O&M personnel for assistance.
500	00012048	Failed to delete the ELB.	Contact O&M personnel for assistance.
500	00012049	The VPC endpoint license is invalid.	Contact O&M personnel for assistance.
500	00012050	Failed to create a VPC endpoint.	Contact O&M personnel for assistance.
500	00012051	Failed to receive the VPC endpoint connection.	Contact O&M personnel for assistance.
500	00012052	Failed to delete a VPC endpoint.	Contact O&M personnel for assistance.
500	00012053	Failed to create an OBS folder.	Verify if the OBS bucket has been set up and is functioning as expected.
500	00012054	Failed to create a database.	Contact O&M personnel for assistance.
500	00012055	Failed to create a database security group.	Contact O&M personnel for assistance.
500	00012056	Failed to create database security group rules.	Contact O&M personnel for assistance.
500	00012057	Failed to delete a database security group.	Contact O&M personnel for assistance.
500	00012058	Failed to create the business database.	Contact O&M personnel for assistance.
500	00012059	Failed to create the business database.	Contact O&M personnel for assistance.
500	00012060	The database creation is suspended.	Contact O&M personnel for assistance.
500	00012061	Failed to make the database persistent.	Contact O&M personnel for assistance.
500	00012062	Failed to bind the database to the cluster.	Contact O&M personnel for assistance.
500	00012063	Failed to delete a single business database.	Contact O&M personnel for assistance.
500	00012064	Failed to detach the database from the cluster.	Contact O&M personnel for assistance.
500	00012065	Failed to query the database based on the cluster ID.	Contact O&M personnel for assistance.
500	00012066	Failed to initialize DCS.	Contact O&M personnel for assistance.
500	00012067	Failed to create a security group.	Contact O&M personnel for assistance.
500	00012068	Failed to add security group rules.	Contact O&M personnel for assistance.
500	00012069	Failed to create a DCS instance.	Contact O&M personnel for assistance.
500	00012070	The DCS instance creation task is suspended.	Contact O&M personnel for assistance.
500	00012071	Failed to merge the four atomic operations.	Contact O&M personnel for assistance.
500	00012072	Failed to make DCS persistent.	Contact O&M personnel for assistance.
500	00012073	Failed to associate DCS with the cluster.	Contact O&M personnel for assistance.
500	00012074	Failed to delete a security group.	Contact O&M personnel for assistance.
500	00012075	Failed to delete DCS.	Contact O&M personnel for assistance.
500	00012076	Failed to detach DCS from the cluster.	Contact O&M personnel for assistance.
500	00012077	Failed to prepare a resource container account.	Contact O&M personnel for assistance.
500	00011001	Failed to perform the health check on the management console.	Increase the specifications when the CPU or memory is insufficient. Check the status of peripheral services. Restart the pods on the management plane.
500	00011002	Failed to run the external script.	Check whether the script contains errors.
500	00011003	Duplicate sequence ID in a WebSocket request.	View logs to locate and rectify the fault.
500	00011004	Failed to create an API Gateway.	View logs to locate and rectify the fault.
500	00011005	Failed to create an API Gateway due to insufficient AZ.	View logs to locate and rectify the fault.
500	00011006	The default API Gateway interface group does not exist.	View logs to locate and rectify the fault.
500	00011007	Failed to import APIs in batches to API Gateway.	View logs to locate and rectify the fault.
500	00011008	Failed to import APIs in batches to API Gateway because the backend ELB is not ready.	View logs to locate and rectify the fault.
500	00011009	There is no available environment for publishing an API Gateway.	View logs to locate and rectify the fault.
500	00011010	LakeFormation Admin server certificate is about to expire.	Replace the certificate and complete the upgrade in a timely manner.
500	00011011	LakeCat authentication credential of cluster is not found.	Check whether the corresponding credential exists in the database.
500	00011012	Failed to update the LakeCat authentication credential of cluster.	View logs to check whether the certificate fails to be obtained.
500	00011013	Image with tag does not exist.	Check whether the configured image exists.
500	00011014	Failed to connect an endpoint to the API Gateway.	View logs to locate and rectify the fault.
500	00011015	The cluster does not exist.	Ensure that the clusters associated with the instance have been established and are operating correctly.
500	00011016	The API Gateway instance does not exist.	Ensure that the APIG instances associated with the instance have been established and are functioning properly.
500	00011017	An exception occurred when a SQL statement is executed.	View logs to locate and rectify the fault.
500	00011018	The I/O stream operation is abnormal.	View logs to locate and rectify the fault.
500	00011019	LakeCat connection authentication failed.	Check whether the authentication credential is correct.
500	00011020	Failed to parse the LakeFormation Admin server certificate.	Rebuild the container.
500	00011021	The bearer tenant ID does not exist.	Ensure that the clusters associated with the instance have been established and are operating correctly.
500	00011022	The VPC ID does not exist.	Ensure that the clusters associated with the instance have been established and are operating correctly.
500	00011023	The VPC subnet ID does not exist.	Ensure that the clusters associated with the instance have been established and are operating correctly.
500	00011024	The service unit ID does not exist.	Ensure that the clusters associated with the instance have been established and are operating correctly.
500	00011025	The cluster ID does not exist.	Ensure that the clusters associated with the instance have been established and are operating correctly.
500	00011026	The information cannot be found.	Check whether the database table is tampered with.
500	00011027	The API status is inconsistent.	Contact O&M personnel for assistance.
500	00011028	The process is being stopped.	Contact O&M personnel for assistance.
500	00011029	Failed to obtain, create, or delete an agency.	Check whether the IAM service is normal.
500	00011030	Running. Try again later.	Try again later.
500	00011031	Failed to re-encrypt the password when uploading the configuration to CCE.	Contact the O&M personnel to check whether the password in the database is correctly encrypted.
500	00011032	Failed to delete the OBS directory.	Manually delete the residual OBS directories.
500	00011033	The VPC does not exist.	Check VPC configurations.
500	00011034	The subnet does not exist.	Check subnet configurations.
500	00011035	The configurations of subnet network segments conflict with those of VPC.	Check subnet segment configurations.
500	00011036	DCS does not exist or is unavailable.	Check DCS configurations.
500	00011037	The database does not exist or is unavailable.	Check database configurations.
500	00011038	An internal error occurred in the quota management service.	Contact O&M personnel to check whether the quota data in the database is correct.
500	00011039	Resources on which LakeFormation depends are severely overloaded.	Check the resource usage.
500	00011040	Resources on which LakeFormation depends are overloaded.	Check the resource usage.
500	00011041	Resources on which LakeFormation depends are moderately overloaded.	Check the resource usage.
500	00011042	Resources on which LakeFormation depends are slightly overloaded.	Check the resource usage.
500	00011043	Failed to execute the method in the cache.	Query logs based on the cache key in the alarm information to locate the fault.
500	00011044	API Gateway health check failed.	Check the status of the APIG service.
500	00011045	CCE health check failed.	Check the status of the CCE service.
500	00011046	CloudAutoDeploy-CDK health check failed.	Check the status of the CDK service.
500	00011047	GaussDB health check failed.	Check the status of the GaussDB service.
500	00011048	ELB health check failed.	Check the status of the ELB service.
500	00011049	VPC endpoint health check failed.	Check the status of VPC endpoint services.
500	00011050	DCS health check failed.	Check the status of the DCS service.
500	00011051	IAM health check failed.	Check the status of the IAM service.
500	00011052	ZooKeeper health check failed.	Check the status of the ZooKeeper service.
500	00011053	MySQL health check failed.	Check the status of the MySQL service.
500	00011054	OBS health check failed.	Check the status of the OBS service.
500	00011055	Failed to perform the cluster health check.	Restart CCE pods or check whether the peripheral services specified in the location information are abnormal.
500	00011056	HiveMetaStore health check failed.	Contact O&M personnel for assistance.
500	00011057	Ranger health check failed.	Contact O&M personnel for assistance.
500	00011058	There are no active business units detected during the health check.	Check the cluster status or wait until the cluster creation process is complete.
500	00011059	Failed to configure DCS instances.	Check whether the DCS instance status is normal and whether the configurations are correctly set.
500	00011060	RDS health check failed.	Check the status of the RDS service.
500	00011061	The proportion of pods on CCE cluster nodes exceeds the upper limit.	Check CCE cluster nodes and migrate pods.
500	00011062	Failed to obtain the agency token.	Create an agency.
500	00011063	Failed to obtain the user ID.	Check if the access client and its instance are functioning properly.
500	00011064	Failed to obtain the project ID.	Check if the access client and its instance are functioning properly.
500	00011065	Failed to obtain the terminal tenant.	Check if the access client and its instance are functioning properly.
500	00011066	Failed to obtain the job.	Check whether the job is normal.
500	00011067	Failed to obtain the task.	Check whether the task is normal.
500	00011068	Failed to access the GOCM service.	Check whether the GOCM service is normal.
500	00011069	Failed to connect to the cluster from the management console.	Restart CCE pods or check whether the VPCEP service is normal.
500	00011070	The node on the management and control plane cannot connect to the tenant plane.	Check whether the instances on the tenant plane are normal.
500	00011071	Failed to execute the workflow.	Locate the cause based on the workflow task ID or service logs.
500	00011072	Failed to initialize the instance.	View logs on the tenant plane.
500	00011073	Failed to destroy the instance.	View logs on the tenant plane.
500	00011074	Failed to upgrade the cluster.	Check whether the cluster mirroring function is normal.
500	00011075	An error occurred during the aging process of the tables.	Check data aging configurations.
500	00011076	Failed to create OpenGauss database because the flavor does not have insufficient AZ.	Contact OpenGauss O&M personnel or try other specifications.
500	00011077	OpenGauss health check failed.	Check the status of GaussDB for MySQL.
500	00011078	Failed to obtain the API calling times record.	Check the connection between the management plane and tenant plane.
500	00011079	Failed to delete the API calling times record.	Check the connection between the management plane and tenant plane.
500	00011080	Failed to scale out the MySQL database.	Check whether the MySQL instance is normal.
500	00011081	DCS scale-out failed.	Check whether the DCS instance is normal.
500	00011082	OLC decryption failed.	Check the overload control decryptor.
500	00011083	GaussDB health check failed.	Check the status of the GaussDB service.
500	00011084	No specCode is found.	Check the configured specCode.
500	00011085	An agency exception occurred when accessing service or tenant account.	Reach out to the support team to have tenant re-authorized.
500	00011086	Failed to perform the health check on CCE nodes.	Check the status of CCE nodes and restart them.
500	00011087	Failed to perform the health check on CCE pods.	Check the status of CCE pods and rebuild them.
500	00011088	The tenant plane's database connection pool has too many connections.	Check the database connection on the tenant plane.
500	00011089	The database connection pool on the control and management plane has too many connections.	Check the database connection on the management plane.
500	00011090	The database usage is moderately high.	Check the instance database capacity on the tenant plane.
500	00011091	The database usage is relatively high.	Check the instance database capacity on the tenant plane.
500	00011092	The database usage is high.	Check the instance database capacity on the tenant plane and expand the capacity in a timely manner.
500	00011093	The database usage is extremely high.	Check the instance database capacity on the tenant plane and expand the capacity in a timely manner.
500	00011094	Failed to perform the VPC endpoint health check.	Check the status of VPC endpoint services.
500	00011095	Failed to create an order.	Try again.
500	00011096	Failed to create a yearly/monthly DB instance.	Try again.
500	00011097	Failed to obtain the CCE workload status.	Reach out to the CCE support team to rectify the fault.
500	00011098	Failed to register the license callback function.	Diagnose the fault based on the error information.
500	00011099	Failed to update the default configuration.	Contact O&M personnel for assistance.
500	00011100	Failed to access the client due to inappropriate client access mode.	Check the creation mode of the access client.
500	00011101	No node pool specifications are available.	Add the node pool specifications or contact O&M personnel for assistance.
500	00011102	The status of work order is abnormal.	Contact O&M personnel for assistance.
500	00011103	Failed to update the cluster ID.	Contact O&M personnel for assistance.
500	00011104	Failed to select a task program for task type.	Contact O&M personnel for assistance.
500	00011105	Failed to obtain the service unit of cluster.	Check whether the instance is created or whether the database is modified.
500	00011106	Failed to obtain the CCE cluster of service unit.	Check whether the instance is created or whether the database is modified.
500	00011107	Failed to execute the work order task.	Contact O&M personnel for assistance.
500	00011108	Failed to initialize the CDR.	Check the billing mode of instance.
500	00011109	An exception occurred when generating SDRs for instance.	Check the SDR of instance.
500	00011110	Failed to create an OBS bucket.	Check whether the OBS service is supported and whether the OBS service permission is correct, or contact O&M personnel for assistance.
500	00011111	Failed to write data to OBS.	Check whether the OBS service is supported and whether the OBS service permission is correct, or contact O&M personnel for assistance.
500	00011112	Failed to update information about task in OBS.	Contact O&M personnel for assistance.
500	00011113	Failed to convert task to the JSON format.	Contact O&M personnel for assistance.
500	00011114	Failed to obtain the IAM token.	Contact O&M personnel for assistance.
500	00011115	Failed to create the CCE cluster.	Contact O&M personnel for assistance.
500	00011116	Failed to install CCE plug-in.	Check CCE configuration items.
500	00011117	Failed to configure the CCE cluster initialization task.	Check CCE configuration items.
500	00011118	Failed to obtain images.	Contact O&M personnel for assistance.
500	00011119	Failed to process the certificate.	Contact O&M personnel for assistance.
500	00011120	Failed to obtain the CTS proxy instance.	Contact O&M personnel for assistance.
500	00011121	Failed to create or delete the database instance.	Locate the failure cause based on logs.
500	00011122	No available database specifications are found for user.	Check configuration items.
500	00011123	The openGauss database does not support the Hive type.	Check configuration items.
500	00011124	Failed to create a database because the system has no sufficient AZs.	Check configuration items or contact O&M personnel for assistance.
500	00011125	Failed to create DCS because the system has no sufficient AZs.	Check configuration items or contact O&M personnel for assistance.
500	00011126	Failed to find the subnet during ELB creation.	Check the status of the VPC network and its associated subnets.
500	00011127	No ELB specifications are available for user to create QPS.	Check configuration items.
500	00011128	Failed to create or update the IAM permission.	Contact O&M personnel for assistance.
500	00011129	Failed to create or update the IAM agency.	Contact O&M personnel for assistance.
500	00011130	The message sent to the tenant plane has been forwarded.	Contact O&M personnel for assistance.
500	00011131	Failed to verify the random AZ ID.	Locate the failure cause based on logs.
500	00011132	OBS I/O exception.	Contact O&M personnel for assistance.
500	00011133	Failed to send initialization data to the tenant plane.	Contact O&M personnel for assistance.
500	00011134	Failed to send user group information to the tenant plane.	Contact O&M personnel for assistance.
500	00011135	An exception occurred when creating or modifying the instance because the task cannot be found.	Locate the failure cause based on logs or contact O&M personnel for assistance.
500	00011136	An exception occurred during the cluster health check.	Restart CCE pods or check whether the peripheral services specified in the location information are abnormal.
500	00011137	Failed to create the application.	Locate the failure cause based on logs or contact O&M personnel for assistance.
500	00011138	Failed to create the application version.	Locate the failure cause based on logs or contact O&M personnel for assistance.
500	00011139	The instance does not exist or is unavailable.	Check database configurations.
400	00011140	Failed to restore the instance.	Check the instance status.
500	00011141	Failed to move the instance to the recycle bin.	Check the instance status.
500	00011142	Failed to bring all APIs online or offline.	Try again later.
500	00011143	Failed to register the alarm rule.	Check whether the alarm rule is correctly configured and whether the CES service is normal.
500	00011144	Failed to obtain the LTS host group.	Confirm if the ICAgent is installed on the tenant's CCE cluster, or if the number of LTS host groups has reached its maximum capacity.
500	00011145	Failed to add monitoring data to CES.	Contact O&M personnel for assistance.
500	00011146	The resource monitoring metric configuration on which LakeFormation depends is invalid.	Review the alarm settings for the resource monitoring metrics essential to LakeFormation. For more information, refer to the detailed alarm configuration of these metrics.
500	00011147	The resource monitoring metric data granularity is not supported.	Use available values, such as 1, 300, 1200, 3600, 14400, and 86400 (measured in seconds).
500	00011148	The resource monitoring metric aggregation mode is not supported.	Use available values, such as average, max, min, sum, and variance.
500	00011149	The comparison operator for resource monitoring metric data is not supported.	Use available values, such as >, >=, <, and <=.
500	00011150	The alarm severity of the resource monitoring metric is not supported.	Use available values, such as EMERGENCY, IMPORTANT, MEDIUM, and COMMON.
500	00011151	The resource monitoring metric is not supported.	Use available values, such as nicByteIn and nicByteOut.
500	00011152	Failed to verify the CCE agency.	Ensure that CCE APIs are authorized.
500	00011157	Failed to verify the link data consistency for LakeFormation.	Restart management-plane pods in CloudOpsPortal.
500	00011158	The number of metadata records in LakeFormation clusters exceeds the upper limit.	Delete unnecessary metadata.
500	00011159	The number of metadata records in LakeFormation clusters exceeds 90% of the upper limit.	Delete unnecessary metadata.
500	00011160	Instance migration failed.	Locate the fault by referring to tenant-plane logs or check the OBS path for migrating the replication instance.
500	00011161	Failed to obtain the agency token.	Check whether the IAM service is normal.
500	00011162	Failed to create SFS instances.	Contact O&M personnel for assistance.
500	00011163	Specification is not supported.	Check the configured specification parameters.
500	00011164	The CDR information contains negative numbers.	Query the SDR information of the corresponding instance based on the location information.
500	00011165	The Helm file cannot be found.	Check whether the Helm file is correct.
500	00011166	Persistent volume creation failed.	Contact O&M personnel for assistance.
500	00011167	Failed to set up the WAF platform.	Check whether the WAF parameters are correct.
500	00011168	Failed to create the persistent volume declaration.	Contact O&M personnel for assistance.
500	00011169	Failed to create LakeFormation instances in MetaStore.	Contact O&M personnel for assistance.
500	00011170	Failed to create the LakeFormation access client in MetaStore.	Contact O&M personnel for assistance.
500	00011171	Failed to create catalogs in MetaStore.	Contact O&M personnel for assistance.
500	00011172	Failed to create databases in MetaStore.	Contact O&M personnel for assistance.
500	00011173	Failed to set up the ModelArts platform.	Contact O&M personnel for assistance.
500	00011174	The CCE ID does not exist.	Ensure that the clusters associated with the instance have been established and are operating correctly.