After next extent change, count didn't matching

After next extent change, my one table become strange and sql work differently with original backup table. I will post sql and schema, can you see why this sql show 0 count instead of about 9500 count.

This is changed sql and table: count = 0
SELECT COUNT(*)
FROM SDAM_ILBI A
WHERE A.IL_DATE BETWEEN '20100201' AND '20100208'
AND A.SABUN NOT IN (
SELECT TM_SABUN
FROM SKWASO_bk20100106
GROUP BY TM_SABUN
)

And this is backuped original table with query : count =9634

SELECT COUNT(*)
FROM SDAM_ILBI A
WHERE A.IL_DATE BETWEEN '20100201' AND '20100208'
AND A.SABUN NOT IN (
SELECT TM_SABUN
FROM SKWASO
GROUP BY TM_SABUN
)

I think something is wrong with reorg or next extend or index.
Thank you.
Here is schema. you can download and put it in DB.
http://dl.dropbox.com/u/529936/skwaso.zip

no, something is wrong with your tables and or query

Assuming same query runs agaisnt both tables most likely scenario is tables have different data.

what is it showing when you do count(*) on the table?

select count(*) from SKWASO_bk20100106;

Thanks,

I found out that column TM_SABUN in SKWASO_BK20100106 has null value.
That's why count = 0 in this query.

But the SKWASO table that has no null value in TM_SABUN resulted count = 9634. Thank for your help.

SQL is basic function, I might study more about how to interpret SQL better.
Xie Xie.

but the script you attached showing that you have inserted and comited some rows in that table ... that means davey is right ... :)

anyway, glad to hear that you found the issue.

Thanks,

select count(*) from SKWASO_bk20100106; this count = 97.
Something wrong was null value in TM_SABUN.
It is not related with next extent value.
This is not PK or Unique, my misunderstanding.
Thank you.

so... let me quote myself "most likely scenario is tables have different data" :cool: