Creating Standby Controlfile

Is it necessary to shutdown the primary database and then mount it to create standby controlfile for both Physical and Logical standby databases?
Or is it alright to create standby controlfile while primary database is open?

You should create standby controlfile while database is in mount mode
Kamran Agayev A. (10g OCP)
http://kamranagayev.wordpress.com
[Step by Step install Oracle on Linux and Automate the installation using Shell Script |http://kamranagayev.wordpress.com/2009/05/01/step-by-step-installing-oracle-database-10g-release-2-on-linux-centos-and-automate-the-installation-using-linux-shell-script/]

Similar Messages

How to create standby controlfile from restored backup

Hi Techies,
I am re-building one of my DR server, Source and target DB is oracle 10g.
I have taken the source backup which is going to be restored on target, But I forgot to take a standby controlfile from source DB at the time (Pre/Post) backup.
Now the issue is I can create a standby controlfile on primary and copy the same to target, But so many datafiles are added after the backup which I have taken to restore and medias are already shipped.
I can send the other set of backup to DR site, but it takes a week time and I don't want to do that If I can regenerate it.
So any clue to create standby controlfile on target with restored datafiles?
Regards,
Nick Loy

Hmm... sounds like you perform this in a rather manual fashion...
Do you use RMAN for taking the backups?
Or maybe the BR*TOOLS?
With these tools you are usually safe from such mistakes - I can only recommend to use them!
However, since you don't have a control file at all on the target side, the only thing left to do would be to
ALTER DATABASE BACKUP CONTROLFILE TO TRACE NORESETLOGS;
on the primary side and manually remove the files that have been added since you took the backup from the control file script,
Afterwards you use the script on the standby side to create the control files.
regards,
Lars

Create standby controlfile

To create a standby controlfile, do I have to be with my database mounted in exclusive, or there is another way to do that without shutdown the database?
Thanks,
Rafael.

dear friend
The production database need not be open in exclusive mode
to create statnd by control file.
Suresh

Create a standby controlfile using cold backup

Hi All,
We have to setup a DR for a production database.
Here we have the coldbackup which backups all the datafiles and the control file from the production database.
For cloining we generally copy them to another instance and then create controlfile manually. But for setting up as a DR , we would be creating it for standby controlfile.
I tried to google but I am not able to find a way to create a standby controlfile from the existing controlfile cold backup.
OS version solaris 10 , database version 11.2.0.1
Regards
KK
Edited by: Kk on Feb 16, 2012 8:51 AM

Kk wrote:
Hi All,
We have to setup a DR for a production database.
Here we have the coldbackup which backups all the datafiles and the control file from the production database.
For cloining we generally copy them to another instance and then create controlfile manually. But for setting up as a DR , we would be creating it for standby controlfile.
I tried to google but I am not able to find a way to create a standby controlfile from the existing controlfile cold backup.
OS version solaris 10 , database version 11.2.0.1
Regards
KK
Edited by: Kk on Feb 16, 2012 8:51 AMTry as below
My version:
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
PL/SQL Release 11.2.0.1.0 - Production
CORE    11.2.0.1.0      Production
TNS for 32-bit Windows: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
SQL>1) Taken backup of current controlfile
2) Deleted Current controlfiles
3) Restored using standby clause from current controlfile
4) Mounted & now controlfile type is Standby
Try in this way when you have cold backup. :)
SQL> select controlfile_type from v$database;
CONTROL
CURRENT
RMAN> run
2> {
3> allocate channel ch1 device type disk format 'c:\oracle\control%U.bkp';
4> backup current controlfile;
5> release channel ch1;
6> }
using target database control file instead of recovery catalog
allocated channel: ch1
channel ch1: SID=63 device type=DISK
Starting backup at 16-FEB-12
channel ch1: starting full datafile backup set
channel ch1: specifying datafile(s) in backup set
including current control file in backup set
channel ch1: starting piece 1 at 16-FEB-12
channel ch1: finished piece 1 at 16-FEB-12
piece handle=C:\ORACLE\CONTROL08N3GEA6_1_1.BKP tag=TAG20120216T230334 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:01
Finished backup at 16-FEB-12
released channel: ch1
RMAN> exit
RMAN> restore standby controlfile from 'C:\ORACLE\CONTROL08N3GEA6_1_1.BKP';
Starting restore at 16-FEB-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=66 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output file name=C:\ORACLE\ORADATA\ORCL\CONTROL01.CTL
output file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\CONTROL02.CTL
Finished restore at 16-FEB-12
SQL> alter database mount;
Database altered.
SQL> select controlfile_type from v$database;
CONTROL
STANDBY
SQL>
Some More information:-
Even if your database backup is old, still you can create a new standby controlfile and restore new controlfile and restore database. Later after starting MRP all will be synchronized. No issues
SQL> select controlfile_type from v$database;
CONTROL
CURRENT
SQL> alter database create standby controlfile as 'c:\oracle\control_stby.ctl';
Database altered.
SQL> $dir c:\oracle\con*
Volume in drive C is System
Volume Serial Number is 1853-3E21
Directory of c:\oracle
02/16/2012 11:41 PM         9,748,480 CONTROL_STBY.CTL
               1 File(s)     19,546,112 bytes
               0 Dir(s) 177,185,570,816 bytes free
