2010 Oracle Corporation 1

Transcription

1 2010 Oracle Corporation 1

2 Session #S Patching Enterprise-Wide Databases: Automation Techniques & Real World Insights Hari Srinivasan, Pr. Product Manager, Oracle Hari Srinivasan, Pr. Product Manager, Oracle Tim Misner, Sr. Director Product Development, Oracle Deepa Nambiar, Sr. DBA, Johns Hopkins Applied Physics Lab

3 Safe Harbor Statement The 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 a purchasing decision. The development, release, and timing of any features or functionality described for Oracle s products remains at the sole discretion of Oracle Oracle Corporation 3

4 Oracle Enterprise Manager Session # S Patching Enterprise-Wide Databases: Automation Techniques & Real World Insights You had almost given up on Patching thousands of databases. And you are not alone to be bugged by the cumbersome, manual processes involved in database patching. Till Enterprise Manager 11g arrived with its rich MOS integration. In this session, you will discover how customers have realized high ROI from Enterprise Manager's patch management solution Oracle Corporation 4

5 Business-Driven IT Management 2010 Oracle Corporation 5

6 Program Agenda Common Patch Management Challenges Patch Management Options Contrast between various manual and automated options Enterprise Manager 11g driven Patch Management Features and Benefits Best Practices Customer Case Study Johns Hopkins Laboratory 2010 Oracle Corporation 6

7 Top 4 Patching Challenges Maintaining scripts Identifying affected systems Identifying right patches Identifying and resolving conflicts 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Huge overhead in maintaining Home grown scripts Identifying vulnerable targets among possible thousands Identifying right patches to be applied Resolving patch conflicts and filing merge requests if needed * Patching Survey conducted by Oracle across customers, Mar Oracle Corporation 7

8 Patching Habits Frequency & Complexity Frequency Number of patches applied per downtime More than 4 times Four times (quarterly) Multiple Thrice Twice One Once 0% 10% 20% 30% 40% 0% 20% 40% 60% 80% Most customers patch multiple times a year Quarterly patching most common Most customers apply multiple l patches per downtime Some large customers apply patches in a single downtime session * Patching Survey conducted by Oracle across customers, Mar Oracle Corporation 8

9 Typical Database Patch Management Process Complex, manual, error-prone po e 1 Identify patches 2 Download patches to local system 3 Identify targets 4 Apply on test system 5 Create/update (optional) scripts Quarterly Security Patch from Oracle Service Requests Patch from other sources Help Desk Create an incident Oracle Support Services Oracle Technology Network My Oracle Support 7 File SR, monitor, replace with merge patch Yes No 6 Conflicts detected? Based on heterogeneous environments (RAC, single instance, DR) 8 Apply across test systems Request for downtime / retrieve ti approval Request for downtime / retrieve approval Update / close RFC Manual processes by one or many DBAs 9 Test patch in QA environment 10 Apply patch in production 11 Verify patch application FTP patches 2010 Oracle Corporation 9

10 Typical Database Patch Management Process and time-consuming too (experience e of large customer w/1000+ databases) abases) 1 Identify patches 2 Download patches to local system 3 hrs. 3 Identify targets 4 Apply on Test system 5 Create/update (optional) scripts Quarterly Security Patch from Oracle Service Requests Patch from other sources Help Desk 3 hrs. 8 hrs. 3 hrs. Create an incident Oracle Support Services Oracle Technology Network My Oracle Support 7 File SR, monitor, replace with merge patch Yes 1 day to 2 weeks No 6 Conflicts detected? 2 days to 1 week Based on heterogeneous environments (RAC, single instance, DR) Request for downtime / retrieve ti approval Request for downtime / retrieve approval Update / close RFC Manual processes by one or many DBAs 8 Apply across Test systems 1 week 9 Test patch in QA environment 2 weeks 10 Apply patch in Production 10 weeks 11 Verify patch application FTP patches Oracle Corporation 10 Total Rollout Effort (Per Quarter): 25 weeks!!! 5 hrs.

