trace文件中记录是什么呢？

飞总的这篇博客文章 https://www.xifenfei.com/2020/05/ora-21779.html 应该对你有用。

参考:
SMON: Following Errors Trapped And Ignored ORA-21779 (Doc ID 988663.1)
Receiving ORA-21780 Continuously in the Alert Log and SMON Trace Reports “Drop transient type”. (Doc ID 1081950.1)

2楼、3楼 说的是这个问题，我想知道除了
1)通过设置alter system set events ’22834 trace name context forever, level 1′禁止smon清理transient types,从而来规避该错误,但是可能会引起transient types对象越来越多,当然你可以通过以下sql查询出来
select o.* from obj$ o, type$ t
where o.oid$ = t.tvoid and
bitand(t.properties,8388608) = 8388608 and (sysdate-o.ctime) > 0.0007;
然后删除掉相关记录DROP TYPE “SYSTPf/r2wN4keX7gQKjA3AFMSw==” FORCE;【这个删除不是必须的】
2) flush shared_pool也可以临时规避这个问题
3) 重启数据库,可以暂时规避

这4种方法，还有打补丁外，引起这个错误的原因transient types到底是什么？
有没有彻底规避这个问题的办法？

[oracle@testserver ~]$ oerr ora 21779
21779, 00000, “duration not active”
// *Cause: User is trying to use a duration that has been terminated.
// *Action: User should avoid performing such operation.
[oracle@testserver ~]$
[oracle@testserver ~]$ oerr ora 21780
21780, 00000, “Maximum number of object durations exceeded.”
// *Cause: This typically happens if there is infinite recursion in the PL/SQL
// function that is being executed.
// *Action: User should alter the recursion condition in order to prevent
// infinite recursion.

有办法追踪是plsql种哪些操作引发的这个ora 21779吗

你还是按MoS的那两篇文章操作吧，文章里说那几种方法可以规避!

按照这几个方法处理过，过段时间又出现了。