在对dsc集群执行restore database命令时，出现[-4558]:文件已存在-CSDN博客

本文链接：https://blog.csdn.net/weixin_42447367/article/details/110434338

博客记录了数据库还原恢复操作中遇到的问题及解决办法。执行还原命令时出现文件已存在的报错，通过查看日志找到报错文件，进入dmamtool工具删除该文件后，重新执行还原恢复操作，最终成功完成数据库的还原和恢复。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

RMAN> restore database ‘/home/dmdba/data2/dsc1_config/dm.ini’ from backupset ‘/home/dmdba/back_db/’;
restore database ‘/home/dmdba/data2/dsc1_config/dm.ini’ from backupset ‘/home/dmdba/back_db/’;
[Percent:0.00%][Speed:0.00M/s][Cost:00:00:00][Remaining:00:00:00]
[-4558]:文件已存在
解决过程：
查看安装数据库的log目录下的BAKERS日志
[dmdba@localhost log]$ vi dm_BAKRES_202011.log
找到报错的log信息处
在这里插入图片描述

报错码[-4558]提示文件已存在，是指那个的文件+DMDATA1/data/dsc/user01.dbf存在，而+DMDATA1/data/dsc/user01.dbf文件是我将+DMDATA/data/dsc/user01.dbf复制到该路径下的，所以我将+DMDATA1/data/dsc/user01.dbf文件删除。
进入dmamtool工具，删除user01.dbf文件
[dmdba@localhost bin]$ ./dmasmtool dcr_ini=/home/dmdba/data/dmdcr.ini
ASM>cd +DMDATA/data/dsc
ASM>rm -f user01.dbf
再重新执行还原恢复
RMAN> restore database ‘/home/dmdba/data/dsc1_config/dm.ini’ from backupset ‘/opt/back_lianji2’;
restore database ‘/home/dmdba/data/dsc1_config/dm.ini’ from backupset ‘/opt/back_lianji2’;
[Percent:100.00%][Speed:0.00M/s][Cost:00:00:05][Remaining:00:00:00]
restore successfully.
time used: 00:00:11.270
RMAN> recover database ‘/home/dmdba/data/dsc1_config/dm.ini’ with archivedir ‘+DMLOG1/arch2’,’/opt/dms0_remote_2’;
recover database ‘/home/dmdba/data/dsc1_config/dm.ini’ with archivedir ‘+DMLOG1/arch2’ , ‘/opt/dms0_remote_2’;
Database mode = 0, oguid = 0
EP[1]'s cur_lsn[44992]
EP[0]'s cur_lsn[44992]
EP[1] adjust cur_lsn from [44992] to [44992]
EP:0 total 1 pkgs applied, percent: 50%
EP:0 total 2 pkgs applied, percent: 100%
EP:1 total 1 pkgs applied, percent: 20%
EP:1 total 2 pkgs applied, percent: 40%
EP:1 total 3 pkgs applied, percent: 60%
EP:1 total 4 pkgs applied, percent: 80%
EP:1 total 5 pkgs applied, percent: 100%
recover successfully!
time used: 00:00:07.016
RMAN> recover database ‘/home/dmdba/data/dsc1_config/dm.ini’ update DB_MAGIC;
recover database ‘/home/dmdba/data/dsc1_config/dm.ini’ update DB_MAGIC;
Database mode = 0, oguid = 0
EP[1]'s cur_lsn[45001]
EP[0]'s cur_lsn[45001]
EP[1] adjust cur_lsn from [45001] to [45001]
recover successfully!