The Big Picture of the Release Upgrade. Mike Swing CTO TruTek

The Big Picture of the Release 12.2.4 Upgrade Mike Swing CTO TruTek

Learning Objectives Objective 1: Understand the detailed technical steps required to upgrade to R12.2. Objective 2: Learn about ADOP, the Online Patching Utility, the options and how to use the options. Objective 3: Examine ways to reduce the upgrade downtime. Objective 4: Investigate the steps involved with the associated database upgrade that may be needed for the R12.2 upgrade. 2 2

Training, Consulting, Books about the E- Business Suite mswing@trutek.com blog.trutek.com www.trutek.com 3

4

When Should You Choose 12.2? Consider targeting 12.2 if any of the following circumstances applies to your organization:. You need the high availability provided by Online Patching. You want the functional enhancements that are in 12.2. You prefer to invest in a single project to upgrade directly to 12.2. 5

Reasons to Upgrade to 12.2? Online Patching for continuous business operation Tech stack modernization for operational efficiency More modern user experience to appeal to users New functional features to reduce customizations & improve automation Continuing, easy-to-adopt updates in 12.2 Longer support life on 12.2 6

Support Timeline from Anne Carlson 7

Nadia s Benejou s R12.2 List 12.2 Overall E-Business Suite Readiness 1. Review the Functional Changes 2. Understand the Technical Architecture Changes 3. Consider Upgrading your Technical Architecture 4. Learn about WebLogic Server 12.2 Online Patching Readiness 5. Understand the 12.2 Patching Cycle 6. Understand Edition Based Redefinition 7. Understanding the Enablement Process 8. Review Online Patching Standards 9. Plan for 12.2 Dual File System 10. Consider New Operational Characteristics 8

Functional NF from Nadia Understand the new accounting model in R12 Understand the upgrade impact on 11i setups and data R12 Upgrade Considerations by Product (Doc 889733.1) Accounting Setup Manager Pre-Update Diagnosis Report (Doc 961742.1) Understand the Datamodel changes from 11i. Doc 1290886.1 Evaluate the impact on your 11i customizations and consider native functionality wherever possible. Upgrading your Customizations to Oracle E-Business Suite Release 12.1 (Doc 1435894.1) EBS File System Comparison Report (Doc 1446430.1) 9

Functional NF from Nadia Evaluate new 12.2 functionalities: Yard Mgt, Outsourced Mfg, In-Memory Costing, Supply Chain Event Mgt (more. Doc 1302189.1) Review the functionalities and modules that have been replaced, such as DBI (Daily Business Intelligence), Oracle Balanced Scorecard, Oracle Financials and Sales Analyzers etc (Doc 1302189.1) Ten Things You Can Do Today to Prepare for Oracle E- Business Suite 12.2 OOW13 Nadia Bendjedou 10

Obsolete Products in R12.2 * Oracle Balanced Scorecard * Oracle CAD-View 3D * Oracle Contracts Intelligence * Demand-Side Product Data Synchronization for GDSN * Supply-Side Product Data Synchronization for GDSN * Oracle E-Business Intelligence * Oracle Enterprise Planning and Budgeting * Oracle Financial Aid * Oracle Financial Consolidation Hub * Oracle Financials and Sales Analyzers * Oracle Financials Intelligence * Oracle Funds Pricing * Oracle Grants Proposal * Oracle HR Intelligence * Oracle Install Base Intelligence * Oracle Interaction Center Intelligence * Oracle Internal Controls Manager * Oracle Marketing Intelligence * Oracle Operational Intelligence * Oracle Personal Portfolio * Oracle Process Manufacturing Intelligence * Oracle Procurement Intelligence * Oracle Product Intelligence * Oracle Product Lifecycle Management * Oracle Profitability Manager 11

Obsolete Products in R12.2 * Oracle Projects Intelligence * Oracle Public Sector Budgeting * Oracle Sales Intelligence * Oracle Service Intelligence ** Oracle Student Recruiting ** Oracle Student Systems * Oracle Supply Chain and Order Management Intelligence * Oracle Transportation Execution * Oracle Transportation Planning * A migration plan exists for customers who have purchased these products in earlier releases. Contact your Sales Representative or Account Manager for more information. ** Customers continuing to use Oracle Student Recruiting and Oracle Student Systems should not upgrade to this release. Support will be provided to existing customers on earlier releases, in accordance with the Oracle Lifetime Support Policy 12

Anne Carlson s List 1. Build the Business Case for 12.2 Upgrade 2. Understand Factors Affecting Time and Resources 3. Understand Online Patching Architecture 4. Plan for Impacts on Apps DBAs 5. Plan for Impacts on Customization Developers 6. Understand the 12.2 Upgrade Process 7. Prepare to Minimize Upgrade Downtime 8. Prepare for Required System Changes 9. Prepare Your Testing Strategy 10.Leverage Key Reference Materials 13

Upgrade database to 11.2.0.3 Complete migration to 64-bit database Complete migration to OATM Migrate to Multi-Org Purge unnecessary data Find bad data Fix bad data Compile a list of all customizations 15

Evolution of the Application Tier 11i R12.0 and R12.1 R12.2 16

EBS Database Tier Evolution 11i R12.0 and R12.1 R12.2 17

