11g Data Guard --ORA-01103: database name 'PRIM' in control file is not 'ST

Dear all,
From no mount stage i am trying to bring the db in mount stage in standby database
SQL> alter database mount standby database;
alter database mount standby database
ERROR at line 1:
ORA-01103: database name 'PRIM' in control file is not 'STANDBY'
What is this problem ?
I have taken standby control from from standby database and places with datafile's and removed the orginal control file. and added this standby.ora file in parameter file also (pfile).
the Primary database name is PRIM and standby database name is STANDBY.
This is my first time doing this data guard configuration kindly let me know what i have to do at this above mentioned stage ..
Regards
Hamid

Standby DB init file
prim.__db_cache_size=536870912
prim.__java_pool_size=8388608
prim.__large_pool_size=8388608
prim.__oracle_base='F:\standby'#ORACLE_BASE set from environment
prim.__pga_aggregate_target=520093696
prim.__sga_target=771751936
prim.__shared_io_pool_size=0
prim.__shared_pool_size=209715200
prim.__streams_pool_size=0
audit_file_dest='F:\standby\admin\standby\adump'
audit_trail='db'
compatible='11.2.0.0.0'
control_files='F:\standby\oradata\standby\STANDBY.ctl'
db_block_size=8192
db_domain='AKEETECH.COM'
db_name='prim'
db_recovery_file_dest='F:\standby\flash_recovery_area'
db_recovery_file_dest_size=4039114752
diagnostic_dest='F:\standby'
dispatchers='(PROTOCOL=TCP) (SERVICE=standbyXDB)'
fal_client='standby'
fal_server='prim'
local_listener='LISTENER_PRIM'
memory_target=1288699904
open_cursors=300
processes=150
remote_login_passwordfile='EXCLUSIVE'
standby_file_management='auto'
undo_tablespace='UNDOTBS1'
standby_file_management=auto
fal_server=prim
fal_client=standby
Primary Db Init file
prim.__db_cache_size=536870912
prim.__java_pool_size=8388608
prim.__large_pool_size=8388608
prim.__oracle_base='D:\Primary'#ORACLE_BASE set from environment
prim.__pga_aggregate_target=520093696
prim.__sga_target=771751936
prim.__shared_io_pool_size=0
prim.__shared_pool_size=209715200
prim.__streams_pool_size=0
*.audit_file_dest='D:\Primary\admin\prim\adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.control_files='D:\Primary\oradata\prim\control01.ctl','D:\Primary\flash_recovery_area\prim\control02.ctl'
*.db_block_size=8192
*.db_domain='AKEETECH.COM'
*.db_name='prim'
*.db_recovery_file_dest='D:\Primary\flash_recovery_area'
*.db_recovery_file_dest_size=4039114752
*.diagnostic_dest='D:\Primary'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=primXDB)'
*.local_listener='LISTENER_PRIM'
*.memory_target=1288699904
*.open_cursors=300
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.undo_tablespace='UNDOTBS1'
standby_file_management=auto
fal_server=prim
fal_client=standby
Steps i have followed till now.
1) Created standby control file in primary in mount stage (STANDBY.CTL)
2) Installed 11g DB software alone in standby location
3) Shutdown the Primary DB and Taken cold back of all the other files and copied in Standby DB location (Primary in D:\ Drive and Standby in F:\ Drive )
4) Edited init parameters in Primary and standby
5) Startup no mount pfile= standby db init file ( its started )
6) SQL> alter database mount standby database; --- at this time i got the error i have mentioned above, so i have changed the db_name same in both init.ora files
7)
Up to this step i have done .. but this is all blindly.. not in clear understanding..
Kindly guide me.. step by step configuration..
Regards
Hamid

