Feedback
Did this article resolve your question/issue?

   

Article

The size of VARCHAR2 (1 CHAR) is returned in bytes instead of in character size

Information

 
TitleThe size of VARCHAR2 (1 CHAR) is returned in bytes instead of in character size
URL NameThe-size-of-VARCHAR2-1-CHAR-is-returned-in-bytes-instead-of-in-character-size
Article Number000117840
EnvironmentProduct: Connect for ADO.Net Oracle provider
Version: 4.1.0.014209
OS: Windows
Database: Oracle
Application: All supported applications
Question/Problem Description
The size of VARCHAR2 (1 CHAR) is returned in bytes instead of in character size when using the Connect for ADO.Net Oracle provider.
Steps to Reproduce
Clarifying Information
This occurs when using the column type as varchar2(x CHAR) or char(x CHAR).
Error Message
Defect NumberDefect ADO-960
Enhancement Number
Cause
In this scenario when NLS_CHARACTERSET is set to AL32UTF8, 4 bytes were assigned for one character.
 
Resolution
Fixed in hot fix 4.3.0.014211

Refer to 4848, Connect for ADO.NET and Connect for .NET hot fix download and install instructions for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date10/29/2019 2:14 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.