Re: TRUNCATE Table Command

In article <1995Jun22.191832.23480_at_dhnews.dehavilland.ca>, t89003_at_isdserv.dehavilland.ca (Rennick Sandra) writes:
> Tony Jambu (aaj_at_phantom.telecom.com.au) wrote:

>
> We cannot use the REUSE STORAGE option because this table contains a long
> field. The application that uses this table constantly deletes and inserts

I am not sure why you cant use the TRUNCATE command with LONG attributes as I have tried it out and it works.

> (no updates) data. Due to excessive chaining, the free space in the blocks
> does not seem to be reused after a while. Instead, the table gets a new
> extent. Eventually, the table runs out of space in the tablespace. As well,
> the performance decreases; which is again attributed to chaining. This is
> my first experience with using the long datatype. Is there a special way
> that the table should be defined? i.e. PCTFREE and PCTUSED?

There is nothing you can do about chaining of LONG rows except to increase your block size when building the database. What are your PCTFREE and PCTUSED?

ta
tony

-- 
 _____       ________ / ___ |Tony Jambu, Database Consultant
  /_  _        /_ __ /      |Wizard Consulting,Aust (ACN 065934778)
 /(_)/ )(_/ \_/(///(/_)/_(  |CIS: 100250.2003_at_compuserve.com FAX: +61-3-4163559
 \_______/                  |EMAIL:TJambu_at_wizard.com.au PHONE: +61-3-4122905