大家好，又见面了，我是全栈君。
数据库处于非归档状态，其联机日志循环覆盖使用，这意味着如果数据库需要进行介质恢复应用相关归档，又由于非归档导致归档文件不存在，那么此时数据库只能执行基于取消的恢复，回退整个数据库到上一次全备份状态。或者修改数据文件头部信息，来规避缺失归档。但不管怎么样都会丢失数据。
下面介绍非归档模式下几种常见故障处理方法。
一 非归档下的常用备份和恢复方法：
如何备份
Backing Up a Database in NOARCHIVELOG Mode You can only backup a database in NOARCHIVELOG mode when the database is closed and in a consistent state.
1 shutdown immediate
2 startup mount
3 backup database
如何恢复
注意 和归档模式下的恢复有如下不同点：
1 Only consistent backups can be used in restoring a database in NOARCHIVELOG mode.
2 Media recovery is not possible because no archived redo logs exist.
恢复步骤如下：
1 startup force mount；
2 restore database；
3 recover database until cancel；
4 alter database open resetlogs；
举例如下：
备份
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination /oracle/archive
Oldest online log sequence 1
Current log sequence 2
RMAN> shutdown immediate;
using target database control file instead of recovery catalog
database closed
database dismounted
Oracle instance shut down
RMAN> startup mount;
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area 1252663296 bytes
Fixed Size 2226072 bytes
Variable Size 1006635112 bytes
Database Buffers 234881024 bytes
Redo Buffers 8921088 bytes
RMAN> backup database;
Starting backup at 2013-02-03 13:26:36
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=63 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=129 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00004 name=/backup/users01.dbf
input datafile file number=00003 name=/oracle/CRM/undotbs3.dbf
input datafile file number=00006 name=/oracle/CRM/erp.dbf
input datafile file number=00007 name=/oracle/CRM/user01.dbf
channel ORA_DISK_1: starting piece 1 at 2013-02-03 13:26:38
channel ORA_DISK_2: starting full datafile backup set
channel ORA_DISK_2: specifying datafile(s) in backup set
input datafile file number=00001 name=/oracle/CRM/system01.dbf
input datafile file number=00002 name=/oracle/CRM/sysaux01.dbf
input datafile file number=00005 name=/oracle/CRM/pos.dbf
channel ORA_DISK_2: starting piece 1 at 2013-02-03 13:26:39
channel ORA_DISK_1: finished piece 1 at 2013-02-03 13:29:36
piece handle=/backup/20130203_fro11v4d_1_1 tag=TAG20130203T132637 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:59
channel ORA_DISK_2: finished piece 1 at 2013-02-03 13:29:38
piece handle=/backup/20130203_fso11v4e_1_1 tag=TAG20130203T132637 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:02:59
Finished backup at 2013-02-03 13:29:38
Starting Control File and SPFILE Autobackup at 2013-02-03 13:29:38
piece handle=/backup/c-3599153036-20130203-00 comment=NONE
Finished Control File and SPFILE Autobackup at 2013-02-03 13:29:41
恢复
RMAN> startup force mount;
Oracle instance started
database mounted
Total System Global Area 1252663296 bytes
Fixed Size 2226072 bytes
Variable Size 1006635112 bytes
Database Buffers 234881024 bytes
Redo Buffers 8921088 bytes
RMAN> restore database;
Starting restore at 2013-02-03 16:13:04
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=63 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=129 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00003 to /oracle/CRM/undotbs3.dbf
channel ORA_DISK_1: restoring datafile 00004 to /backup/users01.dbf
channel ORA_DISK_1: restoring datafile 00006 to /oracle/CRM/erp.dbf
channel ORA_DISK_1: restoring datafile 00007 to /oracle/CRM/user01.dbf
channel ORA_DISK_1: reading from backup piece /backup/20130203_fro11v4d_1_1
channel ORA_DISK_2: starting datafile backup set restore
channel ORA_DISK_2: specifying datafile(s) to restore from backup set
channel ORA_DISK_2: restoring datafile 00001 to /oracle/CRM/system01.dbf
channel ORA_DISK_2: restoring datafile 00002 to /oracle/CRM/sysaux01.dbf
channel ORA_DISK_2: restoring datafile 00005 to /oracle/CRM/pos.dbf
channel ORA_DISK_2: reading from backup piece /backup/20130203_fso11v4e_1_1
channel ORA_DISK_1: piece handle=/backup/20130203_fro11v4d_1_1 tag=TAG20130203T132637
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:04:09
channel ORA_DISK_2: piece handle=/backup/20130203_fso11v4e_1_1 tag=TAG20130203T132637
channel ORA_DISK_2: restored backup piece 1
channel ORA_DISK_2: restore complete, elapsed time: 00:04:11
Finished restore at 2013-02-03 16:17:17
RMAN> host;
[oracle@oracle ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.2.0 Production on Sun Feb 3 16:27:12 2013
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> recover database until cancel;
ORA-00279: change 2942346 generated at 02/03/2013 13:26:11 needed for thread 1
ORA-00289: suggestion : /oracle/archive/1_2_806264057.dbf
ORA-00280: change 2942346 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> alter database open resetlogs;
Database altered.
SQL> select group#,archived,sequence#,status from v$Log;
GROUP# ARC SEQUENCE# STATUS
———- — ———- —————-
1 NO 1 CURRENT
2 YES 0 UNUSED
3 YES 0 UNUSED
4 YES 0 UNUSED
二 非归档无备份，单个文件丢失造成数据库无法打开
第一种方法：
SQL> startup ;
ORACLE instance started.
Total System Global Area 1252663296 bytes
Fixed Size 2226072 bytes
Variable Size 1006635112 bytes
Database Buffers 234881024 bytes
Redo Buffers 8921088 bytes
Database mounted.
ORA-01157: cannot identify/lock data file 8 – see DBWR trace file
ORA-01110: data file 8: ‘/oracle/CRM/test.dbf’
SQL> alter database datafile 8 offline drop;
Database altered.
SQL> alter database open;
Database altered.
SQL> alter database create datafile ‘/oracle/CRM/test.dbf’;
Database altered.
SQL> select hxfil,fhscn,fhrba_seq from x$kcvfh;
HXFIL FHSCN FHRBA_SEQ
———- —————- ———-
1 3078640 37
2 3078640 37
3 3078640 37
4 3078640 37
5 3078640 37
6 3078640 37
7 3078640 37
8 3077425 31
8 rows selected.
SQL> select group#,archived,sequence#,status from v$log;
GROUP# ARC SEQUENCE# STATUS
———- — ———- —————-
1 NO 37 CURRENT
2 NO 34 INACTIVE
3 NO 35 INACTIVE
4 NO 36 INACTIVE
由于是非归档则31、32、33号归档丢失，完全恢复已经不可能，只能执行基于取消的恢复，回退整个数据库。
SQL> startup force mount;
ORACLE instance started.
Total System Global Area 1252663296 bytes
Fixed Size 2226072 bytes
Variable Size 1006635112 bytes
Database Buffers 234881024 bytes
Redo Buffers 8921088 bytes
Database mounted.
SQL> recover database until cancel;
ORA-00279: change 3078640 generated at 02/20/2013 16:44:47 needed for thread 1
ORA-00289: suggestion : /oracle/archive/1_37_806501358.dbf
ORA-00280: change 3078640 for thread 1 is in sequence #37
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-10879: error signaled in parallel recovery slave
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/CRM/system01.dbf
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: ‘/oracle/CRM/system01.dbf’
SQL> alter system set “_allow_resetlogs_corruption”=true scope=spfile;
System altered.
SQL> startup force mount;
ORACLE instance started.
Total System Global Area 1252663296 bytes
Fixed Size 2226072 bytes
Variable Size 1006635112 bytes
Database Buffers 234881024 bytes
Redo Buffers 8921088 bytes
Database mounted.
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [2662], [0], [3078648], [0],
[3078665], [4194432], [], [], [], [], [], []
Process ID: 5678
Session ID: 191 Serial number: 3
这里通过重启规避ora-600 [2662]错误
SQL> startup;
ORACLE instance started.
Total System Global Area 1252663296 bytes
Fixed Size 2226072 bytes
Variable Size 1006635112 bytes
Database Buffers 234881024 bytes
Redo Buffers 8921088 bytes
Database mounted.
Database opened.
第二种方法
SQL> startup
ORACLE instance started.
Total System Global Area 1252663296 bytes
Fixed Size 2226072 bytes
Variable Size 1006635112 bytes
Database Buffers 234881024 bytes
Redo Buffers 8921088 bytes
Database mounted.
ORA-01157: cannot identify/lock data file 8 – see DBWR trace file
ORA-01110: data file 8: ‘/oracle/CRM/test.dbf’
SQL> alter database create datafile ‘/oracle/CRM/test.dbf’;
Database altered.
注意，当我们用 alter database create datafile 创建数据文件时，数据文件头部scn以及rba.seq号均取自于该数据文件创建时控制文件中记录的scn和rba.seq号，如下：
DATA FILE #8:
name #14: /oracle/CRM/test.dbf
Creation Checkpointed at scn: 0x0000.002d4053 02/03/2013 17:02:59
thread:1 rba:(0x2.20d.10)
0x2d4053准换为10进制为2965587
rba:(0x2.20d.10)则表示seq号为2.块525.偏移量10
SQL> select hxfil,fhscn,fhrba_seq,fhrba_bno from x$kcvfh;
HXFIL FHSCN FHRBA_SEQ FHRBA_BNO
———- —————- ———- ———-
1 2967064 9 807
2 2967064 9 807
3 2967064 9 807
4 2967064 9 807
5 2967064 9 807
6 2967064 9 807
7 2967064 9 807
8 2965587 2 525
8 rows selected.
SQL> select group#,archived,sequence#,status from v$Log;
GROUP# ARC SEQUENCE# STATUS
———- — ———- —————-
1 NO 9 CURRENT
4 NO 8 INACTIVE
3 NO 7 INACTIVE
2 NO 6 INACTIVE
注意：结合8号数据文件头部rba.seq号为2以及数据库当前日志的seq为9，那么当我们用命令recover datafile 8进行介质恢复时，数据库需调用2、3、4、5号归档和联机日志6、7、8、9来完成恢复。但事实是，数据库处于非归档模式 2、3、4、5 号归档是不存在的，进行完全介质恢复已不可能。能够做的就是进行基于取消的恢复，或者修改数据 文件头部，使数据文件从9号联机日志处开始介质恢复或者调整该数据文件头部信息和其它数据文件保持一致，使介质恢复跳过归档和联机日志。但不过不管怎样，都会丢失数据。
三 非归档current组日志文件丢失
非归档模式 oracle当前联机日志文件的处理通常有两种处理方式如下：
1 启动数据库到mount状态，用命令alter database clear logfile group n 对丢失的当前日志组进行初始化
2 执行基于取消的恢复
方法一：用命令alter database clear logfile group n 初始化当前日志组
1 数据库的log_mode如下：
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination /oracle/archive
Oldest online log sequence 5
Current log sequence 8
2 当前日志组信息如下：
SQL> select group#,archived,sequence#,status from v$log;
GROUP# ARC SEQUENCE# STATUS
———- — ———- —————-
1 NO 5 INACTIVE
2 NO 6 INACTIVE
3 NO 7 INACTIVE
4 NO 8 CURRENT
SQL> col member for a40
SQL> select group#,member from v$logfile;
GROUP# MEMBER
———- —————————————-
3 /oracle/CRM/redo03.log
2 /oracle/CRM/redo02.log
1 /oracle/CRM/redo01.log
4 /oracle/CRM/redo02.dbf
3 删除当前日志组
SQL> host
[oracle@oracle ~]$ rm -rf /oracle/CRM/redo02.dbf
4 启动报错日志如下：
Errors in file /oracle/app/diag/rdbms/crm/CRM/trace/CRM_m000_5259.trc:
ORA-00313: open failed for members of log group 4 of thread 1
ORA-00312: online log 4 thread 1: ‘/oracle/CRM/redo02.dbf’
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Dumping diagnostic data in directory=[cdmp_20130201163228], requested by (instance=1, osid=5257), summary=[abnormal instance termination].
USER (ospid: 5257): terminating the instance due to error 313
Instance terminated by USER, pid = 5257
5恢复过程
SQL> select group#,archived,sequence#,status from v$log;
GROUP# ARC SEQUENCE# STATUS
———- — ———- —————-
1 NO 5 INACTIVE
4 NO 8 CURRENT
3 NO 7 INACTIVE
2 NO 6 INACTIVE
SQL> alter database clear logfile group 4;
Database altered.
SQL> alter database open;
Database altered.
方法二：执行基于取消的恢复
1 数据库当前日志状态如下：
SQL> select group#,archived,sequence#,status from v$log;
GROUP# ARC SEQUENCE# STATUS
———- — ———- —————-
1 NO 9 INACTIVE
2 NO 6 INACTIVE
3 NO 7 INACTIVE
4 NO 10 CURRENT
SQL> col member for a40
SQL> select group#,member from v$logfile;
GROUP# MEMBER
———- —————————————-
3 /oracle/CRM/redo03.log
2 /oracle/CRM/redo02.log
1 /oracle/CRM/redo01.log
4 /oracle/CRM/redo02.dbf
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
2 删除当前联机日志文件
[oracle@oracle ~]$ rm -rf /oracle/CRM/redo02.dbf
3 恢复过程如下：
SQL> startup mount;
ORACLE instance started.
Total System Global Area 1252663296 bytes
Fixed Size 2226072 bytes
Variable Size 1006635112 bytes
Database Buffers 234881024 bytes
Redo Buffers 8921088 bytes
Database mounted.
SQL> recover database until cancel;
Media recovery complete.
SQL> alter database open resetlogs;
Database altered.
SQL> select group#,archived,sequence#,status from v$log;
GROUP# ARC SEQUENCE# STATUS
———- — ———- —————-
1 NO 1 CURRENT
2 YES 0 UNUSED
3 YES 0 UNUSED
4 YES 0 UNUSED
需要注意的是对于非归档数据库当前日志损坏的处理，我们可以直接对当前日志组用命令alter database clear logfile group n 进行处理 这点和归档模式下还是有区别的。
总结：
个人感觉如果数据库没更新，只是做查询用，数据库为非归档，做一次全备份即可。
本文转自 zhangxuwl 51CTO博客，原文链接：http://blog.51cto.com/jiujian/1139304，如需转载请自行联系原作者
版权声明：本文内容由互联网用户自发贡献，该文观点仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 举报，一经查实，本站将立刻删除。
发布者：全栈程序员-用户IM，转载请注明出处：https://javaforall.cn/107936.html原文链接：https://javaforall.cn
【正版授权，激活自己账号】： Jetbrains全家桶Ide使用，1年售后保障，每天仅需1毛
【官方授权 正版激活】： 官方授权 正版激活 支持Jetbrains家族下所有IDE 使用个人JB账号...
