Dear Group,

I have the task of designing a table with similar characteristics of
Oracle range partitioning.

Note: we are migrating from ORacle to DB2 and we have many tables with
range partitions. The success or failure of the migration depends
mainly on, how we can get the range partition works.

In Oracle we have one table with 13 partition each having one month
worth of data. The oldest patition is droped after the newest
partition is loaded successfully.

This is what I am thinking for DB2:
-----------------------------------
(Note: there will be large amount of data and delete is not an option)

Create 13 tables (12 for the active months and one to act as a
temporary load table )
Create a UNION ALL view on top of the 12 active tables.

I want to have these tables available almost all the time.

I load the latest month into table_13 and if sucsessful, truncate
table_1.

The issue here is, I have to drop and recreate the view, every time
when I load the data, to point to the 12 active tables.

Is there any way, I can create the views on top of all the 13 tables
(so that I do not have to drop and recreate the tables everytime) and
the access is restricted to only the active 12 tables? (In otherwords
make the DB2 to ignore the oldest table while accessing if there are
13 tables in the view)

Any other approaches to implement this effectively?

I am pretty sure, atleast few of you might have migrated from Oracle
to DB2. How did you implement range partitioning (with high
availability for these tables)?

Thanks,
Sandi.