Go to main content

Oracle® SuperCluster M8 and SuperCluster M7 Zones With Oracle Database on Database Domains Configuration Guide

Exit Print View

Updated: June 2020
 
 

Verify Exadata Storage Server Disk Space for Additional Zones

Before beginning the process of creating additional zones on existing Database Domains with zones, you must first verify that you have the appropriate amount of disk space available on the Exadata Storage Servers:

  • If you are not sharing Exadata Storage Servers across clusters and you have entire Exadata Storage Servers available for the additional zones that you are adding to the existing Database Domains with zones, then you do not have to do anything more here. You can assign the entire Exadata Storage Servers to the new zones as part of this procedure.

  • If you are sharing Exadata Storage Servers across clusters, you must determine how much free space is available on the Exadata Storage Servers that you are using for these new zones before proceeding.


Note -  If you are sharing Exadata Storage Servers across clusters, you must follow the procedures in this section so that you will have the correct information before deciding on the size of the disk groups for the new clusters that you will be creating. Failure to do so could result in your existing disk groups being overwritten.
  1. Determine the amount of free space available on the Exadata Storage Servers:
    CellCLI> list celldisk attributes name,freespace,freespacemap
    

    You should see output similar to the following:

    CD_00_etc25celadm01	 366.6875G	 ((offset=162.046875G,size=366.6875G))
    CD_01_etc25celadm01	 366.6875G	 ((offset=162.046875G,size=366.6875G))
    CD_02_etc25celadm01	 393.8125G	 ((offset=164.046875G,size=393.8125G))
    CD_03_etc25celadm01	 393.8125G	 ((offset=164.046875G,size=393.8125G))
    CD_04_etc25celadm01	 393.8125G	 ((offset=164.046875G,size=393.8125G))
    CD_05_etc25celadm01	 393.8125G	 ((offset=164.046875G,size=393.8125G))
    CD_06_etc25celadm01	 393.8125G	 ((offset=164.046875G,size=393.8125G))
    CD_07_etc25celadm01	 393.8125G	 ((offset=164.046875G,size=393.8125G))
    CD_08_etc25celadm01	 393.8125G	 ((offset=164.046875G,size=393.8125G))
    CD_09_etc25celadm01	 393.8125G	 ((offset=164.046875G,size=393.8125G))
    CD_10_etc25celadm01	 393.8125G	 ((offset=164.046875G,size=393.8125G))
    CD_11_etc25celadm01	 393.8125G	 ((offset=164.046875G,size=393.8125G))
    FD_00_etc25celadm01	 0
    FD_01_etc25celadm01	 0
    FD_02_etc25celadm01	 0
    FD_03_etc25celadm01	 0
    FD_04_etc25celadm01	 0
    FD_05_etc25celadm01	 0
    FD_06_etc25celadm01	 0
    FD_07_etc25celadm01	 0
    FD_08_etc25celadm01	 0
    FD_09_etc25celadm01	 0
    FD_10_etc25celadm01	 0
    FD_11_etc25celadm01	 0
    FD_12_etc25celadm01	 0
    FD_13_etc25celadm01	 0
    FD_14_etc25celadm01	 0
    FD_15_etc25celadm01	 0
    
  2. Look at the CD_number entries to determine the amount of available space on each of the Exadata Storage Servers.
  3. Use the information on the amount of available space on each of the Exadata Storage Servers to determine how much space you can use for the disk groups for each new cluster you are creating for the new zones.

    You need enough space for these disk groups for each new cluster that you are creating:

    • DATA

    • RECO

    • DBFS (if necessary)