Online Patching With Oracle E-Business Suite 12.2

Online Patching
with Oracle E-Business Suite 12.2

Kevin Hudson
Senior Director
Applications Technology Group, Oracle E-Business Suite Development
October 27, 2015
Oracle Confidential Internal/Restricted/Highly

Copyright 2014, Oracle and/or its affiliates. All rights reserved. |
Restricted
Program Agenda: Patching with E-Business Suite
12.2
1
Solution Approach
2
Overview of 12.2 Patching Architecture
3
Patching EBS 12.2 with Online Patching
4
Online Patching Cycle Special Operations
5
Patching Applications Tier with Online Patching
Copyright 2014, Oracle and/or its affiliates. All rights reserved. | 3

What if the Following were True During Patching
Critical business operations were not interrupted by maintenance operations
Revenue generating activities were to stay online
Web Orders
Booking Orders
Service Requests
Business users were to stay online
Pay Suppliers
Pay Employees
Uninterrupted manufacturing operations
Downtime required by any patch was predictable
Measured in minutes not days or hours
Global Single Instances remained operational 24*7
Maintenance window easier to allocate as shorter time required
Online Patching
E-Business Suite Remains Online During Patching
In 12.2 all patching operations are online

EBS will remain available to users during patching operations
Different lines of Business are no longer affected by
patching
Run Financials while applying an HR legislative updates
Run Manufacturing while applying Financials updates

Oracle E-Business Suite 12.2 Architecture
Application Database
Online patching uses the

latest features of the
technology stack
Edition-Based Redefinition WebLogic Server
Global Single
(EBR) Data Model
WebLogic JSP
Web Logic Server
Web Listener
JDBC/SQL Net
BC4J
RAC & ASM
UIX 11g
Edition-Based
BI Publisher
Redefinition
Forms

Patches are Applied to a Copy of Production
Production Copy of
Production
E-Business Suite Patches

E-Business Suite
12.2.3 - 12.2.4
12.2.3
- 12.2.5
-
Copy the production code

Apply patches to the copy

Copy the Code, NOT the Data
EBS uses both the file system and the database to store the
code and data that make up the application
Code
Stored both on the File system & In the Database
Any code object changed in a patch is copied
Data
Stored both on the File system & In the Database
Application data is NOT copied by a patch

Downtime Redefined as Cutover
Changing the Unit of Measure for Downtime
Cutover is the time taken to switch users from the

production system to the newly patched copy
Cutover changes the unit of measure for downtime
Measured in minutes NOT hours or days
Cutover time is very predictable
The time taken to bounce the Middle Tiers

Downtime Limited to Short Cutover
Production Patched Production
E-Business Suite
12.2.3
E-Business Suite Patches

12.2.3 12.2.4
12.2.5
.
Users are logged off the production Instance

When users reconnect they are directed to the newly patched system

Changing the Patching Paradigm
Downtime Patches Online Patches
No online users User remain online
Wall clock time very Wall clock time is no longer

important an overriding concern
Consumes all resources Online users share resources
Upgrade designed to run as Data upgrades designed to not

fast as possible affect the running application

Patching Occurs on a Copy
File system Patching

All patches are applied to a secondary file system
Synchronization of the file systems is managed by the
patching tools
Database Patching
A separate copy is maintained of all database code objects
that are changed by a patch
Utilizes Edition-Based Redefinition feature of the Database

Online Patching - High level
Architecture

12.2 Architecture
Dual File System and Edition-Based Redefinition
Run File System Edition-Based Patch File System

Oracle HTTP Server Redefinition
RunPatch
Edition
Edition Oracle HTTP Server
(OHS) (OHS)
WebLogic Server WebLogic Server
(WLS) (WLS)
Developer 10.1.2 Developer 10.1.2
APPL_TOP APPL_TOP
Synchronization Managed
COMMON_TOP Automatically COMMON_TOP
INST_TOP Non-Editioned File INST_TOP

System
APPL_TOP_NE
PATCH_TOP
LOGS

File System Editioning

