标签云
asm 恢复 asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 kfed MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-01110 ORA-01555 ORA-01578 ORA-08103 ORA-600 2662 ORA-600 2663 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)
- 操作系统 (100)
- 数据库 (1,597)
- DB2 (22)
- MySQL (70)
- Oracle (1,463)
- Data Guard (49)
- EXADATA (7)
- GoldenGate (21)
- ORA-xxxxx (158)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (13)
- ORACLE 21C (3)
- Oracle ASM (65)
- Oracle Bug (7)
- Oracle RAC (47)
- Oracle 安全 (6)
- Oracle 开发 (27)
- Oracle 监听 (27)
- Oracle备份恢复 (530)
- Oracle安装升级 (84)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (75)
- PostgreSQL (17)
- PostgreSQL恢复 (5)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (36)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (19)
-
最近发表
- Oracle 19c/21c最新patch信息-202404
- PostgreSQL恢复系列:pg_filedump批量处理
- PostgreSQL部分主要字典信息
- PostgreSQL恢复系列:pg_filedump恢复字典构造
- PostgreSQL 16 源码安装
- ORA-00742 ORA-00312 恢复
- 数据库open成功后报ORA-00353 ORA-00354错误引起的一系列问题(本质ntfs文件系统异常)
- ORA-600 ktsiseginfo1故障
- ORA-00600: internal error code, arguments: [16703], [1403], [4] 原因
- 最近遇到几起ORA-600 16703故障(tab$被清空),请引起重视
- ORA-600 2662快速恢复之Patch scn工具
- TNS-12518: TNS:listener could not hand off client connection
- ora.storage无法启动报ORA-12514故障处理
- 断电引起文件scn异常数据库恢复
- ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
- .[hudsonL@cock.li].mkp勒索加密数据库完美恢复
- 模拟带库实现rman远程备份
- 又一例:ORA-600 kclchkblk_4和2662故障
- Oracle误删除数据文件恢复
- Oracle 19C 备库DML重定向—DML Redirection
标签归档:SCN Compatibility
ORA-00600: internal error code, arguments: [2252], [3987]
客户数据库版本10.2.0.4,启动成功之后立马crash,让我们协助解决
Thu Jul 4 13:03:10 2019 Completed: ALTER DATABASE OPEN Thu Jul 4 13:03:10 2019 db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Thu Jul 4 13:04:01 2019 Errors in file /oracle/app/oracle/admin/orcl/bdump/orcl_reco_22268.trc: ORA-00600: internal error code, arguments: [2252], [3987], [3375047096], [], [], [], [], [] Thu Jul 4 13:04:01 2019 Errors in file /oracle/app/oracle/admin/orcl/bdump/orcl_reco_22268.trc: ORA-00600: internal error code, arguments: [2252], [3987], [3375047096], [], [], [], [], [] Thu Jul 4 13:04:02 2019 Errors in file /oracle/app/oracle/admin/orcl/bdump/orcl_reco_22268.trc: ORA-00600: internal error code, arguments: [2252], [3987], [3375047096], [], [], [], [], [] Thu Jul 4 13:04:02 2019 RECO: terminating instance due to error 476 Instance terminated by RECO, pid = 22268
根据以往经验记录一次ORA-00600[2252]故障解决,很可能是scn过大引起.通过Oracle数据库异常恢复检查脚本(Oracle Database Recovery Check)检查scn相关信息
从ORA-600 2252错误信息看,由于scn可能超过该数据库的天花板理论上而导致该问题,而reco进程主要是由于分布式事务引起,通过和客户确认,该库有通过dblink去访问11204版本oracle,而从2019年6月23日之后scn的算法发生了一些改变(SCN Compatibility问题汇总-2019年6月23日),导致数据库可以支持更大的scn,从而当低版本需要进行分布式事务操作之时,可能导致数据库异常.
处理方案:通过临时屏蔽分布式事务,让数据库临时正常工作;长期解决方案需要把数据库版本升级,避免scn引起相关问题
SCN Compatibility问题汇总-2019年6月23日
最近有不少朋友咨询关于2019年6月23日之前数据库scn,数据库是否要升级或者打补丁等问题,这里对相关问题做一个汇总。
1. 是否一定要升级或者打补丁
不一定,以下几种情况可以不用处理
1) 数据库版本11.1.0.7.20+ /11.2.0.3.9+ /11.2.0.4+版本已经包含了该补丁,无需处理
2) 数据库版本全部低于1)中数据库版本
3) 你的数据库环境中不存在1和2中数据库dblink访问
4) 你的数据库环境中有1和2中的数据库dblink访问,但是通过通过dbms_scn设置,不让1中的数据库版本scn compatibility改变(都保持为1)
2. 到了2019年6月23日之后,数据库的scn发生什么改变
简单的说就是数据库每秒可以使用的scn变大了,距离天花板的scn更加大,出现数据库scn用完的概率大大降低
--compat -- SCN compatibility value --headroom_in_scn -- Difference between current SCN and RSL --headroom_in_sec -- number of seconds it would take to reachRSL SQL> set serveroutput on ; SQL> declare 2 rsl number; 3 headroom_in_scn number; 4 headroom_in_sec number; 5 cur_scn_compat number; 6 max_scn_compat number; 7 begin 8 dbms_scn.GetCurrentSCNParams(rsl,headroom_in_scn,headroom_in_sec,cur_scn_compat,max_scn_compat); 9 dbms_output.put_line('rsl=' || rsl); 10 dbms_output.put_line('headroom_in_scn=' || headroom_in_scn); 11 dbms_output.put_line('headroom_in_sec=' || headroom_in_sec); 12 dbms_output.put_line('cur_scn_compat=' || cur_scn_compat); 13 dbms_output.put_line('max_scn_compat=' || max_scn_compat); 14 end; 15 / rsl=16424869609472 headroom_in_scn=16424867538319 headroom_in_sec=1002494356 cur_scn_compat=1 max_scn_compat=3 PL/SQL procedure successfully completed. SQL> Alter Database Set SCN Compatibility 2; Database altered. SQL> declare 2 rsl number; 3 headroom_in_scn number; 4 headroom_in_sec number; 5 cur_scn_compat number; 6 max_scn_compat number; 7 begin 8 dbms_scn.GetCurrentSCNParams(rsl,headroom_in_scn,headroom_in_sec,cur_scn_compat,max_scn_compat); 9 dbms_output.put_line('rsl=' || rsl); 10 dbms_output.put_line('headroom_in_scn=' || headroom_in_scn); 11 dbms_output.put_line('headroom_in_sec=' || headroom_in_sec); 12 dbms_output.put_line('cur_scn_compat=' || cur_scn_compat); 13 dbms_output.put_line('max_scn_compat=' || max_scn_compat); 14 end; 15 / rsl=21792299122688 headroom_in_scn=21792297051479 headroom_in_sec=665048127 cur_scn_compat=2 max_scn_compat=3 PL/SQL procedure successfully completed. SQL> Alter Database Set SCN Compatibility 3; Database altered. SQL> declare 2 rsl number; 3 headroom_in_scn number; 4 headroom_in_sec number; 5 cur_scn_compat number; 6 max_scn_compat number; 7 begin 8 dbms_scn.GetCurrentSCNParams(rsl,headroom_in_scn,headroom_in_sec,cur_scn_compat,max_scn_compat); 9 dbms_output.put_line('rsl=' || rsl); 10 dbms_output.put_line('headroom_in_scn=' || headroom_in_scn); 11 dbms_output.put_line('headroom_in_sec=' || headroom_in_sec); 12 dbms_output.put_line('cur_scn_compat=' || cur_scn_compat); 13 dbms_output.put_line('max_scn_compat=' || max_scn_compat); 14 end; 15 / rsl=34585263898624 headroom_in_scn=34585261822622 headroom_in_sec=351819476 cur_scn_compat=3 max_scn_compat=3 PL/SQL procedure successfully completed.
这里大概演示了数据库scn compatibility变化带来的相关变化,这里可以看出来每秒
3. 如何禁用/启用scn compatibility自动升级
SQL> begin dbms_scn.DisableAutoRollover; end; 2 / PL/SQL procedure successfully completed. SQL> declare 2 EFFECTIVE_AUTO_ROLLOVER_TS date; 3 TARGET_COMPAT number; 4 IS_ENABLED boolean; 5 begin 6 dbms_scn.GETSCNAUTOROLLOVERPARAMS(EFFECTIVE_AUTO_ROLLOVER_TS,TARGET_COMPAT,IS_ENABLED); 7 dbms_output.put_line('EFFECTIVE_AUTO_ROLLOVER_TS='||to_char(EFFECTIVE_AUTO_ROLLOVER_TS,'yyyy-mm-dd hh24:mi:ss')); 8 dbms_output.put_line('TARGET_COMPAT=' || TARGET_COMPAT); 9 if(IS_ENABLED)then 10 dbms_output.put_line('IS_ENABLED IS TURE'); 11 else 12 dbms_output.put_line('IS_ENABLED IS FALSE'); 13 end if; 14 end; 15 / EFFECTIVE_AUTO_ROLLOVER_TS=2019-06-23 00:00:00 TARGET_COMPAT=3 IS_ENABLED IS FALSE PL/SQL procedure successfully completed. SQL>
4. scn compatibility手工调整
SQL> Alter Database Set SCN Compatibility 2; Database altered. SQL> Alter Database Set SCN Compatibility 3; Database altered. SQL> Alter Database Set SCN Compatibility 1; Alter Database Set SCN Compatibility 1 * ERROR at line 1: ORA-01126: database must be mounted in this instance and not open in any instance SQL> shutdown immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL> startup mount; ORACLE instance started. Total System Global Area 4999609080 bytes Fixed Size 9145080 bytes Variable Size 1040187392 bytes Database Buffers 3942645760 bytes Redo Buffers 7630848 bytes Database mounted. SQL> Alter Database Set SCN Compatibility 1; Database altered. SQL> alter database open; Database altered. SQL> set serveroutput on ; SQL> declare 2 rsl number; 3 headroom_in_scn number; 4 headroom_in_sec number; 5 cur_scn_compat number; max_scn_compat number; 6 7 begin 8 dbms_scn.GetCurrentSCNParams(rsl,headroom_in_scn,headroom_in_sec,cur_scn_compat,max_scn_compat); 9 dbms_output.put_line('rsl=' || rsl); dbms_output.put_line('headroom_in_scn=' || headroom_in_scn); 10 11 dbms_output.put_line('headroom_in_sec=' || headroom_in_sec); 12 dbms_output.put_line('cur_scn_compat=' || cur_scn_compat); 13 dbms_output.put_line('max_scn_compat=' || max_scn_compat); end; / 14 15 rsl=16425127591936 headroom_in_scn=16425125502261 headroom_in_sec=1002510101 cur_scn_compat=1 max_scn_compat=3 PL/SQL procedure successfully completed.
参考文档:
Recommended patching and actions for Oracle database versions 12.1.0.1, 11.2.0.3 and earlier-before June 2019(Doc ID 2335265.1)
Recommended patches and actions for Oracle databases versions 12.1.0.1, 11.2.0.3 and earlier–before June 2019(Doc ID 2361478.1)