Standby destination control file enqueue unavailable

Hi,
more than two days ..totally i tried 3 times for creating standby database in oralce 10g ..everthing working fine but i didnt get archive log from primary database..please help me
NOTE: both primary and standby database on same system
*#standby database 'stby' (omitted common parameters)*
*.compatible='10.2.0.3.0'
*.control_files='d:\oracle\product\10.2.0\oradata\stby\controlsb01.ctl','d:\oracle\product\10.2.0\oradata\stby\controlsb02.ctl','d:\oracle\product\10.2.0\oradata\stby\controlsb03.ctl'
*.db_file_name_convert='D:\oracle\product\10.2.0\oradata\live','D:\oracle\product\10.2.0\oradata\stby'
*.db_name='live'
*.fal_client='stby'
*.fal_server='live'
*.log_archive_config='DG_CONFIG=(live,stby)'
*.log_archive_dest_1='LOCATION=D:\oracle\product\10.2.0\flash_recovery_area\stby VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=stby'
*.log_archive_dest_2='SERVICE=live ARCH ASYNC VALID_FOR=(ONLINE_LOGFILE,PRIMARY_ROLE) DB_UNIQUE_NAME=live'
*.log_file_name_convert='D:\oracle\product\10.2.0\oradata\live','D:\oracle\product\10.2.0\oradata\stby'
*.remote_login_passwordfile=EXCLUSIVE
*.standby_file_management='AUTO'
*.instance_name=stby
*.db_unique_name=stby
*#primary database 'live'*
*.compatible='10.2.0.3.0'
*.control_files='d:\oracle\product\10.2.0\oradata\live\control01.ctl','d:\oracle\product\10.2.0\oradata\live\control02.ctl','d:\oracle\product\10.2.0\oradata\live\control03.ctl'
*.db_file_name_convert='D:\oracle\product\10.2.0\oradata\stby','D:\oracle\product\10.2.0\oradata\live'
*.db_name='live'
*.fal_client='live'
*.fal_server='stby'
*.log_archive_config='DG_CONFIG=(live,stby)'
*.log_archive_dest_1='LOCATION=D:\oracle\product\10.2.0\flash_recovery_area\live VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=live'
*.log_archive_dest_2='SERVICE=stby ARCH ASYNC VALID_FOR=(ONLINE_LOGFILE,PRIMARY_ROLE) DB_UNIQUE_NAME=stby'
*.log_file_name_convert='D:\oracle\product\10.2.0\oradata\stby','D:\oracle\product\10.2.0\oradata\live'
*.remote_login_passwordfile=EXCLUSIVE
*.standby_file_management='AUTO'
*.instance_name=live
*.DB_UNIQUE_NAME=live
*#standby database*
SQL> STARTUP MOUNT
ORACLE instance started.
Total System Global Area 251658240 bytes
Fixed Size 1290012 bytes
Variable Size 159383780 bytes
Database Buffers 83886080 bytes
Redo Buffers 7098368 bytes
Database mounted.
SQL> alter database recover managed standby database disconnect from session;
Database altered.
SQL> select group#,member from v$logfile;
GROUP#
MEMBER
3
D:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\REDO03.LOG
2
D:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\REDO02.LOG
1
D:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\REDO01.LOG
GROUP#
MEMBER
4
D:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\SREDO04.LOG
5
D:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\SREDO05.LOG
6
D:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\SREDO06.LOG
6 rows selected.
*#primary database*
SQL> ALTER SYSTEM SWITCH LOGFILE;
SQL> select SEQUENCE#, applied from v$archived_log;
SEQUENCE# APP
15 NO
16 NO
17 NO
18 NO
19 NO
20 NO
SQL> SELECT SEQUENCE#,STATUS FROM V$MANAGED_STANDBY;
SEQUENCE# STATUS
0 CONNECTED
19 CLOSING
20 CLOSING
0 CONNECTED
0 CONNECTED
0 CONNECTED
0 CONNECTED
0 CONNECTED
*#standby database*
SQL> select * from v$archived_log;
no rows selected
*#see even my standby database open .*
SQL> alter database open;
Database altered.
*# listener.ora*
STBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = selvaPC)(PORT = 2031))
LIVE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = selvaPC)(PORT = 2030))
SID_LIST_STBY =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = live)
(SID_NAME = stby)
SID_LIST_LIVE =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = live)
(SID_NAME = live)
*# tnsnames.ora*
STBY =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = selvaPC)(PORT = 2030))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = live)
LIVE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = selvaPC)(PORT = 2031))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = stby)
*#Error in alert file..during startup primary database*
Controlfile lock conflict at host 'stby'
Possible invalid cross-instance archival configuration
ORA-16146: standby destination control file enqueue unavailable
thanks
selva..

