To manage UDFs, Teradata uses default and temporary paths for UDF creation and execution, including:
- A default directory that Teradata uses to search for UDF source files and object files if the CREATE FUNCTION does not explicitly specify the location.
If a source file or object file is on the server and the path is not fully specified in the CREATE FUNCTION statement, the full path of the file is expected to begin here.
An administrator, or someone with sufficient privileges, is responsible for creating this directory.
- A temporary directory where UDFs are compiled.
Any files needed for the compilation process are moved here. This includes source files from the server or client as well as object and header files, if needed.
- A directory where Teradata saves the dynamically linked libraries.
- A directory of shared memory files for UDFs that execute in protected mode.
For information, including the names of UDF default and temporary paths, see the Cufconfig utility in Teradata Vantage™ - Database Utilities, B035-1102.