ML Engine Error Messages - Teradata Vantage

Teradata Vantage™ User Guide

Product
Teradata Vantage
Release Number
1.1
Published
May 2020
Language
English (United States)
Last Update
2020-05-28
dita:mapPath
ioz1543440393126.ditamap
dita:ditavalPath
jsj1481748799576.ditaval
dita:id
B700-4002
lifecycle
previous
Product Category
Teradata Vantage
Some ML Engine function names have changed. To map an error message function name with its new function name, see ML Engine Analytic Function Mapping.
Error message text contains an error number, universally unique identifier (UUID), error tag, and error text.
  • UUID is a unique identifier. As such, the UUID shown in your error message will not be the same as what appears in the table below.
  • Error tag MLE_ERR indicates the error was raised from ML Engine.
  • Error tag MLE_ERR_FFE indicates that the error was raised by the ML Engine connector.
  • Errors raised in the various functions executing in ML Engine are tagged with the function name.
  • The presence of the UUID with no error tags indicates that the error was raised in Advanced SQL Engine.
Error Message Text Description and Solution
*** Error 9134 Error: 9101 (63e825e9-3d89-4327-b1a1-00000000001f) MLE_ERR_FFE: G_IntervalHour is not supported A function attempted to return an unsupported datatype.

Solution: It may be possible to correct the function to use a decimal with defined precision, or use CAST in the SQL syntax to cast the datatype to a supported datatype. Otherwise, contact Teradata Customer Support.

*** Error 9134 QGIEC: 60104: (f8b385b9-8f12-4da2-9d63-00000000010e) asterdart0595 : FFMeta : MLE_ERR_FFE: Column user_id in sequenceInputBy argument clause does not exist in the table with Alias inputtable In the sequenceInputBy or UniqueId argument, the column name does not exist in the table given in the inputtable alias.

Solution: Check the column name to make sure it is in the table.

*** Error 9134 QGIEC: 60104: (ab64f100-dfd9-4dde-8f74-000000000044) MLE_ERR_FFE: Column col1 in sequenceInputBy argument clause does not exist in the given table In the sequenceInputBy or UniqueId argument, the column name does not exist in the table given.

Solution: Check the column name to make sure it is in the table.

*** Failure 9134 QGIE: 24582: (d30ab077-53b9-4c24-928a-000000000020) MLE_ERR: An internal error has occurred. Please contact support at Teradata. () An internal error may be encountered during query interactions.

Solution: Resubmit the query. If it fails again, contact Teradata Customer Support.

*** Failure 9134 QGIE: 24582: (4ec0fb9f-4cfe-4cbe-8f52-000000000661) tdap1513t2 : ExpDE : MLE_ERR: The supplied statement could not be completed due to an internal error at a database worker node. Please contact support at Teradata. () An internal error may be encountered during query interactions.

Solution: Resubmit the query. If if fails again, contact Teradata Customer Support.

*** Failure 9134 QGIE: 24582: (07955e5e-9b89-4f47-b91b-00000000aabc) MLE_ERR: The supplied statement could not be completed due to an internal error at the database coordinator node. Please contact support at Teradata. () An internal error may be encountered during query interactions.

Solution: Resubmit the query. If it fails again, contact Teradata Customer Support.

*** Error 9134 QGIE: 60104: (beea1fb3-4202-4e81-896c-0000000009db) tdap656t2 : ForeignFunctionMeta : MLE_ERR_FFE: Function function name cannot take input from a nested function. function name is the name of the function that cannot take input from a nested function.

Solution: Rewrite the SQL statement to place the results of the nested function into a derived table and let the outer function take its input from the derived table. See Limitation for an example.

*** Error 9134 QGInitiatorExportContract: 9101 (829113ff-e7ac-4179-b694-000000000018) MLE_ERR_FFE:Alias table alias appears more than once The same table alias was used more than once in a function invocation.

Solution: Resubmit the query with a different name for each table alias.

*** Error 9134 QGInitiatorImport: 6 (f743340f-d4ae-49d4-8bce-00000000001b) MLE_ERR_FFE: JsonElement element-name not found in function descriptor. Incomplete information in the function descriptor file.

Solution: Correct the function descriptor to supply the required information, or if the function descriptor came from Teradata, contact Teradata Customer Support.

*** Error 9134 QGInitiatorExportContract: 9101 (f743340f-d4ae-49d4-8bce-000000000019) MLE_ERR_FFE:Exception in processing the function descriptor: JsonElement element-name not found in function descriptor. Incomplete information in the function descriptor file.

