The 2016 Leap Second in the Cloud: It’s spread out for Oracle DBs on RDS

The 27th leap second will be officially applied December 31, 2016 at 23:59:60 UTC. For Oracle DB instances on RDS the following applies:

  • RDS will spread out the leap second equally in the 24h surrounding the timestamp above.
  • After this period RDS time will be in sync with  Cordinated Universal Time.
  • This applies for Oracle DB instances with versions,, and They will follow AWS Adjusted Time that is applied to RDS.

Oracle Container Cloud Service (OCCS)

Docker has undergone a dramatic evolution in only the last couple of years. From virtually unknown in 2014, it still seemed to be a exotic, niche open source solution when WebLogic was certified on Docker in early 2015.

Nowadays this is different. End of 2016 it has become very common to explore new software by just running an official Docker image from Docker hub. CI / CD pipelines are often built on Docker for repeatability. Docker is one of the key building blocks for runtime environments of those wandering down the microservices alley.

However, you need much more than just a starting a Docker container or two. You need infrastructure, networking, private and public registries, containers have to be scaled and restarted if they fail. All this needs to be installed, configured, and operated. On premises this is not an easy task.

There is a huge difference between spinning up a Docker container and operating a Kubernetes cluster for enterprise critical applications 24/7 in production. So the the obvious choice is often the cloud with a PaaS based container cloud service.

Oracle Container Cloud Service (OCCS) is the newest addition in the Oracle Cloud portfolio. It was built to solve the issues discussed in this posting. The following webcast helps you to understand the key components of OCCS. If you follow it, you can have a worldwide monitoring of your own domain running in some 5 minutes on a hosted Docker container.

Those who know my WebLogic Distinctive Recipes book understand that I am not a big fan of those click here, screenshot, then click there, screenshot articles – therefore I created the webcast for you with a working example that is not already in OCCS. Make sure to read the OCCS documentation anyway.


Let me know if you like it!


OSB / SOA Suite 12c Domain Types

OSB / SOA Suite 12c Domain Types

screen-shot-2016-11-30-at-16-22-10Let me explain you some news about the domain types in 12c, since some of my colleagues were fiddling around with this. Due to the new quickstart installer for SOA Suite and OSB 12c there are more domain types available now for SOA Suite and OSB12c that you need to understand. The following options describe those types with added comments of when the make sense.




  1. The integrated domain that gets generated by JDeveloper if you run a project. Sometimes it is called default domain. This domain is bound to JDeveloper. Whenever you quit JDev, the domain shuts down. The downside is that this domain always supports OSB and SOA Suite, so a bit of waste of resources if you are only after OSB . This is the easiest solution for your first steps because no manual domain creation is required and JDev does it all for you.
  2. A standalone domain. This is the new and interesting option, because a standalone domain uses the Java DB and does not require you to run the RCU utility. Still a standalone domain is running independent from JDeveloper 12c, so you could you use this type of domain for development with OSB web console.You create the domain by setting the QS_TEMPLATES environment variable and running, then create an application server connection with JDev, use the standalone server option in the application server connection wizzard, and point it to the standalone domain.
    You will be able to use “Deploy” from JDeveloper, but unfortunately not “Run as”.
    There are more benefits to a standalone domain not mentioned in the official documentation: Whereas the integrated domain includes everything needed for SOA suite you can restrict a standalone domain to Service Bus only and therefore reduce the number of internal deployments from 304 to 278 which will save you startup time.
  3. A compact domain can be used with quickstart. Also compact domains are targeted for development. This domain will be compatible with add-ons such at MFT, OES, etc. Note that you have to specify a special parameter for this option to be visible in the configuration wizzard.
    Since you can use it with an compatible Oracle DB, the necessary schemas have to be created with the RCU utility. Note: A compact domain is a developer domain consisting of a single admin server and no managed servers.
    The opposite of a compact domain is called extended domain where resources are deployed on a cluster of managed servers. Use extended domain for environments such as test, integration, load test, prod. These environments are distributed and clustered typically due to HA requirements.


It is important to understand the various domain types and to choose the correct domain type for your requirements. You can strip down a standalone domain to be OSB only, then make sure to select Integrated Servers if you want to deploy directly from JDev to it.

It’s a wrap: Oracle and Cloudera Big Data Training – On Premise and Cloud

Wow – We have done it! Weeks of preparation, reading, trying out tools, and hacking went into the preparation of this training course. Even during the OTN APAC tour I took some days off and worked from my Bangkok home office to prepare for the DOAG trainings day.

At the end it was totally worth it. I had 21 top notch DBAs and developers on the attendee list, also some 10 students attended. DOAG is running a good student program. For helping out a little bit students are allowed to attend sessions and the DOAG training day. Quite often I get a lot of them. 2 years ago I was running a full day multi-cloud training and every single student including their professor decided to attend my session – although they had the choice amongst 6 different trainings. Anyway, nice to be popular with the young people. Next time I will come in sneakers and wear that Cloudera T-Shirt. Also it became a bit of a challenge for Oracle to attract students. So I am glad to help 🙂

Fabulous news was that Edelweiss took over the Oracle part, so I was lucky to talk about what I love – the open source and Cloudera part.


Edelweiss did her session via Skype. I was a bit sceptical and expecting technical problems because of the network latency but it went swimmingly. The conference room had good speakers, so I could play some music in the break and Edelweiss almost seemed to be present in the room but kind of invisible.



Well now you know it. This is what is cool.



A really great surprise was that everyone enjoyed the idea of working with VirtualBox and accepted labs that I prepared. Most people took them home to further play with the Big Data Lite instance.

At the end we covered a whole lot of content in a long day:

From Open Source / Cloudera Stack 

From Oracle Big Data Products

Oracle Big Data ApplianceOBIEEOracle Data Integrator (ODI)Oracle Big Data Discovery