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 |
|---|---|
| OPT - 10694 | Complex queries with aggregations, joins, correlated sub-queries might see ET, AMP CPU time regressions with most likely an Explain plan change. Workaround: None. Deployments: Lake on AWS |
| Key | Description |
|---|---|
| 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-2733 | 7810 error issued for queries under heavy stress and concurrency. Workaround: None. This is a very intermittent problem under heavy stress. If 7810 error is encountered, the user should retry the query. Deployments: Lake on Azure | AWS | GC |
| 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-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 |
Fixed 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 |
|---|---|
| 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 |
| 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 |