PLATINUM TSREORG Part 2
Date: 1995/05/18
Message-ID: <3pgh0q$ma$2_at_mhade.production.compuserve.com>#1/1
Howie,
Repost PART 2:
To deal with this problem, in 1.0.18 of TSreorg, we put in
the same "hack" that is used by many DBA's to recoalese ORACLE6
free space -- that is to create a table the size of the total
free space and then drop it. This works except for one problem,
ORACLE 7.1.x has a bug(ora bug # 248875) that causes dropped
index extents to appear as temporary used extents for a period of
about an hour after the index was dropped. Of course this
prevents the "create on big table" workaround mentioned above
from working. We are told by ORACLE that this bug is fixed in
7.1.6 and 7.2.
It is important to note that all other aspects of the tablespace
reorg are not affected. This includes defragmentation of used
extents, removal of row chaining, removal of row migrations,
recovery of wasted space, etc. etc... With regard to eventually
eliminating the "create one big table" hack, ORACLE has admitted
that there needs to be a way to ask "smon" to wake-up and perform
its duties by non-ORACLE processes. They have not given us a
release number where this feature will appear yet.
Richard Headley
V.P. Dimeric Development Lab
PLATINUM technology, inc
SALES: 800-442-6861, 708-620-5000, Tech Support 800-691-0708
Received on Thu May 18 1995 - 00:00:00 CEST