rh14 Rh11 rh13 rh12 rh10 rh16 rh15 Start with 12.1.1 Upgrade DB to 11.2.0.3 or 12.1.0.2 Post Patches For 12.1.0.2 Install 12.2.0 Run Preinstall Patches 1448102.1 1320330.1 Merge admode R12.AD.C (10117518) and AD CUP5 patch (18040523: R12.AD.C) with 19477748: Start 12.2.0 10124646 11i 18 hours 12.1 6-8 hours with 20937084 from doc 1320300. 1 Phase A32 Finish 12.2.0 Configure R12.2.0 Online Enablement Patch 13543062 TXK/AD RUP5 12-16 hours Apply 12.2.4 17919161 6-8 hours 12.2.4 Online Help Patch 179191 62 18

R12.2.4 Technical Upgrade Class Apps R12.1.1 to R12.2.4 Database 11.1.0.7 to 11.2.0.3 (12.1.0.2) If you are migrating to R12 you must take this class. The hands-on training and knowledge of the instructor is invaluable. -Roland 19

Upgrade Steps R12.1.1 to R12.2.4 Upgrade Database to at least 11.2.0.3. We ll upgrade to 12.1.0.2, Doc ID 1524398.1, 12.1.0.2 software from Patch 17694377, Database Preparation Guidelines for an E- Business Suite Release 12.2 Upgrade (Doc ID 1349240.1) Install 12.2.0 - Oracle E-Business Suite Installation Guide: Using Rapid Install, Release 12.2 (12.2.0) Part Number E22950-18 Apply CUPs and R12.AD.C - Merge R12.AD.C (10117518) and AD CUP5 patch (18040523:R12.AD.C) with 19477748:R12.AD.C Upgrade to 12.2.0 Oracle E-Business Suite Upgrade Guide, Release 12.0 and 12.1 to 12.2, Part No. E48839-09 - Upgrade driver u10124646.drv 20

Upgrade Steps R12.1.1 to R12.2.4 Online Patching Enablement-Patch 13543062 Apply AD/TXK RUP6 Doc ID 1617461.1 Apply 12.2.4 downtime mode Patch 17919161 Post upgrade steps & patches 21

R12.2 Upgrade Flowchart 22 11.5.9 and lower No 11.5.10.2 Yes Yes Upgrade to 11.5.10.2 Upgrade to 12.2.0 Upgrade to 12.2.0 Upgrade to 12.2.4 Upgrade to 12.2.4 Upgrade Guide Release 11i to 12.2 Part No. E48834-03 No 12.0.4 12.0.6 Yes Upgrade to 12.2.0 Upgrade to 12.2.4 Upgrade Guide Release 12.0 and 12.1 to 12.2 Part No. E48839-03 No 12.1.X Yes Upgrade to 12.2.0 Upgrade to 12.2.4 Upgrade Guide Release 12.0 and 12.1 to 12.2 Part No. E48839-03 22

R12.2 Upgrade Paths For 11i, you must be on 11i10CU2 and satisfy the minimum baseline patch level (MBL) requirements for extended support (MOS ID 883202.1) for a direct upgrade to R12.2 Apply patch 13543062 as an additional step to enable edition based redefinition (EBR) after the US upgrade driver is complete. All patches beyond this step MUST be applied using ADOP ( online patching compatible version of adpatch ) The EBS upgrade to R12.2 itself is NOT an Online Patch 23

Best Practices for Minimizing Oracle E-Business Suite Release 12.2 Upgrade Downtime by Jim Machin Fixed object and dictionary statistics are not gathered automatically in the Release 12.2 upgrade They will change after platform, database or E- Business Suite upgrades. Also after Online Patching Enablement (and the underlying Edition-Based Redefinition) Internal SQL in Online Patching Enablement, R12.2 RUPs and other online patches can sometimes be long running. Gathering fixed object or dictionary statistics can help. 24

Best Practices for Minimizing Oracle E-Business Suite Release 12.2 Upgrade Downtime by Jim Machin The new diagnostics available for ADOP are logs. They do not identify the SQL or underlying events that caused the performance issue Use AWR reports, AD Job Timing Reports, Display Cursor Reports, SQL Traces, TKPROFs, SQLT with XTRACT. statistics_level = ALL or _rowsource_execution_statistics = TRUE. There are no statistics on display cursor or SQLT without this AWR Reports (each long running job, each snapshot). They can be automated. See Performance Diagnosis with AWR (Document 1674086.1) SQL Trace can be gathered for specific jobs, but only once you know that they are long running. It does not tell you the exact joins/filters (predicates). You can get actual statistics (rowsource and waits) on the first iteration using Display Cursor report and AWRs 25

Best Practices for Minimizing Oracle E-Business Suite Release 12.2 Upgrade Downtime by Jim Machin Express Diagnosis of Oracle E-Business Suite Release 12 Upgrade Performance Issues (Document 1583752.1) describes this method and includes useful scripts. Before the Oracle E-Business Suite Upgrade: Set the statistics_level to ALL or _rowsource_execution_statistics = TRUE (there are no statistics without this) During the Oracle E-Business Suite Upgrade: Monitor top SQL in AWR or Cursor Cache (memory). This could be internal or application SQL. Enterprise Manager can also be used to identify expensive SQL as it occurs 26

Phase A32 Create Indexes 27

