The following commands update storage servers on three Exadata systems simultaneously from the same software directory; one update using a rolling update, the others updates are non-rolling.

In this example:

Each patchmgr command must be run from a separate terminal window.

Each patchmgr execution uses a unique logging directory name automatically generated based on the content of the component_list_file.

(terminal1) ./patchmgr -cells cell_group_exa01 -patch -rolling

thomas

not sure. DOKU lesen. hier weiter

Jhonata

A,F

Nishant Baurai

C and F are corrrect.

• Rolling: A rolling patch is performed sequentially on each storage server. The rolling patch process relies on ASM redundancy to maintain disk group availability while each storage server is updated and restarted. Databases remain operational while all of the storage servers are patched. Each storage server can take up to approximately two hours to patch. Therefore, patch application on a Full Rack Database Machine can take more than a day tocomplete.
• Non-rolling: A non-rolling patch is applied to all storage servers simultaneously with databases offline. This approach requires down time, but may be preferred if a scheduled maintenance window exists for the system. Because all of the storage servers are patched in parallel, the whole patch make take approximately two hours to complete.

ssseee

answer is B,C

-cells cell_group

After -cells parameter, you need to give a file, not cell name.

question is not valid, patchmgr for database nodes patching not cells. Command used in this questions is mix of arguments used by patchmgr and dcli