11 Current Patching Tools opatch Custom scripts Enterprise Manager Command Line tool installed with the base database product Scope of execution limited to an Oracle Home Supports interactive and silent modes Limited capability to handle pre and post patching steps Custom scripts developed around opatch, SQLPlus, etc. Usually limited to a single server Significant maintenance overhead to meet new version and configuration needs Out of box procedures to handle end-to-end patch deployment Can span multiple servers Can handle pre- and post- patching steps Oracle-provided updates to handle new version and configuration needs 2010 Oracle Corporation 11

12 Comparison of Patching Options OPATCH CUSTOM SCRIPT ENTERPRISE MANAGER Automatic advisory No No Yes Patch conflict check Deployment time only Deployment time only Yes (Up-front) Community information review No No Yes Automated download No No Yes Multiple instances support per HOME No Yes Yes Pre and post Shutdown and No Yes Yes startup Multiple databases on No No Yes different machines Multiple patches in single run Yes Yes Yes Post patching dictionary changes Rolling Clusterware and RAC patching Guaranteed support for new database versions No Yes Yes Limited Limited Yes Yes No Yes 2010 Oracle Corporation 12

13 Enterprise Manager Patch Management Process Reliable, Scalable, Automated 1 Identify patches 2 Consolidate list of patches 3 Create patch Plan 4 Validate Patch Plan Patch advisory Quarterly Security Patch from Oracle Service Requests Patch search Siebel Help Desk BMC Remedy HP Service Center Create an incident 6 Request for downtime / retrieve ti approval Request for downtime / retrieve approval Place merge patch request; monitor SR for a merge patch Yes No 5 Conflicts detected? 7 Create Policies to test patch application 8 Test patch in QA environment 9 Apply patch in production Compare Oracle Homes for compliance validation Update / close RFC 10 Verify patch application (re-run UDP) 2010 Oracle Corporation 13 *MOS@EM - My Oracle Support Integrated within EM

14 Enterprise Manager Patch Management End-to-End Change Lifecycle Detect and verify patching success Detect drift from existing gold images and rebuild them for future software rollouts Close change request Patch Verification Patch Advise Patch Rollout Roll out the patches within stipulated downtime Advise/recommend patches based on configuration Let users research the patch by providing readme and community information Patch Planning Plan downtime File change request Identify patch conflicts, impact and dependencies Plan rollback strategy Test patch in test environment Test application in test environment 2010 Oracle Corporation 14

15 Database Patch Management Patch Advise Generate advisories based on Critical patch updates & Other Oracle Recommendations Incident (SR) based one-off recommendations Community information (from tens of thousands of customers) Advisories are ranked based on criticality File exception violations with Remedy, HP Service Center, Siebel CRM Patch Verification Patch Advise Patch Rollout Patch Planning 2010 Oracle Corporation 15

16 Database Patch Management Patch ac Advise 2010 Oracle Corporation 16

17 What APL Is Saying Enterprise Manager enabled systems administrators to use personalized dashboards and power views to quickly identify issues related to their areas of responsibility and take timely action Johns Hopkins University, Applied Physics Laboratory 2010 Oracle Corporation 17

18 Database Patch Management Patch ac Planning Bundle multiple changes for rollout under a single downtime Upfront conflict and pre-requisite analysis Integrate with Oracle Support to request and get Merge patches Understand environments and Analyze patchability before the actual deployment Design change workflow using Plans Deploy the changes with Best Practices Deployment Procedures Activate Policies for ongoing tracking of the patches Bi-directional integration with Remedy, HP Service Center, Siebel Patch Verification Patch Advise Patch Rollout Patch Planning 2010 Oracle Corporation 18

19 Database Patch Management Patch ac Planning 2010 Oracle Corporation 19

20 The availability of Oracle Real Application Testing for Oracle Database 10g and Oracle9i Database, is key to accelerating our migration of mission critical applications to Oracle Database 11g in an efficient manner. Starwood Hotels & Resorts Worldwide, Inc. What Starwood Is Saying 2010 Oracle Corporation 20

