Oracle Database 19c: The best upcoming features..!!
By Rodrigo Jorge
In the Oracle Open World 2018 event that happened in San Francisco last week, from October 22nd to 25th, much has been said about the trends and strategy paths that Oracle is taking in both OCI and in Oracle Database.
As we DBA’s are always excited about the upcoming features, We will share below some of the main things that I’ve spotted on OOW. Please note that this can change, and we don’t even have a beta release yet.
First of all, it was very clear that Oracle’s main focus for the 19c database will be stability. This will be the final release for the “12cR2” family. So it was repeated multiple times: “don’t expect to see many new features in this release“, what in my opinion is really great.
Since 184.108.40.206, Oracle has been implementing a lot of core changes in Oracle Database (like multi-tenancy, unified audit, etc) and it’s still very hard nowadays to find a stable 12 release to recommend. 220.127.116.11 is my favorite one, however many bugs are unfixed and it lacks a secure PDB layout (PDB escape techniques are pretty easy to explore). 18c will probably be ignored by all as it was a “transition” release, so I hope that 19c becomes the real stable one, as 18.104.22.168 was for 11g release family. Let’s see…
This is indeed the most important and one of the coolest features I’ve even seen in Oracle DB. Once this kind of automation is implemented and released, it will open doors to many other product automations (like automatic table reorganization, automatic table encryption or anything you can imagine).
The automatic indexing methodology will be based on a common approach to manual SQL Tuning. Oracle will capture the SQL statements, identify the candidate indexes and evaluates the ones that will benefit those statements. The whole process is not something simple.
Basically, Oracle will first create those indexes as unusable and invisible (metadata only). Then, outside the application workflow, oracle will ask the optimizer to test if those candidate indexes improve the SQL performance. In case the performance is better for all statements when indexed is used, it will become visible. If performance is worse, it remains invisible. And if it only performs better for some statements, the index is only marked visible for those SQLs (via SQL Patch, maybe).
The automation will also drop the indexes that become obsoleted by the newly created indexes (logical merge) and also remove the indexes that were created automatically but have not been used in a long time. Everything is customizable. For more details, we need to wait for the Beta Release!
to read the rest of the article, click here:
We hope the content could be useful for your Oracle DBA Tasks!