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
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) |
UDF
| Key | Description |
|---|---|
| UDF-1427 | It was discovered that there are issues in supporting more than one third party UDF solutions, including the following:1. If two third-party solutions are installed in the same environment, upgrade (including blue/green or in-place upgrade) will not be successful. 2. If the users want to make any changes (e.g. update or delete) the system may hang. 3. If the users want to install more than one third party solutions at the same time (rare scenario), one or both may fail. 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 of Lake supporting more than one 3rd Party solutions. |
SQLE Services
| Key | Description |
|---|---|
| SQLES-11944 | POG Deployments can fail with certain node-count and storage size combination in AWS and Azure. Contact customer support for further assistance. Workaround: Avoid the size where the problem has been identified until the fix is in place. Contact Teradata customer support for further assistance. Deployments: Azure, AWS |
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) |
Query Service
| Key | Description |
|---|---|
| QS–969 | When using CCP Editor to run queries, BYTE column values are currently returned incorrectly.Limitation: To avoid this issue, queries cannot have BYTE column values returned. Deployments: All |
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 | This issue was seen during an INSERT operation in the DBS while using the KeyVault. 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. Deployments: 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: Recommend using files with total length of column names less than 15000 characters. Deployments: Accounts deployed on AWS and Azure environments. |
Core Services
| 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 |