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

Frequently asked questions about data development.

1. Why can't I add ancestor nodes when I configure scheduling parameters for a logical dimension table?
2. Why can't a logical fact table use a submitted logical dimension table as an associated dimension?
3. An error is reported when I query a data table.
4. An error is reported when I publish a logical dimension table.
5. How do I define variables in a code task?
6. Can I reference the attributes of an existing logical fact table when I add fact attributes to a logical fact table?
7. Does Dataphin support clearing multiple partitions of a data table by running a single SQL statement?
8. Does Dataphin support adding a statistic granularity to a generated derived metric?
9. Does the system support using a logical dimension table as the source table for a logical fact table?
10. Can a WHERE expression be used in a composite metric to filter data?

1. Why can't I add ancestor nodes when I configure scheduling parameters for a logical dimension table?

Check the following items:

Check whether the name of the ancestor node is standard. The output name of an ancestor node must be in the Project name.Data table name format.
Check whether the ancestor node is submitted. You can add only submitted nodes as ancestor nodes.

If you still cannot add ancestor nodes after you check the preceding items, submit a ticket.

2. A dimension is submitted, but a logical fact table cannot use the logical dimension table as an associated dimension.

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

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

3. An error is reported when I query a data table.

You can query a data table in the following ways:

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

4. An error is reported when I publish a logical dimension table.

The logical dimension table and the dimension must be published at the same time.

5. How do I define variables in a code task?

Use the following formats to reference variables in a code task:

If you use the Dev-Prod development mode and need to publish a code task to the Prod project, reference variables in the ${English name of the Prod project}.physical_table or ${English name of the Prod business category}.logical_table format.
If you use the Dev-Prod development mode and write a task by running an ad hoc query, reference variables in one of the following formats:
- To reference a table in the Prod project, use the ${English name of the Prod business category}.logical_table or ${English name of the Prod project}.physical_table format.
- To reference a table in the Dev project, use the ${English name of the Dev business category}.logical_table or ${English name of the Dev project}.physical_table format.
If you use the Basic development mode and write a task by running an ad hoc query, reference variables in the ${English name of the Basic project}.physical_table or ${English name of the Basic business category}.logical_table format.

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

No, this operation is not supported.

7. 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 recreate the table.

8. 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.

9. Does the system support using a logical dimension table as the source table for a logical fact table?

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

10. Can a WHERE expression be used in a composite metric to filter data?

No. The expression for a composite metric uses a numerator/denominator format.

