1 Reply Latest reply on Oct 9, 2018 11:40 AM by Joerg.Sobottka

    Duplicate target database failed


      --Strange is the error when connection is successful to target and auxiliary still the duplcate fails with TNS error

      -- Error faced during POC for DG on 12.2


      $ rman target sys/Oracle123@usa auxiliary sys/Oracle123@usastdby1

      Recovery Manager: Release - Production on Fri Sep 28 16:58:20 2018

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

      connected to target database: USA (DBID=1370041883)
      connected to auxiliary database: USA (not mounted)

      RMAN> duplicate target database for standby from active database nofilenamecheck;

      Starting Duplicate Db at 28-SEP-18
      using target database control file instead of recovery catalog
      allocated channel: ORA_AUX_DISK_1
      channel ORA_AUX_DISK_1: SID=35 device type=DISK

      contents of Memory Script:
         backup as copy reuse
         targetfile  '+DATA/USA/PASSWORD/pwdusa.256.985698011' auxiliary format
      '+DATA/usastdby/PASSWORD/orapwusa'   ;
      executing Memory Script

      Starting backup at 28-SEP-18
      allocated channel: ORA_DISK_1
      channel ORA_DISK_1: SID=77 instance=usa2 device type=DISK
      RMAN-00571: ===========================================================
      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
      RMAN-00571: ===========================================================
      RMAN-03002: failure of Duplicate Db command at 09/28/2018 17:02:52
      RMAN-05501: aborting duplication of target database
      RMAN-03015: error occurred in stored script Memory Script
      RMAN-03009: failure of backup command on ORA_DISK_1 channel at 09/28/2018 17:02:52
      ORA-17627: ORA-12154: TNS:could not resolve the connect identifier specified
      ORA-17629: Cannot connect to the remote database server


        • 1. Re: Duplicate target database failed

          This question is NOT Data Guard related and should be moved to the Recovery Manager (RMAN) Thread.


          To answer your question. While cloning, the databases connect vice versa in every direction, so ensure, that you can connect sys@usa and sys@usastby1 from BOTH nodes, so the one that hosts the primary as well as the one that hosts the auxiliary database.