Online Patching uses
Patchafile
Dual File System
system
Used by patching tools
Run file system Stores a complete Non-Editioned file
Used by online users copy of all system
Applications and
Stores a complete Used for data files
Middle Tier code
copy of all e.g.: data import/export
Applications and Logically mapped to files, log files, report
Middle Tier code either fs1 or fs2 output files
Logically mapped to Only stores data files
either
fs1 andfs1 orswitch
fs2 fs2 Run and Patch designation during the cutover phase of an
Online Patching cycle
Run Patch
Cutover
fs1 fs2 fs1 fs2
fs1

12.2 E-Business Suite File System Layout
File System Laid Down after 12.2 Rapid Install
Install base
File System File System

New file to choose the
1 fs1 fs2
2
environment to set:
EBSapps.env RUN|PATCH
fs1 fs2 fs_ne EBSapps.env
EBSapps FMW_HOME inst EBSapps FMW_HOME inst
10.1.2 appl comn 10.1.2 appl comn
ad ar gl ad ar gl

Non-Editioned File System
Stores external data files

Human readable
Have a structure that is mostly independent of the application code level
Not directly patched by EBS Development and they should not be editioned
Examples
Concurrent report output
Log files
Data import/export files
SSL certificates
File-based system integration
Patch downloads
Install base

fs1 fs2 fs_ne Subdirectories
New file to choose the sparsely
environment to populated
set:
EBSapps.env RUN|PATCH
Only created as needed
fs1 fs2 fs_ne EBSapps.env
EBSapps inst
appl patch log
adop

R12.2 Environment Overview
Working with the 12.2 Environment
New script to setup the environment: EBSapps.env

RUN | PATCH
New environment variables for R12.2 to help you navigate
the system
$FILE_EDITION - Current fs edition type sourced, values: run or patch
$RUN_BASE - RUN file system base directory
$PATCH_BASE - PATCH file system base directory
$NE_BASE - Non-edition file system base directory
$APPL_TOP_NE - Application top that stores product files considered data
$PATCH_TOP Directory where the patch files are unzipped
On a multi-node system with non-shared file systems, you must copy the
patch files to each separate $PATCH_TOP directory, so that the patch files are
available from the same location
Copyright on all and/or
2014, Oracle nodes
its affiliates. All rights reserved. |
R12.2 Environment Overview
Setting the 12.2 Environment
Source the Run
environment
$ source EBSapps.env RUN
E-Business Suite Environment Information
----------------------------------------
RUN File System : /scratch/orauser/im4kevin/fs2/EBSapps/appl Note: fs2 is the RUN file system
PATCH File System : /scratch/orauser/im4kevin/fs1/EBSapps/appl
Non-Editioned File System : /scratch/orauser/im4kevin/fs_ne
DB Host: rws3270749.us.oracle.com Service/SID: im4kevin
Sourcing the RUN File System ...
Echo environment variables

$ echo $FILE_EDITION : run Note: RUN file system is sourced
$ echo $RUN_BASE : /scratch/orauser/im4kevin/fs2 Note: fs2 is the RUN file system
$ echo $PATCH_BASE : /scratch/orauser/im4kevin/fs1
$ echo $NE_BASE : /scratch/orauser/im4kevin/fs_ne
$ echo $APPL_TOP_NE : /scratch/orauser/im4kevin/fs_ne/EBSapps/appl
$ echo $PATCH_TOP : /scratch/orauser/im4kevin/fs_ne/EBSapps/patch

Working with the 12.2 Environment
Source the Run environment
$ source EBSapps.env RUN
E-Business Suite Environment Information
Install base
----------------------------------------
RUN File System : /scratch/orauser/im4kevin/fs2/EBSapps/appl
PATCH File System : /scratch/orauser/im4kevin/fs1/EBSapps/appl
Non-Editioned File System : /scratch/orauser/im4kevin/fs_ne
DB Host: rws3270749.us.oracle.com Service/SID: im4kevin
Sourcing the RUN File System ...
Echo environment variables

$ echo $FILE_EDITION : run
$ echo $RUN_BASE : /scratch/orauser/im4kevin/fs2 fs1 fs2 fs_ne

$PATCH_BASE $RUN_BASE $NE_BASE
$ echo $PATCH_BASE : /scratch/orauser/im4kevin/fs1
$ echo $NE_BASE : /scratch/orauser/im4kevin/fs_ne
$ echo $APPL_TOP_NE : /scratch/orauser/im4kevin/fs_ne/EBSapps/appl
$ echo $PATCH_TOP : /scratch/orauser/im4kevin/fs_ne/EBSapps/patch
EBSapps inst
appl patch log

