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 126.96.36.199, 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.
I wrote this post quite a while ago and it stayed as draft since. A few days ago, during Oracle Open World 2017, I had a long chat with Jim Czuprynski and somehow we got to talking about the English language. As you well know by now, I’m not a native English speaker, but Jim is. I still managed to bring up some anecdotes and taught him a thing or two about English in different countries in the world. After that talk I decided to go and publish this post. It’s not technical at all, but I like it and I think you might find some of the things amusing.
When Oracle are adding a new feature to the database, they usually add a parameter to control it. Sometimes, after adding feature and the parameter, they realize that the parameter they chose for controlling the feature is not suitable. It might be confusing, or too general or something else. In these cases they change the parameter in the following version.
I wrote in the past about my frustration with Oracle support. I also hear from customers and colleagues about their frustration with Oracle support, from different reasons. People like to complain when something doesn’t work well, however, I’m writing this post to tell about excellent experience I had with the support lately.
Starting with Oracle 12.1 we can export views as tables. This means that the export will contains a “create table” command and its data, while the original object was actually a view.