当前位置：网站首页>Space not freed after TRUNCATE table

Space not freed after TRUNCATE table

2022-08-09 23:44:00 【change】

oracle version 11.2.0.4

Truncate a batch of tables. Before the operation, I checked the size of dba_segments, a total of 500G. After truncate, the table space is still so large, and there is no more space in v$asm_diskgroup. What is the reason?



Accepted answer 1:

image.png

image.png
Content from:
https://blog.csdn.net/u010371854/article/details/9118323

You see if it fits your situation.


Other Answer 1:

image.png

image.png
Content from:
https://blog.csdn.net/u010371854/article/details/9118323

You see if it fits your situation.


Other Answer 2:

v$asm_diskgroup This is queried, and the data file corresponding to the tablespace needs to be resized before it will change.
Look, are these tables of truncate in the tablespace you checked?


Other Answer 3:

Yes, I recorded the capacity and usage ratio of the tablespace before the TRUNCATE operation.


Other Answer 4:

It may be the cause of INITIAL_EXTENT, You try to shrink the truncate table

原网站

版权声明
本文为[change]所创，转载请带上原文链接，感谢
https://yzsam.com/2022/221/202208091603458709.html

边栏推荐

猜你喜欢

随机推荐