$APPL_TOP_NE $PATCH_TOP
adop

File Systems Patching Cycle
1
Prepare Two complete file systems are always
present
un Run Edition - Used by the running
Patch
Patch Application
dition
Cutover
2 Patch Edition - Either:
File
Edition
Edition
1 Currently being patched
Cutover
or
tch
Waiting for the next patching cycle
The two files systems are rotated between
Patch
Run
System Run and Patch during every patch cycle
ition
Prepare 2
Edition
Edition Copyright 2014, Oracle and/or its affiliates. All rights reserved. |
Database Edition-Based Redefinition

11gR2 Edition-Based Redefinition (EBR)
Key enabling technology for Online Patching

Enables the online upgrade of the application definition
Allows an application to efficiently store multiple copies of its code
and schema in the same database
Provides an isolation mechanism that allows pre-upgrade
and post-upgrade schemas to co-exist
Changes to database objects are made in the isolation of an
Edition
Changes to database objects do not affect the running application

Online Patching is Enabled by 11gR2 Edition-
Based Redefinition
Multiple Copies of Database Code Objects Can Coexist
Client code connects to an edition Business Users

DBA
of the database
Run Edition
OldOld Edition RunPatch
Edition
Old
Edition Edition
Edition
Used by online users
Never changed by a patch
Patch Edition
Used by patching tools
Changes do not affect the running application
Patch Edition becomes the
Run Edition at Cutover
12.2 Online Patching Cycle

Online Patching Cycle Orchestration
Formalized Patching Cycle
New utility to orchestrate the Online Patching cycle
adop replaces adpatch as the 12.2 patching tool
Supports single and multi-node environments
Dual file systems are synchronized automatically
Database Editions are managed automatically
Users remain online during patching
Patching CANNOT affect the running application
Data model changes (tables, indexes)
Code changes ( pl/sql, views, c code, java code)
Running application CANNOT affect the patch
Understanding the Online Patching Cycle
Online Patching is used to apply all patches in 12.2

Online Patching cycle includes 5 major phases
New patching tool adop orchestrates the patching
cycle
Oracle Confidential Internal/Restricted/Highly
Restricted
Online Patching Cycle - Overview
The Basics
Prepare Apply Finalize Cutover Cleanup
Copy the Apply one or Compile Restart Remove

production more patches invalid application on obsolete
application to the Patch Objects Patch Edition objects
code Edition Wait for a
Create a new good
Patch Edition downtime
in the window
database
Users Online Users Offline Users
Online
Online Patching is used to apply all patches
in 12.2
Online Patching cycle includes 5 major
phases Copyright 2014, Oracle and/or its affiliates. All rights reserved. |
Online Patching Cycle Prepare Phase
The Basics
Prepare
Copy the
production
application
code
Create a new
Patch Edition
in the
database
Online
Synchronizes Patch Edition and Run Edition on the
file system
Create a new Patch Edition in the database

Preparing the File System
Patch Edition & Run Edition of the

file systems are synchronized
un Prepare All files on the Patch Edition are an

exact copy of the files on the Run
Patch
dition
Edition
Efficient synchronization
Incremental synchronization is the
Edition
default
Only files changed in the last patch
File application are copied

Full synchronization available if
necessary
Preparing the Database
Patch Edition is created in the

database
un Prepare
All code objects in the Patch Edition
begin as pointers to code objects in
the Run Edition
ditionPatch Efficient use of space

Objects are only Actualized into
the Patch Edition when a new
Edition Database copied

revision of the code is applied
Storage objects such as tables are not
New patching standards are

followed for upgrading storage
objects
What Preparing
ADOP controls to Know the What to Do
system for patching Execute prepare on the primary
Validates system configuration to node
ensure that the system is ready to $ adop phase=prepare
start an Online Patching cycle.
Prepare is run on all nodes in a
muti-node configuration
Synchronizes the Run and Patch
File System
Creates the Database Patch
Edition Copyright 2014, Oracle and/or its affiliates. All rights reserved. | 34
Online Patching Cycle - Apply
Copy the Apply one or

production more
application patches to
code the Patch
Create a new Edition
Patch Edition
in the
database
Users Users Users
Online Offline Online
Execute patch drivers to update Patch Edition

