16.10 - HybridServer Fields - Teradata Database

Teradata Database Utilities

Product
Teradata Database
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-04-26
dita:mapPath
zll1480972831047.ditamap
dita:ditavalPath
changebar_rev_16_10_exclude_audience_ie.ditaval

Purpose

Each node of a Teradata Database system can have one hybrid server that provides protected mode, multiple-threaded execution for external language procedures and UDFs to all AMPs and PEs on the node. (Protected mode UDFs are those that do not include the EXTERNAL SECURITY clause in their UDF SQL definitions.)

Each group of HybridServer fields specifies settings that the server uses when servicing procedures and UDFs written in the language specified by the HybridServerLanguage field of the group.

Example: HybridServer fields

The following group of cufconfig fields, all HybridServer3 settings, specify custom settings used by the hybrid server when running UDFs defined to have a LANGUAGE attribute of EAH.

HybridServer3Execution: /usr/tdbms/bin/udfsectsk
HybridServer3Library:
HybridServer3LibPath:
HybridServer3IncPath:
HybridServer3EnvFile:
HybridServer3MemSize: 262144
HybridServer3Threads: 20 
HybridServer3Language (display only): EAH 
HybridServer3AppCat (display only): 8
HybridServer3FreeSpace: 0
HybridServer3MemFileSize: 0
HybridServer3JREPath: /opt/teradata/jvm64/jre8/jre/
HybridServer3JVMOptions:
EAH is the external access handler language used exclusively for Teradata QueryGrid functions. This group of HybridServer settings should be changed only under the direction of the Teradata Support Center.