Belloni Studio Legale

What’s New In Oracle Database 19c

What’s New In Oracle Database 19c

19c is confirmed as Long Term Support version, with major help no less than to 2022 and extended assist to 2025. Note that in Oracle Cloud, extended assist is without additional fees.
In case you are nonetheless in because you don’t need frequent upgrades, 19c would be the launch to go (however keep it updated with Release Updates). If you want to be sure you do this upgrade as soon as 19c is available on premises, then better to test it as soon as attainable 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 options is an awesome choice from Oracle Development.
test 19c in Oracle Cloud as quickly as available. You may use more options than what you could have on-premises for those tests, such as the Performance Analyzer.

he huge new thing, in my opinion, is that the Java One convention has been merged to Oracle Open World convention, and renamed to Oracle Code One. Interleaving Dev and Ops periods is a really good idea. The Oracle Technology Network (OTN) which grew to become Oracle Developer Community (ODC) is now becoming the Oracle Groundbreakers. What I like right here is that there is no mention of technology or development. We are all in the identical project: improve the user experience with all of the application elements, 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 needed to share my expertise in Dev and Ops groups, on monolithic, shopper/server, 3-tiers,… architectures. Because segregation of responsibility is nice at logical level, but the way to efficiency and scalability should typically undergo colocation in same server, process, engine…

In this speak, I discussed Oracle XE which can be embedded for free. The 18c version of XE was launched Saturday through the ACED Briefing. Lots larger than the 11g however with more options. Compression is a crucial one because the storage is limited to 12 GB.
19c new Optimizer features
The very best you can do for the optimizer is offering accurate statistics. Day by day gathering on stale tables just isn't adequate, and dynamic statistics overload parse activity too much. We will have two new options:
High Frequency Automatic Statistics Activity: some statistics gathering shall be finished during the day, when the system is idle, managed by the Useful resource Manager.
Real-Time Statistics: some statistics (like high/low worth) are maintained throughout DML. This might be great to keep away from Out-of-Range issues with linear decay from obsolete statistics.
We must always not depend on hints, however generally, we need. And we want to make sure that they are used (because no error is raised when not).
Hint Utilization Reporting: dbms_xplan reports the hints per operation and alias name, with an indication for those that weren't used (and reason)
Talking about DBMS_XPLAN, oracle java classes the comparability of plans have improved:
Evaluate SQL Execution Plans: shows directly where the plan diverges
At execution time, when a question by no means ends the worst that may happen is that the impatient run it again. That’s a good suggestion, but we all do this on Web applications: no answer -> hit F5 several times. The query will not run quicker and this only will increase the contention. Then, better to cancel the statement (resource manager can try this) and quarantine the bad execution plan:
Automated Diagnostic and Repair and Quarantine for Runaway Statements
In fact, the big feature for the 19c Autonomous Transaction Processing cloud service is Automatic Indexing. This deserves an extended description. The brief thought is that a background job will capture and analyze the workload on brief-term (last 15 minutes) to add higher indexes, removes them, or blacklist them (SQL Patch) for some queries.
And the characteristic I like probably the most:
Automated SQL Plan Management: the seize shall be computerized
Enabling the seize for all statements executed occasions will not be simple, even with the new filters launched in the latest release. Here, the capture relies on AWR. When a question is lengthy, the execution plan will be compared with past AWR snapshots. And if a greater 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?