Multiple patches can be applied, including customizations

Online Patching Cycle - Apply
Applying Patches
Patches are applied to the
copy (Patch Edition)
n Prepare The production application is

unaffected by the changes
Patch
tion
Patch Driver
File Driver
Users are connected to the
Application and can perform
their work unaffected by the
File
Edition patch
n Prepare
Database Changes are made in the
System
isolation of an Edition
Patch
Driver
The running application is
tion unaffected by these
Edition
Database changes
Online Patching Cycle Apply Phase
What to Know What to Do

ADOP controls application of Execute adop apply on the primary
patches to the file system and node
database $ adop phase=apply patches=12345
$ adop phase=apply patches=1234,5678,9876
Mutiple patches can be applied in $ adop phase=apply patches=1234,5678 workers=4
the same patching cycle $ adop input_file=October2015.txt
Supports all options previous October2015.txt
supported by adpatch phase=prepare,apply,finalize

patches=1234,5678,9876
Supports fully automated workers=4
execution via inputs files

Online Patching Cycle - Finalize
Copy the Apply one or

Compile
production more patches
invalid
application to the Patch
Objects
code Edition
Wait for a
Create a new good
in the window
database
Users Users Users
Compile invalid objects
Generate derived objects
Wait for a good downtime window

Online Patching Cycle - Finalize

Performs any remaining processing that Execute adop finalize on the
is needed to ensure the system is ready primary node
for the fastest possible cutover $ adop phase=finalize
Object compilation $ adop phase=finalize finalize_mode=quick
Environment can pause at this stage for as $ adop phase=finalize finalize_mode=full
long as required
Default finalize_mode is quick
Full mode computes statistics on key data
dictionary tables for improved performance

Online Patching Cycle - Cutover

Copy the Apply one or Compile Restart
production more patches invalid application on
application to the Patch Objects Patch Edition
Create a new good
in the window
database
Users Users Users
Stop middle-tier services
Cutover to the Patch Edition of the file system
Cutover to the Patch Edition of the database
Restart middle-tier services
During cutover a brief downtime is taken

Middle tier services are stopped and users are logged off the system
The Patch file system is promoted to be the Run file system
The Patch database edition is promoted to be the Run database edition
Perform final maintenance operations
Middle tier services are restarted
Users are brought back online on the patched system
The database does NOT need to be and should not be bounced
during cutover

Cutover Automatically Manages all Services on all Nodes
Old
Middle-tier processes
Old
Old
Run
stopped
Manages all nodes in the configuration
Patch
FS - Editions
via remote execution
Edition
Edition
End Users are disconnected
1
Run
Edition
Edition
Running
File system roles swapped
Patched (FS-2) promoted to Run
Databas
Application FS-1 available for next patching cycle
FS -
Database Patch Edition
promoted to Run Edition
e Middle-tier processes
Patch
2
restarted
Manages all nodes in the configuration
via remote execution
Users reconnect
What to
Cutover represents Know
the official downtime for
What to do
an EBS patch Execute adop cutover on the primary node
Application tier services are automatically shut $ adop phase=cutover
down and restarted on all nodes
You must ensure that no users remain on the

system during cutover
Any third-party processes connected to the old
run edition of the database should be shut down,
otherwise they will be terminated automatically
Cutover will take longer if it has to wait for

long-running concurrent processes to
complete
You can terminate the internal concurrent
manager by executing the adcmctl.sh abort
command
Deferring Application Tier Restart
What to Know What to do
In some cases, you may need to Execute adop cutover on the
perform additional manual steps primary node without starting the
after cutover but before restarting application services
the application tier services $ adop phase=cutover mtrestart=no
Apply customizations Perform manual steps
Patch the database tier
Start application tier services
You must start the application tier manually
services manually after performing $ source EBSapps.env run
additional steps $ adstrtal.sh mode=allnodes

Online Patching Cycle - Cleanup
Apply Finalize
Cleanu
Prepare Cutover
p
Create a new good
in the window
Database
Users Users Users
Cleanup old editions to recover space

Cleanup occurs after the users have been brought back online

Cleanup occurs after users have been

