understanding patching for your oracle fusion cloud services marc lamarche senior director global...

Understanding Patching for Your Oracle Fusion Cloud Services

Marc LamarcheSenior DirectorGlobal HCM Customer SupportSep 28, 2014

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. |

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted 3

Safe Harbor StatementThe following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.


Agenda

Fusion Cloud Basics

Mandatory and Optional Patches

Patching Recommendations

Common Patching Scenarios

Q&A

1

2

3

4

5


Oracle Cloud Hosting and Delivery Policies

Fully managed environments—high availability, flexibility, backup, and monitoring to enable secure and scalable applications

General maintenance releases (Upgrades R7 to R8), selected functionality releases, and documentation updates

Assistance with Service Requests 24 hours per

day, 7 days a week

Access to My Oracle Support Portal(24 x7), with the ability to log

Service Requests online

Applications updates, security fixes, and critical

patch updates

Non-technical customer service during normal

business hours

cloud.oracle.com - navigate to Resources -> Support ->Oracle Cloud Policies ->Policies


SaaS Basics

• We publish policies that cover our service lifecycle processes– We provision, maintain, and upgrade for you

• We publish a schedule for maintaining the software– Patches to fix problems– Upgrades to improve software capability or operational infrastructure

• As a customer you agree to work within our maintenance schedule • You plan your project milestones to accommodate our published

maintenance schedule for Production and Non-Production instances

We manage the software for you as a service


Provisioned Environments

• 2 environments are provisioned as standard– Test (aka Stage) to be used for initial development and then for testing patches and upgrades– Production (aka Prod)– Dev1-n : Customers can acquire instances for parallel development and testing

• Production to Test (P2T) content migration requires that both instances are at exactly the same release and patch level

• Customers need their own instance management strategy for the lifetime of their service– Understand the mandated standard monthly maintenance schedule for both Test and Prod– Understand the options and process to get critical patches as an exception to the monthly schedule– Understand the conditions attached to exception patching

Test, Prod and Optional Dev


Mandatory and Optional Patches

• Mandatory Patches– Monthly Patch Bundle (MPB)– Monthly Vertex Patch (Tax and address files)– Quarterly Database and Hardware Maintenance patches

• Optional Patches– Weekly Patch Bundle (WPB)– Monthly Translation Patches– One-Off Critical Showstopper Patches



Monthly Patch Bundle (MPB)

• Our standard monthly process for maintaining all customer environments• Includes Applications, Middleware and BI patches• The MPB is cumulative and includes all eligible patches available since the

last monthly patch bundle• Applied automatically to all customer instances on the published schedule

– No exceptions (cannot be skipped)– Non Production (Test/Dev) : 1st Friday of every month– Production (Prod) : 3rd Friday of every month

• A full automated regression test suite is executed against the MPB• Outage notifications sent to customers

Mandatory Patches - Applications PB & Middleware P4FA


Vertex, DB and Hardware Maintenance Patches

• Monthly Vertex Patches– Vertex is an Oracle business partner that provides monthly tax updates and

address validation files that must be patched into all environments– Non Production instances are patched on the 18th of each month– Production instances are patched on the 25th of each month– No outage is required to apply these patches (applied in the background)

• Quarterly Database and Hardware Maintenance Patches– Example: Database updates, security patches, EXA patches, etc…– Applied as-needed (typically quarterly in conjunction with MPB)– Outage notifications sent to customers– Next planned outage Dec 19th

Mandatory Patches


Weekly Patch Bundle (WPB)

• Not for live production instances • Includes critical patches blocking your ability to go live

– The WPB is an aggregate of approved one-off patches release after the last MPB – We run a full automated regression test suite on the WPB

• Applied weekly at the start of every weekend (for current month)– Before requesting the WPB you must be aware of your P2T schedule– P2Ts can only be done in a month where you do not request a WPB on your Test

instance or your instances will be out of Sync

• Customers who request the WPB must agree:– To take subsequent WPBs until the end of the current month (aka the “Train”)– To take the WPB on all environments if in pre-production status (keep in sync)

Optional Patches


Translation and One-Off Critical Showstopper Patches

• Translation Patches (R8)– Applied on request via SR

• Non-Production instances - 2nd Friday of the month• Production Instances - 4th Friday of the month

