Académique Documents
Professionnel Documents
Culture Documents
Applies to:
Goal
The present document provide in detail the steps to shutdown/startup the Exadata & RDBMS
services along with the Cell/Compute nodes on an Exadata Configuration:
Fix
# cd /opt/oracle.SupportTools/onecommand
3) Note whether the Grid Infrastructure is currently enabled for autostart, so that this state can
be restored later:
4) Disable the Grid Infrastructure for autostart on the database servers if the previous step
indicated it is currently enabled for autostart.
Note: This is step is [Optional] and it can required during maintenance operation like
"firmware patches" which requires to reboot the Compute Node several times.
5) Stop the Grid Infrastructure stack on the database servers (compute nodes):
6) Verify that the Grid Infrastructure stack has shutdown successfully on the database servers.
The following command should show no output if the GI stack has shutdown:
7) [Optional] Disable email/SNMP alerts if applicable. If alerts will be enabled, first note the
notification method in use so that it can be restored later. The following command will show
the current notification method:
# dcli -g cell_group -l root "su - celladmin -c \"cellcli -e alter cell shutdown services
all \""
# cp /opt/oracle.SupportTools/onecommand/dbs_group
/opt/oracle.SupportTools/onecommand/dbs_group2
12) Power off all the compute nodes (expect compute node # 1):
# dcli -g dbs_group2 -l root poweroff
# poweroff
14) Now, both Cell Servers & Compute nodes are down for maintenance.
15) Power compute node #1 on, by using the power button on the front panel of the
Exadata Storage Servers.
16) Power the cells on, either by using the power button on the front panel of the Exadata
Storage Servers, or by executing the following script from the first database server (from
Compute node #1):
17) Wait until all the Cell servers are up, then power the compute nodes on, either by using
the power button on the front panel of the Exadata Storage Servers, or by executing the
following script from the first database server:
18) Verify that all Exadata Storage Servers have booted successfully:
19) Verify all the cells are up (MS, RS & CELLSRV services must be running):
# dcli -g cell_group -l root "su - celladmin -c \"cellcli -e list cell detail \""
20) Reenable email/SNMP alerts if they were disabled during the pre-maintenance steps. The
example below illustrates the command to use if both email and SMTP alerting used, but
adjust the command as necessary to restore the notification method noted during the pre
maintenance steps.
21) Start the Grid Infrastructure stack on the first database server
22) Wait until the Grid Infrastructure stack has started successfully on the first database
server. To check the status of the Grid Infrastructure stack, run the following command and
verify that the "ora.asm" instance is started. Note that the command below will continue to
report that it is unable to communicate with the Grid Infrastructure software for several
minutes after issuing the "crsctl start crs" command above:
23) Start the Grid Infrastructure stack on all remaining database servers with a 1-minute delay
between servers. Note that the command below will issue the start command for all database
servers, including the first database server where it is already started. The output for the first
server will therefore indicate that the software is already started, but this message can be
safely ignored:
24) Monitor the startup progress (this could take several minutes):
25) Reenable the Grid Infrastructure for autostart if it was found to be enabled for autostart at
the beginning of the pre-maintenance steps.