Re: oracle and solaris 2.6

Two tips :

1. Go for raw filesystems
2. If u can afford the space, go for bit-mapped indexes, they increase speed drastically (and use space drastically too).

Rgds,

In article <7kc1e2$evq$1_at_oak.prod.itd.earthlink.net>,   "Oliver Niesen" <oliver_at_allpayments.com> wrote:
> i just got oracle installed on solaris 2.6. my problem is that i have
a dump
> file that is in excess of 4gb that i need to get imported in a timely
> manner. i am using a block size of 8192 ( i dont know yet what effect
that
> will have once it becomes a production machine, since its mainly small
> transactions that we run) and forcing direct i/o on those partitions
holding
> the oracle tablespaces. i have shaved considerably time with those two
items
> alone. but i am wondering if anybody has other tricks like messing
with the
> fsflush daemon and what the consequences are of running direct i/o and
large
> block_size in a production environment with mostly oltp and some
batching?
> any input or similar experiences would be greatly appreciated.
>
> thanks in advance!
>
>

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Mon Jun 21 1999 - 04:15:34 CDT