Your customer wants you to partition the database and storage grids in his X3-2 full rack, creating
database clusters and two storage grids.
One cluster will be used for production and should consist of 6 databases servers and 11 cells
from the first storage grid.
The other cluster will be used for test and development, and should consist of 2 database servers
and 3 cells from the second storage grid.
The storage must be partitioned so that the cells are visible only to the appropriate database
servers based on the description above.
What must be done to achieve this?
Configure Exadata realms using Oracle ASM scoped security mode.
Configure Exadata realms using Database scoped security mode.
Edit the CELLIP.ORA file on each database server to contain IP addresses of cells in the
storage grid associated with cluster to which that database server belongs.
Edit the CELLINIT.ORA file on each database server to contain IP addresses of cells in the
storage grid associated with the cluster to which that database server belongs.
Edit the CELLIP.ORA file on each database server to contain IP addresses of database servers
which are allowed access to specific cells in the same storage grid.
Edit the CELLIP.ORA file on each cell to contain IP addresses of database servers in the
database server grid that are associated with the storage grid to which that cell belongs.
The cellip.ora is the configuration file, on every compute node, that tells ASM instances which cells
are available to this cluster.
Here is a content of a typical cellip.ora file for a quarter rack system:
$ cat /etc/oracle/cell/network-config/cellip.ora
Now that we see what is in the cellip.ora, the grid disk path, in the examples above, should make
*cellinit.ora decides which network takes storage traffic.
*cellip.ora – list of cells, new cells can be added dynamically without shutdown