Understanding Exadata

 Exadata:

Oracle Exadata is a part of Oracle Engineered Family 

Oracle Exadata Database Machine is engineered to be the highest performing and most available platform for running Oracle Database.

It is a combination of Oracle Compute nodes and Oracle Storage nodes 

A typical Exadata machine contains 

-> Compute nodes (3,4,8)

-> Storage nodes called as cell servers (14 cells with each cell containing 12 physical disks )

-> 2 infi band switches(for intra node communication)

-> 1 cisco switch 

-> 1 spine switch to group one or more  exadata machines

-> each cell contains 4 flash cells with 6.5 TB (6.5 * 4 = 27 TB approx)


Storage server runs on OLE6/7 installed with cell software to manage the cells 



Some Important Points :

============== 

ASM disk group will be created on grid disk -> cell -> LUN -> physical disks

asm_diskstring  /o/cell ip/grid disk


How to manage Exadata:

===============

cellcli -> used to login on a storage server and can manage single cell server 

dcli -> distributed cli used to manage all the cell servers 

DBMCLI -> works on each compute node to manage cell servers

EXAcli -> used to connect to the cell server on remote host 

IDB -> intelligent protocol used by the compute nodes and database nodes to transfer the data, it works on reliable data gram sockets 

ILOM -> called as Integrated lights out managers is a special piece of hardware with embodied software.

ILOM proactively manage the following

Identify hardware error and faults
Remotely control the power of the node
View current status of sensors and indicators of the system
Identify the hardware configuration of the system
Receive alerts that are generated about system events
ILOM proactively manage the following:

Identify hardware error and faults
Remotely control the power of the node
View the graphical and non-graphical console of the host
View current status of sensors and indicators of the system
Identify the hardware configuration of the system
Receive alerts that are generated about system events


Exadata Features:

  • Smart flash cache 
  • Smart flash log
  • Smart Scan
  • HCC
  • IORM
How to enable smart scan :
cell_smart_scan_capable=true
cell_offloading_processing=true
Smart scan works for 
full table /full index/direct_path 
to enable direct path _serial_direct-read=true
Smart scan is not useful during 

  • concurrent DML 
  • Excessive Row chaining 
  • if data already in buffer cache then it won't process
  • Storage server CPU utilization more that database server 
Storage index helps in eliminating I/O processing by identifying storage regions without values 
To enable flash cache we can mention 
cell_flash_cache -> default/keep/none
None -Exclude the object from the flash cache entirely.
default -> Give the object a normal priority for caching
Keep -> Give the object a higher priority for caching


Flash cache  write through -> DML directly to disk 
Flash cache write back -> DML to flash cache then to disk 







  


Comments

Popular posts from this blog

Understanding Terraform

How to make CRS and ASM not to restart after server reboot

How to repair ASM disk header