Having a Proactive Patch Plan is the way to Go!

Posted by user793553 on Oracle Blogs See other posts from Oracle Blogs or by user793553
Published on Mon, 25 Jun 2012 16:22:58 +0000 Indexed on 2012/06/25 21:21 UTC
Read the original article Hit count: 267

Filed under:

BUILDING A SUCCESSFUL PATCHING STRATEGY

Make Patching Easy!

Having a Patching Strategy for your E-Business Suite system is a great way to manage your system downtime, identify the proper resources needed to perform the necessary task and familiarizing yourself with the Patching Tools in EBS.

Having a Proactive Patch Plan is the way to Go!

Proactive Patching is a preventive measure allowing you to have a complete patching strategy when applying patches periodically. Oracle provides several tools to help you get started to set the foundation for a solid and proactive patching strategy in Note 313.1 - "Patching & Maintenance Advisor: E-Business Suite 11i and R12". It details all the steps and tooling available for the patching strategy along with the benefits. Among other things it covers the following:

  • How to plan ahead for system downtime
  • Patching Tools in E-Business Suite (Autopatch, OUI, OPatch)
  • How to Identify Patches (RUPs, EBS Family Packs, Critical Patch Updates, etc)
  • How to properly test your patching plan and move to Production

Make sure you visit the New E-Business Patching Community!

We encourage you to access the "E-Business Patching Community" prior to applying an E-Business Suite patch. Doing so will allow you to explore perspectives shared by industry peers, get real-world experiences with the patch, and benefit from known solutions and lessons learned. Additionally, Oracle Support engineers monitor discussion topics to help provide guidance and solutions for your E-Business Suite patching needs.

This is a valuable opportunity to "Get Proactive" with the patching and maintenance of your E-Business Suite environment. Start now, and find fast, proactive resolutions before you begin.

Related Articles:

© Oracle Blogs or respective owner

Related posts about /Oracle/Communication