If you user this then a lot of information ( threads) can be found with the same problem.
Anyway the original ORA-message/solution is:
Error:     ORA-16146 (ORA-16146)
Text:     standby destination control file enqueue unavailable
Cause:     The target standby destination control file is currently
     unavailable to the Remote File Server (RFS) process. This
     indicates that the target destination is the primary database
     itself.
Action:     Check for and eliminate the standby destination archive log
     parameter in question.
This means you have an error in the log_archive_dest entries on the standby server.
Can you use Dataguard Manager (dgmgrl) to verify the configuration?
Edit:
Our Dataguard config e.g. has on primary:
log_archive_config='dg_config=(STDBY)'
On the standby it is:
log_archive_config='dg_config=(PRIMARY)'

Similar Messages

  • ORA-00230: operation disallowed: snapshot control file enqueue unavailable

    Hi,
    on 10g R2, on Win 2003
    my rman backup failed (just at the end) with :
    release channel 000
    ORA-00230: operation disallowed: snapshot control file enqueue unavailable1-should I rerun the back up task ?
    2-how to verify if this backup is correct/good ?
    PS : I use nocatalog (controlfile for repository)
    Thank you.

    1-should I rerun the back up task ?appear its failed during controlfile backup if database backup log fine than just take controlfile backup.
    2-how to verify if this backup is correct/good ?in 10g ,we can see status in v$rman_status view,it also show any other running job as well.
    select * from (select SID ,recid   ,STATUS,operation,MBYTES_PROCESSED/1024 "GB",START_TIME,END_TIME from v$rman_status order by start_time desc) where rownum <11

  • Drop a datafile from physical standby's control file

    Hi,
    I am trying to create a physical standby database for my production...
    1) I have taken cold backup of my primary database on 18-Nov-2013...
    2) I added a datafile on 19-nov-2013 ( 'O:\ORADATA\SFMS\SFMS_DATA4.DBF' )
    3) Standby control file was generated on 20-ov-2013 (today) after shutting down and then mounting the primary database...
    When i try to recover the newly setup standby using archive files, i am getting the following error (datafile added on 19th Nov is missing)
    SQL> recover standby database;
    ORA-00283: recovery session canceled due to errors
    ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    ORA-01157: cannot identify/lock data file 39 - see DBWR trace file
    ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    How to overcome this situation...
    Can i delete the entry for the newly added datafile from the backup control file ?
    When i tried to delete datafile using "alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF';", it is showing that database should be  open..
    SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    ERROR at line 1:
    ORA-01109: database not open
    SQL> show parameter STANDBY_FILE_MANAGEMENT
    NAME                                 TYPE        VALUE
    standby_file_management              string      AUTO
    SQL> alter system set STANDBY_FILE_MANAGEMENT=manual;
    System altered.
    SQL> show parameter STANDBY_FILE_MANAGEMENT
    NAME                                 TYPE        VALUE
    standby_file_management              string      MANUAL
    SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    ERROR at line 1:
    ORA-01109: database not open
    Regards,
    Jibu

    Jibu wrote:
    Hi,
    I am trying to create a physical standby database for my production...
    1) I have taken cold backup of my primary database on 18-Nov-2013...
    2) I added a datafile on 19-nov-2013 ( 'O:\ORADATA\SFMS\SFMS_DATA4.DBF' )
    3) Standby control file was generated on 20-ov-2013 (today) after shutting down and then mounting the primary database..
    Hi,
    What is your version?
    If you added new datafile or created new tablespace, take backup again for restore new created standby database.
    If your standby  database running well, DG configuration success, then this datafile will create on standby side, too.
    Set STANDBY_FILE_MANAGEMENT=AUTO best practice.
    When i try to recover the newly setup standby using archive files, i am getting the following error (datafile added on 19th Nov is missing)
    SQL> recover standby database;
    ORA-00283: recovery session canceled due to errors
    ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    ORA-01157: cannot identify/lock data file 39 - see DBWR trace file
    ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    How to overcome this situation...
    Can i delete the entry for the newly added datafile from the backup control file ?
    Not need any delete datafile from standby side, you must recreate standby database, or you can  take RMAN backup and restore to standby  side again.
    When i tried to delete datafile using "alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF';", it is showing that database should be  open..
    SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    ERROR at line 1:
    ORA-01109: database not open
    SQL> show parameter STANDBY_FILE_MANAGEMENT
    NAME                                 TYPE        VALUE
    standby_file_management              string      AUTO
    SQL> alter system set STANDBY_FILE_MANAGEMENT=manual;
    System altered.
    SQL> show parameter STANDBY_FILE_MANAGEMENT
    NAME                                 TYPE        VALUE
    standby_file_management              string      MANUAL
    SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    ERROR at line 1:
    ORA-01109: database not open
    It is not logical, Physical  standby must be bit-for-bit same with Primary  database.
    Regards
    Mahir M. Quluzade

  • Whwn to create a standby control file?

    Hi All ,
    I want to setup a standby database for my Production DB.
    I have a doubt, can we create a Standby by control file when the Primary database is up and running(read-write) mode. or else it is must to be in mount state only ?
    Please advise.
    Thanks.

    Hello;
    I do it like this: (And then copy the STANDBY.ctl to the Standby system and rename)
    SQL>startup mount;
    SQL>alter database create standby controlfile as 'STANDBY.ctl';
    This command will fail is STANDBY.ctl exists.
    See step 8 of my cliff notes here:
    http://www.visi.com/~mseberg/data_guard_on_oracle_10_step_by_step.html
    Or Step 7 if Oracle 11 here:
    http://www.visi.com/~mseberg/data_guard_on_oracle_11_step_by_step.html
    Best Regards
    mseberg

  • Control file lock time in rac

    Hi all,
    Database version 11.2.0.2
    Os version Red hat 5.3
    Two node RAC
    What is the default control file lock time in rac environment i am getting error after 120 seconds.
    The default lock time in single instance is 900 seconds.
    Does in rac this time lowered to 120 seconds.
    error in alert log file
    Errors in file /u01/app/oracle/diag/rdbms/lfgoimdb/LFGoimdb2/trace/LFGoimdb2_arc2_27691.trc (incident=15905):
    ORA-00240: control file enqueue held for more than 120 seconds
    After hitting this error I have observed that another node evicts this node.

    The above link state that it is a bug in previous versions but i am in recent version 11.2.0.2.5 and this bug is resolved in this version.

  • Problem in identifying control file when creating physical standby

    hi there,
    (database version: 10.2.0.4
    plateform linux)
    I'm using the command as below to create physical standby database from backup:
    rman target / auxiliary sys/tiger@paceview
    Recovery Manager: Release 10.2.0.4.0 - Production on Tue Sep 4 18:05:53 2012
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    connected to target database: PACEVIEW (DBID=2092349485)
    connected to auxiliary database: PACEVIEW (not mounted)
    run {
    allocate auxiliary channel c1 device type DISK;
    set until sequence 38;
    duplicate target database for standby dorecover nofilenamecheck;
    released channel: ORA_DISK_1
    allocated channel: c1
    channel c1: sid=35 devtype=DISK
    allocated channel: c2
    channel c2: sid=36 devtype=DISK
    executing command: SET until clause
    Starting Duplicate Db at 04-SEP-12
    contents of Memory Script:
       set until scn  138180211934;
       restore clone standby controlfile;
       sql clone 'alter database mount standby database';
    executing Memory Script
    executing command: SET until clause
    Starting restore at 04-SEP-12
    channel c1: restoring control file
    ORA-19625: error identifying file /backup/rman/paceview/DEL1_standby.ctl
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-19600: input file is control file  (/backup/rman/paceview/DEL1_standby.ctl)
    ORA-19601: output file is control file  (/PGHProdDB/oradata/paceview/control1.ctl)
    failover to previous backup
    released channel: c1
    released channel: c2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/04/2012 18:01:44
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06024: no backup or copy of the control file found to restorei have already tried crosscheck but still giving same error
    thanks

    Hello;
    So this is what I would do :
    Backup Primary ( change to your directory as need )
    RMAN RUN {
    allocate channel d1 type disk;
    backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
    sql 'alter system archive log current';
    backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
    backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
    release channel d1;
    }Move the backup and duplicate like this :
    rman target sys/password@PRIMARY auxiliary /
    RMAN> run {
    allocate channel C1 device type disk;
    allocate auxiliary channel C2 device type disk;
    duplicate target database for standby nofilenamecheck;
    }For complete details of this method see :
    http://www.visi.com/~mseberg/duprman2.html
    Best Regards
    mseberg

  • Reg Creating Physical Standby Control File

    Hi,
    I am trying to create a physical standby in the same server in a different partition.
    I have copied the home and changed the init.ora file.
    I have created listeners.
    I did creating standby Control file Using
    alter database create standby controlfile as '/some/path/to/a/file'
    Then i copied the datafiles from primary to standby and when i tried to mount the database it gives error
    RACLE instance started.
    Total System Global Area 285212672 bytes
    Fixed Size 1267044 bytes
    Variable Size 88083100 bytes
    Database Buffers 188743680 bytes
    Redo Buffers 7118848 bytes
    ORA-01103: database name 'WMSTDBY' in control file is not 'WMTEST'
    My Primary Sid is WMSTDBY
    My Standby SId is WMTEST.
    Please help in this regard.
    Krishna.V.V

    You cannot change the DB_NAME of the standby. It has to be the same as the Primary. You can change (and should) the INSTANCE_NAME (SID) and the DB_UNIQUE_NAME parameters to WMTEST.
    Larry

  • Creating a standby control file for cloning a standby database

    Hi
    I am in the process of trying to document the cloning of a standby database. I am trying to amalgamate three different documents - one for a normal clone, one for the creation of a SB database, and the other a formal Oracle document - the Business Continuity doc.
    Among the several things that confuse me, is the issue of creating (or not) a standby control file.
    I am not doing any kind of data file deletion / copying from source to target, as the SB database is updated all day with data file changes. I am doing a complete copying over of the APPL_TOP and techstacks.
    My question then, is this: should I be worried about creating a standby control file? I am told by our Senior here that "you can get away with not doing it", which sounds like too much of a risk to me.
    I am under a bit of pressure for this and I am not 100% sure about certain issues (see my other post for knowing how many DATA_TOPS we have on the SB, for instance).
    Thanks for listening.
    AIX 5.2.
    Oracle 10g.
    DA

    Do you already have a Standby running ? (then it may be using a standby controlfile).
    Yes. And there is already a standby control file there. It seems to me, that if the data (logs) transfers are done each minute or whatever between source and SB, and the SB is a copy of the db, then we dont need to worry about any kind of data files, since they should be identical. The only things I will need to change are the configuration files like the ifile in both dbs and tns_names, listener, tnsnames.ora, and the init.ora.
    b. Are you creating a document about the process of creating standby from production ? If you plan to use DataGuard, you will need a standby controlfile. Otherwise , it depends on how you configure the standby.
    No. I am creating a doc for how to clone from Production to a SB environment. A reason behind this is that the Apps side of the SB is about 9 patches behind the Production box, and we need to update it. I believe this is the main reason for doing this.
    c. Just to check : You are NOT using Storage Mirroring -- ie D.R. ?
    No, no DR on this environment.
    Thanks.
    DA

  • 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-01665 : control file is not a standby control file

    I've already tested Dataguard configuration on Oracle 10g Enterprise edition for Windows.
    While configuring the same in Sun Solaris, I'm receiving this error:
    ORA-01665: control file is not a standby control file
    Steps I follow are as below:
    1) Creating a password file on both databases (primary and standby)
    2) Force logging primary db and shut it down. Take a cold backup of redo log files and datafiles.
    3) Transferring them to Standby db.
    4) Starting primary db in mount mode and creating a standby controlfile. Transferring standby controlfile to proper location defined in standby init file.
    5) Start primary db in read-write mode and secondary db in mount mode using:
    alter database mount standby database;
    I receive this error while firing this SQL.
    Can anyone please help me out solving the same.

    I'm already done with the same. Find log below:
    bash-3.00$ sqlplus sys/sys123@orcl as sysdba
    SQL*Plus: Release 10.2.0.1.0 - Production on Thu Feb 19 11:54:29 2009
    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>
    SQL>
    SQL> alter database create standby controlfile as '/export/home/oracle/abc/control4.ctl';
    Database altered.
    SQL> alter database create standby controlfile as '/export/home/oracle/abc/control5.ctl';
    Database altered.
    SQL>

  • Control file failed error while duplicating database using RMAN

    I am using oracle database 10g R2 and trying to make a clone of the source database orcl on the same machine but with different directory structure with the name of test.
    When i run the duplicate command to create test database, then following error is generted:
    D:\>rman target sys@orcl nocatalog auxiliary /
    Recovery Manager: Release 10.2.0.1.0 - Production on Fri Nov 11 12:13:26 2011
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    target database Password:
    connected to target database: ORCL (DBID=1264668332)
    using target database control file instead of recovery catalog
    connected to auxiliary database: TEST (not mounted)
    RMAN> @script.txt
    RMAN> Run {
    2> Allocate channel C1 type disk;
    3> allocate auxiliary channel 'adisk_0' type DISK;
    4> duplicate target database to "test";
    5> #BACKUP INCREMENTAL LEVEL 1 DATABASE;
    6> #BACKUP INCREMENTAL LEVEL 1 CUMULATIVE DATABASE;
    7> #BACKUP INCREMENTAL LEVEL 0 DATABASE;
    8> #delete obsolete;
    9> }
    allocated channel: C1
    channel C1: sid=140 devtype=DISK
    allocated channel: adisk_0
    channel adisk_0: sid=157 devtype=DISK
    Starting Duplicate Db at 11-NOV-11
    contents of Memory Script:
       set until scn  12926250;
       set newname for datafile  1 to
    "D:\TEST\ORADATA\SYSTEM01.DBF";
       set newname for datafile  2 to
    "D:\TEST\ORADATA\UNDOTBS01.DBF";
       set newname for datafile  3 to
    "D:\TEST\ORADATA\SYSAUX01.DBF";
       set newname for datafile  4 to
    "D:\TEST\ORADATA\USERS01.DBF";
       set newname for datafile  5 to
    "D:\TEST\ORADATA\EXAMPLE01.DBF";
       set newname for datafile  6 to
    "D:\TEST\ORADATA\GL.DBF";
       restore
       check readonly
       clone database
    executing Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 11-NOV-11
    channel adisk_0: starting datafile backupset restore
    channel adisk_0: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to D:\TEST\ORADATA\SYSTEM01.DBF
    restoring datafile 00002 to D:\TEST\ORADATA\UNDOTBS01.DBF
    restoring datafile 00003 to D:\TEST\ORADATA\SYSAUX01.DBF
    restoring datafile 00004 to D:\TEST\ORADATA\USERS01.DBF
    restoring datafile 00005 to D:\TEST\ORADATA\EXAMPLE01.DBF
    restoring datafile 00006 to D:\TEST\ORADATA\GL.DBF
    channel adisk_0: reading from backup piece D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_07\O1_MF_NNND0_TAG20111107T220822_7CJ
    P
    channel adisk_0: restored backup piece 1
    piece handle=D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_07\O1_MF_NNND0_TAG20111107T220822_7CJ44MH4_.BKP tag=TAG20111107T220
    channel adisk_0: restore complete, elapsed time: 00:01:46
    Finished restore at 11-NOV-11
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "TEST" RESETLOGS ARCHIVELOG
      MAXLOGFILES     16
      MAXLOGMEMBERS      3
      MAXDATAFILES      100
      MAXINSTANCES     8
      MAXLOGHISTORY      292
    LOGFILE
      GROUP  1 ( 'D:\TEST\ORADATA\REDO01.LOG' ) SIZE 50 M  REUSE,
      GROUP  2 ( 'D:\TEST\ORADATA\REDO02.LOG' ) SIZE 50 M  REUSE,
      GROUP  3 ( 'D:\TEST\ORADATA\REDO03.LOG' ) SIZE 50 M  REUSE
    DATAFILE
      'D:\TEST\ORADATA\SYSTEM01.DBF'
    CHARACTER SET WE8MSWIN1252
    contents of Memory Script:
       switch clone datafile all;
    executing Memory Script
    datafile 2 switched to datafile copy
    input datafile copy recid=1 stamp=766930525 filename=D:\TEST\ORADATA\UNDOTBS01.DBF
    datafile 3 switched to datafile copy
    input datafile copy recid=2 stamp=766930525 filename=D:\TEST\ORADATA\SYSAUX01.DBF
    datafile 4 switched to datafile copy
    input datafile copy recid=3 stamp=766930526 filename=D:\TEST\ORADATA\USERS01.DBF
    datafile 5 switched to datafile copy
    input datafile copy recid=4 stamp=766930526 filename=D:\TEST\ORADATA\EXAMPLE01.DBF
    datafile 6 switched to datafile copy
    input datafile copy recid=5 stamp=766930526 filename=D:\TEST\ORADATA\GL.DBF
    contents of Memory Script:
       set until scn  12926250;
       recover
       clone database
        delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 11-NOV-11
    channel adisk_0: starting incremental datafile backupset restore
    channel adisk_0: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00001: D:\TEST\ORADATA\SYSTEM01.DBF
    destination for restore of datafile 00002: D:\TEST\ORADATA\UNDOTBS01.DBF
    destination for restore of datafile 00003: D:\TEST\ORADATA\SYSAUX01.DBF
    destination for restore of datafile 00004: D:\TEST\ORADATA\USERS01.DBF
    destination for restore of datafile 00005: D:\TEST\ORADATA\EXAMPLE01.DBF
    destination for restore of datafile 00006: D:\TEST\ORADATA\GL.DBF
    channel adisk_0: reading from backup piece D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_09\O1_MF_NNND1_TAG20111109T223628_7CO
    P
    channel adisk_0: restored backup piece 1
    piece handle=D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_09\O1_MF_NNND1_TAG20111109T223628_7COGJZVT_.BKP tag=TAG20111109T223
    channel adisk_0: restore complete, elapsed time: 00:00:07
    channel adisk_0: starting incremental datafile backupset restore
    channel adisk_0: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00001: D:\TEST\ORADATA\SYSTEM01.DBF
    destination for restore of datafile 00002: D:\TEST\ORADATA\UNDOTBS01.DBF
    destination for restore of datafile 00003: D:\TEST\ORADATA\SYSAUX01.DBF
    destination for restore of datafile 00004: D:\TEST\ORADATA\USERS01.DBF
    destination for restore of datafile 00005: D:\TEST\ORADATA\EXAMPLE01.DBF
    destination for restore of datafile 00006: D:\TEST\ORADATA\GL.DBF
    channel adisk_0: reading from backup piece D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_10\O1_MF_NNND1_TAG20111110T221428_7CR
    P
    channel adisk_0: restored backup piece 1
    piece handle=D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_10\O1_MF_NNND1_TAG20111110T221428_7CR1MQFO_.BKP tag=TAG20111110T221
    channel adisk_0: restore complete, elapsed time: 00:00:16
    starting media recovery
    archive log thread 1 sequence 524 is already on disk as file D:\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2011_11_11\O1_MF_1_524_7CS
    C
    archive log filename=D:\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2011_11_11\O1_MF_1_524_7CSG2HVT_.ARC thread=1 sequence=524
    media recovery complete, elapsed time: 00:00:14
    Finished recover at 11-NOV-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     230686720 bytes
    Fixed Size                     1248236 bytes
    Variable Size                 67109908 bytes
    Database Buffers             155189248 bytes
    Redo Buffers                   7139328 bytes
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "TEST" RESETLOGS ARCHIVELOG
      MAXLOGFILES     16
      MAXLOGMEMBERS      3
      MAXDATAFILES      100
      MAXINSTANCES     8
      MAXLOGHISTORY      292
    LOGFILE
      GROUP  1 ( 'D:\TEST\ORADATA\REDO01.LOG' ) SIZE 50 M  REUSE,
      GROUP  2 ( 'D:\TEST\ORADATA\REDO02.LOG' ) SIZE 50 M  REUSE,
      GROUP  3 ( 'D:\TEST\ORADATA\REDO03.LOG' ) SIZE 50 M  REUSE
    DATAFILE
      'D:\TEST\ORADATA\SYSTEM01.DBF'
    CHARACTER SET WE8MSWIN1252
    released channel: C1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 11/11/2011 12:16:21
    RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
    ORA-01504: database name 'TEST' does not match parameter db_name 'orcl'
    RMAN> **end-of-file**
    Script.txt
    Run {
    Allocate channel C1 type disk;
    allocate auxiliary channel 'adisk_0' type DISK;
    duplicate target database to "test";
    }Kindly help?

    Moazzam wrote:
    RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
    ORA-01504: database name 'TEST' does not match parameter db_name 'orcl'
    Kindly help?>Please check what is the value of parameter db_name in the standby database? It should be match with TEST name
    Cheers

  • Need a help: how to recover using backup control file?

    Please a help:
    First computer
    1. I create a database
    2. put it in archive mode,
    3. shutdown and made a cold backup
    4. Created backup control file (alter database backup control file to trace)
    5. I started up and created some archived log files.
    Second Computer
    1. I copied all files created in the step 3 above except the control file
    2. I create all the same map directory on the 2nd computer as in the 1st computer
    3. I recreate the control file from the script got in the step 4 above
    4. I Copy archived log files generated at the step 5 in the local directory in the second computer
    5. I set the logsource and set the autorecovery to on
    6. I recover the database: RECOVER DATABASE USING BACKUP CONTROL FILE UNTIL CANCEL
    Error got:
    the archived log file applied do not go beyond the first one?,How could I do to applied all archived log files copied from the first computer to the second computer to have the same data?
    Thank you very much

    archived log sequeces in the first computerSQL> select sequence#,first_change#,next_change# from v$log_history;
    SEQUENCE# FIRST_CHANGE# NEXT_CHANGE#
    1 553723 555484
    2 555484 557345
    Actions I did in the second Computer(after copied the former two archived log files from the 1st computer)
    SQL> CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS ARCHIVELOG
    2 MAXLOGFILES 16
    3 MAXLOGMEMBERS 3
    4 MAXDATAFILES 100
    5 MAXINSTANCES 8
    6 MAXLOGHISTORY 292
    7 LOGFILE
    8 GROUP 1 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG' SIZE 50M,
    9 GROUP 2 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG' SIZE 50M,
    10 GROUP 3 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG' SIZE 50M
    11 -- STANDBY LOGFILE
    12 DATAFILE
    13 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF',
    14 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF',
    15 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF',
    16 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF'
    17 CHARACTER SET WE8ISO8859P1
    18 ;
    Control file created.
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Disabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 0
    Next log sequence to archive 0
    Current log sequence 0
    SQL> alter database archivelog;
    Database altered.
    SQL> set logsource C:\local_destination1_orcl
    SQL> set autorecovery on;
    SQL> recover database using backup controlfile until cancel;
    ORA-00279: change 555611 generated at 01/18/2007 14:14:14 needed for thread 1
    ORA-00289: suggestion :
    C:\LOCAL_DESTINATION1_ORCL\ARCH.1_1_612194518_43F17CF5.ARC
    ORA-00280: change 555611 for thread 1 is in sequence #1
    ORA-00328: archived log ends at change 555483, need later change 555611
    ORA-00334: archived log:
    'C:\LOCAL_DESTINATION1_ORCL\ARCH.1_1_612194518_43F17CF5.ARC'
    Idon't know where the change 555611 is coming from?

  • Cannot recover control file in Oracle10g

    Dear friends ,
    I have to delete my three control files for testing purpose in ORacle 10g .Before Deleting , I take a backup with control file and spfile using following way :
    script :
    run
    allocate channel t1 type disk;
    backup format 'df_%t_%s_%p'
    (database);}
    AND OUTPUT of RMAN ,
    RMAN> show all;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'C:\TEMP\ctrl_file%F';
    Now when I run the restore script then it shows follwing error :
    RMAN> set DBID=1178861114;
    executing command: SET DBID
    RMAN> restore controlfile from autobackup db_recovery_file_dest='C:\TEMP\CTRL_FILEC-1178861114-20080413-00';
    Starting restore at 13-APR-08
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=158 devtype=DISK
    recovery area destination: C:\TEMP\CTRL_FILEC-1178861114-20080413-00
    database name (or database unique name) used for search: ORCL
    channel ORA_DISK_1: no autobackups found in the recovery area
    channel ORA_DISK_1: looking for autobackup on day: 20080413
    channel ORA_DISK_1: looking for autobackup on day: 20080412
    channel ORA_DISK_1: looking for autobackup on day: 20080411
    channel ORA_DISK_1: looking for autobackup on day: 20080410
    channel ORA_DISK_1: looking for autobackup on day: 20080409
    channel ORA_DISK_1: looking for autobackup on day: 20080408
    channel ORA_DISK_1: looking for autobackup on day: 20080407
    channel ORA_DISK_1: no autobackup in 7 days found
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 04/13/2008 10:35:34
    RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
    I dont know why my control files are not backed up ? can anybody plz help me ?

    I can't say why what you did didn't work but I can say that using RMAN is not the best way to recover lost control files.
    Lets assume you have three control files located on three different drives. It is impossible to accidentally delete all three so the best solution to losing one is to shutdown the database and copy an existing one to the location where a file has gone missing and rename it to the name of the deleted file.
    Failing that you should always have a script created using:
    BACKUP CONTROLFILE TO TRACE;I would only use the control files backed up by RMAN to create an auxiliary database such as a standby or for testing.

  • 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.

  • Creation of control file failed

    Hi all
    when i am trying to create control file my terminal is hanging on following stage
    SQL> @/u02/ORACLE/orcldb/9.2.0/dbs/contrl.sql
    ORACLE instance started.
    Total System Global Area 581506668 bytes
    Fixed Size 452204 bytes
    Variable Size 402653184 bytes
    Database Buffers 167772160 bytes
    Redo Buffers 10629120 bytes
    54
    and in alert log file no error are given

    Hi
    Thanks for your reply
    i am pasting whole sql file here please check it and tell me if any error are there ?
    STARTUP NOMOUNT
    CREATE CONTROLFILE SET DATABASE "ORCL" NORESETLOGS ARCHIVELOG
    -- SET STANDBY TO MAXIMIZE PERFORMANCE
    MAXLOGFILES 32
    MAXLOGMEMBERS 5
    MAXDATAFILES 512
    MAXINSTANCES 8
    MAXLOGHISTORY 7260
    LOGFILE
    GROUP 1 (
    '/u02/ORACLE/orcldata/log01a.dbf',
    '/u02/ORACLE/orcldata/log01b.dbf'
    ) SIZE 10M,
    GROUP 2 (
    '/u02/ORACLE/orcldata/log02a.dbf',
    '/u02/ORACLE/orcldata/log02b.dbf'
    ) SIZE 10M
    -- STANDBY LOGFILE
    DATAFILE
    '/u02/ORACLE/orcldata/system01.dbf',
    '/u02/ORACLE/orcldata/system02.dbf',
    '/u02/ORACLE/orcldata/system03.dbf',
    '/u02/ORACLE/orcldata/system04.dbf',
    '/u02/ORACLE/orcldata/system05.dbf',
    '/u02/ORACLE/orcldata/ctxd01.dbf',
    '/u02/ORACLE/orcldata/owad01.dbf',
    '/u02/ORACLE/orcldata/a_queue02.dbf',
    '/u02/ORACLE/orcldata/odm.dbf',
    '/u02/ORACLE/orcldata/olap.dbf',
    '/u02/ORACLE/orcldata/system10.dbf',
    '/u02/ORACLE/orcldata/system06.dbf',
    '/u02/ORACLE/orcldata/portal01.dbf',
    '/u02/ORACLE/orcldata/system07.dbf',
    '/u02/ORACLE/orcldata/system09.dbf',
    '/u02/ORACLE/orcldata/system08.dbf',
    '/u02/ORACLE/orcldata/system11.dbf',
    '/u02/ORACLE/orcldata/undo01.dbf',
    '/u02/ORACLE/orcldata/a_txn_data01.dbf',
    '/u02/ORACLE/orcldata/a_txn_ind01.dbf',
    '/u02/ORACLE/orcldata/a_ref01.dbf',
    '/u02/ORACLE/orcldata/a_int01.dbf',
    '/u02/ORACLE/orcldata/a_summ01.dbf',
    '/u02/ORACLE/orcldata/a_nolog01.dbf',
    '/u02/ORACLE/orcldata/a_archive01.dbf',
    '/u02/ORACLE/orcldata/a_queue01.dbf',
    '/u02/ORACLE/orcldata/a_media01.dbf',
    '/u02/ORACLE/orcldata/a_txn_data02.dbf',
    '/u02/ORACLE/orcldata/a_txn_data03.dbf',
    '/u02/ORACLE/orcldata/a_txn_ind02.dbf',
    '/u02/ORACLE/orcldata/a_txn_ind03.dbf',
    '/u02/ORACLE/orcldata/a_txn_ind04.dbf',
    '/u02/ORACLE/orcldata/a_txn_ind05.dbf',
    '/u02/ORACLE/orcldata/a_ref02.dbf'
    CHARACTER SET US7ASCII

Maybe you are looking for