Oracle Analytics and AI

EmmanuelMash

Hi Legends

Can you help me with some insight into how you are managing patches and upgrades for OBIEE. Business is more focused on stability (if its not broken don't touch it mindset) but as tech guys we strive to keep up with the versions, latest patches and latest functionality. How are you guys managing this? How can we sell the need to upgrade to business if everything is working perfectly?

Regards

Emmanuel

Joel Acha

Hi @EmmanuelMash, here's my 2 pennies worth - there is no scientific formula to this I'm afraid but most times, it is ends up being a case of "if it aint broke, don't fix it".

patches are usually applied to correct issues with certain functionality. Ideally, it would be best to be using the latest versions but that again comes with its risks as new software tends to throw in a few new bugs here and there and only the adventurous tend to be on the latest release straightaway. The pragmatic approach is to let the early adopters/trendsetters help Oracle iron out all the teething problems and then you can move to the latest versions when these versions have stabilised.

There is an argument that adopting the "if it aint broke, don't fix it" approach could mean people could still be stuck on 10g because it's "stable" whilst those that tend to grab hold of the new features stand the risk of exposing themselves to bugs and instability in newer versions. There's also the small matter of extended support cost for older version of software to take into account.

I guess the best approach would be to be in the middle ground and not adopt latest versions immediately and also not languish behind with older versions. Patches should be applied for security purposes as well as bug fixes which affect your implementation.