标签云
asm恢复 bbed bootstrap$ dul kcbzib_kcrsds_1 kccpb_sanity_check_2 kcratr_nab_less_than_odr MySQL恢复 obet ORA-00312 ORA-00704 ORA-00742 ORA-01110 ORA-01200 ORA-01555 ORA-01578 ORA-01595 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-600 kcratr_nab_less_than_odr 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 比特币加密文章分类
- MongoDB (1)
- MongoDB恢复 (1)
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (112)
- 数据库 (1,882)
- DB2 (22)
- MySQL (82)
- Oracle (1,707)
- Data Guard (53)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (168)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (72)
- Oracle Bug (8)
- Oracle RAC (56)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (661)
- Oracle安装升级 (108)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (91)
- PostgreSQL (37)
- pdu工具 (7)
- PostgreSQL恢复 (13)
- SQL Server (34)
- SQL Server恢复 (14)
- TimesTen (7)
- 达梦数据库 (5)
- 达梦恢复 (3)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (51)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (34)
- MongoDB (1)
-
最近发表
- 断电引起ORA-600 3005故障处理
- 记录一次云存储资源到期之后引起的数据库恢复
- Firebird 损坏数据库数据抢救工具—firebirdext
- Oracle 19c 202610补丁(RUs+OJVM)-19.33
- 由于con$.con#值达到极限,触发数据库增加约束报ORA-600 12807错误
- MongoDB 离线提取工具—mongoext
- .bres勒索病毒加密数据库dmp文件可恢复
- ORA-600 krsm_mrp_rebuild_lf_list.lno_mismatch
- 记录一次0丢失的ORA-00354: 损坏重做日志块标头故障恢复
- 不当数据库恢复操作导致一个月数据丢失
- obet快速修复oracle 位图损坏块
- 不太常见的10.2.0.1的oracle redo损坏恢复
- obet forcecopy功能抢救硬件故障中的数据文件
- kcratr_nab_less_than_odr和system坏块故障处理
- 通过obet 恢复system坏块,打开数据库
- obet dbv功能完整说明
- 分享一例运行在aix上的sap系统数据库恢复过程
- OBET-Oracle Block Editor Tool使用说明
- 几乎动用了所有手段的Oracle故障恢复
- Oracle Block Edit Tool (obet) 功能增强–2026.07
月归档:七月 2012
客户端版本导致ORA-00600[kssadd_stage: null parent]
有客户一台应用不能正常工作,报ORA-00600[kssadd_stage: null parent]错误,重启中间件后工作正常.
alert日志
ORA-00600: internal error code, arguments: [kssadd_stage: null parent], [], [], [], [], [], [], [] Tue Jul 17 14:57:37 2012 Trace dumping is performing id=[cdmp_20120717145742] Tue Jul 17 14:57:39 2012 Errors in file /oracle/10g/admin/fdjdb/udump/fdjdb2_ora_307720.trc: ORA-00600: internal error code, arguments: [kssadd_stage: null parent], [], [], [], [], [], [], [] Tue Jul 17 14:57:45 2012 Errors in file /oracle/10g/admin/fdjdb/udump/fdjdb2_ora_357344.trc: ORA-00600: internal error code, arguments: [kssadd_stage: null parent], [], [], [], [], [], [], []
trace文件
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
ORACLE_HOME = /oracle/10g/db
System name: AIX
Node name: ora2
Release: 1
Version: 6
Machine: 00CCFD354C00
Instance name: fdjdb2
Redo thread mounted by this instance: 2
Oracle process number: 89
Unix process pid: 111068, image: oracle@ora2
*** ACTION NAME:() 2012-07-17 15:08:42.043
*** MODULE NAME:(gsrvr.exe) 2012-07-17 15:08:42.043
*** SERVICE NAME:(fdjdb) 2012-07-17 15:08:42.043
*** SESSION ID:(991.44140) 2012-07-17 15:08:42.043
*** 2012-07-17 15:08:42.043
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kssadd_stage: null parent], [], [], [], [], [], [], []
No current SQL statement being executed.
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst+001c bl ksedst1 40D1A9663F9E7ABB ?
6ED89E14D59386B5 ?
ksedmp+0290 bl ksedst 104A2CDB0 ?
ksfdmp+0018 bl 03F2735C
kgerinv+00dc bl _ptrgl
kgeasnmierr+004c bl kgerinv 11041D938 ? 700000220FFBFC8 ?
110000770 ? 7000004FDF0C700 ?
FFFFFFFFFFF89C0 ?
kssadd_stage+0080 bl kgeasnmierr 110195490 ? 110450040 ?
104AC46B8 ? 000000000 ?
000000000 ? 000000000 ?
000000000 ? 7000004F0FA9208 ?
kqreqa+0058 bl kssadd_stage 105670038 ? 104CF7BA0 ?
000000000 ? 000000000 ?
kqrpre1+0850 bl kqreqa 100203514 ? 1101A2B20 ?
kqrpre+001c bl kqrpre1 710000770 ? 000000009 ?
FFFFFFFFFFF9088 ?
28A4202200000000 ?
10012AEE4 ? FFFFFFFFFFF9080 ?
000000000 ? 11022A3E0 ?
opiosq0+009c bl kqrpre 000000000 ? 000000000 ?
000000000 ? 1101A2B20 ?
FFFFFFFFFFF9198 ? 1104B7C60 ?
FFFFFFFFFFF9458 ?
kpooprx+0168 bl opiosq0 4A00000001 ? 000000001 ?
000000000 ? A40000000000FF ?
kpoal8+0400 bl kpooprx FFFFFFFFFFFB964 ?
FFFFFFFFFFFB680 ?
5000000050 ? 100000001 ?
000000000 ? A40000000000A4 ?
000000000 ? 1103A1AD8 ?
opiodr+0ae0 bl _ptrgl
ttcpip+1020 bl _ptrgl
opitsk+1124 bl 01F971E8
opiino+0990 bl opitsk 000000000 ? 000000000 ?
opiodr+0ae0 bl _ptrgl
opidrv+0484 bl 01F96034
sou2o+0090 bl opidrv 3C02D9A29C ? 4A006E298 ?
FFFFFFFFFFFF8A0 ?
opimai_real+01bc bl 01F939B4
main+0098 bl opimai_real 000000000 ? 000000000 ?
__start+0070 bl main 000000000 ? 000000000 ?
--------------------- Binary Stack Dump ---------------------
咨询客户得知访问该数据库的是通过中间件(OCI)+10g Release 1 (10.1) for Windows访问数据库,然后查询MOS[ID 752149.1]发现stack trace
kssadd_stage <- kqreqa <- kqrpre1 <- kqrpre <- opiosq0 <- kpooprx <- kpoal8 <- opiodr <- ttcpip <- opitsk <- opiino <- opiodr <- opidrv <- sou2o <- opimai_real <- main <- start 和客户端版本和访问环境都和unpublished Bug 4937225相似
处理建议
客户端升级到10.2.0.3或者更高版本
8i升级到9i出现ORA-07445[pevm_MOVC_i()+18]
一个朋友数据库从8i升级到9i后,出现ORA-07445[pevm_MOVC_i()+18]错误
alert日志ORA-07445[pevm_MOVC_i()+18]
Mon Jul 16 12:21:54 2012 Errors in file /oracle/admin/ora8/udump/ora8_ora_8938.trc: ORA-07445: exception encountered: core dump [pevm_MOVC_i()+18] [SIGSEGV] [Address not mapped to object] [0x7] [] []
trace文件
--版本平台信息
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.4.0 - Production
ORACLE_HOME = /oracle/product/9.2.0
System name: Linux
Node name: localhost.localdomain
Release: 2.6.18-194.el5PAE
Version: #1 SMP Tue Mar 16 22:00:21 EDT 2010
Machine: i686
Instance name: ora8
Redo thread mounted by this instance: 1
Oracle process number: 15
Unix process pid: 8938, image: oracle@localhost.localdomain (TNS V1-V3)
--trace信息
*** 2012-07-16 12:21:54.399
*** SESSION ID:(12.6) 2012-07-16 12:21:54.399
Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x7, PC: [0x9bfac06, pevm_MOVC_i()+18]
Registers:
%eax: 0x00000000 %ebx: 0x00000025 %ecx: 0x00000000
%edx: 0xbf93bf50 %edi: 0x00000000 %esi: 0x002ff1d8
%esp: 0xbf93bc28 %ebp: 0xbf93bc60 %eip: 0x09bfac06
%efl: 0x00010296
pevm_MOVC_i()+6 (0x9bfabfa) mov %edi,0xffffffcc(%ebp)
pevm_MOVC_i()+9 (0x9bfabfd) mov %esi,0xffffffd0(%ebp)
pevm_MOVC_i()+12 (0x9bfac00) mov %ebx,0xffffffc8(%ebp)
pevm_MOVC_i()+15 (0x9bfac03) mov 0x14(%ebp),%eax
> pevm_MOVC_i()+18 (0x9bfac06) movb 0x7(%eax),%dl
pevm_MOVC_i()+21 (0x9bfac09) mov $0x0,0xfffffff0(%ebp)
pevm_MOVC_i()+28 (0x9bfac10) movb %dl,0xffffffe0(%ebp)
pevm_MOVC_i()+31 (0x9bfac13) movb %dl,0xffffffe0(%ebp)
pevm_MOVC_i()+34 (0x9bfac16) cmpb $0x1,%dl
*** 2012-07-16 12:21:54.407
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [pevm_MOVC_i()+18] [SIGSEGV] [Address not mapped to object] [0x7] [] []
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedmp()+269 call ksedst()+0 1 ? 0 ? 0 ? 1 ? 64252C31 ?
6666006C ?
ssexhd()+1108 call ksedmp()+0 3 ? 0 ? 0 ? 0 ? 0 ? 0 ?
pevm_MOVC_i()+18 signal ssexhd()+0 B ? BF93B8BC ? BF93B93C ?
pfrrun()+8458 call pevm_MOVC_i()+0 2FF19C ? 16 ? BE14650 ? 0 ?
pricar()+1277 call pfrrun()+0 2FF19C ? 1 ? BF93CCFC ?
AD638A0 ? 2DFBAC ? 0 ?
pricbr()+427 call pricar()+0 BF93DA88 ? BF93D084 ?
9BEAE0C ? 1 ? 0 ? 98C93728 ?
prient2()+598 call pricbr()+0 BF93DA88 ? BF93D084 ? 0 ?
prient()+1438 call prient2()+0 BF93DA88 ? BF93D084 ? 1 ?
BF93E4E0 ? 0 ?
kkxrpc()+347 call prient()+0 BF93DA88 ? AD638A0 ?
BF93E534 ? 38 ? 1C8C997 ? 0 ?
kporpc()+138 call kkxrpc()+0 4C ? F ? BF93E63C ?
opiodr()+5238 call kjushutdown()+2671 4C ? F ? BF93E63C ?
ttcpip()+2124 call opiodr()+0 4C ? F ? BF93E63C ? 0 ?
Cannot find symbol in /lib/libc.so.6.
opitsk()+1635 call ttcpip()+0 AD638A0 ? 4C ? BF93E63C ? 0 ?
BF93EF14 ? BF93EF10 ?
opiino()+602 call opitsk()+0 0 ? 0 ? AD638A0 ? BE01DE0 ?
103 ? 0 ?
opiodr()+5238 call kjushutdown()+2671 3C ? 4 ? BF9402E0 ?
opidrv()+517 call opiodr()+0 3C ? 4 ? BF9402E0 ? 0 ?
sou2o()+25 call opidrv()+0 3C ? 4 ? BF9402E0 ?
main()+182 call sou2o()+0 BF9402C4 ? 3C ? 4 ?
BF9402E0 ? 0 ? 0 ?
00125E9C call main()+0 2 ? BF940384 ? BF940390 ?
88A810 ? 0 ? 1 ?
---------------------Binary Stack Dump ---------------------
--进程信息
Process global information:
process: 0x962ba0b8, call: 0x96342cd8, xact: (nil), curses: 0x962e4070, usrses: 0x962e4070
----------------------------------------
SO: 0x962ba0b8, type: 2, owner: (nil), flag: INIT/-/-/0x00
(process) Oracle pid=15, calls cur/top: 0x96342cd8/0x96342cd8, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 196 0 4
last post received-location: kslpsr
last process to post me: 962b7828 1 6
last post sent: 0 0 15
last post sent-location: ksasnd
last process posted by me: 962b7828 1 6
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 0x962d9444
O/S info: user: oracle, term: UNKNOWN, ospid: 8938
OSD pid info: Unix process pid: 8938, image: oracle@localhost.localdomain (TNS V1-V3)
----------------------------------------
SO: 0x962e4070, type: 4, owner: 0x962ba0b8, flag: INIT/-/-/0x00
(session) trans: (nil), creator: 0x962ba0b8, flag: (8000041) USR/- BSY/-/-/-/-/-
DID: 0001-000F-00000004, short-term DID: 0000-0000-00000000
txn branch: (nil)
oct: 0, prv: 0, sql: (nil), psql: 0x98c3b858, user: 95/DDDD
O/S info: user: mis, term: LANDERSVR3, ospid: 7904:3012, machine: XANDER\LANDERSVR3
program: c:\orant\bin\f50run32.exe c:\forms\bas9010.fmx
application name: c:\orant\bin\f50run32.exe c:\forms\bas9010.fmx, hash value=0
last wait for 'db file sequential read' blocking sess=0x0 seq=1277 wait_time=11
file#=1, block#=21b, blocks=1
1.该用户程序是从8i升级到9i之后产生该错误
2.报错的访问程序是FORM 5
解决方案
查询MOS[ID 273411.1]发现是因为FORM 5和9i不兼容导致该错误,ORACLE未给出解决方案,言外之意,如果FORM不能升级,那就只能把ORACLE重新降级到8i.
温馨提示
在做oracle数据库升级前,需要实现进行评估,测试,如果是oracle相关软件和oracle数据库结合紧密,升级前最好需要和ORACLE技术人员确认是否兼容.
using backup controlfile 两种使用情况区别
使用备份控制文件和重建控制文件恢复,都需要使用到using backup controlfile命令,但是两种情况下却有着本质的区别
试验准备条件
SQL> select * from v$version; BANNER ------------------------------------------------------------------------- Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production PL/SQL Release 11.2.0.3.0 - Production CORE 11.2.0.3.0 Production TNS for Linux: Version 11.2.0.3.0 - Production NLSRTL Version 11.2.0.3.0 - Production SQL> select to_char(sysdate,'yyyy-mm-dd')"www.xifenfei.com" from dual; www.xifenfei.com -------------------- 2012-07-13 SQL> alter database open resetlogs; Database altered. SQL> select name from v$controlfile; NAME ---------------------------------------------------- /u01/oracle/oradata/ora11g/control01.ctl SQL> !cp /u01/oracle/oradata/ora11g/control01.ctl /tmp/xff.ctl SQL> alter system checkpoint; System altered. SQL> / System altered. SQL> / System altered. SQL> alter system switch logfile; System altered. SQL> / System altered. SQL> / System altered. SQL> / System altered. SQL> alter system checkpoint; System altered. SQL> shutdown abort; ORACLE instance shut down. SQL> !rm /u01/oracle/oradata/ora11g/control01.ctl SQL> ! cp /tmp/xff.ctl /u01/oracle/oradata/ora11g/control01.ctl SQL> startup ORACLE instance started. Total System Global Area 523108352 bytes Fixed Size 1346052 bytes Variable Size 432014844 bytes Database Buffers 83886080 bytes Redo Buffers 5861376 bytes Database mounted. ORA-01122: database file 1 failed verification check ORA-01110: data file 1: '/u01/oracle/oradata/ora11g/system01.dbf' ORA-01207: file is more recent than control file - old control file
相关说明:
1.通过resetlogs使得试验更加清晰
2.通过多次的checkpoint实现增加scn,switch logfile实现日志组切换
3.通过模拟备份控制文件恢复
查询相关SCN
SQL> set linesize 150
SQL> select file#,to_char(checkpoint_change#,'9999999999999999') "SCN",
2 to_char(RESETLOGS_CHANGE#,'9999999999999999') "RESETLOGS SCN",FUZZY
3 from v$datafile_header;
FILE# SCN RESETLOGS SCN FUZZY
---------- ---------------------------------- ---------------------------------- ------
1 2118981 2118577 YES
2 2118981 2118577 YES
3 2118981 2118577 YES
4 2118981 2118577 YES
6 2118981 2118577 YES
SQL> select file#,to_char(checkpoint_change#,'999999999999999') "SCN",
2 to_char(last_change#,'999999999999999')"STOP_SCN" from v$datafile;
FILE# SCN STOP_SCN
---------- -------------------------------- --------------------------------
1 2118580
2 2118580
3 2118580
4 2118580
6 2118580
SQL> select CONTROLFILE_CHANGE# from v$database;
CONTROLFILE_CHANGE#
-------------------
2118713
做关于控制文件和数据文件dump
SQL> oradebug setmypid; Statement processed. SQL> oradebug dump file_hdrs 3; Statement processed. SQL> oradebug tracefile_name; /u01/oracle/diag/rdbms/ora11g/ora11g/trace/ora11g_ora_593.trc SQL> exit Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options [oracle@xifenfei ~]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.3.0 Production on Fri Jul 13 03:05:48 2012 Copyright (c) 1982, 2011, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> oradebug setmypid; Statement processed. SQL> oradebug dump controlf 3; Statement processed. SQL> oradebug tracefile_name; /u01/oracle/diag/rdbms/ora11g/ora11g/trace/ora11g_ora_775.trc
分析file_hdrs 3 dump文件
--datafile 1的datafile header信息 Tablespace #0 - SYSTEM rel_fn:1 Creation at scn: 0x0000.00000007 09/18/2011 17:33:47 Backup taken at scn: 0x0000.00000000 01/01/1988 00:00:00 thread:0 reset logs count:0x2eff82e3 scn: 0x0000.002053b1 prev reset logs count:0x2e9e8451 scn: 0x0000.0016eaab recovered at 07/13/2012 02:56:18 status:0x2004 root dba:0x00400208 chkpt cnt: 760 ctl cnt:759 begin-hot-backup file size: 0 Checkpointed at scn: 0x0000.00205545 07/13/2012 03:01:42 --datafile 1的控制文件中信息 DATA FILE #1: name #7: /u01/oracle/oradata/ora11g/system01.dbf creation size=0 block size=8192 status=0xe head=7 tail=7 dup=1 tablespace 0, index=1 krfil=1 prev_file=0 unrecoverable scn: 0x0000.00000000 01/01/1988 00:00:00 Checkpoint cnt:752 scn: 0x0000.002053b4 07/13/2012 02:59:18 Stop scn: 0xffff.ffffffff 07/13/2012 02:58:43 Creation Checkpointed at scn: 0x0000.00000007 09/18/2011 17:33:47
通过这里可以看出来:
datafile header的Checkpointed scn(00205545)>controfile datafile的Checkpoint scn(002053b4)
datafile header的checkpiont count(760)>controfile datafile的checkpiont count(752)
所以在数据库open的时候会报ORA-01207错误
尝试恢复数据库
SQL> recover database using backup controlfile;
ORA-00279: change 2118713 generated at 07/13/2012 02:58:43 needed for thread 1
ORA-00289: suggestion : /u01/oracle/oradata/archivelog/ora11g/1_1_788497123.dbf
ORA-00280: change 2118713 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'/u01/oracle/oradata/archivelog/ora11g/1_1_788497123.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
SQL>
SQL> select to_char(2118713,'xxxxxxx') from dual;
TO_CHAR(2118713,
----------------
205439
分析controlf 3 dump文件
*************************************************************************** DATABASE ENTRY *************************************************************************** (size = 316, compat size = 316, section max = 1, section in-use = 1, last-recid= 0, old-recno = 0, last-recno = 0) (extent = 1, blkno = 1, numrecs = 1) 03/12/2012 22:17:06 DB Name "ORA11G" Database flags = 0x00404000 0x00001000 Controlfile Creation Timestamp 03/12/2012 22:17:07 Incmplt recovery scn: 0x0000.00000000 Resetlogs scn: 0x0000.002053b1 Resetlogs Timestamp 07/13/2012 02:58:43 Prior resetlogs scn: 0x0000.0016eaab Prior resetlogs Timestamp 05/01/2012 13:14:57 Redo Version: compatible=0xb200000 #Data files = 5, #Online files = 5 Database checkpoint: Thread=1 scn: 0x0000.002053b4 Threads: #Enabled=1, #Open=1, Head=1, Tail=1 Max log members = 3, Max data members = 1 Arch list: Head=0, Tail=0, Force scn: 0x0000.00000000scn: 0x0000.00000000 Activation ID: 4184707968 Controlfile Checkpointed at scn: 0x0000.00205439 07/13/2012 02:59:25 <==控制文件checkpiont,控制文件每3秒的一次checkpiont thread:0 rba:(0x0.0.0)
通过recover的提示和对于controlf 3 dump文件的分析,可以确定数据库使用备份控制文件恢复,需要改控制文件备份之时开始的所有归档日志
查询数据库当前redo情况
SQL> select member from v$logfile;
MEMBER
-------------------------------------------------------------
/u01/oracle/oradata/ora11g/redo03.log
/u01/oracle/oradata/ora11g/redo02.log
/u01/oracle/oradata/ora11g/redo01.log
SQL> select SEQUENCE#,STATUS,FIRST_CHANGE# ,NEXT_CHANGE# from v$log;
SEQUENCE# STATUS FIRST_CHANGE# NEXT_CHANGE#
---------- -------------------------------- ------------- ------------
1 CURRENT 2118577 2.8147E+14
0 UNUSED 0 0
0 UNUSED 0 0
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination /u01/oracle/oradata/archivelog/ora11g
Oldest online log sequence 1
Current log sequence 1
SQL> alter system dump logfile '/u01/oracle/oradata/ora11g/redo03.log';
System altered.
SQL> alter system dump logfile '/u01/oracle/oradata/ora11g/redo02.log';
System altered.
SQL> alter system dump logfile '/u01/oracle/oradata/ora11g/redo01.log';
System altered.
因为数据库处于非归档模式,而得到的redo信息主要都是来自控制文件,所以只能通过dump redo来分析当前redo的情况
分析redo log dump
DUMP OF REDO FROM FILE '/u01/oracle/oradata/ora11g/redo03.log' Opcodes *.* RBAs: 0x000000.00000000.0000 thru 0xffffffff.ffffffff.ffff SCNs: scn: 0x0000.00000000 thru scn: 0xffff.ffffffff Times: creation thru eternity FILE HEADER: Compatibility Vsn = 186646528=0xb200000 Db ID=4173966754=0xf8c9ada2, Db Name='ORA11G' Activation ID=4184707968=0xf96d9380 Control Seq=7660=0x1dec, File size=30720=0x7800 File Number=3, Blksiz=512, File Type=2 LOG descrip:"Thread 0001, Seq# 0000000003, SCN 0x00000020553d-0x000000205540" thread: 1 nab: 0x2 seq: 0x00000003 hws: 0x2 eot: 0 dis: 0 resetlogs count: 0x2eff82e3 scn: 0x0000.002053b1 (2118577) prev resetlogs count: 0x2e9e8451 scn: 0x0000.0016eaab (1501867) Low scn: 0x0000.0020553d (2118973) 07/13/2012 03:01:34 Next scn: 0x0000.00205540 (2118976) 07/13/2012 03:01:35 Enabled scn: 0x0000.002053b1 (2118577) 07/13/2012 02:58:43 Thread closed scn: 0x0000.0020553d (2118973) 07/13/2012 03:01:34 Disk cksum: 0xa716 Calc cksum: 0xa716 DUMP OF REDO FROM FILE '/u01/oracle/oradata/ora11g/redo02.log' Opcodes *.* RBAs: 0x000000.00000000.0000 thru 0xffffffff.ffffffff.ffff SCNs: scn: 0x0000.00000000 thru scn: 0xffff.ffffffff Times: creation thru eternity FILE HEADER: Compatibility Vsn = 186646528=0xb200000 Db ID=4173966754=0xf8c9ada2, Db Name='ORA11G' Activation ID=4184707968=0xf96d9380 Control Seq=7663=0x1def, File size=30720=0x7800 File Number=2, Blksiz=512, File Type=2 LOG descrip:"Thread 0001, Seq# 0000000005, SCN 0x000000205543-0xffffffffffff" thread: 1 nab: 0xffffffff seq: 0x00000005 hws: 0x1 eot: 1 dis: 0 resetlogs count: 0x2eff82e3 scn: 0x0000.002053b1 (2118577) prev resetlogs count: 0x2e9e8451 scn: 0x0000.0016eaab (1501867) Low scn: 0x0000.00205543 (2118979) 07/13/2012 03:01:36 Next scn: 0xffff.ffffffff 01/01/1988 00:00:00 Enabled scn: 0x0000.002053b1 (2118577) 07/13/2012 02:58:43 Thread closed scn: 0x0000.00205543 (2118979) 07/13/2012 03:01:36 Disk cksum: 0xc3f9 Calc cksum: 0xc3f9 Terminal recovery stop scn: 0x0000.00000000 Terminal recovery 01/01/1988 00:00:00 Most recent redo scn: 0x0000.00000000 DUMP OF REDO FROM FILE '/u01/oracle/oradata/ora11g/redo01.log' Opcodes *.* RBAs: 0x000000.00000000.0000 thru 0xffffffff.ffffffff.ffff SCNs: scn: 0x0000.00000000 thru scn: 0xffff.ffffffff Times: creation thru eternity FILE HEADER: Compatibility Vsn = 186646528=0xb200000 Db ID=4173966754=0xf8c9ada2, Db Name='ORA11G' Activation ID=4184707968=0xf96d9380 Control Seq=7663=0x1def, File size=30720=0x7800 File Number=1, Blksiz=512, File Type=2 LOG descrip:"Thread 0001, Seq# 0000000004, SCN 0x000000205540-0x000000205543" thread: 1 nab: 0x2 seq: 0x00000004 hws: 0x2 eot: 0 dis: 0 resetlogs count: 0x2eff82e3 scn: 0x0000.002053b1 (2118577) prev resetlogs count: 0x2e9e8451 scn: 0x0000.0016eaab (1501867) Low scn: 0x0000.00205540 (2118976) 07/13/2012 03:01:35 Next scn: 0x0000.00205543 (2118979) 07/13/2012 03:01:36 Enabled scn: 0x0000.002053b1 (2118577) 07/13/2012 02:58:43 Thread closed scn: 0x0000.00205540 (2118976) 07/13/2012 03:01:35 Disk cksum: 0xaa26 Calc cksum: 0xaa26 Terminal recovery stop scn: 0x0000.00000000 Terminal recovery 01/01/1988 00:00:00 Most recent redo scn: 0x0000.00000000
通过对redo dump的分析可以得到:
1.最小的sequence#=3是redo03.log
2.current redo为redo02.log
继续尝试恢复
SQL> recover database using backup controlfile;
ORA-00279: change 2118713 generated at 07/13/2012 02:58:43 needed for thread 1
ORA-00289: suggestion : /u01/oracle/oradata/archivelog/ora11g/1_1_788497123.dbf
ORA-00280: change 2118713 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/u01/oracle/oradata/ora11g/redo02.log
ORA-00326: log begins at change 2118979, need earlier change 2118713
ORA-00334: archived log: '/u01/oracle/oradata/ora11g/redo02.log'
关于备份控制文件使用using backup controlfile总结:恢复的启动控制文件备份的scn,需要该控制文件备份后的所有归档日志.对于当前这个非归档,而且redo被覆盖的库,该方法无法正常恢复
重建控制文件并做controlf 3 dump
SQL> alter database backup controlfile to trace as '/tmp/ctl.trace';
Database altered.
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORA11G" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/u01/oracle/oradata/ora11g/redo01.log' SIZE 15M BLOCKSIZE 512,
GROUP 2 '/u01/oracle/oradata/ora11g/redo02.log' SIZE 15M BLOCKSIZE 512,
GROUP 3 '/u01/oracle/oradata/ora11g/redo03.log' SIZE 15M BLOCKSIZE 512
DATAFILE
'/u01/oracle/oradata/ora11g/system01.dbf',
'/u01/oracle/oradata/ora11g/sysaux01.dbf',
'/u01/oracle/oradata/ora11g/undotbs01.dbf',
'/u01/oracle/oradata/ora11g/users01.dbf',
'/u01/oracle/oradata/ora11g/xifenfei02.dbf'
CHARACTER SET AL32UTF8
;
ORACLE instance started.
Total System Global Area 523108352 bytes
Fixed Size 1346052 bytes
Variable Size 432014844 bytes
Database Buffers 83886080 bytes
Redo Buffers 5861376 bytes
SQL> 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Control file created.
SQL> oradebug setmypid;
Statement processed.
SQL> oradebug dump controlf 3;
Statement processed.
SQL> oradebug tracefile_name;
/u01/oracle/diag/rdbms/ora11g/ora11g/trace/ora11g_ora_1867.trc
尝试数据库恢复
SQL> recover database using backup controlfile;
ORA-00279: change 2118981 generated at 07/13/2012 03:01:42 needed for thread 1
ORA-00289: suggestion : /u01/oracle/oradata/archivelog/ora11g/1_5_788497123.dbf
ORA-00280: change 2118981 for thread 1 is in sequence #5
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'/u01/oracle/oradata/archivelog/ora11g/1_5_788497123.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
SQL>
SQL> select to_char(2118981,'xxxxxxx') from dual;
TO_CHAR(2118981,
----------------
205545
SQL> set linesize 150
SQL> select file#,to_char(checkpoint_change#,'9999999999999999') "SCN",
2 to_char(RESETLOGS_CHANGE#,'9999999999999999') "RESETLOGS SCN",FUZZY
3 from v$datafile_header;
FILE# SCN RESETLOGS SCN FUZZY
---------- ---------------------------------- ---------------------------------- ------
1 2118981 2118577 YES
2 2118981 2118577 YES
3 2118981 2118577 YES
4 2118981 2118577 YES
6 2118981 2118577 YES
SQL> select file#,to_char(checkpoint_change#,'999999999999999') "SCN",
2 to_char(last_change#,'999999999999999')"STOP_SCN" from v$datafile;
FILE# SCN STOP_SCN
---------- -------------------------------- --------------------------------
1 2118981
2 2118981
3 2118981
4 2118981
6 2118981
分析 controlf 3 dump文件
*************************************************************************** DATABASE ENTRY *************************************************************************** (size = 316, compat size = 316, section max = 1, section in-use = 1, last-recid= 0, old-recno = 0, last-recno = 0) (extent = 1, blkno = 1, numrecs = 1) 07/13/2012 03:24:51 DB Name "ORA11G" Database flags = 0x00400102 0x00001000 Controlfile Creation Timestamp 07/13/2012 03:24:51 Incmplt recovery scn: 0x0000.00000000 Resetlogs scn: 0x0000.002053b1 Resetlogs Timestamp 07/13/2012 02:58:43 Prior resetlogs scn: 0x0000.0016eaab Prior resetlogs Timestamp 05/01/2012 13:14:57 Redo Version: compatible=0xb200000 #Data files = 5, #Online files = 5 Database checkpoint: Thread=1 scn: 0x0000.00205543 *************************************************************************** DATA FILE RECORDS *************************************************************************** (size = 520, compat size = 520, section max = 100, section in-use = 6, last-recid= 0, old-recno = 0, last-recno = 0) (extent = 1, blkno = 11, numrecs = 100) DATA FILE #1: name #8: /u01/oracle/oradata/ora11g/system01.dbf creation size=0 block size=8192 status=0x12 head=8 tail=8 dup=1 tablespace 0, index=1 krfil=1 prev_file=0 unrecoverable scn: 0x0000.00000000 01/01/1988 00:00:00 Checkpoint cnt:760 scn: 0x0000.00205545 07/13/2012 03:01:42 Stop scn: 0xffff.ffffffff 07/13/2012 03:24:51 Creation Checkpointed at scn: 0x0000.00000007 09/18/2011 17:33:47
完成恢复
SQL> recover database using backup controlfile;
ORA-00279: change 2118981 generated at 07/13/2012 03:01:42 needed for thread 1
ORA-00289: suggestion : /u01/oracle/oradata/archivelog/ora11g/1_5_788497123.dbf
ORA-00280: change 2118981 for thread 1 is in sequence #5
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/u01/oracle/oradata/ora11g/redo02.log
Log applied.
Media recovery complete.
关于重建控制文件后使用using backup总结:重建控制文件后,恢复的起点是datafile header scn 最小值,需要改scn之后的所有日志
发表在 Oracle备份恢复
一条评论

加我微信(17813235971)
加我QQ(107644445)

