15.00 - 6868 The %FSTR routine contains invalid parameter data type. %VSTR - Teradata Database

Teradata Database Messages

Product
Teradata Database
Release Number
15.00
Content Type
Programming Reference
Publication ID
B035-1096-015K
Language
English (United States)

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.