Is coalesce required after converting TBS from DMT to LMT ?
Oracle is currently working on an SR on this topic, while we are diagnosing the problem we are opening up this question to our user community so they can add perspective to the solution based on their real world experience
We have a lot of dictionary managed tablespaces which we scheduled to convert to locally managed. However, after conversion, we found that the maximum free segments dropped significantly. Did the converted locally managed tablespace can coalesces by themselves ? Can we perform a manual coalesce on the tablespace ?
At our environment , we found the max free segments dropped significantly (from 30GB to 2GB) after the tablespace conversion ( after 2 weeks from the conversion) although the total free space is similar around 50GB.
We have a lot of dictionary managed tablespaces which we scheduled to convert to locally managed. However, after conversion, we found that the maximum free segments dropped significantly. Did the converted locally managed tablespace can coalesces by themselves ? Can we perform a manual coalesce on the tablespace ?
At our environment , we found the max free segments dropped significantly (from 30GB to 2GB) after the tablespace conversion ( after 2 weeks from the conversion) although the total free space is similar around 50GB.
0