I have the same opinion as kerry (use all as flashcache). Flash makes OLTP perform (or: mimic the SAN cache of a regular setup). And flash is rather limited in size, so if you configure flash as a diskgroup, you have to put in extra work to choose the objects to put in the flash diskgroup, and even more important: administer those, because most database objects change over time. Frits Hoogland http://fritshoogland.wordpress.com mailto: frits.hoogland@xxxxxxxxx cell: +31-6-53569942 On Mar 19, 2011, at 10:19 AM, Kerry Osborne wrote: > Hi Surachart, > > The biggest concern for me would be taking space away that could be used as > Flash Cache, which is critical for OLTP type work loads. Keep in mind that > you'll be duplicating blocks 2x or 3x depending on redundancy setting of the > grid disk (normal or high). My going in position would be to use all of the > space as Flash Cache. I would only consider creating a grid disk for very > high write objects and only if I could demonstrate a real improvement via > testing. > > Kerry Osborne > Enkitec > blog: kerryosborne.oracle-guy.com > > > > > > > On Mar 19, 2011, at 3:34 AM, Surachart Opun wrote: > >> On Exadata, You will have flashdisks. Idea to use them: >> A. Make them for Exadata Smart Flashcache >> B. Use them for Grid Disk for ASM Disk Group, and store some database files. >> C. Use both A and B in Database System >> >> I just curious, What should I concern, if use Flash Disks to be Grid Disks. >> What is you idea to use Flashdisk? However, Database System supports both >> OLTP and DSS. >> >> Thank You >> Surachart Opun >> Oracle ACE, Contributor (Oracle User Group in Thailand) >> http://surachartopun.com >> skye: surachart_op >> >> >