Now that the new volumes are added to the clone VM, the next step is to refresh them with data from the source.
# ssh pureuser@10.21.228.28 purevol copy --overwrite oracle-rt-prdm-prod-01-orahome oracle-rt-prdm-dev-01-orahome
Name Size Source Created Serial
oracle-rt-prdm-dev-01-orahome 2T oracle-rt-prdm-prod-01-orahome 2020-04-16 00:57:37 PDT 730D187406C14775000BED12
# ssh pureuser@10.21.228.28 purevol copy --overwrite oracle-rt-prdm-prod-01-data oracle-rt-prdm-dev-01-data
Name Size Source Created Serial
oracle-rt-prdm-dev-01-data 2T oracle-rt-prdm-prod-01-data 2020-04-16 00:58:17 PDT 730D187406C14775000BED13
# ssh pureuser@10.21.228.28 purevol copy --overwrite oracle-rt-prdm-prod-01-fra oracle-rt-prdm-dev-01-fra
Name Size Source Created Serial
oracle-rt-prdm-dev-01-fra 2T oracle-rt-prdm-prod-01-fra 2020-04-16 00:58:34 PDT 730D187406C14775000BED14
Add an entry to /etc/fstab for the /u01 filesystem. Actually, the entry is already there, we just need to uncomment it. We should be able to mount the /u01 filesystem now.
# lsscsi --scsi_id
[1:0:0:0] disk VMware Virtual disk 2.0 /dev/sda 36000c29513f1b35efa4b3b55f7c9ee74
[1:0:1:0] disk PURE FlashArray 8888 /dev/sdb 3624a9370730d187406c14775000bed12
[1:0:2:0] disk PURE FlashArray 8888 /dev/sdc 3624a9370730d187406c14775000bed13 <-- DATA
[1:0:3:0] disk PURE FlashArray 8888 /dev/sdd 3624a9370730d187406c14775000bed14 <-- FRA
Update UDEV rules - edit /etc/udev/rules.d/99-oracle-asmdevices.rules and update the RESULT value with the SCSI_ID obtained above.
KERNEL=="sd*", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/%k", RESULT=="3624a9370730d187406c14775000bed13",
SYMLINK+="asm_data", ACTION=="add|change", OWNER="grid", GROUP="asmadmin", MODE="0660
KERNEL=="sd*", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/%k", RESULT=="3624a9370730d187406c14775000bed14",
SYMLINK+="asm_fra", ACTION=="add|change", OWNER="grid", GROUP="asmadmin", MODE="0660"
Once the rules are updated, reload them and test using the commands below.
# udevadm control --reload-rules
# udevadm test /block/sdc
# udevadm test /block/sdd
Symbolic links should have gotten created and device ownership should show grid:asmadmin as shown below.
# ls -l /dev/asm* /dev/sdc /dev/sdd
lrwxrwxrwx. 1 root root 3 Apr 16 01:35 /dev/asm_data -> sdc
lrwxrwxrwx. 1 root root 3 Apr 16 01:35 /dev/asm_fra -> sdd
brw-rw----. 1 grid asmadmin 8, 32 Apr 16 01:35 /dev/sdc
brw-rw----. 1 grid asmadmin 8, 48 Apr 16 01:35 /dev/sdd�
Reboot the clone VM. The VM should boot without any errors this time.
If the ASM and database instance is configured to start on reboot, they should start automatically.
You might have noticed that we did not change the hostname of the cloned VM. This was done on purpose. That's because changing the hostname will break Oracle Grid Infrastructure configuration and neither ASM nor the database will come up.
To reconfigure Grid Infrastructure configuration, so that ASM comes back up after the hostname change, a few additional steps need to be performed. These steps are discussed in detail in Cloning Oracle Grid Infrastructure for a Standalone Server.