Over the years I’ve heard and learned quite a lot about how Oracle does stuff. Some of it was logical, some just details to remember (I have a really lousy memory, but somehow, I actually remember some of the details). Not too long ago I wrote a query and got a parse error, and that lead me to write this post (and a couple more that will follow).
Every day you can learn something new, even after 20 years in the field. For some reason, I was always under the impression that within a single schema, objects must have a unique name. Apparently, this is not the case.
If you don’t know that by now, OTN (Oracle Technology Netowrk) has changed its name to ODC (Oracle Developer Community), so OTN Appreciation Day becomes ODC Appreciation Day.
During OOW17 a customer ran into a wrong result issue in 188.8.131.52, which is very bad. I diagnosed this and found out that it happens because of bloom filter, so we just disabled that and it was solved. But I still opened an SR so Oracle can find and fix this bug.
The LIKE operator is a very useful one. It is used to match strings with partial match while using the underscore (‘_’) as a single character wildcard and the percentage sign (‘%’) as multiple character wildcard.
Remember my post about Oracle 12.2 release date? I’ve heard rumors that Oracle changed the date to March 1st, and it was right!
Oracle 12.2 is available for download for Linux x86-64, and Solaris (both SPARC and x86-64). I don’t know the release dates for other platforms. This is the download page: http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
I’m downloading it as I write, and hopefully will have time to play with it a little bit soon. I wrote so much about new features that I have to try some of them at least. Stay tuned!