21 Database Patch Management Patch ac Rollout ou Patch multiple installations with multiple patches in a single window Support one-offs, patchsets, CPUs and PSUs (incl. overlay patches) Support patching of RAC, Clusterware, ASM, Database Zero-downtime Rolling patching of RAC clusters Support patching Databases on Physical Standby Support impersonation methods for deployment in multi-admin environments Support Software Library for Release Mgmt Flexible error handling, retry and rollback Patch Verification Patch Advise Patch Rollout Patch Planning 2010 Oracle Corporation 21

22 Database Patch Management Patch ac Rollout ou 2010 Oracle Corporation 22

23 What Bayer Is Saying We manage thousands of databases and application servers with Enterprise Manager, and we have been able to reduce the patch application time from one hour down to one minute per database. Enterprise Manager allows us to automate this process, which translates into huge savings in time and money. Bayer 2010 Oracle Corporation 23

24 Database Patch Management Patch ac Verification Post-change validation and verification Deep out-of-box checks for Databases Create User Defined Policies for ongoing compliance tracking Out-of-box patch reports Check compliance to the Patch policy Patch Verification Patch Advise Patch Rollout Patch Planning 2010 Oracle Corporation 24

25 Database Patch Management Patch ac Verification 2010 Oracle Corporation 25

26 What CERN Is Saying Enterprise Manager helps us efficiently address compliance and regulatory requirements. Specifically, Configuration Management Pack provides proactive change detection, policies and reporting capabilities that simplify and automate processes, enabling us to further reduce costs and risk and improve overall efficiencies. CERN 2010 Oracle Corporation 26

27 Best Practice Recommendations 2010 Oracle Corporation 27

28 Commonly Asked Questions How do I ensure that I find and fix all possible errors before, not during, my downtime window? Can I reduce the downtime involved in the patching process? Can I make the patching operation more secure and auditable? Can the procedure notify me during execution so I can let it run completely unattended ( lights out )? Can I use patching features in my security restricted environment? 2010 Oracle Corporation 28

29 Make Patch Rollouts Reliable Best Practice ce Recommendation e o 1 How do I ensure that I found and fix all possible errors before, not during, my downtime window? Is my environment patchable? Do the targets meet the pre-requisites? Can I reduce the downtime involved in the patching process? Can I make the patching operation more secure and auditable? Can the procedure notify me during execution so I can let it run completely unattended ( lights out )? Can I use patching features in my security-restricted environment? 2010 Oracle Corporation 29

30 Check for Patchability Using Reports Best Practice ce Recommendation e o 1 Here s How Run Patchability Report from Deployments >> Reports >> EM Target Patchability Report 2010 Oracle Corporation 30

31 Check for Patchability Using Pre-Flight Checks Best Practice ce Recommendation e o 1 Here s How Run the Deployment Procedure in Analyze Mode at the end of the procedure interview 2010 Oracle Corporation 31

32 Make Patch Rollouts Reliable Best Practice ce Recommendation e o 1 How do I ensure that I found and fix all possible errors before, not during, my downtime window? Is my environment patchable? EM Target Patchability Report: Identify patchable targets under the environment monitored and mitigate issues to improve patching coverage Do the targets meet the pre-requisites? Pre-flight checks with Analyze Mode: Run comprehensive checks on Patches and Targets checking for applicability of the patch and target sanity to ensure success during patch deployment 2010 Oracle Corporation 32

33 Stage Patches Pre-Downtime Best Practice ce Recommendation e o 2 How do I ensure that I found and fix all possible errors before, not during, my downtime window? Can I reduce the downtime involved in the patching process? Can I pre-stage the patch before patching process? Can I use a shared location to stage the patches and apply patches from there? Can I make the patching operation more secure and auditable? Can the procedure notify me during execution so I can let it run completely unattended d ( lights out )? Can I use patching features in my security-restricted environment? 2010 Oracle Corporation 33

34 Pre-Stage Patches to Shared Location Best Practice ce Recommendation e o 2 Here s How Pick a procedure >> Specify the location to stage the patch >> Execute the Procedure in Analyze mode Patch gets staged in the location specified during Analysis. Disable the Stage step in the Procedure >> Select the previously specified patch stage location Patch is selected from the pre-staged location rather than being restaged Oracle Corporation 34

