By Mike Dietrich-Oracle on Jul 03, 2015
Just fyi in case you had bookmarked this blog post or found a link to it:
There will be an update on Oracle Database 12c SE soon.
Thanks for your patience and sorry for the inconvenience!
On March 31, 2015 SAP has been certified to run on Oracle Database 188.8.131.52:
As of June 30, 2015, Oracle Database In-Memory is supported and certified for SAP environments for all SAP products based on SAP NetWeaver 7.x. on Unix/Linux, Windows and Oracle Engineered Systems platforms running Oracle Database 12c - in single instance and Oracle Oracle Real Application Clusters deployments.
Oracle Database 12c is the database of choice for SAP customers based on In-Memory Technology which is fully supported for SAP BW and SAP OLTP applications.
For requirements, restrictions, and implementation details see the documents below.
Press Release [added July 24, 2015]:
Oracle Database 12c and Oracle Database In-Memory Certified and Supported by SAP for use with SAP Solutions
PS: Fidel, thanks for the correct links - highly appreciated!!!
I have blogged many times about the End of Premier Support for Oracle Database 11.2 and the different stages and regulations for Extended Support for this release. But still I'm getting inquiries almost every day, internally and externally.
Let me first point out that I'm not a rep of Oracle Support. I'm just a Product Manager with some Oracle Support background. So you'll always have to consult our officially available documents and sources as regulations may change after I published this blog post. I'm just trying to summarize what I know at the moment to help you avoid some of the usual misunderstandings.
Fact. Premier Support for Oracle 11.2 has ended on Jan 31, 2015. Period. Regardless of the patch level you may be on. No further discussion here please. Just for your notes: this has happened a while ago in case you've missed the date:
Quoting from MOS Note:1067455.1:
Support for Patch Set 184.108.40.206
Under the new policy for overlapping Patch Set support, 220.127.116.11 will continue to be supported through 27 August 2015. The last Critical Patch Updates (Security Patch Update and Patch Set Update) for 18.104.22.168 will be released in July 2015. After then you will need to be running on 22.214.171.124 or a supported 12.1 Patch Set to get Critical Patch Updates.
I have learned in the past weeks that some information in the official Support documents (Lifetime Support Policy). such as the Brochure for Technology Products (including of course the database but also a clear description about the different levels of support) is not clear and obvious to everybody. This docs don't differentiate between the several patch releases.
Therefore you will have to consult MOS Note:742060.1 for further clarification and specific dates per patch level.
The new version of Oracle's Cloud Control 12c Release 5 is available for download as of today. Some of the new features include Hybrid Cloud Computing but also the support for RMAN incremental rolling forward backups (cross platform, cross Endianness) to decrease downtime for Transportable Tablespaces and Full Transportable Export/Import migrations.
Find it here on OTN:
Enterprise Manager Base Platform
(Full Installers for OMS, Agent, Repository, Management Plug-ins)
for Linux x86 (32-bit)
for Linux x86-64 (64-bit)
for Windows x86-64 (64-bit)
for Solaris Operating System (SPARC)
for Solaris Operating System (x86-64)
for IBM AIX on POWER Systems (64-bit)
for HP-UX Itanium (64-bit)
SAP certified Oracle Database 126.96.36.199 as of March 31, 2015!
Yes, it's true. Our colleagues in the Oracle/SAP/CompetenceCenter in Walldorf worked really hard to complete the certification for SAP with Oracle Database 188.8.131.52 But finally it happened. Actually it was announced long time before as planned. And it happened right in time.
Please find the official documents here:
SAP Service Marketplace ==> Products ==> Installation & Upgrade Guides ==> Database Upgrades (login required) ==> Oracle
And here's the link to the official announcement:
Great job by a excellent Oracle team in Walldorf - and please no excuses anymore from anybody saying that you can't certify your application on Oracle Database 184.108.40.206. If SAP can do it, everybody can do it
If you are looking for more information and useful documents please see this discussion here - scroll down a bit (thanks to Upgrade Expert Andreas Becker from the Oracle-SAP-CC in Walldorf):
See also the ROADMAP for Oracle/SAP regarding future developments, feature support, In-Memory etc:
I'm expressing my sincere condolences as one of the 5 founders of SAP, Klaus Tschira, died on March 31, 2015 way too early at the age of 74 years. May he rest in piece!
Oracle In-Memory is such a great feature - but often the challenge you'll face is the tricky question:
Which of your tables and/or partitions should you mark for In-Memory column store availability?
And the answer is now easier to find as the new In-.Memory Advisor is available via download from MyOracle Support:
The Advisor produces a report identifying the objects that should be placed In-Memory for maximum benefit, along with a SQL*PLUS script which implements those recommendations. It can be run on Oracle Database 220.127.116.11 and above. And of course the recommendations can be implemented on Oracle Database 18.104.22.168. (and newer).
Important to know: The In-Memory Advisor is licensed as part of
the Database Tuning Pack.
Further information can be found at: OTN
In case you have obtained a pre-release version of the Advisor, please discard it and replace it with the production version
Beginning with Oracle Database 22.214.171.124 a non-CDB architecture is deprecated.
What does this mean?
Deprecation first of all does not mean "desupported". It means in this case that you of course can have still stand-alone Oracle databases as you know the architecture from previous releases. But you can also have a single-tenant deployment (a CDB with one PDB - no Multitenant license required) or multitenant databases (a CDB with up to 252 PDBs - Multitenant Option license required).
But in a future Oracle release single-tenant and multitenant databases only may be allowed. Right now there's no information available when this might happen. --
Which features are not supported at the moment?
From the Upgrade Guide:
By deprecate, we mean that the feature is no longer being enhanced but is still supported for the full life of the 12.1 release. By desupported, we mean that Oracle will no longer fix bugs related to that feature and may remove the code altogether. Where indicated, a deprecated feature may be desupported in a future major release
Every release offers some surprises - even to myself
Right now Roy and I are in the final steps to refresh our big slide deck to the new layout, but more important, to have Oracle 126.96.36.199 information included as well (were necessary). So I did my usual "compare parameters" query between releases - getting unusual surprises this time.
This is the list of new parameters introduced with the patch set Oracle Database 188.8.131.52. Where applicable I have added the link to the doc.
But as you may recognize not all of them are explained in the doc
DBFIPS_140enables Transparent Data Encryption (TDE) and
DBMS_CRYPTOPL/SQL package program units to run in a mode compliant to the Federal Information Processing Standard (subsequently known as "FIPS mode"
COMMON_USER_PREFIXis set to an empty string, Oracle will not enforce any restrictions on the names of common or local users, roles, and profiles.
trueto enable RDBMS services used by Oracle GoldenGate
INMEMORY_CLAUSE_DEFAULTparameter is unset or set to an empty string (the default), only tables and materialized views explicitly specified as
INMEMORYwill be populated into the IM column store. Setting the value of the
NO INMEMORYhas the same effect as setting it to the default value.
INMEMORYare populated into the In-Memory Column Store (IM column store) or not. The default value is
DEFAULT. When this value is in effect, the IM column store is populated only with tables and materialized views specified as
OFFis specified, then even if the IM column store is configured on this instance, no tables or materialized are populated in memory.
PGA_AGGREGATE_TARGETvalue divided by 512M, whichever is less.
INMEMORY_MAX_POPULATE_SERVERSinitialization parameter value
falsecauses the optimizer to ignore the in-memory property of tables during the optimization of SQL statements. This behavior can also be achieved by setting the
OPTIMIZER_FEATURES_ENABLEinitialization parameter to values lower than 184.108.40.206
PS: Forgot to mention this one as a parameter which had been disappeared in Oracle 220.127.116.11:
Oh, how often have I heard this phrase:
"We'll wait for the second release!"
And sometimes it makes me really anxious and angry at the same time when I hear that.
Anxious because it means that somebody has no strategy for the database upgrades/migrations and is just postponing necessary tasks to sometime in the future. Easy deal but not very clever.
Angry because this is a way of thinking from the 90s/00s when Oracle had this "10.1", then later "10.2" strategy in database releases. But we are in 2014 now. And things have changed. Changed a lot in fact.
I'm probably not the only person who would love to see if we'd remove this "first" and "second" release tags. This has become obsolete with Oracle 11.1. We were telling customers officially that this is the brand new fantastic Oracle Database 11g release. But in fact it was - from the coding perspective - more or less a very stable 10g. In my workshops I did call it Oracle 10.3 with a marketing sticker on it. And as far as I can see the customer's I've had helped with going live on Oracle Database 18.104.22.168 were quite happy. Some really large shops still work with this release today with hundreds of databases in production.
But honestly most of the changes got introduced with Oracle Database 11.2. And not for a small number of customers this meant waiting for the first patch set (which since then has become a full release). Plenty of people went live with Oracle Database 22.214.171.124. But a lot of the remarkable changes got introduced not in Oracle 11.1 but in Oracle 11.2. Just remember things such as the move from Clusterware to Grid Infrastructure. But also minor things such as DEFERRED_SEGMENT_CREATION and plenty of optimizer news.
Now with Oracle Database 12c and the first patch set (full release) 126.96.36.199 I have heard this again - and I see it on the mailing list as well once a week:
"When will Oracle 12.2 be available?"
Well, that's the misconception. It's true, Oracle Database 188.8.131.52 has new features and extensions. But it has also many fixes over the already very stable Oracle 184.108.40.206. Why should anybody wait for Oracle 12.2 now? Because it's supposed to be THE SECOND release? Forget this - this is thinking from the old days.
We are in year 2014 now.
And then spend a minute to look closer to the Support Policy.
That means if you plan to stay on Oracle 220.127.116.11/4 for a longer period you'll either have to calculate 20% extra of your support fee for the 2nd year of Extended Support. Or you prefer to "hope".
I can't tell you when Oracle 12.2 will be available - and I don't care. Usually people wait for the first patch set anyways which gets releases based on experience from the past 3 databases releases roughly a year and a bit after the initial release. Just do the math and you'll see where you end up with this strategy.
My recommendations are:
Oracle Database 18.104.22.168 is available for download now. It is the most comprehensive patch set we've ever built. Look up the list of inclusions - and it includes the new marquee feature OracleDatabase In-Memory.
Three things important to mention:
And it contains a bunch of new things and improvements:
(22.214.171.124.0) - Enterprise Edition
|Linux x86-64||File 1, File 2 (2.5 GB) See All|
|Oracle Solaris (SPARC systems, 64-bit)||File 1, File 2 (2.6 GB) See All|
| Oracle Solaris (x86 systems, 64-bit)
Microsoft Windows x64 (64-bit)
|File 1, File 2 (2.3 GB) See All
File 1, File 2 (2.5 GB) See All
Time to upgrade!!!
PS: Kudos to Morohashi-san for alerting me about the link to the internal MOS - exchanged the link address!
PPS: Updated entry on Sept 30 with links for MS Windows
It took a while ... but finally Oracle Database 12c is available for:Oracle Database 12c Release 1
|Microsoft Windows x64 (64-bit)||File 1, File 2 (2.5 GB) See All|
|Linux x86-64||File 1, File 2 (2.3 GB) See All|
|Oracle Solaris (SPARC systems, 64-bit)||File 1, File 2 (2.6 GB) See All|
|Oracle Solaris (x86 systems, 64-bit)||File 1, File 2 (2.3 GB) See All|
|HP-UX Itanium||File 1, File 2 (3.1 GB) See All|
|AIX (PPC64)||File 1, File 2 (2.7 GB) See All|
|zLinux64||File 1, File 2 (2.3 GB) See All|
Sometimes it is by far easier to watch a few short videos instead of reading an entire book
So enjoy watching Roy talking about Upgrades and Migrations to Oracle Database 12c in short videos covering also the new Upgrade and Migration features in Oracle Database 12c.
Chapter 1 - Upgrading is Universal
Chapter 2 - Minimizing Risk and Downtime
Chapter 3 - Leveraging Consolidation to ease Migration
Chapter 4 -Why Upgrade?
Chapter 5 - Automating the Upgrade Process
Good things come to those who wait ... and yes, Oracle Database 12c (Oracle 126.96.36.199) is available for download from OTN/eDelivery for MS Windows as well since last night
PS: Just on the side, there won't be versions for 32bit OS' available, neither on Windows, nor on Linux.
Good things come to those who wait ... finally ... Oracle Database 12c (Oracle 188.8.131.52) is available for download from the Oracle Software Cloud (formerly know as eDelivery) and OTN (Oracle Tech Network) for Linux 64bit (Solaris will follow within the next few hours):
And yes, it will be supported on Oracle Exadata and SuperCluster as well
And with the release of Oracle Database 12c we are offering you also our
with (sorry, we've did it again!) over 500 slides covering:
And of course, the slide deck will see some updates in the near future
Master Product Manager - Database Upgrade & Migrations - Oracle Corp
Based near Munich/Germany and spending plenty of time in airplanes to run either upgrade workshops or work onsite or remotely with reference customers. Acting as interlink between customers/partners and the Upgrade Development.
Follow me on TWITTER
Contact me via LinkedIn or XING