A woman in labour suddenly shouted, “Shouldn’t! Wouldn’t! Couldn’t! Didn’t! Can’t!”
“Don’t worry,” said the doc. “Those are just contractions.”
The weather has been questionable this Summer in the UK – hoping to eek a little bit of sunshine before September…
In the meantime, here’s some of the latest news for this rainy, rainy day.
Blogs of the week
Connor McDonald begins his blog by writing, “I grabbed the following screen shot from a slide deck I’ve been giving about Autonomous Transaction Processing (ATP). It shows the services that are made available to you once you create your database. At first glance, it looks like we have a simple tier, where the lower in the tier you are, the smaller the slice of the database resource “pie” you get.”
He links to these docs.
He concludes by saying, “TL;DR: For standard transactional activities on ATP, make sure it uses the TP or TPURGENT services. If you need faster performance for volume operations, then HIGH and MEDIUM are your friend, but understand the locking and commit implications.”
Debashis Paul says, “Let’s talk something different than Traditional BI today which is about Apache Superset , A modern UI framework based on Flask and React JS.”
This short blog contains a link to these documents.
Mohamed Houri starts off by writing, “There is one Oracle running system launching simultaneously 49 sessions doing the same business for distinct partitions and distinct ranges of employees so that there will never be any collision in this process. However, this application uses bind variables and is, therefore, confronted to the classical performance threat of sharing the same execution plan between a set of bind variables not necessarily dealing with the same volume of data. This application was upgrading from 11gR2 to 12cR1. I was then asked to find a solution so that execution plans will not be shared between those 49 sessions.”
Jonathan Lewis opens with, “In the “Parse Puzzle” I posted a couple of days ago I showed a couple of extracts from an AWR report that showed contradictory results about the time the instance spent in parsing and hard parsing, and also showed an amazing factor of 4 difference between the DB Time and the “SQL ordered by Elapsed Time”. My example was modelling a real world anomaly I had come across, but was engineered to exaggerate the effect to make it easy to see what was going on.”
Connor McDonald writes, “Cloning a pluggable database takes time, and for environments where you’d like to use clones as part of unit testing, or other elements of Agile development, it would be nice to be able to bring a clone into operation in the smallest time possible. One mechanism for that is sparse storage clones aka snapshot copy, but depending on your database version and your storage infrastructure, you might hit some limitations.”
This blog starts with, “ODI developers often create their own ODI procedures that contains any kind of specific logic/technology on it. Since it’s a custom code, we want to be sure that they are efficient, but also easy to read or show errors/warnings when something wrong happens. Let’s see an example of what can be done in ODI regarding this topic.”
Jonathan Lewis asks, “What happens when you execute dbms_stats.gather_system_stats() with the ‘Exadata’ option ?”
Franck Pachot opens by writing, “The indexes created by the 19c Auto Indexing feature have a generated name like: “SYS_AI_gg1ctjpjv92d5”. I don’t like to rely on the names: there’s an AUTO column in DBA_INDEXES to flag the indexes created automatically.
But, one thing is very nice: the name is not random. The same index (i.e on same table and columns) will always have the same name. Even when dropped and re-created. Even when created in a different database. This is very nice to follow them (like quickly searching in my e-mails and find the same issue encountered in another place). Like we do with SQL_ID.”
Richard Foote posts about an upcoming webinar.
This week on Twitter
UKOUG tweeted a link to UKOUG Analytics Modernisation Summit
Jeff Smith posted Version 19.2 is now available
Videos such as:
Commit too soon? Don’t Panic!
Oracle Functions and the Fn Project