Online patching ebs122_aioug_appsdba_nov2017

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. |
Oracle E-Business Suite 12.2: Online Patching
Sharath Vishwanath (Director, EBS Release Engineering)
Shivdas Tomar (Group Manager, EBS – Applications Technology
Group)

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.

Program Agenda: Patching with E-Business Suite 12.2
4
Overview of 12.2 Architecture
Patching EBS 12.2 with Online Patching
Online Patching Cycle – Special Operations
Patching Applications Tier Technology Patches
1
2
3
4

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | 5
Oracle E-Business Suite 12.2 Architecture
JDBC/SQLNet
Application Database
RAC & ASM
Global Single
Data Model
WebLogic JSP
Forms
BI Publisher
BC4J
WebListener
UIX 11g
WebLogic Server
• Online patching uses the latest
features of the technology stack
– Edition-Based Redefinition (EBR)
– Web Logic Server
Edition-Based
Redefinition

Oracle E-Business Suite 12.2 Architecture
6
Dual File System
Synchronization managed
by patching tools
Edition-Based Redefinition
Non-Editioned File System
Developer 10.1.2
COMMON_TOP
APPL_TOP
INST_TOP
Oracle HTTP Server (OHS)
WebLogic Server (WLS)
File System 1
Developer 10.1.2
COMMON_TOP
APPL_TOP
INST_TOP
Oracle HTTP Server (OHS)
WebLogic Server (WLS)
File System 2
PATCH_TOP
APPL_TOP_NE
LOGS
More information in the Online
Patching FAQ (Note 1583902.1)

• Dual File System (Run Edition File System and Patch Edition File System).
• Patches are applied to Patch Edition File System (copy of Production
System)
• Downtime limited to short ‘Cutover’.
– Cutover is the time taken to switch users from the production system to the newly
patched copy.
– Measured in minutes not in hours/days.
• Changing the Patching Paradigm (downtime patching vs online patching).
7
Online Patching with Oracle E-Business Suite R12.2

File System Editioning
8

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

12.2 E-Business Suite File System Layout
File System Laid Down after 12.2 Rapid Install
Install base
fs_nefs2 EBSapps.envfs1
New file to choose the
environment to set:
EBSapps.env RUN|PATCH
fs1
instFMW_HOMEEBSapps
10.1.2 appl comn
ar …glad
fs2
instFMW_HOMEEBSapps
10.1.2 appl comn
ar …glad
File System 1 File System 2

• 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
Non-Editioned File System (fs_ne)

Install base
fs_nefs2 EBSapps.envfs1
New file to choose the
environment to set:
EBSapps.env RUN|PATCH
12
fs_ne
instEBSapps
adop
appl patch log
fs2fs1
• Subdirectories sparsely populated
• Only created as needed

R12.2 Environment Overview
• 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 on all
nodes
Working with the 12.2 Environment

File Systems Patching Cycle
• Two complete file systems are always present
– Run Edition - Used by the running Application
– Patch Edition - Either:
• Currently being patched
or
• Waiting for the next patching cycle
– The two files systems are rotated between Run and
Patch during every patch cycle
Cutover
Prepare
Prepare
Cutover
1
2
1
2

File System Synchronization
• Two file synchronization options
– Patch (driver files from previous patching cycle are reapplied )
– File (only files changed in previous patching cycle are synchronized)
• File based provides a significant performance improvement in adop Prepare phase
– Configurable callout to file system synchronization logic
– Example implementation provided using unix rsync command
– Customer can replace command with smart/advanced disk utility of their choice
• Automatic support for customizations (with ‘sync_mode=delta’)
– All files in the Applications file system are synchronized
– Customizations no longer need to be registered in the custom synchronization driver (adop_sync.drv)
15
Efficient File Based Synchronization*
* Available in AD/TXK Delta 8 and above

File System Synchronization
• New prepare phase parameter (sync_mode) to control synchronization
behaviour
– adop phase=prepare sync_mode=patch (default)
– adop phase=prepare sync_mode=delta (new file based)
• Delta style synchronization uses the file system synchronization command
specified in:
$AD_TOP/patch/115/etc/delta_sync_drv.txt
• Only files changed in the previous patching cycle are synchronized
16

