I’d even tried with alter session set “_kcfis_storageidx_disabled”=true; but the null issue still remained on old version.
Now with the new cell sw upgrade the results are as expected.

Thanks
Harshad

You said you had tried turning off storage indexes. Just verifying you used this syntax.

alter session set “_kcfis_storageidx_disabled”=true;

You can also check the stat “cell physical IO bytes saved by storage index” in v$mystat or v$sesstat to make sure storge indexes have not been used. I published a little script called mystats.sql that does that you can use for that. You can find more info about it here: Oracle Exadata – Storage Indexes

At any rate, you should definitely consider upgrading, as 11.2.0.1 is several years old and there have been many bug fixes and enhancements since then.

Oracle returns no rows ( expected output ).
The current setting is cell_offload_processing=TRUE, and when query runs under this setting it returns nulls for col1<0.

Partitiion : Range by date
subpartition : list
col1 : number data type and it is NOT part of partition/subpartition scheme.
Query : select col1 from t1 partiton (p_20110101) where col1 < 0 ;

I see Oracle returning rows whre col1 is null.

When I run the same query by changing the -
alter session set cell_offload_processing=TRUE;

I see no output.

I could not understand why Exadata treats nulls different than it treats on regular Oracle database.
I thought Storage index might be the cuase of this behaviour..I tried changing "_kcfis_storageidx_disabled"
but I still get the same o/p ie Oracle retruns nulls for the condtition col1 < 0.

Have you seen this before ?
Please let me know if you need more info.

Thanks
Harshad

Kerry

SQL_ID CHILD PLAN_HASH EXECS AVG_ETIME AVG_PX OFFLOAD IO_SAVED_% SQL_
————- —— ———- —— ———- —— ——- ———- —-
2uka1yym51jfg 1 3599640982 1 4.06 13 Yes -55.58 inse