Security - Oracle Exadata Recipes: A Problem-Solution Approach - page 357

Stop your Oracle databases and cluster resources using srvctl and/or crsctl . 2.

Launch cellcli from any storage cell in your Exadata storage grid and create a key: 3.

CellCLI> create key
f3eda381ef98b0dcc1a1d89b6249d042
CellCLI>

With this key, create a cellkey.ora with the key generated above on one of the compute
nodes as the Grid Infrastructure owner. In the following example, the cellkey.ora file is
placed in the grid account's home directory:

4.

[grid@cm01dbm01 ~]$ cat cellkey.ora
key=f3eda381ef98b0dcc1a1d89b6249d042
asm=+ASM
#realm=my_realm
[grid@cm01dbm01 ~]$

Use dcli to alter each of your grid disks and make them available to the
+ASM db_unique_name :

5.

[oracle@cm01dbm01 ~]$ dcli -g ./cell_group "cellcli -e \
alter griddisk all availableTo=\'+ASM\'"
cm01cel01: GridDisk DATA_CD_00_cm01cel01 successfully altered
cm01cel01: GridDisk DATA_CD_00_cm01cel02 successfully altered
... Additional output omitted

■ in the this command, we're making all grid disks available to the “ +ASM ” aSM instance; you can opt to choose
only a subset of the grid disks, if so desired.

Note

Copy the cellkey.ora file created previously to /etc/oracle/cell/network-config
directory on each compute node and set permissions to 600:

6.

[grid@cm01dbm01 ~]$ dcli -g ./dbs_group "cellcli -l grid -f \
/home/grid/cellkey.ora -d /etc/oracle/cell/network-config/
[grid@cm01dbm01 ~]$ dcli -g ./dbs_group "cellcli -l grid -f \
chmod 600 /etc/oracle/cell/network-config/cellkey.ora
[grid@cm01dbm01 ~]$

7. Finally, start CRS on each compute node and validate your environment.