What’s New In Oracle Database 19c
If you're still in 11.2.0.four because you don’t need frequent upgrades, 19c will be the launch to go (but preserve it up to date with Release Updates). If you wish to be sure you do this upgrade as quickly as 19c is available on premises, then better to test it as quickly as possible and report any bug you encounter. This means:
enter the beta program. Having a beta program for a launch centered more on stability than new features is an awesome decision from Oracle Development.
test 19c in Oracle Cloud as soon as available. Chances are you'll use more options than what you've got on-premises for these tests, such as the Efficiency Analyzer.
he massive new thing, in my view, is that the Java One convention has been merged to Oracle Open World convention, and renamed to Oracle Code One. Interleaving Dev and oracle 18c classes Ops sessions is a really good idea. The Oracle Technology Network (OTN) which turned Oracle Developer Group (ODC) is now becoming the Oracle Groundbreakers. What I like right here is that there is no point out of technology or development. We're all in the identical project: enhance the consumer expertise with all of the application components, from system to code.
This was also the event to offer a chat more focused at developers than at DBA. On the time of Microservices, I needed to share my experience in Dev and Ops groups, on monolithic, client/server, three-tiers,… architectures. Because segregation of responsibility is great at logical level, but the way to efficiency and scalability must usually undergo colocation in same server, process, engine…
In this discuss, I discussed Oracle XE which may be embedded for free. The 18c model of XE was released Saturday during the ACED Briefing. Loads larger than the 11g however with more options. Compression is a crucial one because the storage is proscribed to 12 GB.
19c new Optimizer features
One of the best you can do for the optimizer is providing accurate statistics. Day by day gathering on stale tables is just not sufficient, and dynamic statistics overload parse activity too much. We will have two new features:
High Frequency Automatic Statistics Process: some statistics gathering will be executed during the day, when the system is idle, controlled by the Useful resource Manager.
Real-Time Statistics: some statistics (like high/low value) are maintained throughout DML. This will be nice to keep away from Out-of-Range issues with linear decay from out of date statistics.
We should always not depend on hints, however generally, we need. And we want to ensure that they're used (because no error is raised when not).
Hint Usage Reporting: dbms_xplan reports the hints per operation and alias name, with an indication for those who weren't used (and reason)
Talking about DBMS_XPLAN, the comparison of plans have improved:
Compare SQL Execution Plans: shows directly where the plan diverges
At execution time, when a question by no means ends the worst that may occur is that the impatient run it again. That’s a good idea, but we all do that on Web applications: no answer -> hit F5 a number of times. The query is not going to run sooner and this only increases the contention. Then, better to cancel the statement (useful resource manager can do this) and quarantine the bad execution plan:
Automated Diagnostic and Restore and Quarantine for Runaway Statements
In fact, the big characteristic for the 19c Autonomous Transaction Processing cloud service is Automatic Indexing. This deserves a longer description. The brief concept is that a background job will capture and analyze the workload on short-time period (final quarter-hour) to add higher indexes, removes them, or blacklist them (SQL Patch) for some queries.
And the feature I like the most:
Automated SQL Plan Administration: the capture will be automatic
Enabling the seize for all statements executed times is not easy, even with the new filters launched within the latest release. Right here, the capture relies on AWR. When a question is lengthy, the execution plan can be compared with past AWR snapshots. And if a better plan was used up to now, then this one will be the accepted SQL Plan baseline. This is what we do manually, isn’t it?