rman恢复报错ORA-01110: data file 1

最新推荐文章于 2024-08-20 20:35:11 发布
最新推荐文章于 2024-08-20 20:35:11 发布
阅读量1.1k 收藏 1
点赞数 1
文章标签： 数据库 操作系统
在进行一次从RMAN全备份文件中(有全备文件集,归档备份,控制文件及spfile)在异地恢复时遇到报错,恢复不成功,开始怀疑是数据库修改过归档目录引起归档日志备份不成功。但当把最近的归档日志恢复出来后，仍然报同样的错误。接着发现一个datafile的状态为offline，进而看到其checkpiont是很早以前的。问题就出在这里。以下是整个恢复过程：
一、恢复pfile
RMAN> restore spfile to '/opt/oracle/backup/spfile.ora' from '/opt/oracle/backup/itown01_20120723_9910_1.spf';
Starting restore at 27-JUL-12
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=12 devtype=DISK
channel ORA_DISK_1: autobackup found: /opt/oracle/backup/itown01_20120723_9910_1.spf
channel ORA_DISK_1: SPFILE restore from autobackup complete
Finished restore at 27-JUL-12
RMAN> exit  
SQL> create pfile='/opt/oracle/backup/pfile.ora' from spfile='/opt/oracle/backup/spfile.ora'
  2  ;
