Logical standby and truncate partition

Question

Hi,
I'm evaluation whether a logical standby database would meet our needs.
We have a live database and want a reporting database that is identical to the live one, just minutes behind in time to the live one, plus we want to create other summary tables etc on the reporting db.
Logical standby seems to meet our needs but I have one query.
- On the live db the most of the tables are organized by date partitions and only 5 days are kept with new partitions being created every night for the forthcoming days and the oldest date partitions being truncated.
On the reporting database we want to keep 30 days partitions.
Can we have all the DDL and DML from live being applied to the standby APART from the specific truncate partition statements?
Many Thanks,
Kailas

Answer 1

Addendum.
If you can , it is better to truncate the partition but not drop it, after exporting the partition for archive purposes. If you ever need to bring the data back, the data will go into the correct partition . If the table structure has been changed by adding or lengthening columns, this will still work OK where column names match.
Test ease of restoration of archived data to existing and non-existing partitions with altered structure (dropped columns,added columns, renamed columns) for yourself though.
Regards, Vin.
PS. When splitting maxdata partition to create new 'highest' partition, use a small initial extent then the 'next' being the expected real size needed. When the partition is truncated, the only space that should remain un-claimable will be that allocated for the initial extent.