Service Control Scripts Service Group Service(s) Service Control Script Root Service Node Manager adnodemgrctl.sh Web Administration WebLogic Admin Server adadminsrvctl.sh Web Entry Point Services Oracle HTTP Server Oracle Process Manager Web Application Services oacore oafm forms forms-c4ws Batch Processing Services Other Services Oracle TNS Listener Concurrent Manager Fulfillment Server Oracle ICSM Forms Server Oracle MWA Service adapcctl.sh adopmnctl.sh admanagedsrvctl.sh admanagedsrvctl.sh admanagedsrvctl.sh admanagedsrvctl.sh adalnctl.sh adcmctl.sh jtffmctl.sh ieoicsm.sh adformsrvctl.sh mwactlwrpr.sh 28

12.2 Configuration EBS and DB Profile Options, Developer 10g, AutoConfig OAM, AutoConfig HTTP Weblogic Performance directives, log configuration, ports, mod_wl_ohs, mod_perl oacore, oafm, forms and forms-c4ws services FMW Control WLS Admin Console 29

R12.2 Architecture http://blogs.oracle.com/stevenchan/entry /glimpses_of_e_business_suite 30

31

11g FMW Application Server OPMN Manages HTTP & Weblogic Client J2SE plug-in Database 11.2.0.3 or 12.1.0.2 Web Listener Forms Runtime Engine 10.1.2 - frmweb SQLNet HTTP Server Apache mod_wl Parent WL Web Container JVM Forms WL Web Container Forms Listener Servlet Child Child Child JVM OACore WL Web Container JDBC Conn Object AOL/J JDBC Conn Pool.dbc SGA 32

R12.2 Disk Space Requirements Ensure that there is sufficient temporary disk space. You should have at least 50 MB in the temporary directories denoted by $APPLTMP and $APPLPTMP (UNIX). You should also have space in the operating system s default temporary directory, which is usually /tmp or /usr/tmp (UNIX). SYSTEM tablespace has a minimum of 25 GB of free space APPS_TS_SEED tablespace has a minimum of 5 GB of free space 33

R12.2 Disk Space Requirements Node Database node file system (Fresh install) Database node file system (Vision Demo database) Applications node file system (OracleAS 10.1.2 Oracle Home, Oracle FMW Oracle Home, COMMON_TOP, APPL_TOP, and INST_TOP) Space Required 90 GB (includes database files and 11gR2 database Oracle Home). 200 GB (includes database files and 11gR2 database Oracle Home). 64 GB (for dual file system). Also, see Note below for language (NLS) considerations. 34

12.1.3 vs 12.2 Size Comparison Component 12.1.3 12.2 ORACLE_HOME 3.6 GB 3.6 GB APPL_TOP 28 GB N/A INST_TOP 20 MB N/A fs1 (APPL_TOP+ INST_TOP) fs2 (APPL_TOP+ INST_TOP) N/A N/A 30 GB 29 GB fs_ne N/A 660 KB 35

File Systems for 12.2 During Release 12.2 installation, Rapid Install will lay down two copies of the application tier file system, FS1 and FS2, or Run Edition and Patch Edition. Run Edition Patch Edition 36

File Systems for 12.2 There are two copies of the application tier file system, fs1, fs2, or the Run Edition and the Patch Edition. There also a non-editioned file system, fs_ne Application Server 1 Application Server 2 Application Server 3 Shared APPL_TOP vs non shared APPL_TOP 37

R12.2 Online Patching https://blogs.oracle.com/stevenchan/entr y/glimpses_of_e_business_suite 38

Online Patching All EBS patches for Release 12.2 and beyond are Online Patches Online Patching of code is enabled by the Dual File System and 11gR2 Database Editioning features Online Patching of transactional tables is enabled by Editioning Views and Cross-Edition Triggers The Patch Edition becomes the Run Edition at Cutover Run Edition Patch Edition 39

Data is updated in the Patch Edition during Patching Planning and Preparing for Your Upgrade to Oracle E-Business Suite 12.2 Anne Carlson OOW12 During patching, data updates are propagated from the Run Edition to the Patch Edition using Cross-Edition Triggers 40

Cross-Edition Triggers Update Data in the Patch Edition Planning and Preparing for Your Upgrade to Oracle E- Business Suite 12.2 Anne Carlson OOW12 41

Editions and Tables Tables cannot be versioned: there is only one definition of a table across all Editions Data is not versioned: a record exists once and only once The solution for managing changes to Tables: Editioning Views and Cross Edition Triggers. Editioning Views are defined on base table (no joins) Editioning Views can have DML triggers defined (just like base table). Using an editioning view in a query or DML statement does not impact the performance of the query or DML 42

Cross Edition Triggers If you remove a (mandatory) column from the current Editioning View a Reverse Cross-edition Trigger ensures that new records get some value in that (invisible) column If you add a (mandatory) column to the table (and the current Editioning View) a Forward Cross-edition Trigger ensures that records DMLed through previous Editioning View versions are made valid (optionally) Apply Forward Cross-edition Trigger for all existing records (created in old edition of the table) Use DBMS_SQL.parse (with parameter Apply_Crossedition_Trigger set to name of trigger) Use DBMS_PARALLEL_EXECUTE 43

Payroll Functionality Not Available During ADOP US localization earnings and deduction setup cannot be used. Tax Withholding Rules Setup cannot be used. Wage Attachment Earnings Rules Setup cannot be used. Garnishment Rules Setup cannot be used. Quick Paint Reports cannot be used. Quantum Program Update Installer execution is unavailable. 44

Functionality Not Available During ADOP Order Management: Creation of a new Defaulting Condition in the Attribute Defaulting Rules form is disabled, unless the same seeded condition already exists for a given attribute. Warehouse Management: WMS Rule creation is restricted. Inventory: Concurrent program Generate Stock Locator Flexfield Definition for Mobile Transactions will be disabled. 45

