在本例中，當您按一下 BigQuery 節點詳細資料時，會看到訊息 Entry with this fully qualified name is not available in Dataplex
Universal Catalog or you do not have permissions to view it。
[[["容易理解","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-05 (世界標準時間)。"],[[["\u003cp\u003eThis document outlines troubleshooting steps for issues with Dataplex data lineage, specifically when it's not displaying correctly or when certain metadata is missing.\u003c/p\u003e\n"],["\u003cp\u003eData lineage visibility issues can be caused by the Data Lineage API being disabled in the active or compute project, or by the user lacking the Data Lineage Viewer role in either project.\u003c/p\u003e\n"],["\u003cp\u003eMissing BigQuery process metadata, like SQL statements or process types, often indicates that the user lacks \u003ccode\u003ebigquery.jobs.get\u003c/code\u003e permission in the compute project.\u003c/p\u003e\n"],["\u003cp\u003eIf BigQuery table details are incomplete, showing only the fully qualified name, it typically means the user needs \u003ccode\u003ebigquery.tables.get\u003c/code\u003e permission in the storage project.\u003c/p\u003e\n"],["\u003cp\u003eWhen troubleshooting data lineage issues, remember that it may take 30 minutes up to 24 hours for data lineage to display after a job is ran, depending on the complexity of the data.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot data lineage issues\n\nThis document describes how to resolve issues with Dataplex Universal Catalog\ndata lineage.\n\nProject types\n-------------\n\nData assets can reside in different projects. The following is a summary of\npossible projects and their asset names.\n\n### BigQuery storage project\n\nThis project stores your BigQuery data assets.\nYou can find it in asset details as a part of `Table ID`, before the first dot.\n**Figure 1.** The name of a BigQuery storage project.\n\n### Compute project\n\nThis project stores the data lineage metadata.\nFor BigQuery, this is where you run a job.\nIf you run a job using the Google Cloud console, you can find the compute project\nname in the project selector:\n**Figure 2.** The name of a compute project that runs BigQuery jobs.\n\nWhen sending requests to the BigQuery API, specify the compute project\nin the URL, for example: \n\n POST /bigquery/v2/projects/docs-compute/jobs HTTP/1.1\n Host: bigquery.googleapis.com\n User-Agent: Go-http-client/1.1\n Authorization: \u003cREDACTED 1031 BYTES\u003e\n Accept-Encoding: gzip\n {\n \"configuration\": {\n \"query\": {\n \"useLegacySql\": false,\n \"query\": \"CREATE OR REPLACE TABLE `docs-target.dataset.target-002` AS SELECT * FROM `docs-source.dataset.source-002`;\"\n }\n },\n \"jobReference\": {\n \"projectId\": \"docs-compute\",\n \"jobId\": \"docs-compute-job-id\",\n \"location\": \"us\",\n }\n }\n\n### Active project\n\nThis is the project from which you are viewing the data lineage.\nThe Google Cloud console shows the active project in the project selector.\nIf you're using the API, the active project is the project from which you're\nmaking API calls.\n**Figure 3.** The active project in the the Google Cloud console.\n\nBigQuery data lineage not showing\n---------------------------------\n\nThe following issue occurs after running a BigQuery job. In this case,\nthe problem can be caused by three scenarios:\n\n- The Data Lineage API is disabled in the [active project](#active-project) or the [compute project](#compute-project).\n- You don't have the [Data Lineage Viewer role](/iam/docs/understanding-roles#datalineage.viewer) (`roles/datalineage.viewer`) in the [active](#active-project) or the [compute](#compute-project) project.\n- The data lineage hasn't arrived yet. Depending on the volume and complexity of the data being processed, it can take from standard 30 minutes up to 24 hours for the data lineage to display.\n\nIf you see the message \"Fetching lineage failed due to missing permissions.\"\non the bottom of the page, you are missing permissions on the\n[active project](#active-project).\nOtherwise you are missing permissions on the\n[compute project](#compute-project).\n**Figure 4.** Example of lineage not showing in BigQuery UI.\n\nTo resolve this issue, check if the Data Lineage API is enabled for the\n[compute project](#compute-project).\nAfter enabling the API, you need to run a job to see the data lineage.\nDepending on the volume and complexity of the data being processed, it can take\nfrom standard 30 minutes up to 24 hours for the data lineage to display.\n\nNext, check if the Data Lineage API is enabled for the\n[active project](#active-project).\n\nWhen the Data Lineage API is enabled, grant the\n[Data Lineage Viewer role](/iam/docs/understanding-roles#datalineage.viewer) (`roles/datalineage.viewer`)\nin both the [active](#active-project)\nand the [compute](#compute-project) projects.\n\nBigQuery process metadata not showing\n-------------------------------------\n\nThe following issue occurs when you open the table details pane, which doesn't\nshow all the details like the SQL statement or the `Process type` property.\nThis happens even though the data lineage displays properly.\n\nThis can happen when you don't have permissions to see metadata in the\n[compute project](#compute-project).\n\nExample:\n\n- BigQuery source table: `docs-source.dataset.source-001`\n- BigQuery target table: `docs-target.dataset.target-001`\n- Data lineage between `docs-source.dataset.source-001` and `docs-target.dataset.target-001` in [compute project](#compute-project) `docs-compute`\n- You have the [Data Lineage Viewer role](/iam/docs/understanding-roles#datalineage.viewer) for [active](#active-project) and [compute](#compute-project) `docs-compute` projects.\n\nClicking the BigQuery process details displays the following message\nin the Google Cloud console: \n\n```\nYou don't have permission to view BigQuery process metadata in project X.\n```\n**Figure 5.** Example of BigQuery process details not showing in BigQuery UI.\n\nTo resolve this issue, grant the user `bigquery.jobs.get` permission\n(for example included in [BigQuery Resource Viewer](/iam/docs/understanding-roles#bigquery.resourceViewer)\nrole) in the [compute project](#compute-project).\n\nBigQuery table details not showing\n----------------------------------\n\nThe following issue occurs when you open the table details pane, which shows\nonly the `Fully qualified name` property. This happens even though the\ndata lineage displays properly.\nThis can happen when you don't have all required permissions in the table's\n[storage projects](#storage-project).\n\nExample:\n\n- BigQuery table `docs-source.dataset.source-001`\n- BigQuery table `docs-target.dataset.target-001`\n- Data lineage between `docs-source.dataset.source-001` and `docs-target.dataset.target-001` with [compute project](#compute-project) `docs-compute`\n- You have the [Data Lineage Viewer role](/iam/docs/understanding-roles#datalineage.viewer) for the [active](#active-project) and [compute](#compute-project) `docs-compute` projects\n\nIn this case, when you click on BigQuery node details, you can see a\nmessage `Entry with this fully qualified name is not available in Dataplex\nUniversal Catalog or you do not have permissions to view it`.\n**Figure 6.** Example of BigQuery table details not showing in BigQuery UI.\n\nTo resolve this issue, grant the `bigquery.tables.get` permissions\n(for example included in [BigQuery Data Viewer role](/iam/docs/understanding-roles#bigquery.dataViewer)) in the [storage project](#storage-project)."]]
