Resolving UDF Server Setup Errors | External Stored Procedures | Vantage - Resolving UDF Server Setup Errors - Analytics Database - Teradata Vantage

SQL External Routine Programming

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
iiv1628111441820.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1147
lifecycle
latest
Product Category
Teradata Vantageā„¢

When an external routine like an UDF, UDM, or external stored procedure is called, a UDF server process is acquired from the UDF server pool to execute the external routine. If there are no UDF server processes in the pool or if all of the processes in the pool are busy, then the system tries to start a new UDF server process for the request.

The startup of the new UDF server usually takes some time, especially if the UDF server is for executing Java external routines, or if the system is very busy. If the new UDF server cannot be started within the default time limit, the query that contains the UDF, UDM, or external procedure call is aborted, and you may receive a 7583 error indicating that the UDF server setup encountered a problem. The system log may also record a 7820 error specifying that the UDF server could not stay up long enough for initialization.

If you are experiencing these errors, you can contact Teradata Support Center personnel to adjust the time limit allowed for starting a new UDF server process. For details, see the information about the Cufconfig utility in Teradata Vantageā„¢ - Database Utilities, B035-1102.