It is obvious at this point that we have a performance problem on this tableIt is not that obvious for us here.
ji li wrote:I give up.
So, back to my original question: can I safely "move" a table containing several CLOB columns and also how do I rebuild the LOB indexes?
I also made a test with too many columns (> 254) - but don't want to add the code here ... For a table with 300 columns and 10000 rows I got a CHAIN_CNT of 667: but at the moment I don't have the time to find a good interpretation for that number ...
-- 184.108.40.206 -- blocksize 8K create table test_chaining2 ( col1 number , col2 varchar2(4000) , col3 varchar2(4000) ); insert into test_chaining2 select 1, lpad('*', 4000, '*'), lpad('*', 4000, '*') from dual; select table_name, chain_cnt from user_tables where table_name = 'TEST_CHAINING2'; TABLE_NAME CHAIN_CNT ------------------------------ ---------- TEST_CHAINING2 1
ji li wrote:post SQL that was used to "gather stats".
Thanks for your help Martin.
I've tried creating a simple table as select * from 'trouble_table' where rownum < 11, then gathered stats on the table, but the CHAIN_CNT was 0.
Maybe this is an indication that the CHAIN_CNT I have on the actual table is from real row migration or chaining rather than intra-chaining due to too many columns.