Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

RMAN dupilcate gives RMAN-06004: RMAN-20003

MarGurDec 31 2016 — edited Jan 9 2017

Hello all,

Happy New Years.

Please, help me to resolve an issue:

I am cloning PROD (registered in it's own prod catalog) to BUILD (registered in dev catalog) Catalog reads backups from tdpo.opt file, that has all the info about backups of PROD.

I am issuing the following:

[oracle@bla build_refresh]$ rman auxiliary=/ catalog=ngss/ngssrcat@rcatprod <- production catalog, no banbld registered

RMAN> run

2> {

3> duplicate database banprod DBID 825770406 to banbld

4> until time "TO_DATE('12/25/2016 00:00:00', 'MM/DD/YYYY HH24:MI:SS')";

5> }

<...бла-бла-бла, ристор произошел, но потом..>

Oracle instance started

Total System Global Area  5368709120 bytes

Fixed Size   2935712 bytes

Variable Size   3036677216 bytes

Database Buffers  2315255808 bytes

Redo Buffers  13840384 bytes

contents of Memory Script:

{

   sql clone "alter system set db_name =

''BANBLD'' comment=

''Reset to original value by RMAN'' scope=spfile";

   sql clone "alter system reset db_unique_name scope=spfile";

  shutdown clone immediate;

}

executing Memory Script

sql statement: alter system set  db_name =  ''BANBLD'' comment= ''Reset to original value by RMAN'' scope=spfile

sql statement: alter system reset db_unique_name scope=spfile

Oracle instance shut down

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of Duplicate Db command at 12/31/2016 04:03:55

RMAN-05501: aborting duplication of target database

RMAN-03015: error occurred in stored script Memory Script

RMAN-06004: ORACLE error from recovery catalog database: RMAN-20003: target database incarnation not found in recovery catalog

I can understand, banbld is not registered in prod catalog.... But what to do? I tried to backup control file to trace on PROD and then copied it to BUILD and did:

CREATE CONTROLFILE set DATABASE "banbld" RESETLOG

but of course, because the DB was cloned up to Decemeber 25, the control file taken from PROD is much older....

sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Sat Dec 31 05:08:27 2016

Copyright (c) 1982, 2014, OracleAll rights reserved.

Connected to an idle instance.

SQL> @ccf

ORACLE instance started.

Total System Global Area 5368709120 bytes

Fixed Size   2935712 bytes

Variable Size   3036677216 bytes

Database Buffers  2315255808 bytes

Redo Buffers  13840384 bytes

Control file created.

ALTER DATABASE OPEN RESETLOGS

*

ERROR at line 1:

ORA-01152: file 1 was not restored from a sufficiently old backup

ORA-01110: data file 1: '/o003/home/oracle/data/banbld/system01.dbf'

I tried NID, but of course I cannot startup mount the DB, because of:

SQL> startup

ORACLE instance started.

Total System Global Area 5368709120 bytes

Fixed Size   2935712 bytes

Variable Size   3036677216 bytes

Database Buffers  2315255808 bytes

Redo Buffers  13840384 bytes

ORA-01103: database name 'BANPROD' in control file is not 'BANBLD'

Guys, please, help sister out! I am at my wits here, really behind on this project and clone needs to be completed YESTERDAY. I know it's holidays and all, but hoping somebody can still help

Happy New Years, fellow DBAs. May 2017 be more kind

Thank you in advance,

M

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Feb 6 2017
Added on Dec 31 2016
13 comments
3,081 views