that’s me when it comes to tuning your Oracle database.
Tuning an Oracle database is nothing more than configuring the system and program global areas and locking them into memory. This is relatively simple on Solaris and most Linux distributions.
Oracle has been building in tuning features for thirty years. They have succeeded with version 11g, and improved on it in Oracle12c Enterprise Editions (only). Not all features are turned on by default, or design. Several things must be checked with possible configuration changes in order to allow them to work. Kernel settings and swap type, size and location, are also validated. It still takes an expert to turn some of them on,.. and it may require restarts, or a prototype, to test production systems.
An Oracle database, properly installed and configured, works as fast as it is allowed under all circumstances. For those occasions when it does not, we use the Oracle Wait Interface (OWI) to determine why not. Your database does not “slow down”, it runs full speed, or it “waits”. When it waits, there is always an identifiable fix. If it waits too long and too often, it sure seems to slow down.
One client was using Oracle label security (OLS) and we found that row level security was averaging between 25 and 33% of all available CPU. It was found taking 93 minutes of CPU time in one three hour block. We reduced this to 14 minutes by using the OWI to create and save optimal execution plans.
In addition to tuning your Oracle database you must tune the SQL code, too. Oracle can tune itself and all application SQL including that in Java and 3rd party applications. It can do this automatically, and it can provide all the documentation required on the execution plans. In 12c, It can now even change a plan during execution. It takes set up, and monitoring; but, once you see what it does, you won’t stop it.
Let me tune your Oracle Enterprise database and configure it to tune itself.
Whether you need to migrate earlier versions of Oracle to Oracle12c, or simply move your Oracle database to the cloud, I have experience doing both. My recent experience is with Amazon Web Services (AWS), using both EC2 and RDS instances.
Migrations of any Oracle edition can be accomplished as well as several high availability options. Tuning Oracle instances and 3rd party applications requires Enterprise Edition. Any instances that I create will be done using Oracle Technical Network (OTN) Developer’s Licenses. You will be responsible for any required production licenses.
If you are thinking about leaving Oracle, please check out my post on migrating to PostgreSQL