Why is solid state devices not a good option to store data for a very dynamic (frequent updates) oracle database?
Although for read intensive databases ssd does give a huge performance improvement.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.
SSD drives have memory cells with finite lifespans; the more you write/erase/write to the cells the sooner they go "bad" so frequently accessed drives with something like a heavily used database will drive down the life of the drive. I don't know if there are any "enterprise ready" SSD drives on the market that offer high reliability either. That would lead me to believe that the advice you've heard is because SSD drives may be more prone to failure in a relatively short time compared to fast (and field-tested) hardware solutions out there already, given the high price point of SSD drives per gigabyte.
If you're going to use that kind of solution you should be ready to deal with having it well-RAIDed with spares ready and a well tested backup and restore procedure.
When it comes to database read operations it's best they won't require any (disk) storage access at all. If read query speed is your concern make sure all data is held in-memory.
My advice just throwing as much memory as possible at your database addresses only the simple assumption that using SSD will give you better read operation performance.