谢谢

惜分飞,

谢谢回应。
示例里是注释的，注释了才是原始环境。

我想表达的意思是，10.2.0.5.0和11.2.0.4.0
两版本，不是应该默认释放掉的么？

我们已经测试，在10205中依旧有该问题，对于11204，我尚未测试，不清楚

谢谢回应。
示例里是注释的，注释了才是原始环境。

我想表达的意思是，10.2.0.5.0和11.2.0.4.0
两版本，不是应该默认释放掉的么？

你好,
我想知道,这个所谓的FIXED是指什么意思.
根据文章的脚本,我在10.2.0.5.0和11.2.0.4.0上测试,得到的结果,都是:
SQL> connect xifenfei/tc@A_SYJ
Connected to Oracle Database 10g Enterprise Edition Release 10.2.0.5.0
Connected as xifenfei@A_SYJ
SQL> –alter session set events ’60025 trace name context forever’;
SQL> select to_nclob(‘a’) from dual;
TO_NCLOB(‘A’)
——————————————————————————–
a
SQL> select t.blocks from v$tempseg_usage t where t.username like ‘%XIFENFEI%’; BLOCKS
———-128
SQL> commit;
Commit complete
SQL> select t.blocks from v$tempseg_usage t where t.username like ‘%XIFENFEI%’; BLOCKS
———-128
SQL>

是我这安装有问题?
是更高版本BUG又回来了?

我看你的 –alter session set events ’60025 trace name context forever’; 是注释掉的，如果注释了，就有该问题

是我这安装有问题?
是更高版本BUG又回来了?

While using temporary LOBs the temp segment used for this 
purpose remains active until the session exits.
When there is a request to cleanup those temp lobs we do free space from 
temp tablespace and the same session can reuse it, but the temp segment is not 
released which means it is not available for use to other sessions. 
The actual cleanup happens only on session exit. This is intentional.
 
This fix introduces a new event 60025 such that when there are
no active temp lobs in the session (ie: both cache temp lob and 
no-cache temp lobs used are zero) then the temp segment itself
will also be freed releasing the space for other sessions to use.
 
Note that this change is disabled by default.