Data Development-Dataphin(Dataphin)-阿里云帮助中心

This topic describes common issues related to data development.

Why can't I add an upstream dependency when I configure scheduling parameters for a logical dimension table?
The dimension has been submitted, but the logical fact table cannot be associated with the logical dimension table
An error occurs when I query a data table
An error occurs when I publish a logical dimension table
How do I write variables in a code task?
Can I reference the attributes of an existing logical fact table when I add fact attributes to a logical fact table?
Does Dataphin support adding a statistic granularity to a generated derived metric?
Can a logical dimension table be used as the source table for a logical fact table?

Why can't I add an upstream dependency when I configure scheduling parameters for a logical dimension table?

Check the following items:

The name of the ancestor node is valid. The output name of an ancestor node must be in the project_name.table_name format.
The ancestor node is submitted. You can add only submitted nodes as upstream dependencies.

If you still cannot add the upstream dependency after you check these items, submit a ticket.

A submitted logical dimension table cannot be used as an associated dimension for a logical fact table

A logical fact table can be associated with a dimension only if the following two conditions are met:

The system automatically generates logical dimension tables only for common dimensions and common (hierarchical) dimensions.
The logical dimension table is in the submitted state.

An error occurs when I query a data table

You can query a data table in one of the following ways:

To query a logical table, run the following command.
```
SELECT * FROM LD_newretail.dws_xnwd_03 WHERE ds='${bizdate}';
```
Where:
- dws_xnwd_03 is the logical table.
- LD_newretail is the English name of the business segment.
To query a physical table, run the following command.
```
SELECT * FROM beijing_ast.ads_perform_taok_all_goods_day WHERE ds='${bizdate}';
```
Where:
- ads_perform_taok_all_goods_day is the physical table.
- beijing_ast is the English name of the project.

An error occurs when I publish a logical dimension table

Publish the logical dimension table and the dimension at the same time.

How do I write variables in a code task?

The format for referencing variables in a code task is as follows:

If you use the Dev-Prod development mode and need to publish the code task to the production project, use the following format: ${Prod_project_English_name}.physical_table or ${Prod_business_segment_English_name}.logical_table.
If you use the Dev-Prod development mode and write a task using an ad hoc query, use one of the following formats:
- To reference a table in the production project, use the following format: ${Prod_business_segment_English_name}.logical_table or ${Prod_project_English_name}.physical_table.
- To reference a table in the development project, use the following format: ${Dev_business_segment_English_name}.logical_table or ${Dev_project_English_name}.physical_table.
If you use the Basic development mode and write a task using an ad hoc query, use the following format: ${Basic_project_English_name}.physical_table or ${Basic_business_segment_English_name}.logical_table.

Can I reference the attributes of an existing logical fact table when I add fact attributes to a logical fact table?

No, this is not supported.

Does Dataphin support clearing multiple partitions of a data table by running a single SQL statement?

No. You can run the alter table table_name drop [IF EXISTS] PARTITION partition_space; command to delete partitions one by one. To delete many partitions, you must create the table again.

Does Dataphin support adding a statistic granularity to a generated derived metric?

No. You must create the derived metric again. For more information, see Create a derived metric.

Can a logical dimension table be used as the source table for a logical fact table?

No. The main source table of a logical fact table must be a physical table.

Can a composite metric have a WHERE expression to filter data?

No. A composite metric is expressed as a numerator and a denominator.

