OracleDataAdapter.Fill returns incorrect data for small numbers.

Question

Hi All,
Recently we moved to Oracle client 11.1.0.7.20 with ODP.NET and instant client.
And we encountered the following issue.
When FetchSize of the command is set to any value that differs from default for some number fields with size <5 incorrect values are returned.
I used the following code to reproduce the issue:
var query = "SELECT * FROM RT ORDER BY ID";
var connectionString = "Data Source=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=server)(PORT=1531)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=test)));User Id=user;Password=password;";
var column = "IS_LEAF"; // data type is NUMBER(1, 0)
using (var connection = new OracleConnection(connectionString))
using (var cmd1 = connection.CreateCommand())
using (var cmd2 = connection.CreateCommand())
cmd1.CommandText = query;
cmd2.CommandText = query;
cmd2.FetchSize = 512*1024; // 512K
var adapter1 = new OracleDataAdapter(cmd1);
var table1 = new DataTable();
adapter1.Fill(table1);
var adapter2 = new OracleDataAdapter(cmd2);
var table2 = new DataTable();
adapter2.Fill(table2);
for (int i = 0; i < table1.Rows.Count; i++)
var row1 = table1.Rows;
var row2 = table2.Rows[i];
if (!object.Equals(row1[column], row2[column]))
Console.WriteLine(string.Format("values don't match: {0}, {1}", row1[column], row2[column]));
there are some ouput lines:
values don't match: 0, 3328
values don't match: 0, 3
values don't match: 1, 3
values don't match: 0, 318
values don't match: 0, 264
values don't match: 1, 10280
values don't match: 1, 842
values don't match: 1, 7184
The column type is NUMBER(1, 0) and only values in the database are 1 or 0. So as you can see most of the values filled with custom fetch size are totally incorrect.
We have several tables with small number fields and for some of them the issue reproduces but for others does not.
And the issue doesn't appear:
1. with Oracle client 11.1.0.6.20
2. if I use data readers and compare values record by record.
Our Oracle DB version is 10.2.0.4.
Thanks,
Maxim.

Answer 1

For anyone that may find this at a later time, this behavior has now been corrected, and is available in 11107 Patch 31 and newer, available on My Oracle Support. Note that the "self tuning=false" did not work in all cases, so the only reliable solution is to get the patch.
Greg