This content has been marked as final. Show 6 replies
So is your question about partitioning or upgrading?
my question is for partitioning with minimum downtime with zero data loss.
the scenario is like
I took a export of source table and create a new partitioned table with different name, then import the data into new table, drop the source table and rename the new partitioned table with the source tables's name. Its all fine because there will be very minimum downtime but here we will loss some data. It is because the transactions which are done in the mean time will not be in the exported file. Is there any way another..? I hope you got my question.
Take a look at the DBMS_REDEFINITION package.
You can't be using DBMS_REDIFINITION if you want to run both the Upgrade and the table Partitioning (i.e. DBMS_REDEFINITION cannot be used across the upgrade).
You should split these as two separate actions. I would recommend an Upgrade first followed by implementation of Partitioning later.
You must test your Partitioning design in a test environment to see that it meets performance (query and DML) requirements and data maintenance requirements.
Hemant K Chitale
Edited by: Hemant K Chitale on Jan 22, 2013 3:04 PM
thanks for the suggestions..i will try partition exchange. thanks a lot.