Hi all,
I just inherited an 8.1.7.4 database running on Solaris 2.8,
16 k block size, using raw devices for database datafiles. The
raw slices all appear to be a uniform size, 200 meg each. As
part of my initial site survey, I noticed that the tablespaces
are all dictionary managed.
Would it be optimal to convert the existing application data
and index tablespaces to locally managed tablespaces?
Does anyone know of any issues/problems when using locally managed
tablespaces with raw devices?
Another question that I do have concerns the proper sizing of
datafiles for new tablespaces. I have only utilized locally
managed tablespaces on OS filesystems. With OS-level datafiles
I usually create datafiles as a multiple of the OS filesystem
block size + 64K for the bitmap header and metadata blocks.
For example:
OS block size datafile size
------------- -------------
8k 256 meg + 64k
With raw disk slices, the OS filesystem is bypassed. What then
should be the optimal "formula" when creating new datafiles?
Thanks,
Lou Avrami
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Louis Avrami
INET: [EMAIL PROTECTED]
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
