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
| 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:
Workaround: There is no workaround to install more than one third party UDF solutions until this issue is resolved. If running into any issues, 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. |
| Key | Description |
|---|---|
| SQLES-14124 | If encryption is enabled for internal bucket, it can cause failure of provisioning of the QueryGrid component. Workaround: None. Submit a case from Support Portal to engage Teradata Support for assistance. Deployments: Lake on Azure| GC| AWS |
| Key | Description |
|---|---|
| QUERYGRID-31925 | Spool size and service account size are being sent in bytes instead of MB thus QGM failed when receiving these numbers. Workaround: None. Deployments: Lake on Azure| GC| AWS |
| Key | Description |
|---|---|
| OTF-4332 | There may be intermittent errors, specifically a "NullPointerException," when you try to run more than three database queries at the same time. The error message you get directly from the SQL might not always clearly say "NullPointerException," so it's important to check your otf.log file to confirm if the details match what's described in the JIRA issue. Workaround: No workaround. Do not run more than three queries concurrently. Deployments: Lake on Azure| AWS |
| OTF-3776 | SELECT COUNT for OTF queries returns inconsistent results. Workaround: None Deployments: Lake on Azure| AWS |
| OTF-3749 | Query failures observed due to OTF Java engine hitting the Out Of Memory exceptions. Workaround: The memory issue occurs when the OTF engine is subjected to a high volume of concurrent queries over an extended period. While typically short-lived, in rare cases this can cause the Java-based OTF engine to enter a stale state, disrupting communication with AMP processes. When this happens, restarting the Java engine usually resolves the problem. To initiate a restart, open a support ticket. Deployments: Lake on Azure| GC| AWS |
| OTF-3516 | Failure during synchronization of Iceberg metadata in Databricks Unity catalog using Spark SQL. Workaround: The issue happens when a spark job is submitted on the Databricks Spark cluster to perform Iceberg metadata sync operation. This is an intermittent issue and the current workaround is to rerun the query. Deployments:Databricks Unity/Iceberg write operations ONLY on all CSPs. |
| Key | Description |
|---|---|
| ICBAAS-8695 | Objects whose backup is completed are also getting displayed in SKIPPED OBJECTS tab in UI. Workaround: None. Deployments: Lake on Azure| GC| AWS |
| Key | Description |
|---|---|
| HARM-7043 | The auto resync function is not used during upgrades. This feature is used for non-upgrade related sync and it can interfere with upgrades if it kicks in at a specific time during the upgrade. There is the potential to lose data for the table being synced if this fails. This fix prevents the auto resync From kicking in during the upgrade. Workaround: Set the autoResyncTimeWindow config value to and empty string ''. Teradata will apply this setting automatically for an upgrade. Deployments: Lake on Azure| GC| AWS |
| HARM-6898 | The incorrect error is returned to the user causing confusion. Workaround: None. For now all 4500 memory errors should be viewed as an LSN not found error, which means the system was restarted and no reconnect is allowed. Deployments: Lake on Azure| GC| AWS |
| Key | Description |
|---|---|
| DINSIGHTS-2423 | When the database is under high load and queries are responding slowly, the API may temporarily return 504 Gateway Timeout errors even while your query continues running in the background. Workaround: Check the status after a while when the database load has decreased. Deployments: Lake on Azure | AWS |
| Key | Description |
|---|---|
| CCP-11353 | If vector store creation fails because a user has insufficient perm space (error shows "No more room in database <dbname>"), fixing the perm space in the UI will remove the TD_AIAdmin role in the DB, causing creation to fail again because it is missing the role. Workaround: To resolve this, remove and re-assign the AskAi_Admin role in the UI. Deployments:Affects AWS and Azure environments with Vector Store enabled |
| CCP-11041 | If user excludes some object from a database having more than 10K objects then restore job will not restore objects beyond 10k objects from that database. Workaround: Do not exclude tables from a database when it has more than 10k tables or restore the complete database. Deployments: Lake on AWS |
| Key | Description |
|---|---|
| BYOA-3179 | A Timeout Error is observed when org admin user activates Anaconda feature from the VantageCloud Lake Console. Workaround: None. Submit a case from Support Portal to engage Teradata Support for assistance. Deployments: Lake on GC |
Fixed Issues
| Key | Description |
|---|---|
| VEL - 2559 | When Vector store is created with non-English data, we may see accuracy issue when using ask or similarity search API on such vector store. Workaround: None. Submit a case from Support Portal to engage Teradata Support for assistance. Deployments: Lake on AWS |
| Key | Description |
|---|---|
| TDGSS-11273 | The Power BI job failed after the TLS connection, established through the .NET data provider, was unexpectedly disconnected during execution. Workaround: Add proper serialization of TLS read/write operations to prevent connection instability during Power BI jobs. Deployments: Lake on Azure| GC| AWS |