Gather Information From the Source Database on the Physical Server

Oracle

Audience
Public
Technology Integrations
Oracle
Source Type
Documentation
3a. Identify the FlashArray volume containing the software
[oracle@orademo1 ~]$ echo $ORACLE_HOME
/u01/app/oracle/product/19.0.0/dbhome_1

[oracle@orademo1 ~]$ cat /etc/fstab | grep u01
/dev/mapper/oracle-rt-ora01prd-home-01  /u01    xfs     defaults        0 0
3b. Query the data dictionary to identify the FlashArray volumes where the database is residing.
In our example, the source database is called ORA01PRD and all the data, temp, control and log files are located in an ASM disk group called ORA01PRD_DATA. In case the database is on an OS file system, you can identify the FlashArray volumes by looking at mount path or device information in /etc/fstab, like we did in the previous step for the ORACLE_HOME.
SYS@ORA01PRD >select file_name from dba_data_files;

FILE_NAME
--------------------------------------------------------------------------------
+ORA01PRD_DATA/ORA01PRD/DATAFILE/system.257.1029181373
+ORA01PRD_DATA/ORA01PRD/DATAFILE/sysaux.258.1029181409
+ORA01PRD_DATA/ORA01PRD/DATAFILE/undotbs1.259.1029181423
+ORA01PRD_DATA/ORA01PRD/DATAFILE/users.260.1029181425
+ORA01PRD_DATA/ORA01PRD/DATAFILE/mgmt_ecm_depot_ts.271.1029193195
+ORA01PRD_DATA/ORA01PRD/DATAFILE/mgmt_tablespace.272.1029193197
+ORA01PRD_DATA/ORA01PRD/DATAFILE/mgmt_ad4j_ts.273.1029193197
SYS@ORA01PRD >select file_name from dba_temp_files;   
    
FILE_NAME
--------------------------------------------------------------------------------
+ORA01PRD_DATA/ORA01PRD/TEMPFILE/temp.269.102918148
SYS@ORA01PRD >select member from v$logfile;
MEMBER
--------------------------------------------------------------------------------
+ORA01PRD_DATA/ORA01PRD/ONLINELOG/group_3.265.1029181483
+ORA01PRD_DATA/ORA01PRD/ONLINELOG/group_3.268.1029181483
+ORA01PRD_DATA/ORA01PRD/ONLINELOG/group_2.264.1029181483
+ORA01PRD_DATA/ORA01PRD/ONLINELOG/group_2.267.1029181483
+ORA01PRD_DATA/ORA01PRD/ONLINELOG/group_1.263.1029181483
+ORA01PRD_DATA/ORA01PRD/ONLINELOG/group_1.266.1029181483
SYS@ORA01PRD >select name from v$controlfile;

NAME
--------------------------------------------------------------------------------
+ORA01PRD_DATA/ORA01PRD/CONTROLFILE/current.262.1029181479
+ORA01PRD_DATA/ORA01PRD/CONTROLFILE/current.261.1029181479
3c. The spfile file is also in ASM.
SYS@ORA01PRD >show parameter spfile

NAME                                 TYPE        VALUE
------------------------------------ ----------- -----------------------------------------------------------
spfile                               string      +ORA01PRD_DATA/ORA01PRD/PARAMETERFILE/spfile.270.1029181705
3d. Identify the destination for the Fast Recovery Area
SYS@ORA01PRD >show parameter db_recovery_file_dest 

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest                string      +ORA01PRD_DATA
3e. Identify ASM disk paths for the disk groups identified in the previous step.
SYS@ORA01PRD >SELECT g.group_number, d.path
  2  FROM v$asm_disk d, v$asm_diskgroup g
  3  WHERE d.group_number = g.group_number and g.name='ORA01PRD_DATA';
  
  GROUP_NUMBER PATH
------------ ------------------------------
           1 AFD:ORA01PRD_DATA01
3f. In this case, we have only one disk and one datastore. Using the below command, we can find the device mapper for each of the disks.
[grid@orademo1 ~]$ cat /dev/oracleafd/disks/ORA01PRD_DATA01
/dev/mapper/oracle-rt-ora01prd-data01
3g. And then from /etc/multipath.conf, we identify the FlashArray volume serial numbers for both the Oracle software directory.
  multipath {
                wwid 3624a93706c1d7213605f49200006d926
                alias  oracle-rt-ora01prd-data01
        }
        multipath {
                wwid 3624a93706c1d7213605f49200006d937
                alias  oracle-rt-ora01prd-home-01
        }
3h. Using the serial numbers, the FlashArray volumes can be identified either through the GUI, or using the CLI as shown below.
[oracle@orademo1 ~]$ ssh pureuser@10.21.228.24 "purevol list --filter \"serial = '*6c1d7213605f49200006d926'\"" 
Name                       Size  Source  Created                  Serial                  
oracle-rt-ora01prd-data01  2T    -       2019-10-24 03:04:03 PDT  6C1D7213605F49200006D926

[oracle@orademo1 ~]$ ssh pureuser@10.21.228.24 "purevol list --filter \"serial = '*6c1d7213605f49200006d937'\""
Name                        Size  Source  Created                  Serial                  
oracle-rt-ora01prd-home-01  500G  -       2019-10-24 03:07:19 PDT  6C1D7213605F49200006D937
At the end of this step, you should have a list of volumes, their sizes, and their serial numbers.

These volumes should be added to a Protection Group, if not done already. In our example, the protection group is called oracle-rt-ora01prd-pg.