35 Save Downtime and Bandwidth with Pre-Staging Best Practice ce Recommendation e o 2 How do I ensure that I found and fix all possible errors before, not during, my downtime window? Can I reduce the downtime involved in the patching process? Can I pre-stage the patch before patching process? Can I use a shared location to stage the patches and apply patches from there? Save Downtime and Bandwidth: Stage the patch once to a shared staging location. Patch the local hub of systems from the pre-staged location 2010 Oracle Corporation 35

36 Make Patch Rollouts Secure and Audited Best Practice ce Recommendation e o 3 Can I avoid identifying errors that are based on my environments during the deployment process? Can I reduce the downtime involved in the patching process? Can I make the patching operation more secure and auditable? Can I avoid using shared OS accounts while patching? Can I lock access to Oracle account? Can the procedure notify me during execution so I can let it run completely unattended d ( lights out )? Can I use patching features in my security-restricted environment? 2010 Oracle Corporation 36

37 Use Impersonated Accounts for Rollouts Best Practice ce Recommendation e o 3 Here s How Pick a procedure >> Do a Create Like >> >> Specify the User Impersonation settings in Privilege Delegation Settings 2010 Oracle Corporation 37

38 Make Patch Rollouts Secure and Auditable Best Practice ce Recommendation e o 3 Can I avoid identifying errors that are based on my environments during the deployment process? Can I reduce the downtime involved in the patching process? Can I make the patching operation more secure and auditable? Can I lock access to the Oracle account? User Impersonation: Lock Oracle accounts and setup authentication through SUDO or Power Broker. Update EM Deployment Procedures to execute through SUDO or Power broker 2010 Oracle Corporation 38

39 Light Outs Tracking Through Notifications Best Practice ce Recommendation e o 4 Can I avoid identifying errors that are based on my environments during the deployment process? Can I reduce the downtime involved in the patching process? Can I make the patching operation more secure and auditable? Can the procedure notify me during execution so I can let it run completely unattended ( lights out )? Can I track procedure executions and step level executions without being on the system? Can I use patching features in my security-restricted environment? 2010 Oracle Corporation 39

40 Set Up EM Notifications to Patch in Lights Out Mode Best Practice ce Recommendation e o 4 Here s How Pick a procedure >> Do a Create Like >> Enable Notification along with required status 2010 Oracle Corporation 40

41 Light Outs Tracking Through Notifications Best Practice ce Recommendation e o 4 Can I avoid identifying errors that are based on my environments during the deployment process? Can I reduce the downtime involved in the patching process? Can I make the patching operation more secure and auditable? Can the procedure notify me during execution so I can let it run completely unattended ( lights out )? Can I track procedure executions and step level executions without being on the system? Remote Monitoring: Enable Notifications for different status of procedures to receive /pager alerts for procedure execution. This provides user with handle to monitor the execution even when it runs unattended 2010 Oracle Corporation 41

42 Offline Datacenters No Connectivity to MOS Best Practice ce Recommendation e o 5 Can I avoid identifying errors that are based on my environments during the deployment process? Can I reduce the downtime involved in the patching process? Can I make the patching operation more secure and auditable? Can the procedure notify me during execution so I can let it run completely unattended ( lights out )? Can I use patching features in my security-restricted environment? How do I get to use patching my OMS doesn t have connectivity to My Oracle Support? 2010 Oracle Corporation 42

43 Off-Line Data Centers Feature Limitations Best Practice ce Recommendation e o 5 1. Limited availability of Patch Management Features associated with My Oracle Support 2. Patch Search, Patch Activity and Patch Plans are not available in this mode 3. Patch Recommendations and Patch Rollout through Deployment Procedures can be exercised still 2010 Oracle Corporation 43

