Thursday Mar 20, 2014

I won't be able to come to India in March :-(

I assumed that it will become a tough trip to India this time in March with 3 workshops on 3 days in 3 different cities. But it became even tougher before. Unfortunately due to sick leave I won't be able to fly to India next week. I deeply appologize as I was really looking forward to my 2nd visit to India. 

Our next option: Roy will do it. But this is not possible as it takes at least 5 working days to acquire a Business Visa for India. Therefore our team's disaster recovery solution won't work either. 

The local teams will deliver the content on their own. I'm pretty sure that will work out very well.
Hope to see you next time ...


Thursday Mar 13, 2014

Do you know?
Premier Support for Oracle 11.2 will end soon!!!


*** Please read this newer blog post as well ***
*** Please read this newer blog post as well ***


Do you know that Oracle Database 11.2 will run out of PREMIER SUPPORT in less than 11 months?

Well. you may mention now the waived first year of free EXTENDED SUPPORT but this will apply to Oracle Database (and to Oracle Database until Aug 27, 2015) only!!! Now if you think of upgrading to Oracle within the next months start thinking more into the direction of Oracle Database 12c instead. There won't be much difference in efforts and the amount of time you'll spend, regardless if you'd like to Oracle Database or Oracle Database 12c.

Don't waste your time, resources and money - start evaluation Oracle Database 12c today!!! 

Now a bit of clarification as somebody has raised this question:
MOS Note:209768.1 Error Correction Policy describes clearly what you can expect after the Premier Support for Oracle Database 11.2 has ended.

  • Error correction is only available for the: 
  • Current patch set, and 
  • Previous patch set, for the duration of the Grace Period
  •  What does the Grace Period mean?

    Grace Period: up to 1 year for first patch set (minimum 3 months), and up to 2 years for second and subsequent patch sets. 

    • First Patch Set: Customers on all platforms have up to one year from the release of the first patch set on the first platform of a major release to install it.

    • Second and Subsequent Patch Sets: For the second and any subsequent patch set release, customers on all platforms have up to two years from the release of a new patch set to install it. 

    As an example, for release X.Y (base release version X.Y.0.1): 

    • First patch set for (X.Y.0.2) comes out on Linux x86-64 in September 2010. Customers on all platforms have until September 2011 to install it. 

    • Second patch set (X.Y.0.3) comes out in September 2011. Customers would have two years – until September 2013 – to install X.Y.0.3. 

    • Third patch set (X.Y.0.4) comes out in July 2013, customers have until July 2015 to install it.

    During the grace period we will create new bug fixes for the previous patch set and the current patch set.

    Patching end dates for current and most recent patch sets can be found on My Oracle Support in Release Schedule of Current Database Releases (Doc ID 742060.1)


    I appologize but I got used to Support policies for 18 years now and therefore got to learn about something which got removed with Oracle Database The direct combination of "Terminal Patch Set" and "Extended Support" has been removed a while back (and I didn't know it). That means (and the above posting has been corrected already):

    In order to get Extended Support for Oracle Database 11.2 you will have to be on Oracle Database (the terminal patch set) or on Oracle Database In the latter case patching will end by August 27, 2015 - which is described clearly in MOS Note: 742060.1

    Release Patching Ends

    Exceptions* 31-Jan-2018
    HP-UX Itanium: Patching ends Dec 2020. Beginning Feb 1, 2018, Sev 1 fixes only (no PSU or CPU will be produced). 27-Aug-2015 31-Oct-2013
    End date extended beyond normal.

    Thursday Mar 06, 2014

    Free Webcast available now On Demand --- Upgrade and Migrate to Oracle Database 12c and Consolidate with Oracle Multitenant

    Almost 90 minutes about Upgrade, Migrate and Consolidate to Oracle Database 12c with or without Multitenant Option.
    Available now on demand. Just register yourself and watch it whenever it is convenient for you:

    Register to receive the On Demand Link and Watch It!


    Wednesday Mar 05, 2014

    PSU1 and PSU2: Datapatch Issues coverd in MOS Note

    You may have read a posting disrecommending PSU1 and PSU2 for Oracle Multitenant especially in RAC/GI environments earlier this week. Actually following a lot of internal discsussions I will post some advice and clarification later this week.

    Now I have an useful update:
    Datapatch Issues are covered within a separate MOS Note making it easier to keep track and find workarounds for known issues.
    Please see MOS Note:1609718.1 Datapatch Known Issues


    Tuesday Mar 04, 2014

    Upgrade to Grid Infrastructure - but OCR and VOTING on RAW?

    Just received this question from a colleague these days:

    "The current customer environment is on Linux with a 2 node RAC cluster having OCR and Voting Disks on RAW devices. Customer is concerned about the possibility of upgrading to 11gR2 Grid infrastructure first before they could upgrade to 12c Grid infrastructure."

    Now the answer is written down in MOS Note 1572925.1:
    How to Upgrade to 12c Grid Infrastructure if OCR or Voting File is on Raw/Block Devices

    Basically the MOS Note says:
    You will have to relocate your OCR/Voting to a supported device BEFORE you can upgrade to Oracle Grid Infrastructure 12c. No way out. A bit more clarification (thanks to Markus Michalewicz):

    The assumption of the note (which you might want to state) is that the customer has pre-12c GI with OCR / Voting Disk on RAW.

    In this case, Option A is always an option.

    For Option B, however, you need to distinguish. So the note should say: 

    • Option B: Customer is on 11g Rel. 2 still using RAW Devices 
      • Then move the OCR and Voting Disks to ASM
    • Option C: Customer is on pre-11g Rel. 2 and does not want to introduce a CFS (bad idea anyways) or use NFS
      • Then upgrade to 11g Rel. 2 and move the Clusterware files into ASM as mentioned under Option B.

    Unfortunately another example to add to my collection of "What happens if you stay too long on older releases?". In this case it simply increases complexity and drives costs as well. And please no complaints: Oracle Database 10.2 went out of PREMIER SUPPORT in July 2010 - 3.5 years ago!!!


    Monday Mar 03, 2014

    Upgrade Workshops in India in March 2014

    *** Due to sick leave I won't be able to come to India  ***
    *** I deeply appologize - hope to see you soon again *** 


    It will be a tough trip as I will travel on my own with long distances in between the workshops but I'm really looking forward to my second trip to India to run 3 Upgrade, Migrate and Consolidate to Oracle Database 12c workshops in March 2014 in India.

    Register as soon as possible as we have limited seat capacity:

    Hope to see you soon :-)



    Mike Dietrich - Oracle Mike Dietrich
    Master Product Manager - Database Upgrade & Migrations - Oracle

    Based in Germany. Interlink between customers/partners and the Upgrade Development. Running workshops between Arctic and Antartica. Assisting customers in their reference projects onsite and remotely. Connect via:

    - -


    « March 2014 »
    Slides Download Center
    Visitors since 17-OCT-2011
    White Paper and Docs
    Viewlets and Videos
    Workshop Map
    x Oracle related Tech Blogs
    This week on my Rega & Pono
    Upgrade Reference Papers