View previous topic :: View next topic
|
Author |
Message |
nkumar
New User
Joined: 09 Mar 2008 Posts: 28 Location: USA
|
|
|
|
Hi All!!
I want to discuss a scenario at my workshop. We have to often REORG our DB2 table to tune it. REORG works fine when tables contain smaller volume of data.
But when the table is big (in terms of volume), it often gives space error. We tried to increase the temporary work files used by REORG but it did not work. So we take sequential unload of that table, then sort it and then load back in to the table.
But this process takes too much time to get complete. Can anyone suggest a better approach to do the REORG in more time efficient manner??
Please let me know if I need to provide more information. |
|
Back to top |
|
|
Peter Nancollis
New User
Joined: 15 Mar 2011 Posts: 47 Location: UK
|
|
|
|
you dont reorg tables - you reorg tablespaces
how long to reorg - how long to unload/load?
what is the constraint on the reorg? - what fails
Is this a real problem or imaginary ? |
|
Back to top |
|
|
sushanth bobby
Senior Member
Joined: 29 Jul 2008 Posts: 1020 Location: India
|
|
|
|
nKumar,
You have give in more details to get some realistic answer, like
How many rows does the table have ?
What is the total length of the row ?
Is it partitioned or non-partitioned ?
Show us your error details ?
How often REORG is done(weekly, bi-weekly, monthly or based on some condition) like that ?
when is the REORG Job executed like on maintainence window(when there is no online or when system is less busy) ?
And do show us your current REORG Statements.
Without these kind of information, everybody reading this post will think exactly as peter said"Is this a real problem or imaginary ?"
Thanks,
Sushanth |
|
Back to top |
|
|
|