connected to target database: GENDB (not mounted)

本文描述了一位技术专家通过RMAN在Oracle数据库中处理无法连接的节点问题。他们首先从另一个正常运行的DB2节点获取DBID,然后在问题节点DB1上设置相同的DBID并执行挂载操作。经过重新连接和打开数据库的步骤,最终成功挂载并验证了备份设置。

今天通过rman 连接oracle 发现一台节点,提示没有挂载,很是突兀,完成没搞过这破玩意,在网上查了很多资料,让从别一节点上备份,然后在这一台上进行恢复;但是我查了一下备份的内容,这台连不上的上面都有,而且文件也是一致的,所以我直接做了挂载动作

第一步:从DB2 上获取到DBID

[oracle@DB2 ~]$ rman

Recovery Manager: Release 11.2.0.4.0 - Production on Wed Jul 5 18:28:39 2023

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect target /

connected to target database: GENDB (DBID=27951032)

第二步:把DB2上的DBID 设置到DB1上,并进行数据库挂载,并退出

[oracle@DB1 ~]$ rman

Recovery Manager: Release 11.2.0.4.0 - Production on Wed Jul 5 18:27:55 2023

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect target /                     

connected to target database: GENDB (not mounted)

RMAN> set DBID=27951032  //  在好的一台上取DBID

executing command: SET DBID

RMAN> alter database mount;

using target database control file instead of recovery catalog
database mounted

RMAN> exit     

第三步:退出后,重新连接,会提示数据库有打开  not open, 重新打开数据库

[oracle@DB1 ~]$ rman

Recovery Manager: Release 11.2.0.4.0 - Production on Wed Jul 5 18:31:05 2023

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect target /      

connected to target database: GENDB (DBID=27951032, not open)

RMAN> alter database open;

using target database control file instead of recovery catalog
database opened

RMAN> exit

第四步:测试挂载完成, 查询备份设置,一切正常。。。

[oracle@DB1 ~]$ rman

Recovery Manager: Release 11.2.0.4.0 - Production on Wed Jul 5 18:37:39 2023

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect target /

connected to target database: GENDB (DBID=27951032)   完成挂载

RMAN> list backupset;

using target database control file instead of recovery catalog

List of Backup Sets
===================


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
6088    Incr 1  1.50G      DISK        00:09:41     04-JUL-23      
        BP Key: 6088   Status: AVAILABLE  Compressed: NO  Tag: TAG20230704T220004
        Piece Name: /home/oracle/ora_backupset/backupset/20230704/5f20eqn7
  List of Datafiles in backup set 6088
  File LV Type Ckp SCN    Ckp Time  Name

b2b-dg:/home/oracle#rman target sys/oracle@ecps auxiliary sys/oracle@ecpsdg Recovery Manager: Release 11.2.0.4.0 - Production on Fri Oct 24 17:26:34 2025 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: ECPS (DBID=3593407971) connected to auxiliary database: ECPS (not mounted) RMAN> duplicate target database for standby from active database nofilenamecheck; Starting Duplicate Db at 24-OCT-25 using target database control file instead of recovery catalog configuration for DISK channel 2 is ignored allocated channel: ORA_AUX_DISK_1 channel ORA_AUX_DISK_1: SID=350 device type=DISK contents of Memory Script: { backup as copy reuse targetfile '/home/app2/oracle/11.2.0.4/dbs/orapwecps1' auxiliary format '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwecpsdg' ; } executing Memory Script Starting backup at 24-OCT-25 released channel: ORA_AUX_DISK_1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 10/24/2025 17:26:45 RMAN-05501: aborting duplication of target database RMAN-03015: error occurred in stored script Memory Script RMAN-12001: could not open channel ORA_DISK_1 RMAN-10008: could not create channel context RMAN-10003: unable to connect to target database ORA-12154: TNS:could not resolve the connect identifier specified
最新发布
10-25
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

_Fighter

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

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

余额充值