File created.
SQL>
二、启动到nomount
SQL> connect / as sysdba
Connected to an idle instance.
SQL> startup nomount pfile='/opt/oracle/backup/pfile.ora';
ORACLE instance started.
Total System Global Area 1678842656
bytes
Fixed Size                   453408
bytes
Variable Size             838860800
bytes
Database Buffers          838860800
bytes
Redo Buffers                 667648
bytes
SQL> create spfile from pfile='/opt/oracle/backup/pfile.ora';
File created.
SQL> exit
三、recover
RMAN> connect target /  
connected to target database: itown01m (not mounted)
RMAN> set dbid=2826132969
executing command: SET DBID
RMAN> restore controlfile from '/opt/oracle/backup/itown01_20120723_9911_1.ctl_1.ctl';
Starting restore at 27-JUL-12
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=12 devtype=DISK
channel ORA_DISK_1: restoring controlfile
channel ORA_DISK_1: restore complete
replicating controlfile
input filename=/u01/product/oradata/itown01m/control01.ctl
output filename=/u01/product/oradata/itown01m/control02.ctl
output filename=/u01/product/oradata/itown01m/control03.ctl
Finished restore at 27-JUL-12
RMAN> alter database mount;
RMAN> run{
set until sequence 195375 thread 1;
2> 3> restore database;
4> recover database;
5> }
executing command: SET until clause
Starting restore at 31-JUL-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /u01/product/oradata/itown01m/system01.dbf
restoring datafile 00017 to /u01/product/oradata/itown01m/et_tab_s_01.dbf
restoring datafile 00022 to /u01/product/oradata/itown01m/et_tab_l_03.dbf
restoring datafile 00030 to /u01/product/oradata/itown01m/ss01.dbf
restoring datafile 00031 to /u01/product/oradata/itown01m/ss_h1n101.dbf
channel ORA_DISK_1: restored backup piece 1
piece handle=/opt/oracle/backup/itown01_20120723_9904_1.dbf tag=TAG20120723T040049 params=NULL
channel ORA_DISK_1: restore complete
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00004 to /u01/product/oradata/itown01m/drsys01.dbf
restoring datafile 00005 to /u01/product/oradata/itown01m/example01.dbf
restoring datafile 00013 to /u01/product/oradata/itown01m/et_tab_l_01.dbf
restoring datafile 00014 to /u01/product/oradata/itown01m/system02.dbf
restoring datafile 00023 to /u01/product/oradata/itown01m/et_tab_l_04.dbf
restoring datafile 00036 to /u01/product/oradata/itown01m/ss02.dbf
channel ORA_DISK_1: restored backup piece 1
piece handle=/opt/oracle/backup/itown01_20120723_9905_1.dbf tag=TAG20120723T040049 params=NULL
channel ORA_DISK_1: restore complete
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00002 to /u01/product/oradata/itown01m/undotbs01.dbf
restoring datafile 00012 to /u01/product/oradata/itown01m/et_idx_l_01.dbf
restoring datafile 00016 to /u01/product/oradata/itown01m/et_idx_s_01.dbf
restoring datafile 00021 to /u01/product/oradata/itown01m/et_tab_xl_02.dbf
restoring datafile 00027 to /u01/product/oradata/itown01m/jablog02.dbf
restoring datafile 00035 to /u01/product/oradata/itown01m/bas01.dbf
restoring datafile 00037 to /u01/product/oradata/itown01m/cm02.dbf
channel ORA_DISK_1: restored backup piece 1
piece handle=/opt/oracle/backup/itown01_20120723_9906_1.dbf tag=TAG20120723T040049 params=NULL
channel ORA_DISK_1: restore complete
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00003 to /u01/product/oradata/itown01m/cwmlite01.dbf
restoring datafile 00007 to /u01/product/oradata/itown01m/odm01.dbf
restoring datafile 00008 to /u01/product/oradata/itown01m/tools01.dbf
restoring datafile 00010 to /u01/product/oradata/itown01m/xdb01.dbf
restoring datafile 00015 to /u01/product/oradata/itown01m/undotbs02.dbf
restoring datafile 00020 to /u01/product/oradata/itown01m/et_tab_l_02.dbf
restoring datafile 00026 to /u01/product/oradata/itown01m/jablog01.dbf
restoring datafile 00028 to /u01/product/oradata/itown01m/users03.dbf
restoring datafile 00032 to /u01/product/oradata/itown01m/isys01.dbf
restoring datafile 00033 to /u01/product/oradata/itown01m/cm01.dbf
channel ORA_DISK_1: restored backup piece 1
piece handle=/opt/oracle/backup/itown01_20120723_9907_1.dbf tag=TAG20120723T040049 params=NULL
channel ORA_DISK_1: restore complete
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00006 to /u01/product/oradata/itown01m/indx01.dbf
restoring datafile 00009 to /u01/product/oradata/itown01m/users01.dbf
restoring datafile 00011 to /u01/product/oradata/itown01m/et_tab_xl_01.dbf
restoring datafile 00018 to /u01/product/oradata/itown01m/et_fee_tab_01.dbf
restoring datafile 00019 to /u01/product/oradata/itown01m/et_fee_idx_01.dbf
restoring datafile 00024 to /u01/product/oradata/itown01m/et_tab_xl_03.dbf
restoring datafile 00025 to /u01/product/oradata/itown01m/users02.dbf
restoring datafile 00029 to /u01/product/oradata/itown01m/users04.dbf
restoring datafile 00034 to /u01/product/oradata/itown01m/it_fee01.dbf
channel ORA_DISK_1: restored backup piece 1
piece handle=/opt/oracle/backup/itown01_20120723_9908_1.dbf tag=TAG20120723T040049 params=NULL
channel ORA_DISK_1: restore complete
Finished restore at 31-JUL-12
Starting recover at 31-JUL-12
using channel ORA_DISK_1
starting media recovery
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/product/oradata/itown01m/system01.dbf'
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/31/2012 11:02:54
RMAN-06053: unable to perform. media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 195352 scn 9513178976437 found to restore
RMAN-06025: no backup of log thread 1 seq 195351 scn 9513178974630 found to restore
RMAN-06025: no backup of log thread 1 seq 195350 scn 9513178971090 found to restore
RMAN-06025: no backup of log thread 1 seq 195349 scn 9513178926221 found to restore
RMAN-06025: no backup of log thread 1 seq 195348 scn 9513178923827 found to restore
RMAN-06025: no backup of log thread 1 seq 195347 scn 9513178921875 found to restore
RMAN-06025: no backup of log thread 1 seq 195346 scn 9513178920145 found to restore
RMAN-06025: no backup of log thread 1 seq 195345 scn 9513178841667 found to restore
RMAN-06025: no backup of log thread 1 seq 195344 scn 9513178838073 found to restore
RMAN-06025: no backup of log thread 1 seq 195343 scn 9513178835907 found to restore
RMAN-06025: no backup of log thread 1 seq 195342 scn 9513178834071 found to restore
RMAN-06025: no backup of log thread 1 seq 195341 scn 9513178832365 found to restore
RMAN-06025: no backup of log thread 1 seq 195340 scn 9513178793681 found to restore
RMAN-06025: no backup of log thread 1 seq 195339 scn 9513178790355 found to restore
RMAN-06025: no backup of log thread 1 seq 195338 scn 9513178788305 found to restore
RMAN-06025: no backup of log thread 1 seq 195337 scn 9513178786372 found to restore
RMAN-06025: no backup of log thread 1 seq 195336 scn 9513178780586 found to restore
RMAN-06025: no backup of log thread 1 seq 195335 scn 9513178740495 found to restore
RMAN-06025: no backup of log thread 1 seq 195334 scn 9513178737628 found to restore
RMAN-06025: no backup of log thread 1 seq 195333 scn 9513178735681 found to restore
RMAN-06025: no backup of log thread 1 seq 195332 scn 9513178733922 found to restore
RMAN-06025: no backup of log thread 1 seq 195331 scn 9513178730090 found to restore
RMAN-06025: no backup of log thread 1 seq 195330 scn 9513178670788 found to restore
RMAN-06025: no backup of log thread 1 seq 195329 scn 9513178668403 found to restore
RMAN-06025: no backup of log thread 1 seq 195328 scn 9513178666438 found to restore
RMAN-06025: no backup of log thread 1 seq 195327 scn 9513178664711 found to restore
RMAN-06025: no backup of log thread 1 seq 195326 scn 9513178627155 found to restore
RMAN-06025: no backup of log thread 1 seq 195325 scn 9513178623613 found to restore
RMAN-06025: no backup of log thread 1 seq 195324 scn 9513178621484 found to restore
RMAN-06025: no backup of log thread 1 seq 195323 scn 9513178619620 found to restore
RMAN-06025: no backup of log thread 1 seq 195322 scn 9513178617849 found to restore
RMAN-06025: no backup of log thread 1 seq 195321 scn 9513178572577 found to restore
RMAN-06025: no backup of log thread 1 seq 195320 scn 9513178569205 found to restore
RMAN-06025: no backup of log thread 1 seq 195319 scn 9513178567200 found to restore
RMAN-06025: no backup of log thread 1 seq 195318 scn 9513178565271 found to restore
RMAN-06025: no backup of log thread 1 seq 195317 scn 9513178553945 found to restore
RMAN-06025: no backup of log thread 1 seq 195316 scn 9513178545850 found to restore
RMAN-06025: no backup of log thread 1 seq 195315 scn 9513178506636 found to restore
RMAN-06025: no backup of log thread 1 seq 195314 scn 9513178504655 found to restore
RMAN-06025: no backup of log thread 1 seq 195313 scn 9513178502956 found to restore
RMAN-06025: no backup of log thread 1 seq 195312 scn 9513178499499 found to restore
RMAN-06025: no backup of log thread 1 seq 195311 scn 9513178462055 found to restore
RMAN-06025: no backup of log thread 1 seq 195310 scn 9513178459671 found to restore
RMAN-06025: no backup of log thread 1 seq 195309 scn 9513178457766 found to restore
RMAN-06025: no backup of log thread 1 seq 195308 scn 9513178455989 found to restore
RMAN-06025: no backup of log thread 1 seq 195307 scn 9513178437688 found to restore
RMAN-06025: no backup of log thread 1 seq 195306 scn 9513178434194 found to restore
RMAN-06025: no backup of log thread 1 seq 195305 scn 9513178408127 found to restore
RMAN-06025: no backup of log thread 1 seq 195304 scn 9513178406180 found to restore
RMAN-06025: no backup of log thread 1 seq 195303 scn 9513178404599 found to restore
RMAN-06025: no backup of log thread 1 seq 195302 scn 9513178357609 found to restore
RMAN-06025: no backup of log thread 1 seq 195301 scn 9513178354332 found to restore
RMAN-06025: no backup of log thread 1 seq 195300 scn 9513178352262 found to restore
RMAN-06025: no backup of log thread 1 seq 195299 scn 9513178350260 found to restore
RMAN-06025: no backup of log thread 1 seq 195298 scn 9513178345591 found to restore
MAN-06025: no backup of log thre
RMAN> exit
恢复自动停止，数据库打不开。发现datafile异常
select file#,status
from v$datafile;
1 SYSTEM
2 ONLINE
3 ONLINE
4 ONLINE
5 ONLINE
6 ONLINE
7 ONLINE
8 ONLINE
9 ONLINE
10 ONLINE
11 ONLINE
12 ONLINE
13 ONLINE
14 SYSTEM
15 ONLINE
16 ONLINE
17 ONLINE
18 ONLINE
19 ONLINE
20 ONLINE
21 ONLINE
22 ONLINE
23 ONLINE
24 ONLINE
25 ONLINE
26 ONLINE
27 ONLINE
28 ONLINE
29 ONLINE
30 ONLINE
31 ONLINE
32 ONLINE
33 ONLINE
34 ONLINE
35 ONLINE
36      OFFLINE
37 ONLINE
四、修改了pfile两个参数开始恢复：
*._allow_terminal_recovery_corruption=true
*._allow_resetlogs_corruption= TRUE
 