SQL>Now Just restore database. You already have backup.
Or
If you have opportunity you can go ahead for Duplicate/Duplicate from active database
Edited by: CKPT on Feb 16, 2012 11:41 PM

Can standby controlfile be created after backup

can we take the online backup of primary database first and then create standby controlfile.will it be useful.
as i have yesterday backup..now can i create standby controlfile now and configure data guard by restoring that backup.
Regards

Hi,
user11221081 wrote:
can we take the online backup of primary database first and then create standby controlfile.will it be useful.
as i have yesterday backup..now can i create standby controlfile now and configure data guard by restoring that backup.
Regards
Yes, we can create standby control file, after backup.
What is your database version?
If you are using 11g version, then you can RMAN DUPLICATE command FROM ACTIVE DATABASE option.
This duplication is not backup-based duplication.
Regards
Mahir M. Quluzade

Problem when create standby database

hello,
I have two server(NT4.0,SP6) installed Oracle 8i(8.1.6 Enterprise) at the same directory.I want one as the primary database,another one as the standby database.
The two database have the same SID,use SQL*Plus it can access each other.
My operating steps as below:
1.on primary server:
1)connect internal;
2)shutdown immediate;
3)copy all datafiles(*.DBF) to a backup directory;
4)startup
5)alter database create standby controlfile as 'd:\oracle\ora81\ILLDB\standby.ctl'
6)alter system archive log current
2.on standby server:
1)copy all backuped datafile,standby.ctl,all redo log files from primary server to standby server,overwrite all same name files;
2)modify the init.ora,add this parameter:
"standby_archive_dest = "location=D:\Oracle\oradata\ILLDB\archive" ";
3)statup oracle service in Service control manel;
4)run svrmgrl.exe;
5)startup nomount;
6)alter database mount standby database;
then a error message appear:
"ORA-01665 controlfile is not a standby controlfile".
I don't know which step is mistake.Please tell me correct steps.
Thanks

I did face the similar problem while trying to create and startup a clone database for Point in Time Recovery (PITR). The error message is
ORA-01696 controlfile is not a clone controlfile
Are you folks have any idea how do I resolve this problem?? Is there any way to create clone control file??

Creating Standby database with Oracle 10gR2 SE (no dataguard). Procedure

Hello,
I have problems in creating a standby database without Dataguard (Oracle Standard Edition)
-Oracle 10gR2 SE (No DataGuard !!!!)
- SUSE Enterprise 10.
Both primary and standby databases are running in Virtual machines (lab).
I will describe the exact steps I followed :
1.---------------------------------------------------
Both primary and standby databases have exactly the same file / folder structure
2.---------------------------------------------------
I enabled archive log mode with a new destination : /opt/oracle/oradata/orcl/archive_logs.
Also : SQL> alter database force logging;
3.---------------------------------------------------
I shut down the primary database (shutdown immediate)
4.---------------------------------------------------
I created a standby controlfile on the primary database:
SQL> startup mount
SQL> alter database create standby controlfile as '/tmp/standby.ctl'
SQL> shutdown immediate
5.---------------------------------------------------
I did a cold backup from the primary db to the standby db
(I copied all the db files, control files, redo log)
6.---------------------------------------------------
I copied from the primary db to the standby db the standby control file
(from primary /tmp/standby.ctl)
7.---------------------------------------------------
I copied from the primary db to the standby db the standby control file
(from primary /tmp/standby.ctl)
8.---------------------------------------------------
I created on the standby database a pfile from the spfile :
SQL> create pfile from spfile;
9.---------------------------------------------------
I edited the pfile and changed the controlfile location (with the standby controlfile created in step 4)
>>>>> *.control_files='/opt/oracle/oradata/orcl/standby.ctl'
10.--------------------------------------------------
I started the standby db
SQL> startup mount pfile='/opt/oracle/product/10.2/db_1/dbs/initorcl.ora'
SQL> alter database recover managed standby database disconnect from session;
SQL> quit
11.--------------------------------------------------
I made some changes on the primary db on user scott
SQL> update table set .......
12.--------------------------------------------------
I switched logfile on the primary db
SQL> alter system switch logfile;
13.--------------------------------------------------
I manually copied the new archivelog to the standby db
And then nothing !!!
The db changes are not applied.
Please help me fix the procedure !!!
Thanks