Functionality Not Available During ADOP Public Sector Financials International: Users will not be able to run the following concurrent programs: Subledger Security: Apply Security Subledger Security: Import/Export Data Fix Subledger Accounting: Users will not be able to Validate the Application Accounting definitions. Accounts Receivable: Users will not be able to create new Transaction Sources. 46

Functionality Not Available During ADOP Incentive Compensation: Transaction collection process for new mappings will not be available and any changed mapping will continue to use previous mapping rules. Users will not be able to run the Synchronize Classification Rulesets program. Users will not be able to use the Formula Generation feature. Users will not be able to specify new formulas or changes to compensation rules. Oracle Demand Planning: Demand plans will not be available for users. 47

Materialized Views The Materialized View is a non-editioned object type, and therefore a materialized view cannot directly reference editioned objects. To avoid this limitation, Oracle E-Business Suite Online Patching technology implements a new Effectively Editioned Materialized View compound object. Application developers create and maintain the Materialized View Definition (query) in an ordinary view. The Online Patching technology then automatically maintains a corresponding Materialized View Implementation that is legal for editioned databases. 48

Custom Code Custom code may need to be EBR compliant in preparation for the upgrade to R12.2 Compliant with Online Patching standards. Use the Online Patching Readiness Report, Manual Fix Readiness Report, Global Standards Compliance Checker script and Online Patching Database Compliance Checker to evaluate code compliance. 49

Customizations in R12.2 Global Standards Compliance Checker (GSCC) Virtual Private Database (VPD) Policy Ordinary Tables Table Usage Standards Materialized Views 50

Global Standards Compliance Checker (GSCC) This patch delivers scripts to automatically check that custom code complies with E-Business Suite (EBS) online-patching coding standards. The implementation of Online Patching in Oracle E- Business Suite Release 12.2 relies on the Oracle Database 11gR2 Editioning feature and adds a new logical view over the database objects in Oracle E- Business Suite. File.Gen.35 Table must be owned by an EBS product schema Table and not APPS. File.Gen.41 Query/DML statements must access Tables via the Table Synonym or Editioning View. 51

ADOP Cycle R12.2. Maintenance Guide 52

Customize the Patch Edition Before running finalize_mode # Apply any customizations to patch edition (optional): $. <EBS_ROOT>/EBSapps.env patch $ sqlplus apps/apps @my_custom_script_01 $ sqlplus apps/apps @my_custom_script_02 53

apply_mode=downtime $ adop phase=apply patches=123456 apply_mode=downtime Allows patches to be applied in downtime mode. Added to adop phase=apply command. apply_mode=downtime applies the specified patches in downtime mode. When using this mode, you only run the apply phase. Important: Downtime mode is only supported for production use where specifically advised by Oracle. 54

apply_mode=downtime From Doc ID 1903052.1 for AD, TXK RUP4 3.3.1 Alternative For Systems Experiencing Online Patching Issues If your system is currently experiencing problems executing online patching cycles, you may apply the AD/TXK consolidated patches in downtime mode. Execute the following commands: Shut down application tier services on all nodes. $ adop phase=apply patches=18491990,18497540 apply_mode=downtime Start up application tier services on all nodes. 55

ENABLE_ADPATCH=YES export ENABLE_ADPATCH=YES adpatch works in standalone mode 56

Online Patching Future Enhancements Planned Increase number of diagnostic tools for Online Patching Allow testing against Patch Edition after patching is complete Under Investigation Rollback patches after cutover 57

adopscanlog To scan all log directories of the latest adop session for errors: $ adopscanlog The utility can also be run with various options. Examples include: To scan log directories relating to the latest run of adop in the latest session: $ adopscanlog -latest=yes To scan log directories relating to the latest run of the specified phase, in the latest session: $ adopscanlog -latest=yes -phase=<phase_name> To scan all log directories of a given session (represented by a session_id) for errors: $ adopscanlog -session_id=<number> To see a complete list of supported parameters: $ adopscanlog -help 58

UPGRADE THE DATABASE 59

Database Upgrade MOS Notes Oracle Applications Release Notes, Release 12.1.1 (Document 798258.1) Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID 1320300.1) Interoperability Notes Oracle EBS 12.2 with Oracle Database 12c Release 1 (Doc ID 1926201.1) Interoperability Notes EBS 12.0 or 12.1 with RDBMS 12cR1 (Doc ID 1524398.1) You can obtain the 12.1.0.2 software from Patch 17694377 on My Oracle Support Database Preparation Guidelines for an E-Business Suite Release 12.2 Upgrade (Doc ID 1349240.1) 60

Prepare to Upgrade the Database Update application tier context file with new database listener port number Install the 12.1.0 software Install Oracle Database 12c Products from the 12c Examples CD (mandatory) Apply additional 12.1.0.2 RDBMS patches Document 1594274.1 Create nls/data/9idata directory Install JRE 6 - see document 1459546.1 61

Patches from Doc ID 1594274.1 12.1.0.2 Patches for 12.2 18689530, 19393542, 19472320, 19562030, 19649152, 19779028, 19779059, 19291380, 19627012, 19896336, 20093776, 20177858, 20181016 Forms and Reports Patches 18186693 (see Footnote 12), 18620223, 19434967 (see Footnote 14) Footnote 12 - This is the Forms Overlay Patch on 10.1.2.3.2. For a more recent Forms Overlay Patch 19434967 should be applied instead on Unix/Linux. Footnote 14 - This is the Forms Overlay Patch on 10.1.2.3.2. For a full list of inclusions and OUI/OPatch requirements, refer to the patch README FMW webtier 11.1.1.6 17555224, 17639414, 19945419 62

