标签云
asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-00742 ORA-01110 ORA-01555 ORA-01578 ORA-01595 ORA-08103 ORA-600 2131 ORA-600 2662 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 Oracle 恢复 ORACLE恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (103)
- 数据库 (1,741)
- DB2 (22)
- MySQL (75)
- Oracle (1,590)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (161)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (68)
- Oracle Bug (8)
- Oracle RAC (54)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (28)
- Oracle备份恢复 (582)
- Oracle安装升级 (95)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (84)
- PostgreSQL (27)
- pdu工具 (5)
- PostgreSQL恢复 (9)
- SQL Server (30)
- SQL Server恢复 (11)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (37)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (20)
-
最近发表
- GAM、SGAM 或 PFS 页上存在页错误处理
- ORA-600 krhpfh_03-1208
- VMware勒索加密恢复(vmdk勒索恢复)
- ORA-39773: parse of metadata stream failed故障处理
- sql数据库备份失败—失败: 23(数据错误(循环冗余检查)
- vmdk文件被加密恢复(虚拟机文件加密)
- 差点被误操作的ORA-600 kcratr_nab_less_than_odr故障
- win平台19c 打patch遭遇2个小问题汇总
- pg单个数据库目录恢复-pdu恢复单个数据库目录数据
- pg删除数据恢复—pdu恢复pg delete数据
- .[OnlyBuy@cyberfear.com].REVRAC勒索mysql恢复
- 表dml操作权限授权给public,导致只读用户失效
- 21c数据库恢复遭遇ora-600 ktugct: corruption detected
- pg_control丢失/损坏处理
- 当前主流数据库版本服务支持周期-202503
- pg启动报invalid checkpoint record处理
- 删除redo导致ORA-00313 ORA-00312故障处理
- Navicat连接postgresql时出现column “datlastsysoid” does not exist错误解决
- aix磁盘损坏oracle数据库恢复
- pg误删除数据恢复(PostgreSQL delete数据恢复)
标签归档:ORA-21779
ORA-21779错误处理
有客户win 10.2.0.4的rac,查看alert日志发现如下错误
Mon May 04 17:25:18 2020 Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl2_smon_2548.trc: ORA-21779: 持续时间不活动 ORA-06512: 在 line 1 Mon May 04 17:25:28 2020 Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl2_smon_2548.trc: ORA-21779: 持续时间不活动 ORA-06512: 在 line 1 Mon May 04 17:25:38 2020 Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl2_smon_2548.trc: ORA-21779: 持续时间不活动 ORA-06512: 在 line 1 Mon May 04 17:25:39 2020 Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl2_smon_2548.trc: ORA-21779: 持续时间不活动 ORA-06512: 在 line 1
查看对应trace
Dump file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl2_smon_2548.trc Sat Aug 31 15:02:39 2019 ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0 vsnsql=14 vsnxtr=3 Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production With the Partitioning, Real Application Clusters, OLAP, Data Mining and Real Application Testing options Windows Server 2003 Version V5.2 Service Pack 2 CPU : 32 - type 8664, 2 Physical Cores Process Affinity : 0x0000000000000000 Memory (Avail/Total): Ph:17543M/32742M, Ph+PgF:19550M/33833M ………… *** 2020-05-04 18:40:35.687 SMON: following errors trapped and ignored: ORA-21779: 持续时间不活动 ORA-06512: 在 line 1 *** 2020-05-04 18:40:45.734 Drop transient type: SYSTPzpEA6olJSImGURLObkiE6w== *** 2020-05-04 18:40:45.734 SMON: following errors trapped and ignored: ORA-21779: 持续时间不活动 ORA-06512: 在 line 1 *** 2020-05-04 18:40:55.812 Drop transient type: SYSTPzpEA6olJSImGURLObkiE6w== *** 2020-05-04 18:40:55.812 SMON: following errors trapped and ignored: ORA-21779: 持续时间不活动 ORA-06512: 在 line 1 *** 2020-05-04 18:41:05.875 Drop transient type: SYSTPzpEA6olJSImGURLObkiE6w== *** 2020-05-04 18:41:05.875 SMON: following errors trapped and ignored: ORA-21779: 持续时间不活动 ORA-06512: 在 line 1
出现该问题是由于oracle的smon进程无法清理掉 transient types,从而出现该问题,根据官方的说法,这个错误是不会影响数据库正常使用,但是可以通过以下方法暂时规避这种错误:
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) 重启数据库,可以暂时规避
具体参考:
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)