brought back online to the newly patched
atch Application
Patch
Run
File system
dition
The pre-patch file system is now ready for the
next patching cycle
File
Edition
Edition
Re-synchronized
Old
Database
Code objects patched in the latest patching
System
Run cycle are deleted from Old Editions
Edition Once all objects are deleted from an Old Edition

it is also deleted
Edition Copyright 2014, Oracle and/or its affiliates. All rights reserved. |
Users are online during the cleanup What to do
What to Know
process
Execute adop cutover on the primary
Removes obsolete objects from the
node
system to recover space
$ adop phase=cleanup
If you fail to run the cleanup phase $ adop phase=cleanup cleanup_mode=quick
explicitly, it will be run automatically on $ adop phase=cleanup cleanup_mode=full
the next prepare cycle
This will cause a delay in starting your next online
patching cycle
Three cleanup_modes are available

quick - Performs only essential cleanup tasks
standard (default) - Removes obsolete code
objects
full - Performs maximum cleanup, which drops
all obsolete code and data from earlier editions
Online Patching Cycle - Overview
The Basics

Create a new good
in the window
database
Online
Online Patching is used to apply all patches in 12.2
Online Patching cycle includes 5 major phases
Application is only offline during the Cutover phase

Monitor The Online Patching Cycle
Display Status of a Single Node Online Patching Cycle
$ adop -status
Node Name Node Type Phase Status Started Finished Elapsed
------------- ---------- -------- --------- ------------------------------ ------------------------------ ------------
ebsnode01 Primary PREPARE COMPLETED 11-APR-15 04:10:19 -07:00 11-APR-15 04:13:55 -07:00 0:03:39
APPLY COMPLETED 11-APR-15 04:15:00 -07:00 11-APR-15 04:26:01 -07:00 0:11:01
FINALIZE COMPLETED 11-APR-15 04:27:02 -07:00 11-APR-15 04:28:40 -07:00 0:01:38
CUTOVER COMPLETED 11-APR-15 04:28:26 -07:00 11-APR-15 04:38:05 -07:00 0:09:39
CLEANUP COMPLETED 11-APR-15 04:45:02 -07:00 11-APR-15 04:46:11 -07:00 0:01:09

Online Patching Cycle Multi-Node
Completely automated in multi-node deployments through

adop
No distinction between environments that are:
Shared file system configuration
Non shared file system configuration
Primary node takes control of the patching cycle
Performed by remote command invocations across nodes
Remote command invocation setup required

Always Execute adop on the Primary Node
Primar Primar Seconda Secondary

y y ry Node
Node Node Node
Application Application
adop Tier adop Tier
Database
Tier Database
Tier
Single Application Tier Multiple Application Tier

Node Nodes

In a multi-node deployment, adop
commands are only executed from On the primary node
the primary node. $ adop phase=prepare
The primary adop node uses $ adop phase=apply patches=12345
remote execution to automatically $ adop phase=finalize
perform required actions on any $ adop phase=cutover
secondary node $ adop phase=cleanup
Remote command invocations
from the primary node to all
secondary nodes must be
enabled.
Muti-Node Configuration Automatically
Managed
Display Status of a Multi-Node Online Patching Cycle
$ adop -status
Current Patching Session ID: 75
Node Name Node Type Phase Status Started Finished Elapsed

--------------- --------------- --------------- --------------- ------------------------------ ------------------------------ ---------
ebsapi01d Primary PREPARE COMPLETED 14-NOV-14 09:59:33 -05:00 14-NOV-14 10:14:11 -05:00 0:14:38
APPLY NOT STARTED
FINALIZE NOT STARTED
CUTOVER NOT STARTED
CLEANUP NOT STARTED
ebsape01d Secondary PREPARE COMPLETED 14-NOV-14 09:59:45 -05:00 14-NOV-14 10:13:18 -05:00 0:13:33
APPLY NOT STARTED
CUTOVER NOT STARTED
CLEANUP NOT STARTED
ebsape02d Secondary PREPARE COMPLETED 14-NOV-14 09:59:38 -05:00 14-NOV-14 10:16:32 -05:00 0:16:54
APPLY NOT STARTED
CUTOVER NOT STARTED
CLEANUP NOT STARTED
File System Synchronization Used in this Patching Cycle: Full

Online Patching Cycle Special
Operations

