It’s been about a year since Oracle decided to change their database version schema, from version with a couple of releases (e.g. 12.1 is 12cR1 and 12.2 is 12cR2) to a single annual version (e.g. 18c and 19c). Now, when 18c is stable and 19c is here on the cloud and Exadata and almost here on-premises, I thought it’s a good time to revisit this topic.
As every year since 2016, we’re having the ODC Appreciation Day around October. If you don’t know what “ODC Appreciation Day” is, it is Tim Hall’s initiative to simply say thank you. It started as “OTN (Oracle Technology Network) appreciation day” and then changed to “ODC (Oracle Developer Community) Appreciation Day” when Oracle rebranded OTN. It is meant to acknowledge that we, as a community, appreciate what the people at Oracle community are doing for us by writing these posts and add the hashtag #ThanksODC.
Oracle Open World and Oracle Code One conferences are around the corner. In about a month, tons of people from around the world will be in San Francisco and my twitter will explode, as every year.
I debated quite a lot before writing this post. When I wrote the post about interviewing a DBA, in the “technical questions I do ask” part I just gave a general explanation of what I ask, but didn’t reveal the real questions. Now, more than 3 years later, I decided to give one of the questions as a challenge here.
I just came back from RMOUG Training Days conference. It was my first time in Colorado (and obviously my first RMOUG training day) and it was really great (I wrote about it in another post).
During my second session (From 4 Minutes to 8 Seconds – about a real SQL tuning case I had quite a few years ago), I mentioned that one thing that I usually do when I see a query and need to analyze it, is to take a piece of paper and draw the tables and relations between them. When I later look at the execution plan and try to understand what Oracle does, it helps a lot if I know the structure of the tables. There is a big difference between queries built like a “star” (a single table in the middle, while the others are joined to it) or a “line” (each table is joined to the next one), or any other structure.
This is a short note just to say I’m happy to have my first GitHub project.
A few months ago I wrote a blog post and a python script (on gist) to analyze the listener log file. A few weeks later I got a message from Adric Norris who asked me to create a proper GitHub project, as with gist, people cannot improve and add code.