Error message	Cause	Solution
DPN.Bbox.Any	An internal system error occurred.	Submit a ticket.
DPN.Bbox.MetaCenterServiceError	The global meta service is unavailable.
DPN.Bbox.ModelNotFound	The model cannot be found for the specified model ID.
DPN.Bbox.ServerError	An internal system error occurred.
DPN.Commons.InternalError	An internal system error occurred.
DPN.Os.InternalError	DPN.Os.InternalError
DPN.TaskScheduler.Api.AccessTokenNotFound	An internal system error occurred.
DPN.TaskScheduler.Global.UncategorizedError	An internal error occurred in the CDN mapping system.
DPN.TaskScheduler.Util.GsonDeserializeError	An error occurred when the system used Gson to deserialize data.
DPN.Bbox.AttributeMissing	The field that identifies the statistical period of the atomic metric was deleted. As a result, the system cannot find the corresponding logical field based on the field ID.	Reset the field that identifies the statistical period for the atomic metric. For more information, see Create an atomic metric.
DPN.Bbox.CatalogNotFound	The common English name of the business category or project is invalid.	Check whether the common English name of the business category or project in the SQL code is misspelled. The placeholder for the common English name of a project is `${common English name of the project}`. The placeholder for the common English name of a business category is `${common English name of the business category}`.
DPN.Bbox.DimensionNotFound	The system cannot find the dimension for the specified dimension ID.	Check whether the dimension exists. If the dimension is deleted, modify the current task object and submit or publish the object again. If the dimension is unpublished, publish or submit the dimension again. If the dimension still cannot be found after you perform the preceding operations, submit a ticket or contact Dataphin helpdesk for assistance. You can also scan the following QR code with DingTalk to join the DingTalk group and provide feedback.
DPN.Bbox.FieldNotFound	The system cannot find the field for the specified field name.	Check whether the field exists in the model.
DPN.Bbox.IllegalSql	The SQL code segment is invalid.	Check whether the SQL segment in the error message is valid in the entire SQL statement. For more information about the MaxCompute SQL syntax that is supported by Dataphin, see Common commands.
DPN.Bbox.LogicModelException	The definition of the logical model violates a rule.	Modify the model based on the error message.
DPN.Bbox.MetadataNotFound	The metadata cannot be found for the specified table name.	Check whether the table name is misspelled and whether the table exists. For more information, see Search for data.
DPN.Bbox.PublishFail	Failed to publish the node.	Troubleshoot the issue based on the error message in the publishing record.
DPN.Bbox.UnsupportedCatalogVariable	The common English name of the business category or project that is automatically replaced by the system is invalid.	Modify the variable name in the SQL statement to the common English name of the business category or project. The placeholder for the common English name of a project is `${common English name of the project}`. The placeholder for the common English name of a business category is `${common English name of the business category}`.
DPN.ComputeEngine.ConfigRepeat	The configurations of the compute engine that you want to create or edit are identical to existing configurations in the system.	Modify the configurations of the compute engine. For more information, see Compute engines.
DPN.ComputeEngine.MaxComputeAkNotMatchCurrentTenant	The AccessKey pair of the MaxCompute compute engine does not belong to the Alibaba Cloud account in which Dataphin resides.	Check whether the AccessKey pair of the MaxCompute compute engine is valid. Important The MaxCompute project and the Dataphin instance must belong to the same Alibaba Cloud account.
DPN.ComputeEngine.MaxComputeAkQueryMainAccountError	An error occurred when the system retrieved the Alibaba Cloud account that corresponds to the AccessKey pair of the MaxCompute compute engine.	Check whether the AccessKey pair of the MaxCompute compute engine is valid.
DPN.DataSource.UrlSsrfCheckFailed	You are not allowed to access internal systems.	Check the URL configuration of the data source.
DPN.Os.CatalogNotFound	The catalog specified before the table name cannot be found.	Check the following items: Check whether the Dataphin project or business category exists. Check whether the variable in the query statement is in the `${common English name of the project}.physical_table` or `${common English name of the business category}.logical_table` format.
DPN.Os.ColumnAmbiguous	The field in the SQL code is ambiguous.	Add the name of the table to which the field belongs before the field name, or modify the SQL code.
DPN.Os.ColumnAuthCheckFailed	You do not have permissions for the field.	Apply for permissions for the field. For more information, see Apply for, renew, and revoke permissions on a table.
DPN.Os.ColumnNotFound	The field is not found.	Analyze the cause of the error from the following aspects: If the error is reported when you submit a node, check whether the table exists in the development environment. If the error is reported when you publish a node, check whether the table exists in the production environment.
DPN.Os.SqlParserFailed	Failed to parse the SQL statement.	Check whether the SQL statement has a syntax error. For more information about the MaxCompute SQL syntax that is supported by Dataphin, see Common commands.
DPN.Project.DisplayNameDuplicated	The name of the project that you want to create or edit is identical to an existing project name in the system.	Change the project name. For more information, see Add a project member.
DPN.Project.NoPermission	The current member does not have administrator permissions for any project.	Contact a super administrator or another project administrator to add the member as an administrator for a project.
DPN.Project.ParameterError	The project parameter is invalid.	Identify the cause based on the invalid parameter returned in the error message.
DPN.Project.ProjectComputeEngineValidateFailed	Failed to verify the compute engine when the project was created.	Analyze the cause of the error from the following aspects: Check the network connectivity of the compute engine. For more information, see Network connectivity solutions. Check whether the configurations of the compute engine are valid.
DPN.Search.GetDocumentError	An error occurred when the system wrote the data that was retrieved based on the code.	You can ignore this error if it does not affect the main node process. If the main node process is affected, troubleshoot 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.	A network issue may have occurred on the server. Retry the request. If the error persists, 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, see the error details.	Find a solution based on the error code in the error details.
DPN.TaskScheduler.Node.IllegalNodeIdFormat	The format of the node ID is invalid. The node ID must be in the `[n_Number]` format.	Check the format of the node ID and call the operation again. If the error persists, submit a ticket.
DPN.TaskScheduler.Node.NodeNotFoundByIdAndTenantId	The node cannot be found for the specified node ID.	Check whether the node ID is valid, or whether the node has been deleted or unpublished.
DPN.TaskScheduler.Node.NodeNotFoundByNodeId	The node cannot be found for the specified node ID.
DPN.TaskScheduler.Node.NodeNotFoundByOutputName	The node cannot be found for the specified output name.	Check whether the output name of the node is valid, or whether the node has been deleted or unpublished.
DPN.TaskScheduler.Node.NodeNotFoundByOutputNameAndTenantId	The node cannot be found for the specified output name.
DPN.TaskScheduler.Node.NodeOutputNameEmpty	The output name of the node is empty.	Specify the node output name. For SQL tasks, the recommended format is `[project_name].[table_name]`. Important The output name of a node must be unique in the system.
DPN.TaskScheduler.Node.NodeOutputNameOccupied	The output name of the node is already used.	The specified node output name is already in use by another task. For SQL tasks, the recommended output name format is `[ProjectName].[TableName]`. Important The output name of a node must be unique in 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 try again.
DPN.TaskScheduler.Node.OutputNameToUpdateContainsDownstream	A downstream dependency is detected for the output name of the node that you want to modify.	Remove the dependency of the descendant node on the output name of the current node and try again.
DPN.TaskScheduler.Resource.ResourceNotFoundByResourceCode	The resource cannot be found for the specified 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 valid format. The valid format is `@resource_reference{"[resourcecode]"}.`.
DPN.TaskScheduler.Task.IllegalTaskIdFormat	The format of the task ID is invalid.	Check whether the task ID is in the `[t_Number]` format and call the operation again.
DPN.TaskScheduler.Task.TaskNotFoundByTaskId	The instance cannot be found for the specified instance ID. The instance may have been deleted, or the specified parameter may be invalid.	Make sure that the instance exists before you perform the operation. If you perform the operation in the console, you can refresh the page and try again. Instances are periodically deleted. Instance retention policy: Recurring instances and their run logs are retained for 15 days. One-time instances and data backfill instances and their run logs are permanently retained.
DPN.TaskScheduler.Task.TaskNotFoundByTaskIdAndTenantId
DPN.TaskScheduler.Task.TaskRunning	You cannot rerun a running instance.	Rerun the instance after it stops running. You can rerun only instances that are in the Successful or Failed state.
DPN.TaskScheduler.Task.TaskToKillHasFinished	You cannot stop tasks unless they are in a running status.	The instance has stopped running. You do not need to stop the instance.
DPN.TaskScheduler.Task.TaskToResumeNotPaused	You cannot resume an instance that is not paused.	The node is not paused. You do not need to resume the scheduling.
DPN.TaskScheduler.Tenant.DatasourceNotFoundById	The data source cannot be found for the specified 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 compute engine service of Dataphin may be temporarily unavailable.	The system failed to retrieve the compute engine of the project. The compute engine service of Dataphin may be temporarily unavailable. Contact Dataphin helpdesk for assistance.
DPN.TaskScheduler.Tenant.FetchTenantDatasourceError
DPN.TaskScheduler.Tenant.InvalidTenantId	The current tenant is inactive. The service may have expired, or Dataphin has not been activated.	Activate or renew Dataphin. For more information, see Activate Dataphin or Renewal.