oracle日志损坏的处理

最新推荐文章于 2024-07-30 13:15:00 发布
最新推荐文章于 2024-07-30 13:15:00 发布
阅读量288 收藏
点赞数
文章标签： 数据库
日志损坏实际处理的一个例子，以备查询。[@more@]

[oracle@ts01 oracle]$ sqlplus ''''/ as sysdba''''

SQL*Plus: Release 9.2.0.4.0 - Production on Tue Nov 15 10:35:11 2005

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.


Connected to:
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

SQL> conn / as sysdba
Connected.
SQL>

在另一个SESSION：
[oracle@ts01 oracle]$ cd /oracle/oradata/TSMISC02
[oracle@ts01 TSMISC02]$ ll
total 681820
drwxr-xr-x 2 oracle oinstall 4096 Nov 15 08:52 archive
-rw-r----- 1 oracle oinstall 1662976 Nov 15 10:35 control01.ctl
-rw-r----- 1 oracle oinstall 1662976 Nov 15 10:35 control02.ctl
-rw-r----- 1 oracle oinstall 1662976 Nov 15 10:35 control03.ctl
-rw-r----- 1 oracle oinstall 20979712 Nov 15 09:23 drsys01.dbf
-rw-r----- 1 oracle oinstall 26222592 Nov 15 09:23 indx01.dbf
-rw-r----- 1 oracle oinstall 20979712 Nov 15 09:23 odm01.dbf
-rw-r----- 1 oracle oinstall 2097664 Nov 15 10:35 redo01.log
-rw-r----- 1 oracle oinstall 2097664 Nov 15 05:48 redo02.log
-rw-r----- 1 oracle oinstall 2097664 Nov 15 08:52 redo03.log
-rw-r----- 1 oracle oinstall 387981312 Nov 15 10:26 system01.dbf
-rw-r----- 1 oracle oinstall 52436992 Nov 15 09:23 system02.dbf
-rw-r----- 1 oracle oinstall 42999808 Nov 1 14:16 temp01.dbf
-rw-r----- 1 oracle oinstall 10493952 Nov 15 09:23 tools01.dbf
-rw-r----- 1 oracle oinstall 52436992 Nov 15 10:28 undotbs2.dbf
-rw-r----- 1 oracle oinstall 26222592 Nov 15 09:23 users01.dbf
-rw-r----- 1 oracle oinstall 47194112 Nov 15 09:23 xdb01.dbf
[oracle@ts01 TSMISC02]$ cat redo01.log| od -x|head
0000000 0200 0000 0200 0000 1000 0000 5c5d 5a5b
0000020 0000 0000 1606 0000 0000 0000 0000 0000
0000040 0000 0000 0000 0000 0000 0000 0000 0000
*
0001000 003e 0000 0001 0000 f0c1 223c 0000 fec1
0001020 0000 0920 0000 0920 98c2 6798 5354 494d
0001040 4353 3230 01ec 0000 1000 0000 0200 0000
0001060 0001 0002 15c2 6798 0000 0000 0000 0000
0001100 0000 0000 0000 0000 0000 0000 0000 0000
0001120 0000 0000 0000 0000 0000 0000 6854 6572
[oracle@ts01 TSMISC02]$ >redo01.log
[oracle@ts01 TSMISC02]$ ll
total 679764
drwxr-xr-x 2 oracle oinstall 4096 Nov 15 08:52 archive
-rw-r----- 1 oracle oinstall 1662976 Nov 15 11:12 control01.ctl
-rw-r----- 1 oracle oinstall 1662976 Nov 15 11:12 control02.ctl
-rw-r----- 1 oracle oinstall 1662976 Nov 15 11:12 control03.ctl
-rw-r----- 1 oracle oinstall 20979712 Nov 15 09:23 drsys01.dbf
-rw-r----- 1 oracle oinstall 26222592 Nov 15 09:23 indx01.dbf
-rw-r----- 1 oracle oinstall 20979712 Nov 15 09:23 odm01.dbf
-rw-r----- 1 oracle oinstall 0 Nov 15 11:12 redo01.log
-rw-r----- 1 oracle oinstall 2097664 Nov 15 05:48 redo02.log
-rw-r----- 1 oracle oinstall 2097664 Nov 15 08:52 redo03.log
-rw-r----- 1 oracle oinstall 387981312 Nov 15 10:57 system01.dbf
-rw-r----- 1 oracle oinstall 52436992 Nov 15 09:23 system02.dbf
-rw-r----- 1 oracle oinstall 42999808 Nov 1 14:16 temp01.dbf
-rw-r----- 1 oracle oinstall 10493952 Nov 15 09:23 tools01.dbf
-rw-r----- 1 oracle oinstall 52436992 Nov 15 11:11 undotbs2.dbf
-rw-r----- 1 oracle oinstall 26222592 Nov 15 09:23 users01.dbf
-rw-r----- 1 oracle oinstall 47194112 Nov 15 09:23 xdb01.dbf
[oracle@ts01 TSMISC02]$