Database Edition-Based Redefinition
17

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
18

Online Patching is Enabled by 11gR2 Edition-Based
Redefinition
• Client code connects to an “edition”
of the database
– Run 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
19
Multiple Copies of Database Code Objects Can Coexist
DBA
Business Users

Seed Data Management
20

Seed Data Management
• Seed data is data stored in database tables that affects the behavior of the
application and is patched by EBS development
• In order to patch seed data without disturbing the running application, we
enhance seed data tables to support Editioned Data Storage
– The ability to store multiple editions (copies) of seed data in the same table
• AD/TXK Delta 7
– Full synchronization and cleanup of all rows in seed data table
• AD/TXK Delta 8 and above
– Only rows changed in the last patching cycle are synchronized
21

Incremental Seed Data Synchronization*
• Significant performance improvement in adop Apply phase
– Only rows changed since the last synchronization are updated
– The time taken to synchronize seed data is proportional to the number of rows changed
since the last synchronization
– Minor changes no longer incur the cost of full data replication
• Dual rowset seed data synchronization
– Two permanent sets of seed data
– Only rows changed by a patch are synchronized on prepare
– No cleanup required
22
* Available in AD/TXK Delta.8 and above

12.2 Online Patching Cycle
23

Understanding the Online Patching Cycle
24
• 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

Online Patching Cycle – Prepare Phase
• The Basics CleanupCutoverFinalizeApply
• Copy the
production
application code
• Create a new
Patch Edition in
the database
Prepare
Users Online Users OnlineUsers Offline
Prepare
• Synchronizes Patch Edition and Run Edition on the file system
• Create a new Patch Edition in the database

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | Confidential – Oracle Internal 26
Preparing the File System
• Patch Edition & Run Edition of the file systems
are synchronized
• All files on the Patch Edition are an exact copy
of the files on the Run Edition
• Incremental synchronization is the default
– File based
• All changed files are synchronized
– Patch based
• Patches applied on last cycle are reapplied
• Full synchronization available if necessary

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | Confidential – Oracle Internal 27
Preparing the Database
• Patch Edition is created in the database
• All code objects in the Patch Edition begin as
pointers to code objects in the Run Edition
• Efficient use of space
– Objects are only “Actualized” into the Patch Edition when a
new revision of the code is applied
• Storage objects such as tables are not copied
– New patching standards are followed for upgrading
storage objects

28
adop phase=prepare
• Validates system configuration to ensure
that the system is ready to start an Online
Patching cycle.
• Check whether to perform cleanup;
execute if needed.
• Prepare is run on all nodes in a muti-node
configuration
• Synchronizes the Run and Patch File System
• Creates the Database Patch Edition
What to Know
• Creates Patch Service and Checks the
integrity of the database data dictionary.
• Checks and submits "Online Patching In
Progress" (ADZDPATCH) concurrent
program.
• Check to see if Oracle E-Business Suite
Technology Codelevel Checker (ETCC) has
has been run.
What to Know

Online Patching Cycle - Apply
• Execute patch drivers to update Patch Edition
• Multiple patches can be applied, including customizations
CleanupCutoverFinalize
• Apply one or
more patches to
the Patch Edition
Apply
• Copy the
production
application code
• Create a new
Patch Edition in
the database
Prepare
Users
Online
Users
Online
Users
Offline

Patch Driver
–File System actions
–Database Actions
30
Online Patching Cycle - Apply
• Patches are applied to the copy
(Patch Edition)
• The production application is
unaffected by the changes
– Users are connected to the
Application and can perform their
work unaffected by the patch
• Changes are made in the isolation of
an Edition
– The running application is
unaffected by these changes
Applying Patches

