Teradata SQL Error and Failure Codes from Error 3612 To 3626

SQLServerF1_Header_Small

3612 Incorrect use of a subquery %VSTR.
Explanation: A subquery occurred where an expression was expected.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit request.

3613 Dump/Restore, no hashed nonfallback tables found.
Explanation: Selected AMP Dump or Restore with the all tables option found no qualified tables.
Generated By: OPT modules.
For Whom: Dump and Restore Program.
Remedy: Correct the statement and resubmit the request.

3614 Statement permitted only during FastLoad or MLoad.
Explanation: CHECKPOINT LOADING or END LOADING was issued outside of a Fast Load or MLoad Session.
Generated By: OPT modules.
For Whom: Host Utility Fast Load or MLoad.
Remedy: Correct the statement and resubmit the request.

3615 Statement not permitted during Fast Load.
Explanation: Only BT, CHECKPOINT LOADING, END LOADING, ET, and INSERT are permitted during Fast Load.
Generated By: OPT modules.
For Whom: Host Utility Fast Load.
Remedy: Correct the statement and resubmit the request.

3616 Wrong table referenced for INSERT during Fast Load.
Explanation: INSERT referenced a table other than that specified by BEGIN LOADING during a Fast Load session.
Generated By: OPT modules.
For Whom: Host Utility Fast Load.
Remedy: Correct the statement and resubmit the request.

3617 FORMAT ’%VSTR’ does not match the datatype.
Explanation: The user tried to use a numeric/graphic format with a character type, a character/graphic format with a
numeric type, or character/numeric format with a graphic type. The mismatch may be within a single data descriptor as in
(CHAR(3), FORMAT’999’) or may be the result of applying a FORMAT clause without an explicit type declaration to an
expression which has an inappropriate type, as in (Year – 1900)(FORMAT ’XX’). Note that the FORMAT displayed in the
error message may not show in the users source statement if the FORMAT was an attribute of a VIEW definition.
Generated By: SYN and OPT modules.
For Whom: End User.
Notes: “x(CHAR(3), FORMAT ’999’)” is invalid. If this is a type conversion, the user probably wanted “(x(FORMAT
’999’))(CHAR(3))”.
Remedy: Re-specify the format.

3618 Expression not allowed in Fast Load Insert, column %VSTR.
Explanation: FastLoad does not permit expressions in the INSERT during Fast Load.
Generated By: OPT modules.
For Whom: Host Utility Fast Load.
Remedy: Correct the statement and resubmit the request.

3619 Only one level of data type conversion allowed, column %VSTR.
Explanation: FastLoad does not permit USING data types, which require more than one level of conversion.
Generated By: OPT modules.
For Whom: Host Utility Fast Load.
Remedy: Correct the statement and resubmit the request.

3620 Cannot create nonfallback table ’%VSTR’ with AMP down.
Explanation: The user tried to create a nonfallback table while an AMP is down.
Generated By: OPT modules.
For Whom: End User.
Remedy: Wait until all AMPs are up.

3621 Cannot load table %TVMID unless secondary indexes and join indexes are removed.
Explanation: BEGIN LOADING referenced a table that has secondary indexes. They must be removed and, if desired,
created after the table is loaded.
Generated By: OPT modules.
For Whom: Host Utility Fast Load.
Remedy: DROP secondary indexes and join indexes on table to be loaded.

3622 The user cannot perform that operation on DATEs.
Explanation: An operation on a DATE data type does not make sense, for example, trying to SUM a column of DATEs.
Generated By: OPT modules.
For Whom: End User.
Remedy: Rephrase the request and try again.

3623 The user cannot use COMPRESS on a primary index column or partitioning expression column.
Explanation: A primary index column or partitioning expression column specifies the COMPRESS option.
Generated By: GEN modules.
For Whom: End User.
Remedy: Rephrase the request and try again.

3624 There are no statistics defined for the table.
Explanation: There are no statistics defined for the table referenced in a COLLECT STATISTICS or HELP STATISTICS statement.
Generated By: OPT modules.
For Whom: End User.
Notes: This error may be caused by a misspelled name of a table.
Remedy: Resubmit the statement with a valid table name.

3625 GROUP BY and WITH…BY clauses may not contain aggregate functions.
Explanation: The given SELECT operation contains a GROUP BY, or a WITH…BY clause that uses aggregate function
references. This is not legal.
Generated By: OPT modules.
For Whom: End User.
Remedy: Resubmit statement with a valid GROUP BY or BY clause.

3626 Internal error: WITH BY clause contains multiple tables.
Explanation: The given SELECT operation contains a WITH…BY grouping clause that contains multiple table references.
This is an internal check for the case — this should not be possible.
Generated By: OPT modules.
For Whom: System Support Representative.
Remedy: Save a test case that causes the failure and contact your support representative.

Above are list of Teradata Errors or Failure Codes from Error 3612 To 3626 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *