How to create ddl for partitioning for a child table?

Question

Hi folks,
I am new to the partitioning topic. I red some manuals and tutorials but I did not found exactly what I need. So I would ask for your help.
I have two tables.
The partitioning of the master table is clear:
create TABLE ASP_PARTITION_TABLE_MASTER
MASTER_ID VARCHAR2(20) NOT NULL
, TIMESTAMP DATE
, DATA VARCHAR2(20)
, CONSTRAINT ASP_PARTITION_TABLE_MASTE_PK PRIMARY KEY
MASTER_ID
USING INDEX
ENABLE
PARTITION BY RANGE (TIMESTAMP)
PARTITION PARTITION1 VALUES LESS THAN (TO_DATE('20090101','YYYYMMDD')) NOCOMPRESS
, PARTITION PARTITION2 VALUES LESS THAN (TO_DATE('20100101','YYYYMMDD')) NOCOMPRESS
, PARTITION PARTITION3 VALUES LESS THAN (TO_DATE('20110101','YYYYMMDD')) NOCOMPRESS
This table should be partitioned by a timestamp.
Now comes the difficulty:
I have a child table which has the master_id as foreign key. The slave table should also be partitioned by the timestamp - but this one occurs only in the master table.
CREATE TABLE ASP_PARTITION_TABLE_SLAVE
SLAVE_ID VARCHAR2(20) NOT NULL
, FK_MASTER_ID NUMBER(10)
, DATA1 VARCHAR2(20)
, DATA2 VARCHAR2(20)
, COLUMN1 VARCHAR2(20)
, CONSTRAINT ASP_PK_SLAVE PRIMARY KEY
SLAVE_ID
ENABLE
ALTER TABLE ASP_PARTITION_TABLE_SLAVE
ADD CONSTRAINT ASP_FK_MASTER_IS FOREIGN KEY
SLAVE_ID
REFERENCES ASP_PARTITION_TABLE_MASTER
MASTER_ID
ON DELETE CASCADE ENABLE;
How can I create such a range partition for the slave table?
PS: Currently we are using oracle 10.2 but we will upgrade to oracle 11g in near future.
Thanks in advance,
Andreas

Answer 1

@sb92075:
seems if I should give more details:
the parent table is holding the master_id, the timestamp and plenty of general information which is valid for all children.
Each parent has between 5 and 50 children which contain different data items. So our child table is much bigger than the parent table.
Our selects are joining parent and child table filtered by the timestamp and some other indexed rows, so we are not saving the same timestamp redundantly.
@bluefrog
With the partitioning we would like to reach the following goals:
1. gain more performance (quicker response time)
2. get the ability to archive and drop partitions which are older than a specific timestamp. (We only need to keep the data of the last 1.5 years so we would like to drop the complete partition / tablespace instead of using a delete-statement which generates much load (transaction, archive, logging)).
Thank you for your links. I will have a look on it.
But due to the archiving issue we would also like split up the child table by the timestamp of the parent table.
Regards, Andreas