Re: PCTFREE & PCTUSED

mike.borden_at_gmail.com (tilwenbr_at_netscape.net) wrote in message news:<2d4a7b11.0410060458.85f0fb1_at_posting.google.com>...
> joel-garry_at_home.com (Joel Garry) wrote in message news:<91884734.0410051646.7a271f26_at_posting.google.com>...
> > mike.borden_at_gmail.com (tilwenbr_at_netscape.net) wrote in message news:<2d4a7b11.0410050819.666c3e1c_at_posting.google.com>...
> Ok, yes I meant LMT. :) They just do not support it. I'm not sure why
> but they do not. I'm thinking becuase when they do updates to the
> schema they explictly set the storage settings and such when a table
> is created. However, I have not tried creating a table with storage
> settings and tried putting that table into a LMT tablespace, so I do
> not know if it would fail or not. I do not have the "privelege of a
> play db" here. I just know that they do not support LMT with 8.1.7.4.
> Hec, they are just supporting 92.

You might consider checking how many extents are being generated, either by a script or using Tablespace Map in OEM. If any table has many thousands, you might consider telling the vendor they are messing you up (not the old myth about performance, but rather abuse of the segment tracking tables in the data dictionary, and perhaps wrong storage parameters). Google this group for LMT for more details. We would be interested in hearing the vendors' reasons for not supporting it (my uninformed guess would be they don't want to support customers changing existing working scripts - especially if customers aren't totally familiar with the basics).

There are some vendors who set storage parameters in scripts, to try to cover their general customers, with the intent that larger or more specialized installations will have a DBA to tweak things. Then they don't want to give DBA support to those sorts of installations, leaving the support personnel to give stupid answers.

jg

--
@home.com is bogus.
http://money.cnn.com/2004/10/05/news/fortune500/anheuser_busch.reut/index.htm?cnn=yes