Online Patching Cycle - fs_clone
Re-Cloning the Patch Edition File System
Patch file system is normally incrementally What to Do
What to Know
synchronized with the run edition file system during
prepare Execute re-clone on the primary node
In some special cases a full re-clone is required $ adop phase=fs_clone
when
The previous Online Patching cycle was aborted
Manual changes were made to the run edition file
system
Middle-tier technology components were patched
A full re-clone is recommended
After applying a large EBS RUP
Re-cloning the patch edition file system
Ensures that the files systems are correctly
synchronized
Minimizes any synchronization delay that would
normally occur on the next prepare
Cannot be executed when there is an active Online
Patching cycle Copyright 2014, Oracle and/or its affiliates. All rights reserved. | 55
Online Patching Cycle - Abort
The Online Patching Cycle can be aborted at any
time prior to Cutover
rt
o
Ab

Online Patching Cycle - Abort
Useful when an Online Patching cycle
encounters problems that cannot be fixed
immediately
Returns the system to normal runtime Execute adop abort on the primary node
operation $ adop phase=abort
Online Patching cycle cannot be aborted $ adop phase=cleanup cleanup_mode=full
after cutover $ adop phase=fs_clone
Requires a full cleanup and fs_clone

before the next patching cycle to remove
the effects of the failed cycle
If a full cleanup & fs_clone are not run
explicitly, they will be run automatically
by the next prepare
This will cause a delay during the prepare phase
of the next online patching cycle
Online Patching Cycle actualize_all
Full Cleanup as a Periodic Maintenance Operation
As each Online Patching cycle is
completed, the database will accumulate Execute adop on the primary node to
an additional old database edition. actualize all objects and perform a full
cleanup
When the number of database editions
reaches 25 or more, you should consider $ adop phase=prepare
running a special maintenance operation $ adop phase=actualize_all
to remove old database editions $ adop phase=finalize finalize_mode=full
Actualize all is a special adop phase that $ adop phase=cutover

ensures every database object has a $ adop phase=cleanup cleanup_mode=full
version in the PATCH edition
This allows all copies in OLD editions to be
removed by full cleanup

Online Patching Cycle - Actualize All
Full Cleanup Combined with a Scheduled Online Patching Cycle
Execute adop on the primary node to
actualize all objects and perform a full
The actualize all and full cleanup can also
cleanup
be executed in conjunction with an Online
$ adop phase=prepare
Patching cycle
$ adop phase=apply patches=12345,67890
This maintenance operations will take
$ adop phase=actualize_all
much longer than a typical Online
$ adop phase=finalize
Patching cycle and should only be finalize_mode=full
performed when there is no immediate
$ adop phase=cutover
need to start or complete a patching
$ adop phase=cleanup cleanup_mode=full
cycle

Single File System and Downtime Patching
Mode
Designed for Development Instances Only
Designed for building & testing custom code
Patches should always be tested on a standard dual file system test instance
before being applied to production.
Single file system
Allows for a reduced footprint
Patch file system is not present
All patches must be applied to the RUN edition using adop apply in downtime mode
Downtime mode for adop
Applies patches directly to the RUN edition of the instance
The downtime mode should only be used on a production when directed by the patch
readme or other documentation

Single File System for Development Systems
Patches
Run Filemust be applied in
System Edition-Based Patch File System
downtime mode
Oracle HTTP Server Redefinition
Patch Edition Oracle HTTP Server
(OHS)
adop phase=apply (OHS)
WebLogic Server WebLogic Server
apply_mode=downtime
(WLS) (WLS)
patches=12345,9876
Developer 10.1.2 Developer 10.1.2
Patches are applied to:
APPL_TOP Synchronization is managed APPL_TOP
Run file system
by patching tools
RunCOMMON_TOP
Edition of the database COMMON_TOP
INST_TOP Non-Editioned File INST_TOP

System
APPL_TOP_NE
PATCH_TOP
LOGS

Applying Downtime Mode Patches on a Single
Only supported on development
File System
systems
Patches should still be applied to a
test instance
Whatusing a full Online
to Know What to do
Patching cycle
Execute apply on the development
Patches are applied to the RUN
primary node
edition of the file system and $ adop phase=apply patches=123456 apply_mode=downtime
database
Oracle does not test patches in
Downtime mode unless explicitly
stated
All application tier services must
be down before applying a patch
in Downtime mode
Patching Application Tier Technology
Stack