44 Off-Line Data Centers Patch Recommendations Best Practice ce Recommendation e o 5 Here s How 1. Setup >> Patching Setup >> Online and Offline Settings >> Set Connection mode to Offline 2. Download Patch recommendations and related XMLs from MOS separately 3. Upload Metadata XMLs and compute patch recommendations by running Refresh from My Oracle Support job 2010 Oracle Corporation 44

45 Off-Line Data Centers Patch Deployment Best Practice ce Recommendation e o 5 Here s How 1. Download patches separately from MOS to local system 2. Deployments >> View/Upload Patches >> Upload Mass Upload Patches to Software Library 3. Select from Software Library during Deployment 2010 Oracle Corporation 45

46 Off-Line Datacenters No Connectivity to MOS Best Practice ce Recommendation e o 5 Can I avoid identifying errors that are based on my environments during the deployment process? Can I reduce the downtime involved in the patching process? Can I make the patching operation more secure and auditable? Can the procedure notify me during execution so I can let it run completely unattended ( lights out )? Can I use patching features in my security-restricted restricted environment? How do I get to use patching if my OMS doesn t have connectivity it to My Oracle Support? Offline Mode Support: Download recommendation XMLs and patches separately. Select from Software Library during deployment Oracle Corporation 46

47 Best Practice Recommendations Make Automation o Efficient ce Make patch rollouts reliable with Patchability report and pre-flight checks Save downtime and bandwidth by ypre-staging g Set up impersonated accounts for secure rollouts Set up notifications for Lights Out execution For offline datacenters, te fetch recommendations e o and mass upload patches to Software Library for rollouts 2010 Oracle Corporation 47

48 Andreas Stephan Senior DBA Consultant Bayer Business Services We manage thousands of Patch Management databases and application servers Case Study: Bayer with Enterprise Manager, and we have been able to reduce the time 2,000 databases, for database upgrades from 4 hours 5 full time DBAs, down to 1 hour, as well as reduce 1 hour per patch, patch application time from 1 hour 4 times a year down to 1 minute per database. Enterprise Manager Grid Control Before After Enterprise Enterprise allows us to automate t this process, Manager Manager which translates into huge savings in time and money. 8,000 person hours $160, person hours $2, Oracle Corporation 48

49 Reduce Operations Costs with Automation Reduction in costs of managing IT Increase staff productivity Increased agility to business needs Reduction on capital spending Forrester Total Economic Impact of Configuration Management and Provisioning Packs 130% ROI over 3 years 14 months payback period 2010 Oracle Corporation 49

50 Session: #S Patching Enterprise-Wide Databases: Automation Techniques & Real World Insights Johns Hopkins University Applied Physics Laboratory - Deepa Nambiar

51 Agenda 01 Infrastructure 02 Challenges 03 Solution: OEM Patch Automation 04 OEM 11g Patch Automation Features 05 ROI and Results 51

52 The Johns Hopkins University- Applied Physics Laboratory Celebrating 65 + Years of Service to the Nation Not-for-profit research and development laboratory founded in Division of Johns Hopkins University Staffing: 4,000 employees (69% scientist and engineers) Annual revenue ~ 780M Who do we work for- We do projects for Department of Defense, DARPA, Department of Treasury, NASA, NSA etc. 52

53 Infrastructure ERPs and multiple custom developed applications ERP (e.g. PeopleSoft, ebusiness Suite) Other custom applications Time Keeping, Resource Management, Data Warehouse etc databases across multiple data centers Oracle Enterprise Manager(OEM) Grid Control (GC) as central monitoring and administration tool. Production version Currently evaluating new features of OEM11g on a test system. Plan to upgrade soon. Diagnostics, Tuning, Configuration Management and Provisioning o Packs among others Oracle database versions RAC and single instance databases, , & single instance databases O.S. OS - Solaris 10 and Oracle Enterprise Linux Rel5 53

54 Agenda Infrastructure Challenges 03 Solution: OEM Patch Automation 04 OEM 11g Patch Automation Features 05 ROI and Results 54