Solution: Correct the function descriptor to supply the required information, or if the function descriptor came from Teradata, contact Teradata Customer Support.

*** Failure 9134 Error: 6 (d8264ce0-43a5-4dbd-a8a6-0000000009dd) MLE_ERR: Schema doesn't exist. HELP FOREIGN SCHEMA statement referenced a non-existent schema.

Solution: Correct the schema name and resubmit the query.

*** Failure 9134 Error: 6 (56567b0106-3fff-47a1-acbf-000000000168) MLE_ERR_FFE: Function 'FunctionName' not found. Please verify that the function is installed. HELP FOREIGN FUNCTION was invoked for a function that is not installed.

Solution: Verify the function is installed.

*** Failure 9134 Error: 6 (b41e68d0-0305-4f4d-8911-000000000df3) MLE_ERR_FFE: Function Alias name ('alias') exceeds the maximum length of 25 characters. A statement using a coprocessor function was written to refer to the function invocation with an alias name longer than the maximum supported length.

Solution: Resubmit the statement with the function invocation alias name no longer than 25 characters. A function invocation alias is the name that follows the closing parenthesis that follows the name of the function.

*** Failure 9134 Error 6: (d8264ce0-43a5-4dbd-a8a6-0000000009bc) QGEXECUTEFOREIGNQUERY: Cannot read hostname. There is a problem reading hostname from a file in /tmp/hostname in the Docker container.

Solution: Contact Teradata Customer Support.

*** Failure 9134 Error 6: (d8264ce0-43a5-4dbd-a8a6-0000000009ab) QGREMOTEEXPORT: Column name is of unsupported type type The datatype of a column is not supported.

Solution: It may be possible to redefine the column with a supported datatype, or use a CAST in the SQL syntax to cast the datatype to a supported datatype. Otherwise, contact Teradata Customer Support.

*** Failure 9134 Error: 9101 (d8567b0106-3fff-47a1-acbf-000000000168) MLE_ERR-FFE: Function FunctionName is missing a ON clause. The function call is missing required input tables.

Solution: Correct the syntax.

*** Failure 9134 Error: 60104 (63e825e9-3d89-4327-b1a1-00000000001d) MLE_ERR: relation "dsdfs" does not exist If the error was encountered when executing the HELP FOREIGN TABLE statement, it referenced a non-existent table.

Solution: Correct the table name and resubmit the query. If the error was encountered during a function execution, resubmit the query. If the failure is seen again, contact Teradata Customer Support

*** Failure 9134 Error: 60104 (65b09610-8cc4-4f40-9e1b-000000000b4b) MLE_ERR_FFE: Column name with unbounded numeric type is not supported. A function attempted to return an unbounded numeric datatype.

Solution: It may be possible to correct the function to use a numeric with a defined precision, or use CAST in the SQL syntax to cast the datatype to a supported datatype. Otherwise, contact Teradata Customer Support.

*** Failure 9134 Error: 60104 (65b09610-8cc4-4f40-9e1b-000000000b4b) MLE_ERR_FFE: Unbounded G_Number is not supported A function attempted to return an unbounded numeric type.

Solution: It may be possible to correct the function to use a numeric with defined precision, or use CAST in the SQL syntax to cast the datatype to a supported datatype. Otherwise, contact Teradata Customer Support.

*** Failure 9134 Error: 60104 (d8264ce0-43a5-4dbd-a8a6-0000000009dc) MLE_ERR_FFE: Precision range of column name cannot be more than 38. A function attempted to return a datatype with a precision greater than 38.

Solution: It may be possible to correct the function to use a datatype with less precision, or use CAST in the SQL syntax to cast the datatype to a supported datatype. Otherwise, contact Teradata Customer Support.

*** Failure 9134 Error: 60104 (65b09610-8cc4-4f40-9e1b-000000000b4b) MLE_ERR_FFE:Unbounded G_Decimal is not supported A function attempted to return an unbounded decimal type.

Solution: It may be possible to correct the function to use a decimal with defined precision, or use CAST in the SQL syntax to cast the datatype to a supported datatype. Otherwise, contact Teradata Customer Support.

*** Failure 9134 Error: 60109 (56f921d4-bc08-49e1-baba-000000000004) MLE_ERR_FFE: Error occurred while validating the connection.: Unable to create JDBC connection. Role "proxyuser" does not have connect privileges on this database. () This error occurred while validating the connection.

Solution: Contact Teradata Customer Support.

*** Failure 9134 Error: 60129 (94255d29-3ab7-4bc4-b533-000000000110) Error occurred while executing the Foreign Function Execution[Teradata Database][TeraJDBC 15.10.00.07][Error 3803][SQL State 42S01] Table table_name already exists.() This error occurred while executing the Foreign Function Execution.

