with OLE DB, the following insert of a String with length 20 causes ORA-12899
ORA-12899: value too large for column "TESTUTF8"."JOHI_BG2"."NAME2" (actual: 40, maximum: 25);
Apparently the byte length of sText is used instead of character length.
Insert is executed ok with native router.
DB encoding is AL32UTF8, DB-Version is Oracle 10.2.0.3
set sText = '123456789.123456789.'
Insert into johi_bg2 (name2) values (:sText)
-- column name2 is varchar2(25)
TD-4181: TD 5.1 SP1 with Oracle OLE DB: Insert fails
Re: TD-4181: TD 5.1 SP1 with Oracle OLE DB: Insert fails
Hi,
I cannot reproduce this problem with an UTF8 database by following the steps you provided.
If you'd like to provide a reprocase and more details about the environment I'd be glad to test it again.
Thanks,
Ana
I cannot reproduce this problem with an UTF8 database by following the steps you provided.
If you'd like to provide a reprocase and more details about the environment I'd be glad to test it again.
Thanks,
Ana
You do not have the required permissions to view the files attached to this post.
Re: TD-4181: TD 5.1 SP1 with Oracle OLE DB: Insert fails
The missing piece probably is NLS_LENGTH_SEMANTICS = CHAR
NLS_LANG=AMERICAN_AMERICA.AL32UTF8 (client)
NLS_DATABASE_PARAMETERS:
NLS_NCHAR_CHARACTERSET = AL16UTF16
NLS_CHARACTERSET = AL32UTF8
SQL*Plus: Release 9.2.0.7.0 - Production on Mon Jan 28 16:25:01 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning and Data Mining options
SQL> describe johi_bg2
Name Null? Type
----------------------------------------- -------- ----------------------------
NAME NVARCHAR2(25)
NAME2 VARCHAR2(25 CHAR)
Anyway, OLEDB currently is no alternative for us, because it does not accept bind variables in the select expression:
select to_date(:sDate) from dual into :sdate1
so this insert problem is of very low priority for us.
TD-4181 is critical for us, TD-3949 is also important.
NLS_LANG=AMERICAN_AMERICA.AL32UTF8 (client)
NLS_DATABASE_PARAMETERS:
NLS_NCHAR_CHARACTERSET = AL16UTF16
NLS_CHARACTERSET = AL32UTF8
SQL*Plus: Release 9.2.0.7.0 - Production on Mon Jan 28 16:25:01 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning and Data Mining options
SQL> describe johi_bg2
Name Null? Type
----------------------------------------- -------- ----------------------------
NAME NVARCHAR2(25)
NAME2 VARCHAR2(25 CHAR)
Anyway, OLEDB currently is no alternative for us, because it does not accept bind variables in the select expression:
select to_date(:sDate) from dual into :sdate1
so this insert problem is of very low priority for us.
TD-4181 is critical for us, TD-3949 is also important.
Who is online
Users browsing this forum: [Ccbot] and 0 guests