varchar2(4000 char) on XE 11g

[ths]

Hello,
we have changed to the newest version of ODAC component and have error "Invalid Field Size" with Oracle XE 11g for field varchar2(4000 char). We cannot set TOraSession option parameter UseUnicode = true. With older version of ODAC 5.8 components we do not have this error in exactely the same configuration.
Vladimir

[AlexP]

Hello,

We can't reproduce the problem. Please describe the steps to reproduce the situation or send a sample demonstrating the problem to alexp*devart*com.

[ths]

Hello,

please, create test table on Oracle XE 11g with varchar2(4000 char) field. If you place TOraSession and TOraQuery components on the form and try to create fields you should get this error.

Vladimir

[AlexP]

The described error is not reproduced when the varchar2(4000) field is created. Please provide a sample and specify the versions of IDE, ODAC and NLS parameters of the server and client.

[ths]

We use ODAC 9.4.13 for Delphi 5.
Database is Oracle XE 11g. It has NLS_CHARACTERSET AL32UTF8 that cannot be changed according to Oracle. It is important, that the field is 4000 Char (not Byte).
Very simple sample is sent by mail.
Vladimir

[AlexP]

Please send me results of the following queries:

Code: Select all

SELECT USERENV ('language') from dual; 

SELECT * FROM V$NLS_PARAMETERS;

[ths]

SELECT USERENV ('language') from dual;

GERMAN_GERMANY.AL32UTF8

SELECT * FROM V$NLS_PARAMETERS;

PARAMETER,VALUE
NLS_LANGUAGE,GERMAN
NLS_TERRITORY,GERMANY
NLS_CURRENCY,€
NLS_ISO_CURRENCY,GERMANY
NLS_NUMERIC_CHARACTERS,,.
NLS_CALENDAR,GREGORIAN
NLS_DATE_FORMAT,DD.MM.RR
NLS_DATE_LANGUAGE,GERMAN
NLS_CHARACTERSET,AL32UTF8
NLS_SORT,GERMAN
NLS_TIME_FORMAT,HH24:MI:SSXFF
NLS_TIMESTAMP_FORMAT,DD.MM.RR HH24:MI:SSXFF
NLS_TIME_TZ_FORMAT,HH24:MI:SSXFF TZR
NLS_TIMESTAMP_TZ_FORMAT,DD.MM.RR HH24:MI:SSXFF TZR
NLS_DUAL_CURRENCY,€
NLS_NCHAR_CHARACTERSET,AL16UTF16
NLS_COMP,BINARY
NLS_LENGTH_SEMANTICS,BYTE
NLS_NCHAR_CONV_EXCP,FALSE

[AlexP]

Thank you for the sample. We have fixed this behavior, the fix will be included to the next version of ODAC.

[ths]

Hi Alex,
thanks for info. Would you please estimate when the corrected version may be available?

[AlexP]

The new ODAC version including these fixes will be available this week already.

[ths]

Thanks

[ths]

Hello Support,

we have installed new version and the problem is still there. Could you comment on this, please?

Vladimir

[AlexP]

Unfortunately, changes made for this issue solution lead to some other issues (in particular, data cutting and incorrect display). therefore we didn't include this fix to the new build. We continue the issue investigation.

[ths]

Hello Alex,

we are waiting for solution.

Just as a hint - as I already mentioned, there is no such a problem with (very) old version of your components in exactely the same current Oracle configuration.

It is clear to me, that a lot of things were changed in the components since that time...

Vladimir

[ths]

Hello Alex,

would You tell me please when can we count with a new version solving the problem?

Vladimir