There are no “secrets”.
At least, there are no secrets involved in making a database perform properly. Occasionally a useful new piece of information is uncovered – and if it’s worth knowing it will be documented, discussed, and validated in public. (It won’t necessarily be documented on Metalink, OTN, or any other official Oracle site – but that doesn’t make it a secret.)
Whenever I’ve seen people doing presentations about “secrets” they’ve usually split their time between quoting the documentation, stating the obvious, making mistakes, and offering sweeping generalisations that needed careful justification.
I have a simple rule of thumb for presentations – the more glamorous, trendy or exciting the title sounds the less likely it is that the presentation will be useful (but that won’t stop me reading the abstract – just in case).
Oracle Scratchpad 
Do you have any rules of thumbs related to writing abstracts? One of my goals is to start submitting abstracts and presenting one day. It seems a bit difficult for me to come up with an abstract for a topic that would be presented 6 months from now.
Comment by Bradd Piontek — October 13, 2009 @ 2:13 pm BST Oct 13,2009 |
@Jonathan,
true enough however there are many “unpublished bugs” especially in beta and new releases. I found quite a few this week with 12.1.1 EBS. Funny because when I went to apply a non-existent patch from support, Oracle had to supply me with a custom one-off patch to get 12.1.1 working.
cheers,
ben
Comment by Ben Prusinski — October 14, 2009 @ 2:02 am BST Oct 14,2009 |