adop and maintenance task presentation 151015

Best Practices For Patching and Maintaining Oracle E-Business Suite

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

Andreas Sandhi Kuncoro Technical Consultant Support Engineers

Date: 15th October 2015

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

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 purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

3


Agenda

• Hands on EBS Maintenance Procedure• How to find EBS & EBS Technology Stack Patches on My

Oracle Support12.2.4 RPCsEBS Patch Wizard EBS Patch AdvisorApplication Management Pack (AMP) an EBS Plug Ins

5


Hands on / Preventive Maintenance CheckUp

• Standard Procedure on EBS Startup Database, Application and Shutdown Application and Database

• Check Log Usage on EBS

• Add Tablespace on EBS

6


Standard Procedure StartUp / Shutdown Application Server

# su – oraprod

$ . /u01/PROD/<SID_Hostname).env – Set Apps Env.

$ cd $ADMIN_SCRIPT_HOME

$ ./adstrall apps/apps or $ ./adstpall apps/apps

7


Standard Procedure StartUp / Shutdown Database Server

# su – oraprod

$ . /u01/../11.2.0/<SID_Hostname).env – Set DB Env.

$ sqlplus / as sysdba

SQL> startup or SQL> shutdown immediate

SQL> exit

$ lsnrctl start <SID> or $ lsnrctl stop <SID>

8


Preventive Maintenance on Database Server

• Clear log of Database (*.trc, *.trm) from log location : SQL> show parameter back;

• Check alert log (alert_<SID>.log)

• Check workflow_analyzer.sql

• Check addmrpt.txt

• Check awrrpt.html

• Check Tablespace

9


Preventive Maintenance on Application Server• Check Log Size Usage

Forms dump files : $INST_TOP/logs/ora/10.1.2/forms

Reports Cache : $INST_TOP/logs/ora/10.1.2/reports/cache

Apache logs : $INST_TOP/logs/ora/10.1.3/Apache

OPMN Logs : $INST_TOP/logs/ora/10.1.3/opmn

Service Management : $INST_TOP/logs/appl/admin/log

Concurrent Manager logs : $INST_TOP/logs/appl/conc/log

Concurrent Manager out files : $INST_TOP/logs/appl/conc/out10


12.2 Online Patching Best Practices• 12.1 patching

• The online patching cycle

• Upgrade / Install

• AD and TXK Code levels

• Technology Patches

• Patching Modes

• Tips and Tricks

• Information Resources

28


The Online Patching Cycle

30

• adop – AD Online Patching, utility to apply patches to EBS

• 12.2 patching is online. EBS is available while most of the patching operations are performed

• Application is only offline during the Cutover phase

• See technical planning guide, maintenance guide and concepts guide.

CleanupFinalizeApply

• Create patch edition in the database

• Sync run to patch file system.

• ADZDPATCH• Cleanup

Prepare

Users Online

Users Online

Users Offline

• Apply one or more patches to the patch edition/fs

• Adop tool is used

• Ready the system for cutover.

• Compile invalid objects

• Run by cutover if not explicitly run

Users offline

Users online

• Cutover to patch edition of the database & fs

• Run finalize if not already run

• Shutdown and start services

• Cleanup old editions and objects to recover space

Dual file system (run/patch)

Abort


The Online Patching Cycle

31


$ adop -status -detail

$ adop phase=cleanup cleanup_mode=full

$ adop phase=apply patches=<patch_id> hotpatch=yes

$ adop phase=fs_clone

$sqlplus apps/<passwd>

SQL> set markup html on spool adop_sessions_<cust_name>.html set timing on set linesize 120 set pagesize 300 show user select release_name from FND_PRODUCT_GROUPS; select * from FND_NODES; select * from FND_OAM_CONTEXT_FILES; select * from AD_ADOP_SESSIONS; select * from AD_ADOP_SESSION_PATCHES; select * from AD_APPL_TOPS; select codelevel FROM AD_TRACKABLE_ENTITIES where abbreviation in ('txk','ad');set timing off set markup html off spool off

ADOP Best Practice

32


Identifying Missing appTier and dbTier Patches for EBS 12.2

• EBS Technology Codelevel Checker (ETCC)– checkDBpatch.sh (Database EBS Technology Codelevel Checker – DB-ETCC)– CheckMTpatch.sh (Middle Tier EBS Technology Codelevel Checker – MT-ETCC)

– Always use the latest version of ETCC

33


Always Apply Latest Technology Patch• 18274429 1-Off R12.AD.C.Delta.4: script to fix ldt invalidation issue during main divisional upgrade