回到SESSION2：
SQL> select * from v$log;

GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS
---------- ---------- ---------- ---------- ---------- --- ----------------
FIRST_CHANGE# FIRST_TIM
------------- ---------
1 1 62 2097152 1 NO CURRENT
658443 15-NOV-05

2 1 60 2097152 1 YES INACTIVE
641419 15-NOV-05

3 1 61 2097152 1 YES INACTIVE
649920 15-NOV-05


SQL> set linesize 132
SQL> l
1* select * from v$log
SQL> /

GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- ---------
1 1 62 2097152 1 NO CURRENT 658443 15-NOV-05
2 1 60 2097152 1 YES INACTIVE 641419 15-NOV-05
3 1 61 2097152 1 YES INACTIVE 649920 15-NOV-05

SQL> alter system switch logfile;
alter system switch logfile
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel


SQL> /
alter system switch logfile
*
ERROR at line 1:
ORA-03114: not connected to ORACLE


SQL> conn / as sysdba
Connected to an idle instance.
SQL> /
alter system switch logfile
*
ERROR at line 1:
ORA-01034: ORACLE not available


SQL> conn / as sysdba
Connected to an idle instance.
SQL>

启动数据库，

'tGbGe.3O2AT4

oh络pEab,专网E;G|BU]#h
报错：
SQL> conn / as sysdba
Connected to an idle instance.
SQL>
SQL> startup
ORACLE instance started.

Total System Global Area 236000356 bytes
Fixed Size 451684 bytes
Variable Size 201326592 bytes
Database Buffers 33554432 bytes
Redo Buffers 667648 bytes
Database mounted.
ORA-00316: log 1 of thread 1, type 0 in header is not log file
ORA-00312: online log 1 thread 1: ''''/oracle/oradata/TSMISC02/redo01.log''''


SQL>
SQL> select name,OPEN_MODE from v$database;

NAME OPEN_MODE
--------- ----------
TSMISC02 MOUNTED

SQL> select * from v$instance;

INSTANCE_NUMBER INSTANCE_NAME
--------------- ----------------
HOST_NAME
----------------------------------------------------------------
VERSION STARTUP_T STATUS PAR THREAD# ARCHIVE LOG_SWITCH_
----------------- --------- ------------ --- ---------- ------- -----------
LOGINS SHU DATABASE_STATUS INSTANCE_ROLE ACTIVE_ST
---------- --- ----------------- ------------------ ---------
1 TSMISC02
ts01
9.2.0.4.0 15-NOV-05 MOUNTED NO 1 STARTED
ALLOWED NO ACTIVE PRIMARY_INSTANCE NORMAL


SQL> set linesize 132
SQL> select * from v$log;

GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- ---------
1 1 62 2097152 1 NO INVALIDATED 658443 15-NOV-05
2 1 0 2097152 1 YES UNUSED 0 15-NOV-05
3 1 61 2097152 1 YES INACTIVE 649920 15-NOV-05

SQL> col member for a100
SQL> select * from v$logfile;

