Re: ORA-01103 when creating physical standby
- From: David Barbour <david.barbour1@xxxxxxxxx>
- To: litanli@xxxxxxxxx
- Date: Fri, 6 Feb 2009 16:25:59 -0500
At the risk of being either totally wrong or half wrong again, did you mix
up the desigantions of the 'target' and 'auxiliary' in the script? Couple
of other things come to mind. If you're using 10g, make sure the db_name
parameter is identical in the standby init file, the db_unique_name is the
instance ID of your standby. Make sure you've deleted any previous
controlfiles from the control_files locations in the init file.
On Fri, Feb 6, 2009 at 4:09 PM, Li Li <litanli@xxxxxxxxx> wrote:
> Hi, List,
>
> I am following this white paper
>
> http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimaryRACPhysicalStandby.pdf
> to create a physical standby, at TASK 3: step 9, when I was trying to
> 'DUPLICATE TARGET DATABASE FOR STANDBY', I ran into this ORA-01103
> error. The standby control file was backed up from the primary
> database in RMAN by 'backup current controlfile for standby'. Any idea
> what caused this error? Any suggestion would be greatly appreciated!
>
> sql statement: alter database mount standby database
> RMAN-00571: ===========================================================
> RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
> RMAN-00571: ===========================================================
> RMAN-03002: failure of Duplicate Db command at 02/06/2009 15:58:43
> RMAN-03015: error occurred in stored script Memory Script
> RMAN-03009: failure of sql command on clone_default channel at
> 02/06/2009 15:58:43
> RMAN-11003: failure during parse/execution of SQL statement: alter
> database mount standby database
> ORA-01103: database name 'xxxxxx' in control file is not 'yyyyyyyy'
>
> Thanks,
> -Li
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
Other related posts:
