The new versions of the WebLogic 12cR2 and ADF could not have come at a worse time for me. My top priority is learning about the 12cR1 version of the database. Second, is getting to grips with Cloud Control 12cR3. Third on the list is getting up to speed with the changes in WebLogic 12cR2 and ADF. Unfortunately, my personal priorities don’t quite match my work priorities, so WebLogic 12cR2 has moved up the list for a while. As a result, I did some installations last night.
I’ll have to play with this for a few days to get my head round it as I may be doing a test installation at work early next week.
A word of warning. I am a self-confessed WebLogic newbie. If you ask me questions about it I will be redirecting you to people who actually know what they are talking about…
Oracle will be releasing Oracle Database 12cR1 at some point this year. Many companies will avoid this release, opting to wait for 12cR2, their reasoning being it will be more stable and, as a terminal release, will have a longer support life-cycle. Since 12cR2 is what most businesses care about, what can we do to make it as good as it can possibly be? Here are a few thoughts…
- For a start, you’ve got to use 12cR1 in your organization to understand what it does well and what is a bit crappy about it. If you don’t figure this out during 12cR1, chances are your wishlist will not be ticked off in 12cR2. I’m not saying launch straight into production, but don’t just place your head in the sand either.
- Report every bug you find, even those that already have resolutions in MOS. Lots of people, including myself, complain about how buggy the Oracle database has become as the functionality has expanded. Workload in any organization has to be prioritized. Chances are, the things that people shout about the most are the things that Oracle will get done. If we all make our feelings known by logging every bug that affects us and explain why/how it is impacting on us, it can only help the cause.
- Report bugs in the documentation. The Oracle docs have improved a lot over the years, but there is always room for improvements. In the old days you had to report faults in the documentation as SRs. Now, you just need to add comments directly in the documentation, which is a lot quicker and easier. When you see a problem, report it. If you think something is missing, ask for it. Once again, if enough people shout about something, it may affect the priority.
- File enhancement requests. You often come across things that almost solve your problem, but not quite. If that’s the case, file an enhancement request on MOS. If enough people ask for stuff it will probably get added. Even better if you have an example of how cool that feature is in another DB engine.
- Get involved in beta programs. This is not always as easy as it sounds. I would love to have been involved in the 12cR1 beta program, but I was not considered worthy. If your company can get involved in beta programs it’s a good way to help improve and shape the product. The more issues logged during the beta testing period, the more likely the final product will live up to your expectations.
- Make sure Oracle salespeople know and understand your priorities. At the end of the day, Oracle exist to make money. In most commercial companies the sales department have a disproportionate influence on the direction of the products. At every opportunity, make it know what *your* priorities are. I love the new and geeky stuff, but to be honest, most of the work I see people doing requires little more than what was available in Oracle 7. If bug fixes and stability are more important to you than new functionality, make it known.
I have no knowledge of the internal workings of Oracle as a company, so I can’t guarantee these suggestions will have any impact, but I think of this the same way as I do about voting in elections. If you don’t voice your opinions, you don’t really have any right to complain. If Oracle know exactly what their customers want and don’t deliver, they only have themselves to blame if everything goes wrong. If we as customers don’t make our opinions known, we shouldn’t be surprised if Oracle keep chasing the next buzzword, rather than doing what matters to us.
Oracle Cloud Control 12cR2 is installed and merrily monitoring one of the test 11gR2 databases running on HP-UX. I’ll probably leave it like that until I come back from Oracle OpenWorld. I don’t want to change the entire administration and monitoring infrastructure just as I leave for a couple of weeks.
As I’m re-familiarizing myself with the 12c way of doing things, I’ve been wondering if this really is a full “Release 2” product, or just 12cR1 with Bundle Patch 2. Not surprisingly, one of my readers asked the same question, pointing out the version 126.96.36.199 does not look consistent with a “Release 2” product, which would typically be 188.8.131.52.
I take Oracle version numbers with a pinch of salt. I’m currently using WebLogic version 10.3.5, which is 11g WebLogic. At least WebLogic 12c has been versioned appropriately.
So why the 12cR2 branding, when 12cR1 of the database hasn’t been released yet? My guess is this is a marketing move for one very specific reason. One of the big marketing messages around Cloud Control was its ability manage clouds and allow you to charge customers based on their resource usage. While speaking recently to a representative of a large oracle customer/partner, I found out this functionality plain didn’t work, at least not with their selection of (latest version) Oracle products.
Assuming Cloud Control 12cR2 is now actually capable of delivering on this promise, that represents quite a big change that’s probably worthy of a re-brand, even if the version number doesn’t warrant it.
Of course, this is all speculation on my part. I’m not using it for managing clouds or charging customers. I’m just a regular DBA who likes to watch the performance page every few minutes while doing my administration in SQL*Plus.
Update: See Hans’ comment about the version number. He’s quite correct that this version falls in line with a new release in the GC/CC universe.
Enterprise Manager Cloud Control 12c Release 2 was released a couple of days ago for all the major platforms. That in itself is not news any more, but the fact we are going to trial it at work as a replacement for our 11g Grid Control installation is.
It’s in my low priority task list, so I’m not sure I’ll get it all sorted before OOW12, but it is something to look forward too. I know it’s tragic, but I’m quite excited.