Solution: Drop the table table_name and resubmit the query.

User-Defined Functions Error Messages

User-defined error messages occur in the context of invoking a pm.stored_procedure. For example, this call installs a user-defined function in ML Engine:
call pm.install_afunction('kmeans_uif');
Use this table to map substitutions of the variable shown in the error messages:
Variable Variable value can be replaced by:
pm.stored_procedure
  • pm.download_afile
  • pm.download_afile_from_public
  • pm.install_afile
  • pm.install_afile_to_public
  • pm.install.afunction
  • pm.install_afunction_to_public
  • pm.remove_afile
  • pm.remove_afile_from_public
  • pm.remove_afunction
  • pm.remove_afunction_from_public
pm.install_procedure
  • pm.install_afile
  • pm.install_afile_to_public
  • pm.install_afunction
  • pm.install_afunction_to_public
pm.install_function
  • pm.install_afunction
  • pm.install_afunction_to_public
pm.install_file
  • pm.install_afile
  • pm.install_afile_to_public
pm.remove_procedure
  • pm.remove_afile
  • pm.remove_afile_from_public
  • pm.remove_afunction
  • pm.remove_afunction_from_public
pm.download_procedure
  • pm.download_afile
  • pm.download_afile_from_public
Error Message Text Description and Solution
Executed as Single statement. Failed [7825 : 38000] | EXECUTEFOREIGNSQL: The user does not have SELECT access to TD_(SERVER_DB.coprocessor_ddL) Elapsed time = … STATEMENT 1: Unknown failed. User tried to install, uninstall, or download UDF/file without appropriate privilege.

Solution: Ask privileged user to grant the user the appropriate access privileges as described in Access Control Commands for Installing, Removing, and Downloading UDFs and Files.

*** Failure 3523 The user does not have EXECUTE PROCEDURE access to pm.stored-procedure. The user does not have the proper access rights to execute this request.

Solution: Obtain the necessary access rights.

*** Failure 5660 Cannot create index on LOB columns. The first column of the SELECT statement cannot be of data type CLOB or BLOB.

In some functions, first output column is appended from input table (through Accumulate or PartitionColumns arguments). For such cases, either choose a column with a different data type or change the order of columns in the SELECT statement (for example, SELECT col2,col1 FROM <func_name instead of SELECT * FROM func_name or SELECT col1,col2 FROM func_name). Another option is to create an output table from the SELECT statement with NO PRIMARY INDEX or an index on a column which is not a LOB column.

*** Failure 7825 in UDF/XSP/UDM PM.remove_afile_from_public: SQLSTATE 38U78: Either the file file_name does not exist in ML Engine or the user does not have permission to uninstall the file. An attempt was made to remove a file that does not exist or the user does not have the proper permission.

Solution: Check to see if the file exists or if you have the required permission to delete the file.

*** Failure 7825 in UDF/XSP/UDMpm.stored-procedure: SQLSTATE 38U79: empty result from: internal query Internal operation produced an empty result after a retry.

Solution: Try the pm.stored_procedure again. If the problem persists, contact Teradata Customer Support. Give them your Teradata QueryGrid Manager node hostname to help diagnose the problem.

*** Failure 7825 in UDF/XSP/UDM pm.remove-procedure: SQLSTATE 38U81: uninstall function_name failed Failure to remove a function or file caused an internal error.

Solution: Contact Teradata Customer Support. Give them your Teradata QueryGrid Manager node hostname to help diagnose the problem.

*** Failure 7825 in UDF/XSP/UDM PM.remove_afunction_from_public: SQLSTATE 38U82: Either the function function_name does not exist in ML Engine or the user does not have permission to uninstall the function. An attempt was made to remove a function that does not exist or the user does not have the proper permission.

Solution: Check to see if the function exists or if you have the required permission to delete the function.

*** Failure 7825 in UDF/XSP/UDM pm.download_procedure: SQLSTATE 38U83: File file_name is not found in schema_name schema. An attempt was made to download a file that does not exist on a named ML Engine schema.

Solution: Replace the reference to nonexistent file with the correct one.

*** Failure 7825 in UDF/XSP/UDM pm.stored_procedure: SQLSTATE 38U84: User public is not allowed. "public" was used as a user name.

Solution: "public" cannot be used as a user name. Use a different user name.

*** Failure 7825 in UDF/XSP/UDM pm.stored_procedure: SQLSTATE 38U87: uif_name must not have '#'. There is an invalid character in the name of the user installed file (uif).

