Partition. Even on 7, obvious in this case would be
partition views with maybe some changes in the app. Or
maybe not depending the app.
Stripping. Oracle stripping and OS stripping.
Freelists. It seems that the app insert and query.
Because of the inserts it is a perfect case of
freelists. If
Partitioning, Parallel Query.
Do not criticize someone until you walked a mile in their shoes, that way
when you criticize them, you are a mile a way and have their shoes.
Christopher R. Spence
Oracle DBA
Phone: (978) 322-5744
Fax:(707) 885-2275
Fuelspot
73 Princeton Street
North,
I have a big table too, about 16GB.
It is a vert static one(customer table), will add data
once in it, but queried all the time, and do the
segmentations against it all the time.
It also has 12 indexes. Right now , the performance is
ok. Any special consideration for such a big table.
Thanks,
Walter,
Couple of other areas to watch while DMLs are being issues against this
table are: LGWR and DBWR statistics and activities. Based on DBWR/LGWR
statistics, you may need to tune these parameters.
Jay
-Original Message-
Sent: Monday, August 20, 2001 5:31 PM
To: Multiple recipients
Don't put it in a buffer keep because of the amount of
consistent gets the table could have. It seems to be a
high volatile table.
Maybe it is too late but you should look on the
initrans, freelist of the table. Also if the table has
foreign keys, talk with Development to leave the table
without
Good point about the FKs. Fortunately, the table is
stand-alone is is not a parent or a child of any other
table. I thought about initrans and freelists but the
table will only be touched by a single user process
which is running in the background performing all of
the DML transactions, much like
Also I would have high PCTFREE to lessen number of records per block - if
you will have a lot of buffer busy waits. If you have enough memory - simply
increase size of KEEP pool to get enough space for needed number of CR
blocks. You will have to experiment with size of KEEP pool and