GROUP# STATUS TYPE MEMBER
---------- ------- ------- ----------------------------------------------------------------------------------------------------
1 ONLINE /oracle/oradata/TSMISC02/redo01.log
2 ONLINE /oracle/oradata/TSMISC02/redo02.log
3 ONLINE /oracle/oradata/TSMISC02/redo03.log

SQL>


检查alert日志：
Tue Nov 15 11:30:13 2005
Started first pass scan
Tue Nov 15 11:30:13 2005
Errors in file /oracle/admin/TSMISC02/udump/tsmisc02_ora_29582.trc:
ORA-00316: log 1 of thread 1, type 0 in header is not log file
ORA-00312: online log 1 thread 1: ''''/oracle/oradata/TSMISC02/redo01.log''''
ORA-316 signalled during: ALTER DATABASE OPEN...
Tue Nov 15 11:31:09 2005
Restarting dead background process QMN0
QMN0 started with pid=9
Tue Nov 15 11:36:10 2005
Restarting dead background process QMN0
QMN0 started with pid=9
Tue Nov 15 11:41:11 2005
Restarting dead background process QMN0
QMN0 started with pid=9
Tue Nov 15 11:46:12 2005
Restarting dead background process QMN0
QMN0 started with pid=9
Tue Nov 15 11:51:13 2005
Restarting dead background process QMN0
QMN0 started with pid=9
Tue Nov 15 11:56:14 2005
Restarting dead background process QMN0
QMN0 started with pid=9

。。。


相关trace文件内容：
[oracle@ts01 udump]$ ll tsmisc02_ora_29582.trc
-rw-r----- 1 oracle oinstall 912 Nov 15 11:30 tsmisc02_ora_29582.trc
[oracle@ts01 udump]$ cat tsmisc02_ora_29582.trc
/oracle/admin/TSMISC02/udump/tsmisc02_ora_29582.trc
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/920
System name: Linux
Node name: ts01
Release: 2.4.21-4.EL
Version: #1 Fri Oct 3 18:13:58 EDT 2003
Machine: i686
Instance name: TSMISC02
Redo thread mounted by this instance: 1
Oracle process number: 14
Unix process pid: 29582, image: oracle@ts01 (TNS V1-V3)

*** SESSION ID:(11.3) 2005-11-15 11:30:13.297
Thread checkpoint rba:0x00003e.00000002.0010 scn:0x0000.000a0c0b
On-disk rba:0x00003e.00000c1e.0000 scn:0x0000.000a257e
Use incremental checkpoint cache-low RBA
Thread 1 recovery from rba:0x00003e.0000095f.0000 scn:0x0000.00000000
ORA-00316: log 1 of thread 1, type 0 in header is not log file
ORA-00312: online log 1 thread 1: ''''/oracle/oradata/TSMISC02/redo01.log''''
[oracle@ts01 udump]$


SQL> alter database clear logfile group 1;
alter database clear logfile group 1
*
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of thread 1
ORA-00312: online log 1 thread 1: ''''/oracle/oradata/TSMISC02/redo01.log''''


SQL> alter database clear unarchived logfile group 1;
alter database clear unarchived logfile group 1
*
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of thread 1
ORA-00312: online log 1 thread 1: ''''/oracle/oradata/TSMISC02/redo01.log''''


SQL>
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /oracle/oradata/TSMISC02/archive
Oldest online log sequence 61
Next log sequence to archive 62
Current log sequence 62
SQL> select * from v$log;

GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- ---------
1 1 62 2097152 1 NO INVALIDATED 658443 15-NOV-05
2 1 0 2097152 1 YES UNUSED 0 15-NOV-05
3 1 61 2097152 1 YES INACTIVE 649920 15-NOV-05