(Patch)• 20927952 Fix for Bug 20927952 (Patch)• 19371817 Fix for Bug 19371817 (Patch)• 21111894 Fix for Bug 21111894 (Patch)• 20486861 Fix for Bug 20486861 (Patch)• 20083253 Fix for Bug 20083253 (Patch)• 21360713 Fix for Bug 21360713 (Patch)• 20953338 ORACLE APPLICATIONS RELEASE 12.2: CPU PATCH FOR JUL 2015 (Patch)• 20311216 CHECKEDTOUNCHECKEDEXCEPTION: RESULT SET ALREADY CLOSED WHEN BOOKING SO

(Patch)

34


12.2 Patching Best PracticesUptake the latest AD and TXK Code Levels

•Currently AD and TXK Delta 6: Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 Note 1617461.1. Check for additional critical patches! Check for known issues and understand new features

•Follow the correct path. Path A or B for release update packs (AD/TXK/EBS)

•Do not start patching/cloning/integrations etc.. until your system is on the latest AD and TXK code levels.

•Apply latest EBS Release Update Pack: Oracle E-Business Suite Release 12.2.4 Readme Note 1617458.1

37


12.2 Patching Best PracticesApplying Applications Technology Patches and Database Patches

•These patches are required to be applied before moving to latest AD and TXK code levels. Try and apply any newly recommended patches to maintain system stability.

•Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes Note 1594274.1

•Use the EBS Technology Codelevel Checker (ETCC) (patch 17537119) to check database patch levels. Warns of essential missing database bug fixes. Must be done for upgrade and new installation customers before upgrade and/or before AD and TXK patching. Patches to be applied will depend on startCD used for fresh install customers. Shows bug fixes to be applied, not patches.

38


12.2 Patching Best PracticesApplying Applications Technology Patches and Database Patches cont..

•Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite Note 1147107.1 resource for database patch conflicts

•How to Use the My Oracle Support Conflict Checker Tool [Video] (Doc ID 1091294.1)

•Use the txk inventory report to generate a list of applied middle tier patches. $ADPERLPRG $FND_TOP/patch/115/bin/TXKScript.pl -script=$FND_TOP/patch/115/bin/txkInventory.pl -txktop=$APPLTMP -outfile=$APPLTMP/Report_Inventory.html

•Oracle E-Business Suite 12.2 Patching Technology Components Guide (Doc ID 1355068.1)

39


12.2 Patching Best PracticesUnderstand The Available Patching Modes

• Online mode: Default mode. Involves a patching cycle which is initiated with a prepare phase. Changes made available only after cutover. Patch is abortable

• Hotpatch mode: Patch is applied directly to the run file system when services are running. No patch cycle is required. Patch is not abortable. Patches can only be applied in hotpatch mode when instructed in the readme

• Downtime mode: Introduced in AD.C.Delta.5. Patch is applied directly to the run file system when services are down. Patch is not abortable. Only supported for production use where explicitly documented, or when directed by Oracle Support or Development. Before system scale up, single node dev or test environment where high availability and prod support is not required

40

https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1617461.1

https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1617458.1


12.2 Patching Best PracticesTips and Tricks

• adop is always executed from the run file system

• adop logs can be found in fs_ne file system $ADOP_LOG_HOME

• Apply multiple patches in one cycle

• Can run multiple phases automatically adop phase=prepare,apply patches=XXX, finalize

• Keep patches in $PATCH_TOP directory until the next prepare phase is complete

• In a non-shared multi- node system, patches must be downloaded to all nodes

41


12.2 Patching Best PracticesTips and Tricks

• To improve apply phase completion times set workers to maximum number that your system will support; Utilize distributed AD remote worker invocation when running multiple application tiers to utilize resources on other application tiers. Requires shared FS.

• Reduce cutover by: running explicit finalize, shutting down managers before running cutover

• Run adscanlog utility to quickly collect adop failure information from log files: adopscanlog; adopscanlog -session_id=<number>; adopscanlog –help

• Run the adop diagnostic script to collect logs, configuration and other information to diagnose issues with adop and other AD/TXK utilities. Upload results to support. Note 1901242.1

42


Q&A


Appendix


EBS Patching Documents

• E-Business Suite and EBS Technology Stack Patches – Doc 1633974.2

• EBS Patch Wizard – Doc 976188.1

• EBS R12.1.3+ Recommended Patch Collection 1 (RPC1) – Doc 1638535.1

• Patching Advisor (11i - 12.1) – Doc 313.1

• Patching Advisor (R12.2) – Doc 1590494.1

• Oracle AMP for EBS Plug-In – Doc 1532970.1

47


Safe Harbor Statement

The preceding 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.

52