Hi
Ref to your Oracle SE Standby issue, we were in similar situation couple of years ago to build an Automated Standby for our disaster recovery on Oracle SE. We finally got a solution provider Anbul Technologies , they have a one of their solutions based on Oracle SE which provided fully automated Standby in Oracle SE.
We are successfully running that solution in our prod env for many years. You can visit their site www.anbultechnologies.co.uk or contact them for further details. They are Uk based but provides support and services all over Europe.
Cheers

Mounting a standby database with an older standby controlfile (Manual)

Hi,
We recently created a standby database and mounted it with a standby controlfile that was at least 1 month older than than the datafiles. The database was not taken out of recovery mode or opened. When we attempted to recovery the database using the older standby control file, it requested an archival log that was much older than SCN for the datafiles.
My question is: Is it possible to create a new standby controlfile (CREATE STANDBY CONTROLFILE TO <file>) from the production live system and put the standby database back into recovery mode to apply newer/recent archivelogs? Or essentially has anything been corrupted?
The database is 10.2.0.4 on Sun Solaris. Also, the this is manual standby, not automatic (RMAN).
Thanks in advance.

user6676819 wrote:
Hi,
We recently created a standby database and mounted it with a standby controlfile that was at least 1 month older than than the datafiles. The database was not taken out of recovery mode or opened. When we attempted to recovery the database using the older standby control file, it requested an archival log that was much older than SCN for the datafiles.
My question is: Is it possible to create a new standby controlfile (CREATE STANDBY CONTROLFILE TO <file>) from the production live system and put the standby database back into recovery mode to apply newer/recent archivelogs? Or essentially has anything been corrupted?Hi.That is not possible.In your case best way is getting incremental backup from primary database and apply that into standby database then place stanby database in recover mode.To doing this see below thread.
Re: archive log missing for standby

Standby controlfile in 11.2

Dear all,
am in the process of configuring rac physical standby for 11.2 rac one node . Am following the
guide "download.oracle.com/docs/cd/E18283_01/server.112/e17022.pdf" . There is to mentioned
to create standby controlfiles in the primary location and nothing more is mentioned there.
(Probably I missed to understand this :)
In our primary database , we have 3 control files in a single location like
e:\oradata\control01.ctl,e:\oradata\control02.ctl,e:\oradata\control03.ctl and with standby including e:\oradata\standby0101.ctl .
Now, do I have to copy all the control files from the primary to the standby site and mention (in the pfile of the standby as)
control_files=e:\oradata\standby0101.ctl alone ?. or do I have to mention all the control files
in the control_files parameter ?
Please guide
Kai

do I have to copy all the control files from the primary to the standby siteSurely you know by this time that it is logically 1 controlfile file with 3 physical copies --- this is called "multiplexing".
Any production (even development) database -- whether primary or standby -- should be multiplexing its controlfile.
e17022.pdfInstead of reading the Data Guard Broker documentation you should read the Data Guard Concepts and Administration documentation.
Hemant K Chitale

Standby controlfile

