Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle9.2: Data segment compression bug

Re: Oracle9.2: Data segment compression bug

From: Thomas Kyte <tkyte_at_oracle.com>
Date: 17 Nov 2002 11:58:07 -0800
Message-ID: <ar8scf0j7q@drn.newsguy.com>


In article <55a68b47.0211170813.3828148b_at_posting.google.com>, ydias_at_hotmail.com says...
>
>Hi,
>
>There is a whitepaper at this address :
>
>http://otn.oracle.com/products/bi/pdf/o9ir2_compression_twp.pdf
>
>Do you know which dictionary table or view indicates that a table is
>compressed or not ?
>

see
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:5320698733090

for a method

>Thanks
>
>
>"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message
>news:<ar2887$cv4$1$8302bc10_at_news.demon.co.uk>...
>> It's not a but, it's expected behaviour.
>>
>> The documentation is almost non-existent,
>> but you're only expected to compress tables
>> (or partitions) before making them read-only.
>>
>> You should also note that when you compress
>> a table, the PCTFREE switches to zero - it's a
>> little clue that you aren't expected to do any
>> normal DML on the table.
>>
>> I believe there may be a whitepaper about it on
>> OTN by now.
>>
>> --
>> Regards
>>
>> Jonathan Lewis
>> http://www.jlcomp.demon.co.uk
>>
>> Next Seminar dates:
>> (see http://www.jlcomp.demon.co.uk/seminar.html )
>>
>> ____USA__________November 7/9 (Detroit)
>> ____USA__________November 19/21 (Dallas)
>> ____England______November 12/14
>>
>> The Co-operative Oracle Users' FAQ
>> http://www.jlcomp.demon.co.uk/faq/ind_faq.html
>>
>>
>>
>>
>>
>> Vsevolod Afanassiev wrote in message
>> <4f7d504c.0211142142.4c1b75d4_at_posting.google.com>...
>> >It seems that when a table is created with COMPRESS attribute
>> >and then populated via conventional INSERT, the
>> >compression does not work. However, if a table
>> >is populated via direct load insert (using SQL*Loader or /*+ APPEND
>> */
>> >hint), then compression works.
>> >This can be seen from the fact that the segment size is approx. twice
>> >smaller (table consists of multiple small extents of the same size).
>> >
>> >After a table is created, then
>> >ALTER TABLE name MOVE COMPRESS;
>> >will compress it no matter how it was created.
>> >
>> >The happens for both partitioned and non-partitioned tables
>> >and locally managed and dictionary-managed tablespaces.
>> >
>> >Environment:
>> >Sun Solaris 8
>> >Oracle 9.2.0.2.0 (32bit), 16k blocks

--
Thomas Kyte (tkyte@oracle.com)             http://asktom.oracle.com/ 
Expert one on one Oracle, programming techniques and solutions for Oracle.
http://www.amazon.com/exec/obidos/ASIN/1861004826/  
Opinions are mine and do not necessarily reflect those of Oracle Corp 
Received on Sun Nov 17 2002 - 13:58:07 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US