Similar Messages

  • Help for: ORA-01103: database name PRIMARY in control file is not STANDBY

    Hello all, this will be my first post to the support forum. I'm an associate dba with just 6 months on the job, so if I've forgotten something or not given some infromation that is needed please let me know.
    I've also combed the forums/internet, and some of the answers haven't helped. The Oracle Document ORA-1103 While Mounting the Database Using PFILE [ID 237073.1] says my init.ora file is corrupted, but creating a new init.ora file from the spfile does not help. Neither does just starting from the spfile. I have older copies of the init.ora file and the spfiles that the database was running on previously, so I believe they are good.
    This standby NIRNASD1 has existed previously, I had to refresh the primary NIKNASD2, and then re-instantiate NIRNASD1 after the refresh is complete.
    My env is set correctly, and my ORACLE_SID has been exported to NIRNASD1
    NIKNASD2 = Primary Database
    NIRNASD1 = Secondary/Standby Database
    Goal: Creation of Logical Standby NIRNASD1 after creating Physical Standby from NIKNASD2
    My database versions are 10.2.0.4.0, and the databases are on a Unix server. Both databases are located on separate servers.
    Steps that I have taken:
    I used RMAN to backup our primary database to the staging area:
    $ rman target /
    run {
    backup database
    format '/datatransa/dg_stage/%U'
    include current controlfile for standby;
    sql "alter system archive log current";
    backup archivelog all format '/datatransa/dg_stage/%U';
    I used RMAN to Create Secondary Database utilizing RMAN DUPLICATE command.
    RMAN> run {
    2> allocate auxiliary channel auxdisk device type disk;     
    3> duplicate target database for standby NOFILENAMECHECK;
    4> }
    On Secondary database I started Managed Recovery mode
    SQL> shutdown immediate;
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    (I used pfile here, thinking that I needed to mount the database to the pfile so that the database would see the change in the dataguard parameters in the init.ora file, the change from logical to physical- I commeneted out the logical and uncommented the physical line)
    # Dataguard Parameters
    For logical standby, change db_name to name of standby database.
    db_name=NIKNASD2 ### for physical, db_name is same as primary
    #db_name=NIRNASD1 ### for logical, db_name is same as unique_name
    SQL> STARTUP MOUNT PFILE = /oraa/app/oracle/product/1020/admin/NIRNASD1/pfile/initNIRNASD1.ora;
    ORACLE instance started.
    Total System Global Area 1577058304 bytes
    Fixed Size 2084368 bytes
    Variable Size 385876464 bytes
    Database Buffers 1174405120 bytes
    Redo Buffers 14692352 bytes
    Database mounted.
    SQL> ALTER DATABASE recover managed standby database using current logfile disconnect;
    I then verified the Data Guard Configuration by using “alter system archive log current;” on the primary database and watching the sequence number change in the secondary database.
    I made sure that:
    •     The primary database was in MAXIMUM PERFORMANCE MODE
    •     Stopped managed recover on the standby database: alter database recover managed standby database cancel;
    •     Built a logical standby data dictionary on the primary database
    •     The db_name in init.ora was changed (this is in our document at my job)
    •     I changed my database name (from physical to logical) in my init.ora pfile (reverse of what I did above)
    # Dataguard Parameters
    For logical standby, change db_name to name of standby database.
    #db_name=NIKNASD2 ### for physical, db_name is same as primary
    db_name=NIRNASD1 ### for logical, db_name is same as unique_name
    I then went to shutdown my standby database and re-start it in a mount exclusive state, which is where I get the ORA-01103 Error (Again I used the pfile, thinking that I needed to tell the database it is now a logical standby):
    SQL> shutdown immediate;
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    SQL> STARTUP EXCLUSIVE MOUNT PFILE = /oraa/app/oracle/product/1020/admin/NIRNASD1/pfile/initNIRNASD1.ora;
    ORACLE instance started.
    Total System Global Area 1577058304 bytes
    Fixed Size 2084368 bytes
    Variable Size 385876464 bytes
    Database Buffers 1174405120 bytes
    Redo Buffers 14692352 bytes
    ORA-01103: database name 'NIKNASD2' in control file is not 'NIRNASD1'
    From what I understand of the process, the name in the control file is correct, I want it to be NIRNASD1. But the database for some reason thinks it should be NIKNASD2. The following are the parts of my init.ora file that include the dataguard parameters:
    # Database Identification
    db_domain=""
    #db_name=NIRNASD1
    #db_unique_name=NIRNASD1
    # File Configuration
    control_files=("/oradba2/oradata/NIRNASD1/control01.ctl", "/oradba3/oradata/NIRNASD1/control02.ctl", "/oradba4/oradata/NIRNASD1/control03.ctl")
    # Instance Identification
    instance_name=NIRNASD1
    # Dataguard Parameters
    #db_name=NIKNASD2 ### for physical, db_name is same as prmary
    db_name=NIRNASD1 ### for logical, db_name is same as unique_name
    db_unique_name=NIRNASD1
    dg_broker_start=TRUE
    db_file_name_convert='NIKNASD2','NIRNASD1'
    log_file_name_convert='NIKNASD2','NIRNASD1'
    log_archive_config='dg_config=(NIRNASD1,NIKNASD2)'
    log_archive_dest_1='LOCATION="/oraarcha/NIRNASD1/" valid_for=(ONLINE_LOGFILES,all_roles) db_unique_name=NIRNASD1'
    #log_archive_dest_2='LOCATION="/oraarcha/NIKNASD2/" valid_for=(standby_logfiles,standby_roles) db_unique_name=NIRNASD1'
    log_archive_dest_2='LOCATION="/oraarcha/NIKNASD2/" valid_for=(standby_logfile,standby_role) db_unique_name=NIRNASD1'
    STANDBY_ARCHIVE_DEST='LOCATION=/oraarcha/NIKNASD2/'
    # Parameters are not needed since this server will NOT become primary
    #log_archive_dest_2='service=NIKNASD2
    # valid_for=(online_logfiles,primary_role)
    # db_unique_name=NIKNASD2'
    fal_server='NIKNASD2'
    fal_client='NIRNASD1'
    I would appreciate any help, or pointing me in the right direction. I'm just missing something. I am reviewing the documents for building a physical and logical standby from oracle. Just not sure where to go from here.
    Thank you
    Edited by: 977917 on Dec 19, 2012 5:49 PM

    First of all, thank you both for answering my post. I've pulled up Mr. Hesse's page and will make it a go-to staple.
    We're in the process of upgrading our databases, but we have 130+ databases and only six Oracle dba's, and I'm one of them. It's a large corporation, and things move at a "slow and tested" pace.
    The pfile parameters listed above are from my secondary/standby database. And I do want to create a logical standby.
    I forgot to mention that we do use DataGuard Broker, but I did not think that would be the cause of why the database was starting up incorrectly, so I did not mention it. My apologies there.
    As far as the db_name, here's my question on that. It's my understanding the the db_name should be the name of the primary database when you are working with a physical standby, but as soon as you convert it to logical, you should change the db_name to the secondary/standby database? Am I correct on that?
    Leading from that, during the process of creating the physical standby and converting the physical standby to the logical standby, should I change the db_name in the secondary/standby database in the spfile and never use the pfile at all? For instance, when I create the physical standby I have to change the db_name in the standby to the PRIMARY database, so that makes me think I should change db_name in the spfile? (If you see above, I changed db_name in the pfile and did a startup pfile)
    This morning I was able to reach out to a fellow DBA (they are were asleep when I posted this last night), and they tried a few things. We had a redirect in the standby directory /oraa/app/oracle/product/1020/dbs folder that looked like this: spfileNIRNASD1.ora -> /oraa/app/oracle/product/1020/admin/NIRNASD1/pfile/spfileNIRNASD1.ora
    She removed the redirect and the startup mount exclusive then worked without the error.
    Thank you again for your help Mr.Quluzade and Mr. Hesse, I appreciate you all taking the time to teach someone new to the craft. I will definitely read up on the link that you sent me.
    Chris Cranford

  • ORA-01103: database name 'ORDB' in control file is not 'ORCL'

    hey there !!
    11.2.0
    win 7 pro
    let me tell u whole scenario for how i reach to this error - ORA-01103: database name 'ORDB' in control file is not 'ORCL'
    -installed new 11g ( test/ practice environment )
    -by default database created 'ORCL' while installation
    -created another instance 'ORDB' ( my aim was to create auxiliary database/duplicate database )
    -done well according to oracle documents and SUCESSFULLY created a duplicated database
    -i thot of sycnronization to auxiliary to target db , so i read docs and learn that you can issue
    DUPLICATE TARGET DATABASE TO dupdb ( its an oracle Doc's exmple so i put my db name and path accordingly )
    SKIP TABLESPACE tools
    LOGFILE
    GROUP 1 ('/duplogs/redo01a.log',
    '/duplogs/redo01b.log') SIZE 200K REUSE,
    GROUP 2 ('/duplogs/redo02a.log',
    '/duplogs/redo02b.log') SIZE 200K REUSE;NOW, process was Failed , above command didn work bcos of some syntax error .
    BUT what happned is - now whenever i connect both target and auxiliary database from RMAN it shows this -
    C:\Users\Administrator>rman target /@orcl auxiliary /@ordb
    Recovery Manager: Release 11.2.0.1.0 - Production on Fri Apr 5 10:54:04 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: ORCL (DBID=1339650140)
    connected to auxiliary database: ORCL (not mounted)
    RMAN>and also whenever i connect Target ( main , not auxiliary db ) from SQL it shows the error that i described in title .
    I feel like something BUG because this happned to me 5th time , in that 5 times 4 times i got this error while i was duplicating a database . and also after sucessfully duplicated DB ( that was 5th time )
    Thanks
    Regards

    Hi ,
    check the db_name parameter in init parameter file.
    Edited by: Jamsher on Apr 4, 2013 10:33 PM

  • ORA-01103: database name 'PROD1' in control file is not 'PROD2'

    Dear Experts,
    I am trying to use a full compressed backup of PROD1database to create a new database called PROD2 on the SAME host.
    Both databases are using 11.2.0.2 version on Oracle Redhat 5.
    1- I created pfile from source PROD1 database, and modified the following;
    {code}
    *.control_files='+prod2_DG/prod2/controlfile/control01.ctl'
    *.db_create_file_dest='+prod2_DG'
    *.db_name='prod2'
    {code}
    2- Started up no mount the prod2 database using the new pfile.
    3- restore the controlfile from PROD1 backup;
    restore controlfile from '/tmp/prod2/prod1_cntl_4ioet09f_1_1.bkp'
    4- alter database mount give me the following error;
    {code}
    RMAN-00571: ===========================================================
    RMAN-03002: failure of startup command at 07/18/2013 05:52:51
    ORA-01103: database name 'PROD1' in control file is not 'PROD2'
    {code}
    I want to test the backup made on prod1 and same time have a new database prod2 on same host.
    I also tried with SET DBID = <DBID_OF_PROD1> and it doesn't work!
    How I can fix that?
    Thanks and best regards

    SET DBID or DB_NAME in the parameter file don't change the database name  that is in the control file.  At the point of restore, the control file still has the "prod1" database name.
    With RMAN backups, you should consider using DUPLICATE DATABASE
    http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmdupdb.htm#i1008564
    Running a DUPLICATE Database on the same host as the source database is a risky operation.  Done incorrectly, you run the risk of overwriting the datafiles of the source database.  Since your source is a Production database, you run the risk of taking the production database down.  I suggest that you practice the steps on a non-production environment first.
    Hemant K Chitale

  • ORA-01103: database name 'RAC' in control file is not 'STB'

    Hiii..,
    Im doing my dataguard setup, My primary side is a 2node RAC and standby is a single node. Im using 11gR2 Database.
    when im using RMan command for Duplicating the Database im getting the following Error.
    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 10/03/2011 18:33:58
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of sql command on clone_default channel at 10/03/2011 18:33:58
    RMAN-11003: failure during parse/execution of SQL statement: alter database mount standby database
    ORA-01103: database name 'RAC' in control file is not 'STB'
    Plz anyone can help me in resolving the issue.??
    Thanks in advance..

    881222 wrote:
    In my primary side the db_recovery_file_dest is not set as shown beloww..
    SQL> show parameter db_recovery_file_dest;
    NAME                                 TYPE        VALUE
    db_recovery_file_dest                string
    db_recovery_file_dest_size           big integer 0
    SQL> select flashback_on from v$database;
    FLASHBACK_ON
    NO
    so shud i need to set in standby side..??
    Thanks.
    ORA-19801:
         initialization parameter DB_RECOVERY_FILE_DEST is not set
    Cause:      An attempt was made to create a file in DB_RECOVERY_FILE_DEST when DB_RECOVERY_FILE_DEST was not set. There are number of possible causes of this error, including:
                    1) A LOG_ARCHIVE_DEST_n parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archivelog file creation was attempted.
                    2) STANDBY_ARCHIVE_DEST parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archivelog file creation was attempted.
    Action:      Specify a valid destination for DB_RECOVERY_FILE_DEST in initialization parameter file or with the ALTER SYSTEM SET command.

  • ORA-01103: database name 'TESTING2' in control file is not'TESTING1..

    Hello all, please help me on this..im using 10.2.0.4.0 , DB created by ex-colleque
    while connecting db getting ora 1103 error, and tried to create controlfile using trace but i couldn't
    here is the details:
    TESTING1 >startup mount;
    ORACLE instance started.
    Total System Global Area 734003200 bytes
    Fixed Size 2141536 bytes
    Variable Size 328159904 bytes
    Database Buffers 369098752 bytes
    Redo Buffers 34603008 bytes
    ORA-01103: database name 'TESTING2' in control file is not 'TESTING1'
    want to backup ctl file and change the dbname, getting below error..
    TESTING1 >alter database backup controlfile to trace;
    alter database backup controlfile to trace
    ERROR at line 1:
    ORA-01507: database not mounted
    TESTING1:/app/oracle/TESTING1/product/10.2.0.4/dbs >grep db_name initTESTING1.ora
    *.db_name='TESTING1'
    I have found TESTING2 entries in alert log file..
    TESTING1:/app/oracle/TESTING1/admin/bdump >grep TESTING2 alert_TESTING1.log
    DBNAME will be changed from TESTING1 to new DBNAME of TESTING2
    Database name changed to TESTING2.
    Database ID for database TESTING2 changed to 1933958893.
    i have tried to create new controlfile and tried to startup..got below error hence i hv mentioned same datafiles path..
    ORA-01161: database name TESTING2 in file header does not match given name of TESTING1

    Here is the first law of holes.
    When you find yourself in a hole, the first thing you should do is STOP digging.
    Have you taken a full, cold backup since this event started?
    DBNAME will be changed from TESTING1 to new DBNAME of TESTING2When & why did this occur?
    Do you have a valid & recent backup?
    i have tried to create new controlfile Why did you do this?
    Edited by: sb92075 on May 7, 2010 8:36 PM

  • 11g Data guard 建physical standby database配置相关问题

    General information
    OS:red hat Linux 2.6.32-200.13.1.el5uek x86_64(primary,standby)
    Home version:11.2.0.3(primary,standby)
    Situation:
    实验用库,想学习data guard,在另一个服务器上克隆了一个HOME并按照官方文档http://docs.oracle.com/cd/E11882_01/server.112/e25608/create_ps.htm#i1225703
    中去实验,步骤均按照官方文档来,最后在mount standby库时校验select sequence# from v$archived_log没有记录,出错日志如下(从mount开如截取)
    standby alert_dbacoe.log
    Error logs
    alter database mount
    Completed: alter database mount
    Error 604 received logging on to the standby
    +FAL[client, ARC2]: Error 604 connecting to PRIMARYSV for fetching gap sequence+
    Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo01_s.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u03/app/oracle/oradata/dbacoe/redo01.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo01_s.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u03/app/oracle/oradata/dbacoe/redo01.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo02_s.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 2 thread 1: '/u03/app/oracle/oradata/dbacoe/redo02.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo02_s.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 2 thread 1: '/u03/app/oracle/oradata/dbacoe/redo02.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo03_s.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 3 thread 1: '/u03/app/oracle/oradata/dbacoe/redo03.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo03_s.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 3 thread 1: '/u03/app/oracle/oradata/dbacoe/redo03.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ARC3: Archival started
    ARC0: STARTING ARCH PROCESSES COMPLETE
    Addition:
    因为是实验用库,所以结构有点怪,大体如下:
    Primary
    数据文件在BASE所在的oradata下 即/u03/app/oracle下,
    redo文件每组两份,一份在oradata下,另一份在同机的/u04/app/oracle/redundancy中(以_s结尾命名)
    archive文件在/u04/app/oracle/fast_recovery_area中
    standby
    数据文件在/u05/oracle/app/oracle/oradata下
    redundancy中的redo文件随着该目录放到oradata下的red中了
    archive文件目录则是/u05/oracle/app/oracle/fast_recovery_area中
    接下来是对应的init文件与TNS信息
    Primary端的init主要信息
    db_unique_name='PRIMARY'
    fal_client='PRIMARYSV'
    fal_server='STANDBYSV'
    log_archive_config='DG_CONFIG=(PRIMARY,STANDBY)'
    log_archive_dest_1='location=/u04/app/oracle/fast_recovery_area/DBACOE/archivelog VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=PRIMARY'
    log_archive_dest_2='service=STANDBY ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=STANDBY'
    log_archive_dest_state_1='enable'
    log_archive_dest_state_2='enable'
    db_file_name_convert='/u05/oracle/app/oracle/oradata/dbacoe','/u03/app/oracle/oradata/dbacoe',/u05/oracle/app/oracle/oradata/red','/u04/app/oracle/redundancy'
    log_file_name_convert='/u05/oracle/app/oracle/fast_recovery_area/DBACOE/archivelog','/u04/app/oracle/fast_recovery_area/DBACOE/archivelog'
    Standby端的init信息
    log_archive_config='DG_CONFIG=(PRIMARY,STANDBY)'
    db_unique_name='STANDBY'
    db_file_name_convert='/u03/app/oracle/oradata/dbacoe','/u05/oracle/app/oracle/oradata/dbacoe','/u04/app/oracle/redundancy','/u05/oracle/app/oracle/oradata/red'
    log_file_name_convert='/u04/app/oracle/fast_recovery_area/DBACOE/archivelog','/u05/oracle/app/oracle/fast_recovery_area/DBACOE/archivelog'
    log_archive_dest_1='location=/u05/oracle/app/oracle/fast_recovery_area/DBACOE/archivelog VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=STANDBY'
    log_archive_dest_state_1=enable
    log_archive_format=log%t_%s_%r.arc
    log_archive_dest_2='SERVICE=PRIMARYSV ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
    log_archive_dest_state_2=enable
    TNS信息如下(均能tnsping通)
    PRIMARYSV =
    +(DESCRIPTION =+
    +(ADDRESS = (PROTOCOL = TCP)(HOST = db1.ad.xxxxxx.com)(PORT = 1521))+
    +(CONNECT_DATA =+
    +(SERVER = DEDICATED)+
    +(SERVICE_NAME = dbacoe)+
    +)+
    +)+
    STANDBYSV =
    +(DESCRIPTION =+
    +(ADDRESS = (PROTOCOL = TCP)(HOST = db2.ad.xxxxx.com)(PORT = 1529))+
    +(CONNECT_DATA =+
    +(SERVER = DEDICATED)+
    +(SERVICE_NAME = dbacoe)+
    +)+
    +)+
    PS:请大家花费一点点时间阅读一下这冗长的段子,刚开学data guard,参数上设置都很生疏,(光照着文档做了,是否有redo log相关的操作遗漏?)敬请指教
    Edited by: 961394 on Dec 10, 2012 1:52 AM
    Edited by: 961394 on 2012-12-10 上午4:58

    结贴了,感谢maclean一群的Jesse Lui帮我解决问题

  • Database not found/Error: ORA-16621: database name for ADD DATABASE must be

    I am new to Data Guard and am trying to set up Data Guard Broker. I had created a configuration file with both my primary and standby databases and at one time I could show both databases. But now I can no longer show the standby database nor can I enable, disable or reinstate it. Here is what I have:
    Primary Database: orcl10g
    Standby Database: 10gSB
    DGMGRL> show configuration
    Configuration
    Name: orcl10g
    Enabled: YES
    Protection Mode: MaxPerformance
    Fast-Start Failover: DISABLED
    Databases:
    orcl10g - Primary database
    10gSB - Physical standby database
    Current status for "orcl10g":
    SUCCESS
    DGMGRL> show database verbose orcl10g
    Database
    Name: orcl10g
    Role: PRIMARY
    Enabled: YES
    Intended State: ONLINE
    Instance(s):
    orcl10g
    Properties:
    InitialConnectIdentifier = 'orcl10g'
    LogXptMode = 'ASYNC'
    Dependency = ''
    DelayMins = '0'
    Binding = 'OPTIONAL'
    MaxFailure = '0'
    MaxConnections = '1'
    ReopenSecs = '300'
    NetTimeout = '180'
    LogShipping = 'ON'
    PreferredApplyInstance = ''
    ApplyInstanceTimeout = '0'
    ApplyParallel = 'AUTO'
    StandbyFileManagement = 'AUTO'
    ArchiveLagTarget = '0'
    LogArchiveMaxProcesses = '30'
    LogArchiveMinSucceedDest = '1'
    DbFileNameConvert = '10gSB, orcl10g'
    LogFileNameConvert = '/oracle/oracle/product/10.2.0/oradata/orcl10g/redo01.log, /oracle/oracle/product/10.2.0/oradata/10gSB/redo01.log, /oracle/oracle/product/10.2.0/oradata/orcl10g/redo02.log, /oracle/oracle/product/10.2.0/oradata/10gSB/redo02.log, /oracle/oracle/product/10.2.0/oradata/orcl10g/redo03.log, /oracle/oracle/product/10.2.0/oradata/10gSB/redo03.log'
    FastStartFailoverTarget = ''
    StatusReport = '(monitor)'
    InconsistentProperties = '(monitor)'
    InconsistentLogXptProps = '(monitor)'
    SendQEntries = '(monitor)'
    LogXptStatus = '(monitor)'
    RecvQEntries = '(monitor)'
    HostName = 'remarkable.mammothnetworks.com'
    SidName = 'orcl10g'
    LocalListenerAddress = '(ADDRESS=(PROTOCOL=tcp)(HOST=remarkable.mammothnetworks.com)(PORT=1521))'
    StandbyArchiveLocation = '/oracle/flash_recovery_area/orcl10g/archivelog'
    AlternateLocation = ''
    LogArchiveTrace = '1024'
    LogArchiveFormat = '%t_%s_%r.arc'
    LatestLog = '(monitor)'
    TopWaitEvents = '(monitor)'
    Current status for "orcl10g":
    SUCCESS
    DGMGRL> show database verbose 10gSB
    Object "10gsb" was not found
    DGMGRL>
    DGMGRL> remove database 10gSB
    Object "10gsb" was not found
    DGMGRL>
    DGMGRL> reinstate database 10gSB
    Object "10gsb" was not found
    DGMGRL>
    DGMGRL> enable database 10gSB
    Object "10gsb" was not found
    DGMGRL>
    DGMGRL> add database '10gSB' as
    connect identifier is 10gSB
    maintained as physical;Error: ORA-16621: database name for ADD DATABASE must be unique
    Failed.
    How can I get Data Guard to see the standby database correctly again?

    Thank you for the constructive feedback. I have been able to make progress on this issue.
    I did check the Data Guard Log files as you suggested. I did not find anything when I checked them before but this time I found the following:
    DG 2011-06-16-17:23:18 0 2 0 RSM detected log transport problem: log transport for database '10gSB' has the following error.
    DG 2011-06-16-17:23:18 0 2 0 RSM0: HEALTH CHECK ERROR: ORA-16737: the redo transport service for standby database "10gSB" has an error
    DG 2011-06-16-17:23:18 0 2 0 NSV1: Failed to connect to remote database 10gSB. Error is ORA-12514
    DG 2011-06-16-17:23:18 0 2 0 RSM0: Failed to connect to remote database 10gSB. Error is ORA-12514
    DG 2011-06-16-17:23:18 0 2 753988034 Operation CTL_GET_STATUS cancelled during phase 2, error = ORA-16778
    DG 2011-06-16-17:23:18 0 2 753988034 Operation CTL_GET_STATUS cancelled during phase 2, error = ORA-16778
    I verified that I am able to connect to both the primary and standby databases via external connections:
    -bash-3.2$ lsnrctl status
    LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 17-JUN-2011 12:41:03
    Copyright (c) 1991, 2005, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
    Start Date 17-JUN-2011 01:40:30
    Uptime 0 days 11 hr. 0 min. 32 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /oracle/oracle/product/10.2.0/db_1/network/admin/listener.ora
    Listener Log File /oracle/oracle/product/10.2.0/db_1/network/log/listener.log
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=remarkable.mammothnetworks.com)(PORT=1521)))
    Services Summary...
    Service "10gSB" has 1 instance(s).
    Instance "10gSB", status READY, has 1 handler(s) for this service...
    Service "10gSB_DGB" has 1 instance(s).
    Instance "10gSB", status READY, has 1 handler(s) for this service...
    Service "10gSB_XPT" has 1 instance(s).
    Instance "10gSB", status READY, has 1 handler(s) for this service...
    Service "PLSExtProc" has 1 instance(s).
    Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
    Service "orcl10g" has 1 instance(s).
    Instance "orcl10g", status READY, has 1 handler(s) for this service...
    Service "orcl10gXDB" has 1 instance(s).
    Instance "orcl10g", status READY, has 1 handler(s) for this service...
    Service "orcl10g_DGB" has 1 instance(s).
    Instance "orcl10g", status READY, has 1 handler(s) for this service...
    Service "orcl10g_XPT" has 1 instance(s).
    Instance "orcl10g", status READY, has 1 handler(s) for this service...
    The command completed successfully
    -bash-3.2$
    -bash-3.2$
    -bash-3.2$ sqlplus system/dbas4ever@orcl10g
    SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jun 17 12:43:41 2011
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    SQL> quit
    Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    -bash-3.2$ sqlplus system/dbas4ver@10gSB
    SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jun 17 12:43:59 2011
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    ERROR:
    ORA-01033: ORACLE initialization or shutdown in progress <== I think this is normal since the database is in mount mode
    Enter user-name:
    I also checked the listener log file and did see and error associated with a known bug:
    WARNING: Subscription for node down event still pending
    So I added the following to the listener.ora file and bounced the listener:
    SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER=OFF
    That seems to have taken care of the error.
    The following is my listener.ora file:
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = /oracle/oracle/product/10.2.0/db_1)
    (PROGRAM = extproc)
    (SID_DESC = ( GLOBAL_DBNAME = 10gsb_DGMGRL.remarkable.mammothnetworks.com )
    ( SERVICE_NAME = 10gsb.remarkable.mammothnetworks.com )
    ( SID_NAME = 10gsb )
    ( ORACLE_HOME = /oracle/oracle/product/10.2.0/db_1 )
    (SID_DESC = ( GLOBAL_DBNAME = orcl10g_DGMGRL.remarkable.mammothnetworks.com )
    ( SERVICE_NAME = orcl10g.remarkable.mammothnetworks.com )
    ( SID_NAME = orcl10g )
    ( ORACLE_HOME = /oracle/oracle/product/10.2.0/db_1 )
    (SID_DESC = ( GLOBAL_DBNAME = orcl10g.remarkable.mammothnetworks.com )
    ( SERVICE_NAME = orcl10g.remarkable.mammothnetworks.com )
    ( SID_NAME = orcl10g )
    ( ORACLE_HOME = /oracle/oracle/product/10.2.0/db_1 )
    (SID_DESC = ( GLOBAL_DBNAME = 10gsb.remarkable.mammothnetworks.com )
    ( SERVICE_NAME = 10gsb.remarkable.mammothnetworks.com )
    ( SID_NAME = 10gsb )
    ( ORACLE_HOME = /oracle/oracle/product/10.2.0/db_1 )
    SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER=OFF
    I again tried connecting externally to the standby database:
    -bash-3.2$ sqlplus system/dbas4ever@10gSB
    SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jun 17 13:09:00 2011
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    ERROR:
    ORA-01033: ORACLE initialization or shutdown in progress
    Enter user-name:
    and see this in the listener.log file:
    17-JUN-2011 13:10:22 * (CONNECT_DATA=(SERVICE_NAME=10gSB_XPT)(SERVER=dedicated)(CID=(PROGRAM=oracle)(HOST=remarkable.mammothnetworks.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=199.187.124.130)(PORT=11357)) * establish * 10gSB_XPT * 0
    17-JUN-2011 13:10:22 * (CONNECT_DATA=(SERVICE_NAME=10gSB_XPT)(SERVER=dedicated)(CID=(PROGRAM=oracle)(HOST=remarkable.mammothnetworks.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=199.187.124.130)(PORT=11358)) * establish * 10gSB_XPT * 0
    17-JUN-2011 13:10:24 * service_update * 10gSB * 0
    17-JUN-2011 13:10:30 * (CONNECT_DATA=(SID=orcl10g)(CID=(PROGRAM=perl)(HOST=remarkable.mammothnetworks.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=25119)) * establish * orcl10g * 0
    17-JUN-2011 13:10:30 * (CONNECT_DATA=(SID=orcl10g)(CID=(PROGRAM=perl)(HOST=remarkable.mammothnetworks.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=25120)) * establish * orcl10g * 0
    17-JUN-2011 13:10:30 * (CONNECT_DATA=(SID=orcl10g)(CID=(PROGRAM=emagent)(HOST=localhost.localdomain)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=25121)) * establish * orcl10g * 0
    17-JUN-2011 13:11:22 * (CONNECT_DATA=(SERVICE_NAME=10gSB_XPT)(SERVER=dedicated)(CID=(PROGRAM=oracle)(HOST=remarkable.mammothnetworks.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=199.187.124.130)(PORT=11420)) * establish * 10gSB_XPT * 0
    17-JUN-2011 13:11:22 * (CONNECT_DATA=(SERVICE_NAME=10gSB_XPT)(SERVER=dedicated)(CID=(PROGRAM=oracle)(HOST=remarkable.mammothnetworks.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=199.187.124.130)(PORT=11422)) * establish * 10gSB_XPT * 0
    17-JUN-2011 13:11:24 * service_update * 10gSB * 0
    I tried again to see the database in Data Guard Broker:
    DGMGRL> show database 10gSB
    Object "10gsb" was not found
    however, I then was able to add the database in Data Guard Broker:
    DGMGRL> add database 10gSB
    as connect identifier is 10gSB
    maintained as physical;Database "10gsb" added <== this is progress!!!
    However the configuration shows the following:
    DGMGRL> show database 10gSB
    Database
    Name: 10gsb
    Role: PHYSICAL STANDBY
    Enabled: NO
    Intended State: OFFLINE
    Instance(s):
    10gSB
    Current status for "10gsb":
    DISABLED <=====
    So I tried to enable the database:
    DGMGRL> enable database 10gSB
    Error: ORA-16626: failed to enable specified object
    Failed.
    and I tried to reinstate the database:
    DGMGRL> reinstate database 10gSB
    Reinstating database "10gsb", please wait...
    Error: ORA-16653: failed to reinstate database
    Failed.
    Reinstatement of database "10gsb" failed
    So I checked the configuration and now see two entries for the standby database but with case differences:
    DGMGRL> show configuration
    Configuration
    Name: orcl10g
    Enabled: YES
    Protection Mode: MaxPerformance
    Fast-Start Failover: DISABLED
    Databases:
    orcl10g - Primary database
    10gSB - Physical standby database
    10gsb - Physical standby database (disabled)
    Current status for "orcl10g":
    SUCCESS
    Question: How do I get rid of 10gSB and enable 10gsb?

  • ORA-01161: database name DEV in file header does not match given name UAT

    This is my cloning process.... I get the following errors.. I also double check with my process and still couldn't find anything.
    SQL> @backup_control.sql
    ORACLE instance started.
    Total System Global Area  479298392 bytes
    Fixed Size                   742232 bytes
    Variable Size             385875968 bytes
    Database Buffers           81920000 bytes
    Redo Buffers               10760192 bytes
    CREATE CONTROLFILE REUSE DATABASE "UAT" NORESETLOGS  ARCHIVELOG
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01161: database name OBS in file header does not match given name of UAT
    ORA-01110: data file 1: '/u01/oracle/uatdata/system01.dbf'
    Any ideas of this error?
    Best Regards,
    Amy

    Please see followings:
    STARTUP NOMOUNT
    CREATE CONTROLFILE SET DATABASE "OBS" RESETLOGS ARCHIVELOG
    -- SET STANDBY TO MAXIMIZE PERFORMANCE
    MAXLOGFILES 16
    MAXLOGMEMBERS 2
    MAXDATAFILES 500
    MAXINSTANCES 1
    MAXLOGHISTORY 2042
    LOGFILE
    GROUP 1 '/u01/oracle/obsdata/log01a.dbf' SIZE 10M,
    GROUP 2 '/u01/oracle/obsdata/log02a.dbf' SIZE 10M,
    GROUP 3 '/u01/oracle/obsdata/log03a.dbf' SIZE 10M,
    GROUP 4 '/u01/oracle/obsdata/log04a.dbf' SIZE 10M
    -- STANDBY LOGFILE
    DATAFILE
    '/u01/oracle/obsdata/system01.dbf',
    '/u01/oracle/obsdata/system02.dbf',
    '/u01/oracle/obsdata/system03.dbf',
    '/u01/oracle/obsdata/system04.dbf',
    '/u01/oracle/obsdata/system05.dbf',
    '/u01/oracle/obsdata/rbs01.dbf',
    '/u01/oracle/obsdata/ctxd01.dbf',
    '/u01/oracle/obsdata/owad01.dbf',
    '/u01/oracle/obsdata/abmd01.dbf',
    '/u01/oracle/obsdata/abmx01.dbf',
    '/u01/oracle/obsdata/akd01.dbf',
    '/u01/oracle/obsdata/akx01.dbf',
    '/u01/oracle/obsdata/alrd01.dbf',
    '/u01/oracle/obsdata/alrx01.dbf',
    '/u01/oracle/obsdata/amsd01.dbf',
    '/u01/oracle/obsdata/amsx01.dbf',
    '/u01/oracle/obsdata/amvd01.dbf',
    '/u01/oracle/obsdata/amvx01.dbf',
    '/u01/oracle/obsdata/apd01.dbf',
    '/u01/oracle/obsdata/apx01.dbf',
    '/u01/oracle/obsdata/applsysd01.dbf',
    '/u01/oracle/obsdata/applsysx01.dbf',
    '/u01/oracle/obsdata/ard01.dbf',
    '/u01/oracle/obsdata/arx01.dbf',
    '/u01/oracle/obsdata/asfd01.dbf',
    '/u01/oracle/obsdata/asfx01.dbf',
    '/u01/oracle/obsdata/asgd01.dbf',
    '/u01/oracle/obsdata/asgx01.dbf',
    '/u01/oracle/obsdata/asod01.dbf',
    '/u01/oracle/obsdata/asox01.dbf',
    '/u01/oracle/obsdata/astd01.dbf',
    '/u01/oracle/obsdata/astx01.dbf',
    '/u01/oracle/obsdata/axd01.dbf',
    '/u01/oracle/obsdata/axx01.dbf',
    '/u01/oracle/obsdata/azd01.dbf',
    '/u01/oracle/obsdata/azx01.dbf',
    '/u01/oracle/obsdata/bend01.dbf',
    '/u01/oracle/obsdata/benx01.dbf',
    '/u01/oracle/obsdata/bicd01.dbf',
    '/u01/oracle/obsdata/bicx01.dbf',
    '/u01/oracle/obsdata/bild01.dbf',
    '/u01/oracle/obsdata/bilx01.dbf',
    '/u01/oracle/obsdata/bimd01.dbf',
    '/u01/oracle/obsdata/bimx01.dbf',
    '/u01/oracle/obsdata/bisd01.dbf',
    '/u01/oracle/obsdata/bisx01.dbf',
    '/u01/oracle/obsdata/bixd01.dbf',
    '/u01/oracle/obsdata/bixx01.dbf',
    '/u01/oracle/obsdata/bomd01.dbf',
    '/u01/oracle/obsdata/bomx01.dbf',
    '/u01/oracle/obsdata/bscd01.dbf',
    '/u01/oracle/obsdata/bscx01.dbf',
    '/u01/oracle/obsdata/cctd01.dbf',
    '/u01/oracle/obsdata/cctx01.dbf',
    '/u01/oracle/obsdata/ced01.dbf',
    '/u01/oracle/obsdata/cex01.dbf',
    '/u01/oracle/obsdata/cnd01.dbf',
    '/u01/oracle/obsdata/cnx01.dbf',
    '/u01/oracle/obsdata/crpd01.dbf',
    '/u01/oracle/obsdata/crpx01.dbf',
    '/u01/oracle/obsdata/csd01.dbf',
    '/u01/oracle/obsdata/csx01.dbf',
    '/u01/oracle/obsdata/cscd01.dbf',
    '/u01/oracle/obsdata/cscx01.dbf',
    '/u01/oracle/obsdata/csdd01.dbf',
    '/u01/oracle/obsdata/csdx01.dbf',
    '/u01/oracle/obsdata/csfd01.dbf',
    '/u01/oracle/obsdata/csfx01.dbf',
    '/u01/oracle/obsdata/cspd01.dbf',
    '/u01/oracle/obsdata/cspx01.dbf',
    '/u01/oracle/obsdata/csrd01.dbf',
    '/u01/oracle/obsdata/csrx01.dbf',
    '/u01/oracle/obsdata/cssd01.dbf',
    '/u01/oracle/obsdata/cssx01.dbf',
    '/u01/oracle/obsdata/cuad01.dbf',
    '/u01/oracle/obsdata/cuax01.dbf',
    '/u01/oracle/obsdata/cufd01.dbf',
    '/u01/oracle/obsdata/cufx01.dbf',
    '/u01/oracle/obsdata/cuid01.dbf',
    '/u01/oracle/obsdata/cuix01.dbf',
    '/u01/oracle/obsdata/cund01.dbf',
    '/u01/oracle/obsdata/cunx01.dbf',
    '/u01/oracle/obsdata/cupd01.dbf',
    '/u01/oracle/obsdata/cupx01.dbf',
    '/u01/oracle/obsdata/cusd01.dbf',
    '/u01/oracle/obsdata/cusx01.dbf',
    '/u01/oracle/obsdata/czd01.dbf',
    '/u01/oracle/obsdata/czx01.dbf',
    '/u01/oracle/obsdata/eaad01.dbf',
    '/u01/oracle/obsdata/eaax01.dbf',
    '/u01/oracle/obsdata/ecd01.dbf',
    '/u01/oracle/obsdata/ecx01.dbf',
    '/u01/oracle/obsdata/ecxd01.dbf',
    '/u01/oracle/obsdata/ecxx01.dbf',
    '/u01/oracle/obsdata/engd01.dbf',
    '/u01/oracle/obsdata/engx01.dbf',
    '/u01/oracle/obsdata/evmd01.dbf',
    '/u01/oracle/obsdata/evmx01.dbf',
    '/u01/oracle/obsdata/fad01.dbf',
    '/u01/oracle/obsdata/fax01.dbf',
    '/u01/oracle/obsdata/femd01.dbf',
    '/u01/oracle/obsdata/femx01.dbf',
    '/u01/oracle/obsdata/fiid01.dbf',
    '/u01/oracle/obsdata/fiix01.dbf',
    '/u01/oracle/obsdata/flmd01.dbf',
    '/u01/oracle/obsdata/flmx01.dbf',
    '/u01/oracle/obsdata/fptd01.dbf',
    '/u01/oracle/obsdata/fptx01.dbf',
    '/u01/oracle/obsdata/frmd01.dbf',
    '/u01/oracle/obsdata/frmx01.dbf',
    '/u01/oracle/obsdata/fvd01.dbf',
    '/u01/oracle/obsdata/fvx01.dbf',
    '/u01/oracle/obsdata/gld01.dbf',
    '/u01/oracle/obsdata/glx01.dbf',
    '/u01/oracle/obsdata/gmad01.dbf',
    '/u01/oracle/obsdata/gmax01.dbf',
    '/u01/oracle/obsdata/gmdd01.dbf',
    '/u01/oracle/obsdata/gmdx01.dbf',
    '/u01/oracle/obsdata/gmed01.dbf',
    '/u01/oracle/obsdata/gmex01.dbf',
    '/u01/oracle/obsdata/gmfd01.dbf',
    '/u01/oracle/obsdata/gmfx01.dbf',
    '/u01/oracle/obsdata/gmid01.dbf',
    '/u01/oracle/obsdata/gmix01.dbf',
    '/u01/oracle/obsdata/gmld01.dbf',
    '/u01/oracle/obsdata/gmlx01.dbf',
    '/u01/oracle/obsdata/gmpd01.dbf',
    '/u01/oracle/obsdata/gmpx01.dbf',
    '/u01/oracle/obsdata/gmsd01.dbf',
    '/u01/oracle/obsdata/gmsx01.dbf',
    '/u01/oracle/obsdata/grd01.dbf',
    '/u01/oracle/obsdata/grx01.dbf',
    '/u01/oracle/obsdata/hrd01.dbf',
    '/u01/oracle/obsdata/hrx01.dbf',
    '/u01/oracle/obsdata/hrid01.dbf',
    '/u01/oracle/obsdata/hrix01.dbf',
    '/u01/oracle/obsdata/hxcd01.dbf',
    '/u01/oracle/obsdata/hxcx01.dbf',
    '/u01/oracle/obsdata/hxtd01.dbf',
    '/u01/oracle/obsdata/hxtx01.dbf',
    '/u01/oracle/obsdata/ibad01.dbf',
    '/u01/oracle/obsdata/ibax01.dbf',
    '/u01/oracle/obsdata/ibed01.dbf',
    '/u01/oracle/obsdata/ibex01.dbf',
    '/u01/oracle/obsdata/ibpd01.dbf',
    '/u01/oracle/obsdata/ibpx01.dbf',
    '/u01/oracle/obsdata/ibud01.dbf',
    '/u01/oracle/obsdata/ibux01.dbf',
    '/u01/oracle/obsdata/ibyd01.dbf',
    '/u01/oracle/obsdata/ibyx01.dbf',
    '/u01/oracle/obsdata/icxd01.dbf',
    '/u01/oracle/obsdata/icxx01.dbf',
    '/u01/oracle/obsdata/iebd01.dbf',
    '/u01/oracle/obsdata/iebx01.dbf',
    '/u01/oracle/obsdata/iemd01.dbf',
    '/u01/oracle/obsdata/iemx01.dbf',
    '/u01/oracle/obsdata/ieod01.dbf',
    '/u01/oracle/obsdata/ieox01.dbf',
    '/u01/oracle/obsdata/iesd01.dbf',
    '/u01/oracle/obsdata/iesx01.dbf',
    '/u01/oracle/obsdata/ieud01.dbf',
    '/u01/oracle/obsdata/ieux01.dbf',
    '/u01/oracle/obsdata/iexd01.dbf',
    '/u01/oracle/obsdata/iexx01.dbf',
    '/u01/oracle/obsdata/igcd01.dbf',
    '/u01/oracle/obsdata/igcx01.dbf',
    '/u01/oracle/obsdata/igfd01.dbf',
    '/u01/oracle/obsdata/igfx01.dbf',
    '/u01/oracle/obsdata/igsd01.dbf',
    '/u01/oracle/obsdata/igsx01.dbf',
    '/u01/oracle/obsdata/igwd01.dbf',
    '/u01/oracle/obsdata/igwx01.dbf',
    '/u01/oracle/obsdata/invd01.dbf',
    '/u01/oracle/obsdata/invx01.dbf',
    '/u01/oracle/obsdata/ipad01.dbf',
    '/u01/oracle/obsdata/ipax01.dbf',
    '/u01/oracle/obsdata/iscd01.dbf',
    '/u01/oracle/obsdata/iscx01.dbf',
    '/u01/oracle/obsdata/jad01.dbf',
    '/u01/oracle/obsdata/jax01.dbf',
    '/u01/oracle/obsdata/jed01.dbf',
    '/u01/oracle/obsdata/jex01.dbf',
    '/u01/oracle/obsdata/jgd01.dbf',
    '/u01/oracle/obsdata/jgx01.dbf',
    '/u01/oracle/obsdata/jld01.dbf',
    '/u01/oracle/obsdata/jlx01.dbf',
    '/u01/oracle/obsdata/jtfd01.dbf',
    '/u01/oracle/obsdata/jtfx01.dbf',
    '/u01/oracle/obsdata/med01.dbf',
    '/u01/oracle/obsdata/mex01.dbf',
    '/u01/oracle/obsdata/mfgd01.dbf',
    '/u01/oracle/obsdata/mfgx01.dbf',
    '/u01/oracle/obsdata/mrpd01.dbf',
    '/u01/oracle/obsdata/mrpx01.dbf',
    '/u01/oracle/obsdata/mscd01.dbf',
    '/u01/oracle/obsdata/mscx01.dbf',
    '/u01/oracle/obsdata/msdd01.dbf',
    '/u01/oracle/obsdata/msdx01.dbf',
    '/u01/oracle/obsdata/msod01.dbf',
    '/u01/oracle/obsdata/msox01.dbf',
    '/u01/oracle/obsdata/mwad01.dbf',
    '/u01/oracle/obsdata/mwax01.dbf',
    '/u01/oracle/obsdata/oed01.dbf',
    '/u01/oracle/obsdata/oex01.dbf',
    '/u01/oracle/obsdata/okcd01.dbf',
    '/u01/oracle/obsdata/okcx01.dbf',
    '/u01/oracle/obsdata/oked01.dbf',
    '/u01/oracle/obsdata/okex01.dbf',
    '/u01/oracle/obsdata/oksd01.dbf',
    '/u01/oracle/obsdata/oksx01.dbf',
    '/u01/oracle/obsdata/okxd01.dbf',
    '/u01/oracle/obsdata/okxx01.dbf',
    '/u01/oracle/obsdata/ontd01.dbf',
    '/u01/oracle/obsdata/ontx01.dbf',
    '/u01/oracle/obsdata/opid01.dbf',
    '/u01/oracle/obsdata/opix01.dbf',
    '/u01/oracle/obsdata/osmd01.dbf',
    '/u01/oracle/obsdata/osmx01.dbf',
    '/u01/oracle/obsdata/otad01.dbf',
    '/u01/oracle/obsdata/otax01.dbf',
    '/u01/oracle/obsdata/ozfd01.dbf',
    '/u01/oracle/obsdata/ozfx01.dbf',
    '/u01/oracle/obsdata/ozpd01.dbf',
    '/u01/oracle/obsdata/ozpx01.dbf',
    '/u01/oracle/obsdata/ozsd01.dbf',
    '/u01/oracle/obsdata/ozsx01.dbf',
    '/u01/oracle/obsdata/pad01.dbf',
    '/u01/oracle/obsdata/pax01.dbf',
    '/u01/oracle/obsdata/pjmd01.dbf',
    '/u01/oracle/obsdata/pjmx01.dbf',
    '/u01/oracle/obsdata/pmid01.dbf',
    '/u01/oracle/obsdata/pmix01.dbf',
    '/u01/oracle/obsdata/pnd01.dbf',
    '/u01/oracle/obsdata/pnx01.dbf',
    '/u01/oracle/obsdata/pod01.dbf',
    '/u01/oracle/obsdata/pox01.dbf',
    '/u01/oracle/obsdata/poad01.dbf',
    '/u01/oracle/obsdata/poax01.dbf',
    '/u01/oracle/obsdata/pomd01.dbf',
    '/u01/oracle/obsdata/pomx01.dbf',
    '/u01/oracle/obsdata/psad01.dbf',
    '/u01/oracle/obsdata/psax01.dbf',
    '/u01/oracle/obsdata/psbd01.dbf',
    '/u01/oracle/obsdata/psbx01.dbf',
    '/u01/oracle/obsdata/pspd01.dbf',
    '/u01/oracle/obsdata/pspx01.dbf',
    '/u01/oracle/obsdata/qad01.dbf',
    '/u01/oracle/obsdata/qax01.dbf',
    '/u01/oracle/obsdata/qpd01.dbf',
    '/u01/oracle/obsdata/qpx01.dbf',
    '/u01/oracle/obsdata/rgd01.dbf',
    '/u01/oracle/obsdata/rgx01.dbf',
    '/u01/oracle/obsdata/rhxd01.dbf',
    '/u01/oracle/obsdata/rhxx01.dbf',
    '/u01/oracle/obsdata/rlad01.dbf',
    '/u01/oracle/obsdata/rlax01.dbf',
    '/u01/oracle/obsdata/rlmd01.dbf',
    '/u01/oracle/obsdata/rlmx01.dbf',
    '/u01/oracle/obsdata/sspd01.dbf',
    '/u01/oracle/obsdata/sspx01.dbf',
    '/u01/oracle/obsdata/vead01.dbf',
    '/u01/oracle/obsdata/veax01.dbf',
    '/u01/oracle/obsdata/vehd01.dbf',
    '/u01/oracle/obsdata/vehx01.dbf',
    '/u01/oracle/obsdata/wipd01.dbf',
    '/u01/oracle/obsdata/wipx01.dbf',
    '/u01/oracle/obsdata/wmsd01.dbf',
    '/u01/oracle/obsdata/wmsx01.dbf',
    '/u01/oracle/obsdata/wpsd01.dbf',
    '/u01/oracle/obsdata/wpsx01.dbf',
    '/u01/oracle/obsdata/wshd01.dbf',
    '/u01/oracle/obsdata/wshx01.dbf',
    '/u01/oracle/obsdata/wsmd01.dbf',
    '/u01/oracle/obsdata/wsmx01.dbf',
    '/u01/oracle/obsdata/xdpd01.dbf',
    '/u01/oracle/obsdata/xdpx01.dbf',
    '/u01/oracle/obsdata/xlad01.dbf',
    '/u01/oracle/obsdata/xlax01.dbf',
    '/u01/oracle/obsdata/xncd01.dbf',
    '/u01/oracle/obsdata/xncx01.dbf',
    '/u01/oracle/obsdata/xnmd01.dbf',
    '/u01/oracle/obsdata/xnmx01.dbf',
    '/u01/oracle/obsdata/xnpd01.dbf',
    '/u01/oracle/obsdata/xnpx01.dbf',
    '/u01/oracle/obsdata/xnsd01.dbf',
    '/u01/oracle/obsdata/xnsx01.dbf',
    '/u01/oracle/obsdata/xtrd01.dbf',
    '/u01/oracle/obsdata/xtrx01.dbf',
    '/u01/oracle/obsdata/applsysd02.dbf',
    '/u01/oracle/obsdata/applsysx02.dbf',
    '/u01/oracle/obsdata/asld01.dbf',
    '/u01/oracle/obsdata/aslx01.dbf',
    '/u01/oracle/obsdata/pvd01.dbf',
    '/u01/oracle/obsdata/pvx01.dbf',
    '/u01/oracle/obsdata/system06.dbf',
    '/u01/oracle/obsdata/itgd01.dbf',
    '/u01/oracle/obsdata/itgx01.dbf',
    '/u01/oracle/obsdata/ipdd01.dbf',
    '/u01/oracle/obsdata/ipdx01.dbf',
    '/u01/oracle/obsdata/eamd01.dbf',
    '/u01/oracle/obsdata/eamx01.dbf',
    '/u01/oracle/obsdata/enid01.dbf',
    '/u01/oracle/obsdata/enix01.dbf',
    '/u01/oracle/obsdata/okrd01.dbf',
    '/u01/oracle/obsdata/okrx01.dbf',
    '/u01/oracle/obsdata/cued01.dbf',
    '/u01/oracle/obsdata/cuex01.dbf',
    '/u01/oracle/obsdata/fted01.dbf',
    '/u01/oracle/obsdata/ftex01.dbf',
    '/u01/oracle/obsdata/msrd01.dbf',
    '/u01/oracle/obsdata/msrx01.dbf',
    '/u01/oracle/obsdata/igid01.dbf',
    '/u01/oracle/obsdata/igix01.dbf',
    '/u01/oracle/obsdata/portal01.dbf',
    '/u01/oracle/obsdata/ahld01.dbf',
    '/u01/oracle/obsdata/ahlx01.dbf',
    '/u01/oracle/obsdata/ahmd01.dbf',
    '/u01/oracle/obsdata/ahmx01.dbf',
    '/u01/oracle/obsdata/aspd01.dbf',
    '/u01/oracle/obsdata/aspx01.dbf',
    '/u01/oracle/obsdata/bivd01.dbf',
    '/u01/oracle/obsdata/bivx01.dbf',
    '/u01/oracle/obsdata/csed01.dbf',
    '/u01/oracle/obsdata/csex01.dbf',
    '/u01/oracle/obsdata/csid01.dbf',
    '/u01/oracle/obsdata/csix01.dbf',
    '/u01/oracle/obsdata/csld01.dbf',
    '/u01/oracle/obsdata/cslx01.dbf',
    '/u01/oracle/obsdata/cugd01.dbf',
    '/u01/oracle/obsdata/cugx01.dbf',
    '/u01/oracle/obsdata/iecd01.dbf',
    '/u01/oracle/obsdata/iecx01.dbf',
    '/u01/oracle/obsdata/imcd01.dbf',
    '/u01/oracle/obsdata/imcx01.dbf',
    '/u01/oracle/obsdata/imtd01.dbf',
    '/u01/oracle/obsdata/imtx01.dbf',
    '/u01/oracle/obsdata/jtmd01.dbf',
    '/u01/oracle/obsdata/jtmx01.dbf',
    '/u01/oracle/obsdata/jtsd01.dbf',
    '/u01/oracle/obsdata/jtsx01.dbf',
    '/u01/oracle/obsdata/okbd01.dbf',
    '/u01/oracle/obsdata/okbx01.dbf',
    '/u01/oracle/obsdata/okid01.dbf',
    '/u01/oracle/obsdata/okix01.dbf',
    '/u01/oracle/obsdata/okod01.dbf',
    '/u01/oracle/obsdata/okox01.dbf',
    '/u01/oracle/obsdata/posd01.dbf',
    '/u01/oracle/obsdata/posx01.dbf',
    '/u01/oracle/obsdata/xnid01.dbf',
    '/u01/oracle/obsdata/xnix01.dbf',
    '/u01/oracle/obsdata/system07.dbf',
    '/u01/oracle/obsdata/system08.dbf',
    '/u01/oracle/obsdata/system09.dbf',
    '/u01/oracle/obsdata/rbs02.dbf',
    '/u01/oracle/obsdata/amfd01.dbf',
    '/u01/oracle/obsdata/amfx01.dbf',
    '/u01/oracle/obsdata/bned01.dbf',
    '/u01/oracle/obsdata/bnex01.dbf',
    '/u01/oracle/obsdata/csmd01.dbf',
    '/u01/oracle/obsdata/csmx01.dbf',
    '/u01/oracle/obsdata/dddd01.dbf',
    '/u01/oracle/obsdata/dddx01.dbf',
    '/u01/oracle/obsdata/domd01.dbf',
    '/u01/oracle/obsdata/domx01.dbf',
    '/u01/oracle/obsdata/egod01.dbf',
    '/u01/oracle/obsdata/egox01.dbf',
    '/u01/oracle/obsdata/ibcd01.dbf',
    '/u01/oracle/obsdata/ibcx01.dbf',
    '/u01/oracle/obsdata/okld01.dbf',
    '/u01/oracle/obsdata/oklx01.dbf',
    '/u01/oracle/obsdata/pjid01.dbf',
    '/u01/oracle/obsdata/pjix01.dbf',
    '/u01/oracle/obsdata/pond01.dbf',
    '/u01/oracle/obsdata/ponx01.dbf',
    '/u01/oracle/obsdata/qotd01.dbf',
    '/u01/oracle/obsdata/qotx01.dbf',
    '/u01/oracle/obsdata/qrmd01.dbf',
    '/u01/oracle/obsdata/qrmx01.dbf',
    '/u01/oracle/obsdata/discoverer01.dbf',
    '/u01/oracle/obsdata/cinvd01.dbf',
    '/u01/oracle/obsdata/cinvx01.dbf',
    '/u01/oracle/obsdata/cpod01.dbf',
    '/u01/oracle/obsdata/cpox01.dbf',
    '/u01/oracle/obsdata/capd01.dbf',
    '/u01/oracle/obsdata/capx01.dbf',
    '/u01/oracle/obsdata/card01.dbf',
    '/u01/oracle/obsdata/carx01.dbf',
    '/u01/oracle/obsdata/cqcd01.dbf',
    '/u01/oracle/obsdata/cqcx01.dbf',
    '/u01/oracle/obsdata/cfndd01.dbf',
    '/u01/oracle/obsdata/cfndx01.dbf',
    '/u01/oracle/obsdata/cgld01.dbf',
    '/u01/oracle/obsdata/cglx01.dbf',
    '/u01/oracle/obsdata/convd01.dbf',
    '/u01/oracle/obsdata/applsysd03.dbf',
    '/u01/oracle/obsdata/applsysx03.dbf',
    '/u01/oracle/obsdata/cwpld01.dbf',
    '/u01/oracle/obsdata/cwplx01.dbf',
    '/u01/oracle/obsdata/csyd01.dbf',
    '/u01/oracle/obsdata/csyx01.dbf',
    '/u01/oracle/obsdata/cpod02.dbf',
    '/u01/oracle/obsdata/csyd02.dbf'
    CHARACTER SET UTF8
    ALTER DATABASE OPEN RESETLOGS;
    DROP tablespace TEMP;
    DROP tablespace TEMPSYN;
    CREATE temporary tablespace TEMP TEMPFILE '/u01/oracle/obsdata/temp01.dbf'
         SIZE 1048576000 REUSE extent management local uniform size 128K;
    CREATE temporary tablespace TEMPSYN TEMPFILE '/u01/oracle/obsdata/tempsyn01.dbf'
         SIZE 1048576000 REUSE extent management local uniform size 128K;
    Edited by: amychan60 on Jun 17, 2009 9:30 PM

  • ORA-01161: database name

    DB 10.2.0.4
    AIX 5.2
    I am trying to make clone.Even I made clone, the database was up but when I saw in the alert log file it was giving continue below error(1) and the size of alert log file was getting increase so I decided to restore missed file and I restored and trying to create control file but this time it is giving below second(2) error.
    1:
    ORA-00376: file 35 cannot be read at this time
    ORA-01111: name for data file 35 is unknown - rename to correct file
    ORA-01110: data file 35: '/vol01/oracle/product/10g/dbs/MISSING00035'
    2:
    SQL> @clone.ctl
    CREATE CONTROLFILE SET DATABASE "dev" RESETLOGS
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01161: database name prod in file header does not match given name of dev
    ORA-01110: data file 35: '/vol01/oracle/index08.dbf'
    Suggest me.

    You could have missed that datafile in create controlfile statement, thats the reason for file naming convention to MISSING
    --okay but now what is the solution. That missing file does not physical exist at error location.                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • ORA-01504: database name 'DEV1' does not match parameter db_name 'PROD1'

    Hi, All -
    This is my first time cloning a database. The recovery finished but gave me the following error message. All the parameters in the pfile are set to "DEV1". I believe that the parameter db_name 'PROD1' exists in the control file and causing this error. The control file is under ASM.
    How can I change the parameter in the control file and bring the 'DEV1' cloned database up? Also, how can I avoid this issue next time I do a clone?
    Thanks in advance!
    Oracle 10g Release 2 on RHEL5
    Database cloning using RMAN Duplicate > ORA-01504: database name 'DEV1' does not match parameter db_name 'PROD1'
    ASMCMD> ls
    control01.ctl
    current.275.729098001
    archive log filename=/u001/dbsvr/dev1/1_131706_653848580.dbf recid=59 stamp=741953991
    media recovery complete, elapsed time: 00:09:31
    *Finished recover at 01-FEB-11*
    contents of Memory Script:
       shutdown clone;
       startup clone nomount ;
    executing Memory Script
    database dismounted
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area     725614592 bytes
    Fixed Size                     2075592 bytes
    Variable Size                448791608 bytes
    Database Buffers             268435456 bytes
    Redo Buffers                   6311936 bytes
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DEV1" RESETLOGS ARCHIVELOG
      MAXLOGFILES     50
      MAXLOGMEMBERS      5
      MAXDATAFILES      100
      MAXINSTANCES     1
      MAXLOGHISTORY     5445
    LOGFILE
      GROUP  1 '+DATA3/dev1/datafile/redo01.log' SIZE 100 M ,
      GROUP  2 '+DATA3/dev1/datafile/redo02.log' SIZE 100 M ,
      GROUP  3 '+DATA3/dev1/datafile/redo03.log' SIZE 100 M
    DATAFILE
      '+DATA3/dev1/datafile/system01.dbf'
    CHARACTER SET WE8ISO8859P1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 02/01/2011 10:30:17
    RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
    ORA-01504: database name 'DEV1' does not match parameter db_name 'PROD1'
    RMAN>
    RMAN> **end-of-file**
    RMAN>

    Respected, Sybrand Bakker -
    Thanks for constructive feedback!
    Here are the command that I ran.
    RMAN> connect target sys/<password>@PROD1
    connected to target database: PROD1 (DBID=556212836)
    RMAN> connect auxiliary sys/<password>
    connected to auxiliary database: DEV1 (not mounted)
    RMAN> @rman_dup.sql
    rman_dup.sql contains
    run {
        allocate auxiliary channel d1 type disk;
    set newname for datafile 1 to '+DATA3/dev/datafile/system01.dbf';
    set newname for datafile 2 to '+DATA3/dev/datafile/undotbs01.dbf';
    set newname for datafile 3 to '+DATA3/dev/datafile/cwmlite01.dbf';
    set newname for datafile 4 to '+DATA3/dev/datafile/drsys01.dbf';
    set newname for datafile 5 to '+DATA3/dev/datafile/example01.dbf';
    set newname for datafile 6 to '+DATA3/dev/datafile/indx01.dbf';
    set newname for datafile 7 to '+DATA3/dev/datafile/odm01.dbf';
    set newname for datafile 8 to '+DATA3/dev/datafile/tools01.dbf';
    set newname for datafile 9 to '+DATA3/dev/datafile/users01.dbf';
    set newname for datafile 10 to '+DATA3/dev/datafile/xdb01.dbf';
    set newname for datafile 11 to '+DATA3/dev/datafile/cons01.dbf';
    set newname for datafile 12 to '+DATA3/dev/datafile/survey01.dbf';
    set newname for datafile 13 to '+DATA3/dev/datafile/mem201.dbf';
    set newname for datafile 14 to '+DATA3/dev/datafile/cons02.dbf';
    set newname for datafile 15 to '+DATA3/dev/datafile/mem202.dbf';
    set newname for datafile 16 to '+DATA3/dev/datafile/cater01.dbf';
    set newname for datafile 17 to '+DATA3/dev/datafile/users02.dbf';
    set newname for datafile 18 to '+DATA3/dev/datafile/mar_data01.dbf';
    set newname for datafile 19 to '+DATA3/dev/datafile/sysaux01.dbf';
    set newname for datafile 20 to '+DATA3/dev/datafile/streams_tbs_01.dbf';
    set newname for datafile 21 to '+DATA3/dev/datafile/users03.dbf';
    set newname for tempfile 1 to '+DATA3/dev1/tempfile/temp01.dbf';
      duplicate target database to dev1
      until scn 48712532746
      logfile
       '+DATA3/dev1/datafile/redo01.log' size 100M,
       '+DATA3/dev1/datafile/redo02.log' size 100M,
       '+DATA3/dev1/datafile/redo03.log' size 100M;
    }Edited by: CipherDBA on Feb 3, 2011 10:50 AM

  • How to setup Data guard for SAP database?

    Can someone please tell me how to setup data guard for SAP databases?
    Thanks,
    Abhi

    Hi Abhi,
    have a look at OSS 105047 - Support for Oracle functions in the SAP environment you find this under
    14
    Oracle Data Guard
    You can use "Physical Standby".
    You cannot use "Logical Standby".
    You are allowed to use Fast Start Failover (FSFO) but SAP Support is not provided.
    You can use Data Guard Broker.
    You can use Maximum Performance Mode, Maximum Availability Mode and Maximum Protection Mode.
    In the case of Maximum Availability and Maximum Protection, you must pay particular attention to a fast network connection in order to avoid performance problems.
    Maximum Protection causes the primary database to terminate if problems occur in the standby database.
    And here you find on Oracle white paper from 2010 http://www.oracle.com/us/solutions/sap/wp-ora4sap-dataguard11g-303811.pdf
    Perhaps some SAP user have answers for you http://scn.sap.com/community/oracle/content?query=guard
    regards
    Kay

  • 11g data Guard

    Hi,
    Please provide me the document to configure 11g Data Guard
    Regds

    hi,
    Please read this document Oracle® Data Guard Concepts and Administration 11g Release 2 (11.2)
    http://download.oracle.com/docs/cd/E11882_01/server.112/e10700/concepts.htm#i1039416
    Thanks,
    Ajikumar G
    Expertise in Oracle Apps...

  • ORA-04091: table name is mutating, trigger/function may not see it

    Hi,
    I have a row level before update trigger written on a table A which calls a procedure to undergo some processing. Procedure has some select queries against table A and it inturn causes the following error.
    ORA-04091: table name is mutating, trigger/function may not see it
    To overcome this I have used a combination of PL/SQL collection types (nested tables based on the following definition TYPE t_table_a is table of A.colname%TYPE index by binary_integer;), a row level before update trigger and statement level after update trigger. The mutating problem is fixed, but to update one row of data it took around 3 min and I am wondering if its the problem with PL/SQL tables I have used.
    In before update trigger I am storing the unique id's which needs to be updated into the PL/SQL table and in the after update trigger I am looping through the PL/SQL table and peforming the rest of the processing by calling in the procedure.
    Can anyone help how to minimize the run time of this process or if any other better solution exists?
    Thanks for the help

    Triggers raise the mutating table issue, because else they could be used to create endless loops. If you work around the mutating table issue, then you should make sure not to create an endless loop yourself. This would be possible.
    You description also seems to imply something like this.
    Without code it is impossible to say something specific.
    - Do you initialize your collection in a before statement trigger?
    - Is your looping mechanism somehow broken?
    - Do you update the same table again and again and again?

  • Can I make a Data Guard configuration using EM console without Grid Control

    Can I make a Data Guard configuration using EM console without Grid Console?
    Can I download Grid Console software from Oracle website without cost?

    Assuming this is for 10g,
    You could use Oracle® Data Guard Broker
    Even you can download Grid Control software for free from Oracle site, you can't legally use it without license.

Maybe you are looking for

  • UME Service suddenly stopped and now does not start

    Hello experts, a weird problem has come up to my attention. A few days ago our Enterprise Portal suddenly went down and when we restarted all services, the UME Service did not start. We tried restarting the whole server, to no avail. This service jus

  • Memory leak in LoadVars?

    Hi, In one of our apps, we've a need to continuously load new data (using Loadvars) every x seconds from the server. However, I seem to be having a memory leak issue when doing the same. Consider the following skeletal code: var myVars:LoadVars = new

  • How IE works for  flat file

    Hi all:      As we all know that, when IE gets a idoc's service name from SLD, then use it with idoc's message type and Idoc type to do receiver determniation, what about flat file ? how can we know its Service name and interface name  if there is on

  • Not able to start OID 11g

    Hi Everyone, All of a sudden I am not able to start ODS instance that includes (OID and OVD). I can see OVD process is up but not OID. DB and listeners are up and running. Any quick thoughts ? Thanks

  • Contacts Despair

    I have a Nokia 5300 XpressMusic, and have bought a 5800 XpressMusic today. The problem with my 5300 was that the top keyboard had stopped working. Before it stopped working completely, though, I was able to export my contacts, just in case. I saved t