ORA-19697: standby control file not found in backup set
FranklinFaces.com
FranklinFaces.com - Oracle & SQL Server Database Forums for all IT Professionals
 Home          Members     Calendar     Who's On

Welcome Guest ( Login | Register )
        



ORA-19697: standby control file not found in... Expand / Collapse
Message
Posted 1/19/2011 4:23:40 PM Post #517
 

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being
ORA-19697: standby control file not found in backup set

We are getting the following error when duplicating database in oracle 11gR2  .  This is on redhat linux 5 enterprise.    Everything from PROD matches this of DEV.  We've done this many times and for some reason this time around we got this message. We can't connect to PROD because it's production so can't open RMAN session to PROD.  Also we are not using RMAN Catalog.

Strange. Very strange this ora error.   We have level 0 backup in /oradump/level0/01012011  that was taken from PROD.   All contents from this was scp'ed over to the development server and put in the same local mount point /oradump/level0/01012011

When we issued the following command as rman, it gave us the following error message:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/01/2011 11:37:14
RMAN-03015: error occurred in stored script Memory Script
ORA-19697: standby control file not found in backup set

Here is our script:

run {
allocate auxiliary channel ch1 type disk;
allocate auxiliary channel ch2 type disk;
allocate auxiliary channel ch3 type disk;
allocate auxiliary channel ch4 type disk;
allocate auxiliary channel ch5 type disk;
allocate auxiliary channel ch6 type disk;
allocate auxiliary channel ch7 type disk;
allocate auxiliary channel ch8 type disk;
duplicate database to DEV
until time "to_date('01/01/2011 11:29:37','MM/DD/YYYY HH24:MI:SS')"
BACKUP LOCATION '/oradump/level0/01012011'
nofilenamecheck
skip tablespace history_data
undo tablespace undotbs01;
}

We tried everything and can't seem to figure out why it's looking for standby control file.  This is not a standby database and neither the production server.

Posted 1/19/2011 4:28:29 PM Post #518
 

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/01/2011 11:37:14
RMAN-03015: error occurred in stored script Memory Script
ORA-19697: standby control file not found in backup set

Here is complete output that we followed and we got the error:

#sqlplus '/ as sysdba'

SQL*Plus: Release 11.2.0.1.0 Production on Tue Jan 01 11:36:30 2011

Copyright (c) 1982, 2009, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> shutdown immediate;
ORA-01109: database not open


Database dismounted.
ORACLE instance shut down.
SQL> startup nomount;
ORACLE instance started.

Total System Global Area 2.1379E+10 bytes
Fixed Size                  2213136 bytes
Variable Size            7247760112 bytes
Database Buffers         1.3959E+10 bytes
Redo Buffers              170340352 bytes
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

#rman auxiliary sys/xxxxxx

Recovery Manager: Release 11.2.0.1.0 - Production on Tue Jan 01 11:36:46 2011

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

connected to auxiliary database: PROD (not mounted)

RMAN> run {
allocate auxiliary channel ch1 type disk;
allocate auxiliary channel ch2 type disk;
allocate auxiliary channel ch3 type disk;
allocate auxiliary channel ch4 type disk;
allocate auxiliary channel ch5 type disk;
allocate auxiliary channel ch6 type disk;
allocate auxiliary channel ch7 type disk;
allocate auxiliary channel ch8 type disk;
duplicate database to DEV
until time "to_date('01/01/2011 11:00:37','MM/DD/YYYY HH24:MI:SS')"
BACKUP LOCATION '/oradump/level0/01012011'
nofilenamecheck
skip tablespace history_data
undo tablespace undotbs01;
}

#rman auxiliary sys/xxxxx

Recovery Manager: Release 11.2.0.1.0 - Production on Tue Jan 01 11:36:46 2011

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

connected to auxiliary database: PROD (not mounted)

RMAN> run {
allocate auxiliary channel ch1 type disk;
2> 3> allocate auxiliary channel ch2 type disk;
allocate auxiliary channel ch3 type disk;
4> allocate auxiliary channel ch4 type disk;
5> allocate auxiliary channel ch5 type disk;
6> allocate auxiliary channel ch6 type disk;
7> allocate auxiliary channel ch7 type disk;
allocate auxiliary channel ch8 type disk;
8> duplicate database to DEV
9> until time "to_date('01/01/2011 11:20:00','MM/DD/YYYY HH24:MI:SS')"
BACKUP LOCATION '/oradump/level0/01012011'
10> nofilenamecheck
11> skip tablespace history_data
undo tablespace undotbs01;
12> }13> 14> 15> 16>

allocated channel: ch1
channel ch1: SID=2521 device type=DISK

allocated channel: ch2
channel ch2: SID=2647 device type=DISK

allocated channel: ch3
channel ch3: SID=2773 device type=DISK

allocated channel: ch4
channel ch4: SID=2899 device type=DISK

allocated channel: ch5
channel ch5: SID=1 device type=DISK

allocated channel: ch6
channel ch6: SID=127 device type=DISK

allocated channel: ch7
channel ch7: SID=254 device type=DISK

allocated channel: ch8
channel ch8: SID=380 device type=DISK

Starting Duplicate Db at 01/01/11

contents of Memory Script:
{
   sql clone "alter system set  db_name =
 ''PROD'' comment=
 ''Modified by RMAN duplicate'' scope=spfile";
   sql clone "alter system set  db_unique_name =
 ''DEV'' comment=
 ''Modified by RMAN duplicate'' scope=spfile";
   shutdown clone immediate;
   startup clone force nomount
   restore clone primary controlfile from  '/oradump/level0/01012011/h1m8m4k2_1.20110109';
   alter clone database mount;
}
executing Memory Script

sql statement: alter system set  db_name =  ''PROD'' comment= ''Modified by RMAN duplicate'' scope=spfile

sql statement: alter system set  db_unique_name =  ''DEV'' comment= ''Modified by RMAN duplicate'' scope=spfile

Oracle instance shut down

Oracle instance started

Total System Global Area   21378957312 bytes

Fixed Size                     2213136 bytes
Variable Size               7247760112 bytes
Database Buffers           13958643712 bytes
Redo Buffers                 170340352 bytes
allocated channel: ch1
channel ch1: SID=2521 device type=DISK
allocated channel: ch2
channel ch2: SID=2647 device type=DISK
allocated channel: ch3
channel ch3: SID=2773 device type=DISK
allocated channel: ch4
channel ch4: SID=2899 device type=DISK
allocated channel: ch5
channel ch5: SID=1 device type=DISK
allocated channel: ch6
channel ch6: SID=127 device type=DISK
allocated channel: ch7
channel ch7: SID=254 device type=DISK
allocated channel: ch8
channel ch8: SID=380 device type=DISK

Starting restore at 01/01/11

channel ch2: skipped, AUTOBACKUP already found
channel ch3: skipped, AUTOBACKUP already found
channel ch4: skipped, AUTOBACKUP already found
channel ch5: skipped, AUTOBACKUP already found
channel ch6: skipped, AUTOBACKUP already found
channel ch7: skipped, AUTOBACKUP already found
channel ch8: skipped, AUTOBACKUP already found
channel ch1: restoring control file
released channel: ch1
released channel: ch2
released channel: ch3
released channel: ch4
released channel: ch5
released channel: ch6
released channel: ch7
released channel: ch8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/01/2011 11:37:14
RMAN-03015: error occurred in stored script Memory Script
ORA-19697: standby control file not found in backup set

RMAN>

Posted 1/19/2011 4:38:09 PM Post #519
 

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being
This is what we did to resolve the ora error issue: ORA-19697: standby control file not found in backup set

On production server we logged in and issued the following:

STEP 1:

#/u01> rman target /

Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jan 01 12:11:24 2011

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

connected to target database: PROD (DBID=1243636221)

RMAN> backup current controlfile for standby;


Starting backup at 01/01/11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=5153 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including standby control file in backup set
channel ORA_DISK_1: starting piece 1 at 01/19/11
channel ORA_DISK_1: finished piece 1 at 01/19/11
piece handle=/u01/app/oracle/product/11.2.0/dbs/qbm1gi2v_1_1 tag=TAG20110101T121136 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 01/01/11

RMAN>

STEP 2:

Once that finished,  i copied this over to the DEV server in the same exact location as the backup directory:

scp /u01/app/oracle/product/11.2.0/dbs/qbm1gi2v_1_1  DEV:/oradump/level0/01012011/

STEP 3:

Once i copied it there, I logged on to the DEV RMAN and typed in following:


RMAN> restore clone primary controlfile from '/oradump/level0/01012011/qbm1gi2v_1_1';

Starting restore at 01/01/11
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=2521 device type=DISK

channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/oracle/oradata/PROD/control01.ctl
output file name=/oracle/oradata/PROD/control02.ctl
Finished restore at 01/01/11

STEP 4:

Once that completed, I issued the following to do the restore.  PLEASE NOTE THAT WE TOOK OUT THE TIME OPTION.  THIS WAS THE PROBLEM.  FOR SOME REASON ORACLE DIDN'T LIKE THIS TIME.   NOT SURE WHY!  WE USED THIS ALL THE TIME.  We took this line out:  "until time "to_date('01/09/2011 11:30:00','MM/DD/YYYY HH24:MI:SS')""


run {
allocate auxiliary channel ch1 type disk;
allocate auxiliary channel ch2 type disk;
allocate auxiliary channel ch3 type disk;
allocate auxiliary channel ch4 type disk;
allocate auxiliary channel ch5 type disk;
allocate auxiliary channel ch6 type disk;
allocate auxiliary channel ch7 type disk;
allocate auxiliary channel ch8 type disk;
duplicate database to DEV
BACKUP LOCATION '/oradump/level0/01012011/'
nofilenamecheck
skip tablespace history_data
undo tablespace undotbs01;
}

That time thing was weird.



Hope this helps you guys out.

Thanks,

Admin



 

« Prev Topic | Next Topic »


Reading This Topic Expand / Collapse
Active Users: 0 (0 guests, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: silencer

Permissions Expand / Collapse

All times are GMT -5:00, Time now is 7:00pm

Powered By InstantForum.NET v4.1.4 © 2012
Execution: 0.031. 11 queries. Compression Disabled.
Contextual Links