Ok. Then the sole difference is that LGWR and DBWR will write on exadata cell disks instead of normal disks
LGWR and DBWR work the same way on Exadata as on any other platform.
So, when you know that
When you do an update on any row, the blocks containing this row will be read into the SGA, and modified, like in any non-Exadata Oracle database.
1) Where that modified data will be temporary stored? Is there a buffer cache in the storage tier where this modified data are put?The same as in a normal database it will be even before commit changed in the buffer cache and flushed to disk if the block ages out (same for the undo).
2) When I commit those modifications, will the DBWR (when it will wake up) puts the modified data into the exadata cells disks taking the modified data blocks from theBefore or after commit the DBWR will put the modified data into the exadata cells disks. So when you do a smart scan the SCN of your session will be leading and oracle will bring all blocks with a lower SCN into the PGA.
storage buffer cache?