Online Patching Cycle – Apply Phase
31
• ADOP controls application of patches to
the file system and database
• Mutiple patches can be applied in the
same patching cycle
• Supports all options previous supported by
adpatch
• Supports fully automated execution via
inputs files
What to Know
• Execute adop apply on the primary node
$ adop phase=apply patches=12345
$ adop phase=apply patches=1234,5678,9876
$ adop phase=apply patches=1234,5678 workers=4
$ adop input_file=April2016.txt
April2016.txt
phase=prepare,apply,finalize
patches=1234,5678,9876
workers=4
…
What to Do

Online Patching Cycle - Finalize
• Pre-compute DDL that needs to be run at cutover.
• Compile invalid objects
• Validate that the system is ready for cutover.
• Wait for a good downtime window
CleanupCutover
• Compile invalid
Objects
• Validates system’s
readiness for cutover
• Wait for a good
downtime window
Finalize
• Apply one or more
patches to the
Patch Edition
Apply
• Copy the
production
application code
• Create a new
Patch Edition in
the database
Prepare
Users
Online
Users
Online
Users
Offline

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

Online Patching Cycle - Cutover
• 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
Cleanup
• Promote Patch
Edition as Run
Edition.
• Restart MT services
on latest Run
EditionFS.
• Compile invalid
Objects
• Wait for a good
downtime
window
Finalize
patches to the
Patch Edition
Apply
• Copy the
production
application code
• Create a new
Patch Edition in
the database
Prepare
Users
Online
Users
Online
Users
Offline
Cutover

• 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
35

Cutover Automatically Manages all Services on all Nodes
• Middle-tier processes stopped
– Manages all nodes in the configuration
via remote execution
– End Users are disconnected
• File system roles swapped
– Patched (FS-2) promoted to Run
– FS-1 available for next patching cycle
• Database Patch Edition promoted to
Run Edition
• Middle-tier processes restarted
– Manages all nodes in the configuration
via remote execution
– Users reconnect

37
• Brief Downtime
– Application tier services are automatically shut 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
– If you do not want to wait for in-progress concurrent
requests to finish normally, you can terminate the internal
concurrent manager by executing the ‘adcmctl.sh abort’
command from a different shell.
What to Know
• Before running the cutover command, ensure you are
ready to commit to application of the selected patches.
Once cutover is complete, it is not possible to revert to
the previous edition.
• Execute adop cutover on the primary node
$ adop phase=cutover
What to do

38
Deferring Application Tier Restart
• In some cases, you may need to perform
additional manual steps after cutover but
before restarting the application tier
services
– Apply customizations
– Patch the database tier
• You must start the application tier services
manually after performing additional steps
What to Know
without starting the application services
$ adop phase=cutover mtrestart=no
• Perform manual steps
• Start application tier services manually
$ source EBSapps.env run
$ adstrtal.sh –mode=allnodes
What to do

Online Patching Cycle - Cleanup
• Remove
obsolete
objects
• Restart application
on Patch Edition
Cutover
• Compile invalid
Objects
• Wait for a good
downtime
window
Finalize
patches to the
Patch Edition
Apply
• Copy the
production
application code
• Create a new
Patch Edition in
the Database
Prepare
Users
Online
Users
Online
Users
Offline
Cleanup
• 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 Application (new Run
Edition FS)
• Database
– Code objects patched in the latest patching cycle are
deleted from Old Editions
– Once all code objects are deleted from an Old Edition it is
also deleted (if cleanup run post actualize_all).

41
• Users are online during the cleanup process
• Removes obsolete objects from the system to
recover space
• If you fail to run the cleanup phase explicitly, it will
be run automatically on the next prepare cycle
– This will cause a delay in starting your next online patching
cycle
• Three cleanup_mode are available
– quick - Performs only essential cleanup tasks
– standard (default) - Removes obsolete code objects
– full - Performs maximum cleanup, which drops all obsolete
code from earlier editions
What to Know
$ adop phase=cleanup
$ adop phase=cleanup cleanup_mode=quick
$ adop phase=cleanup cleanup_mode=full
What to do

