Database Reference
In-Depth Information
Creating tablespaces and table partitions
At this point, you will have to decide how you want to partition your tables, spe-
cifically what date range to divide the data, as well as identify which tablespace
each of the partitions will reside in. The DBA may also decide to specify different
storage parameters for each tablespace. In this section, we cover generic ex-
amples that should be customized by the DBA.
Before proceeding, make sure you shut down your Oracle SOA Suite 11g infra-
structure (but not the database!). In this example, we separate the data by year,
having each range in its own separate tablespace. To do this, we will create two
separate tablespaces; soa_ts_2011 and soa_ts_2012 , residing on two sep-
arate physical disks:
CREATE TABLESPACE soa_ts_2011
DATAFILE '/u01/app/oracle/oradata/orcl/soa_ts_2011.dbf'
SIZE 5G
REUSE
AUTOEXTEND ON
NEXT 128M
BLOCKSIZE 8192
EXTENT MANAGEMENT LOCAL AUTOALLOCATE
SEGMENT SPACE MANAGEMENT AUTO;
CREATE TABLESPACE soa_ts_2012
DATAFILE '/u02/app/oracle/oradata/orcl/soa_ts_2012.dbf'
SIZE 5G
REUSE
AUTOEXTEND ON
NEXT 128M
BLOCKSIZE 8192
EXTENT MANAGEMENT LOCAL AUTOALLOCATE
SEGMENT SPACE MANAGEMENT AUTO;
We have already identified that the SOA Infrastructure requires partitioning
of
all
of
the
following
nine
tables:
COMPOSITE_INSTANCE,
Search WWH ::




Custom Search