标签云
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,598)
- 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 (18)
- PostgreSQL恢复 (6)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (36)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (19)
-
最近发表
- PostgreSQL解析wal日志之—walminer
- 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
Oracle 19c/21c最新patch信息-202404
|
19.0.0.0 | |||
Description | Database Update | GI Update | Windows Bundle Patch |
APR2024 (19.23.0.0.0) | 36233263 | 36233126 | 36219938 |
JAN2024 (19.22.0.0.0) | 35943157 | 35940989 | 35962832 |
OCT2023 (19.21.0.0.0) | 35643107 | 35642822 | 35681552 |
JUL2023 (19.20.0.0.0) | 35320081 | 35319490 | 35348034 |
APR2023 (19.19.0.0.0) | 35042068 | 35037840 | 35046439 |
JAN2023 (19.18.0.0.0) | 34765931 | 34762026 | 34750795 |
Oct2022 (19.17.0.0.0) | 34419443 | 34416665 | 34468114 |
JUL2022 (19.16.0.0.0) | 34133642 | 34130714 | 34110685 |
APR2022 (19.15.0.0.0) | 33806152 | 33803476 | 33829175 |
JAN2022 (19.14.0.0.0) | 33515361 | 33509923 | 33575656 |
OCT2021(19.13.0.0.0) | 33192793 | 33182768 | 33155330 |
JUL2021 (19.12.0.0.0) | 32904851 | 32895426 | 32832237 |
APR2021 (19.11.0.0.0) | 32545013 | 32545008 | 32409154 |
JAN2021 (19.10.0.0.0) | 32218454 | 32226239 | 32062765 |
OCT2020 (19.9.0.0.0) | 31771877 | 31750108 | 31719903 |
JUL2020 (19.8.0.0.0) | 31281355 | 31305339 | 31247621 |
APR2020 (19.7.0.0.0) | 30869156 | 30899722 | 30901317 |
JAN2020 (19.6.0.0.0) | 30557433 | 30501910 | 30445947 |
OCT2019 (19.5.0.0.0) | 30125133 | 30116789 | 30151705 |
JUL2019 (19.4.0.0.0) | 29834717 | 29708769 | NA |
APR2019 (19.3.0.0.0) | 29517242 | 29517302 | NA |
19.0.0.0 | |||
Description | OJVM Update | OJVM + DB Update | OJVM + GI Update |
APR2024 (19.23.0.0.240416) | 36199232 | 36209492 | 36209493 |
JAN2024 (19.22.0.0.240116) | 35926646 | 36031426 | 36031453 |
OCT2023 (19.21.0.0.231017) | 35648110 | 35742413 | 35742441 |
JUL2023 (19.20.0.0.230718) | 35354406 | 35370174 | 35370167 |
APR2023 (19.19.0.0.230418) | 35050341 | 35058163 | 35058172 |
JAN2023 (19.18.0.0.230117) | 34786990 | 34773489 | 34773504 |
OCT2022 (19.17.0.0.221018) | 34411846 | 34449114 | 34449117 |
JUL2022 (19.16.0.0.220719) | 34086870 | 34160831 | 34160854 |
APR2022 (19.15.0.0.220419) | 33808367 | 33859194 | 33859214 |
JAN2022 (19.14.0.0.220118) | 33561310 | 33567270 | 33567274 |
OCT2021 (19.13.0.0.211019) | 33192694 | 33248420 | 33248471 |
JUL2021 (19.12.0.0.210720) | 32876380 | 32900021 | 32900083 |
APR2021 (19.11.0.0.210420) | 32399816 | 32578972 | 32578973 |
JAN2021 (19.10.0.0.210119) | 32067171 | 32126828 | 32126842 |
OCT2020 (19.9.0.0.201020) | 31668882 | 31720396 | 31720429 |
JUL2020 (19.8.0.0.200714) | 31219897 | 31326362 | 31326369 |
APR2020 (19.7.0.0.200414) | 30805684 | 30783543 | 30783556 |
JAN2020 (19.6.0.0.200114) | 30484981 | 30463595 | 30463609 |
OCT2019 (19.5.0.0.191015) | 30128191 | 30133124 | 30133178 |
JUL2019 (19.4.0.0.190716) | 29774421 | 29699079 | 29699097 |
APR2019 (19.3.0.0.190416) | 29548437 | 29621253 | 29621299 |
参考:Assistant: Download Reference for Oracle Database/GI Update, Revision, PSU, SPU(CPU), Bundle Patches, Patchsets and Base Releases (Doc ID 2118136.2)
ORA-00742 ORA-00312 恢复
有客户反馈,断电之后数据库启动报ORA-00742和ORA-00312,无法正常open
我们远程上去尝试open库结果也报同样错误
[oracle@oldhis oradata]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Wed Apr 10 09:40:03 2024 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> recover database; Media recovery complete. SQL> alter database open; alter database open * ERROR at line 1: ORA-00742: Log read detects lost write in thread %d sequence %d block %d ORA-00312: online log 3 thread 1: '/oradata/shrdh/redo03.log' SQL> select group#,status from v$log; GROUP# STATUS ---------- ---------------- 1 INACTIVE 3 CURRENT 2 INACTIVE
因为recover已经成功,但是依旧报ORA-742错误,尝试查询scn相关信息
SQL> set pages 10000 set numw 16 SELECT status, checkpoint_change#, checkpoint_time,last_change#, count(*) ROW_NUM FROM v$datafile GROUP BY status, checkpoint_change#, checkpoint_time,last_change# ORDER BY status, checkpoint_change#, checkpoint_time; set numw 16 col CHECKPOINT_TIME for a40 set lines 150 set pages 1000 SELECT status, to_char(checkpoint_time,'yyyy-mm-dd hh24:mi:ss') checkpoint_time,FUZZY,checkpoint_change#, count(*) ROW_NUM FROM v$datafile_header GROUP BY status, checkpoint_change#, to_char(checkpoint_time,'yyyy-mm-dd hh24:mi:ss'),fuzzy ORDER BY status, checkpoint_change#, checkpoint_time; SQL> SQL> 2 3 4 5 6 7 STATUS CHECKPOINT_CHANGE# CHECKPOIN LAST_CHANGE# ROW_NUM ------- ------------------ --------- ---------------- ---------------- ONLINE 1279351848 26-MAR-24 1279351848 19 SYSTEM 1279351848 26-MAR-24 1279351848 1 SQL> SQL> SQL> SQL> SQL> SQL> SQL> 2 3 4 5 6 STATUS CHECKPOINT_TIME FUZ CHECKPOINT_CHANGE# ROW_NUM ------- ---------------------------------------- --- ------------------ ---------------- ONLINE 2024-03-26 00:05:45 NO 1279351848 20
基于这样的情况,我们判断数据库直接open成功
SQL> recover database using backup controlfile; ORA-00279: change 1279351848 generated at 03/26/2024 00:05:45 needed for thread 1 ORA-00289: suggestion : /oradata/arch/shrdh/shrdh_1_12984_974767526.arc ORA-00280: change 1279351848 for thread 1 is in sequence #12984 Specify log: {<RET>=suggested | filename | AUTO | CANCEL} /oradata/shrdh/redo03.log Log applied. Media recovery complete. SQL> alter database open resetlogs; Database altered.
后面比较不幸,数据库报ORA-600 4194错误导致数据库异常
Wed Apr 10 09:43:08 2024 ALTER DATABASE RECOVER database using backup controlfile Media Recovery Start started logmerger process Parallel Media Recovery started with 4 slaves ORA-279 signalled during: ALTER DATABASE RECOVER database using backup controlfile ... Wed Apr 10 09:43:24 2024 ALTER DATABASE RECOVER LOGFILE '/oradata/shrdh/redo03.log' Media Recovery Log /oradata/shrdh/redo03.log Media Recovery Complete (shrdh) Completed: ALTER DATABASE RECOVER LOGFILE '/oradata/shrdh/redo03.log' alter database open resetlogs RESETLOGS after complete recovery through change 1279351849 Clearing online redo logfile 1 /oradata/shrdh/redo01.log Clearing online log 1 of thread 1 sequence number 12982 Clearing online redo logfile 1 complete Clearing online redo logfile 2 /oradata/shrdh/redo02.log Clearing online log 2 of thread 1 sequence number 12983 Clearing online redo logfile 2 complete Clearing online redo logfile 3 /oradata/shrdh/redo03.log Clearing online log 3 of thread 1 sequence number 12984 Clearing online redo logfile 3 complete Resetting resetlogs activation ID 1820377766 (0x6c80c2a6) Online log /oradata/shrdh/redo01.log: Thread 1 Group 1 was previously cleared Online log /oradata/shrdh/redo02.log: Thread 1 Group 2 was previously cleared Online log /oradata/shrdh/redo03.log: Thread 1 Group 3 was previously cleared Wed Apr 10 09:43:34 2024 Setting recovery target incarnation to 2 Wed Apr 10 09:43:34 2024 Assigning activation ID 2011515185 (0x77e54931) Thread 1 opened at log sequence 1 Current log# 1 seq# 1 mem# 0: /oradata/shrdh/redo01.log Successful open of redo thread 1 Wed Apr 10 09:43:34 2024 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Wed Apr 10 09:43:34 2024 SMON: enabling cache recovery [25089] Successfully onlined Undo Tablespace 2. Undo initialization finished serial:0 start:1273646224 end:1273646494 diff:270 (2 seconds) Dictionary check beginning Dictionary check complete Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed SMON: enabling tx recovery Database Characterset is ZHS16GBK No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Errors in file /u01/app/oracle/diag/rdbms/shrdh/shrdh/trace/shrdh_smon_21704.trc (incident=84296): ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] Incident details in: /u01/app/oracle/diag/rdbms/shrdh/shrdh/incident/incdir_84296/shrdh_smon_21704_i84296.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Starting background process QMNC Wed Apr 10 09:43:35 2024 QMNC started with pid=24, OS id=25340 LOGSTDBY: Validating controlfile with logical metadata LOGSTDBY: Validation complete Block recovery from logseq 1, block 61 to scn 1279351933 Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0 Mem# 0: /oradata/shrdh/redo01.log Block recovery stopped at EOT rba 1.99.16 Block recovery completed at rba 1.99.16, scn 0.1279351933 Block recovery from logseq 1, block 61 to scn 1279351919 Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0 Mem# 0: /oradata/shrdh/redo01.log Block recovery completed at rba 1.87.16, scn 0.1279351922 Errors in file /u01/app/oracle/diag/rdbms/shrdh/shrdh/trace/shrdh_smon_21704.trc: ORA-01595: error freeing extent (2) of rollback segment (7)) ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] Completed: alter database open resetlogs Wed Apr 10 09:43:37 2024 Errors in file /u01/app/oracle/diag/rdbms/shrdh/shrdh/trace/shrdh_m000_25343.trc (incident=84392): ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] Incident details in: /u01/app/oracle/diag/rdbms/shrdh/shrdh/incident/incdir_84392/shrdh_m000_25343_i84392.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Wed Apr 10 09:43:37 2024 Starting background process CJQ0 Wed Apr 10 09:43:37 2024 CJQ0 started with pid=29, OS id=25357 Starting background process SMCO Wed Apr 10 09:43:37 2024 SMCO started with pid=30, OS id=25360 Wed Apr 10 09:43:38 2024 Flush retried for xcb 0x115b42d28, pmd 0x1148dea70 Block recovery from logseq 1, block 61 to scn 1279351933 Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0 Mem# 0: /oradata/shrdh/redo01.log Block recovery completed at rba 1.99.16, scn 0.1279351934 Errors in file /u01/app/oracle/diag/rdbms/shrdh/shrdh/trace/shrdh_pmon_21679.trc (incident=84208): ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] Incident details in: /u01/app/oracle/diag/rdbms/shrdh/shrdh/incident/incdir_84208/shrdh_pmon_21679_i84208.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Errors in file /u01/app/oracle/diag/rdbms/shrdh/shrdh/trace/shrdh_pmon_21679.trc: ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] PMON (ospid: 21679): terminating the instance due to error 472 Wed Apr 10 09:43:47 2024 Instance terminated by PMON, pid = 21679
报错比较明显,对undo进行处理即可.
数据库open成功后报ORA-00353 ORA-00354错误引起的一系列问题(本质ntfs文件系统异常)
服务器异常断电之后,开机启动数据库启动成功,但是报ORA-00353 ORA-00354以及ORA-600 kdsgrp1错误
Sun Mar 31 01:19:51 2024 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Sun Mar 31 01:19:51 2024 SMON: enabling cache recovery [4528] Successfully onlined Undo Tablespace 2. Undo initialization finished serial:0 start:64250 end:64859 diff:609 (6 seconds) Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed SMON: enabling tx recovery Database Characterset is ZHS16GBK No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Sun Mar 31 01:19:57 2024 QMNC started with pid=40, OS id=4912 Sun Mar 31 01:20:03 2024 Completed: alter database open Sun Mar 31 01:20:04 2024 Starting background process CJQ0 Sun Mar 31 01:20:04 2024 CJQ0 started with pid=20, OS id=5104 Setting Resource Manager plan SCHEDULER[0x32DE]:DEFAULT_MAINTENANCE_PLAN via scheduler window Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter Sun Mar 31 01:20:07 2024 Starting background process VKRM Sun Mar 31 01:20:07 2024 VKRM started with pid=48, OS id=4160 Sun Mar 31 01:20:32 2024 Incomplete read from log member 'E:\APP\ARCHIVELOG\ARC0000005281_1157968160.0001'. Trying next member. Incomplete read from log member 'E:\APP\ARCHIVELOG\ARC0000005281_1157968160.0001'. Trying next member. Errors in file E:\APP\ADMINISTRATOR\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_j000_4180.trc(incident=132393): ORA-00353: 日志损坏接近块 13792 更改 33686946 时间 03/31/2024 00:17:54 ORA-00334: 归档日志: 'E:\APP\ARCHIVELOG\ARC0000005281_1157968160.0001' Incomplete read from log member 'E:\APP\ARCHIVELOG\ARC0000005281_1157968160.0001'. Trying next member. Incomplete read from log member 'E:\APP\ARCHIVELOG\ARC0000005281_1157968160.0001'. Trying next member. Errors in file E:\APP\ADMINISTRATOR\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_j000_4180.trc(incident=132394): ORA-00353: 日志损坏接近块 13792 更改 33686946 时间 03/31/2024 00:17:54 ORA-00334: 归档日志: 'E:\APP\ARCHIVELOG\ARC0000005281_1157968160.0001' ORA-00353: 日志损坏接近块 13792 更改 33686946 时间 03/31/2024 00:17:54 ORA-00334: 归档日志: 'E:\APP\ARCHIVELOG\ARC0000005281_1157968160.0001' Errors in file E:\APP\ADMINISTRATOR\diag\rdbms\xifenfei\xifenfei\incident\incdir_132393\xifenfei_j000_4180_i132393.trc: ORA-00354: 损坏重做日志块标头 ORA-00353: 日志损坏接近块 13792 更改 33686946 时间 03/31/2024 00:17:54 ORA-00334: 归档日志: 'E:\APP\ARCHIVELOG\ARC0000005281_1157968160.0001' ORA-00353: 日志损坏接近块 13792 更改 33686946 时间 03/31/2024 00:17:54 ORA-00334: 归档日志: 'E:\APP\ARCHIVELOG\ARC0000005281_1157968160.0001' Sun Mar 31 01:20:35 2024 Sweep [inc][132394]: completed Errors in file E:\APP\ADMINISTRATOR\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_j000_4180.trc: ORA-00354: 损坏重做日志块标头 ORA-00353: 日志损坏接近块 13792 更改 33686946 时间 03/31/2024 00:17:54 ORA-00334: 归档日志: 'E:\APP\ARCHIVELOG\ARC0000005281_1157968160.0001' Errors in file E:\APP\ADMINISTRATOR\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_j000_4180.trc(incident=132395): ORA-00600: 内部错误代码, 参数: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], [] Incomplete read from log member 'E:\APP\ARCHIVELOG\ARC0000005281_1157968160.0001'. Trying next member. Incomplete read from log member 'E:\APP\ARCHIVELOG\ARC0000005281_1157968160.0001'. Trying next member. Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details.
再次重启数据库报ORA-600 2131错误,数据库无法正常mount
Sun Mar 31 08:59:20 2024 alter database mount exclusive Errors in file E:\APP\ADMINISTRATOR\diag\rdbms\xifenfei\xifenfei\trace\xifenfei_ora_3232.trc (incident=144175): ORA-00600: ??????, ??: [2131], [9], [8], [], [], [], [], [], [], [], [], [] Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. ORA-600 signalled during: alter database mount exclusive...
因为这个库有ctl备份,通过rman还原ctl备份,然后尝试recover库,结果报ORA-00310 ORA-00334(由于需要的redo无法正常应用导致)
对于这类情况,只能通过屏蔽一致性强制打开库
数据报ORA-600 2662错误,此类错误比较简单,使用patch scn工具一键搞定(ORA-600 2662快速恢复之Patch scn工具),数据库open成功,导出数据完整恢复
对于正常open的库,出现此类问题属于反常现象,通过分析系统事件确定是由于ntfs文件系统本身有问题导致