By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,237 Members | 1,256 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,237 IT Pros & Developers. It's quick & easy.

reorgs taking a long time

P: n/a
Hi all,

Ive got a script Ive built which runs reorgs on all tables needing it
based on output of reorgchk. The reorgs are ran inline. This past
weekend, the reorgs were running against 450 tables on a database that
is about 250 GB in size. The reorgs took all weekend and bled into
the week. Ultimately they did not finish. Where should I start
looking to speed this up? Thanks

rdudejr

Aug 8 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
"rdudejr" <rd*****@gmail.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
Hi all,

Ive got a script Ive built which runs reorgs on all tables needing it
based on output of reorgchk. The reorgs are ran inline. This past
weekend, the reorgs were running against 450 tables on a database that
is about 250 GB in size. The reorgs took all weekend and bled into
the week. Ultimately they did not finish. Where should I start
looking to speed this up? Thanks

rdudejr
What is an "inline" reorg? There are regular and on-line reorgs. A script
that runs a regular reorg does so sequentially, one table at a time. A
script that does an on-line reorg does it asynchronously, starting the next
reorg before the last reorg has finished. That has implications regarding
the amount work space needed for the reorgs if they are done simultaneously.

A reorg needs lots work space to run efficiently, either free space in the
tablespace where the table and indexes are located, or in a system temporary
tablespace if you specify that it be used for the reorg (see the REORG
command).
Aug 9 '06 #2

P: n/a
It was actually "inplace" that I meant to say....and do you think it
would help if I specified a temporary tablespace to be used? And can
one do so on the fly or does the tablespace have to already exist?
Mark A wrote:
"rdudejr" <rd*****@gmail.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
Hi all,

Ive got a script Ive built which runs reorgs on all tables needing it
based on output of reorgchk. The reorgs are ran inline. This past
weekend, the reorgs were running against 450 tables on a database that
is about 250 GB in size. The reorgs took all weekend and bled into
the week. Ultimately they did not finish. Where should I start
looking to speed this up? Thanks

rdudejr

What is an "inline" reorg? There are regular and on-line reorgs. A script
that runs a regular reorg does so sequentially, one table at a time. A
script that does an on-line reorg does it asynchronously, starting the next
reorg before the last reorg has finished. That has implications regarding
the amount work space needed for the reorgs if they are done simultaneously.

A reorg needs lots work space to run efficiently, either free space in the
tablespace where the table and indexes are located, or in a system temporary
tablespace if you specify that it be used for the reorg (see the REORG
command).
Aug 9 '06 #3

P: n/a
One more thing that should help...this is an SMS tablespace, so would
that mean that it does not use any "extra" space in the tablespace to
do the reorg? Or will it make space temporarily?

rdudejr wrote:
It was actually "inplace" that I meant to say....and do you think it
would help if I specified a temporary tablespace to be used? And can
one do so on the fly or does the tablespace have to already exist?
Mark A wrote:
"rdudejr" <rd*****@gmail.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
Hi all,
>
Ive got a script Ive built which runs reorgs on all tables needing it
based on output of reorgchk. The reorgs are ran inline. This past
weekend, the reorgs were running against 450 tables on a database that
is about 250 GB in size. The reorgs took all weekend and bled into
the week. Ultimately they did not finish. Where should I start
looking to speed this up? Thanks
>
rdudejr
>
What is an "inline" reorg? There are regular and on-line reorgs. A script
that runs a regular reorg does so sequentially, one table at a time. A
script that does an on-line reorg does it asynchronously, starting the next
reorg before the last reorg has finished. That has implications regarding
the amount work space needed for the reorgs if they are done simultaneously.

A reorg needs lots work space to run efficiently, either free space in the
tablespace where the table and indexes are located, or in a system temporary
tablespace if you specify that it be used for the reorg (see the REORG
command).
Aug 9 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.