Commonly Encountered Errors in Hyper-Q

The purpose of this article is to address common and easily fixable errors in Hyper-Q. In each part of this article there will be an explanation and remediation steps for this type of error. 

DTM8031 : Object not found or no permission 

This error is an easy one as the error message is quite informative. Just as the message says, it indicates a missing object definition. In this case, please retrieve the definition from the source Teradata system using a SHOW TABLE, SHOW VIEW, SHOW MACRO, or SHOW PROCEDURE command. 

After this, create the definition using Hyper-Q as well as any dependent objects that may be needed. 

 

DTM8591: Statistics does not exist.

Teradata statistics statements usually reference a column. In this case, Hyper-Q automatically knows what table and column to collect statistics on. However, in some cases, there may be no preexisting statistics on an object and no column referenced by the statistic statement. In this case, please run the following statement against the source cloud data warehouse to remediate the issue:

Synapse:

create statistics Sample_Statistics_Name on SchemaName.TableName (Target_Column);

update statistics SchemaName.TableName (Sample_Statistics_Name);

Note: In order to choose a column to collect statistics on, please reference the table that is the target of the Collect Statistics statement by running a SHOW TABLE command. 

 

DTM8193: Syntax error before: 'EOL'

This error is encountered in macros and stored procedures. It indicates that the definition is truncated and needs to be refreshed. This can be confirmed by running SHOW MACRO or SHOW PROCEDURE on the object in question. To remediate this error, please retrieve the original object definition from Teradata or from a Datometry support engineer and recreate it via Hyper-Q. 

 

DTM3103 : Cannot insert the value NULL into column 

In Teradata table syntax, columns can have a NOT NULL feature that prevents NULL data from being inserted into these fields. If this error is encountered, it indicates that the result set for a UPDATE or INSERT query is returning NULL for at least one column with this NOT NULL feature. To validate this, run the SELECT statement that is attempting to populate a table or update a field to examine the results. Once a partial or full source of the NULL values is identified, please work with a DBA or process SME to resolve the issue. 

 

DTM3031 : The datepart tzoffset is not supported by date function datepart for data type datetime

This issue is often encountered in complex statements with many nested views. If the statement that caused this error has more than one source view, run select count(*) statements against the dependent views involved to determine where the error came originates from. Continue this process until the view causing the issue is identified. To resolve the issue, simply re-run the view definition once and validate that a select count(*) can be run against it. All these analysis and remediation steps must be run through Hyper-Q.

 

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.