updated 19th march 2015
When reading this Guide, look out for possible pitfalls when on a Standard Edition database
In previous post “PART I” the subject was:
Enterprise Manager Express – the default tool
I pinpointed things to remember when using this nice tool in a Standard OR a Standard One Edition.
In this post “PART II”, I continue to evaluate the new features, and if there is anything we need to avoid/remember as a Standard Edition Database DBA.
And remember; In the end, it is always good to contact Oracle when having some doubts about options and feature usage in Standard Edition.
12c New Feature (12.1) – any concerns?
Oracle Home User
After reading about this feature, I could only understand it as an”all editions feature”., and couldn’t find anything about it from the license document. It is a nice feature for Windows Systems that bring some more security to the system.
Briefly it is “This Oracle Home User is used to run the Windows services for a Oracle home, and is similar to the oracle user on Oracle Database on Linux”
Check this document for deeper insight.
Application Continuity & Transaction Guard
In my experience, always when the document is telling you about a really awesome feature or option, the warning bell should start making some noise.
As you can see above, the new feature mentions words like “Oracle Active Data Guard”, “Oracle RAC One Node”, and “Oracle Real Application Clusters (=RAC)”.
These words should awaken your suspicions, since we know that only the “RAC” option is available in Standard Edition Database Environment.
Lets check the license document:
As you noticed. These nice features cannot be used in a Standard Edition Database Environment, so if your business needs these features, you need to talk to somebody and start preparing for a database edition upgrade process.
Java and JDBC Support for Application Continuity
Oracle JDBC Support for Transaction Guard
The license document tells us:
Application Continuity for Java is available with Oracle Database, JDBC Thin driver, and the Oracle connection pools: UCP (Universal Connection Pool) and WebLogic Server Active GridLink.
Application Continuity is transparent for Java EE and Java SE applications that use Oracle JDBC, use Oracle connection pools (UCP or WLS Active GridLink), and do not have external actions. For applications with external actions (for example, using autonomous transactions or using UTL_HTTP to issue an SOA call), Application Continuity is transparent only if the application’s correctness is preserved when these external actions are replayed after a failure.
Difficult to say. The License on Transaction Guard & Application Continuity tells us that its only available for EE database, so wouldn’t these java support thing need an Enterprise Edition Database and by so requiring an license? Sorry this is to “dizzy” for me, so maybe it is worth the effort to check with somebody at Oracle License department, before implementing.
Upcoming PART III
In next “PART III” I just continue with the evaluation process. Is there something else in the documentation that a Standard Edition Database Environment DBA must take into considerations or not?
Have a lovely day!
Turku 15th October 2014