SQL> recover database using backup controlfile;
ORA-00279: change 9513219033290 generated at 07/23/2012 04:00:51 needed for
thread 1
ORA-00289: suggestion : /u01/arch01/1_195369.dbf
ORA-00280: change 9513219033290 for thread 1 is in sequence #195369

Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log '/u01/arch01/1_195369.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3

ORA-00308: cannot open archived log '/u01/arch01/1_195369.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3

SQL> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
[oracle@new0 backup]$ cd /u01/arch01
[oracle@new0 arch01]$ ls
[oracle@new0 arch01]$ rman
Recovery Manager: Release 9.2.0.6.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.
RMAN> connect target /
connected to target database: ITOWN01M (DBID=2826132969)

RMAN> restore archivelog from sequence 195369 until sequence 195374;
Starting restore at 31-JUL-12
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=195369
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=195370
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=195371
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=195372
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=195373
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=195374
channel ORA_DISK_1: restored backup piece 1
piece handle=/opt/oracle/backup/itown01_20120723_9909_1.arc tag=TAG20120723T050953 params=NULL
channel ORA_DISK_1: restore complete
Finished restore at 31-JUL-12
RMAN> exit

Recovery Manager complete.
[oracle@new0 arch01]$ ls
1_195369.dbf  1_195370.dbf  1_195371.dbf  1_195372.dbf  1_195373.dbf  1_195374.dbf
[oracle@new0 arch01]$ sqlplus /nolog
SQL*Plus: Release 9.2.0.6.0 - Production on Tue Jul 31 11:15:28 2012
Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
SQL> connect / as sysdba
Connected.
SQL> recover database using backup controlfile;
ORA-00279: change 9513219033290 generated at 07/23/2012 04:00:51 needed for
thread 1
ORA-00289: suggestion : /u01/arch01/1_195369.dbf
ORA-00280: change 9513219033290 for thread 1 is in sequence #195369

Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 9513245274971 generated at 07/23/2012 05:06:51 needed for
thread 1
ORA-00289: suggestion : /u01/arch01/1_195370.dbf
ORA-00280: change 9513245274971 for thread 1 is in sequence #195370
ORA-00278: log file '/u01/arch01/1_195369.dbf' no longer needed for this
recovery

ORA-00279: change 9513245275649 generated at 07/23/2012 05:09:45 needed for
thread 1
ORA-00289: suggestion : /u01/arch01/1_195371.dbf
ORA-00280: change 9513245275649 for thread 1 is in sequence #195371
ORA-00278: log file '/u01/arch01/1_195370.dbf' no longer needed for this
recovery

ORA-00279: change 9513245275711 generated at 07/23/2012 05:09:50 needed for
thread 1
ORA-00289: suggestion : /u01/arch01/1_195372.dbf
ORA-00280: change 9513245275711 for thread 1 is in sequence #195372
ORA-00278: log file '/u01/arch01/1_195371.dbf' no longer needed for this
recovery

ORA-00279: change 9513245275714 generated at 07/23/2012 05:09:51 needed for
thread 1
ORA-00289: suggestion : /u01/arch01/1_195373.dbf
ORA-00280: change 9513245275714 for thread 1 is in sequence #195373
ORA-00278: log file '/u01/arch01/1_195372.dbf' no longer needed for this
recovery

ORA-00279: change 9513245275718 generated at 07/23/2012 05:09:52 needed for
thread 1
ORA-00289: suggestion : /u01/arch01/1_195374.dbf
ORA-00280: change 9513245275718 for thread 1 is in sequence #195374
ORA-00278: log file '/u01/arch01/1_195373.dbf' no longer needed for this
recovery

ORA-00279: change 9513245275721 generated at 07/23/2012 05:09:53 needed for
thread 1
ORA-00289: suggestion : /u01/arch01/1_195375.dbf
ORA-00280: change 9513245275721 for thread 1 is in sequence #195375
ORA-00278: log file '/u01/arch01/1_195374.dbf' no longer needed for this
recovery

ORA-00308: cannot open archived log '/u01/arch01/1_195375.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

SQL> alter database open resetlogs;
Database altered.
SQL>
数据库打开了，数据没有丢失。

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

转载于:http://blog.itpub.net/26870952/viewspace-739451/

congjuyan5037
关注
ORA-01110: data file
JIANGJIAN12345的专栏
03-05 5511
测试场insert 操作时报错。 ORA-01110: data file 4: '/home/XXX/data/XXX_01.dbf' 。先查看了下DB状态，是OPEN。DF，看空间大小，也没满。从dba_data_files中找出这个DBF对应的TABLESPACE，去dba_tablespaces中看了下它的状态。为READ ONLY！ 有点慌。。快速查看了所有的表空间哪些是REA
ORA-19909: datafile 1 belongs to an orphan incarnation
cuiruipan6325的博客
06-20 1549
ORA-19909: datafile 1 belongs to an orphan incarnation ORA-01110: data file 1: '+...
“ORA-01110: data file 1: 'F:\oracle\product\10.2.0\oradata\orcl\sysaux01.dbf'"解决方法
热门推荐
RainbowGu
11-22 1万+
解决办法： SQL>recover datafile 'F:\oracle\product\10.2.0\oradata\orcl\SYSAUX01.DBF';
linux下ora 01110,rman备份恢复到异机报ORA-01110 ORA-01180错误
weixin_28685287的博客
05-25 912
[Oracle@server1 ORACLE]$ rman target /Recovery Manager: Release 10.2.0.5.0 - Production on Thu Jul 31 13:51:40 2014Copyright (c) 1982, 2007, Oracle. All rights reserved.connected to target database (...
ORA-01110: data file 12: '/home/oracle/perfstat.dbf'
ckc22471的博客
01-29 309
今天下午在rac节点2做statspack的时候，不小心将perfstat表空间的dbf文件创建到了本地磁盘上，没有放到存储上。用户登录时候报错 SQL> select file_name from dba_dat...
ORA-01110: data file 56
N
08-24 3142
1.事件产生大概是这样，版本9.2.0.1 同事加错文件到UNDO表空间，然后进行删除文件（想通过直接删文件，不想通过常规方法） Thu Aug 23 09:54:26 2012 ALTER DATABASE datafile 'D:\RMDATA\UNDOTBS1\UNDOTBS1_01.DBF' offline DROP Thu Aug 23 09:54:26 2012 OR
oracle进入rman报错,Oracle 11g RMAN 异机恢复报错 RMAN-06172、ORA-07202
weixin_42499444的博客
04-03 1410
Oracle 11g RMAN 异机恢复，恢复参数文件的时候报错。RMAN> startup nomountOracle instance startedTotal System Global Area 17103163392 bytesFixed Size 2245480 bytesVariable Size 2181...
rman 恢复数据报ORA-19573: cannot obtain exclusive enqueue for ...
cqszpx的博客
09-25 497
原来是database 在open下，忘了将datafile offline，造成此低级错误；将数据文件offline 后，重启数据库到mount下，在执行恢复，问题解决！
oracle可以放在文件的第一号,【案例】Oracle报错ORA-01210 datafile header block损坏的修复方法...
weixin_35696075的博客
04-03 772
天萃荷净Oracle研究中心案例分析：运维DBA反映Oracle数据库遇到报错ORA-01210分析原因为数据文件头块损坏块导致，使用BBED修复损坏文件。本站文章除注明转载外，均为本站原创： 转载自love wife & love life —Roger 的Oracle技术博客本文链接地址: Archivelog 模式下，datafile header损坏，如何恢复？客户数据库出现故障，...
RMAN异机恢复遭遇ORA-01547、ORA-01152、ORA-01110错误案例
weixin_34183910的博客
04-03 457
测试环境：     操作系统  ：  Red Hat Enterprise Linux ES release 4 (Nahant Update 4)   VMWARE     数据库     ：  Oracle Database 10g Release 10.2.0.4.0 - Production     简要介绍，一台服务器A位于虚拟机VMWARE上，由于测试需要，在VMWARE上克隆了...
ORA-01110
最新发布
weixin_72431427的博客
08-20 484
检查数据库文件的权限：确保数据库文件的权限设置正确，并且数据库用户具有对这些文件的读取和写入权限。检查数据库文件的完整性：使用Oracle的恢复工具或备份工具来检查数据库文件的完整性。如果某个数据库文件的状态为"RECOVER"，那么可能是数据库文件损坏或不可用。在这种情况下，你可以尝试恢复数据库文件或替换损坏的文件。检查数据库文件路径的正确性：确保数据库文件的路径在Oracle数据库配置中正确配置。检查数据库文件的可用性：首先，确保数据库文件存在于正确的位置并且可用。
OracleRMAN备份与恢复之六：数据文件异常修复[ORA-01157、ORA-01578、ORA-01110]
Eric.zhong
08-27 808
[AlertLog日志] ORA-01157: 无法标识/锁定数据文件 4 - 请参阅 DBWR 跟踪文件 ORA-01110: 数据文件 4: ‘D:\ORADATA\ORCL\USERS01.DBF’ ORA-01157: 无法标识/锁定数据文件 2 - 请参阅 DBWR 跟踪文件 ORA-01110: 数据文件 2: ‘D:\ORADATA\ORCL\SYSAUX01.DBF’ [处理方法]...
oracle无法识别锁定数据文件,ORA-01157、ORA-01110无法识别/锁定数据文件
weixin_33622555的博客
04-14 1207
之前在生产中遇到同样报错，用户在客户端查询表中数据，报如下错误：Errors in file /oratrace/xxx/diag/rdbms/xxx/xxx2/trace/xxx2_dbw0_8454382.trc:ORA-01157: cannot identify/lock data file 366 - see DBWR trace fileORA-01110: data file 366...
oracle 15124,ORA-01124: cannot recover data file 1 - file is in use or recovery
weixin_34763128的博客
04-14 1088
Dear allI have refresh quality server with production serevr , database started , but plroblem shows in sm21:00:15 DIA 004 000 SAPSYS BY0 > ORA-00376: file 411 cannot be read at this ti:00:15 DIA 0...
oracle无法进入system,ora-01113 ora-01110 system01.dbf无法打开数据库
weixin_39737947的博客
04-03 1055
今天一企业生产数据库系统出现问题，同事求助，windows平台，oracle版本8.1.7.0.0.，非归档模式，没有任何有效的备份，系统已经运行了几年，比较气愤这种情况，备份怎么强调也有人不执行啊！首先在os层面备份oradata文件夹及参数文件、口令文件，然后开始进行处理。先清除非当前日志文件：alter database clear unarchived logfile group 1；al...
oracle报错01110,Oracle 12c DG备库Alert报错ORA-01110
weixin_34632251的博客
04-09 529
环境是12.2.0.1 version, Oracle Data Guard备库今天故障恢复了一下，RMAN恢复后发现备库Alert一直报错，但是备库主库同步一致，数据一致。2018-07-05T23:42:22.184048+08:00Errors in file /u01/app/oracle/diag/rdbms/dwjrstdydb/dwjrstdydb/trace/dwjrstdydb_...
system01.dbf文件被offline,导致数据库报ORA-01245 ORA-01110故障恢复----惜分飞
weixin_34326429的博客
12-09 2219
转载：system01.dbf文件被offline,导致数据库报ORA-01245 ORA-01110故障恢复 有朋友找到我,说数据库做recover报ORA-01245和ORA-01110错误,无法继续恢复,请求支持 SQL> recover database using backup controlfile until cancel;...
help!ORACLE RMAN恢复问题ORA-01152 ORA-01110
爱肯的专栏
01-07 1733
异机恢复过程：在rman>run{allocate channel ch00 type sbt_tape parms="ENV=(NB_ORA_CLIENT=zjddms1)";set newname for datafile 1 to /oradata/zjdms/1.dbf;......set newname for datafile 23 to /oradata/test/23.d
oracle 更改system.dbf,oracle数据文件system01.dbf上有坏块，如何修复
weixin_30728435的博客
04-10 616
本帖最后由 eavin_wang 于 2013-9-27 14:35 编辑问题：数据库被一同事shutdown abort后，无法启动，报错如下：ksedmp: internal or fatal errorORA-00600: internal error code, arguments: [4193], [3422], [3470], [], [], [], [], []Current SQL...
Oracle数据文件损坏修复：使用RMAN备份解决ORA-01578错误
3. **验证修复**：完成恢复后，为了确保数据文件没有其他损坏的块，我们需要运行`RMAN> backup validate datafile 3;`来验证数据文件的完整性。这一步会检查数据文件并报告任何未解决的问题。 在给出的日志中，我们...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值