SQL>
断定，管{YoU2Vl软]1W的;UgXDj_垠(W,网

v'育o,理_QK中Wx
损坏的是current 的日志。

设置两个隐含参数：_ALLOW_RESETLOGS_CORRUPTION = TRUE 和 _corrupted_rollback_segments ，因为redo损坏的时候，undo数据也大都不一致了。

使用隐含参数启动数据库：
SQL> create pfile=''''/home/oracle/pfile.tmp'''' from spfile;

File created.

SQL>
SQL> shutdown immediate;
ORA-01109: database not open


Database dismounted.
ORACLE instance shut down.
SQL>


[oracle@ts01 oracle]$ tail pfile.tmp
*.sort_area_size=524288
*.star_transformation_enabled=''''FALSE''''
*.timed_statistics=TRUE
*.undo_management=''''AUTO''''
*.undo_retention=10800
*.undo_tablespace=''''UNDOTBS2''''
*.user_dump_dest=''''/oracle/admin/TSMISC02/udump''''

_ALLOW_RESETLOGS_CORRUPTION = TRUE

[oracle@ts01 oracle]$

这个参数的解释：
SQL> select KSPPDESC from X$KSPPI where ksppinm=''''_allow_resetlogs_corruption'''';

KSPPDESC
----------------------------------------------------------------
allow resetlogs even if it will cause corruption

SQL>

[oracle@ts01 oracle]$ sqlplus ''''/ as sysdba''''

SQL*Plus: Release 9.2.0.4.0 - Production on Mon Nov 21 15:57:21 2005

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to an idle instance.

SQL> startup mount pfile=pfile.tmp
ORACLE instance started.

Total System Global Area 236000356 bytes
Fixed Size 451684 bytes
Variable Size 201326592 bytes
Database Buffers 33554432 bytes
Redo Buffers 667648 bytes
Database mounted.
SQL>
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery


SQL> select status from v$instance;

STATUS
------------
MOUNTED

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-00316: log 1 of thread 1, type 0 in header is not log file
ORA-00312: online log 1 thread 1: ''''/oracle/oradata/TSMISC02/redo01.log''''


SQL>


SQL> recover database using backup controlfile until cancel;
ORA-00279: change 658443 generated at 11/15/2005 08:52:17 needed for thread 1
ORA-00289: suggestion : /oracle/oradata/TSMISC02/archive/1_62.dbf
ORA-00280: change 658443 for thread 1 is in sequence #62


Specify log: {=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: ''''/oracle/oradata/TSMISC02/system01.dbf''''


ORA-01112: media recovery not started


SQL> alter database open resetlogs;
。。。
很长时间，C提中络+o3-7,FX6中CS-q

9"X专{%hKC

Y(v?Lmg5d[的育)[]供(业

就好像hang住了
。。。
有过了一会：
SQL> alter database open resetlogs;

alter database open resetlogs
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel


SQL>
SQL> select status from v$instance;
select status from v$instance
*
ERROR at line 1:
ORA-03114: not connected to ORACLE


SQL> conn / as sysdba
Connected to an idle instance.
SQL>


检查日志，发现：
[oracle@ts01 bdump]$ tail alert_TSMISC02.log
Errors in file /oracle/admin/TSMISC02/udump/tsmisc02_ora_10762.trc:
ORA-00600: internal error code, arguments: [2662], [0], [658448], [0], [664313], [12582921], [], []
Mon Nov 21 16:11:44 2005
Errors in file /oracle/admin/TSMISC02/udump/tsmisc02_ora_10762.trc:
ORA-00600: internal error code, arguments: [2662], [0], [658448], [0], [664313], [12582921], [], []
Mon Nov 21 16:11:44 2005
Error 600 happened during db open, shutting down database
USER: terminating instance due to error 600
Instance terminated by USER, pid = 10762
ORA-1092 signalled during: alter database open resetlogs...
[oracle@ts01 bdump]$


设置event adjust_scn：
alter session set events ''''10015 trace name adjust_scn level 1'''';

SQL> conn / as sysdba
Connected to an idle instance.
SQL> startup mount pfile=pfile.tmp
ORACLE instance started.

Total System Global Area 236000356 bytes
Fixed Size 451684 bytes
Variable Size 201326592 bytes
Database Buffers 33554432 bytes
Redo Buffers 667648 bytes
Database mounted.
SQL>
SQL> alter session set events ''''10015 trace name adjust_scn level 1'''';

Session altered.

SQL>
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 658445 generated at 11/21/2005 16:11:43 needed for thread 1
ORA-00289: suggestion : /oracle/oradata/TSMISC02/archive/1_1.dbf
ORA-00280: change 658445 for thread 1 is in sequence #1


Specify log: {=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: ''''/oracle/oradata/TSMISC02/system01.dbf''''


ORA-01112: media recovery not started


SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced


SQL>
检查日志：
[oracle@ts01 bdump]$ tail alert_TSMISC02.log
Errors in file /oracle/admin/TSMISC02/udump/tsmisc02_ora_10762.trc:
ORA-00600: internal error code, arguments: [2662], [0], [658448], [0], [664313], [12582921], [], []
Mon Nov 21 16:11:44 2005
Errors in file /oracle/admin/TSMISC02/udump/tsmisc02_ora_10762.trc:
ORA-00600: internal error code, arguments: [2662], [0], [658448], [0], [664313], [12582921], [], []
Mon Nov 21 16:11:44 2005
Error 600 happened during db open, shutting down database
USER: terminating instance due to error 600
Instance terminated by USER, pid = 10762
ORA-1092 signalled during: alter database open resetlogs...

[oracle@ts01 bdump]$ tail alert_TSMISC02.log
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0
Mem# 0 errs 0: /oracle/oradata/TSMISC02/redo01.log
Mon Nov 21 16:21:41 2005
Errors in file /oracle/admin/TSMISC02/udump/tsmisc02_ora_10795.trc:
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [4194], [91], [69], [], [], [], [], []
Error 607 happened during db open, shutting down database
USER: terminating instance due to error 607
Instance terminated by USER, pid = 10795
ORA-1092 signalled during: alter database open resetlogs...
[oracle@ts01 bdump]$ tail -f alert_TSMISC02.log
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0
Mem# 0 errs 0: /oracle/oradata/TSMISC02/redo01.log
Mon Nov 21 16:21:41 2005
Errors in file /oracle/admin/TSMISC02/udump/tsmisc02_ora_10795.trc:
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [4194], [91], [69], [], [], [], [], []
Error 607 happened during db open, shutting down database
USER: terminating instance due to error 607
Instance terminated by USER, pid = 10795
ORA-1092 signalled during: alter database open resetlogs...

[oracle@ts01 bdump]$


设置隐含参数：
将undo改变成手工管理的，

s教`HXN业WZ9V
然后重启数据库，

SQL> show parameter undo

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
undo_management string MANUEL
undo_retention integer 10800
undo_suppress_errors boolean FALSE
undo_tablespace string UNDOTBS2
SQL>

[oracle@ts01 oracle]$ tail pfile.tmp
*.undo_management=''''AUTO''''
*.undo_retention=10800
*.undo_tablespace=''''UNDOTBS2''''
*.user_dump_dest=''''/oracle/admin/TSMISC02/udump''''

*._ALLOW_RESETLOGS_CORRUPTION = TRUE
*.undo_management=''''manual''''

[oracle@ts01 oracle]$
[oracle@ts01 oracle]$ exit
exit
SQL> startup pfile=pfile.tmp
ORACLE instance started.

Total System Global Area 236000356 bytes
Fixed Size 451684 bytes
Variable Size 201326592 bytes
Database Buffers 33554432 bytes
Redo Buffers 667648 bytes
Database mounted.
Database opened.
SQL>
SQL> conn lunar/lunar
Connected.
SQL> select * from tab;

TNAME TABTYPE CLUSTERID
------------------------------ ------- ----------
LUNARTEST TABLE

SQL>

总结：

将undo改变成手工管理的，

u无j网-jb},提jV*)

=Q管V8`?IO&E*S供J--|}无EC!cHK供
然后设置隐含参数 _ALLOW_RESETLOGS_CORRUPTION = TRUE 和 _corrupted_rollback_segments ,因为redo损坏的时候，undo数据也大都不一致
了。
2，open resetlogs之前，先使用recover database using backup controlfile until cancel;
如果此时又遇到600错误，就使用ADJUST_SCN事件来调整当前的SCN，如果SCN相差不多，可以通过多次重起数据库解决。如果scn相差比较多，

可以使用10015 event：
alter session set events ''''10015 trace name adjust_scn level 1'''';
如果SCN相差比较多，可以设置level 2，。。。level 10等 (level 1是每次打开时将将scn推进1百万)

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/34329/viewspace-911226/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/34329/viewspace-911226/

cuishi6011
关注
Oracle redo 日志损坏的几种情况下的恢复方式
Ahern_的博客
05-09 1436
该参数默认值为 FALSE，意思是不允许使用 resetlogs 打开数据库，这样会导致数据库事故，修改为 true 表示即使会导致数据库事故，也可以使用 resetlogs 打开数据库，2、数据库处于归档模式，数据库open状态、当前正在使用的日志文件损坏，并且正常关闭了数据库。3、数据库处于归档模式，数据库open状态、当前正在使用的日志文件损坏，并且异常关闭数据库。1、归档模式，不是当前正在使用的日志损坏(INACTIVE)，数据库处于活动状态。3、数据库处于活动状态，非归档模式，非当前日志损坏。
ORACLE联机日志文件丢失或损坏的处理方法
11-05
ORACLE联机日志文件丢失或损坏的处理方法，联机日志分为当前联机日志和非当前联机日志
oracle 联机日志文件损坏的几种场景和恢复方法
oradh的专栏
04-25 2239
oracle 日志文件记录数据库运行过程中发生d
oracle日志组损坏的处置方法
最新发布
07-30 127
3）如果之前没有可用的备份，或问题严重到任何方法都不能 resetlogs 打开数据库，为了抢救数据，考虑最后一招使用 Oracle的隐含参数：_allow_resetlogs_corruption=TRUE。数据库此时为打开状态，这步若能成功，一定要做一个新的数据库全备，因为当前日志无法归档，归档日志 sequence 已无法保持连续性。本例日志组 1 状态是 CURRENT 状态的，现在模拟当前日志组损坏。2）数据库已经崩溃，只能做传统的基于日志的不完全恢复或使用闪回数据库。切换几次，触动它一下。
oracle在线日志损坏,前在线日志文件损坏与ora-600 [4000]处理
weixin_42367557的博客
04-15 258
这次又是一台机器上面有两个实例A和B。又是由于非当前的在线日志文件的状态是处于closed状态的(裸设备)，于是dba将A节点的非当前在线日志文件填加到了B节点上面去了，于是在A节点日志发生切换时，导致了当前在线日志文件损坏。一般情况下当前在线日志文件损坏也是还好处理的，但是这次却是较为复杂。。。。系统环境：aix p550，oracle 9206首先检查v$datafile_header，发现c...
oracle 日志 损坏,在线重做日志文件损坏时的Oracle数据库恢复方法
weixin_39663933的博客
04-09 238
问：我在CentOS 4操作系统的NOARCHIVE模式下运行了一个Oracle 9i数据库。最近，我试图启动数据库，但是它无法达到启动状态(一直处于安装状态)。输出日志是这样的：SQL> ORACLE instance started.Total System Global Area 823203616 bytesFixed Size 452384 bytesVariable Size 3...
REDO文件损坏修复
喝醉酒的小白
02-13 2202
inactive current active
Oracle数据库日志文件损坏时修复方法的实验研究.pdf
10-10
而在归档模式下，若重做日志损坏，可以使用归档日志进行恢复。如果归档日志也损坏，修复过程会更加复杂，可能需要结合备份和时间点恢复技术。 文章通过模拟数据库故障的方式，对不同情况下的修复方法进行了实验研究...
关于oracle日志文件.docx
01-21
- **异常处理**: 当日志文件状态显示为INVALID、STALE或DELETED时，需要立即采取行动，例如检查文件的物理路径、修复损坏的文件或重新创建。 **数据库恢复**: 在介质故障或实例故障情况下，通过重做日志和归档日志...
Oracle 12c实战日志文件
03-05
### Oracle 12c 实战日志文件详解 #### 一、概述 Oracle 12c 是 Oracle 数据库管理系统的一个重要版本，它引入了许多新功能和技术改进，旨在提高数据库性能、安全性和易用性。其中，日志文件管理是确保数据库稳定...
oracle 控制文件启动不了,Oracle 控制文件损坏解决方案
weixin_36299482的博客
04-03 1330
Oracle控制文件损坏解决方案故障一：丢失(损坏)一个控制文件前台报错：ORA-00205：error in identifying control file,check alert log formore info解决方案：(干净或非干净方式关闭数据库)使用完好的控制文件复制(替换)重命名丢失(损坏)的控制文件；故障二：两个控制文件版本不一致(1)一个控制文件正常，另一个控制文件来源于其他备份...
如果控制文件损坏那么如何恢复？恢复控制文件的方式有哪几种
小麦苗DBA宝典
04-02 833
【RMAN】如果控制文件损坏那么如何恢复？恢复控制文件的方式有哪几种？ 真题1、如果控制文件损坏那么如何恢复？恢复控制文件的方式有哪几种？ 答案：如果控制文件有多个，而只损坏了单个控制文件，那么只需要关闭数据库，拷贝其它好的控制文件覆盖掉坏的控制文件即可。也可以修改参数文件，只保留1个控制文件。如果损坏了全部控制文件...
oracle回滚段损坏,10.10.2 如何处理回滚段损坏（1）
weixin_34932795的博客
04-07 215
10.10.2 如何处理回滚段损坏(1)如果生产环境中遇到了回滚段的损坏，当然***的方法当然是完全恢复，不过如果现实条件不允许的话(比如没有备份，或恢复时间太长)，对于回滚段还可以有一种非常规的手段，这个手段的处理流程如图10-4所示。之所以可以这么处理，因为回滚段是用来支持事务的，如果事务提交，回滚段中的数据就没用了。如果事务尚未提交时回滚段发生了损坏，我们可以强制事务提交，这样只会损失部分...
重庆思庄oracle技术分享-控制文件全部损坏的解决方案
duanweifang的博客
08-10 242
重庆思庄oracle技术分享-控制文件全部损坏的解决方案
Oracle 文件损坏及恢复的过程
07-18 99
一、基本情况 OS：RHEL 3 CPU：4个Intel(R) Xeon(TM) MP CPU 2.70GHz Mem：8G Swap：16G Disk：120G Oracle Database 10g Enterprise Edition Release 10.1.0.3.0 二、备份方式 数据库以archive模式运行，RMAN多级增量备份。策略如下： 设置控...
oracle ORA-00214 控制文件损坏处理
LightJie的专栏
03-03 1265
<br />SQL> conn sys as sysdba<br />SQL> startup nomount<br />SQL> alter system set control_files=<br />  'D:/ORACLE/ORADATA/ORA10/CONTROL02.CTL'<br />  scope=spfile;<br />SQL> alter database mount<br />SQL> alter database open
ORA-16456错误，由于备库未mount而在主库执行切换，解决办法详解
cuiyan1982的专栏
10-19 1911
如果对数据库进行主备库的切换需要的前提条件是： （1）备库必须mount状态下,主库open状态 （2）必须不能在最大保护模式下  我们有时做主备库的切换，结果忘记了把备库处于mount状态而是open状态下； 当在primary执行过切换操作之后： SQL>alterdatabase commit to switchover to physical standby;
oracle 启动_Oracle体系结构之数据库启停（二）--实例操作
weixin_39845306的博客
11-23 117
实例启动与关闭一、 数据库的四种状态.二、 启动数据库的相关指令.三、 实例的启动与关闭.接上一篇三、实例的启动与关闭(三)、启动实例阶段(STARTED) 3．打开的文件 1) 警告日志文件 //启动实例前执行，查看进程是否打开 [oracle@oracle ~ ]$ ps -ef | grep ora_ oracle 4809 4776 0 09:10 pts/2 00:00:00 grep ...
Oracle日志分析工具LogMiner入门与实例
然而，值得注意的是，尽管LogMiner非常强大，但它并不适合处理复杂的恢复任务，如数据丢失或损坏的情况，这些情况通常需要借助RMAN（Recovery Manager）进行更全面的备份和恢复操作。此外，频繁使用LogMiner可能对...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值