标签云
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
标签归档:ORA-00353 ORA-00312
commit_wait和commit_logging设置不当导致数据库无法正常启动
客户数据库设置以下参数,突然掉电之后,数据库无法正常启动
commit_wait = "NOWAIT" commit_logging = "BATCH"
数据库open报错
alter database open Block change tracking file is current. Beginning crash recovery of 1 threads parallel recovery started with 31 processes Started redo scan Errors in file /media/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_28711.trc (incident=8002955): ORA-00353: log corruption near block 3 change 17372812227460 time 03/20/2022 00:11:51 ORA-00312: online log 12315 thread 1: '/media/oracle/redolog/redo05.log' Aborting crash recovery due to error 399 Errors in file /media/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_28711.trc: ORA-00399: corrupt change description in redo log ORA-00353: log corruption near block 3 change 17372812227460 time 03/20/2022 00:11:51 ORA-00312: online log 12315 thread 1: '/media/oracle/redolog/redo05.log' Errors in file /media/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_28711.trc: ORA-00399: corrupt change description in redo log ORA-00353: log corruption near block 3 change 17372812227460 time 03/20/2022 00:11:51 ORA-00312: online log 12315 thread 1: '/media/oracle/redolog/redo05.log' ORA-399 signalled during: alter database open...
报错信息比较明显是由于redo损坏导致,尝试强制open库
Sun Mar 20 18:32:35 2022 alter database open resetlogs RESETLOGS is being done without consistancy checks. This may result in a corrupted database. The database should be recreated. RESETLOGS after incomplete recovery UNTIL CHANGE 17372812227456 Resetting resetlogs activation ID 1627598093 (0x61032d0d) Sun Mar 20 18:34:08 2022 Setting recovery target incarnation to 2 Sun Mar 20 18:34:08 2022 Initializing SCN for created control file Database SCN compatibility initialized to 3 Warning - High Database SCN: Current SCN value is 17372812227459, threshold SCN value is 0 If you have not previously reported this warning on this database, please notify Oracle Support so that additional diagnosis can be performed. Sun Mar 20 18:34:08 2022 Assigning activation ID 1627615603 (0x61037173) Thread 1 opened at log sequence 1 Current log# 2 seq# 1 mem# 0: /media/oracle/redolog/redo02.log Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Sun Mar 20 18:34:08 2022 SMON: enabling cache recovery Errors in file /media/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_14369.trc (incident=8003142): ORA-00600: internal error code, arguments: [2662], [4044], [3964482439], [4044], [3964488833], [12669344], Incident details in: /media/oracle/diag/rdbms/orcl/orcl/incident/incdir_8003142/orcl_ora_14369_i8003142.trc Errors in file /media/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_14369.trc (incident=8003143): ORA-00353: log corruption near block 3 change 17372812227462 time 03/20/2022 18:34:10 ORA-00312: online log 2 thread 1: '/media/oracle/redolog/redo02.log' ORA-00600: internal error code, arguments: [2662], [4044], [3964482439], [4044], [3964488833], [12669344], Incident details in: /media/oracle/diag/rdbms/orcl/orcl/incident/incdir_8003143/orcl_ora_14369_i8003143.trc Errors in file /media/oracle/diag/rdbms/orcl/orcl/incident/incdir_8003142/orcl_ora_14369_i8003142.trc: ORA-00399: corrupt change description in redo log ORA-00353: log corruption near block 3 change 17372812227462 time 03/20/2022 18:34:10 ORA-00312: online log 2 thread 1: '/media/oracle/redolog/redo02.log' ORA-00600: internal error code, arguments: [2662], [4044], [3964482439], [4044], [3964488833], [12669344], Errors in file /media/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_14369.trc (incident=8003144): ORA-00353: log corruption near block 3 change 17372812227462 time 03/20/2022 18:34:10 ORA-00334: archived log: '/media/oracle/redolog/redo02.log' ORA-00600: internal error code, arguments: [2662], [4044], [3964482439], [4044], [3964488833], [12669344], Incident details in: /media/oracle/diag/rdbms/orcl/orcl/incident/incdir_8003144/orcl_ora_14369_i8003144.trc Sun Mar 20 18:34:11 2022 ORA-00603: ORACLE server session terminated by fatal error ORA-00600: internal error code, arguments: [2662], [4044], [3964482444], [4044], [3964488833], [12669344], ORA-00600: internal error code, arguments: [2662], [4044], [3964482443], [4044], [3964488833], [12669344], ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00600: internal error code, arguments: [2662], [4044], [3964482439], [4044], [3964488833], [12669344],
强制open数据库报ora-600 2662错误,比较常见,通过修改scn再尝试open库
Sun Mar 20 18:38:43 2022 alter database open resetlogs RESETLOGS is being done without consistancy checks. This may result in a corrupted database. The database should be recreated. RESETLOGS after incomplete recovery UNTIL CHANGE 17372812227460 Resetting resetlogs activation ID 1627615603 (0x61037173) Sun Mar 20 18:40:02 2022 Setting recovery target incarnation to 2 Sun Mar 20 18:40:02 2022 Initializing SCN for created control file Database SCN compatibility initialized to 3 Warning - High Database SCN: Current SCN value is 17372812227463, threshold SCN value is 0 If you have not previously reported this warning on this database, please notify Oracle Support so that additional diagnosis can be performed. Sun Mar 20 18:40:02 2022 Assigning activation ID 1627669665 (0x610444a1) Thread 1 opened at log sequence 1 Current log# 2 seq# 1 mem# 0: /media/oracle/redolog/redo02.log Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Sun Mar 20 18:40:02 2022 SMON: enabling cache recovery Undo initialization finished serial:0 start:779809538 end:779809788 diff:250 (2 seconds) Dictionary check beginning Tablespace 'TEMP' #3 found in data dictionary, but not in the controlfile. Adding to controlfile. Dictionary check complete Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed SMON: enabling tx recovery ********************************************************************* WARNING: The following temporary tablespaces contain no files. This condition can occur when a backup controlfile has been restored. It may be necessary to add files to these tablespaces. That can be done using the SQL statement: ALTER TABLESPACE <tablespace_name> ADD TEMPFILE Alternatively, if these temporary tablespaces are no longer needed, then they can be dropped. Empty temporary tablespace: TEMP ********************************************************************* Database Characterset is AL32UTF8 No Resource Manager plan active ********************************************************** WARNING: Files may exists in db_recovery_file_dest that are not known to the database. Use the RMAN command CATALOG RECOVERY AREA to re-catalog any such files. If files cannot be cataloged, then manually delete them using OS command. One of the following events caused this: 1. A backup controlfile was restored. 2. A standby controlfile was restored. 3. The controlfile was re-created. 4. db_recovery_file_dest had previously been enabled and then disabled. ********************************************************** replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Sun Mar 20 18:40:04 2022 QMNC started with pid=55, OS id=16232 LOGSTDBY: Validating controlfile with logical metadata LOGSTDBY: Validation complete Sun Mar 20 18:40:05 2022 db_recovery_file_dest_size of 3882 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. Sun Mar 20 18:40:05 2022 Starting background process CJQ0 Sun Mar 20 18:40:05 2022 CJQ0 started with pid=58, OS id=16251 Completed: alter database open resetlogs
后续增加temp,导出数据到新库,恢复完成
正常open库报ORA-600 2662,ORA-600 4097错误
又一起数据库正常open之后继续报ORA-600 2662
Sat Dec 29 04:30:40 2018 QMNC started with pid=36, OS id=12985 LOGSTDBY: Validating controlfile with logical metadata LOGSTDBY: Validation complete Completed: alter database open Sat Dec 29 04:30:42 2018 Starting background process CJQ0 Sat Dec 29 04:30:42 2018 CJQ0 started with pid=41, OS id=12999 Sat Dec 29 04:30:43 2018 Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_m000_12989.trc (incident=365101): ORA-00600: internal error code, arguments: [2662], [0], [193646286], [0], [193662077], [50331650], [], [], [], [], [], [] Sat Dec 29 04:30:43 2018 Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_m002_12993.trc (incident=365117): ORA-00600: internal error code, arguments: [2662], [0], [193646286], [0], [193662077], [50331650], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_365101/orcl_m000_12989_i365101.trc Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_365117/orcl_m002_12993_i365117.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 /home/app/diag/rdbms/orcl/orcl/trace/orcl_m000_12989.trc (incident=365102): ORA-00600: internal error code, arguments: [2662], [0], [193646286], [0], [193662077], [50331650], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_365102/orcl_m000_12989_i365102.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 /home/app/diag/rdbms/orcl/orcl/trace/orcl_m002_12993.trc (incident=365118): ORA-00600: internal error code, arguments: [2662], [0], [193646286], [0], [193662077], [50331650], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_365118/orcl_m002_12993_i365118.trc
在open状态处理掉ORA-00600 2662错误之后,又出现了ORA-600 4097 以及ORA-00353 ORA-00312错误,这个也是一种不常见的现象,一般都是数据库open之前出现类似错误,但是这里在open之后出现(以前类似处理参考:ORA-600 4097故障处理和ORA-00322 ORA-00312 ,ORA-00354 ORA-00353 ORA-00312异常处理)
Sat Dec 29 05:55:22 2018 Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_j000_19136.trc (incident=432567): ORA-00600: internal error code, arguments: [4097], [3], [15], [76480], [], [], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_432567/orcl_j000_19136_i432567.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 /home/app/diag/rdbms/orcl/orcl/trace/orcl_j000_19136.trc (incident=432568): ORA-00353: log corruption near block 15682 change 193647101 time 12/29/2018 04:40:31 ORA-00312: online log 3 thread 1: '/home/app/oradata/orcl/redo03.log' ORA-00312: online log 3 thread 1: '/home/app/oradata/orcl/redo03.log' ORA-00600: internal error code, arguments: [4097], [3], [15], [76480], [], [], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_432568/orcl_j000_19136_i432568.trc Errors in file /home/app/diag/rdbms/orcl/orcl/incident/incdir_432567/orcl_j000_19136_i432567.trc: ORA-00399: corrupt change description in redo log ORA-00353: log corruption near block 15682 change 193647101 time 12/29/2018 04:40:31 ORA-00312: online log 3 thread 1: '/home/app/oradata/orcl/redo03.log' ORA-00312: online log 3 thread 1: '/home/app/oradata/orcl/redo03.log' ORA-00600: internal error code, arguments: [4097], [3], [15], [76480], [], [], [], [], [], [], [], [] Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_j000_19136.trc (incident=432569): ORA-00353: log corruption near block 15682 change 193647101 time 12/29/2018 04:40:31 ORA-00334: archived log: '/home/app/oradata/orcl/redo03.log' ORA-00312: online log 3 thread 1: '/home/app/oradata/orcl/redo03.log' ORA-00600: internal error code, arguments: [4097], [3], [15], [76480], [], [], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_432569/orcl_j000_19136_i432569.trc
处理完成上面报错之后,继续出现比较少见的ORA-600 ktecgsc:kcbz_objdchk错误,具体参考:ORA-00600 [ktecgsc:kcbz_objdchk] on 11.2 (Doc ID 1562473.1)
Sat Dec 29 06:00:17 2018 DBMS_STATS: GATHER_STATS_JOB encountered errors. Check the trace file. Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_j001_19436.trc: ORA-20011: Approximate NDV failed: ORA-08103: object no longer exists Sat Dec 29 06:00:21 2018 Errors in file /home/app/diag/rdbms/orcl/orcl/trace/orcl_j002_19479.trc (incident=432631): ORA-00600: internal error code, arguments: [ktecgsc:kcbz_objdchk], [0], [0], [1], [], [], [], [], [], [], [], [] Incident details in: /home/app/diag/rdbms/orcl/orcl/incident/incdir_432631/orcl_j002_19479_i432631.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details.