Home » RDBMS Server » Server Administration » Partitioning Tables (12.1.0.2.0,Oracle Linux 7,x86_64)
Partitioning Tables [message #643786] Sun, 18 October 2015 08:53 Go to next message
preet_kumar
Messages: 199
Registered: March 2007
Senior Member
The Database size including tables,indexes etc is 400G and of this 300GB is used by one single table and its indexes.
Now i would like to partition this.
What would be the best way to do this in a production environment without disrupting the application which heavily uses this table.

Thanks
Re: Partitioning Tables [message #643787 is a reply to message #643786] Sun, 18 October 2015 08:55 Go to previous messageGo to next message
BlackSwan
Messages: 25848
Registered: January 2009
Location: SoCal
Senior Member
preet_kumar wrote on Sun, 18 October 2015 06:53
The Database size including tables,indexes etc is 400G and of this 300GB is used by one single table and its indexes.
Now i would like to partition this.
What would be the best way to do this in a production environment without disrupting the application which heavily uses this table.

Thanks



post SQL & results that show the problem that partitioning will solve.

post sample DDL that shows how you propose to partition the table.
Re: Partitioning Tables [message #643788 is a reply to message #643786] Sun, 18 October 2015 09:26 Go to previous messageGo to next message
John Watson
Messages: 7255
Registered: January 2010
Location: Global Village
Senior Member
If used appropriately, partitioning can deliver benefits; used inappropriately, it may be disastrous. You need to prove, mathematically, that your chosen table and index partitioning strategies will solve your problem, without introducing others. And by "problem", I mean something real: your overnight batch jobs don't finish till lunchtime, or a screen refresh takes 5 seconds and you need it on 1. Just because the table is 300GB is no reason to partition it.

More information needed!
Re: Partitioning Tables [message #643791 is a reply to message #643786] Sun, 18 October 2015 11:07 Go to previous messageGo to next message
Michel Cadot
Messages: 65377
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

You post questions and questions and questions and never feedback no more thank to our help and answer to our questions.
It is time you review all your previous topics and give feedback.

[Updated on: Sun, 18 October 2015 11:08]

Report message to a moderator

Re: Partitioning Tables [message #646619 is a reply to message #643791] Tue, 05 January 2016 12:47 Go to previous message
garan
Messages: 27
Registered: January 2016
Junior Member
Hi

I think you need to test thoroughly in the lower environment like QA by partitioning the table. Partitioning might help solving in one area and might introduce a problem in another area, You need to test the whole application thoroughly wherever the table is accessed. Again whether you go for range partitioning or list partitioning is business/process driven. If you are loading the data once in a month and if you frequently access one month data then it is better to go for monthly range partitioning.

I would suggest you implement the partitioning during weekends or when there is downtime in production

After partitioning you might have to regather the table and index statistics

garan
Previous Topic: EXP-00008: ORACLE error 1406 encountered ORA-01406: fetched column value was truncated EXP-00000: Ex
Next Topic: default optimizer_mode
Goto Forum:
  


Current Time: Sat Feb 17 16:24:19 CST 2018

Total time taken to generate the page: 0.01368 seconds