Applying Technology Stack Updates
Oracle E-Business Suite Release Application Tier
ApplicationWhat
tier technology
to Know stack updates What to Do
can be
Prepare the PATCH filesystem.
Applied to the PATCH file system while
EBS is online Apply technology stack patches to PATCH
filesystem.
Applied in conjunction with an EBS
Apply EBS patches (optional).
or Coordinate time for CUTOVER and complete
the online patching cycle.
Applied as a separate Online Patching
exercise Synchronize the technology stack patches
between the RUN and PATCH filesystems.
A full re-clone must be performed after
applying Application tier patches to
synchronize the RUN and PATCH file
systems
Applying Technology Stack Updates
Oracle E-Business Suite Release Application Tier
Application tier technology stack updates
can be What to Know What to Do
Applied to the PATCH filesystem while EBS is Prepare the instance for patching
online $ adop phase=prepare
Apply technology stack patches to the PATCH file
Applied in conjunction with an EBS Online
system
Patching cycle
$ source .EBSapps.env PATCH
or $ bsu.sh
$ opatch apply
Applied as a separate Online Patching
exercise Apply EBS patches (optional)
$ adop phase=apply inputfile=myinputfile
A full re-clone must be performed after
Complete the Online Patching cycle
applying Application tier patches to
$ adop phase=finalize
synchronize the RUN and PATCH file $ adop phase=cutover
systems $ adop phase=cleanup
Synchronize technology patches between the RUN

and PATCH file systems
Oracle E-Business Copyright
Suite 12.2
2014, Patching
Oracle and/or Technology
its affiliates. All rights
$ adop phase=fs_clone reserved. | Components65
Apply Online Patches with Oracle E-Business
Suite Plug-In
Oracle E-Business Suite Release Patch Manager and Online
Patching Apply patch immediately or
schedule for later
Define options for all phases of
Define and send patch activity
notifications

Apply Patches with Oracle E-Business Suite
Plug-In
Oracle E-Business Suite Release Patch Manager and Online
Patching

Online Patching - Testing
Patch Edition is not a testing environment

Application tiers cannot be run against the PATCH edition
Patches must be tested on a test instance with a complete Online
Patching cycle
Do not used downtime mode
Do not use a single file system
Consider new test scenarios
Users can be online during patch application

Online Patching Resource Considerations
Database
SYSTEM tablespace requires double its current space allocation
25GB increase to 50GB
SEED tablespace requires double its current space allocation
5GB increases to 10GB
File System
2 file systems require double the space of 1 file system
System resources consumed by a patch can be throttled
ADOP Workers
Smart worker allocation designed to share resources with online users
Oracle EBS 12.2 AD/TXK Delta 7 Now Available
Stay Current with the Latest Updates
Description MOS Doc
AD/TXK are the infrastructure ID
components that provide the Applying the Latest AD and TXK 1617461.
12.2 Release Update Packs to Oracle 1
E-Business Suite Release 12.2
Online Patching technology
Oracle E-Business Suite 2033780.
Strongly recommend that you Applications DBA and Technology 1
Stack Release Notes for
apply the latest patch collections R12.AD.C.Delta.7 and
at yourearliest convenience R12.TXK.C.Delta.7

Online Patching Delta 7 Enhancements
Enhanced adop console
messages
New Online Patching monitoring
tool
New Online Patching Improved phase execution

infrastructure validation option performance
adop -validate

Plan for Database Administrators and
Developers
Stay Current with Documentation Updates
Oracle E-Business Suite Concepts Release 12.2

Oracle E-Business Suite Maintenance Guide Release 12.2
Oracle E-Business Suite Developer's Guide Release 12.2
Oracle E-Business Suite Release 12.2 Information Center (Doc
1583110.1)
Developing and Deploying Customizations in Oracle E-Business Suite
Release 12.2
(Doc 1577661.1)
Guidance for Integrating Custom and Third-Party Products with Oracle
E-Business Suite Release 12.2 (Doc 1916149.1)
Oracle E-Business Suite Release 12.2: Online Patching FAQ (Doc
1583902.1) Copyright 2014, Oracle and/or its affiliates. All rights reserved. | 72
Online Patching Key Takeaways
Online Patching is the new patching paradigm for E-Business Suite

