Use this procedure to perform one of these changes to a DB VM group.
Increase the number of VMs in the group.
Increase or decrease the number of cores in VMs.
Increase the maximum allowable file size for u01. The maximum file size varies and is displayed at the appropriate prompt. You cannot decrease the file size after you have increased it.
In this example, the number of VMs on node 1 and 2 are increased from two VMs per node to three VMs per node. The new VMs are VM5 and VM6. The mcmucommand prompts for VM parameters for the new VMs. Responding with Return accepts the default value, which is displayed in parentheses.
% mcmu tenant -P -u Listing DB VM Group Profile.. Status : Active EditStatus : Description : DBVM Group 1 - NORMAL - SHARED - CIS deletable : True progress : False VMgroupName : dbgp1 editable : True VMgroupID : 1 Enter ID of the VM Group Profile that you want to edit[1] (1): 1 Do you want to "[E]dit & Save the changes"? Enter Y/N (Y): Y Getting DB VM Group Profile... Edit Database Virtual Machine Group Profile Description Virtual Machine Group Profile Name : dbgp1 Enter Number of VM(s) on Node 1, between(2,4) (2): 3 Enter Number of VM(s) on Node 2, between(2,4) (2): 3 Enter Description (DB MVM Group 1 - NORMAL - SHARED - CIS): <Return> Virtual Machine Group Profile Name : dbgp1 . <output omitted> . ASM Disk Group Redundancy : NORMAL PCI DSS Security Setting Enabled: No Enter u01 size (in GB, 100 to max 2182) (165): 200 Number of Disks : None Number of VM(s) on Node 1 : 3 Number of VM(s) on Node 2 : 3 Description : DBVM Group 1 - NORMAL - SHARED - CIS Virtual Machines Information Node 1 : mc3-n1 Virtual Machine 1 CURRENT VM STATUS: active Public Hostname mc3-n1vm1-z1 Public IP: xx.xxx.73.196 Private Hostname mc3-n1vm1-z1-priv Private IP: 192.0.2.6 Virtual Hostname mc3-n1vm1-z1-vip Virtual IP: xx.xxx.73.197 Enter Cores [0 to max 7] (4): <Return> Virtual Machine 2 CURRENT VM STATUS: active Public Hostname mc3-n1vm1-z2 Public IP: xx.xxx.73.198 Private Hostname mc3-n1vm1-z2-priv Private IP: 192.0.2.7 Virtual Hostname mc3-n1vm1-z2-vip Virtual IP: xx.xxx.73.199 Enter Cores [0 to max 3] (3): <Return> Virtual Machine 3 Enter Public Hostname (dbgp1-vm3-mc3-n1): mc3-n1vm1-z3 Enter Public IP (To be generated): <Return> Enter Private Hostname (mc3-n1vm1-z3-priv): <Return> Enter Private IP (To be generated): <Return> Enter Virtual Hostname (mc3-n1vm1-z3-vip): <Return> Enter Virtual IP (To be generated): <Return> Enter Cores [0 to max 0] (0): <Return> Node 2: mc3-n2 Virtual Machine 1 CURRENT VM STATUS: active Public Hostname mc3-n2vm1-z1 Public IP: xx.xxx.73.100 Private Hostname mc3-n2vm1-z1-priv Private IP: 192.0.2.2 Virtual Hostname mc3-n2vm1-z1-vip Virtual IP: xx.xxx.73.101 Enter Cores [0 to max 12] (0): <Return> Virtual Machine 2 CURRENT VM STATUS: active Public Hostname mc3-n2vm1-z2 Public IP: xx.xxx.73.102 Private Hostname mc3-n2vm1-z2-priv Private IP: 192.0.2.5 Virtual Hostname mc3-n2vm1-z2-vip Virtual IP: xx.xxx.73.106 Enter Cores [0 to max 12] (0): Virtual Machine 3 Enter Public Hostname (dbgp1-vm3-mc3-n2): mc3-n2vm1-z3 Enter Public IP (To be generated): <Return> Enter Private Hostname (mc3-n2vm1-z3-priv): <Return> Enter Private IP (To be generated): <Return> Enter Virtual Hostname (mc3-n2vm1-z3-vip): <Return> Enter Virtual IP (To be generated): <Return> Enter Cores [0 to max 12] (0): <Return> Cluster Information SCAN name : dbgp1-scan SCAN IPs :192.0.2.7,192.0.2.8,1,192.0.2.9. . <output omitted> . status: 0 message: Updating DB VM Group Profile succeeded Getting DB VM Group Profile... PROFILE INFORMATION VMGroupName : dbgp1 SCAN_name : dbgp1-scan SCAN_ip : 192.0.2.10,1192.0.2.11,192.0.2.12 VM DEFINITIONS VM 1 name : dbgp1-vm1-mc3-n1 globalName : mc3-n1 public_ip : xx.xxx.73.113 public_hostname : mc3-n1vm1-z1 virtual_ip : 192.0.2.14 virtual_hostname : mc3-n1vm1-z1-vip VM 2 name : dbgp1-vm2-mc3-n1 globalName : mc3-n1 public_ip : xx.xxx.73.115 public_hostname : mc3-n1vm1-z2 virtual_ip : 192.0.2.16 virtual_hostname : mc3-n1vm1-z2-vip VM 3 name : dbgp1-vm1-mc3-n2 globalName : mc3-n2 public_ip : xx.xxx.73.117 public_hostname : mc3-n2vm1-z1 virtual_ip : 192.0.2.18 virtual_hostname : mc3-n2vm1-z1-vip VM 4 name : dbgp1-vm2-mc3-n2 globalName : mc3-n2 public_ip : xx.xxx.73.119 public_hostname : mc3-n2vm1-z2 virtual_ip : 192.0.2.20 virtual_hostname : mc3-n2vm1-z2-vip VM 5 name : dbgp1-vm3-mc3-n1 globalName : mc3-n1 public_ip : xx.xxx.73.120 public_hostname : mc3-n1vm1-z3 virtual_ip : 192.0.2.22 virtual_hostname : mc3-n1vm1-z3-vip VM 6 name : dbgp1-vm3-mc3-n2 globalName : mc3-n2 public_ip : xx.xxx.73.121 public_hostname : mc3-n2vm1-z3 virtual_ip : 192.0.2.24 virtual_hostname : mc3-n2vm1-z3-vip Please insert the IP-mappings in the DNS Server if not already done. Aug 24 17:17:29 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2 Setting ssh timeout before exiting. Please wait.. mcinstall@mc3-n1:/var/home/mcinstall % mcinstall@mc3-n1:/var/home/mcinstall % mcinstall@mc3-n1:/var/home/mcinstall %
When prompted to edit, save, or apply, specify A for apply.
% mcmu tenant -P -u Setting ssh timeout before carrying out further operations. Please wait.. [INFO ] Log file path : /var/opt/oracle.minicluster/setup/logs/tenant_cli_082416_171912.log Listing DB VM Group Profile.. Status : Active EditStatus : edited Description : DB MVM Group 1 - NORMAL - SHARED - CIS deletable : True progress : False VMgroupName : dbgp1 editable : True VMgroupID : 1 Enter ID of the VM Group Profile that you want to edit[1] (1): <Return> Do you want to "[E]dit & Save" or "[A]pply previously saved changes"? Enter E/A (E): A . <output omitted> . INFO:MCMU.controllers.dbzonegroupmanager:Zonegroup is updated with profile changes. status: 0 message: Updating DB VM Group succeeded. Getting DB VM Group Profile.... . <output omitted> .
In this example, VMs with ID 23 (one on each node) are new DB VMs displayed with a status of running.
% mcmu status -Z -a [INFO ] Log file path : mc3-n1:/var/opt/oracle.minicluster/setup/logs/mcmu_082416_180834.log [INFO ] Zone status on node1 ID NAME STATUS PATH BRAND IP 0 global running / solaris shared 2 acfskz running - solaris-kz excl 7 dbgp1-vm1-mc3-n1 running /mcpool/dbgp1-vm1-mc3-n1zroot solaris excl 8 dbgp1-vm2-mc3-n1 running /mcpool/dbgp1-vm2-mc3-n1zroot solaris excl 1 avm1-vm1-mc3-n1 running /mcpool/avm1-vm1-mc3-n1zroot solaris excl 14 avm2-vm1-mc3-n1 running /mcpool/avm2-vm1-mc3-n1zroot solaris excl 17 avm4-vm1-mc3-n1 running /mcpool/avm4-vm1-mc3-n1zroot solaris excl 20 avm5-vm1-mc3-n1 running /mcpool/avm5-vm1-mc3-n1zroot solaris excl 23 dbgp1-vm3-mc3-n1 running /mcpool/dbgp1-vm3-mc3-n1zroot solaris excl - appzonetemplate installed /mcpool/appzonetemplate solaris excl - dbzonetemplate installed /mcpool/dbzonetemplate solaris excl [INFO ] Zone status on node2 ID NAME STATUS PATH BRAND IP 0 global running / solaris shared 2 acfskz running - solaris-kz excl 7 dbgp1-vm1-mc3-n2 running /mcpool/dbgp1-vm1-mc3-n2zroot solaris excl 8 dbgp1-vm2-mc3-n2 running /mcpool/dbgp1-vm2-mc3-n2zroot solaris excl 11 avm1-vm1-mc3-n2 running /mcpool/avm1-vm1-mc3-n2zroot solaris excl 14 avm2-vm1-mc3-n2 running /mcpool/avm2-vm1-mc3-n2zroot solaris excl 17 avm6-vm1-mc3-n2 running /mcpool/avm6-vm1-mc3-n2zroot solaris excl 20 avm7-vm1-mc3-n2 running /mcpool/avm7-vm1-mc3-n2zroot solaris excl 23 dbgp1-vm3-mc3-n2 running /mcpool/dbgp1-vm3-mc3-n2zroot solaris excl - appzonetemplate installed /mcpool/appzonetemplate solaris excl - dbzonetemplate installed /mcpool/dbzonetemplate solaris excl
If you didn't add DB VMs, this step doesn't apply.
The new VMs do not show up in the list. After the new instances are created, you can compare this list with a new list. See Step 7.
% mcmu tenant -I -l 1 Aug 24 18:10:01 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2 LIST OF DB INSTANCES IN DB VM GROUP 1 ID: 3, NAME: dw12rac, VM_ID: 1, DBHOME_ID: 1, TYPE: RAC, STATUS: Active ID: 12, NAME: ol11rac1, VM_ID: 1, DBHOME_ID: 5, TYPE: RACONENODE, STATUS: Active ID: 14, NAME: ol12sinC, VM_ID: 2, DBHOME_ID: 2, TYPE: SINGLE, STATUS: Active ID: 7, NAME: dw11rac, VM_ID: 2, DBHOME_ID: 6, TYPE: RAC, STATUS: Active ID: 4, NAME: dw12rac, VM_ID: 3, DBHOME_ID: 3, TYPE: RAC, STATUS: Active ID: 11, NAME: ol11rac1, VM_ID: 3, DBHOME_ID: 7, TYPE: RACONENODE, STATUS: Active ID: 8, NAME: dw11rac, VM_ID: 4, DBHOME_ID: 8, TYPE: RAC, STATUS: Active ID: 16, NAME: dw11sin, VM_ID: 4, DBHOME_ID: 8, TYPE: SINGLE, STATUS: Active
You are prompted to provide instance parameters.
% mcmu tenant -I -c Database Instance Profile Description Select Database Instance Type [SINGLE/RAC/RACONE] : rac Select Database Instance Template: Data Warehouse(DW) / Online Transaction Processing(OLTP) [DW/OLTP] : oltp List of Character Set [1] AL32UTF8 [2] AR8ADOS710 [3] AR8ADOS710T . <output omitted> . [112] ZHT16HKSCS [113] ZHT16MSWIN950 [114] ZHT32EUC [115] ZHT32SOPS [116] ZHT32TRIS [117] US7ASCII Select Character Set Number (1): 115 List of National Character Set [1] AL16UTF16 [2] UTF8 Select National Character Set Number (1): <Return> Listing DB VM Group Profile.. Status : Active EditStatus : Description : DB MVM Group 1 - NORMAL - SHARED - CIS deletable : True progress : False VMgroupName : dbgp1 editable : True VMgroupID : 1 Select Database VMgroupID [1] (1): List of All Active VMs in VM Group dbgp1 Getting DB VM Group... status : Active name : dbgp1-vm1-mc3-n1 globalName : mc3-n1 id : 1 memory : 522496 cores : 4 status : Active name : dbgp1-vm2-mc3-n1 globalName : mc3-n1 id : 2 memory : 522496 cores : 3 status : Active name : dbgp1-vm1-mc3-n2 globalName : mc3-n2 id : 3 memory : 522496 cores : 0 status : Active name : dbgp1-vm2-mc3-n2 globalName : mc3-n2 id : 4 memory : 522496 cores : 0 status : Active name : dbgp1-vm3-mc3-n1 <<=== NEW VM globalName : mc3-n1 id : 13 memory : 522496 cores : 0 status : Active name : dbgp1-vm3-mc3-n2 <<=== NEW VM globalName : mc3-n2 id : 14 memory : 522496 cores : 0 Select Database VM ID [1/2/3/4/13/14] : 13 <<=== ID of New VM List of All Active DB home in zone dbgp1-vm3-mc3-n1 Listing DB Home... status : Active VM_id : 13 version : 12.1.0.2 home : /u01/app/oracle/product/12.1.0/dbhome_12c type : RAC id : 9 status : Active VM_id : 13 version : 11.2.0.4 home : /u01/app/oracle/product/11.2.0/dbhome_11g type : RAC id : 11 Select Database Home ID [9/11] : 9 Select one VM from the other compute node status : Active name : dbgp1-vm1-mc3-n2 globalName : mc3-n2 id : 3 memory : 522496 cores : 0 status : Active name : dbgp1-vm2-mc3-n2 globalName : mc3-n2 id : 4 memory : 522496 cores : 0 status : Active name : dbgp1-vm3-mc3-n2 globalName : mc3-n2 id : 14 memory : 522496 cores : 0 Select Secondary Database VM ID [3/4/14] : 14 <<=== ID of new VM on second node Enter Container Database [True/False] (false): Enter PGA (Program Global Area) in MB (2560): 5120 Enter SGA (System Global Area) in MB (6400): 12800 Enter Database Instance Name : ol12rac List of Inputs for DB Instance Creation: Database Instance Type: RAC Database Instance Template: OLTP VM: dbgp1-vm3-mc3-n1,dbgp1-vm3-mc3-n2 (ID: 13,14) Database Home: /u01/app/oracle/product/12.1.0/dbhome_12c (ID: 9) PGA (Program Global Area) in MB: 5120 SGA (System Global Area) in MB: 12800 Database Instance Name: ol12rac Character Set: US7ASCII National Character Set: AL16UTF16 Container Database : false Do you want to change the inputs? Enter Y/N (N): N Creating DB Instance... . <output omitted> .
% mcmu tenant -I -l 1 Aug 24 18:43:12 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2 LIST OF DB INSTANCES IN DB VM GROUP 1 ID: 3, NAME: dw12rac, VM_ID: 1, DBHOME_ID: 1, TYPE: RAC, STATUS: Active ID: 12, NAME: ol11rac1, VM_ID: 1, DBHOME_ID: 5, TYPE: RACONENODE, STATUS: Active ID: 14, NAME: ol12sinC, VM_ID: 2, DBHOME_ID: 2, TYPE: SINGLE, STATUS: Active ID: 7, NAME: dw11rac, VM_ID: 2, DBHOME_ID: 6, TYPE: RAC, STATUS: Active ID: 4, NAME: dw12rac, VM_ID: 3, DBHOME_ID: 3, TYPE: RAC, STATUS: Active ID: 11, NAME: ol11rac1, VM_ID: 3, DBHOME_ID: 7, TYPE: RACONENODE, STATUS: Active ID: 8, NAME: dw11rac, VM_ID: 4, DBHOME_ID: 8, TYPE: RAC, STATUS: Active ID: 16, NAME: dw11sin, VM_ID: 4, DBHOME_ID: 8, TYPE: SINGLE, STATUS: Active ID: 19, NAME: ol12rac, VM_ID: 13, DBHOME_ID: 9, TYPE: RAC, STATUS: Active ID: 20, NAME: ol12rac, VM_ID: 14, DBHOME_ID: 10, TYPE: RAC, STATUS: Active