APPLY CUPS, PRE-INSTALL PATCHES AND UPGRADE TO 12.2.0 63

Just Before the Upgrade Flush all the interfaces, ex. Auto Invoice, Order Import Gather the schema statistics (with GATHER_AUTO option for all schemas) close to the start of the downtime. Use FND_STATS or Gather Statistics concurrent programs Stop all Concurrent Jobs, so they won t start when the CM starts again Gather Fixed Object and Dictionary Statistics 64

Prepare to Upgrade Chapter 2 Drop event alert triggers in custom schemas (conditional) Review sizes of old and new tablespaces (required) Migrate Existing Objects to New Tablespace Model (OATM) If 12.0.4 or 12.0.6, apply patch 11939659 Run the American English Functional Tasks Financials, Procurement, Subledger Accounting, Human Resource Management (HRMS), Supply Chain Management Tasks, Product Hub Gather Schema Statistics JRE Install on the database tier (conditional) Reset init.ora parameters (required) Run Rapid Install to install 12.2.0 (required) MOS Note 1330701.1 65

Prepare to Upgrade Chapter 2 Synchronize values of APPLPTMP with UTL_FILE_DIR for PL/SQL based Concurrent Requests (required) System Backup Migrate database to at least Oracle11g Release 2 Use MOS Note 1594274.1 to apply patches for 11.2.0.3 Follow MOS Note 1349240.1 to apply 11.2.0.3 patch 16303726 66

APPLY CUPS AND UPGRADE TO 12.2.0 67

From Doc ID 1320300.1 $ adpatch preinstall=y Apply the pre-upgrade patches that were released after the Consolidated Upgrade Patch 18007406:12.2.0. Refer to My Oracle Support Knowledge Document 1448102.2 for the Oracle E-Business Suite Release 12.2 Pre-install Patches Report; it provides a list of essential patches that you must apply in pre-install mode before upgrading from Release 11i/12.0/12.1 to Release 12.2. Follow the recommendations within My Oracle Support Knowledge Document 1448102.2 and apply the additional pre-install patches. 68

Document 1448102.2 Pre-install Patches Report SCM Upgrade script failure Data corruption Performan ce issue Upgrade integrity fix TOTAL MSD 1 - - - 1 ONT - - 1-1 ITM - - 1-1 TOTAL 1 0 2 0 3 69

Pre-upgrade Patches from 1448102.2 PRODUCT PATCH PATCH_ABSTRACT QRE1220CUP5:JL.SQL:SKIPPED JOB: 18995966 JL JLZZMIGAWTDIST.SQL ON JL_ZZ_AP_INV_DIS_WH_ALL_TI PAY 19730774 PAY_33193_UPG_CANNOT_ENABLE ERROR on PYSAGUPUDT.LDT in 12.2 Upgrade CSM 19503850 QRE:GSIUPG:FAILURE:CSM:CSMCSMA.ODF MSD 19601460 QRE:GSIUPG:VIEW FAILURE:MSD:MSDSVW06.SQL XLE 18792770 XLEUPG01.SQL FAILING R12.2 UPGRADE PAY 19584199 AMS 18973713 AP 20280791 PJC 20179510 AP 19391190 Upgrade 11.5.10.2 TO 12.2 fails on pyfkbal.sql and pyfkteng.sql UPGRADE SCRIPT DELETES THE CATEGORY WITH CATEGORY_ID 10000 RCA: XLA_DISTRIBUTION_LINKS TABLE NOT GETTING POPULATED FOR MANUAL PAY ADJ EVENT TRACKING BUG TO STUB OUT PATRXINTDEL.SQL ON 12.2.X CODE LINE CODE: WRONG UPDATE ON HZ_ORGANIZATION_PROFILES IN APSTCA01.SQL 70

Pre-upgrade Patches from 1448102.2 AR 18951016 PERFORMANCE ISSUE WITH AR120TRXPSA.SQL IN PATCH 10124646 AP 19080116 AR 20018655 JAI 20293834 PERFORMANCE PROBLEM WITH APXLAUPG.SQL SCRIPT DURING R12.2.2 UPGRADE UPGRADE TO 12.2: AR120TRXPSA.SQL PERF AND ORA-00001 RUNNING MULTIPLE WORKERS 1OFF:17639120:JAI_DF_3848220.SQL IS RUNNING FOR MORE THAN 14 HOURS XLA 19807467 FIX PERFORMANCE OF LONG RUNNING NEW SQLS IN XLAAXUAR.SQL ITM 20226747 SQL 3012796.SQL RUNNING LONG ON DRIVER PATCH ONT 20366382 ONT00161.SQL: Added checkfile syntax to prevent re-application of file during 12.2 upgrade IBY 19765736 Upgrade integrity fix--ebs ADZDPMAN.SQL REPORTS ERROR WITH IBY_TRXN_SUMMARIES_ALL.INITIATOR_EXTENSION_ID#1 PAY 20526716 122: DELIVER SCRIPT TO UPGRADE SPWL SEED TABLES 71