Hi all,
I have created a standby database and is working propertly. I just drop the redo logs and recreated more and larger redo logs in the primary database. I followed the oracle documentation and try to refresh the standby database controlfile so that it reflects this change:
1. shutdown the standby database
2. on the primary datbase:
alter database create standby controlfile as 'filesname'
3. move the control file created in the step 2 to the primary database
4. startup nomount
5. alter database mount standby database.
so far so good, no erros yet. Therefore I try to apply the log:
6. recover standby database until cancel
I hit cancel
and received the following:
SVRMGR> recover standby database until cancel;
ORA-00279: change 95713083 generated at 02/16/2001 12:34:59 needed for thread 1
ORA-00289: suggestion : /logs/ORCL/arch/ORCL_1_492.arc
ORA-00280: change 95713083 for thread 1 is in sequence #492
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/oradata/ORCL/system01.dbf'
Why this happend? Any suggestion?
Thank you very much in advance!
--yc

Oh,
I mean move the standby controlfile to the standby database.
--yc
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Shuet Ying Choi ([email protected]):
Hi all,
I have created a standby database and is working propertly. I just drop the redo logs and recreated more and larger redo logs in the primary database. I followed the oracle documentation and try to refresh the standby database controlfile so that it reflects this change:
1. shutdown the standby database
2. on the primary datbase:
alter database create standby controlfile as 'filesname'
3. move the control file created in the step 2 to the primary database
4. startup nomount
5. alter database mount standby database.
so far so good, no erros yet. Therefore I try to apply the log:
6. recover standby database until cancel
I hit cancel
and received the following:
SVRMGR> recover standby database until cancel;
ORA-00279: change 95713083 generated at 02/16/2001 12:34:59 needed for thread 1
ORA-00289: suggestion : /logs/ORCL/arch/ORCL_1_492.arc
ORA-00280: change 95713083 for thread 1 is in sequence #492
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/oradata/ORCL/system01.dbf'
Why this happend? Any suggestion?
Thank you very much in advance!
--yc<HR></BLOCKQUOTE>
null

Standby controlfiles

I have 2 questions regarding the subject,
1. When we create standby controlfile does this entry gets written into the existing controlfiles, if yes then if i run the create controlfile command again will it be overwriting the entry in existing contriol file?
2. As per below text from documentation, Why do we have to create it only after the backup of datafiles.
The below is from documentation:
A control file needs to be created for the standby system. Execute the following on the primary system:
alter database create standby controlfile as '/some/path/to/a/file'
The created file must meet two conditions:
•Its filename must be different from any other control file
*•Must be created after the backup of the datafiles.*

1. When you execute a CREATE CONTROLFILE, you lose all information about ArchiveLogs, Backups etc that was present in the controlfile. (You need to reregister backups into the controlfile with ALTER SYSTEM REGISTER LOGFILE for ArchiveLogs and CATALOG for all other backups).
Nevertheless, an ALTER DATABASE CREATE STANDBY CONTROLFILE does not appear to register the standby controlfile as a backup of the controlfile.
2. When you need to initiate Recovery or Managed Recovery of the Standby database, it should start with a target SCN higher than the datafile SCNs. A Standby controlfile that is created after the datafile backups, does have a higher SCN than those of the datafiles.
Hemant K Chitale

Standby controlfile SCN ahead of datafile SCN

Hello,
Is there any quick fix to the scenario where the standby side controlfile SCN has gone ahead of the datafile SCN. All the archives are getting shipped to the standby side, but any attempt to start the MRP fails with -
Recovery interrupted!
Standby recovery stopped due to failure in applying recovery marker (opcode 17.4).
Datafiles are recovered to a consistent state at change 12679713219897 but controlfile is ahead at change 12679713219906.
DB (stand-alone): 11.2.0.2
Platform: Sun SPARC
Thanks
aBBy

Is there any quick fix to the scenario where the standby side controlfile SCN has gone ahead of the datafile SCN. All the archives are getting shipped to the standby side, but any attempt to start the MRP fails with -
Recovery interrupted!
Standby recovery stopped due to failure in applying recovery marker (opcode 17.4).
Datafiles are recovered to a consistent state at change 12679713219897 but controlfile is ahead at change 12679713219906.
Are you trying to perform Manual recovery from SQL? like recover standby database?
Even if controlfile is new and datafiles are older, still you should able to perform recovery , But this will be a valid database to open when SCN's are in SYNC.
SO perform recovery automated and then check synchronization.
SQL> alter database recover managed standby database disconnect from session;
Refer alert log file until it waits as " Media recovery waiting for thread# <no> sequence# <>"
Then, check SYNC as follows
Primary:-
SQL> select thread#, max(sequence#) from v$archived_log group by thread#;
Standby:-
SQL> select thread#, max(sequence#) from v$archived_log group by thread#;
SQL> select thread#, max(sequence#) from v$archived_log where applied='YES' group by thread#;
Also you can try option of recreating standby controlfile as below from primary
SQL> alter database create standby controlfile as 'loation';
& restore it in standby database.

