Re: PCTFREE & PCTUSED

Stupid me! I was too busy trying to find the answer based on a complicated reasoning, I overlooked the obvious and plain answer for question 5 --- I realise it now -- increase MAXEXTENTS for a table that grows significantly. Shows what overenthusiasm can do to you. You get lost in your own world a bit.

So anyway the revised Q&A (subject to any other corrections) is :-

> Q: Which parameter reserves the more space for future updates
>
> 1. high PCTINCREASE
> 2. high PCTFREE ** CORRECT **
> 3. high INITIAL
> 4. high PCTUSED
>
> Q: Row migration is a result of
>
> 1. high PCTFREE
> 2. low PCTFREE ** CORRECT **
> 3. high PCTUSED
> 4. low PCTUSED
>
> Q: If the space usage parameters are set to the default clause, which change
> could cause higher processing costs because blocks will be considered
> free more often.
>
> A. raising PCTUSED ** CORRECT **
> B. raising PCTFREE
> C. lowering PCTUSED
> D. lowering PCTFREE
>
> Q : Which setting for the storage parameter should you use if tables are
> updated very infrequently
>
> 1. low PCTUSED
> 2. high PCTUSED
> 3. low PCTFREE ** CORRECT **
> 4. high PCTFREE
>
> Q : If your table grows significantly, which storage parameter should you
> increase
>
> 1. MAXEXTENTS ** CORRECT **
> 2. PCTINCREASE ^H^H^H^H^H^H^H
> 3. PCTFREE
> 4. PCTUSED
>
> Q: Which parameter value should you use if tables have frequent inserts and
> deletes
>
> 1. low PCTUSED ** CORRECT ** (I think - reason :- lowers freelist processing?)
> 2. high PCTUSED
> 3. low PCTFREE
> 4. high PCTFREE
>
> Q: You are creating the LINE_ITEM table that will experience extensive
> insert activity.
> Which space utilization parameter setting is most appropriate for the table?
>
> A. low PCTUSED
> B. low PCTFREE
> C. high PCTUSED
> D. high PCTFREE ** CORRECT **

All the best,

David P. Received on Thu Mar 09 2000 - 00:00:00 CST