CUPs and PreInstall Patches 1. Step 9 from the Upgrade Guide, page 3-5, apply patch 10117518 and other patches as noted in the README 2. From the 10117518 README Merge 10117518, 18040523, 19477748, 20937084 using admrgpch -admode

CUPs and PreInstall Patches 3. Step 10 from the Upgrade Guide Note 1320300.1 - Section 3.1 Step 1-10117518 - already applied Step 2-18007406 preinstall=y Check the APPL_TOP/admin/TWO_TASK/preinstall directory is empty Apply preinstall patches from 1448102.2 If DB is 12.1.0.1 or greater apply 19587162, 19985726 Step 3 - merge driver files cd $AU_TOP/patch/115/driver admrgpch -d. -preinstall -master u10124646.drv

CUPs and PreInstall Patches 4. Step 4 from Note 1320300.1 and step 11 from the Upgrade Guide adpatch options=nocopyportion,nogenerateportion

PERFORM THE UPGRADE CHAPTER 3 75

Perform the Upgrade Chapter 3 Disable AOL Audit Trail (conditional) Shut down application tier listeners and concurrent managers (required) Update init.ora with upgrade parameters MOS Note 396009.1 Set FAILED_LOGIN_ATTEMPTS to UNLIMITED for Oracle E-Business Suite schema - Doc ID 403537.1 Disable custom triggers, constraints, and indexes (conditional) Back up the database (recommended) Ensure that Maintenance Mode is enabled Apply AD 12.2 upgrade driver prerequisite patch 10117518 76

Perform the Upgrade Chapter 3 Apply all Consolidated Upgrade Patches (CUPs) listed in the Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID: 1320300.1) Run the American English upgrade patch driver (required) u10124646.drv merged as follows: To bring your database to the full Oracle E-Business Suite Release 12.2 level, use AutoPatch to run the (American English) upgrade patch driver (u10124646.drv) merged with latest Consolidated Upgrade Patch for Oracle E-Business Suite Release 12.2 Disable Maintenance Mode (required) Reset init.ora parameters (required) MOS Note 396009.1 77

Merge and Apply R12.AD.C and AD CUP5 When directed to apply AD 12.2.0 (R12.AD.C) in Chapter 3, Upgrading to Release 12.2 within "Oracle E- Business Suite Upgrade Guide 12.0 and 12.1 to 12.2" and "Oracle E-Business Suite Upgrade Guide 11i to 12.2", perform the following steps instead: Merge R12.AD.C (patch 10117518) and AD CUP5 patch (patch 18040523:R12.AD.C) with patch 19477748:R12.AD.C. Note: This merge is a full merge using admode. 78

Merge and Apply R12.AD.C and AD CUP5 Example: Download patch 10117518, 20029957 (if using 12c), 12.2.0 AD CUP5 patch 18040523 and patch 19477748 under <PATCH_TOP>/AD_source mkdir -p <PATCH_TOP>/10117518_CUP5 admrgpch -s <PATCH_TOP>/AD_source -d <PATCH_TOP>/10117518_CUP5 -merge_name 10117518_cup5 -admode 79

Upgrade to 12.2.0 No need to merge drivers as the pre-install patches have already been applied. Change directory to <AU_TOP>/patch/115/driver cd $AU_TOP/patch/115/driver adpatch options=nocopyportion,nogenerateportion 80

Start of 12.2 u_merged.drv 81

Finish the Upgrade to 12.2.0 Configure Release 12.2 E-Business Suite instance (required) Update the RDBMS ORACLE_HOME file system with AutoConfig and Clone files - perl <AD_TOP>/bin/admkappsutil.pl Install JRE on the database tier to ensure that the application tier and the database tier match (Conditional). Create the Context Name directory in the RDBMS oracle home. Generate a new database context file cd <RDBMS ORACLE_HOME>/appsutil/bin perl adbldxml.pl Clean up old node information Synchronize values of APPLPTMP with UTL_FILE_DIR for PL/SQL based Concurrent Requests Run AutoConfig on the database tier nodes. 82

Finish the Upgrade to 12.2.0 Source the Run filesystem environment file Run AutoConfig on the Apps Tier Run Rapid Install to configure the Release 12.2 E-Business Suite environment. You must run Rapid Install a second time to complete the configuration using Run File System context file. In the Rapid Install wizard, select Upgrade to Oracle E- Business Suite Release 12.2.0 and then select the option Configure Upgraded Release 12.2.0 Instance. Upgrade considerations for Add-on Localization products Integrate custom objects and schemas (conditional) Re-enable custom triggers, constraints, and indexes 83

Long Running Jobs adsstats.sql 5:55:51 apxlaupg.sql 5:27:22 adobjcmp.sql 0:59:23 eni_oltp_item_star_mlog.xdf 0:40:35 appdstln.sql 0:37:28 ADZDSTATS.sql 0:36:12 psadvefc.sql 0:31:25 adobjcmp.sql 0:28:16 apidstln.sql 0:19:15 apilnupg.sql 0:18:27 afnls.odf 0:13:30 ADZDWRKR.sql 0:12:29 84