55 JHU-APL Challenges APL security guidelines demand implementation of security fixes within short time frame Oracle Corporation releases PSU/CPUs quarterly Manual patching time consuming and error prone 150+ databases, 4 times a year, approx 0.5hours/db, assuming 51% multi tasking. ~ 300 hours patching per year Effectively utilize limited DBA resources (150+ Databases / 3 DBA s) Being on course with PSU/CPU patch cycles. Making g sure all required targets are patched at the same level. Spent a lot of time on repetitive tasks like patching and did not leave much time for DBA s to work on strategic activities. 55

56 Agenda 01 Infrastructure 02 Challenges 03 Solutions- OEM Patch Automation 04 OEM 11g Patch Automation Features 05 ROI and Results 56

57 Solutions for Patching Grid Control Patching deployment procedures allow Comprehensive Automation- Full scope of patching procedure including blackouts, OPatch update and SQL apply and utlrp on databases. Detects databases already shutdown and in blackout. One time Patch Download from My Oracle Support to software library directly, made it available across dev, test uat and production environments. Schedule Mass deployment: No more logging into every server to apply the patch. Error Logging, Ability to Customize and Status Notifications through s Quick deployment. 57

58 Patch Cycle At JHU-APL Pre Rollout Checks Critical Patch Advisory Identifies System Vulnerabilities Applies on Pre prod System In Analyze Mode Check patch conflicts Apply on Pre prod Systems Rollout Selects the Patches from Software Library (Pre-Maintenance) Verifies Production System in Analyze Mode (During Maintenance) Mass deployment in Production System Generates Reports 58

59 Patch Management Life Cycle- PreRollout Before Patch application, Verify Target Patchability Target Patchability Report, lists databases that cannot be patched using OEMGC. 11g Rel2 database cannot be patched with OEMGC Good practice to validate that t all targets t and communicating with OMS and can be patched using the tool. 59

60 Patch Management Life Cycle- PreRollout 1 Identify the Critical Patch Advisory /system vulnerabilities quickly and easily using OEMGC. Patch Advisories under Compliance, provides complete list of database homes and security ypatches that need to be applied supports CPU and PSU patch application, including overlay patches. EM provides CPU advisories. 11g provides PSU advisories. 60

61 Patch Management Life Cycle Pre Rollout 2 3 Identify vulnerable systems easily 61

62 Patch Management Life Cycle Pre Rollout Analyze mode ROCKS! - If patch conflicts are detected contact oracle support for a replacement patch. 62

63 Patch Management Life Cycle Pre Rollout Conflict Detection 63

64 Patch Management Life Cycle Pre Rollout Real world example Deployment procedure run history available, if need to refer to old conflicts arises. It is recommend that deployment procedure runs be meaningfully named 64

65 Patch Management Life Cycle- PreRollout Analyze mode conducts a dry run of the patching process without actually applying the patch. Upfront patch conflict and pre-requisite requisite analysis If a conflict is detected, may need to file a merge patch request. Good practice for DBA s to run the deployment procedure in analyze mode against all the targets, as they patch Development test and production databases. 65

66 Patch Management Life Cycle Patch Rollout 1 Rollout :Select Patch Oracle Database Deployment Procedure 2 Patch now available in the software library 66

67 Patch Management Life Cycle -Patch Rollout 3 Rollout :Select Targets and proceed to Deploy 67

68 Patch Management Life Cycle- Patch Rollout Add database targets applicable to the patch across multiple servers. Patch without having to physically log into all the servers. Can use a single interface. 68

69 Patch Management Life Cycle Patch Rollout Patch application can be prescheduled, and just check status. Ability to Patch multiple installations with multiple patches in a single window. We take advantage of this. Not a Black Box - Lists steps that the deployment procedure goes through. -Logs available for each step of the patching process. Applied Interim Patches Report to verify overall patch effort. 69

70 Agenda 01 Infrastructure 02 Challenges 03 Solutions OEM Patch Automation 04 OEM 11g- Patch Automation Features 05 ROI and Results 70

71 Patch Management Life Cycle- In OEMGC 11g 1 View Overall Patch Recommendations OEM11g has integrated MOS into the EM product. MOS is now a tab within EM. New process of identifying Security vulnerabilities. Security recommendations, under Patches & Updates tab lists security patches that are applicable to a particular database. 71

