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 - 5809 | Certain scenarios of inserts using Delta Write will not write out the parquet file; this is dependent on file size and partitions. Workaround: None. Deployments: Lake on Azure| AWS |
| OTF-5584 | Queries with a WHERE condition on a partition column of type DATE may fail due to inconsistencies in how partition values are stored and interpreted. Workaround: None. Deployments: Lake on Azure| GC| AWS |
| OTF-5583 | There is a mismatch in date partition types that causes empty results when executing BETWEEN queries on Delta tables. This issue is due to inconsistent handling of date partition values between Delta logs (which store dates as days-since-epoch integers) and other engines (which use ISO string date formats). Workaround: None. Deployments: Lake on Azure| GC| AWS |
| OTF-4797 | String type conversion from utf8 to utf-16 is causing a SegV for column stats from Iceberg to Teradata. Workaround: Disable native OTF and use Java OTF to get the query working. Deployments: Lake on Azure| GC| AWS |
| OTF-4601 | This issue is reproduced when running Lake Formation Iceberg OTF queries, specifically DML queries, in duration mode. Workaround: The workaround is to restart the OTF UDF server. Deployments: AWS with Lake Formation enabled for the DATALAKE |
Optimizer
| Key | Description |
|---|---|
| OPT-11472 | Query with GEN SUM path and containing 'using row' is causing a crash. Workaround: Disable GEN SUM feature using dbscontrol internal 788 or using diagnostic : "diagnostic disablecgigensumstep on for session;". Deployments: Lake on Azure| GC| AWS |
| 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 |
|---|---|
| NOS-13574 | Bucket name is not parsed correctly in LOCATION field for AWS VPCE endpoints, leading to NOS SQL error. Workaround: Rewrite all their queries to use the new Simplified URI format. Deployments: Lake on Azure| GC| 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 |
Cloud Control Panel
| 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
Unified Data Migration/Protection
| Key | Description |
|---|---|
| UDMP-2856 | Create copy plan might fail with no indication on the VantageCloud Lake console. Workaround: None. Deployments: Lake on Azure| GC| 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-8087 | When LMNUMHASHBITS diagnostic is used queries could fail with snapshot dumps. Workaround: Do not use LMNUMHASHBITS diagnostic. Deployments: Lake on Azure| GC| AWS |