OBIEE 12c Analyses Fail with ODBC Error - String data, right truncation
(Doc ID 2757178.1)
Last updated on JUNE 01, 2023
Applies to:
Business Intelligence Suite Enterprise Edition - Version 12.2.1.4.0 to 12.2.1.4.0 [Release 12g]Microsoft Windows x64 (64-bit)
Symptoms
After enabling TLS 1.2 and disabling TLS 1.0/1.1 on all servers, the ODBC DSNs for SQL Server data sources (and which are specified in the RPD Connection Pools) were updated from the SQL Server ODBC Driver to the SQL Server Native Client 11.0 ODBC driver (which supports TLS 1.2).
In the SQL Server database, there are some columns with datatypes of NVARCHAR(MAX) or VARCHAR(MAX).
In the RPD Physical Layer, the columns have Type of LONGVARCHAR (32768).
When an Analysis that includes the corresponding Presentation Column is run, the following error is thrown:
[nQSError: 16001] ODBC error state ... [Microsoft] [SQL Server Native Client 11.0] String data, right truncation
[nQSError: 16011] ODBC error occurred while executing SQLExtendedFetch to retrieve the results of a SQL statement
One workaround is to CAST the RPD Logical Table column to VARCHAR(8000), but this is unpractical when there are many such columns affected.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |