February 2025 - Teradata VantageCloud Lake

Lake - Updates and Changes
Deployment
VantageCloud
Edition
Lake
Product
Teradata VantageCloud Lake
Release Number
Published
February 2025
ft:locale
en-US
ft:lastEdition
2026-02-20
dita:mapPath
gze1736983055688.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
gze1736983055688

The following lists the fixed and known issues in this release. If you experience any of the following issues, open an incident with Teradata Customer Support and include the Key in your description.

Known Issues

Vantage ModelOps

Key Description
VMO-1599 ModelOps deployment may fail if previously deleted. This is due to resources not having properly been cleaned up.

Workaround: None. Submit a case from Support Portal to engage Teradata Support for assistance.

Deployments: Lake on AWS
VMO-1573 ModelOps may not function after upgrade.

Workaround: None. Submit a case from Support Portal to engage Teradata Support for assistance.

Deployments: Lake on AWS

User-Defined Functions

Key Description
UDF-1709 BYOM functions may fail after a database restart. This is due to a problem with UDF containers being out of sync.

Workaround: None. Submit a case from Support Portal to engage Teradata Support for assistance.

Deployments: Lake on AWS
UDF-1427 It was discovered that there are issues in supporting more than one third party UDF solutions, including the following:
  1. If two third-party solutions are installed in the same environment, upgrade (including blue/green or in-place upgrade) will not be successful.
  2. If the user wants to make any changes (e.g. update or delete) the system may hang.
  3. If the customer wants to install more than one third party solutions at the same time (rare scenario), one or both may fail.

Workaround: There is no workaround to install more than one third party UDF solutions until this issue is resolved. If running into any issues, please open a case from Support Portal to engage Teradata Support for assistance.

Deployments: AWS is the only platform on Lake supporting more than one third-party solution.

HARM

Key Description
HARM-5668 When using dot notation to shred a result JSON value in a result set, a 3807 error returns. This error occurs only when upgrades are in progress.

Workaround: Avoid using dot notation to shred the JSON object.

Deployments: Lake on Azure| GC| AWS

Fixed Issues

User-Defined Functions Service

Key Description
UDF-1813 The issue was seen when UDF create command was run through tdextroutine CLI tool for UDF installation.

Workaround: Remove any BAK secrets from Vault having the substring "TDaas_CloudInstallS" (and ends in "_BAK").

Deployments: Lake on Azure

Native Object Store FS

Key Description
NOSFS-14957 Insert - Select query with large dataset on OFS table crashes..

Workaround: None. Reduce the select data while inserting into OFS table.

Deployments: Lake on Azure| GC| AWS

HARM

Key Description
HARM-5028 Clients using the specified .Net driver will get a Username, or Password Error, preventing login.

Workaround: Use a different driver from the ones listed (17.10 and 17.20 .Net driver) or to block port 443 at the router.

Deployments:This issue is cloud agnostic. It affects all could vendors.

COG

Key Description
COG-10121 Due to issues with handling Capacity Reservation, Compute Clusters may take a long time to resume.

Workaround: No workaround available. Submit a case from the Support Portal to engage Teradata Support for assistance.

Deployments: Lake on AWS