OSB 12c ( More Maven Issues and Solutions

Existing Bugs and Issues with Maven and OSB and How to Fix Them

It is a well known fact that Maven in OSB came with glitches that required manual fixes as described in Robert Patrick’s blog posting and in the Oracle support notes Doc ID 2186338.1. However, this article is centered around the latest OSB, its particular Maven issues and how to fix them. Same as version OSB also suffers from various maven glitches, however in a more subtle way.

[Note, that I usually don’t post references to MOS, since not everybody has access to it. Anyway, if you cannot access to Doc ID 2186338.1 don’t worry. It basically describes what Robert writes about in his blog. In addition it recommends actually not to fix it manually, but instead wait for a patch. I actually I agree. Also note that as of OSB this issue is not marked as fixed although the behavior of the newest version is different.]

The current situation with OSB and Maven is “interesting”, to put it mildly:

  • mvn with OSB and the maven push plugin only will not work out of the box. This means the official documentation won’t help you in this case. The good news – despite the fact that mvn with OSB is not working correctly – is that it is rather easy to fix manually (see below, Fix 1: Maven with OSB and the mvn push plugin).
  • Also mvn with OSB and maven.oracle.com will not work (as of Jan 7, 2017). Since the required .pom and .jar files are pulled over from maven.oracle.com and several of them are missing it is obviously not easy to fix it yourself.
  • Here comes the crazy part (well, crazy on an IT scale): if you configure both, i.e. first use the OSB Maven plugin to push from an OSB ORACLE_HOME into the .m2 repository, and then in addition configure the maven.oracle.com repository, then it is done twice. Yet then also both issues cancel each other out.


Here are the fixes, as promised

Fix 1:Maven with OSB and the mvn push plugin

a) easy manual fix, updating two lines in two files:

After usign the push plugin, in .m2 Repository, e.g. D:\Users\frank\.m2\repository\com\oracle\servicebus\sbar-system-common\12.2.1-2-0 change the file sbar-system-common- as follows:



change the version tag to <version>12.2.1-2-0</version>

also for the file sbar-project-common- in the directory
.m2\repository\com\oracle\servicebus\sbar-project-common\12.2.1-2-0 change the version number the same way.

b.) Install patch 22392646

This is the second, alternative option to fix the issue. Install patch 22392646 from My Oracle Support. After a lengthy and tiring discussion I had with support it is now also applicable to OSB – voilà! Depending on your provisioning approach this might be the easier fix, but actually you could just copy over the files (or even run sed on those two files).


Issue 2: Maven with OSB and the maven.oracle.com

There is no known fix at the moment, maven.oracle.com is missing a whole lot of files (again) and also some of those delivered are wrong again. Bug 23698828 describes a very similar issue, yet reports it as fixed for Oracle support knows about it, so let’s hope it will be fixed soon in maven.oracle.com. I will keep you posted, promised.

Update: After the first round with support their “solution” did not work. The issue is still not fixed. If you think about it for a second, how hard can it be to push a patched .m2 repo to maven.oracle.com? Stay tuned 🙂

To conclude

You are lucky if you simply retyped all the instructions available and configured both ways to use Maven with OSB (although I somehow guess you would have not read this article then).

As soon as you follow a clear path and either go for the push plugin on a machine with OSB installed, or maven.oracle.com on a build server without an OSB installation, you will run into issues. It is obvious that Oracle would do good with automatically testing this functionality for future releases. Not being able to browse the maven.oracle.com repo makes it more difficult for customers to debug those issues, so it might be a good idea to use a local proxy / cache.

Let me know your feedback!


WebLogic 12c Zero Downtime Director’s Cut: What you missed …

Everything has limitations. And 2 Minute Tech Tips are 2 minutes only. Strict rules. Anyway, you missed a lot of the good stuff that I recorded in Manly Australia, i.e. the introduction of the 2 minute tech tip about Zero Downtime (ZDT):
Why I was standing on Manly Beach, the wildlife story about sharks that stopped me from having a bath, furthermore some whales (real whales! – not a Docker whale this time) and all the crazy things that happened while we recorded.

So here is the introduction. Enjoy.

DNS Lookup and Ping Times Measurement with Grafana on Oracle Container Cloud Service

Welcome back to a new posting about the Oracle Container Cloud service(OCCS). In my previous OCCS blog posting I went through some details of the brand new OCCS.

In the following webcast I try to measure some key characteristics like DNS lookup and ping times for major industry websites such as cloud.oracle.com, google.com and munzandmore.com. All the measurements are done from probes running in various capitals throughout the world. The important thing to understand is that we not measuring times from the Oracle Cloud to somewhere.

The results actually show that cloud.oracle.com is on a par with google.com and both obviously beat my own domain which is not a big surprise.

Grafana is visualizing the results of these probes. It is running in a Docker container which is running on Oracle Container Cloud Service (OCCS) – the newest addition to the Oracle Cloud.

Enjoy the webcast. Let me know if you have some interesting findings about measurements with Grafana and the worldping plugin or the Oracle Container Cloud service! For sure I will post more about it later.



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 Database on Docker Official Now!

Those of you using Docker will know that we had a Docker file provided by Oracle for creating an Oracle database image since quite a while. However, the Oracle database was so far not certified to run on Docker. This has changed now!

Oracle database on on a Docker container is now officially certified, you can refer to the MOS Doc ID 2216342.1. Don’t worry if you cannot access the link. So far it only states some very basic facts. Also those who know me will understand that I generally dislike postings referring to closed content such as my Oracle support – please regard this as an add-on if you have access to MOS.

How it works

  • There won’t be simple way to just issue a docker run command to get an Oracle DB running since there is no publicly available Docker image for Oracle database due to legal reasons.
  • You have to build your own Docker image from based on a directory that you can check out from github.

Oracle DB on Docker – What is supported

  • A single instance Oracle DB, either Oracle Database – Enterprise Edition – Version or Oracle Database – Standard Edition – Version
  • Docker containers running on Oracle Linux and Red Hat RHEL  x86-64

Oracle DB on Docker – What is not supported

  • Oracle RAC
  • Although not stated in the support notes there is probably more that is not supported, i.e. everything that is not explicitly listed (how about Golden Gate etc.?)