做网站图片怎么找/网络软文营销案例

该楼层疑似违规已被系统折叠 隐藏此楼查看此楼

dbv检查system文件报坏块

对应具体地址为:file 1 block 39041和66738

判断控制文件异常

通过数据库恢复检查脚本(Oracle Database Recovery Check)脚本检测数据库发现控制文件明显异常(checkpoint scn)

尝试恢复数据库

因此对该库进行了不完全恢复,然后尝试resetlogs打开数据库,数据库报ORA-600 2662错误

Fri Aug 29 02:35:08 2014alter database open resetlogsFri Aug 29 02:35:11 2014RESETLOGS after complete recovery through change 451371288Resetting resetlogs activation ID 1232269761 (0x4972f1c1)Fri Aug 29 02:35:15 2014Setting recovery target incarnation to 3Fri Aug 29 02:35:15 2014Assigning activation ID 1384652231 (0x52881dc7)LGWR: STARTING ARCH PROCESSESARC0 started with pid=17, OS id=1084Fri Aug 29 02:35:15 2014ARC0: Archival startedARC1: Archival startedLGWR: STARTING ARCH PROCESSES COMPLETEARC1 started with pid=18, OS id=2836Fri Aug 29 02:35:15 2014Thread 1 opened at log sequence 1 Current log# 1 seq# 1 mem# 0: Z:\ORACLE\PRODUCT\10.2.0\ORCL\REDO01.LOGSuccessful open of redo thread 1Fri Aug 29 02:35:15 2014MTTR advisory is disabled because FAST_START_MTTR_TARGET is not setFri Aug 29 02:35:15 2014ARC1: Becoming the *no FAL* ARCHARC1: Becoming the *no SRL* ARCHFri Aug 29 02:35:15 2014ARC0: Becoming the heartbeat ARCHFri Aug 29 02:35:15 2014SMON: enabling cache recoveryFri Aug 29 02:35:16 2014Errors in file d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4824.trc:ORA-00600: 内部错误代码, 参数: [2662], [0], [451371311], [0], [451374534], [8388977], [], [] Fri Aug 29 02:35:16 2014Errors in file d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4824.trc:ORA-00600: 内部错误代码, 参数: [2662], [0], [451371311], [0], [451374534], [8388977], [], [] Fri Aug 29 02:35:16 2014Error 600 happened during db open, shutting down databaseUSER: terminating instance due to error 600Fri Aug 29 02:35:17 2014Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_2928.trc:ORA-00600: ??????, ??: [], [], [], [], [], [], [], [] Instance terminated by USER, pid = 4824ORA-1092 signalled during: alter database open resetlogs...

ORA-600 2662 该错误解决思路很明显,推进scn,数据库报ORA-01578

Fri Aug 29 02:42:47 2014SMON: enabling cache recoveryFri Aug 29 02:42:47 2014Successfully onlined Undo Tablespace 1.Dictionary check beginningDictionary check completeFri Aug 29 02:42:49 2014SMON: enabling tx recoveryFri Aug 29 02:42:49 2014Database Characterset is ZHS16GBKOpening with internal Resource Manager planwhere NUMA PG = 1, CPUs = 16replication_dependency_tracking turned off (no async multimaster replication found)Fri Aug 29 02:42:50 2014Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_4804.trc:ORA-00604: 递归 SQL 级别 1 出现错误ORA-01578: ORACLE 数据块损坏 (文件号 1, 块号 39041)ORA-01110: 数据文件 1: *Z:\ORACLE\PRODUCT\10.2.0\ORCL\SYSTEM01.DBF* Fri Aug 29 02:42:50 2014LOGSTDBY: Validating controlfile with logical metadataFri Aug 29 02:42:51 2014LOGSTDBY: Validation completeORA-604 signalled during: alter database open...

使用event跳过坏块，启动数据库成功

Fri Aug 29 02:48:59 2014SMON: enabling cache recoveryFri Aug 29 02:49:00 2014Successfully onlined Undo Tablespace 1.Fri Aug 29 02:49:00 2014SMON: enabling tx recoveryFri Aug 29 02:49:00 2014Database Characterset is ZHS16GBKOpening with internal Resource Manager planwhere NUMA PG = 1, CPUs = 16replication_dependency_tracking turned off (no async multimaster replication found)Starting background process QMNCQMNC started with pid=34, OS id=3096Fri Aug 29 02:49:01 2014db_recovery_file_dest_size of 4096 MB is 0.00% used. This is auser-specified limit on the amount of space that will be used by thisdatabase for recovery-related files, and does not reflect the amount ofspace available in the underlying filesystem or ASM diskgroup.Fri Aug 29 02:49:01 2014Completed: alter database open

查询坏块对象

因为这些对象均不是核心对象,直接进行truncate然后插入老数据

后续还有大量错误修复

ORA-12012: error on auto execute of job 1ORA-08102: index key not found, obj# 239, file 1, block 1674 (2) ORA-00600: 内部错误代码, 参数: [kcbz_check_objd_typ], [0], [0], [1], [], [], [], [] ORA-00600: internal error code, arguments: [6749], [3], [12606796], [173], [], [], [], [] ORA-00600: 内部错误代码, 参数: [13013], [52898], [52895], [38288618], [44], [38288618], [17], [] ORA-00600: 内部错误代码, 参数: [13013], [5001], [52895], [38286476], [5], [38286476], [17], []

再次说明,很多时候数据库恢复不要看成多神秘,就是几个参数搞定,更加不要神化有坏块就bbed修复,当然非常极端,使用N中工具,N种尝试的也存在.做好备份重于一切