R
Rob
Hi,
We are using the Oracle OLEDB provider(9.2.0.2) and OLEDB
data access components in .NET using C#. When we fetch
more rows than the FetchSize connection string parameter
(default 100), any varchar2 columns have corrupt data.
Upon closer inspection the corrupt strings have the
correct characters, it is that they are packed into 1 byte
instead of being unicode (2 byte) characters. The first
fetchsize number of rows are fine.
Does anyone have a solution to this? We have the most
recent Oracle Client and OLE DB provider. Just increasing
the Fetchsize is not an option.
Thanks,
Rob
We are using the Oracle OLEDB provider(9.2.0.2) and OLEDB
data access components in .NET using C#. When we fetch
more rows than the FetchSize connection string parameter
(default 100), any varchar2 columns have corrupt data.
Upon closer inspection the corrupt strings have the
correct characters, it is that they are packed into 1 byte
instead of being unicode (2 byte) characters. The first
fetchsize number of rows are fine.
Does anyone have a solution to this? We have the most
recent Oracle Client and OLE DB provider. Just increasing
the Fetchsize is not an option.
Thanks,
Rob