This content has been marked as final. Show 6 replies
yes,,,you have to rebuild the indexes....
Use the UPDATE INDEXES clause if you want to keep the undexes usable.
Please can somebody tell me the concequences of this statement.
I am concerned about the existing data in the table will it by any change gets deleted, and what about indexes, do I have to rebuild, etc.
No - no data will get deleted. As others have said there are options for keeping the indexes up-to-date or you can rebuild them.
I cannot test this as I don't have a test environment and moreover the table is having 70 million records and we don't have time/hardware resources to recreate this by export import in another database.
That's the lamest excuse I have heard on the forums in a long time. You have several hours to post and thread and then wait to see if there is anyone you don't know and have never worked with that will respond but you don't have a couple of hours to do a simple test?
Seventy million records is nothing and if you do the test on a PC using a version of Oracle that you can download for free.
Anyone that doesn't test changes going into their production environment should NOT be working in this field: they should find a new line of work. That is incompetence at its worst.
The SPLIT PARTTION test doesn't need a lot of data: just some data for each of the two resulting partitions. You can easily create a clone table using CTAS and then manually add the indexes.
Thanks to all for the response.
I was able to do this task, and to your knowledge please note that Indexes were intact and I needn't rebuild them after completing the split partition task.
And yes I created the table in test environment by expdp/impdp with compression option and tested the split partition task before applying it on production.
Once again Thanks to all.
you have used update indexes clause while splitting the partition as suggested by john.. ???
I cannot test this as I don't have a test environment and moreover the table is having 70 million records and we don't have time/hardware resources to recreate this by export import in another database.If you want to test performance of the SPLIT PARTITION, you would want to create a test table with many million rows.
If you want to test the concept of SPLIT PARTITION (and it's impact on indexes etc), you need to create at table with 2 rows in each partition (including the MAXVALUE partition). The SPLIT should be at a value between the two rows in the partition.
Hemant K Chitale