Tuesday, August 24, 2010

Oracle Acquisitions Survey: The Results Are In

I received another email from Stephen Jannise of ERP Software Advice this morning to let me know that he had published the results from the Oracle Mergers and Acquisitions Survey that I had previously blogged about.

There were a total of 1,250 responses to the survey and the results are interesting.

The two front runners fall into the category of "fairly straightforward ideas" with 38% of the voters choosing a company within this category.

It also seems I was not alone in opting for a "bold move into the network layer", 19% of voters also chose within this category, although Juniper Networks came in slightly behind Research in Motion.

Full results from the survery and Stephen's analysis can be found here in his updated article.

Are the results as you expected?

Wednesday, August 04, 2010

Note to Newbies: Know when it's time to call Oracle Support

This thread on the OTN forums caught my eye today.

Whilst I love the forums and think they are a great place to go for help and advice, there are times when they are not the best medium for support and this was one of them.

Forum questions are answered by volunteers, people who have day jobs to do themselves, that are happy to share their experience and help out others with queries. That’s why you will often see people getting flamed for posting subject titles with ‘URGENT’ or ‘PLEASE HELP NOW’.

In this thread there were a lot of people wiling to help, but with the OP seemingly not fully understanding some of the responses and even admitting in one post that they were ‘in a panic’ the confusion led to the problem being made worse.

If you’ve screwed up production and are in a panic, there’s a good chance that you may not have explained the issue clearly. Responses can only be given based on the information that you have provided and if that is not accurate, or you misread some of the instructions, then you could very quickly end up in an even bigger mess.

It’s too easy to say ‘don’t panic’.
I’ll admit that I’ve experienced that awful feeling in the pit of your stomach when you realise you have done something you shouldn’t have done, especially in production. I’m sure many others have too. But panic is generally what makes things worse (this especially applies to my diving as well as DBA work!).

Instead, take a deep breath and put in that call to Oracle Support.

The last post in the thread pretty much sums up the best response:

My first advice would have been:
Shutdown both databases and take a cold backup of everything if you have the time & space for that.
Contact Oracle Support!
Wait patiently for their advice and do not simply everything anybody tells you over the internet !

Unfortunately, the ‘Too late now for that’ also rings true and I just hope that the OP was able to get this resolved.

Tuesday, August 03, 2010

What will Oracle buy next?

Stephen Jannise of ERP Software Advice has written an interesting article around likely targets for Oracle's next acquisition.

The article is well written and well thought out, being based on research into the past 5 years of Oracle acquisitions alongside a study into the current market.

There's also a diagram to show all of the companies that Oracle has acquired since the PeopleSoft acquisition in 2004. There's over 40 of them and it's quite something to see them all laid out in the diagram.

Based on the research and an analysis of Oracle's M&A strategy, the study has presented a list of 13 potential targets and Stephen is asking readers to vote on who they think is the most likely candidate for a future acquisition.

I had a bit of a think about it and, as anyone who knows me will testify, my thought patterns can be a bit odd - which has made me think that the next acquisition is likely to be something in the networking arena - so I have voted for Juniper.

But I'm not an Analyst so that's just my opinion.

Go and take a look at the article and have fun with the voting. It'll be interesting to see the results to find out what other people think.