OLEDB 11.2.0.1: DBColumnInfo->ulColumnSize shows wrong length (BYTES instead CHAR) for NVARVCHAR column when RDBMS parameter nls_length_semantics = CHAR
(Doc ID 1136838.1)
Last updated on MARCH 04, 2022
Applies to:
Oracle Provider for OLE DB - Version 11.2.0.1 and laterInformation in this document applies to any platform.
Symptoms
Using OLEDB 11.2.0.1 against database using init.ora parameter
returns maximum lengh for BYTES - not CHAR.
I.e. if NVARCHAR(40) is defined, return value is 80 (2*40) instead expected 40
Using OLEDB 11.1.0.7 and lower correct values for DBColumnInfo->ulColumnSize returned.
Changes
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 |
Changes |
Cause |
Solution |
References |