What it is and how to use it ADOP Online Patching What it is and how to use it Brett H Barnhart, Sr Manager of Technical Application Management Fred Tingle, Application DBA Manager October 26, 2017 Heartland Oracle User Conference

Agenda Executive Summary Introductions and Company Overview Technology Overview What is ADOP Patching How to prepare and remain healthy Using ADOP Summary Q & A

Executive Summary Here is a case study of how HNI a leading office furniture manufacturer performed a performance and load test of its solution, hardware, interfaces, and process orchestration as part of a readiness strategy for system roll-out. Having a complex ERP footprint including EBS, VCP, SOA, BI-Publisher, UC4, Endeca, OBIA (OBIEE), Scan Guns, and other interfaces, the Load Test team faced unique challenges in meeting the objective of Load Testing and Performance testing HNI’s full solution.

Brett Barnhart Introduction Technical Application Manager at HNI Corp since May 2014 Application Integration SOA, BizTalk, Informatica Solution Delivery EBS/VCP and related applications code delivery Scheduling and Workflow Administration UC4 Release Execution Application and Database Administration 18 Yrs Experience with Oracle EBS Development/Management

Fred Tingle Introduction Application Database Manager EBS, VCP, SOA, Endeca, Demantra, SSO, OIM, EDQ Legacy Oracle Databases, SQL Server, MYSQL SOA Admin, Endeca Admin, UC4 Admin, SSO/OIM Admin, EDQ Admin 17 years of Oracle experience 13 years of Oracle Applications experience

HNI Corporation Overview HNI Corporation (NYSE: HNI) (http://www.hnicorporation.com/) is the second-largest office furniture manufacturer in North America, and the nation's leading manufacturer and marketer of gas- and wood-burning fireplaces.

ADOP Online Patching What is it? Conceptually, what is ADOP Online Patching? Starting in 12.2, EBS now has 2 file systems. Run and Patch In Online mode, patches are applied to the Patch File System while the application is running. There is a short downtime during "Cutover" when the Patch File System becomes the Run File System. Database objects are "Editioned", so that structure changes become non-breaking

Technical aspects of ADOP online patching You will have 2 of everything! Disk space for run file system and the mirror of the patch file system space has to be accounted for. Large number of editioned objects inside the database for online patching Two Weblogic homes(run and patch) Increased amount of time needed from your DBA team. Increased amount of time it takes to start and stop the instance Longer cloning times due to setting up both run and patch file systems Additional complexity in the patching process Increased areas of technology that is new to your DBA team such as the use of Weblogic in the Application tier vs 12.1.3 version of EBS application.

Technical aspects of ADOP online patching: Continued 3.  DBA's have longer hours due to the amount of time needed to apply the online patches but reduces users downtime experience. Have strict controls in place and quality testing plans. Make certain you stay up to date on patching of AD and TXK since Security patches will force these upgrades over time. Cloning issue get resolved in later version of AD and TXK so keep that in mind when you are having cloning issues. Keep in mind that with different patches you can run into patching issues in production even though you've tested on recent clones of production(10/15/2017)…..My personal example of where data in the system caused patching to fail...Long Day!

ADOP Online Patching Online vs Downtime mode Downtime is essentially the existing cold patching that we’ve had in EBS. Patches are applied directly to the Run file system during a system downtime. Online patching is the new and supported method of applying patches Document 1583902.1

ADOP Online Patching What are the stages

ADOP Online Patching The steps Prepare Used to start a new online patching cycle Checks whether to perform a cleanup, which will be needed if the user failed to invoke cleanup after the cutover phase of a previous online patching cycle. Checks the integrity of the database data dictionary. If any corruption is found, adop exits with an error. Checks system configuration on each application tier node. A number of critical settings are validated to ensure that each application tier node is correctly registered, configured, and ready for patching. Generally, we run a FS_Clone cycle prior to prepare to ensure that Patch FS is fully in sync with Run FS

ADOP Online Patching The steps Apply In the apply phase, adop applies the specified patches to the system. Patches are applied to the patch edition of the database and file system. Finalize The finalize phase will be executed while the application is still online. It is used to perform any remaining processing that is needed to ensure the system is ready for the fastest possible cutover. Pre-compute DDL that needs to be run at cutover Compile all invalid objects Validate that the system is ready for cut-over If finalize_mode=full, compute statistics for key data dictionary tables for improved performance

ADOP Online Patching The steps Cutover Used to perform the transition to the patched environment. Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase the involves a brief downtime. Cleanup This adop phase is used to remove obsolete code and data from old editions. Reference: http://expertoracle.com/2016/02/21/online-patching-adop-in-oracle-ebs-r12-2/

ADOP Online Patching Preparing your code Guidance for Integrating Custom and Third-Party Products With Oracle E Business Suite Release 12.2 (Doc ID 1916149.1) Note: ADZDDBCC.sql is from note 1531121.1 Type of Compliance Rule Tools Minimal Non-editioned objects cannot depend on editioned objects. Run ADZDPSUM.sql, ADZDPAUT.sql, and ADZDPMAN.sql and fix any violations References to the data model must go through a synonym in the apps schema. Run gscc.pl and fix all violations. Run ADZDDBCC.sql and fix all violatons tagged as minimal. Full Follows rules for minimal compliance plus additonal development standards laid out in the Developer's Guide. Run ADZDPSUM.sql, ADZDPAUT.sql, and ADZDPMAN.sql and fix any violations. Run gscc.pl and fix all violations. Run ADZDDBCC.sql and fix all violations, including those tagged as minimal and those tagged as full.

ADOP Online Patching Basic rules of development Do not call base tables directly, always call the editioned synonym. Easy solution is to prefix all objects with APPS for code not in the APPS schema Custom Code objects need to live in the APPS schema Packages, procedures, functions, views, triggers, types, synonyms Do not create synonyms manually. Custom tables need to be editioned Oracle script creates an editioned view and synonym in APPS Register all custom schemas with the application Do not use LONG data types

ADOP Online Patching Basic rules of development Table Names cannot exceed 29 characters or use ‘#’ Column names cannot exceed 28 characters Materialized View Names cannot exceed 29 characters Object Names end in alphanumeric character Index and constraint names must contain at least one ‘_’ All files going to file system have to have the following header (/* $Header: <Packagename> <Version#> <DateTime> appldev noship $ */) This is used for AD Maintain Snapshot information

Summary ADOP Online patching can greatly reduce down time required for patching. If used for Custom Code, it also provides stability and the registration of that code deployment in the Application. Per Oracle, Online patching is the only approved mechanism for applying patches in 12.2, unless otherwise directed by Oracle.

Questions? Q & A Brett Barnhart - barnhartb@hnicorp.com Fred Tingle- tinglef@hnicorp.com