I am planning to clone my Virtual Box VM which is already installed and configured with Oracle Restart 19c and patched with the October 2020 RU (19.9.0.0.0). However, instead of reinstalling the whole thing including OS, User/Group creation, Kernel adjustments, Oracle ASM, Oracle Restart and so on, I thought about simply cloning the VM and do a few changes afterwards. Hopefully, this will be much faster. In the end, the goal is to have two VM’s which are configured and patched the same way, where I can build Data Guard on top.
If you follow the next steps, you should have a new VM up and running (incl. Grid Infrastructure, ASM .. and so on), much much faster, compared to re-installing the whole thing.
The process of accomplishing the task can be divided into 5 steps:
- Start a Full Clone via the Virtual Box Gui
Generate new MAC addresses for all network adapters - Adjust the udev rules
- Configure the new hostname and ip addresses
- Reconfigure Oracle Restart
- Create the listener and ASM cluster resource
Full Clone via the Virtual Box Gui
Oracle’s Virtual Box offers you a few options when it comes to cloning. The important one for us is the “Full Clone”, which copies all dependent disks to the new VM folder. The beauty of a “Full Clone” is that it can operate fully by it’s own without any reference to the source VM.
The next important option is the ability to generate new MAC addresses for all network adapters that are attached to the VM. Without this option, the VM’s will not be able to communicate with each other.
After these options are set, the cloning itself is quite boring. Just shutdown the VM, start the cloning process, and meanwhile drink a coffee. 🙂
Adjust the udev rules
The next step is to adjust the udev rules, because the virtual hardware WWN’s might have change. Simply follow the instruction, which I already have documented in the below Blog.
https://ptdb.ch/2020/10/27/how-to-create-udev-rules-for-oracle-19c-asm-on-centos-rhel-8-2/
-- udev rules
[root@ocm199 ~]# udevadm info --query=all --name=/dev/nvme0n1 | egrep "WWN|SERIAL" | grep "WWN=eui"
E: ID_WWN=eui.c24ef9fc7147544eba3b1b5746a0b31b
[root@ocm199 ~]# udevadm info --query=all --name=/dev/nvme0n2 | egrep "WWN|SERIAL" | grep "WWN=eui"
E: ID_WWN=eui.7d0198fae3572d46a166fc9b76931631
[root@ocm199 ~]# udevadm info --query=all --name=/dev/nvme0n3 | egrep "WWN|SERIAL" | grep "WWN=eui"
E: ID_WWN=eui.c64900c50b84574993f70cef527ada4f
[root@ocm199 ~]# udevadm info --query=all --name=/dev/nvme0n4 | egrep "WWN|SERIAL" | grep "WWN=eui"
E: ID_WWN=eui.a1f44ad59423d641861cee659576ea18
[root@ocm199 ~]# udevadm info --query=all --name=/dev/nvme0n5 | egrep "WWN|SERIAL" | grep "WWN=eui"
E: ID_WWN=eui.8a8383fb5a57d84e94806bcfd5e339b0
[root@ocm199 ~]# udevadm info --query=all --name=/dev/nvme0n6 | egrep "WWN|SERIAL" | grep "WWN=eui"
E: ID_WWN=eui.a54db5c5ae956b49a70fe1a9b600d037
[root@ocm199 ~]# udevadm info --query=all --name=/dev/nvme0n7 | egrep "WWN|SERIAL" | grep "WWN=eui"
E: ID_WWN=eui.fa036e78788c3243bb9484b828189edc
[root@ocm199 ~]#
[root@ocm199 ~]# cat /etc/udev/rules.d/96-storage-asm.rules
ACTION=="add|change", ENV{ID_WWN}=="eui.c24ef9fc7147544eba3b1b5746a0b31b", SYMLINK+="oracleasm/asmdisk01", GROUP="dba", OWNER="oracle", MODE="0660"
ACTION=="add|change", ENV{ID_WWN}=="eui.7d0198fae3572d46a166fc9b76931631", SYMLINK+="oracleasm/asmdisk02", GROUP="dba", OWNER="oracle", MODE="0660"
ACTION=="add|change", ENV{ID_WWN}=="eui.c64900c50b84574993f70cef527ada4f", SYMLINK+="oracleasm/asmdisk03", GROUP="dba", OWNER="oracle", MODE="0660"
ACTION=="add|change", ENV{ID_WWN}=="eui.a1f44ad59423d641861cee659576ea18", SYMLINK+="oracleasm/asmdisk04", GROUP="dba", OWNER="oracle", MODE="0660"
ACTION=="add|change", ENV{ID_WWN}=="eui.8a8383fb5a57d84e94806bcfd5e339b0", SYMLINK+="oracleasm/asmdisk05", GROUP="dba", OWNER="oracle", MODE="0660"
ACTION=="add|change", ENV{ID_WWN}=="eui.a54db5c5ae956b49a70fe1a9b600d037", SYMLINK+="oracleasm/asmdisk06", GROUP="dba", OWNER="oracle", MODE="0660"
ACTION=="add|change", ENV{ID_WWN}=="eui.fa036e78788c3243bb9484b828189edc", SYMLINK+="oracleasm/asmdisk07", GROUP="dba", OWNER="oracle", MODE="0660"
[root@ocm199 ~]# udevadm control --reload-rules
[root@ocm199 ~]# udevadm trigger --type=devices --action=change
[root@ocm199 ~]#
Configure the new hostname and ip addresses
After you login to your VM via the console (the console is the only option you have at this moment), you will notice that the interfaces enp0s8 and enp0s9 have no ip addresses attached to them.
-- Network
[root@ocm199 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:35:dc:eb brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic noprefixroute enp0s3
valid_lft 85770sec preferred_lft 85770sec
inet6 fe80::a00:27ff:fe35:dceb/64 scope link
valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:d3:00:a0 brd ff:ff:ff:ff:ff:ff <= This is the new MAC address
4: enp0s9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:8b:9b:86 brd ff:ff:ff:ff:ff:ff <= This is the new MAC address
The easiest way to change the MAC and the ip addresses is to edit the ifcfg files which are located in the /etc/sysconfig/network-scripts/ directory, and change the HWADDR and the IPADDR for the Public and the Interconnect interface.
[root@ocm199 network-scripts]# pwd /etc/sysconfig/network-scripts [root@ocm199 network-scripts]# cat ifcfg-Wired_connection_1 HWADDR=08:00:27:D3:00:A0 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=no IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=Public UUID=e6f7e6a0-c283-4520-98f0-8cca03f00b2b ONBOOT=yes IPADDR=192.168.56.200 PREFIX=24 GATEWAY=192.168.56.2 [root@ocm199 network-scripts]# cat ifcfg-Wired_connection_1-1 HWADDR=08:00:27:8B:9B:86 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy <strong>NAME=Interconnect UUID=4bbfd24f-8a0a-46a3-8da1-fa7fc6e33993 ONBOOT=yes IPADDR=10.10.10.200 PREFIX=24 GATEWAY=10.10.10.2 [root@ocm199 network-scripts]#
After a reboot, the network interfaces with the new ip addresses should be up correctly.
[root@ocm199 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:35:dc:eb brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic noprefixroute enp0s3
valid_lft 86258sec preferred_lft 86258sec
inet6 fe80::a00:27ff:fe35:dceb/64 scope link
valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:d3:00:a0 brd ff:ff:ff:ff:ff:ff
inet 192.168.56.200/24 brd 192.168.56.255 scope global noprefixroute enp0s8
valid_lft forever preferred_lft forever
inet6 fe80::a00:27ff:fed3:a0/64 scope link
valid_lft forever preferred_lft forever
4: enp0s9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:8b:9b:86 brd ff:ff:ff:ff:ff:ff
inet 10.10.10.200/24 brd 10.10.10.255 scope global noprefixroute enp0s9
valid_lft forever preferred_lft forever
inet6 fe80::f7c2:3eba:b62:fd1e/64 scope link noprefixroute
valid_lft forever preferred_lft forever
[root@ocm199 ~]#
And the cloned ASM + CDB instance should be up and running as well. Remember, we haven’t changed the hostname yet. 😉
[root@ocm199 ~]# ps -ef | grep pmon oracle 10947 1 0 10:22 ? 00:00:00 asm_pmon_+ASM oracle 11073 1 0 10:22 ? 00:00:00 ora_pmon_CDB
Now it’s time to change the hostname from ocm199 to ocm200. But before doing so, we need to stop and disable HAS.
[root@ocm199 ~]# /u01/grid/19c/bin/crsctl stop has CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'ocm199' CRS-2673: Attempting to stop 'ora.cdb.db' on 'ocm199' CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'ocm199' CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'ocm199' succeeded CRS-2677: Stop of 'ora.cdb.db' on 'ocm199' succeeded CRS-2673: Attempting to stop 'ora.DATA.dg' on 'ocm199' CRS-2673: Attempting to stop 'ora.FRA.dg' on 'ocm199' CRS-2677: Stop of 'ora.DATA.dg' on 'ocm199' succeeded CRS-2677: Stop of 'ora.FRA.dg' on 'ocm199' succeeded CRS-2673: Attempting to stop 'ora.asm' on 'ocm199' CRS-2677: Stop of 'ora.asm' on 'ocm199' succeeded CRS-2673: Attempting to stop 'ora.evmd' on 'ocm199' CRS-2677: Stop of 'ora.evmd' on 'ocm199' succeeded CRS-2673: Attempting to stop 'ora.cssd' on 'ocm199' CRS-2677: Stop of 'ora.cssd' on 'ocm199' succeeded CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'ocm199' has completed CRS-4133: Oracle High Availability Services has been stopped. [root@ocm199 ~]# [root@ocm199 ~]# /u01/grid/19c/bin/crsctl disable has CRS-4621: Oracle High Availability Services autostart is disabled. [root@ocm199 ~]#
After HAS is stopped we can change the hostname via the hostnamectl command. Remember that this is an online operation and no downtime is required here.
[root@ocm199 ~]# hostnamectl
Static hostname: ocm199
Icon name: computer-vm
Chassis: vm
Machine ID: fb1db93cbb394fcfa65b72fd24cd2cd0
Boot ID: f7fc6ba6ea334b0d81ca910ae986b4e0
Virtualization: oracle
Operating System: CentOS Linux 8 (Core)
CPE OS Name: cpe:/o:centos:centos:8
Kernel: Linux 4.18.0-193.19.1.el8_2.x86_64
Architecture: x86-64
[root@ocm199 ~]#
[root@ocm199 ~]#
[root@ocm199 ~]#
[root@ocm199 ~]# hostnamectl set-hostname ocm200
[root@ocm199 ~]#
[root@ocm199 ~]# hostnamectl
Static hostname: ocm200
Icon name: computer-vm
Chassis: vm
Machine ID: fb1db93cbb394fcfa65b72fd24cd2cd0
Boot ID: f7fc6ba6ea334b0d81ca910ae986b4e0
Virtualization: oracle
Operating System: CentOS Linux 8 (Core)
CPE OS Name: cpe:/o:centos:centos:8
Kernel: Linux 4.18.0-193.19.1.el8_2.x86_64
Architecture: x86-64
[root@ocm199 ~]#
After starting a new shell, you should see the new hostname
[root@ocm200 ~]# hostnamectl
Static hostname: ocm200
Icon name: computer-vm
Chassis: vm
Machine ID: fb1db93cbb394fcfa65b72fd24cd2cd0
Boot ID: f7fc6ba6ea334b0d81ca910ae986b4e0
Virtualization: oracle
Operating System: CentOS Linux 8 (Core)
CPE OS Name: cpe:/o:centos:centos:8
Kernel: Linux 4.18.0-193.19.1.el8_2.x86_64
Architecture: x86-64
[root@ocm200 ~]#
Reconfigure Oracle Restart
Now the fun part begins. The reconfiguration of Oracle Restart. Be careful, this process removes all your cluster resources which you have configured beforehand, including the Listener, ASM and any Oracle DB resource.
If you want this to be a successful process, make sure that you don’t forget the chown command after the deconfiguration has finished.
OK. Let’s start the deconfiguration of HAS. Be aware, that the roothas.sh -deconfig -force removes any configuration on the system that referenced the old host name.
[root@ocm200 install]# pwd /u01/grid/19c/crs/install [root@ocm200 install]# ./roothas.sh -deconfig -force Using configuration parameter file: /u01/grid/19c/crs/install/crsconfig_params The log of current session can be found at: /u01/app/oracle/crsdata/ocm200/crsconfig/hadeconfig.log PRCR-1070 : Failed to check if resource ora.asm is registered CRS-5168 : unable to communicate with ohasd 2020/10/28 10:29:50 CLSRSC-180: An error occurred while executing the command '/u01/grid/19c/bin/srvctl remove asm -force ' PRCR-1070 : Failed to check if resource ora.ons is registered CRS-5168 : unable to communicate with ohasd 2020/10/28 10:29:51 CLSRSC-180: An error occurred while executing the command '/u01/grid/19c/bin/srvctl config ons' CLSU-00107: operating system function: opendir; failed with error data: 2; at location: scrsearch1 CLSU-00101: operating system error message: No such file or directory CLSU-00104: additional error information: cant open scr home dir scls_scr_getval CRS-4639: Could not contact Oracle High Availability Services CRS-4000: Command Stop failed, or completed with errors. 2020/10/28 10:29:53 CLSRSC-337: Successfully deconfigured Oracle Restart stack [root@ocm200 install]#
Don’t forget this one. Change the owner, group membership of the crs/log directory.
[root@ocm200 crs]# pwd /u01/app/oracle/diag/crs [root@ocm200 crs]# chown -R oracle:oinstall ocm200 [root@ocm200 crs]#
If you forget to do so, you will end up with very ugly error messages like the following one.
Oracle Clusterware infrastructure error in OCRCONFIG (OS PID 14598): CLSD/ADR initialization failed with return value -1 1: clskec:has:CLSU:910 4 args[clsdAdr_CLSK_err][mod=clsdadr.c][loc=(:CLSD00050:)][msg=2020-10-28 10:33:45.969 (:CLSD00050:) dbgc_init_all failed with return code 49802. Detected in function clsdAdrInit at line number 1828. ] 2: clskec:has:CLSU:910 4 args[clsdAdrInit_CLSK_err][mod=clsdadr.c][loc=(:CLSD00281:)][msg=clsdAdrInit: Additional diagnostic data returned by the ADR component for dbgc_init_all failure: DIA-49802: missing read, write, or execute permission on specified ADR home directory [/u01/app/oracle/diag/crs/ocm200/crs/log] DIA-49801: actual permissions [rwxrwx---], expected minimum permissions [rwxrwxrwx] for effective user [oracle] DIA-48188: user missing read, write, or exec permission on specified directory Linux-x86_64 Error: 13: Permission denied Additional information: 2 Additional information: 511 Additional information: 16888 ([all diagnostic data retrieved from ADR])] Oracle Clusterware infrastructure error in CLSCFG (OS PID 14616): CLSD/ADR initialization failed with return value -1 1: clskec:has:CLSU:910 4 args[clsdAdr_CLSK_err][mod=clsdadr.c][loc=(:CLSD00050:)][msg=2020-10-28 10:33:46.572 (:CLSD00050:) dbgc_init_all failed with return code 49802. Detected in function clsdAdrInit at line number 1828. ] 2: clskec:has:CLSU:910 4 args[clsdAdrInit_CLSK_err][mod=clsdadr.c][loc=(:CLSD00281:)][msg=clsdAdrInit: Additional diagnostic data returned by the ADR component for dbgc_init_all failure: DIA-49802: missing read, write, or execute permission on specified ADR home directory [/u01/app/oracle/diag/crs/ocm200/crs/log] DIA-49801: actual permissions [rwxrwx---], expected minimum permissions [rwxrwxrwx] for effective user [oracle] DIA-48188: user missing read, write, or exec permission on specified directory Linux-x86_64 Error: 13: Permission denied
Now run the root.sh from your Grid Home.
[root@ocm200 ~]# cd /u01/grid/19c/
[root@ocm200 19c]#
[root@ocm200 19c]# ./root.sh
Performing root user operation.
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/grid/19c
Enter the full pathname of the local bin directory: [/usr/local/bin]:
The contents of "dbhome" have not changed. No need to overwrite.
The contents of "oraenv" have not changed. No need to overwrite.
The contents of "coraenv" have not changed. No need to overwrite.
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Using configuration parameter file: /u01/grid/19c/crs/install/crsconfig_params
The log of current session can be found at:
/u01/app/oracle/crsdata/ocm200/crsconfig/roothas_2020-10-28_10-38-44AM.log
2020/10/28 10:38:45 CLSRSC-363: User ignored prerequisites during installation
LOCAL ADD MODE
Creating OCR keys for user 'oracle', privgrp 'oinstall'..
Operation successful.
PROT-29: The Oracle Cluster Registry location is already configured
2020/10/28 10:38:47 CLSRSC-155: Replace of older local-only OCR failed
LOCAL ONLY MODE
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
CRS-4664: Node ocm200 successfully pinned.
2020/10/28 10:38:50 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.service'
ocm200 2020/10/28 10:39:17 /u01/app/oracle/crsdata/ocm200/olr/backup_20201028_103917.olr 376483838
2020/10/28 10:39:17 CLSRSC-327: Successfully configured Oracle Restart for a standalone server
[root@ocm200 19c]#
Run roothas.sh to finish up the reconfiguration.
[root@ocm200 install]# /u01/grid/19c/crs/install/roothas.sh Using configuration parameter file: /u01/grid/19c/crs/install/crsconfig_params The log of current session can be found at: /u01/app/oracle/crsdata/ocm200/crsconfig/roothas_2020-10-28_10-41-13AM.log 2020/10/28 10:41:13 CLSRSC-363: User ignored prerequisites during installation 2020/10/28 10:41:14 CLSRSC-352: CRS is already configured on this node for the CRS home location /u01/grid/19c [root@ocm200 install]#
In case the ora.cssd should not have the AUTO_START set to 1, modify the Cluster resource with the following command. Remember that this step has to be run as user oracle or the Grid Infrastructure owner.
[oracle@ocm200 ~]$ /u01/grid/19c/bin/crsctl modify resource "ora.cssd" -init -attr "AUTO_START=1" -unsupported [oracle@ocm200 ~]$
Just a quick check, if it is configured correctly.
[oracle@ocm200 ~]$ /u01/grid/19c/bin/crsctl stat resource "ora.cssd" -p | grep AUTO_START AUTO_START=1
And a few other checks to see if everything is fine.
[oracle@ocm200 ~]$ /u01/grid/19c/bin/crsctl enable has CRS-4622: Oracle High Availability Services autostart is enabled. [oracle@ocm200 ~]$ crsctl check has CRS-4638: Oracle High Availability Services is online [oracle@ocm200 ~]$ crsctl stat res NAME=ora.cssd TYPE=ora.cssd.type TARGET=OFFLINE STATE=OFFLINE NAME=ora.diskmon TYPE=ora.diskmon.type TARGET=OFFLINE STATE=OFFLINE NAME=ora.evmd TYPE=ora.evm.type TARGET=ONLINE STATE=ONLINE on ocm200 NAME=ora.ons TYPE=ora.ons.type TARGET=OFFLINE STATE=OFFLINE
Create the listener and ASM cluster resource
Recreate the listener via netca (Gui) or any other preferred method.
[oracle@ocm200 ~]$ srvctl add listener -listener LISTENER -oraclehome /u01/grid/19c -endpoints "TCP:1521" [oracle@ocm200 ~]$ [oracle@ocm200 ~]$ srvctl status listener Listener LISTENER is enabled Listener LISTENER is not running [oracle@ocm200 ~]$ srvctl start listener [oracle@ocm200 ~]$ srvctl status listener Listener LISTENER is enabled Listener LISTENER is running on node(s): ocm200 [oracle@ocm200 ~]$
And last but not least, we will recreate the ASM instance cluster resource. Recreating the ASM instance consists of a few more steps. First, create the init+ASM.ora file in the $GI_HOME/dbs directory with the following parameters. Afterwards create the cluster resource, start the ASM instance, and create the spfile.
[oracle@ocm200 ~]$ cd $ORACLE_HOME/dbs
[oracle@ocm200 dbs]$ vi init+ASM.ora
[oracle@ocm200 dbs]$ cat init+ASM.ora
+ASM.__oracle_base='/u01/app/oracle'
+ASM.asm_diskgroups='DATA','FRA'
*.asm_diskstring='/dev/oracleasm/*'
*.asm_power_limit=1
*.large_pool_size=12M
*.remote_login_passwordfile='EXCLUSIVE'
[oracle@ocm200 dbs]$ srvctl add asm -listener LISTENER
[oracle@ocm200 dbs]$
[oracle@ocm200 dbs]$ srvctl config asm
ASM home: <CRS home>
Password file:
Backup of Password file:
ASM listener: LISTENER
Spfile:
ASM diskgroup discovery string: ++no-value-at-resource-creation--never-updated-through-ASM++
[oracle@ocm200 dbs]$ crsctl modify resource "ora.asm" -init -attr "AUTO_START=1" -unsupported
[oracle@ocm200 dbs]$
[oracle@ocm200 ~]$ /u01/grid/19c/bin/crsctl stat resource "ora.asm" -p | grep AUTO
AUTO_START=1
[oracle@ocm200 dbs]$ sqlplus / as sysasm
SQL*Plus: Release 19.0.0.0.0 - Production on Thu Oct 29 01:55:06 2020
Version 19.9.0.0.0
Copyright (c) 1982, 2020, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup pfile=/u01/grid/19c/dbs/init+ASM.ora
ASM instance started
Total System Global Area 1137173320 bytes
Fixed Size 8905544 bytes
Variable Size 1103101952 bytes
ASM Cache 25165824 bytes
ASM diskgroups mounted
SQL>
SQL> SELECT path FROM v$asm_disk;
PATH
--------------------------------------------------------------------------------
/dev/oracleasm/asmdisk02
/dev/oracleasm/asmdisk06
/dev/oracleasm/asmdisk01
/dev/oracleasm/asmdisk05
/dev/oracleasm/asmdisk07
/dev/oracleasm/asmdisk04
/dev/oracleasm/asmdisk03
7 rows selected.
SQL> create spfile from pfile;
File created.
[oracle@ocm200 dbs]$ srvctl modify asm -spfile /u01/grid/19c/dbs/spfile+ASM.ora
[oracle@ocm200 dbs]$
[oracle@ocm200 dbs]$ srvctl config asm
ASM home: <CRS home>
Password file:
Backup of Password file:
ASM listener: LISTENER
Spfile: /u01/grid/19c/dbs/spfile+ASM.ora
ASM diskgroup discovery string: /dev/oracleasm/*
[oracle@ocm200 dbs]$
[oracle@ocm200 ~]$ crsctl stop has
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'ocm200'
CRS-2673: Attempting to stop 'ora.DATA.dg' on 'ocm200'
CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'ocm200'
CRS-2677: Stop of 'ora.DATA.dg' on 'ocm200' succeeded
CRS-2673: Attempting to stop 'ora.evmd' on 'ocm200'
CRS-2673: Attempting to stop 'ora.FRA.dg' on 'ocm200'
CRS-2677: Stop of 'ora.FRA.dg' on 'ocm200' succeeded
CRS-2673: Attempting to stop 'ora.asm' on 'ocm200'
CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'ocm200' succeeded
CRS-2677: Stop of 'ora.evmd' on 'ocm200' succeeded
CRS-2677: Stop of 'ora.asm' on 'ocm200' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'ocm200'
CRS-2677: Stop of 'ora.cssd' on 'ocm200' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'ocm200' has completed
CRS-4133: Oracle High Availability Services has been stopped.
[oracle@ocm200 ~]$
[oracle@ocm200 ~]$
[oracle@ocm200 ~]$
[oracle@ocm200 ~]$ crsctl start has
CRS-4123: Oracle High Availability Services has been started.
[oracle@ocm200 ~]$ crsctl stat res -t
--------------------------------------------------------------------------------
Name Target State Server State details
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA.dg
ONLINE ONLINE ocm200 STABLE
ora.FRA.dg
ONLINE ONLINE ocm200 STABLE
ora.LISTENER.lsnr
ONLINE INTERMEDIATE ocm200 Not All Endpoints Re
gistered,STABLE
ora.asm
ONLINE ONLINE ocm200 Started,STABLE
ora.ons
OFFLINE OFFLINE ocm200 STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
1 ONLINE ONLINE ocm200 STABLE
ora.diskmon
1 OFFLINE OFFLINE STABLE
ora.evmd
1 ONLINE ONLINE ocm200 STABLE
--------------------------------------------------------------------------------
Ready. That’s it.
Conclusion
By following these steps, you have seen that cloning of a pre-configured VM with Oracle Restart is possible, and from my point of view much faster compared to re-installing the OS, GI Software, Patching … and so on, which you would have done otherwise. Besides that, it is a cool exercise, because you might learned something new about Oracle Restart, and re-configuring it. 😉
Cheers
William