Recap: Online Patching Cycle
• The Basics
• Remove
obsolete
objects
Cleanup
• Stop MT services
on Run FS.
• Promote Patch
Edition as Run
Edition.
• Start MT services
on new Run FS.
Cutover
• Compile invalid
Objects
• Validates system’s
readiness for
cutover
• Wait for a good
downtime window
Finalize
patches to the
Patch Edition
Apply
• Copy the
production
application code
• Create a new
Patch Edition in
the database
Prepare
Users Online Users OnlineUsers Offline
• 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

Online Patching Cycle – Special Operations
43

Online Patching Cycle - fs_clone
44
Re-Cloning the Patch Edition File System
• Patch file system is normally incrementally synchronized with
the run edition file system during prepare
• In some special cases a full re-clone of Patch Edition FS is
required 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 of Patch Edition FS is recommended
– After applying a large EBS RUP; EBS upgrade to 12.2 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
What to Know
• Must be invoked from the run file system, before the next
prepare phase is run.
• Execute re-clone on the primary node
$ adop phase=fs_clone
What to Do

Online Patching Cycle - Abort
• The Online Patching Cycle can be aborted at any time prior to
Cutover

adop phase=abort
46
• The abort phase is used to terminate a patching cycle
before it is complete and rollback any changes that
have been made.
• Aborts the online patching cycle by dropping the
database patch edition.
• Confirms that there is an in-progress online patching
cycle, so the abort call is therefore valid.
• Cancels the ADZDPATCH concurrent program, if it is
running.

Online Patching Cycle - Abort
47
• Useful when an Online Patching cycle encounters
problems that cannot be fixed immediately
• Returns the system to normal runtime operation
• Online Patching cycle cannot be aborted after
cutover
• 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
What to Know
• Execute adop abort on the primary node
$ adop phase=abort
What to Do

Online Patching Cycle – actualize_all
Confidential – Oracle Internal 48
Full Cleanup as a Periodic Maintenance Operation
• As each Online Patching cycle is completed, the
database will accumulate an additional old
database edition.
• When the number of database editions reaches 25
or more, you should consider running a special
maintenance operation to remove old database
editions
• Actualize all is a special adop phase that ensures
every database editioned object has a version in the
PATCH edition
– This allows all copies in OLD editions to be removed by
full cleanup
What to Know
• Before starting, you should ensure that the system has
the recommended database patches and latest AD-TXK
code level installed.
• Execute adop on the primary node to actualize all
objects and perform a full cleanup
$ adop phase=prepare
$ adop phase=actualize_all
What to do

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

Single File System and Downtime Patching Mode
• 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
– Patch file system is not present
– All patches must be applied to the RUN edition using adop apply in downtime mode
• Limited adop phases and modes supported
– Apply phase in downtime mode: Applies patches directly to the RUN edition of the instance.
• Downtime mode should not be used unless directed in the README of the patch.
– Cleanup phase.
50
Designed for Development Instances Only

Applying Downtime Mode Patches on a Single File System
51
Designed for Development Instances Only
• Only supported on development systems
to test custom code
– The code should then always be tested in a standard dual file system
test environment before being applied to production.
• Patches are applied to the RUN edition
of the file system and database
• Oracle does not test patches in Downtime
mode unless explicitly stated in README.
• All application tier services must be down
before applying a patch in Downtime
mode.
What to Know
• Single file system environment must have a
single-node application tier: multi-node
application tiers are not supported.
• Single file system environment can only be
created by conversion from an existing dual
file system environment.
• You cannot convert a single file system
environment back to a dual file system.
• You cannot clone from a single file system
environment.
IMPORTANT

Online Patching: Monitoring & Reporting
Tools
52

Monitor The Online Patching Cycle
$ adop -status
53
Display Status of a Single Node Online Patching Cycle
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

Monitoring and Reporting Tools
– adopmon: Online Patching Monitoring utility
• Provides a continuously refreshed view of key adop actions
– adopreports: Online Patching Diagnostic Reports
• Can be used to help diagnose issues or simply gather information about the status of your system.
• System Information | Online Patch Information | Database Edition Information | Developer
Information
– adopscanlog: Analyzing Log files
• adopscanlog –latest : scan log directories related to latest run.
• adopscanlog -latest=yes -phase=<phase_name>
• adopscanlog -session_id=<number>
• Adopscanlog –scan_dir=<directory>
• adopscanlog -help
54

