[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eThis document details common error messages encountered when using Dataproc Metastore, providing explanations and recommended actions for each.\u003c/p\u003e\n"],["\u003cp\u003eGeneral errors include invalid client inputs, invalid API resource states, insufficient API access permissions, and service agent permission issues that may arise during resource creation or operations.\u003c/p\u003e\n"],["\u003cp\u003eErrors related to import and export can involve insufficient Cloud Storage permissions, using unsupported Hive versions for Avro operations, or missing tables during the import process.\u003c/p\u003e\n"],["\u003cp\u003eBackup and restore related errors include failing to find a backup for restoration, or attempting to delete a backup that is currently in use.\u003c/p\u003e\n"],["\u003cp\u003eResolving these errors typically involves checking resource states, adjusting permissions, validating input data, updating configurations, and ensuring compatibility with supported Hive versions.\u003c/p\u003e\n"]]],[],null,["# Error messages\n\nThis page explains common error messages that you might receive when using\nDataproc Metastore. Each section includes more information on what the\nmessages mean and the recommended actions for resolving the errors.\n\nGeneral errors:\n\n- [Invalid client inputs:](#invalid-client-inputs)\n\n - \"ResourceName error Path \\[RESOURCE_NAME\\] does not match template \\[RESOURCE_TEMPLATE\\].\"\n - \"Invalid warehouse directory override: \\[GCS_URI\\].\"\n - \"The provided krb5.conf object krb5Config was invalid.\"\n- [Invalid API resource state:](#invalid-api-resource-state)\n\n - \"Current state of resource \\[RESOURCE_NAME\\] is not a valid state for this operation. Valid state(s) are \\[RESOURCE_STATE\\].\"\n - You tried to run update, import, export, backup, or restore on a Dataproc Metastore service, but the service was not `ACTIVE`.\n - \"Backup \\[BACKUP_ID\\] not ready.\"\n- [API access permission:](#api-access-permission)\n\n - You didn't have enough permission to call the Dataproc Metastore APIs.\n- [Insufficient service agent permissions:](#insufficient-service-agent-permissions)\n\n - \"The Dataproc Metastore service agent \\[SERVICE_AGENT\\] does\n not have sufficient IAM permissions to access the network \\[NETWORK\\].\n Please make sure the service agent is granted roles/metastore.serviceAgent\n in the project \\[PROJECT_NUMBER\\].\"\n\n - \"Dataproc Metastore Service Agent cannot access Cloud Storage\n URI \\[GCS_URI\\] with permissions \\[SERVICE_AGENT_PERMISSIONS\\]; Please check\n permissions or VPC Service Controls service perimeter.\"\n\n - \"The provided warehouse directory's Cloud Storage bucket \\[GCS_URI\\] is\n not readable and writable by the Dataproc Metastore service\n agent.\"\n\nErrors relating to import and export:\n\n- [Import and export Cloud Storage permissions:](#cloud-storage-permissions)\n\n - \"\"Dataproc Metastore Service Agent\" or \"Caller\" does not have enough permissions of the Cloud Storage URI for import/export (\\[SERVICE_AGENT\\] cannot access Cloud Storage URI \\[GCS_URI\\] with permissions \\[SERVICE_AGENT_PERMISSIONS\\]).\"\n- [Run Avro import or export on an unsupported Hive version:](#run-avro-on-unsupported-hive-version)\n\n - \"Importing from Avro files is not supported for Hive version \\[HIVE_METASTORE_VERSION\\], supported versions are \\[SUPPORT_HIVE_VERSIONS\\].\"\n- [Missing import tables:](#missing-import-tables)\n\n - \"Avro source files not found for tables \\[MISSING_TABLE_LIST\\].\"\n - \"Hive schema validation failed, missing tables: \\[MISSING_TABLE_LIST\\].\"\n\nErrors relating to backup and restore:\n\n- [Backup not found for restore:](#backup-not-found)\n\n - \"Backup \\[BACKUP_ID\\] not found.\"\n- [Cannot delete a backup:](#cannot-delete-backup)\n\n - \"Cannot delete a backup in a state \\[RESOURCE_STATE\\].\"\n\nGeneral errors\n--------------\n\nThis section explains general errors.\n\n### Invalid client inputs\n\nThis is a generic error that means something about your request is invalid,\nindependent of the server's state. This error type could be triggered by many\ndifferent things, such as:\n\n- When using the REST API, you specified the name of a network in an invalid\n format.\n\n \u003e ResourceName error Path \\[RESOURCE_NAME\\] does not match template \\[RESOURCE_TEMPLATE\\].\n- The warehouse directory was not a valid Cloud Storage path. For more\n information, see [Hive Metastore](/dataproc-metastore/docs/hive-metastore).\n\n \u003e Invalid warehouse directory override: \\[GCS_URI\\].\n- You specified invalid Kerberos configurations (see\n [Configure Kerberos for a service](/dataproc-metastore/docs/configure-kerberos).\n\n \u003e The provided krb5.conf object krb5Config was invalid.\n\n**Recommended action:** Fix your request.\n\n### Invalid API resource state\n\nThis is a generic error that means that something about the request is not\ncompatible with the current state of the server resource.\n\u003e Current state of resource \\[RESOURCE_NAME\\] is not a valid state for this operation. Valid state(s) are \\[RESOURCE_STATE\\].\n\nThis can happen if the API resource (Dataproc Metastore service,\nimport, export, backup, or restore) is not in the correct state to perform the\naction, for example:\n\n- You tried to run update, import, export, backup, or restore on a Dataproc Metastore service, but the service was not `ACTIVE`.\n- You tried to restore a backup, and the Dataproc Metastore service\n was `ACTIVE`, but the backup was not `ACTIVE`.\n\n \u003e Backup \\[BACKUP_ID\\] not ready.\n\n**Recommended action:** Check that your API resource is in the correct state\nbefore retrying the request.\n\n### API access permission\n\nYou didn't have enough permission to call the Dataproc Metastore\nAPIs.\n\n**Recommended action:** Grant the user the correct [Dataproc Metastore IAM permissions](/dataproc-metastore/docs/iam-roles).\n\n### Insufficient service agent permissions\n\nYou received a permission error when creating resources in your project. The\nerror is usually caused by a deleted service account, or modified service\naccount permissions, for example:\n\n- You used a network belonging to a different project, but didn't grant the Dataproc Metastore\n service agent permission to access it. For more information, see [Cross project deployment](/dataproc-metastore/docs/cross-project-deployment#set-up-permissions).\n\n \u003e The Dataproc Metastore service agent \\[SERVICE_AGENT\\] does not have sufficient IAM permissions to access the network \\[NETWORK\\]. Please make sure the service agent is granted roles/metastore.serviceAgent in the project \\[PROJECT_NUMBER\\].\n- You provided a custom data warehouse Cloud Storage bucket, but you didn't\n grant the Dataproc Metastore service agent permission to access\n it. For more information, see [Hive warehouse directory](/dataproc-metastore/docs/hive-metastore#hive-warehouse-dir).\n\n \u003e Dataproc Metastore Service Agent cannot access Cloud Storage URI \\[GCS_URI\\] with permissions \\[SERVICE_AGENT_PERMISSIONS\\]; Please check permissions or VPC Service Controls service perimeter.\n\nOr Dataproc Metastore couldn't access the warehouse directory\nCloud Storage path.\n\u003e The provided warehouse directory's Cloud Storage bucket \\[GCS_URI\\] is not readable and writable by the Dataproc Metastore service agent.\n\n**Recommended action:** Check your [service account permissions](/dataproc-metastore/docs/iam-and-access-control#service-accounts)\nor [VPC Service Controls service perimeter](/dataproc-metastore/docs/vpc-sc).\n\nErrors relating to import and export\n------------------------------------\n\nThis section explains errors relating to import and export.\n\n### Import and export Cloud Storage permissions\n\nYour Dataproc Metastore service agent didn't have enough\npermissions to perform the import or export.\n\u003e \"Dataproc Metastore Service Agent\" or \"Caller\" does not have enough permissions of the Cloud Storage URI for import/export (\\[SERVICE_AGENT\\] cannot access Cloud Storage URI \\[GCS_URI\\] with permissions \\[SERVICE_AGENT_PERMISSIONS\\]).\n\n**Recommended action:** Check your [service account permissions](/dataproc-metastore/docs/iam-and-access-control#service-accounts)\nor [VPC Service Controls service perimeter](/dataproc-metastore/docs/vpc-sc).\n\n### Run Avro import or export on an unsupported Hive version\n\n\u003e Importing from Avro files is not supported for Hive version \\[HIVE_METASTORE_VERSION\\], supported versions are \\[SUPPORT_HIVE_VERSIONS\\].\n\n**Recommended action:** See [Version policy](/dataproc-metastore/docs/version-policy)\nfor the most up-to-date Hive version support. Update your database files to a\nsupported version.\n\n### Missing import tables\n\n- For Avro import\n\n \u003e Avro source files not found for tables \\[MISSING_TABLE_LIST\\].\n- For SQL import\n\n \u003e Hive schema validation failed, missing tables: \\[MISSING_TABLE_LIST\\].\n\n**Recommended action:** Use the [Dataproc Metastore Toolkit](https://github.com/GoogleCloudPlatform/dataproc-metastore-toolkit)\nas a reference to check the correct Hive metadata schemas of your database files.\n\nErrors relating to backup and restore\n-------------------------------------\n\nThis section explains errors relating to backup and restore.\n\n### Backup not found for restore\n\nWhen restoring a backup in a service, Dataproc Metastore couldn't\nfind your provided backup resource.\n\u003e Backup \\[BACKUP_ID\\] not found.\n\n**Recommended action:** Check that your backup exists within your Dataproc Metastore\nservice.\n\n### Cannot delete a backup\n\nYou couldn't delete a backup when it was being used to restore a service.\n\u003e Cannot delete a backup in a state \\[RESOURCE_STATE\\].\n\n**Recommended action:** Wait for the restore job to complete before attempting\nto delete the backup.\n\nWhat's next\n-----------\n\n- To find solutions for common issues that you might encounter when using Dataproc Metastore, see [Troubleshooting](/dataproc-metastore/docs/troubleshooting)."]]