Error Message	Cause	Solution
DPN.Bbox.Any	Internal system error.	Submit a ticket.
DPN.Bbox.MetaCenterServiceError	The global meta service is unavailable.
DPN.Bbox.ModelNotFound	The model cannot be found using the model ID.
DPN.Bbox.ServerError	Internal system error.
DPN.Commons.InternalError	Internal system error.
DPN.Os.InternalError	DPN.Os.InternalError
DPN.TaskScheduler.Api.AccessTokenNotFound	Internal system error.
DPN.TaskScheduler.Global.UncategorizedError	Internal error in the CDN mapping system.
DPN.TaskScheduler.Util.GsonDeserializeError	An error occurred during deserialization using Gson.
DPN.Bbox.AttributeMissing	The field that identifies the statistical period of the atomic metric was deleted. Therefore, the system cannot find the corresponding logical field using the ID of the statistical period identifier field.	Reset the field that identifies the statistical period of the atomic metric. For more information, see Create an atomic metric.
DPN.Bbox.CatalogNotFound	The common English name of the business segment or project is incorrect.	Check whether the common English name of the business segment or project in the SQL code is misspelled. The placeholder for the common English name of a project is `${project_common_English_name}`. The placeholder for the common English name of a business segment is `${business_segment_common_English_name}`.
DPN.Bbox.DimensionNotFound	The system cannot find the dimension using the dimension ID.	Check whether the dimension exists: If the dimension was deleted, modify the current task object and submit or publish it again. If the dimension was unpublished, publish or submit the dimension again. If you still cannot find the dimension using the dimension ID after you perform these operations, submit a ticket, or contact Dataphin helpdesk for assistance. You can also scan the following QR code to join the DingTalk group and provide feedback.
DPN.Bbox.FieldNotFound	The system cannot find the field using the field name.	Check whether the field exists in the corresponding model.
DPN.Bbox.IllegalSql	The SQL code segment is invalid.	Check whether the SQL segment in the error message is valid within the entire SQL statement. For more information about the MaxCompute syntax that Dataphin supports, see Common commands.
DPN.Bbox.LogicModelException	The definition of the logical model violates one or more rules.	Modify the model based on the error message provided by the system.
DPN.Bbox.MetadataNotFound	The metadata cannot be found using the table name.	Check whether the table name is misspelled and whether the table exists. For more information, see Search for data.
DPN.Bbox.PublishFail	The job failed to publish.	Troubleshoot the issue based on the error message in the publishing records.
DPN.Bbox.UnsupportedCatalogVariable	The common English name of the business segment or project that is automatically replaced by the system is incorrect.	Modify the variable name in the SQL statement to the common English name of the business segment or project. The placeholder for the common English name of a project is `${project_common_English_name}`. The placeholder for the common English name of a business segment is `${business_segment_common_English_name}`.
DPN.ComputeEngine.ConfigRepeat	The configuration of the compute engine that you are creating or editing is the same as an existing compute engine configuration.	Modify the compute engine configuration. For more information, see Compute engines.
DPN.ComputeEngine.MaxComputeAkNotMatchCurrentTenant	The AccessKey of the MaxCompute compute engine does not belong to the Alibaba Cloud account of the current Dataphin tenant.	Check whether the AccessKey of the MaxCompute compute engine is correct. Important The MaxCompute project and the Dataphin instance must belong to the same Alibaba Cloud account.
DPN.ComputeEngine.MaxComputeAkQueryMainAccountError	An exception occurred when the system retrieved the Alibaba Cloud account of the AccessKey for the MaxCompute compute engine.	Check whether the AccessKey of the MaxCompute compute engine is correct.
DPN.DataSource.UrlSsrfCheckFailed	Access to the internal system is not allowed.	Check the URL configuration of the data source.
DPN.Os.CatalogNotFound	The catalog specified before the table was not found.	Check the following items: Check whether the Dataphin project or business segment exists. Check the variable reference format in the query statement. The correct formats are `${project_common_English_name}.physical_table` and `${business_segment_common_English_name}.logical_table`.
DPN.Os.ColumnAmbiguous	The field in the SQL code is ambiguous.	Add the table name before the field name or modify the SQL code.
DPN.Os.ColumnAuthCheckFailed	You do not have permissions for the field.	Request permissions for the field. For more information, see Request, renew, and revoke table permissions.
DPN.Os.ColumnNotFound	The field was not found.	The cause of the error can be analyzed from the following two perspectives: If the error occurs when you submit the node, check whether the table exists in the development environment. If an error occurs during Job publication, verify that the table exists in the production environment.
DPN.Os.SqlParserFailed	The system failed to parse the SQL statement.	Check for syntax errors in the SQL statement. For more information about the MaxCompute syntax that Dataphin supports, see Common commands.
DPN.Project.DisplayNameDuplicated	The name of the project that you are creating or editing is the same as an existing project name.	Change the project name. For more information, see Add a project member.
DPN.Project.NoPermission	The current member does not have administrative permissions for any project.	Contact a super administrator or another project administrator to add the member as an administrator of a project.
DPN.Project.ParameterError	The project parameters are invalid.	Check the invalid parameters returned by the system.
DPN.Project.ProjectComputeEngineValidateFailed	The system failed to verify the compute engine when the project was created.	Analyze the cause of the error from the following two aspects: Check the connectivity of the compute engine. For more information, see Network connectivity solutions. Verify that the compute source configuration is correct.
DPN.Search.GetDocumentError	An error occurred when the system wrote the code search data.	You can ignore this error if it does not affect the main process of the node. If the error affects the main process of the node, check the node code.
DPN.Search.GetDocumentError
DPN.Search.GetIndexError
DPN.Search.SaveDocumentError
DPN.Search.SearchDocumentsError
DPN.TaskScheduler.Api.RequestError	An error occurred when a remote request was sent.	The error may be caused by a server-side network issue. We recommend that you retry. If the error persists after you retry, contact Dataphin helpdesk for assistance.
DPN.TaskScheduler.Client.ApiError	An error occurred when the API of the CDN mapping system was called. For more information about the cause, see the error details.	Find the solution based on the error code in the error details.
DPN.TaskScheduler.Node.IllegalNodeIdFormat	The format of the specified node ID is incorrect. The format must be `[n_number]`.	Check the format of the node ID and initiate the call again. If the error persists, submit a ticket.
DPN.TaskScheduler.Node.NodeNotFoundByIdAndTenantId	The node cannot be found using the node ID.	Check whether the node ID is correct, or whether the node that corresponds to the node ID has been deleted or unpublished.
DPN.TaskScheduler.Node.NodeNotFoundByNodeId	The node cannot be found using the node ID.
DPN.TaskScheduler.Node.NodeNotFoundByOutputName	The node cannot be found using the output name.	Check whether the output name of the node is correct, or whether the node that corresponds to the output name has been deleted or unpublished.
DPN.TaskScheduler.Node.NodeNotFoundByOutputNameAndTenantId	The node cannot be found using the output name.
DPN.TaskScheduler.Node.NodeOutputNameEmpty	The output name of the node is empty.	Specify an output name for the node. For an SQL node, we recommend that you use the `[project_name].[table_name]` format. Important The output name of a node must be unique within the system.
DPN.TaskScheduler.Node.NodeOutputNameOccupied	The output name of the node is already used.	The specified output name is used by another node. For an SQL node, we recommend that you use the `[project_name].[table_name]` format. Important The output name of a node must be unique within the system.
DPN.TaskScheduler.Node.NodeToDeleteContainsDownstreams	A downstream dependency is detected for the node that you want to delete.	Remove the dependency of the descendant node on the current node and retry.
DPN.TaskScheduler.Node.OutputNameToUpdateContainsDownstream	A downstream dependency is detected for the output name that you want to modify.	Remove the dependency of the descendant node on the output name of the current node and retry.
DPN.TaskScheduler.Resource.ResourceNotFoundByResourceCode	The resource cannot be found using the resource name. The resource name may be invalid, the resource may have been deleted, or the resource service may be unavailable.	Make sure that the resource exists in the current project and that the resource is referenced in the correct format. The format is `@resource_reference{"[resourcecode]"};`.
DPN.TaskScheduler.Task.IllegalTaskIdFormat	The format of the specified task ID is incorrect.	Check whether the task ID is in the `[t_number]` format and initiate the call again.
DPN.TaskScheduler.Task.TaskNotFoundByTaskId	The instance cannot be found using the instance ID. Check whether the instance has been deleted or whether the specified parameter is correct.	Make sure that the instance exists before you perform the operation. If you perform the operation on a page, you can refresh the page and try again. Instances are periodically deleted. The retention policies for instances are as follows: Recurring instances and their operational logs are retained for 15 days. One-time instances, data backfill instances, and their operational logs are retained permanently.
DPN.TaskScheduler.Task.TaskNotFoundByTaskIdAndTenantId
DPN.TaskScheduler.Task.TaskRunning	You cannot rerun a running instance.	Rerun the instance after it finishes running. You can rerun only instances that are in the successful or failed state.
DPN.TaskScheduler.Task.TaskToKillHasFinished	You can only stop tasks that are running.	The instance has finished running. You do not need to stop it.
DPN.TaskScheduler.Task.TaskToResumeNotPaused	You cannot resume an instance that is not paused.	Scheduling cannot be resumed because the task is not paused.
DPN.TaskScheduler.Tenant.DatasourceNotFoundById	The data source cannot be found using the data source ID. The data source may have been deleted.	Check whether the data source exists, or contact the node owner to check the datasource config of the node.
DPN.TaskScheduler.Tenant.FetchProjectDatasourceError	The system failed to retrieve the compute engine of the project. The Dataphin compute engine service may be temporarily inaccessible.	The system failed to retrieve the compute engine of the project. The Dataphin compute engine service may be temporarily inaccessible. Contact Dataphin helpdesk for assistance.
DPN.TaskScheduler.Tenant.FetchTenantDatasourceError
DPN.TaskScheduler.Tenant.InvalidTenantId	The current tenant is unavailable. The service may have expired, or Dataphin is not activated.	Activate or renew Dataphin. For more information, see Activate Dataphin or Renewal.