External UDF .so Linkage Information and Dropping Functions | Teradata Vantage - External UDF .so Linkage Information - Analytics Database - Teradata Vantage

SQL Data Definition Language Detailed Topics

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-07-11
dita:mapPath
vuk1628111288877.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1184
lifecycle
latest
Product Category
Teradata Vantage™

This topic does not apply to SQL UDFs.

There is only one UDF .so file per application category per database per node. The system does not generate .so files for Java UDFs because the source code is contained in the associated JAR files.

Application Category Value Format of the .so File
> 0 libudf_dbid_librevno_AppCat.so
= 0 libudf_dbid_librevno.so

Whenever you create, replace, or drop a UDF, the UDF .so file for that database has to be relinked with all the other UDF object files and then redistributed to all the nodes.

The following example shows the output of a UDF creation on a Linux system. The .so file, libudf_03ee_n.so, increments each time a UDF is created, replaced, or dropped. This DROP FUNCTION operation was the ninth such UDF-related operation in the current database, so the .so file is named libudf_03ee_9.so.

The Unknown statement and 5607 Warning messages are normal.

DROP FUNCTION another;

Result:

 *** Unknown statement, type=124 complete.
 *** Warning: 5607 Check output for possible warnings encountered
     in compiling XSP/UDF.
 *** Total elapsed time was 1 second.

Check output for possible compilation warnings.
-------------------------------------------------------------
 /usr/bin/cc -G -g -Xc -I /tpasw/etc -o libudf_03ee_9.so
pre_Find_Text.o pattern.o pre_really_long_function_name.o
long_name.o pre_udf_scalar_substr.o substr.o
pre_char2hexint.o char2hexint.o   -ludf -lmw -lm