21779: duration not active问题解决方法(2)

This issue does not affect database functionality and the only problem is that the alert.log is filling up with many error messages (also after restarting the instance the error should not occur again).

The command "alter system flush shared_pool" could also resolve the problem.

是个小BUG,说明上说不影响使用,但是会产生大量的日志,使得alert日志快速增长,解决办法是通过设置22834内部事件,但是这样会导致数据库内的 transient types 增长,显然在生产库这样也是不行的,最后提到可以重启下数据库实例,可能这个错误就不再产生,也可以通过命令alter system flush shard_pool

清理下共享池也可以解决这个问题,双管齐下,该问题解决。

内容版权声明:除非注明,否则皆为本站原创文章。

转载注明出处:https://www.heiqu.com/f2abb0ae0fd1d3a5075b339fc3d5c2e7.html