Patching Application Tier Technology Stack
55

Applying Technology Stack Updates
56
Oracle E-Business Suite Release Application Tier
• Application tier technology stack updates can be
– Applied to the PATCH file system while EBS is
online
– Applied in conjunction with an EBS Online
Patching cycle
or
– Applied as a separate Online Patching exercise
• fs_clone must be performed after applying
Application tier technology patches.
What to Know
• Prepare the PATCH filesystem.
• Apply technology stack patches to PATCH filesystem.
• Apply EBS patches (optional).
• Coordinate time for CUTOVER and complete the online
patching cycle.
• Synchronize the technology stack patches between the
RUN and PATCH filesystems.
What to Do

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. |Oracle E-Business Suite 12.2 Patching Technology Components Guide (Doc 1355068.1)
Applying Technology Stack Updates
57
Oracle E-Business Suite Release Application Tier
• Only in case of upgrade to 12.2 (from pre-12.2
Release such as Release 11i, 12.0, 12.1) and 12.2 new
installation, application tier technology stack patches
to be applied on Run Edition File System,
immediately after creating it using Rapid Install.
New Installation and 12.2 Upgrade
• Prepare the instance for patching
• Apply technology stack patches to the PATCH file system
$ source .EBSapps.env PATCH
$ bsu.sh
$ opatch apply
• Apply EBS patches (optional)
$ adop phase=apply inputfile=myinputfile
• Complete the Online Patching cycle
$ adop phase=finalize
$ adop phase=cleanup
• Synchronize technology patches between the RUN and PATCH file
systems
What to Do

EBS Technology Code level Checker (ETCC)
• ETCC can be downloaded via Patch 17537119 from My Oracle Support
• Helps to identify missing Oracle database or middle tier technology patches
that would need to be applied to your E-Business Suite Release 12.2
system.
• Oracle strongly recommends the use of this utility to ensure that all
required database and middle tier bugfixes have been installed.
• The utility maps bug fixes to patches, generating a Patch Recommendation
Summary that lists the patches (including versions and associated
filenames) that are required for your system.
58

• Database Code Level Checker : DB-
ETCC (checkDBpatch.sh)
– Verifies database patches required by
EBS 12.2
• Application Tier Code Level Checker:
MT-ETCC (checkMTpatch.sh)
– Verifies technology stack patches
required by EBS 12.2
59
Technology Stack Code Level Verification Utilities (ETCC)
✓
Application Tier
Forms 10.1.2
OHS
Oracle Common
WebLogic
✓
✓
✓
✓
Forms 10.1.2
OHS
Oracle Common
WebLogic
✓
✓
✓
✓
fs1 fs2
Application TOPs Application TOPs
Note 1594274.1, Oracle E-Business Suite Release 12.2:
Consolidated List of Patches and Technology Bug Fixes

EBS Technology Codelevel Checker (ETCC)
60
New: Automatically maps bug fixes to patches and recommends patches

• AD/TXK are the infrastructure
components that provide the 12.2
Online Patching technology, Cloning, etc.
• Strongly recommend that you apply the
latest patch collections at your earliest
convenience
61
Oracle EBS 12.2 AD/TXK Delta 10 Now Available
Stay Current with the Latest Updates
Description MOS Doc ID
Applying the Latest AD and TXK Release
Update Packs to Oracle E-Business Suite
Release 12.2
1617461.1
Oracle E-Business Suite Applications DBA
and Technology Stack Release Notes for
R12.AD.C.Delta.10 and R12.TXK.C.Delta.10
2295390.1

Plan for Database Administrators and Developers
• 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)
62
Stay Current with Documentation Updates

1
2
3
4

Online patching ebs122_aioug_appsdba_nov2017

Online patching ebs122_aioug_appsdba_nov2017

More Related Content

What's hot

Viewers also liked

Similar to Online patching ebs122_aioug_appsdba_nov2017

Recently uploaded

Online patching ebs122_aioug_appsdba_nov2017