appdstln.sql INSERT /*+ parallel(xtb) append */ INTO XLA_TRIAL_BALANCES XTB( RECORD_TYPE_CODE,SOURCE_ENTITY_ID,EVENT_CLASS_CODE,SOURCE_APPLICATION_ID,APPLIED_TO_ENTITY_ID,APPLIED_TO_APPLICATION_ID,GL_DATE,TRX_CURRENCY_CODE 85

adstats.sql Gather dictionary object statistics when there is a significant change in dictionary, for example, lot of new objects created. exec dbms_stats.gather_dictionary_stats; Gather fixed object statistics with reasonable load on the system exec dbms_stats.gather_fixed_objects_stats Dictionary and Fixed stats should be gather manually as they are not gathered automatically in the Release 12 upgrade by adstats.sql or any other method. 86

Export and Import Statistics if adstats.sql is long running The statistics can be exported using: FND_STATS.backup_schema_stats(schema_name => ALL, statid => '<your statid>') And imported using: FND_STATS.restore_schema_stats(schema_name => ALL, statid => '<your statid>') 87

ENABLE ONLINE PATCHING 88

Online Patching Readiness Report in Oracle EBS Release 12.2 (Doc ID 1531121.1) Apply the correct Online Patching Readiness and GSCC Report Patch for the code level from which you are upgrading: 20128107:R12.AD.C Release 12.2 or higher 20128107:R12.AD.B 12.1 20128107:R12.AD.A 12.0 20128107:11i The patch delivers a new set of Online Patching Development standards for Oracle E- Business Suite Release 12.2, plus a set of reports that will help you analyze the dependencies between database objects as specified by the new rules used by EBR. 89

$AD_TOP/sql/ADZDEXRPT.sql Report FIX_PUBLIC_SYNONYM 4902 S - Successfully Executed RECREATE_AQ_OBJECT 12 S - Successfully Executed DROP_OBJECT 4 S - Successfully Executed ENABLE_EDITIONING UPGRADE_TABLE 200 S - Successfully Executed 1 E - Error 1104 N - Not Executed 126 R - Running 18321 E - Error 90

ENABLE_EDITIONING Error Phase DDL ID Status ENABLE_EDITIONING 10361 ERROR SQL Error; begin ad_zd_prep.enable_user_4edition('apps'); end; ORA-38820: user has evolved object type 91

Enable Online Patching Verify the database version is at least 11.2.0.3 Ensure that the required Database patches for Release 12.2 have been applied Refer to Database Preparation Guidelines for an E- Business Suite Release 12.2 Upgrade (Doc ID: 1349240.1). Apply the latest Oracle E-Business Suite Online Patching Readiness and GSCC Report Patch Refer to Using the Online Patching Readiness Report in Oracle E-Business Suite Release 12.2 (Doc ID 1531121.1). Important: This patch must be applied using adpatch on the Run Edition File System 92

Run the Online Patching Enablement - Readiness Reports Refer to Using the Online Patching Readiness Report in Oracle E-Business Suite Release 12.2 (Doc ID 1531121.1) for instructions on how to download these utilities. You must run the following utility from the application tier APPL_TOP. It reports EBR violations that include objects not complying with the EBR rule about Non-Editioned Objects (data storage objects such as Tables and Materialized Views), and referencing editioned objects (code objects such as: Packages, Triggers, Object Types, and so on). 93

Run the Readiness Reports Run the following Readiness reports: ADZDPSUM.sql sqlplus system @$AD_TOP/sql/ADZDPSUM.sql mv adzdpsum.txt adzdpsum_pre_dbprep.txt ADZDPMAN.sql sqlplus system @$AD_TOP/sql/ADZDPMAN.sql mv adzdpman.txt adzdpman_pre_dbprep.txt ADZDPAUT.sql sqlplus system @$AD_TOP/sql/ADZDPAUT.sql mv adzdpaut.txt adzdpaut_pre_dbprep.txt Fix any violations -. Oracle recommends that you perform the chosen fix by customizing template file 94

Run the Online Patching Enablement - Status Report Set the current directory to $LOG_HOME/appl/op: cd $LOG_HOME/appl/op Take special note to ensure that all online patching objects (objects that match the pattern 'AD_ZD%') are valid: sqlplus <apps username> @$AD_TOP/sql/ADZDEXRPT.sql Note: Enter the apps password when prompted. Save the output as pre_dbprep for future reference, such as: mv adzdexrpt.txt adzdexrpt_pre_dbprep.txt 95

Fix Violations Fix Violations Listed in the Online Patching Readiness Report ADZDPMAN.sql that Require Manual Intervention Oracle recommends that you perform the chosen fix by customizing template file AD_TOP/sql/ADZDPCUST.sql Verify database tablespace free space The Edition-Based Redefinition feature of Oracle Database 11gR2 requires additional space for the dictionary tables that are used to manage editioned objects. 1. Initialize the Run File System environment: source <RUN APPL_TOP>/<Instance ID>_<hostname>.env 96

Fix Violations - Examples exec fnd_oracle_user_pkg.load_row('bi_admin', 'CUSTOM', 'INVALID', NULL, 'N', 'B'); exec fnd_oracle_user_pkg.load_row('clr', 'CUSTOM', 'INVALID', NULL, 'N', 'B'); exec fnd_oracle_user_pkg.load_row('datamgt', 'CUSTOM', 'INVALID', NULL, 'N', 'B'); exec fnd_oracle_user_pkg.load_row('dw_etl', 'CUSTOM', 'INVALID', NULL, 'N', 'B'); 97

If the report contains 'Not Executed' and 'Failed Execution' items, then report these failures to Oracle Support. You will be asked to provide the output from the report, the patch log and all worker logs, and the online patching enablement status report output. If there is any worker failure during the Online Enablement patch, you should not ignore or skip the failed error. The issue should be addressed before restarting the worker. Ignoring or skipping the error can cause database corruption. 98

Apply the R12.2 ONLINE ENABLEMENT PATCH13543062:R12.AD.C This is a long running patch, tuning this patch can reduce downtime. Use Autopatch in hotpatch mode to apply the patch (adpatch options=hotpatch,forceapply). Monitor its progress at any time by running the DDL Status Report (ADZDSHOWDDLS.sql) as follows: sqlplus <apps Username> @$AD_TOP/sql/ADZDSHOWDDLS.sql After the patch finishes, compile invalid objects. 99

100 AD TXK PATCHES & 12.2.4 UPGRADE

101 Apply Patch 20642039 The latest AD-TXK codelevel has a dependency on Oracle Fusion Middleware Patch 20642039. Note: The latest AD-TXK codelevel has a dependency on Oracle Fusion Middleware: 11.1.1.6: Patch 20642039 11.1.1.7: Patch 20756887 If you are applying Delta 6 to a system on a pre-delta 5 AD-TXK codelevel, you must apply the Oracle Fusion Middleware patch before proceeding with the AD and TXK patches. If you do not apply this patch, application of the TXK patch will fail.

102 AD / TXK RUP6 R12.2 AD / TXK RUPs (most recent R12.AD.C.delta.6 / R12.TXK.C.delta.6) Can ONLY be applied after upgrade to R12.2.0 Expect more frequent updates of 12.2 Technology Stack (TXK) and Applications DBA (AD) suite of administrative tools It is strongly recommended to apply the latest AD/TXK RUPs. Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1

103 E-Business Suite AD and TXK RUP6 Information, Release 12.2 (Doc ID 1617461.1) Upgrade and New Installation Customers following Path A of this document must apply Application tier technology patches to the run file system. Refer to My Oracle Support Knowledge Document 1355068.1, Oracle E-Business Suite 12.2 Patching Technology Components Guide for instructions on how to apply technology patches. Path A involves hot patching where patches are applied directly to the run file system. Unless indicated in this document, you should not invoke any adop actions (for example, finalize, cutover, cleanup, fs_clone). These adop actions should be executed in later steps as mentioned in this document.

104 E-Business Suite AD and TXK RUP6 Information, Release 12.2 (Doc ID 1617461.1) Start up only the Weblogic AdminServer service on the run file system. $ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start You should not invoke any adop actions (for example, finalize, cutover, cleanup, fs_clone).

105 E-Business Suite AD and TXK RUP6 Information, Release 12.2 (Doc ID 1617461.1) Unzip patches and run adgrants. The latest RUPs are R12.AD.C.Delta.6 (Patch 19197270) and R12.TXK.C.Delta.6 (Patch 19330775). Follow the instructions in the patch readme of Patch 19197270 to execute adgrants.

106 E-Business Suite AD and TXK RUP6 Information, Release 12.2 (Doc ID 1617461.1) adop phase=apply patches=19197270 hotpatch=yes adop phase=apply patches=19330775,20677045,20864702 hotpatch=yes merge=yes

107 Run ETCC Review My Oracle Knowledge Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes, and apply all relevant patches for your database version. This document also describes the use of the EBS Technology Codelevel Checker (ETCC) to check all required database patches, and provide essential infrastructure for applying the Delta 6 RUPs. ETCC is available via Patch 17537119, and run with the command checkdbpatch.sh (UNIX) Note: When you run ETCC, ensure that the database is open. Otherwise, future patching cycles may fail.

108 Apply two 12.2 patches before the 12.2.4 Upgrade, if using 12cR1 However, for 12.2.0 environments, these patches are needed for the upgrade from 12.2.0 to 12.2.2 (or a later version) to work. Patch 8796558 Patch 19343134 Interoperability Notes EBS Release 12.2 with Database 12cR1 (12.1.0.1) (Doc ID 1959604.1)

109 Downtime Mode Since R12.AD.C.Delta.6 downtime mode can be used, This does not have an online patching cycle and is quicker R12.2 patches are not normally tested in downtime mode. It is only supported where explicitly documented or when directed by Oracle Support or Development (e.g. 12.2.4 RUPs)

R12.2.4 R12.2.4 (most recent recommended RUP) EBS R12.2.4 (17919161 ) RUP was released in Sept 2014 (MOS ID 1617458.1) Suite wide and family level granularity unlike 12.2.3/12.2.2 Apply R12.2.4 RUP using downtime mode adop phase=apply apply_mode=downtime 110

Post 12.2 Upgrade Steps Online Help Patch 17919162 12.2.4 Online Help Patch 17919162 merged with Patch 19290141 using adop hotpatch mode on the run file system. $ adop phase=apply patches=17919162,19290141 hotpatch=yes 111

Post Upgrade Steps from Doc ID 1586214.1 R12.2.4 After you have completed the steps to update all database tier nodes with the latest code level, perform the following post-update steps only if you have licensed this product: HR Legislative customers only: refer to the step "Latest legislation data update (Hrglobal installation)" from the readme of the patch "Oracle E-Business Suite Release 12.2.4 Patch 17020683. Endeca: 12.2 V4 Document 1574273.1 Perform NLS-related Step (conditional) Run the Patch Wizard for current recommended and high priority product patches, Document 1400757.1. 112

Questions? Thanks for attending! Email me to receive the latest copy of this presentation: mswing@trutek.com Visit www.trutek.com and blog.trutek.com for the latest whitepapers, books, training, consulting, R12 upgrade information, and free downloadable books 113