| |
 |
|
Donald K. Burleson
Oracle Tips |
Oracle tablespaces
CWMLITE. This Oracle tablespace is
used to store OLAPSYS schema objects for the new Online Analytical
Processing (OLAP) utilities in Oracle and is created when the
default templates in the DBCA are used to create a database.
DRSYS. Used to store CTXUSER and WKSYS schema objects used in
advanced indexing options and workspace management utilities and is
created when the default templates in the DBCA are used to create a
database.
Each application should have its own set of data and index
tablespaces. If there are several small applications, you might want
to put them in a single large tablespace; but if you can avoid this,
it makes application management easier. Each application should also
have its own index tablespace. This results in a simple formula for
determining the number of tablespaces:
5 + 2 times the number of applications expected
Some applications may require multiple tablespaces, for example
where, for performance, you want to separate out large tables from
the rest of the application. In one case, a single application
generated 13 tablespaces. Most applications aren’t as complicated as
this and will only require two tablespaces. Of course, the purists
will claim each table should be in its own tablespace, but this
often is overkill. If you are looking at Oracle Applications
installs, there may be over 100 tablespaces configured.
How to size tablespaces is a difficult question to answer because
each tablespace will have unique requirements. Here are some general
guidelines:
This is an
excerpt by Mike Ault’s book “Oracle
Administration & Management”. If you want more current Oracle tips
by Mike Ault, check out his new book “Mike
Ault’s Oracle Internals Monitoring & Tuning Scripts” or
Ault’s Oracle Scripts Download.
|
