Now that we’re well into 2017, let’s sit back and ask the question: “What was the best news of 2016 in the Oracle ecosystem?”
- The 12.2 beta ? (no, that was announced in October 2015 :))
- The fact that we now officially know that each PDB will have their own local UNDO ? (no, this was easy to guess)
- The fact that we will be able to flashback a PDB ? (nope. This, too, was easy to guess)
I’ll give you a clue. The best news was something that sneakily appeared between April and October 2016 in your patch maintenance logs :
[root@myclusterdb02 OPatch]# ./opatchauto apply /patches/OCT2016_bundle_patch/24436624/Database/220.127.116.11.0/18.104.22.168.161018DBBP/24448103 -oh /u01/app/oracle/product/22.214.171.124/dbhome_1 -ocmrf /u01/app/oracle/product/126.96.36.199/dbhome_1/OPatch/ocm/bin/ocm.rsp System initialization log file is /u01/app/oracle/product/188.8.131.52/dbhome_1/cfgtoollogs/opatchautodb/systemconfig2016-12-11_05-23-36PM.log. Session log file is /u01/app/oracle/product/184.108.40.206/dbhome_1/cfgtoollogs/opatchauto/opatchauto2016-12-11_05-24-09PM.log WARNING: the option -ocmrf is deprecated and no longer needed. OPatch no longer checks for OCM configuration. It will be removed in a future release.
The interesting part is in that 4th line :
WARNING: the option -ocmrf is deprecated and no longer needed. OPatch no longer checks for OCM configuration. It will be removed in a future release.
This is awesome! We no longer need this annoying ocm.rsp file !
When I discovered this back in November 2016, I searched for an official feature announcement but found nothing (it looks like an opatch 13c new feature backported in 11g and 12c). This ocm.rsp file was still needed when I applied the April 2016 PSU, but from which opatch version was it implemented?
First, I looked at the 2016 dev comments in opatch 220.127.116.11.15 and 18.104.22.168.7 (which were the last version when I was applying this Exadata October 2016 PSU) and I sadly discovered that no specific comments were talking about this new feature (even if it would obviously deserve some):
# opatch 04/08/16 Update CAS_VERSION to 22.214.171.124.3 # opatch 04/11/16 Consolidate all 4 opatch scripts # opatch 06/07/16 Calling auto_patch.pl using the perl from Oracle Home Location # opatch 06/30/16 bug 23721730 - default memory was too high for 32 bit so removed and disabled opatch_env.sh script call
After a quick look at the code, I found the amazing piece of code that would ease our lives in the future (the function is named ocmOptionDetect()):
# Option 'ocmrf' is deprecated in OPatch 13.3 - Detect and give warning message if [ "$OCMRF_OPTION" = "1" ] && [ "$VERSION_13_X" = "1" ]; then echo "WARNING: the option \"-ocmrf\" is deprecated and no longer needed. OPatch no longer checks for OCM configuration. It will be removed in a future release."
I then performed a few greps in different opatch versions that I had and I found that this feature has been implemented in:
- 126.96.36.199.13 or 188.8.131.52.14 for 11g (I was unable to find any of these versions so I couldn’t check)
- Between versions 184.108.40.206.10 and 220.127.116.11.7 for 12c (again, I was unable to find any of these versions so I couldn’t check)
If you come across any of the opatch versions specified above, please “grep -i ocmrf opatch” it and let me know so I can find when this feature has been implemented.
You can now upgrade all your opatches to become ocm.rsp-free and this (for me) was definitely the best new of 2016!
Apparently there is a way to achieve such requirement with Groovy expression, this can be executed from entity level validation - adf.error.addAttribute('Salary'). In addAttribute you need to provide attribute name which will be assigned with the error. Complete expression for entity validator:
Result displayed on UI - validation error message is assigned to the field, which was changed:
Download sample application - GroovyADFApp_v2.zip.
When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong.
The only way of discovering the limits of the possible is to venture a little way past them into the impossible.
Any sufficiently advanced technology is indistinguishable from magic.
The third one has various alternative explanations such as:
Any technology, no matter how primitive, is magic to those who don't understand it ,and
Any sufficiently ancient recovered wisdom or artifact is also indistinguishable from magic
Any sufficiently advanced technology is indistinguishable from a rigged demo, and
Software tests that inexplicably pass or fail are indistinguishable from voodoo
By this time, we are all bought into the value that a Cloud infrastructure brings. So, if you are in Information Technology (IT), you are looking to best leverage a single, centralized Cloud platform to meet your needs. As you think through your Cloud investments, consider an iterative approach where you start off looking for the biggest bang for your money and an initiative that earns you instant results (and credibility) with the various lines of businesses.
I recently wrote a feature for the CIO Review publication in which I explored how a Cloud content hub would create value for both IT and the different lines of businesses. In it, I also shared an example of one of our customers, Omni Financiera to discuss how they are choosing to get immediate value from their Cloud investments. Take a read and see if this could be your next step in the Cloud. As always, I would welcome an open dialog and look forward to hearing from you on your thoughts.
Hope you enjoy the feature.
Oracle's Lifetime Support policy has three phases: Premier Support, Extended Support, and Sustaining Support. For details about coverage during each phase, see:
You can purchase a support plan for your licensed products to obtain Premier Support. There is an additional fee for Extended Support.
Extended Support for Database 11.2 runs to December 31, 2020. The Extended Support fee for Oracle Database 11gR2 11.2 has been waived to December 31, 2018. See:
- Release Schedule of Current Database Releases (Doc ID 742060.1)
- 18.104.22.168 Database Certified with E-Business Suite 11i, 12.0, 12.1
- Oracle Database 22.214.171.124 Certified with E-Business Suite 12.2
- Reminder: Error Correction Support Ended for Database 126.96.36.199
- Sponsored: 64% off Code Black Drone with HD Camera
Our #1 Best-Selling Drone--Meet the Dark Night of the Sky!