list celldisk attributes name, deviceName, diskType, physicalFirmware

list cell attributes name, deviceName, diskType, physicalFirmware

list physicaldisk attributes name, deviceName, diskType, physicalFirmware

list devices attributes name, deviceName, diskType, physicalFirmware

The sparse_<DBM_NAME> diskgroup is created automatically.

There is free space available on the hard disks inside the database servers for possible extension of the /uoi file system.

The DATA_<DBM_Name> and RECO_<DBM_NAME> ASM diskgroups are built on with DATA on the outer-most tracks and RECO on the inner-most tracks of the physical disk.

There is free space available on flashdisks inside the Exadata storage servers for possible use for storage indexes.

There is free space available on flashdisks inside the Exadata storage servers to configure Exadata Smart Flash Logs.

YOU query VSSYSTEM_EVENTS and filter for the event 'cell physical IO interconnect bytes returned by smart scan', associated to your table.

You query v$segment_statistics and filter for the Object ID of your table from dba_objects and the the column STATISTIC_NAME='optimized physical reads'.

You query v$SYSTAT and filter for the statistic 'cell smart table scan', associated to your table.

You run the CellCli-command list activerequest , filtering for the attributes ioReason and objectNumber, that you specify as 'Smart Scan' and the Object ID of your table from DBA_OBJECTS.

The entire access route to the installation site should be free of raised-pattern flooring that can cause vibration.

914mm of space required above the rack height is required for maintenance access.

The incline of any access route ramp must be less than or equal to 6 degrees.

All four leveling and stabilizing feet should be raised and out of the way prior to moving the rack.

Oracle Exadata Rack may only be installed on raised floor environments.

dbmcli -e "set alert ds_temp> 30" on each database server

dbmcli -e "set threshold ds_temp comparison=' >', critical=30" on each database server

dbmcli -e "alert metriccurrent ds_temp where metricValue > 30" on each database server

dbmcli -e "create threshold ds_temp comparison='>', critical=30" on each database server

OS I/O metrics using Enterprise Manager host pages for the storage servers

OS I/O metrics using OS tools such as iostat on the database servers

I/O-specific dynamic performance views such as v$iostat_fiie, v$iostat_function, and v$iostat_consumer_group from the prod database instances using SQL *p1us

cellcli (or exacli/exadcli) to examine storage server metrics such as database, category, ceiidisk, and griddisk

OS I/O metrics using OS tools such as iostat on the storage servers

CeLLCLI> alter cell shutdown SERVICES all on the affected storage server

CeLLCLI> list GRIDDISK where status != 'inactive' on the affected storage server

'crsct1 stop cluster -all' on one of the database servers

CellCLI LIST GRIDDISK ATTRIBUTES name WHERE asmdeactivationoutcome!= 'Yes' on the affected Storage server

CellCLI alter GRIDDISK all inactive on the affected storage server

Failure groups are created for each grid disk to ensure mirror copies are written to the same storage server for faster recovery after a physical disk failure.

Failure groups contain all ASM disks in a single storage server preventing mirror copies being written to the same storage server.

They ensure that the ASM Flex instances are enabled on a maximum of two database servers or VMs per cluster.

Extended Redundancy mirrors data across data centers providing the highest levels of data protection.