Teradata Database Message 7834 - 7834 - Analytics Database - Teradata Vantage

Teradata® VantageCloud Lake - Analytics Database Messages

Edition
Lake
Product
Analytics Database
Teradata Vantage
Published
October 2022
Language
English (United States)
Last Update
2024-02-26
dita:mapPath
tzr1629746512312.ditamap
dita:ditavalPath
ft:empty
dita:id
vza1585613049811
lifecycle
latest
Product Category
Teradata® Vantage™
Message
Invalid UDF/XSP/UDM environment file specification.
Explanation
The error message is generated when the environment file associated with user function or procedure of a specific application category is not in the proper format. The user function or procedure must be running in protected/secure mode. Environment variable are not set for unprotected mode. This is because the user code is not isolated from the database code in this mode and its use could conflict with the database were it to be allowed. The path to the environment file is specified by the UDF configuration file. To print the configuration file enter: start cufconfig -o See the cufconfig utility documentation for further details. The environment files are specified by xxxENVFile where xxx are the letters for the application category for the UDF/UDM or XSP. Check the contents of the environment file(s) shown in the configuration file. All entries of the text file must be of the form (one per line): <envname> = <env value> Where <envname> is the alphanumeric and '_' name of the environment variable and <env value> is the value to assign to it. Each line is input to the set environment variable system call for the platform in question. It is up to the site to make sure the contents are valid for the system platform it is being used on. There is no support for appending additional information to an existing environment variable such as the PATH environment variable. If the environment file is to be used it should be set on each node using the same path and name for the file. However the contents of the file may localized to the node if desired. No error is generated if the environment variable file does not exist even though it is specifed by the UDF configuation file. The environment variables are set when a protected mode server is started. In general the database would have to be restarted to pick up a new set of environment variables when the configuration file is changed.
Generated By
UDF subsystem
For Whom
DBA, Application developer
Notes
None
Remedy
Check and fix the environment text file.