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
Open Table Format
| Key | Description |
|---|---|
| OTF-4635 | Currently, MOTF tables support only the "ICEBERG" table format. Attempts to create MOTF tables using other formats are not supported and will result in failures during CT. Workaround: There is no available workaround at this time. Customers are advised to create MOTF tables exclusively using the "ICEBERG" table format. Creating MOTF tables with any other format is not supported and may lead to errors during data insertion or selection. 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. |
Optimizer
| 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 |
HARM
| 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 |
Data Insights
| 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 |
| 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 |
Bring Your Own Analytics
| 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
Vantage ModelOps
| Key | Description |
|---|---|
| VMO - 4884 | All ModelOps jobs (training, evaluation, Deployment) will fail with error response from daemon: no such image. Workaround: Submit a case from Support Portal to request Teradata Support for assistance. The workaround will be applied by the support team. Deployments: Lake on Azure| AWS |
Open Table Format
| Key | Description |
|---|---|
| OTF-4417 | The create macro statement involving SQLMR functions on OTF tables will fail with execution error. Workaround: Set dbscontrol internal flag "NativeOTFFlags" to 1 and rerun the failed SQL and reset the NativeOTFFlags to 0 after that. Request assistance from Teradata using the Support Portal. Deployments: Lake on Azure| GC| AWS |
Optimizer
| Key | Description |
|---|---|
| OPT-10686 | Incorrect results will be seen for aggregate queries on OTF sources. Workaround: Apply the following statement: diagnostic “bulkaggroption=4” on for session. Deployments: Lake on Azure| GC| AWS |
Firestrike
| Key | Description |
|---|---|
| FIR-2142 | After upgrade to October release, queries do not show up on the lake console -> Queries screen. Workaround: Submit a case from Support Portal to request Teradata Support for assistance. The workaround will be applied by the support team. Deployments: Lake on Azure| GC| AWS |
| FIR-2031 | Queries running on compute group do not have the compute group name displayed on UI. It shows as empty. Workaround: None. Deployments: Lake on Azure| GC| AWS |