What’s New In Oracle Database 19c

What’s New In Oracle Database 19c

19c is confirmed as Lengthy Time period Assist model, with primary assist at the least to 2022 and prolonged support to 2025. Note that in Oracle Cloud, prolonged support is without additional fees.
If you are nonetheless in 11.2.0.four because you don’t need frequent upgrades, 19c will be the release to go (however hold it up to date with Release Updates). If you want to be sure to do this upgrade as soon as 19c is available on premises, then higher to test it as soon as potential and report any bug you encounter. This means:
enter the beta program. Having a beta program for a release targeted more on stability than new features is an superior determination from Oracle Development.
test 19c in Oracle Cloud as soon as available. You may use more options than what you will have on-premises for these tests, such because the Efficiency Analyzer.


he large new thing, for my part, is that the Java One convention has been merged to Oracle Open World convention, and renamed to Oracle Code One. Interleaving Dev and Ops classes is a really good idea. The Oracle Technology Network (OTN) which turned Oracle Developer Community (ODC) is now becoming the Oracle Groundbreakers. What I like here is that there isn't a point out of technology or development. We are all in the same project: enhance the person experience with all the application components, from system to code.

This was additionally the event to provide a talk more focused at builders than at DBA. At the time of Microservices, I wished to share my expertise in Dev and Ops teams, on monolithic, oracle 18c classes consumer/server, 3-tiers,… architectures. Because segregation of responsibility is great at logical level, however the way in which to performance and scalability must usually undergo colocation in same server, process, engine…

In this speak, I mentioned Oracle XE which may be embedded for free. The 18c version of XE was released Saturday through the ACED Briefing. Lots bigger than the 11g but with more options. Compression is a vital one because the storage is proscribed to 12 GB.
19c new Optimizer features
The best you are able to do for the optimizer is offering accurate statistics. Day by day gathering on stale tables is not enough, and dynamic statistics overload parse activity too much. We will have new features:
High Frequency Automatic Statistics Activity: some statistics gathering will likely be carried out throughout the day, when the system is idle, managed by the Resource Manager.
Real-Time Statistics: some statistics (like high/low worth) are maintained throughout DML. This may be great to keep away from Out-of-Range issues with linear decay from out of date statistics.
We must always not rely on hints, but generally, we need. And we want to make certain that they're used (because no error is raised when not).
Hint Utilization Reporting: dbms_xplan reports the hints per operation and alias name, with a sign for those who were not used (and reason)
Speaking about DBMS_XPLAN, the comparison of plans have improved:
Examine SQL Execution Plans: shows directly the place the plan diverges
At execution time, when a question never ends the worst that can happen is that the impatient run it again. That’s a good idea, however all of us do that on Web applications: no answer -> hit F5 a number of times. The question won't run quicker and this only increases the contention. Then, higher to cancel the statement (resource manager can do this) and quarantine the bad execution plan:
Automatic Diagnostic and Repair and Quarantine for Runaway Statements
Of course, the big characteristic for the 19c Autonomous Transaction Processing cloud service is Automated Indexing. This deserves an extended description. The quick concept is that a background job will seize and analyze the workload on quick-term (last 15 minutes) to add better indexes, removes them, or blacklist them (SQL Patch) for some queries.
And the function I like probably the most:
Computerized SQL Plan Administration: the capture will probably be automatic
Enabling the capture for all statements executed occasions is just not simple, even with the new filters launched within the latest release. Right here, the seize relies on AWR. When a query is lengthy, the execution plan will probably be compared with past AWR snapshots. And if a better plan was used previously, then this one would be the accepted SQL Plan baseline. This is what we do manually, isn’t it?