How to create primary controlfile from standby controlfile?

We need to create a primary control file from a standby control file.
SQL> select name, controlfile_type from v$database;
NAME CONTROL
HPR STANDBY
Please help.
Thank you very much.

May wrote:
We need to create a primary control file from a standby control file.
SQL> select name, controlfile_type from v$database;
NAME CONTROL
HPR STANDBY
Please help.
Thank you very much.What is a problem?
You can not create controlfile from standby controlfile(Expected activate time).
And you lost controlfile?

Error in creating standby db... need HELP !!!

Hi,
i want to set up a standby db for current production db and i did the following:
1) shutdown the production db;
2) cp $ORACLE_HOME/oradata/testdb/*.dbf(on
production) to the the standby db server;
3) startup the production db;
4) create a standby controlfile on
production;
5) issue "alter system archive log current"
on production server;
6) copy standby controlfile , init file
and archived logs to standby server;
7) config. the init file;
8) on standby server, i did
(i) startup nomount pfile=initstandby.ora
(ii) alter database mount standby database
(iii) recover managed standby database
up to 8 (iii) , the following error occured:
ORA-01152: file 1 was not restored from a
sufficiently old backup
what's going on ???
Can anybody help me ???
Thanks in advance !!!
stephen
null

I also did as you did, but I did not get any error code.
However, the system seems halt after the command of "recover managed standby database;". I checked my standby database log:
Media Recovery Log
Media Recovery Waiting for thread 1 seq# 15
.... log halting here for a long long time (no anyresponse)
Then I try to primary database do the following command:
alter system archive log current;
Then my standby database log have the following response:
Mon Mar 25 16:27:12 2002
Media Recovery Log /oracle/or9i/dbs/arch1_15.dbf
Media Recovery Waiting for thread 1 seq# 16
...... log halting here again
No any output after all. Why? Can anyone tell me?
Shoud the command "recover managed standby database;" have any ending?
And also I tried to use
SQL> recover managed standby database finish;
ORA-16043: sustained recovery session canceled
ORA-16137: No terminal recovery is required
.... Why?

ORA-19505: failed to identify file - RMAN in creating standby DR database.

I got this error when creating standby database at remote target server.
ORA-19505: failed to identify file "/backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01"
Here is what I did:
1.   started the listener and created corresponding tnsnames entry at remote standyb server
2. startup nomount to the standby database at remote server for an empty instance (instance name dxp1p).
3. All rman backups are in the /backup mount point at primary and the mount point is shared on the remote server as nfs.   So, whatever have in the backup we should be able to see and read from the remote as well.
4. Run the following at primary rman:
sql 'alter system archive log current';
backup current controlfile for standby;
sql 'alter system archive log current';
crosscheck backup;
crosscheck archivelog all;
exit
5.   Start the rman command from primary after connected to the standby server, as the primary DB uses ASM and the standby DB uses file system for the database files:
RUN
SET NEWNAME FOR DATAFILE 1 to '/u01/dxp1p/data/system01.dbf';
SET NEWNAME FOR DATAFILE 2 to '/u01/dxp1p/data/sysaux01.dbf';
SET NEWNAME FOR DATAFILE 3 to '/u01/dxp1p/data/undotbs01.dbf';
SET NEWNAME FOR DATAFILE 4 to '/u01/dxp1p/data/users01.dbf';
SET NEWNAME FOR DATAFILE 5 to '/u01/dxp1p/data/fxtntdata.dbf';
SET NEWNAME FOR DATAFILE 6 to '/u01/dxp1p/data/fxtntindex.dbf';
SET NEWNAME FOR DATAFILE 7 to '/u01/dxp1p/data/mlogs.dbf';
SET NEWNAME FOR DATAFILE 8 to '/u01/dxp1p/data/dts.dbf';
SET NEWNAME FOR DATAFILE 9 to '/u01/dxp1p/data/dxpsoa.dbf';
SET NEWNAME FOR DATAFILE 10 to '/u01/dxp1p/data/expresso_ts.dbf';
SET NEWNAME FOR DATAFILE 11 to '/u01/dxp1p/data/jms_ts.dbf';
SET NEWNAME FOR DATAFILE 12 to '/u01/dxp1p/data/uup_ts.dbf';
SET NEWNAME FOR DATAFILE 13 to '/u01/dxp1p/data/newpage_ts.dbf';
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
DUPLICATE TARGET DATABASE for standby
nofilenamecheck
dorecover;
========================================================================
But I got this error from the rman log:
contents of Memory Script:
   set until scn 12245784375453;
   restore clone standby controlfile;
executing Memory Script
executing command: SET until clause
Starting restore at 04-DEC-13
channel aux1: starting datafile backup set restore
channel aux1: restoring control file
channel aux1: reading from backup piece /backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01
channel aux1: ORA-19870: error while restoring backup piece /backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01
ORA-19505: failed to identify file "/backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
failover to previous backup
channel aux1: starting datafile backup set restore
channel aux1: restoring control file
channel aux1: reading from backup piece /backup/dxp1p/online/DXP1P_20131204_833310136_464
channel aux1: ORA-19870: error while restoring backup piece /backup/dxp1p/online/DXP1P_20131204_833310136_464
ORA-19505: failed to identify file "/backup/dxp1p/online/DXP1P_20131204_833310136_464"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
failover to previous backup
channel aux1: starting datafile backup set restore
channel aux1: restoring control file
channel aux1: reading from backup piece /backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-00
channel aux1: ORA-19504: failed to create file "/oracle/product/11g/dbs/u02/dxp1p/control/control02.ctl"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 1
ORA-19600: input file is control file (/u01/dxp1p/control/control01.ctl)
ORA-19601: output file is control file (/oracle/product/11g/dbs/u02/dxp1p/control/control02.ctl)
Finished restore at 04-DEC-13
contents of Memory Script:
   sql clone 'alter database mount standby database';
executing Memory Script
sql statement: alter database mount standby database
released channel: aux1
released channel: aux2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/04/2013 19:06:13
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 12/04/2013 19:06:13
RMAN-11003: failure during parse/execution of SQL statement: alter database mount standby database
ORA-00205: error in identifying control file, check alert log for more info
=========================================
Not sure why, can somebody help?   Appreciated!

I used company regular script to login to standby instance as sys user from primary DB RMAN as oracle OS user and sys DB user.   We normally run this way for years.
Like this:
$ORACLE_HOME/bin/rman target=/ auxiliary 'sys/sys0rapr321!'@dxp1p_s11 CMDFILE=${HOME}/dba/scripts/rman_cr_dr.cmd
rman_cr_dr.cmd:
RUN
SET NEWNAME FOR DATAFILE 1 to '/u01/dxp1p/data/system01.dbf';
SET NEWNAME FOR DATAFILE 2 to '/u01/dxp1p/data/sysaux01.dbf';
SET NEWNAME FOR DATAFILE 3 to '/u01/dxp1p/data/undotbs01.dbf';
SET NEWNAME FOR DATAFILE 4 to '/u01/dxp1p/data/users01.dbf';
SET NEWNAME FOR DATAFILE 5 to '/u01/dxp1p/data/fxtntdata.dbf';
SET NEWNAME FOR DATAFILE 6 to '/u01/dxp1p/data/fxtntindex.dbf';
SET NEWNAME FOR DATAFILE 7 to '/u01/dxp1p/data/mlogs.dbf';
SET NEWNAME FOR DATAFILE 8 to '/u01/dxp1p/data/dts.dbf';
SET NEWNAME FOR DATAFILE 9 to '/u01/dxp1p/data/dxpsoa.dbf';
SET NEWNAME FOR DATAFILE 10 to '/u01/dxp1p/data/expresso_ts.dbf';
SET NEWNAME FOR DATAFILE 11 to '/u01/dxp1p/data/jms_ts.dbf';
SET NEWNAME FOR DATAFILE 12 to '/u01/dxp1p/data/uup_ts.dbf';
SET NEWNAME FOR DATAFILE 13 to '/u01/dxp1p/data/newpage_ts.dbf';
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
DUPLICATE TARGET DATABASE for standby
nofilenamecheck
dorecover;
exit
==========================
Oinstall is a group.   I am not sure to use oinstall as a user?

Creating Standby Controlfile

Similar Messages

Maybe you are looking for