Solution: Correct the file name.

*** Failure 7825 in UDF/XSP/UDM pm.install_file: SQLSTATE 38U88: File file_name already exists in Machine Learning Engine. An attempt was made to install a file that already exists.

Solution: Remove the file, then install its replacement.

*** Failure 7825 in UDF/XSP/UDM pm.install_function: SQLSTATE 38U89: Function function_name already exists in Machine Learning Engine. An attempt was made to install a function that already exists.

Solution: Remove the function, then install its replacement.

*** Failure 7825 in UDF/XSP/UDM pm.install_function: SQLSTATE 38U90: Linux command failed: error message An internal Linux command IOException occurred during a UDF installation.

Solution: Contact Teradata Customer Support. Give them your Teradata QueryGrid Manager node hostname to help diagnose the problem.

*** Failure 7825 in UDF/XSP/UDM pm.install_function: SQLSTATE 38U91: file IOException not found: error message Internal operation to read a json file failed during a UDF installation.

Solution: Contact Teradata Customer Support. Give them your Teradata QueryGrid Manager node hostname to help diagnose the problem.

*** Failure 7825 in UDF/XSP/UDM pm.stored_procedure: SQLSTATE 38U92: ssh tdqg@sshtdmle mkdir -p /opt/teradata/tdqg/connector/tdqg-tdmle-connector/UDF/fromTD/alice failed with return code 255. Internal operation "ssh tdqg@sshtdmle..." failed because passwordless ssh/scp between Advanced SQL Engine internal user and ML Engine is not working.

Solution: Have your Customer Support Representative set up a passwordless ssh/scp between Advanced SQL Engine and ML Engine.

*** Failure 7825 in UDF/XSP/UDM pm.install_function: SQLSTATE 38U93: unzip path failed: error message An internal unzip IOException occurred during a UDF installation.

Solution: Contact Teradata Customer Support. Give them your Teradata QueryGrid Manager node hostname to help diagnose the problem.

*** Failure 7825 in UDF/XSP/UDM pm.install_function:SQLSTATE 38U94: cp ./path/tmp/_udfInstallInput... failed with return code 1 An internal Linux command got a non zero return code during a UDF installation.

Solution: Retry the operation. If the error persists, contact Teradata Customer Support.

*** Failure 7825 in UDF/XSP/UDM pm.stored_procedure: SQLSTATE 38U95: Please CALL SYSUIF.INSTALL_FILE (file_name) first. An attempt was made to install, remove, or download a function without installing its input user installed file (uif) first. Or, the name of the input uif is over 30 characters.
Solution: If input uif does not exist, install the input uif of the function first. For example:
call sysuif.install_afile ('kmeans_uif', 'kmeans.zip', 'cb!/tmp/kmeans.zip');

If the input uif name is over 30 characters long, use a shorter name.

*** Failure 7825 in UDF/XSP/UDM pm.install_function: SQLSTATE 38U96: walkFileTree path failed: error message An internal walkFileTree IOException occurred during a UDF installation.

Solution: Contact Teradata Customer Support. Give them your Teradata QueryGrid Manager node hostname to help diagnose the problem.

*** Failure 7825 in UDF/XSP/UDM pm.install_function: SQLSTATE 38U97: SearchAndUnzip path failed: error message An internal SearchAndUnzip IOException occurred during a UDF installation.

Solution: Contact Teradata Customer Support. Give them your Teradata QueryGrid Manager node hostname to help diagnose the problem.

*** Failure 7825 in UDF/XSP/UDMpm.install_procedure: SQLSTATE 38U98: call syslib.ExecuteForeignSQL ( 'install file file_name failed: file file_name already exists in schema "public"). An attempt was made to install a public function that already exists.

Solution: Remove the public function or file, then install its replacement.

*** Failure 7825 in UDF/XSP/UDMpm.install_function: SQLSTATE 38U99: create temp dir path gets error message An internal create temp dir IOException occurred during a UDF installation.

Solution: Contact Teradata Customer Support. Give them your Teradata QueryGrid Manager node hostname to help diagnose the problem.

*** Failure 7827 Java SQL Exception SQLSTATE 39001: Invalid SQL State(HY000[Error 9134]: [Teradata Database] [TeraJDBC 16.20.00.02] [Error 9134] [SQLState HY000] Error: 60104 (bf774d8a-a2c5-424d-9d68-000000000030) invalid user name and/or password ()). An internal operation failed because proxyuser has not been set up on ML Engine.

Solution: Have your Customer Support Representative set up proxyuser on ML Engine.