This discussion is archived
10 Replies Latest reply: Jan 10, 2013 5:44 AM by AnandKumar RSS

Create physical standby database and ASM

Robert Lockard Newbie
Currently Being Moderated
Database 11.2.0.1

I have recoved a cold backup of a primary database to a standby instance.

Method to backup: from http://www.visi.com/~mseberg/duprman2.html
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;
}

Method to recover: from http://www.visi.com/~mseberg/duprman2.html
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;
}


Once I mounted the standby instance I'm getting the following errors. This has got me baffled. What did I do wrong? How do I correct?

MRP0: Background Managed Standby Recovery process started (finmeta)
started logmerger process
Wed Mar 21 11:05:34 2012
Managed Standby Recovery not using Real Time Apply
Wed Mar 21 11:05:34 2012
Errors in file /opt/bsaitmod/oracle/app/oracle/diag/rdbms/finmetastby/finmeta/trace/finmeta_dbw0_26771.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '+DATA/finmeta/datafile/system.348.770552129'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/system.348.770552129
ORA-15012: ASM file '+DATA/finmeta/datafile/system.348.770552129' does not exist
Errors in file /opt/bsaitmod/oracle/app/oracle/diag/rdbms/finmetastby/finmeta/trace/finmeta_dbw0_26771.trc:
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: '+DATA/finmeta/datafile/sysaux.347.770554015'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/sysaux.347.770554015
ORA-15012: ASM file '+DATA/finmeta/datafile/sysaux.347.770554015' does not exist
Errors in file /opt/bsaitmod/oracle/app/oracle/diag/rdbms/finmetastby/finmeta/trace/finmeta_dbw0_26771.trc:
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: '+DATA/finmeta/datafile/undotbs1.367.770556497'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/undotbs1.367.770556497
ORA-15012: ASM file '+DATA/finmeta/datafile/undotbs1.367.770556497' does not exist
Errors in file /opt/bsaitmod/oracle/app/oracle/diag/rdbms/finmetastby/finmeta/trace/finmeta_dbw0_26771.trc:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: '+DATA/finmeta/datafile/users.368.770556893'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/users.368.770556893
ORA-15012: ASM file '+DATA/finmeta/datafile/users.368.770556893' does not exist
Errors in file /opt/bsaitmod/oracle/app/oracle/diag/rdbms/finmetastby/finmeta/trace/finmeta_dbw0_26771.trc:
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: '+DATA/finmeta/datafile/xmeta.346.770546851'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/xmeta.346.770546851
ORA-15012: ASM file '+DATA/finmeta/datafile/xmeta.346.770546851' does not exist
Errors in file /opt/bsaitmod/oracle/app/oracle/diag/rdbms/finmetastby/finmeta/trace/finmeta_dbw0_26771.trc:
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: '+DATA/finmeta/datafile/iauser.366.770555491'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/iauser.366.770555491
ORA-15012: ASM file '+DATA/finmeta/datafile/iauser.366.770555491' does not exist
MRP0: Background Media Recovery terminated with error 1110
Errors in file /opt/bsaitmod/oracle/app/oracle/diag/rdbms/finmetastby/finmeta/trace/finmeta_pr00_26826.trc:
ORA-01110: data file 1: '+DATA/finmeta/datafile/system.348.770552129'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '+DATA/finmeta/datafile/system.348.770552129'
Slave exiting with ORA-1110 exception
Errors in file /opt/bsaitmod/oracle/app/oracle/diag/rdbms/finmetastby/finmeta/trace/finmeta_pr00_26826.trc:
ORA-01110: data file 1: '+DATA/finmeta/datafile/system.348.770552129'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '+DATA/finmeta/datafile/system.348.770552129'
Completed: ALTER DATABASE RECOVER managed standby database disconnect from session
Recovery Slave PR00 previously exited with exception 1110
Errors in file /opt/bsaitmod/oracle/app/oracle/diag/rdbms/finmetastby/finmeta/trace/finmeta_mrp0_26824.trc:
ORA-01110: data file 1: '+DATA/finmeta/datafile/system.348.770552129'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '+DATA/finmeta/datafile/system.348.770552129'
MRP0: Background Media Recovery process shutdown (finmeta)
[oracle@fcndrdbdr01-adm /opt/bsaitmod/oracle/app/oracle/diag/rdbms/finmetastby/finmeta/trace]$

