Related Titles
- Full Description
-
Throughout history, advances in technology have come in spurts. A single great idea can often spur rapid change as the idea takes hold and is propagated, often in totally unexpected directions. Exadata embodies such a change in how we think about and manage relational databases. The key change lies in the concept of offloading SQL processing to the storage layer. That concept is a huge win, and its implementation in the form of Exadata is truly a game changer.
Expert Oracle Exadata will give you a look under the covers at how the combination of hardware and software that comprise Exadata actually work. Authors Kerry Osborne, Randy Johnson, and Tanel Põder share their real-world experience, gained through multiple Exadata implementations with the goal of opening up the internals of the Exadata platform. This book is intended for readers who want to understand what makes the platform tick and for whom"how" it does what it is does is as important as what it does. By being exposed to the features that are unique to Exadata, you will gain an understanding of the mechanics that will allow you to fully benefit from the advantages that the platform provides.
- Will changes the way you think about managing SQL performance and processing
- Provides a roadmap to laying out the Exadata platform to best support your existing systems
- Dives deeply into the internals, removing the black box mystique and showing how Exadata actually works
What youll learn
- Configure Exadata from the ground up
- Optimize for mixed OLTP/DW workloads
- Migrate large data sets from existing systems
- Connect Exadata to external systems
- Support consolidation strategies using the Resource Manager
- Configure high-availability features of Exadata, including real application clusters (RAC) and automatic storage management (ASM)
- Apply tuning strategies utilizing the unique features of Exadata
Who this book is for
Expert Oracle Exadata is for database administrators and developers who want to understand what makes Exadata unique so that they can take advantage of all the platform has to offer. It is also for anyone who needs to plan and execute migrations of systems to the Exadata platform. Finally, the book will be invaluable to those who support and maintain such systems.
- Table of Contents
-
Table of Contents
- What Is Exadata?
- Offloading / Smart Scan
- Hybrid Columnar Compression
- Storage Indexes
- Exadata Smart Flash Cache
- Exadata Parallel Operations
- Resource Management
- Configuring Exadata
- Recovering Exadata
- Exadata Wait Events
- Understanding Exadata Performance Metrics
- Monitoring Exadata Performance
- Migrating to Exadata
- Storage Layout
- Compute Node Layout
- Unlearning Some Things We Thought We Knew
- Errata
-
If you think that you've found an error in this book, please let us know about it. You will find any confirmed erratum below, so you can check if your concern has already been addressed.
On page Chapter 7 Page 221:Bottom of page. The listmetricurrent example shows a value of zero and the bullet list right after only shows 1,2 and 3. Not clear how to read this.
On page Chapter 2 Page 39:Table 2.1 has first line of data: Compression and Always malformed as Compression Alwa <space or tab> ys. So the columns do not line up properly.
On page 35:Firstly, congratulation. This e-book really rocks!
Just a minor error:
Cahpter 2 - page 35
Hints in SQL Query at the bottom:
select /*+ bloom join 2 use_hash(skew temp_skew)
If it is intended to be a comment, then the "+" sign should be removed. If it is intended to be a hint, then the use_hash needs correct aliases a b as well as the words "bloom join 2" should be at the end of the hint.
On page 73:page 73: “the two Zlib-based options (QUERY LOW and ARCHIVE HIGH)”
Should be:
the two Zlib-based options (QUERY HIGH and ARCHIVE LOW).
On page 157:parallel_adaptive_multi_user FALSE TRUE
should be:
parallel_adaptive_multi_user FALSE FALSE
On page 286:Just a small typo:
path in mount command reads
/root/mnt/snap
but should read
/mnt/snap/root
On page 362:ebook version
page 362:
Sentence:
So if you scan through a 10GB
compressed segment, physical read total bytes statistic would increase by 10GB, but the cell I/O
uncompressed bytes may well increase by 10 GB if that’s the total uncompressed size of the data.
Question: I am wondering whether the second 10GB should be higher than 10GB because uncompressed data should be higher?
On page 368:Sentence:
So if, for example, LGWR writes
1MB to an ASM disk group with high redundancy (triple mirroring), a total of 1.5 MB of data would be
sent over the interconnect.
I think it should be 3 MB instead of 1.5MB.






