Teradata SQL Error and Failure Codes from Error 6857 To 6868

6857 Table ’%VSTR’ in EXCEPT list not in database being RESTORED.
Explanation: If the databasename is referenced on an table name in the EXCEPT list, it must be identical to the database referenced on the RESTORE clause.
Generated By: OPT modules.
For Whom: End User.
Remedy: Compare the list of the tables in the EXCEPT list. If a table name is qualified with a database name, and that
database name does not match the database name on the RESTORE, either omit the qualified table name, or correct the
database name.

6858 Table ’%VSTR’ is not in RESTORE state
Explanation: The table being restored with a WHERE QUALIFIED clause does not have a Field 4 in the table header, or
the Field 4 does not contain a partition list. One way this could occur is doing a BUILD DATA TABLES command.
Generated By: OPT modules.
For Whom: End User.
Remedy: Rerun the RESTORE

6860 Response exceeds 64K bytes and alternate parcel header was not requested.
Explanation: The server must return the response in alternate parcel Header as the body is >64KB but no request was
sent by the client using the alternate parcel header.
Generated By: Pardrivr module
For Whom: End-user
Remedy: The client must indicate its acceptance of the alternate Parcel headers by submitting a request using this format.
Either re-submit the request using the alternate parcel header format if it is supported for the client software or handle the error code received.

6862 A CAST with specified source and target exists
Explanation: A CAST with the specified source and target data types already exists.
Generated By: RES modules.
For Whom: End User.
Remedy: If CREATE CAST is desired, there is no need to submit the query.

6863 Cast with specified source and target does not exist
Explanation: A CAST with the specified source and target data types does not exist.
Generated By: RES modules.
For Whom: End User.
Remedy: If DROP CAST is desired, there is no need to submit the query.

6864 The %VSTR routine must be UDF.
Explanation: A routine is expected to be User Defined Function. — The TO SQL routine specified in a CREATE TRANSFORM
statement must be a UDF. — The CAST routine specified in a CREATE/REPLACE CAST statement must be a UDF if
the Source data type for the CAST is pre-defined type and the Target data type is Distinct or Structured UDT type.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct and re-submit the query.

6865 The %VSTR routine must be UDF or UDM.
Explanation: A routine is expected to be User Defined Function or User Defined Method. — The From SQL routine specified in a CREATE/REPLACE TRANSFORM statement for Distinct or Structured UDT must be UDF or UDM. — The
Ordering routine specified in a CREATE/REPLACE ORDERING statement for Distinct or Structured UDT must be UDF or
UDM. — The Cast routine specified in a CREATE/REPLACE CAST DDL statement must be a UDF or UDM when the
Source data type of the Cast is Distinct or Structured UDT.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct and re-submit the query.

6866 The %VSTR routine must be deterministic.
Explanation: A routine is expected to be deterministic. For instance, the From SQL routine specified in a CREATE
TRANSFORM statement must be deterministic.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct and re-submit the query.

6867 The %VSTR routine has invalid number of parameters
Explanation: A routine has invalid number of parameters: –The TO SQL UDF of a UDT Transform Group must have
only one declared parameter. –The FROM SQL routine of a UDT Transform Group must have only one declared parameter,
if the routine is a UDF. –The FROM SQL routine of a UDT Transform Group must not have any declared parameter, if the
routine is a UDM. –The Cast routine specified in a CREATE/REPLACE CAST statement must declare only one parameter
if the Cast routine is a UDF. The Cast routine must not declare any parameter if the Cast routine is a UDM (the system will automatically generate the SELF parameter for the UDM).
Generated By: RES modules.
For Whom: End User.
Remedy: Specify a routine with the correct number of parameter(s) and re-submit the query.

6868 The %FSTR routine contains invalid parameter data type. %VSTR
Explanation: A routine has invalid parameter type. For UDT TRANSFORM: –The parameter type of the TO SQL routine
of a UDT Transform Group must be a predefined type. –The result parameter type of the TO SQL routine of a UDT
Transform Group must be the UDT. –If the FROM SQL routine of a UDT Transform Group is a UDF, the parameter type of
the UDF must be the UDT. –The result data type of the FROM SQL routine of a UDT Transform Group must be a predefined
type. –If both TO SQL and FROM SQL routines are declared for a UDT Transform Group, the parameter type of
the TO SQL routine must be the same as the result type of the FROM SQL routine. For UDT ORDERING –For MAP style
ordering, if the ordering routine is UDF then the UDF must declare only one parameter and the parameter data type must
be the UDT for which the ordering is created. –For MAP style ordering, if the ordering routine is UDM then the UDM must
contain an empty parameter list (system will automatically generate a SELF parameter for the UDM). –For RELATIVE
style ordering, if the ordering routine is UDF then the UDF must have two parameters and the data type of the parameters must be the UDT for which the ordering is created. –For RELATIVE style ordering, if the ordering routine is UDM then the
UDM must have one parameter and the parameter data type must be the UDT for which the ordering is created. For UDT
CAST: –The parameter data type of a Cast routine must match the Source data type of the Cast. –If the Source data type of
a Cast is UDT, the Cast routine parameter must match the Source UDT. –The Result data type of a Cast routine must match
the Target data type of the Cast.
Generated By: RES modules.
For Whom: End User.
Remedy: Specify a routine with the correct parameter data type(s) and re-submit the query.

Above are list of Teradata Errors or Failure Codes from Error 6857 To 6868 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 *