Error Codes
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.
|
Status Code |
Error Code |
Error Message |
Description |
Measure |
|---|---|---|---|---|
|
500 |
lakeformation.00012001 |
Failed to import APIs in the swagger file to API Gateway. |
Failed to import the APIs in swagger files to API Gateway. |
Check whether these swagger files about API definitions contain format or syntax errors. |
|
500 |
lakeformation.00012002 |
Failed to create the API Gateway security group. |
Failed to create the API Gateway security group. |
Contact O&M personnel. |
|
500 |
lakeformation.00012003 |
Failed to delete the API Gateway security group. |
Failed to delete the API Gateway security group. |
Contact O&M personnel. |
|
500 |
lakeformation.00012004 |
Failed to add the API Gateway security rule. |
Failed to add an API Gateway security rule. |
Contact O&M personnel. |
|
500 |
lakeformation.00012005 |
Failed to create the API Gateway instance. |
Failed to create an API Gateway instance. |
Contact O&M personnel. |
|
500 |
lakeformation.00012006 |
API Gateway creation failed. |
Failed to complete the API Gateway creation. |
Contact O&M personnel. |
|
500 |
lakeformation.00012007 |
Failed to atomically create API Gateway. |
Failed to atomically create API Gateway. |
Contact O&M personnel. |
|
500 |
lakeformation.00012008 |
Failed to roll back the atomically created API Gateway. |
Failed to roll back the atomically created API Gateway. |
Contact O&M personnel. |
|
500 |
lakeformation.00012009 |
Failed to bind API Gateway to the cluster. |
Failed to bind API Gateway to the cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012010 |
API Gateway failed to create the API list. |
API Gateway failed to create the API list. |
Contact O&M personnel. |
|
500 |
lakeformation.00012011 |
Failed to delete API Gateway. |
Failed to delete the API Gateway. |
Contact O&M personnel. |
|
500 |
lakeformation.00012012 |
Failed to add a CCE cluster. |
Failed to add a CCE cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012013 |
Failed to atomically add a CCE cluster to the cluster. |
Failed to atomically add a CCE cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012014 |
Failed to bind the CCE cluster to the DALF cluster. |
Failed to bind the CCE cluster to the DALF cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012015 |
Check whether the creation task in the CCE cluster is successful. |
Failed to check whether the creation task in the CCE cluster is successful. |
Contact O&M personnel. |
|
500 |
lakeformation.00012016 |
Failed to configure automatic node scaling for the CCE cluster. |
Failed to configure automatic node scaling for the CCE cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012017 |
Failed to set the initialization task for the CCE cluster only once. |
Failed to set the initialization task for the CCE cluster only once. |
Contact O&M personnel. |
|
500 |
lakeformation.00012018 |
Failed to set the initialization task for the ddCCE cluster only once. |
Failed to complete the initialization task setting for the CCE cluster only once. |
Contact O&M personnel. |
|
500 |
lakeformation.00012019 |
Failed to configure service containers for the CCE cluster. |
Failed to configure service containers for the CCE cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012020 |
Failed to add the namespace to the cluster. |
Failed to add a namespace to the cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012021 |
Failed to obtain all CCE clusters in the cluster. |
Failed to obtain all CCE clusters in the cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012022 |
Failed to delete the CCE cluster. |
Failed to delete a CCE cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012023 |
Failed to atomically delete the CCE cluster. |
Failed to atomically delete a CCE cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012024 |
Failed to check whether the deletion task in the CCE cluster is successful. |
Failed to check whether the deletion task in the CCE cluster is successful. |
Contact O&M personnel. |
|
500 |
lakeformation.00012025 |
Failed to unbind the CCE cluster from the DALF cluster. |
Failed to unbind the CCE cluster from the DALF cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012026 |
Failed to set ConfigMap for the CCE cluster. |
Failed to set ConfigMap for the CCE cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012027 |
Failed to add the CCE node. |
Failed to add a CCE node. |
Contact O&M personnel. |
|
500 |
lakeformation.00012028 |
Failed to create all CCE nodes. |
Failed to create all CCE nodes. |
Contact O&M personnel. |
|
500 |
lakeformation.00012029 |
Failed to create a DALF cluster. |
Failed to create a DALF cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012030 |
Failed to create a DALF cluster during rollback. |
Failed to create a DALF cluster during rollback. |
Contact O&M personnel. |
|
500 |
lakeformation.00012031 |
Failed to update the DALF cluster ID of the user instance. |
Failed to update the DALF cluster ID of the user instance. |
Contact O&M personnel. |
|
500 |
lakeformation.00012032 |
Failed to create a VPC. |
Failed to create a VPC. |
Contact O&M personnel. |
|
500 |
lakeformation.00012033 |
Failed to make the VPC persistent. |
Failed to make the VPC persistent. |
Contact O&M personnel. |
|
500 |
lakeformation.00012034 |
Failed to create a subnet. |
Failed to create a subnet. |
Contact O&M personnel. |
|
500 |
lakeformation.00012035 |
Failed to make the subnet persistent. |
Failed to make the subnet persistent. |
Contact O&M personnel. |
|
500 |
lakeformation.00012036 |
Failed to create the business_vpcep service. |
Failed to create the business_vpcep service. |
Contact O&M personnel. |
|
500 |
lakeformation.00012037 |
Failed to make the VPCEP service persistent. |
Failed to make the VPCEP service persistent. |
Contact O&M personnel. |
|
500 |
lakeformation.00012038 |
Failed to create a single ELB. |
Failed to create a single ELB. |
Contact O&M personnel. |
|
500 |
lakeformation.00012039 |
Failed to make a single ELB persistent. |
Failed to make a single ELB persistent. |
Contact O&M personnel. |
|
500 |
lakeformation.00012040 |
Failed to delete a cluster. |
Failed to delete a cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012041 |
Failed to delete the start method of the cluster. |
Failed to delete the start method of the cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012042 |
Failed to change the cluster status. |
Failed to change the cluster status. |
Contact O&M personnel. |
|
500 |
lakeformation.00012043 |
Failed to change the cluster status. |
Failed to change the cluster status. |
Contact O&M personnel. |
|
500 |
lakeformation.00012044 |
Failed to delete the instance. |
Failed to delete an instance. |
Contact O&M personnel. |
|
500 |
lakeformation.00012045 |
Failed to delete a VPC. |
Failed to delete a VPC. |
Contact O&M personnel. |
|
500 |
lakeformation.00012046 |
Failed to delete a subnet. |
Failed to delete a subnet. |
Contact O&M personnel. |
|
500 |
lakeformation.00012047 |
Failed to delete a VPCEP endpoint. |
Failed to delete a VPCEP. |
Contact O&M personnel. |
|
500 |
lakeformation.00012048 |
Failed to delete the ELB. |
Failed to delete the ELB. |
Contact O&M personnel. |
|
500 |
lakeformation.00012049 |
The VPCEP license is invalid. |
The VPCEP license is invalid. |
Contact O&M personnel. |
|
500 |
lakeformation.00012050 |
Failed to create a VPCEP endpoint. |
Failed to create a VPCEP. |
Contact O&M personnel. |
|
500 |
lakeformation.00012051 |
Failed to receive the VPCEP connection. |
Failed to receive the VPCEP connection. |
Contact O&M personnel. |
|
500 |
lakeformation.00012052 |
Failed to delete a VPCEP endpoint. |
Failed to delete a VPCEP. |
Contact O&M personnel. |
|
500 |
lakeformation.00012053 |
Failed to create the obs folder. |
Failed to create the OBS folder. |
Check whether the OBS bucket has been created or whether OBS is normal. |
|
500 |
lakeformation.00012054 |
Failed to create the database. |
Failed to create the database. |
Contact O&M personnel. |
|
500 |
lakeformation.00012055 |
Failed to create the database security group. |
Failed to create the database security group. |
Contact O&M personnel. |
|
500 |
lakeformation.00012056 |
Failed to create the database security group rule. |
Failed to create the database security group rule. |
Contact O&M personnel. |
|
500 |
lakeformation.00012057 |
Failed to delete the database security group. |
Failed to delete the database security group. |
Contact O&M personnel. |
|
500 |
lakeformation.00012058 |
Failed to create a business database. |
Failed to create a business database. |
Contact O&M personnel. |
|
500 |
lakeformation.00012059 |
Failed to create a business database. |
Failed to create a business database. |
Contact O&M personnel. |
|
500 |
lakeformation.00012060 |
The database creation is suspended. |
Failed to complete the database creation. |
Contact O&M personnel. |
|
500 |
lakeformation.00012061 |
Failed to make the database persistent. |
Failed to make the database persistent. |
Contact O&M personnel. |
|
500 |
lakeformation.00012062 |
Failed to bind the database to the cluster. |
Failed to bind the database to the cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012063 |
Failed to delete a single business database. |
Failed to delete a single business database. |
Contact O&M personnel. |
|
500 |
lakeformation.00012064 |
Failed to separate the database from the cluster. |
Failed to separate the database from the cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012065 |
Failed to query the database based on the cluster ID. |
Failed to query the database by cluster ID. |
Contact O&M personnel. |
|
500 |
lakeformation.00012066 |
Failed to initialize DCS. |
Failed to initialize the DCS. |
Contact O&M personnel. |
|
500 |
lakeformation.00012067 |
Failed to create a security group. |
Failed to create a security group. |
Contact O&M personnel. |
|
500 |
lakeformation.00012068 |
Failed to add a security group rule. |
Failed to add a security group rule. |
Contact O&M personnel. |
|
500 |
lakeformation.00012069 |
Failed to create a DCS instance. |
Failed to create a DCS instance. |
Contact O&M personnel. |
|
500 |
lakeformation.00012070 |
The DCS instance creation task is suspended. |
Failed to complete DCS instance creation. |
Contact O&M personnel. |
|
500 |
lakeformation.00012071 |
Failed to merge the four atomic operations. |
Failed to merge the four atomic operations. |
Contact O&M personnel. |
|
500 |
lakeformation.00012072 |
Failed to make DCS persistent. |
Failed to make DCS persistent. |
Contact O&M personnel. |
|
500 |
lakeformation.00012073 |
Failed to associate the DCS with the cluster. |
Failed to associate the DCS with the cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012074 |
Failed to delete a security group. |
Failed to delete a security group. |
Contact O&M personnel. |
|
500 |
lakeformation.00012075 |
Failed to delete DCS. |
Failed to delete DCS. |
Contact O&M personnel. |
|
500 |
lakeformation.00012076 |
Failed to separate DCS from the cluster. |
Failed to separate DCS from the cluster. |
Contact O&M personnel. |
|
500 |
lakeformation.00012077 |
Failed to prepare a resource container account. |
Failed to prepare a resource container account. |
Contact O&M personnel to create a resource container account. The IAM service is faulty or needs to be restored. |
|
500 |
lakeformation.00011001 |
Failed to copy the data flow. |
Failed to copy the data flow. |
Contact O&M personnel to rectify the fault. |
|
500 |
lakeformation.00011002 |
Failed to run the external script. |
Failed to run the external script. |
Check whether the script contains errors. |
|
500 |
lakeformation.00011003 |
Duplicate sequence ID of WebSocket requests. |
Duplicate sequence ID of WebSocket requests. |
View logs to locate and rectify the fault. |
|
500 |
lakeformation.00011004 |
Failed to create an API Gateway instance. |
Failed to create an API Gateway instance. |
View logs to locate and rectify the fault. |
|
500 |
lakeformation.00011005 |
Failed to create API Gateway instances due to insufficient AZ. |
Failed to create API Gateway instances due to insufficient AZ. |
View logs to locate and rectify the fault. |
|
500 |
lakeformation.00011006 |
The default API Gateway API group does not exist. |
The default API Gateway API group does not exist. |
View logs to locate and rectify the fault. |
|
500 |
lakeformation.00011007 |
Failed to import APIs in batches to API Gateway. |
Failed to import APIs in batches to API Gateway. |
View logs to locate and rectify the fault. |
|
500 |
lakeformation.00011008 |
Failed to import APIs in batches to API Gateway because the backend ELB is not ready. |
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 |
lakeformation.00011009 |
There is no API Gateway release environment. |
There is no API Gateway release environment. |
View logs to locate and rectify the fault. |
|
500 |
lakeformation.00011010 |
LakeFormation Admin server certificate will expire soon. |
LakeFormation Admin server certificate will expire soon. |
Replace the certificate and complete the upgrade in a timely manner. |
|
500 |
lakeformation.00011011 |
LakeCat authentication credential of cluster is not found. |
LakeCat authentication credential for clusters is not found. |
Check whether the corresponding credential exists in the database. |
|
500 |
lakeformation.00011012 |
Failed to update the LakeCat authentication credential of cluster. |
Failed to update the LakeCat authentication credential for clusters. |
Check logs to determine whether the ks certificate fails to be obtained. |
|
500 |
lakeformation.00011013 |
Image with tag does not exist. |
Image with tag does not exist. |
Check whether the configured image tag exists. |
|
500 |
lakeformation.00011014 |
Failed to connect the endpoint to API Gateway. |
Failed to connect the endpoint to API Gateway. |
View logs to locate and rectify the fault. |
|
500 |
lakeformation.00011015 |
The cluster does not exist. |
The cluster does not exist. |
Check whether the clusters related to the instance have been created and are running properly. |
|
500 |
lakeformation.00011016 |
The API Gateway instance does not exist. |
The API Gateway instance does not exist. |
Check whether the API Gateway instance related to the instance has been created and is running properly. |
|
500 |
lakeformation.00011017 |
Failed to execute the SQL statement. |
Failed to execute the SQL statement. |
View logs to locate and rectify the fault. |
|
500 |
lakeformation.00011018 |
Abnormal I/O stream operation. |
The I/O stream operation is abnormal. |
View logs to locate and rectify the fault. |
|
500 |
lakeformation.00011019 |
LakeCat connection authentication failed. |
Failed to authenticate LakeCat connection. |
Check whether the authentication credential is correct. |
|
500 |
lakeformation.00011020 |
Failed to parse the LakeFormation Admin server certificate. |
Failed to parse the LakeFormation Admin server certificate. |
Rebuild the container. |
|
500 |
lakeformation.00011021 |
The service tenant ID does not exist. |
The service tenant ID does not exist. |
Check whether the clusters related to the instance have been created and are running properly. |
|
500 |
lakeformation.00011022 |
The VPC ID does not exist. |
The VPC ID does not exist. |
Check whether the clusters related to the instance have been created and are running properly. |
|
500 |
lakeformation.00011023 |
The VPC subnet ID does not exist. |
The VPC subnet does not exist. |
Check whether the clusters related to the instance have been created and are running properly. |
|
500 |
lakeformation.00011024 |
The service unit ID does not exist. |
The service unit ID does not exist. |
Check whether the clusters related to the instance have been created and are running properly. |
|
500 |
lakeformation.00011025 |
The cluster ID does not exist. |
The cluster ID does not exist. |
Check whether the clusters related to the instance have been created and are running properly. |
|
500 |
lakeformation.00011026 |
The specified content cannot be found in the database. |
The specified content cannot be found in the database. |
Check whether the database table is tampered with. |
|
500 |
lakeformation.00011027 |
Inconsistent API statuses. |
The API status is inconsistent. |
Contact O&M personnel. |
|
500 |
lakeformation.00011028 |
Process being stopped. |
The process is being stopped. |
Contact O&M personnel. |
|
500 |
lakeformation.00011029 |
Failed to obtain, create, or delete the agency. |
Failed to obtain, create, or delete an agency. |
Check whether the IAM service is normal. |
|
500 |
lakeformation.00011030 |
Running. |
The task is running. |
Try again later. |
|
500 |
lakeformation.00011031 |
Failed to re-encrypt the password when uploading the configuration to CCE. |
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 |
lakeformation.00011032 |
Failed to delete the OBS directory. |
Failed to delete the OBS directory. |
Manually delete the residual OBS directory. |
|
500 |
lakeformation.00011033 |
The VPC does not exist. |
The VPC does not exist. |
Check the VPC configuration items. |
|
500 |
lakeformation.00011034 |
The subnet does not exist. |
The subnet does not exist. |
Check the subnet configuration items. |
|
500 |
lakeformation.00011035 |
The segment configuration of the subnet network conflicts with VPC. |
The segment configuration of the subnet network conflicts with VPC. |
Check the subnet segment configuration. |
|
500 |
lakeformation.00011036 |
DCS unavailable. |
The DCS does not exist or is unavailable. |
Check the DCS configuration. |
|
500 |
lakeformation.00011037 |
Database unavailable. |
The database does not exist or is unavailable. |
Check the database configuration. |
|
500 |
lakeformation.00011038 |
An internal error occurred in the quota management service. |
An internal error occurred in the quota management service. |
Contact the O&M personnel to check whether the quota data in the database is correct. |
|
500 |
lakeformation.00011039 |
Instance unavailable. |
The instance does not exist or is unavailable. |
Check the database configuration. |
|
500 |
lakeformation.00011040 |
Failed to restore the instance. |
Failed to restore an instance. |
Check the instance status. |
|
500 |
lakeformation.00011041 |
Failed to move the instance to the recycle bin. |
Failed to move the instance to the recycle bin. |
Check the instance status. |
|
500 |
lakeformation.00011042 |
Failed to bring all APIs online or offline. |
Failed to bring all APIs online or offline. |
Try again later. |
|
500 |
lakeformation.00011043 |
Failed to execute the method in the cache. |
Failed to execute the method in the cache. |
Query logs based on the cache key in the alarm information to locate the fault. |
|
500 |
lakeformation.00011044 |
API Gateway health check failed. |
The API Gateway health check failed. |
Check the status of the API Gateway service. |
|
500 |
lakeformation.00011045 |
CCE health check failed. |
The CCE health check failed. |
Check the status of the CCE service. |
|
500 |
lakeformation.00011046 |
CDK health check failed. |
The CloudAutoDeploy-CDK health check failed. |
Check the status of CloudAutoDeploy-CDK. |
|
500 |
lakeformation.00011047 |
GaussDB health check failed. |
The GaussDB health check failed. |
Check the status of GaussDB. |
|
500 |
lakeformation.00011048 |
ELB health check failed. |
The ELB health check failed. |
Check the status of the ELB service. |
|
500 |
lakeformation.00011049 |
VPCEP health check failed. |
The VPCEP health check failed. |
Check the status of the VPCEP service. |
|
500 |
lakeformation.00011050 |
DCS health check failed. |
The DCS health check failed. |
Check the status of the DCS service. |
|
500 |
lakeformation.00011051 |
IAM health check failed. |
The IAM health check failed. |
Check the status of the IAM service. |
|
500 |
lakeformation.00011052 |
ZooKeeper health check failed. |
The ZooKeeper health check failed. |
Check the status of ZooKeeper. |
|
500 |
lakeformation.00011053 |
MySQL health check failed. |
The MySQL health check failed. |
Check the status of MySQL. |
|
500 |
lakeformation.00011054 |
OBS health check failed. |
The OBS health check failed. |
Check the status of the OBS service. |
|
500 |
lakeformation.00011055 |
The health check on the tenant plane failed. |
The health check on the tenant plane failed. |
Contact O&M personnel. |
|
500 |
lakeformation.00011056 |
HiveMetaStore health check failed. |
HiveMetaStore health check failed. |
Contact O&M personnel. |
|
500 |
lakeformation.00011057 |
Ranger health check failed. |
Ranger health check failed. |
Contact O&M personnel. |
|
500 |
lakeformation.00011058 |
No running business unit exists during the health check. |
No running business unit exists during the health check. |
Check the cluster status or wait until the cluster is created. |
|
500 |
lakeformation.00011059 |
Failed to configure the DCS instance. |
Failed to configure the DCS instance. |
Check whether the DCS instance status is normal and configuration is correct. |
|
500 |
lakeformation.00011060 |
RDS health check failed. |
The RDS health check failed. |
Check the status of the RDS service. |
|
500 |
lakeformation.00011061 |
Pods on the CCE cluster node exceeds the upper limit. |
Pods on the CCE cluster node exceed the upper limit. |
Check the CCE cluster nodes and migrate pods. |
|
500 |
lakeformation.00011062 |
Failed to obtain the agency token. |
Failed to obtain the agency token. |
Check whether the IAM service is normal. |
|
500 |
lakeformation.00011063 |
Failed to obtain the user ID. |
Failed to obtain the user ID. |
Check whether the access client or its instance is normal. |
|
500 |
lakeformation.00011064 |
Failed to obtain the project ID. |
Failed to obtain the project ID. |
Check whether the access client or its instance is normal. |
|
500 |
lakeformation.00011065 |
Failed to obtain the terminal tenant. |
Failed to obtain the terminal tenant. |
Check whether the access client or its instance is normal. |
|
500 |
lakeformation.00011066 |
Failed to obtain the job. |
Failed to obtain a job. |
Check whether the job is normal. |
|
500 |
lakeformation.00011067 |
Failed to obtain the task. |
Failed to obtain a task. |
Check whether the task is normal. |
|
500 |
lakeformation.00011068 |
Failed to access the GOCM service. |
Failed to access the GOCM service. |
Check whether the GOCM service is normal. |
|
500 |
lakeformation.00011069 |
The cluster does not have any connection to the tenant plane. |
The cluster does not have any connection to the tenant plane. |
Check whether the instances on the tenant plane are normal. |
|
500 |
lakeformation.00011070 |
The node on the management and control plane cannot connect to the tenant plane. |
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 |
lakeformation.00011071 |
Failed to execute the workflow. |
Failed to execute the workflow. |
Locate the cause based on the workflow task ID or service logs. |
|
500 |
lakeformation.00011072 |
Failed to initialize the instance. |
Failed to initialize the instance. |
View logs on the tenant plane. |
|
500 |
lakeformation.00011073 |
Failed to release the instance. |
Failed to release the instance. |
View logs on the tenant plane. |
|
500 |
lakeformation.00011074 |
Failed to upgrade the cluster. |
Failed to upgrade the cluster. |
Check whether the cluster mirroring function is normal. |
|
500 |
lakeformation.00011075 |
An error occurred during table aging. |
An error occurred during table aging. |
Check the data aging configuration. |
|
500 |
lakeformation.00011076 |
Failed to create OpenGauss because the flavor does not have insufficient AZ. |
Failed to create OpenGauss because the flavor does not have insufficient AZ. |
Contact OpenGauss O&M personnel or try other specifications. |
|
500 |
lakeformation.00011077 |
OpenGauss health check failed. |
The OpenGauss health check failed. |
Check the status of OpenGauss. |
|
500 |
lakeformation.00011078 |
Failed to obtain the API calling times record. |
Failed to obtain the number of API calling times. |
Check the connection between the management plane and tenant plane. |
|
500 |
lakeformation.00011079 |
Failed to delete the API calling times record. |
Failed to delete the API calling times record. |
Check the connection between the management plane and tenant plane. |
|
500 |
lakeformation.00011080 |
Failed to scale out the MySQL database. |
Failed to scale out the MySQL database. |
Check whether the MySQL DB instance is normal. |
|
500 |
lakeformation.00011081 |
DCS scale-out failed. |
DCS scale-out failed. |
Check whether the DCS instance is normal. |
|
500 |
lakeformation.00011082 |
OLC decryption failed. |
OLC decryption failed. |
Check the overload control decryptor. |
|
500 |
lakeformation.00011083 |
GaussDB health check failed. |
The GaussDB health check failed. |
Check the status of the GaussDB service. |
|
500 |
lakeformation.00011084 |
No specCode is found. |
No specCode is found. |
Check the configured specCode. |
|
500 |
lakeformation.00011085 |
An agency exception occurred when accessing service or tenant account. |
An agency exception occurred when a service is accessed or a tenant account is used. |
Authorize the access tenant again. |
|
500 |
lakeformation.00011086 |
Failed to perform the health check on CCE nodes. |
Failed to perform the health check on CCE nodes. |
Check the CCE node status and restart the node. |
|
500 |
lakeformation.00011087 |
Failed to perform the health check on CCE pods. |
Failed to perform the health check on a CCE pod. |
Check the CCE pod status and rebuild the pod. |
|
500 |
lakeformation.00011088 |
Too many connections in the database connection pool on the tenant plane. |
Too many connections in the database connection pool on the tenant plane. |
Check the database connection on the tenant plane. |
|
500 |
lakeformation.00011089 |
Too many connections in the database connection pool on the management plane. |
Too many connections in the database connection pool on the management plane. |
Check the database connection on the management plane. |
|
500 |
lakeformation.00011090 |
Medium high GaussDB database capacity use. |
Medium high GaussDB database capacity use. |
Check the instance database capacity on the tenant plane. |
|
500 |
lakeformation.00011091 |
Medium GaussDB database capacity use. |
Medium GaussDB database capacity use. |
Check the instance database capacity on the tenant plane. |
|
500 |
lakeformation.00011092 |
High GaussDB database capacity use. |
High GaussDB database capacity use. |
Check the instance database capacity on the tenant plane and expand the capacity in a timely manner. |
|
500 |
lakeformation.00011093 |
Ultra GaussDB database capacity use. |
Ultra GaussDB database capacity use. |
Check the instance database capacity on the tenant plane and expand the capacity in a timely manner. |
|
400 |
lakeformation.00010002 |
The instance cannot process requests because it is not running. |
The instance cannot process requests because it is not running. |
Send the request when the instance is running. |
|
400 |
lakeformation.00010003 |
Instance not exist. |
The instance does not exist. |
Use a correct instance ID. |
|
400 |
lakeformation.00010004 |
Bucket entered not exist. |
The entered bucket does not exist. |
Check the bucket. |
|
400 |
lakeformation.00010005 |
Protocol version entered not exist. |
The entered protocol version does not exist. |
Check the protocol version. |
|
400 |
lakeformation.00010006 |
Empty protocol version. |
The protocol version cannot be empty. |
Check the entered protocol version. |
|
400 |
lakeformation.00010007 |
Resource clearing task ID not exist. |
The resource clearing task does not exist. |
Check the task ID. |
|
400 |
lakeformation.00010008 |
Duplicate instance name. |
The instance name already exists. |
Enter another instance name. |
|
400 |
lakeformation.00010009 |
No resources found. |
The queried resource does not exist. |
Enter correct resource and project IDs. |
|
400 |
lakeformation.00010010 |
The resource management service request parameter is incorrect. |
The resource management service request parameter is incorrect. |
Contact the resource management service to check the query parameters. |
|
400 |
lakeformation.00010011 |
Invalid specification code. |
The specification code is invalid. |
Enter a correct specification code. |
|
400 |
lakeformation.00010012 |
Access domain name entered not exist. |
The entered access domain name does not exist. |
Check the entered access domain name. |
|
400 |
lakeformation.00010013 |
Access client not exist. |
The access client does not exist. |
Check the entered access client. |
|
400 |
lakeformation.00010014 |
Duplicate access client name. |
The access client name already exists. |
Check the entered access client name. |
|
400 |
lakeformation.00010015 |
Connected clients reach the upper limit. |
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 |
lakeformation.00010016 |
The VPC ID must be specified in the default system access mode. |
The VPC ID must be specified in the default system access mode. |
Check the entered VPC ID. |
|
400 |
lakeformation.00010017 |
The regional node ID must be specified in the default system access mode. |
The subnet ID must be specified in the default system access mode. |
Check the entered subnet ID. |
|
400 |
lakeformation.00010018 |
Access connection is mandatory in the custom access mode. |
The access connection must be specified in the custom access mode. |
Check the access connection list. |
|
400 |
lakeformation.00010019 |
Only running access clients can be deleted. |
Only running access clients can be deleted. |
Delete the client after it changes to the running state. |
|
400 |
lakeformation.00010020 |
Subnet conflict. Access clients cannot be repeatedly created on the same subnet. |
Subnet conflict. Access clients cannot be repeatedly created on the same subnet. |
Select another VPC subnet to create an access client. |
|
400 |
lakeformation.00010021 |
Failed to delete instances in the current state. |
Failed to delete instances in the current state. |
Delete the cluster after the cluster status changes. |
|
400 |
lakeformation.00010022 |
The feature is restricted and is open only to whitelisted customers. |
The feature is restricted and is open only to whitelisted customers. |
Contact O&M personnel to whitelist you. |
|
400 |
lakeformation.00010023 |
Invalid time format in the parameter. |
The time format in the parameter is invalid. |
Use a valid time format. |
|
400 |
lakeformation.00010024 |
Agency not created and service will be abnormal. |
The current tenant has not created an agency and therefore service functions will be abnormal. |
Contact a user with IAM usage permission under the current tenant to create an agency. |
|
400 |
lakeformation.00010025 |
The quota service failed. |
The quota service failed. |
Check whether the updated quota meets requirements. |
|
400 |
lakeformation.00010026 |
Duplicate key in the tag list. |
The tag list has duplicate keys. |
Check the keys in the tag list. |
|
400 |
lakeformation.00010027 |
Tags for a single instance exceeds the upper limit. |
The number of tags for a single instance exceeds the upper limit. |
Check the number of tags in the instance. |
|
400 |
lakeformation.00010028 |
Duplicate member value in the tag list. |
The tag list has duplicate member values. |
Check the member values in the tag list. |
|
400 |
lakeformation.00010029 |
Null members are not allowed in the tag list. |
Null members are not allowed in the tag list. |
Check the members in the tag list. |
|
400 |
lakeformation.00010030 |
Null members are not allowed in the condition list. |
Null members are not allowed in the condition list. |
Check the members in the condition list. |
|
400 |
lakeformation.00010031 |
Null values are not allowed in the member value list of the tag list. |
Null values are not allowed in the member value list of the tag list. |
Check the member values in the tag list. |
|
400 |
lakeformation.00010032 |
Null member values are not allowed in the tag list. |
Null member values are not allowed in the tag list. |
Check the member values in the tag list. |
|
400 |
lakeformation.00010033 |
Null member values are not allowed in the condition list. |
Null member values are not allowed in the condition list. |
Check the member values in the condition list. |
|
400 |
lakeformation.00010034 |
System tags cannot be deleted in batches. |
System tags cannot be deleted in batches. |
Select another tag operation. |
|
400 |
lakeformation.00010035 |
No permissions for operating system labels. |
You do not have the permission to operate system labels. |
Check your permissions. |
|
400 |
lakeformation.00010036 |
System labels cannot be empty. |
System labels cannot be empty. |
Check the system label parameter. |
|
400 |
lakeformation.00010037 |
System labels and labels cannot be used concurrently. |
System labels and labels cannot be used concurrently. |
Select a system label or a label of your choice. |
|
400 |
lakeformation.00010038 |
Unauthorized requests. |
The request is not authorized. |
Request after authorization. |
|
400 |
lakeformation.00010039 |
Incorrect user or tenant information. |
The entered user or tenant information is incorrect. |
Enter correct user or tenant information. |
|
400 |
lakeformation.00010040 |
Incorrect configuration name. |
The entered configuration name is incorrect. |
Enter a correct configuration name and check whether the configuration is at the system level. |
|
400 |
lakeformation.00010041 |
VPC conflict. Access clients cannot be repeatedly created in the same VPC. |
VPC conflict. Access clients cannot be repeatedly created in the same VPC. |
Select another VPC to create an access client. |
|
400 |
lakeformation.00010042 |
Shared instances are not supported. |
Shared instances are not supported. |
Create an exclusive instance or contact O&M personnel. |
|
400 |
lakeformation.00010043 |
Failed to create instances due to insufficient resources. |
Failed to create instances due to insufficient resources. |
Contact O&M personnel to check resources. |
|
400 |
lakeformation.00010044 |
A user instance is in use in the cluster. |
A user instance is in use in the cluster. |
Release the instances associated with the cluster first. |
|
400 |
lakeformation.00010045 |
Cluster not exist. |
The cluster does not exist. |
Use a correct cluster ID. |
|
400 |
lakeformation.00010046 |
API traffic limit threshold reached. |
The traffic limit threshold of the API is reached. |
Try again later. |
|
400 |
lakeformation.00010047 |
Failed to upgrade the cluster. |
Failed to upgrade the cluster. |
Refresh and try again. Check whether the cluster status is normal. |
|
400 |
lakeformation.00010048 |
System configuration cannot be modified. |
System configurations cannot be modified. |
Check the O&M user's system configurations and operation permission. |
|
400 |
lakeformation.00010049 |
Invalid O&M service invoking parameter. |
The O&M service invoking parameter is invalid. |
Check whether the parameter is valid. |
|
400 |
lakeformation.00010050 |
Failed to change the instance specifications because the instance is not running. |
Failed to change the instance specifications because the instance is not running. |
Change the instance specifications after the instance status changes into Running. |
|
400 |
lakeformation.00010051 |
No permission for sending messages. |
You do not have the permission to send messages. |
Check whether the configuration is correct. |
|
400 |
lakeformation.00010052 |
Current user not authorized for LakeFormation. |
The current user is not authorized to use LakeFormation. |
Grant the user permission to use LakeFormation. |
|
400 |
lakeformation.00010053 |
The current tenant has instances and cannot cancel the authorization. |
The current tenant has instances and cannot cancel the authorization. |
Delete the tenant's all instances (including those in the recycle bin) and cancel the authorization. |
|
400 |
lakeformation.00010054 |
The metadata type of a logical multi-tenant cluster cannot be hivemetastore. |
The metadata type of a logical multi-tenant cluster cannot be hivemetastore. |
Change the metadata type. |
|
400 |
lakeformation.00010055 |
Only non-shared instances support specification change. |
Only non-shared instances support specification change. |
Select a non-shared instance to continue the specification change. |
|
400 |
lakeformation.00010056 |
Only scale-out is supported. |
Only scale-out is supported. |
Select a higher instance specification. |
|
400 |
lakeformation.00010057 |
Failed to set the instance as default because there is another default one. |
Failed to set the instance as default because there is another default one. |
Set the current default instance as non-default and set another instance as default. |
|
400 |
lakeformation.00010058 |
Failed to collect the account ID during overload control. |
Failed to collect the account ID during overload control. |
Check the account information. |
|
400 |
lakeformation.00010059 |
Access tenant unauthorized. |
The access tenant is not authorized. |
Check whether the access tenant has been authorized. |
|
400 |
lakeformation.00010060 |
Access tenant authorized. |
The access tenant has been authorized. |
Do not repeatedly authorize an access tenant. |
|
400 |
lakeformation.00010061 |
Failed to perform this operation because the cluster is not running. |
Failed to perform this operation because the cluster is not running. |
Check the cluster status. |
|
400 |
lakeformation.00010062 |
Failed to perform this operation in the current task status. |
Failed to perform this operation in the current task status. |
Check the task status. |
|
400 |
lakeformation.00010063 |
The task name already exists. |
The task name already exists. |
Check the entered task name. |
|
400 |
lakeformation.00010064 |
The number of tasks has reached the upper limit. |
The number of tasks has reached the upper limit. |
Delete idle tasks and create them again, or contact O&M personnel to increase the maximum number of tasks. |
|
400 |
lakeformation.00010065 |
Risk check failed. |
The risk check failed. |
Check your balance. |
|
400 |
lakeformation.00010066 |
Task task not exist. |
The task does not exist. |
Check the job ID. |
|
400 |
lakeformation.00010067 |
Failed to initialize the task because the number of tasks may have reached the upper limit. |
Failed to initialize the task because the number of tasks may have reached the upper limit. |
Try again later. |
|
400 |
lakeformation.00010068 |
The application cannot be deleted. Duplicate deletion is not allowed. |
The application in the current state cannot be deleted. Duplicate deletion is not allowed. |
The current application is being deleted or has been deleted. Do not repeatedly delete it. |
|
400 |
lakeformation.00010069 |
Application not exist. |
The application does not exist. |
Use a correct application ID. |
|
500 |
lakeformation.00000001 |
Exception being handled. |
The exception is being handled. |
Try again later. |
|
400 |
lakeformation.00000002 |
Unsupported permission types. |
The permission type is not supported. |
Check the entered permission type. |
|
400 |
lakeformation.00000003 |
The resource already exists. |
The resource already exists. |
Check all your resources and reset them. |
|
400 |
lakeformation.00000004 |
The number of resources exceeds the upper limit. |
The number of resources exceeds the upper limit. |
Delete unnecessary resources. |
|
400 |
lakeformation.00000005 |
The resource does not exist. |
The resource does not exist. |
Check whether the resource is available. |
|
400 |
lakeformation.00000006 |
The resource list is empty. |
The resource list is empty. |
Check whether the resource list is empty. |
|
400 |
lakeformation.00000007 |
Resource cannot be null. |
The resource cannot be empty. |
Check whether the resource is null. |
|
400 |
lakeformation.00000008 |
Unsupported resources name. |
The resource name is not supported. |
Check the resource name. |
|
400 |
lakeformation.00000009 |
Unsupported resource types. |
The resource type is not supported. |
Check the entered permission type. |
|
400 |
lakeformation.00000010 |
Unsupported authorization entity types. |
The authorization entity type is not supported. |
Check the entered authorization entity type. |
|
400 |
lakeformation.00000011 |
The operation table is a non-partitioned table. |
The operation table is a non-partitioned table. |
Check the entered table type. |
|
400 |
lakeformation.00000012 |
Incorrect partition value. |
The entered partition value is incorrect. |
Check whether the number and type of the entered partition key list of the table match those of the entered partition value list. |
|
400 |
lakeformation.00000013 |
Incorrect type of column. |
The column type is incorrect. |
Check whether the entered column type matches the type supported by the official website. |
|
500 |
lakeformation.00000014 |
The signature certificate does not exist. |
The signature certificate does not exist. |
Check whether services on the management plane are available. |
|
400 |
lakeformation.00000015 |
Invalid token. |
The token is invalid. |
Check whether the token is valid. |
|
400 |
lakeformation.00000016 |
Insufficient permissions. |
The permission is insufficient. |
Check whether you have the required permission. |
|
400 |
lakeformation.00000017 |
Empty statistics. |
The statistics are empty. |
Check whether the statistics are empty or the statistics type is set incorrectly. |
|
400 |
lakeformation.00000018 |
Incomplete information about the referenced table when attempting to obtain the foreign key. |
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 |
lakeformation.00000019 |
Pattern matching and filtering matching parameters cannot coexist. |
Pattern matching and filtering matching parameters cannot coexist. |
Check the entered pattern matching and filtering parameters. |
|
400 |
lakeformation.00000020 |
Feature is not supported. |
The feature is not supported. |
Look out for version updates. |
|
400 |
lakeformation.00000021 |
The project to which the token belongs is inconsistent with the project ID in the request address. |
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 |
lakeformation.00000022 |
Incorrect request address format. |
The format of the request address is incorrect. |
Enter a correct request address. |
|
400 |
lakeformation.00000023 |
The token is missing. |
The token is missing. |
Enter a token. |
|
500 |
lakeformation.00000030 |
Invalid input parameter. |
The input parameter is invalid. |
Check the input parameter. |
|
400 |
lakeformation.00000031 |
Invalid object. |
The object is invalid. |
Check the object. |
|
400 |
lakeformation.00000032 |
Invalid operation. |
The operation is invalid. |
Check the operation. |
|
400 |
lakeformation.00000033 |
Unknown database. |
The database is unknown. |
Check the database. |
|
400 |
lakeformation.00000034 |
Unknown partition. |
The partition is unknown. |
Check the partition. |
|
400 |
lakeformation.00000035 |
Unknown table. |
The table is unknown. |
Check the table. |
|
400 |
lakeformation.00000036 |
Metadata exception. |
The metadata is abnormal. |
Check the request. |
|
400 |
lakeformation.00000037 |
Exceeded the number supported by the permission principal. |
The permission entity number exceeds the number supported by the permission principal. |
Delete some authorizations. |
|
400 |
lakeformation.00000038 |
Cluster |
The cluster server certificate has expired. |
Replace the certificate and complete the upgrade in a timely manner. |
|
400 |
lakeformation.00000039 |
Failed to created the directory. |
Failed to create the directory. |
Check the path. |
|
400 |
lakeformation.00000040 |
Function does not exist. |
The function does not exist. |
Check the function name. |
|
400 |
lakeformation.00000041 |
Invalid table filter condition field. |
The table filter condition field is invalid. |
Check the fields that can be filtered in the table. |
|
400 |
lakeformation.00000042 |
Location path is not supported. |
The location path is not supported. |
Check the input location path. |
|
400 |
lakeformation.00000043 |
String has SQL injection risks. |
The string has SQL injection risks. |
Check the input string. |
|
500 |
lakeformation.00000044 |
Failed to parse the LakeFormation Admin server certificate. |
Failed to parse the LakeFormation Admin server certificate. |
Rebuild the container. |
|
400 |
lakeformation.00000045 |
The LakeFormation admin server certificate parse failed. |
The path already exists. |
Select an empty path. |
|
500 |
lakeformation.00000046 |
Process being stopped. |
The process is being stopped. |
Wait for the container to restart. |
|
400 |
lakeformation.00000047 |
Failed to delete Catalog because it contains custom databases. |
Failed to delete Catalog because it contains custom databases. |
Delete all non-default databases in this catalog. |
|
500 |
lakeformation.00000048 |
HiveMetaStore health check failed. |
The HiveMetaStore health check failed. |
Check the status of the HiveMetaStore service. |
|
500 |
lakeformation.00000049 |
Ranger health check failed. |
The Ranger health check failed. |
Check the status of the Ranger service. |
|
500 |
lakeformation.00000050 |
OBS health check failed. |
The OBS health check failed. |
Check whether the OBS service is normal and whether the AK/SK for calling OBS has expired. |
|
500 |
lakeformation.00000051 |
Failed to create or update database metadata. |
Failed to create or update database metadata. |
Check whether the SQL statement or database is normal. |
|
400 |
lakeformation.00000052 |
No default instance ID is configured in project by tenant. |
No default instance ID is configured in project by tenant. |
Check whether the default instance ID of the tenant is configured. |
|
400 |
lakeformation.00000053 |
Instance does not belong to tenant. |
The instance does not belong to the tenant. |
Check whether the instance ID is correct. |
|
400 |
lakeformation.00000054 |
Column statistics cannot be created for partitioned tables. |
Column statistics cannot be created for partitioned tables. |
Create or update statistics on the partition. |
|
400 |
lakeformation.00000055 |
Inconsistent data types between column statistics and columns. |
Inconsistent data types between column statistics and columns. |
Ensure that the data type of the column statistics is consistent with that of the table or partition column. |
|
500 |
lakeformation.00000056 |
Protobuf decoding failed. |
Protobuf decoding failed. |
Reset the data. |
|
500 |
lakeformation.00000057 |
No instances found. |
The instance is not found. |
Enter a correct instance ID. |
|
400 |
lakeformation.00000058 |
Failed to collect the account ID during overload control. |
Failed to collect the account ID during overload control. |
Check the account information. |
|
500 |
lakeformation.00000059 |
GaussDB health check failed. |
The GaussDB health check failed. |
Check the status of the GaussDB service. |
|
500 |
lakeformation.00000060 |
Too many requests. |
There are too many requests. |
Try again later. |
|
400 |
lakeformation.00000061 |
Requests cannot be serialized during partition creation. |
Requests cannot be serialized during partition creation. |
Try again later. |
|
400 |
lakeformation.00000062 |
The input exceeds the length limit. |
The input exceeds the length limit. |
Check the input. |
|
400 |
lakeformation.00000063 |
Failed to delete Catalog because it contains databases. |
Failed to delete Catalog because it contains databases. |
Delete all databases in this catalog. |
|
500 |
lakeformation.00000064 |
Failed to delete data from the table. |
Failed to delete data from the table. |
Check the log stack information. |
|
500 |
lakeformation.00023001 |
The WebSocket session is disconnected. |
The WebSocket session is disconnected. |
Check whether services on the management plane are available. |
|
500 |
lakeformation.00023002 |
Too many WebSocket requests. |
Too many WebSocket requests. |
Check whether services on the management plane are frozen. |
|
500 |
lakeformation.00023003 |
Empty WebSocket message. |
Empty WebSocket message. |
Check whether the network is in good condition. |
|
400 |
lakeformation.00023004 |
No permission to perform this operation on resources. |
You do not have the permission to perform this operation on resources. |
Check whether you have the permission to perform this operation on resources. |
|
500 |
lakeformation.00023005 |
Duplicate sequence ID of WebSocket requests. |
Duplicate sequence ID of WebSocket requests. |
View logs to locate and rectify the fault. |
|
500 |
lakeformation.00023006 |
Failed to execute the method in the cache. |
Failed to execute the method in the cache. |
Query logs based on the cache key in the alarm information to locate the fault. |
|
400 |
lakeformation.00023007 |
Failed to delete the role because it has been authorized. |
Failed to delete the role because it has been authorized. |
Unbind all permissions authorizations from the role before deleting it. |
|
400 |
lakeformation.00023008 |
Failed to create resources. |
Failed to create resources. |
Check the resource parameters or database status. |
|
400 |
lakeformation.00023009 |
The catalog cannot be deleted. |
The catalog cannot be deleted. |
The catalog cannot be deleted. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
