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 184.108.40.206.1 of the storage server software.
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.
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 220.127.116.11 (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…
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.
Just recently I came across another unclear error message while troubleshooting an Oracle Instance registration with SCAN Listener. This post is one of the posts which may save quite a bit of time for people who will hit the same issue.
If you ever had tried to switch Oracle net trace than you know that it is quite straight forward to switch it on. You would say that I need to set the following parameters in the sqlnet.ora file…
After over a hundred hours of hard work, Pythian has achieved multiple specializations under our Platinum membership level of the Oracle PartnerNetwork’s OPN Specialized program. We’re proud to be recognized by Oracle as a value-added services partner.
If you have tried to automate EBS cloning then you definitely know that you can’t get through without hacking and customizing the Oracle-provided Rapid Clone utility. One of the areas we should “hack” the code to make it running in batch scripts is the services startup bit. The problem is that by default straight after Rapid Clone is completed Oracle starts all the services on the Apps node and until now there wasn’t a way to change it.