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
UDF Solutions
| Key | Description |
|---|---|
| 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, please open a case from Support Portal to engage Teradata Support for assistance. Deployments: AWS is the only platform of Lake supporting more than one 3rd Party solution. |
TDGSS
| Key | Description |
|---|---|
| TDGSS-10906 | JDBC drivers with Java 8 or earlier can't connect. Workaround: Submit a request from Support Portal to have Teradata apply the work- around. Deployments: All |
TCMC
| Key | Description |
|---|---|
| TCMC-1826 | When users attempt to disable the 'Internet connection' option from the SETTINGS tab in the CCP UI, it gives an error saying, "There was a problem internal server error". The endpoint is returning error 500 when request to remove the CIDRs list is sent. Workaround: From UI there is no workaround. Submit a case from the Support Portal to engage Teradata Support for assistance. Deployments: Affected deployments (AZURE) |
QueryGrid
| Key | Description |
|---|---|
| QueryGrid-25491 | When user sets up L2L configuration with a tenant with COG node the Network diagnostics fail with an error like - 'Failed to connect to node "pog-29ff1df4fe- SMP001-02": No matching addresses found for eth00.' Workaround: None. Submit a case from Support Portal to engage Teradata Support for assistance Deployments: Affected deployments (AWS, AZURE) |
POD Services
| Key | Description |
|---|---|
| PODS-3111 | When users attempt to disable the 'Internet connection' option from the SETTINGS tab in the CCP UI, it gives an error saying, "There was a problem internal server error". The endpoint is returning error 500 when request to remove the CIDRs list is sent. Workaround: No workaround available from the UI. Submit a case from the Support Portal to engage Teradata Support for assistance. Deployments: Affected deployments Google Cloud |
Native Object Store
| Key | Description |
|---|---|
| NOS–11654 | Query failure when NOS query is fetching the credentials information from KeyVault and query encounters any exceptions during the processing. This issue is a memory handling issue and is therefore intermittent. Workaround: None. Submit a case from Support Portal to engage Teradata Support for assistance. Deployments: All |
HARM
| Key | Description |
|---|---|
| HARM-5668 | When using dot notation to shred a result JSON value in a result set, a 3807 error can be returned. This error only occurs when upgrades are in progress. Workaround: Avoid using dot notation to shred the JSON object. Deployments: All. |
| HARM-5028 | Clients using the specified .net driver will get 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. Deployment: This issue is cloud agnostic. It affects all could vendors. |
Data Loading
| Key | Description |
|---|---|
| DLD-2991 | Create FLOW fails when total length of column names exceeds 15000. It occurs with source files having a large number of columns where the total character length for column names is greater than 15000. Workaround: The recommendation is to use files with a total length of column names less than 15000 characters. Deployments: Accounts deployed on AWS and Azure environments. |
Fixed Issues
Core
| Key | Description |
|---|---|
| CORESRVS-2046 | After QueryGrid is deployed when adding your new datasource you will be asked to provide your Google Cloud project number so that it can be trusted by Private Service Connect Load Balancers. During this process QueryGrid resources are detached from VantageCloud Lake Private Service Connect Load Balancers, disrupting future network communication vital to QueryGrid functioning properly. Workaround: A change request must be opened to re-attach the QueryGrid resources to the Load Balancers. Deployments: Any VantageCloud Lake on Google Cloud deployment where QueryGrid is also deployed. |
COG
| Key | Description |
|---|---|
| COG-9260 | Queries may fail with the following error:Failure 4189 ******* : ImpDE : Fabric not reachable Workaround: None. Submit a case from Support Portal to engage Teradata Support for assistance. Deployments: All |