cat /opt/bsaitmod/oracle/app/oracle/diag/rdbms/finmetastby/finmeta/trace/finmeta_dbw0_26771.trc
Trace file /opt/bsaitmod/oracle/app/oracle/diag/rdbms/finmetastby/finmeta/trace/finmeta_dbw0_26771.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /opt/bsaitmod/oracle/app/oracle/product/11.2.0/dbhome_1
System name: Linux
Node name: fcndrdbdr01-adm.aos.hqfincen.gov
Release: 2.6.18-238.19.1.el5
Version: #1 SMP Sun Jul 10 08:43:41 EDT 2011
Machine: x86_64
Instance name: finmeta
Redo thread mounted by this instance: 1
Oracle process number: 10
Unix process pid: 26771, image: oracle@fcndrdbdr01-adm.aos.hqfincen.gov (DBW0)


*** 2012-03-21 11:05:34.778
*** SESSION ID:(111.1) 2012-03-21 11:05:34.778
*** CLIENT ID:() 2012-03-21 11:05:34.778
*** SERVICE NAME:() 2012-03-21 11:05:34.778
*** MODULE NAME:() 2012-03-21 11:05:34.778
*** ACTION NAME:() 2012-03-21 11:05:34.778

DDE rules only execution for: ORA 1110
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '+DATA/finmeta/datafile/system.348.770552129'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/system.348.770552129
ORA-15012: ASM file '+DATA/finmeta/datafile/system.348.770552129' does not exist
DDE: Problem Key 'ORA 1110' was flood controlled (0x1) (no incident)
ORA-01110: data file 2: '+DATA/finmeta/datafile/sysaux.347.770554015'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/sysaux.347.770554015
ORA-15012: ASM file '+DATA/finmeta/datafile/sysaux.347.770554015' does not exist
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: '+DATA/finmeta/datafile/sysaux.347.770554015'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/sysaux.347.770554015
ORA-15012: ASM file '+DATA/finmeta/datafile/sysaux.347.770554015' does not exist
DDE: Problem Key 'ORA 1110' was flood controlled (0x1) (no incident)
ORA-01110: data file 3: '+DATA/finmeta/datafile/undotbs1.367.770556497'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/undotbs1.367.770556497
ORA-15012: ASM file '+DATA/finmeta/datafile/undotbs1.367.770556497' does not exist
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: '+DATA/finmeta/datafile/undotbs1.367.770556497'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/undotbs1.367.770556497
ORA-15012: ASM file '+DATA/finmeta/datafile/undotbs1.367.770556497' does not exist
DDE: Problem Key 'ORA 1110' was flood controlled (0x1) (no incident)
ORA-01110: data file 4: '+DATA/finmeta/datafile/users.368.770556893'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/users.368.770556893
ORA-15012: ASM file '+DATA/finmeta/datafile/users.368.770556893' does not exist
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: '+DATA/finmeta/datafile/users.368.770556893'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/users.368.770556893
ORA-15012: ASM file '+DATA/finmeta/datafile/users.368.770556893' does not exist
DDE: Problem Key 'ORA 1110' was flood controlled (0x1) (no incident)
ORA-01110: data file 5: '+DATA/finmeta/datafile/xmeta.346.770546851'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/xmeta.346.770546851
ORA-15012: ASM file '+DATA/finmeta/datafile/xmeta.346.770546851' does not exist
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: '+DATA/finmeta/datafile/xmeta.346.770546851'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/xmeta.346.770546851
ORA-15012: ASM file '+DATA/finmeta/datafile/xmeta.346.770546851' does not exist
DDE: Problem Key 'ORA 1110' was flood controlled (0x1) (no incident)
ORA-01110: data file 6: '+DATA/finmeta/datafile/iauser.366.770555491'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/iauser.366.770555491
ORA-15012: ASM file '+DATA/finmeta/datafile/iauser.366.770555491' does not exist
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: '+DATA/finmeta/datafile/iauser.366.770555491'
ORA-17503: ksfdopn:2 Failed to open file +DATA/finmeta/datafile/iauser.366.770555491
ORA-15012: ASM file '+DATA/finmeta/datafile/iauser.366.770555491' does not exist
[oracle@fcndrdbdr01-adm /opt/bsaitmod/oracle/app/oracle/diag/rdbms/finmetastby/finmeta/trace]$
  • 1. Re: Create physical standby database and ASM
    Robert Lockard Newbie
    Currently Being Moderated
    Here is the log of the restore:


    RMAN> run {
    allocate channel C1 device type disk;
    allocate auxiliary channel C2 device type disk;
    duplicate target database for standby nofilenamecheck;
    }

    2> 3> 4> 5>
    using target database control file instead of recovery catalog
    allocated channel: C1
    channel C1: SID=673 device type=DISK

    allocated channel: C2
    channel C2: SID=24 device type=DISK

    Starting Duplicate Db at 21-MAR-12

    contents of Memory Script:
    {
    restore clone standby controlfile;
    }
    executing Memory Script

    Starting restore at 21-MAR-12

    channel C2: starting datafile backup set restore
    channel C2: restoring control file
    channel C2: reading from backup piece /var/opt/backup/finmeta/finmetaStandby.ctl
    channel C2: piece handle=/var/opt/backup/finmeta/finmetaStandby.ctl tag=TAG20120310T094217
    channel C2: restored backup piece 1
    channel C2: restore complete, elapsed time: 00:00:02
    output file name=+DATA/finmeta/controlfile/current.366.778503371
    output file name=+DATA/finmeta/controlfile/current.347.778503371
    Finished restore at 21-MAR-12

    contents of Memory Script:
    {
    sql clone 'alter database mount standby database';
    }
    executing Memory Script

    sql statement: alter database mount standby database
    RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.

    contents of Memory Script:
    {
    set newname for tempfile 1 to
    "+data";
    switch clone tempfile all;
    set newname for datafile 1 to
    "+data";
    set newname for datafile 2 to
    "+data";
    set newname for datafile 3 to
    "+data";
    set newname for datafile 4 to
    "+data";
    set newname for datafile 5 to
    "+DATA/xmeta1.dbf";
    set newname for datafile 6 to
    "+DATA/iauser1.dbf";
    restore
    clone database
    ;
    }
    executing Memory Script

    executing command: SET NEWNAME

    renamed tempfile 1 to +data in control file

    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 21-MAR-12

    channel C2: starting datafile backup set restore
    channel C2: specifying datafile(s) to restore from backup set
    channel C2: restoring datafile 00003 to +data
    channel C2: reading from backup piece /var/opt/backup/finmeta/37n5gsha_1_1
    channel C2: piece handle=/var/opt/backup/finmeta/37n5gsha_1_1 tag=%TAG
    channel C2: restored backup piece 1
    channel C2: restore complete, elapsed time: 00:00:02
    channel C2: starting datafile backup set restore
    channel C2: specifying datafile(s) to restore from backup set
    channel C2: restoring datafile 00006 to +DATA/iauser1.dbf
    channel C2: reading from backup piece /var/opt/backup/finmeta/36n5gsh9_1_1
    channel C2: piece handle=/var/opt/backup/finmeta/36n5gsh9_1_1 tag=%TAG
    channel C2: restored backup piece 1
    channel C2: restore complete, elapsed time: 00:00:03
    channel C2: starting datafile backup set restore
    channel C2: specifying datafile(s) to restore from backup set
    channel C2: restoring datafile 00002 to +data
    channel C2: reading from backup piece /var/opt/backup/finmeta/35n5gsh9_1_1
    channel C2: piece handle=/var/opt/backup/finmeta/35n5gsh9_1_1 tag=%TAG
    channel C2: restored backup piece 1
    channel C2: restore complete, elapsed time: 00:00:03
    channel C2: starting datafile backup set restore
    channel C2: specifying datafile(s) to restore from backup set
    channel C2: restoring datafile 00001 to +data
    channel C2: reading from backup piece /var/opt/backup/finmeta/34n5gsh9_1_1
    channel C2: piece handle=/var/opt/backup/finmeta/34n5gsh9_1_1 tag=%TAG
    channel C2: restored backup piece 1
    channel C2: restore complete, elapsed time: 00:00:03
    channel C2: starting datafile backup set restore
    channel C2: specifying datafile(s) to restore from backup set
    channel C2: restoring datafile 00004 to +data
    channel C2: reading from backup piece /var/opt/backup/finmeta/39n5gsli_1_1
    channel C2: piece handle=/var/opt/backup/finmeta/39n5gsli_1_1 tag=%TAG
    channel C2: restored backup piece 1
    channel C2: restore complete, elapsed time: 00:00:01
    channel C2: starting datafile backup set restore
    channel C2: specifying datafile(s) to restore from backup set
    channel C2: restoring datafile 00005 to +DATA/xmeta1.dbf
    channel C2: reading from backup piece /var/opt/backup/finmeta/33n5gsh9_1_1
    channel C2: piece handle=/var/opt/backup/finmeta/33n5gsh9_1_1 tag=%TAG
    channel C2: restored backup piece 1
    channel C2: restore complete, elapsed time: 00:00:07
    Finished restore at 21-MAR-12

    contents of Memory Script:
    {
    switch clone datafile all;
    }
    executing Memory Script

    datafile 1 switched to datafile copy
    input datafile copy RECID=6 STAMP=778503400 file name=+DATA/finmeta/datafile/system.258.778503389
    datafile 2 switched to datafile copy
    input datafile copy RECID=7 STAMP=778503400 file name=+DATA/finmeta/datafile/sysaux.259.778503385
    datafile 3 switched to datafile copy
    input datafile copy RECID=8 STAMP=778503400 file name=+DATA/finmeta/datafile/undotbs1.348.778503381
    datafile 4 switched to datafile copy
    input datafile copy RECID=9 STAMP=778503400 file name=+DATA/finmeta/datafile/users.257.778503391
    datafile 5 switched to datafile copy
    input datafile copy RECID=10 STAMP=778503400 file name=+DATA/xmeta1.dbf
    datafile 6 switched to datafile copy
    input datafile copy RECID=11 STAMP=778503400 file name=+DATA/iauser1.dbf
    Finished Duplicate Db at 21-MAR-12
    released channel: C1
    released channel: C2

    RMAN>
    RMAN> quit
  • 2. Re: Create physical standby database and ASM
    mseberg Guru
    Currently Being Moderated
    Hello

    Thanks for reviewing my notes.


    checking...

    Looks like "SET NEWNAME" is needed because of ASM

    SET NEWNAME FOR DATAFILE 1 TO /oracle/data/file2.f; # rename df 1 as file2.f
    SET NEWNAME FOR DATAFILE 2 TO /oracle/data/file1.f; # rename df 2 as file1.f
    This is the key RMAN-05529 Nope - No action is required. This is an informational message only.

    Would check this out

    RMAN restore to ASM - ORA-17503: ksfdopn:2 Failed to open file [ID 336200.1]



    So the Dup went OK, but the mount is the issue right?

    Ball park Notes

    ORA-01157 Errors When Doing RMAN Duplicate With ASM [ID 353905.1]

    ORA-01157, ORA-01110, ORA-27046 Starting A Restored Database [ID 301635.1]


    Best Regards

    mseberg

    Will update my document for ASM if you post results

    Edited by: mseberg on Mar 21, 2012 10:30 AM

    Edited by: mseberg on Mar 21, 2012 10:36 AM
  • 3. Re: Create physical standby database and ASM
    CKPT Guru
    Currently Being Moderated
    Once I mounted the standby instance I'm getting the following errors. This has got me baffled. What did I do wrong? How do I correct?
    Can you post from standby as

    SQL> select name from v$datafile;

    Probably switching of datafiles not switched properly..

    if above output still points to ASM , then perform rename manually

    SQL> alter database rename file '+DATA/finmeta/datafile/system.348.770552129' to 'new location'

    But still am confused about procedure..

    are you performing RMAN restore from ASM to ASM or ASM to NON-ASM?
  • 4. Re: Create physical standby database and ASM
    Robert Lockard Newbie
    Currently Being Moderated
    This is ASM to ASM

    SQL> select name from v$datafile;


    NAME
    --------------------------------------------------------------------------------
    +DATA/finmeta/datafile/system.348.770552129
    +DATA/finmeta/datafile/sysaux.347.770554015
    +DATA/finmeta/datafile/undotbs1.367.770556497
    +DATA/finmeta/datafile/users.368.770556893
    +DATA/finmeta/datafile/xmeta.346.770546851
    +DATA/finmeta/datafile/iauser.366.770555491

    6 rows selected.

    SQL> SQL>
  • 5. Re: Create physical standby database and ASM
    Robert Lockard Newbie
    Currently Being Moderated
    Yes, the dupe ran just fine. The errors occur when I mount using the standby control file.
  • 6. Re: Create physical standby database and ASM
    CKPT Guru
    Currently Being Moderated
    I think you caught ;-)

    here is clue
    Source Datafile:- '+DATA/finmeta/datafile/iauser.366.770555491'
    Standby Datafile:- name=+DATA/iauser1.dbf

    Then why showing datafile locations still as primary ?

    >
    This is ASM to ASM

    SQL> select name from v$datafile;

    NAME
    +DATA/finmeta/datafile/system.348.770552129
    +DATA/finmeta/datafile/sysaux.347.770554015
    +DATA/finmeta/datafile/undotbs1.367.770556497
    +DATA/finmeta/datafile/users.368.770556893
    +DATA/finmeta/datafile/xmeta.346.770546851
    +DATA/finmeta/datafile/iauser.366.770555491
    >

    Hope you got what am saying?

    So do manually as

    SQL> alter database rename file '+DATA/finmeta/datafile/system.348.770552129' to '+DATA/iauser1.dbf';

    Correct the location of standby datafile location & post
    SQL> select name from v$datafile ;


    Also, why you mentioned different as "+DATA" & "+DATA/xmeta1.dbf"; & so on?

    >
    set newname for tempfile 1 to
    "+data";
    switch clone tempfile all;
    set newname for datafile 1 to
    "+data";
    set newname for datafile 2 to
    "+data";
    set newname for datafile 3 to
    "+data";
    set newname for datafile 4 to
    "+data";
    set newname for datafile 5 to
    "+DATA/xmeta1.dbf";
    set newname for datafile 6 to
    "+DATA/iauser1.dbf";
    restore
    >

    Edited by: CKPT on Mar 21, 2012 9:35 PM
  • 7. Re: Create physical standby database and ASM
    Robert Lockard Newbie
    Currently Being Moderated
    it just gets more and more intresting. I'm really starting to not like ASM.

    SQL> alter database rename file '+DATA/finmeta/datafile/system.348.770552129' to '+DATA/finmeta/datafile/SYSTEM.258.778503389';
    alter database rename file '+DATA/finmeta/datafile/system.348.770552129' to '+DATA/finmeta/datafile/SYSTEM.258.778503389'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01275: Operation RENAME is not allowed if standby file management is automatic.


    SQL>
  • 8. Re: Create physical standby database and ASM
    CKPT Guru
    Currently Being Moderated
    Robert Lockard wrote:
    it just gets more and more intresting. I'm really starting to not like ASM.

    SQL> alter database rename file '+DATA/finmeta/datafile/system.348.770552129' to '+DATA/finmeta/datafile/SYSTEM.258.778503389';
    alter database rename file '+DATA/finmeta/datafile/system.348.770552129' to '+DATA/finmeta/datafile/SYSTEM.258.778503389'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01275: Operation RENAME is not allowed if standby file management is automatic.


    SQL>
    Try after setting STANDBY_FILE_MANAGEMENT=MANUAL
    Also check this...

    use COPY datafile option..
    Refer this link http://www.idevelopment.info/data/Oracle/DBA_tips/Automatic_Storage_Management/ASM_36.shtml

    Edited by: CKPT on Mar 21, 2012 9:58 PM
  • 9. Re: Create physical standby database and ASM
    mseberg Guru
    Currently Being Moderated
    I like CKPT's idea

    You need to set STANDBY_FILE_MANAGEMENT to MANUAL before you try it.

    But if it works It will save you a ton of time.

    Best Regards

    mseberg
  • 10. Re: Create physical standby database and ASM
    AnandKumar Newbie
    Currently Being Moderated
    Hi,

    I am having the same issue. Did we succeed after changing the parameter to MANUAL;

    Is there any way to relate file# in the v$datafile with ASM diskname.

    Please help.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points