72 Patch Management Life Cycle- In OEMGC 11g 2 Select specific Patch Recommendations Patch recommendations list the patch #, the DB version host name. The new interface Provides ready access to the readme and access to community reviews. Earlier had to separately log into forums. 72

73 Patch Management Life Cycle -OEMGC 11g 3. Add the patch to Patch Plan Concept of Patch plan : Logical grouping of patches and targets. You can directly add the patches to a new or existing patch plan. Current design enables you to identify vulnerabilities and check for conflicts and file replacement patch requests all on the same page! 73

74 Patch Management Life Cycle -OEMGC 11g 4. Validate for Conflicts 5. Request Replacement patches Upfront validation for conflict amongst the patches selected and with that of the patches in the oracle home. No manual merge patch service requests required. Screenshot shows output from the replacement patch request. Once replacement patches are obtained it is ready for replacement and status t changes to Conflict free. 74

75 Patch Management Life Cycle -OEMGC 11g Replacement Patch Tracking Once a request is placed, the status can be tracked from the main Patches & Updates page. 75

76 Patch Management age e Life Cycle OEMGC 11g 6. Schedule Deployment 76 Run Procedure is where the new functionality integrates with the old functionality Deployment Procedures Clicking Run Procedure on the Patch Plan will present you with the set of Deployment Procedure screens you have already seen in EM

77 Patch Management Life Cycle OEMGC 11g 7. Apply Patches through Deployment Procedures The Patches from the plan are auto selected Note: At the current patch level, all the selected targets are not auto populated and you get the above message Tip: The message lists the targets that were part of the patch plan Proceed with the procedure as in EM 77

78 Agenda 01 Infrastructure 02 Challenges 03 Solutions OEM Patch Automation OEM 11g- Patch Automation Features ROI and Results 78

79 ROI and Results We have changed from custom script based patching to using OEMGC for patching. No incremental value in spending a large number of hours on repetitive tasks like patching. The tool takes the load off and lets DBA s spend more time on strategic tasks. OEM, adapted to PSU patches almost seamlessly as opposed to home grown scripts. 79

80 ROI and Results Without EMGC With EMGC Patching time from start to finish Administrator Time involved Installation time from start to finish Administrator Time involved ~ 300 hrs (150*.5 hours *4 /deployment) ~ 300 hours 15 min for each mass deployment. Each run may patch one or more of these 150 databases in parallel Average time for 150 deployments: 37 hours Few clicks We derived great value out of the product and hence we have continued to use it and move forward with it in other areas. 80

81 Resources Tip: Fixes are released almost every Quarter Follow Metalink Note: : OMS and Agent Patches required for setting up Provisioning, Patching and Cloning in 10.2 to 11.1 GC Enterprise Manager Administrator's Guide for Software and Server Provisioning and Patching /title.htm OEM 11g- OEM11g admin guide- d l /d / d/e11857 t ll 111/ /toc.htm 81

82 Thanks Deepa Nambiar Johns Hopkins University Applied Physics Laboratory Johns Hopkins Rd Laurel, Maryland

83 Oracle Helps You Maximize Customer Value Deploys SOA infrastructure 92% faster Saves 80% time and effort for managing Databases Avoids online revenue losses up to 25% Improves IT productivity by 25% Drives asset utilization up by 70% Cuts configuration management effort by 90% Saves $1.9 million with Oracle Enterprise Manager Saves $170,000 per year with Oracle Enterprise Manager Replaces manual tools with automation; saves time by 50% Reduces Database testing time by 90% Reduces provisioning effort by 75% Saves weeks on application testing time Cuts application testing from weeks to hours Reduces critical patching time by 80% Delivers 24/7 uptime with Oracle Enterprise Manager 2010 Oracle Corporation 83

84 2010 Oracle Corporation 84

85 Additional Information Database Patching with Enterprise Manager 11g OTN.com ons/provisioning.html 2010 Oracle Corporation 85

86 2010 Oracle Corporation 86

87 2010 Oracle Corporation 87