– In R9 translation patches will be installed automatically on the standard monthly patching cadence based on the language(s) installed in your instances

• One-Off Critical Showstopper Patches– Senior management approval required– Limited to critical live production down issues only– Example: payroll issue, cannot pay employees

Optional Patches


Patching Recommendations for Implementations

• Prior to Go-Live we recommend all customers to be on concurrent patching– Concurrent patching needs to be requested via an SR– Both Test and Prod are patched with the MPB on the first weekend of the month– When WPB is requested, patching is done automatically on Test and Prod

• Plan your go-lives 1 to 2 weeks after the MPB is applied to Production– Latest fixes applied before Go-Live– Sync up Prod and Test (P2T)

• Perform P2T after the Monthly Patch Bundle is applied to Production– Production to Test (P2T) content migration requires same patch level in Test & Prod– Schedule and plan for the P2T well in advance



TEST

PROD

October 2014 November 2014

Patching Scenarios #1 (Live Customers)

MPB 8.10

MPB 8.10

MPB 8.11

MPB 8.11

P2T Window

Live

Week1

MS T W T F S

Week2

MS T W T F S

Week3

MS T W T F S

Week4

MS T W T F S

Week5

MS T W T F S

Week1

MS T W T F S

Week2

MS T W T F S

Week3

MS T W T F S

Week4

MS T W T F S

Dec

Week1

MS T W T F S

MPB 8.12

P2T Window

P2T


TEST

PROD

October 2014 November 2014

Patching Scenarios #2 (Pre Go-Live – Concurrent Patching)

MPB 8.10

MPB 8.10

MPB 8.11

MPB 8.11

Week1

MS T W T F S

Week2

MS T W T F S

Week3

MS T W T F S

Week4

MS T W T F S

Week5

MS T W T F S

Week1

MS T W T F S

Week2

MS T W T F S

Week3

MS T W T F S

Week4

MS T W T F S

Dec

Week1

MS T W T F S

MPB 8.12

P2T Window

WPB x.1

WPB x.1

WPB x.2

WPB x.2

WPB x.3

WPB x.3

Implementing Live

P2T

Go-Live

WPB x.4

WPB x.4

WPB x.5

WPB x.5


R9 Upgrade

• Pre-Upgrade Surveys went out last week• You have until October 6th (HCM/ERP) to reply and voice your preference

– 3 preferences for each environment– Best efforts to accommodate one of the top 3 preferences

• We will begin the broad rollout of upgrades from R8 to R9 in December• The R9 upgrade cannot be skipped• Language patches are done automatically

December Rollout


References

• Oracle ERP Cloud Patching Process (Doc ID 1630770.1)

• Oracle Fusion HCM Cloud Patching Process (Doc ID 1619092.1)

• The Oracle Sales Cloud Service: Patching Process (Doc ID 1900855.1)

• Oracle Fusion Applications Cloud Concurrent Patching Option (Doc ID 1646394.1)

• Guide to the Functional Readme for Fusion HCM Patch Bundles (Doc ID 1554838.1)

• Oracle Fusion Applications R9 Upgrade Process for Oracle HCM Cloud Service (Doc ID 1928157.1)

• Cloud Service Requests and Fulfillment for Oracle HCM Cloud Service (Doc ID 1534683.1)

• Managing Fusion HCM Cloud Service Environments (Doc ID 1537461.1)

Important MOS Docs


Drinks. Food. Fun.My Oracle Support Monday Mix

Tonight!Monday, September 29 6:00 to 8:00 p.m.ThirstyBear Brewing Company(only ½ block from Moscone Center)

Oracle Confidential – Internal/Restricted/Highly Restricted 18

Join us for a relaxing Happy Hour after a busy day at Oracle OpenWorld!• Take a break and unwind with your peers

• Get to know the Oracle support engineers you depend on

• Meet My Oracle Support executives and developers

• Enjoy drinks and hors d’oevres

• Admission is free with your Oracle OpenWorld badge Event details at:www.oracle.com/goto/mondaymix


Oracle Support Stars Bar & Mini Briefing Center

ASK THE EXPERTSMoscone West Exhibition Hall

understanding patching for your oracle fusion cloud services marc lamarche senior director global...

Documents

oracle andor

service slide

oracle cloud hosting

sole discretion of oracle

oracle support portal24

optional dev slide

software patches

service lifecycle