This blog post mentions some of very important components of Exadata Storage Server, which are physical disks, cell disks, grid disks and ASM disks and their correspondence.
I just got an Exadata Customer Advisory e-mail from Oracle, identifying “an important issue that needs your immediate attention” and pointing to MOS note 1265396.1. The only fix is to upgrade to the newly-released version 188.8.131.52.1 of the storage server software.
Welcome to Log Buffer, the weekly news blog about blogs in the datasphere.
I was searching oracle.com for some Exadata-related wait events, and noticed some hits popping up from formerly closely-held Exadata documentation. Upon closer look, I found the full Exadata V1 user’s guide. I hope the V2 documentation will be posted soon.
For those of you who weren’t able to attend my webinar last week “Implementing Exadata: the results are in, recordings are now available here online.
was asked “What’s the deal with Oracle removing InnoDB?” I had not heard this, so I did some research. It took less than 5 minutes to figure out what happened, and it was easy to see where the confusion is. On the MySQL products page at http://mysql.com/products/ the matrix of MySQL editions includes “MySQL Classic” which…
One of the key features of Exadata V2 is the flash cache. Although commonly thought of as an OLTP-specific feature, it has also been marketed as a data warehouse accelerator. According to this frequently-used presentation slide, a full Exadata rack provides 21 GB/sec of disk throughput and 50GB/sec of flash throughput. was testing throughput using a simple query, making use of both smart scans and parallel execution. Here’s what the objects look like. They’re running on a quarter rack system with a stated capacity of 4.5GB/sec disk and 11GB/sec flash.
The new functionality to download latest patches or either apply saved ones came with installer of Oracle 184.108.40.206 (Software Updates Option) It can be used not only through OUI but with silent installation too. There are several options and variables available to get patches from MOS: oracle.installer.autoupdates… MYORACLESUPPORT_… AUTOUPDATES_MYORACLESUPPORT_… Putting it all together I got…
Welcome to Log Buffer, the weekly roundup of happenings in the database world. Lots to cover this week, so let’s get on with Log Buffer #204. Enjoy!
One of my favorite customers had a problem. They had to load around 20G of data into a table on MySQL database. The data loaded fine, but when he tried to build few indexes on the database, he got a mysterious error: ERROR 1114 (HY000): The table ‘really_big_table’ is full. The error was mysterious because we had around 1.5T of free space on the disk. Also, if the customer created the indexes before loading the data there was no error. This gave them a work around, but one that slow and annoying. Later, I found out that we are not the first to run into this mystery.