12.2
Online Patching is enabled by the Dual File System and 11gR2
Edition-Based Redefinition
Online Patching cycle consists of 5 major phases
Prepare, Apply, Finalize, Cutover, Cleanup
Online Patching infrastructure can be used to patch the application tier
Stay current with the latest AD/TXK patching infrastructure
Currently AD/TXK Delta 7
Stay current with documentation updates
Related Sessions
Monday, October 26, 2015
CON8140 - Planning Your Upgrade to Oracle E-Business Suite 12.2 Moscone
J. Anne Carlson, Senior Director, Product Strategy, Oracle E-Business Suite, Oracle West3022
Tuesday, October 27, 2015

CON8128 - Installation, Cloning, and Configuration of Oracle E- Moscone
12:15
Business Suite 12.2 West
p.m.
Max Arderius, Senior Principal Product Manager, Oracle 3014
CON8130 - Migrating and Managing Customizations for Oracle Moscone
5:15 p.m. E-Business Suite 12.2 West
Santiago Bastidas, Senior Principal Product Manager, Oracle 3014

Related Sessions
Wednesday, October 28, 2015
CON8127 - Oracle Enterprise Manager 12c Cloud Control for Moscone
11:00
Managing Oracle E-Business Suite 12.2 West
a.m.
Angelo Rosado, Senior Principal Product Manager, Oracle 3022
CON8142 - Customer Success Stories: Upgrading to Oracle E-
Business Suite 12.2 Moscone
12:15
Andrew McVeagh, Oracle CoE Leader, GE Transportation West
p.m.
Terri Noyes, Senior Director, Oracle 3004
Musa Ramadhani, Lead Oracle Apps DBA, Gentex Corporation
Moscone
CON8134 - Maintenance Strategies for Oracle E-Business Suite
3:00 p.m. West
Elke Phelps, Senior Principal Product Manager, Oracle
3022

Related Sessions
Thursday, October 29, 2015
CON8129 - Advanced Architectures for Oracle E-Business Suite Moscone
10:45
Noby Joseph, Architect ATG Development, Oracle West
a.m.
Elke Phelps, Senior Principal Product Manager, Oracle 3022

Thank You

Online Patching With Oracle E-Business Suite 12.2

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Online Patching With Oracle E-Business Suite 12.2

Caricato da

Copyright:

Formati disponibili

Online Patching

with Oracle E-Business Suite 12.2

Oracle Confidential Internal/Restricted/Highly

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

In 12.2 all patching operations are online

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

Online patching uses the

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

E-Business Suite Patches

Copy the production code

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

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

Cutover is the time taken to switch users from the

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

E-Business Suite Patches

Users are logged off the production Instance

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

Wall clock time very Wall clock time is no longer

Consumes all resources Online users share resources

Upgrade designed to run as Data upgrades designed to not

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

File system Patching

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

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

Run File System Edition-Based Patch File System

INST_TOP Non-Editioned File INST_TOP

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

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

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

File System File System

10.1.2 appl comn 10.1.2 appl comn

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

Stores external data files

Non-Editioned File System

appl patch log

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

New script to setup the environment: EBSapps.env

Echo environment variables

$ echo $NE_BASE : /scratch/orauser/im4kevin/fs_ne

$ echo $APPL_TOP_NE : /scratch/orauser/im4kevin/fs_ne/EBSapps/appl

$ echo $PATCH_TOP : /scratch/orauser/im4kevin/fs_ne/EBSapps/patch

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

Echo environment variables

$ echo $RUN_BASE : /scratch/orauser/im4kevin/fs2 fs1 fs2 fs_ne

$ echo $NE_BASE : /scratch/orauser/im4kevin/fs_ne

$ echo $APPL_TOP_NE : /scratch/orauser/im4kevin/fs_ne/EBSapps/appl

$ echo $PATCH_TOP : /scratch/orauser/im4kevin/fs_ne/EBSapps/patch

appl patch log

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

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

Key enabling technology for Online Patching

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

Client code connects to an edition Business Users

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

Online Patching is used to apply all patches in 12.2

Copy the Apply one or Compile Restart Remove

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

Patch Edition & Run Edition of the

un Prepare All files on the Patch Edition are an

File application are copied

Patch Edition is created in the

ditionPatch Efficient use of space

Edition Database copied

New patching standards are