Professional Documents
Culture Documents
EBS Upgrade PDF
EBS Upgrade PDF
The sizing data is based on the upgrade of a 456 GB Release 12.1.3 database to Release 12.2.
In This Document
Database Size:
Before Upgrade DB Size (GB) After Upgrade DB Size (GB) Delta (GB) % Growth
456 481 25 5.5
The 25 GB greater database size after the upgrade reflects the additional system tablespace needed as a
prerequisite for enablement of Edition-Based Redefinition (EBR).
Environment details
Note: The database and application tiers are on the same machine.
Database Configuration
SGA: 5 GB
Shared Pool Size: 1 GB
PGA: 3 GB
Log Buffer: 30 MB
job_queue_processes: 32
During the upgrade of the Admin Tier, batchsize was 1000 and number of workers used was 32.
Oracle E-Business Suite Release 12.2 introduces Online Patching. This requires three application tier file systems:
• fs1 (Production file system) – Used by the current users of the system.
• fs2 (Copy of production file system) – Used by the patching tools.
• fs_ne (Non-editioned file system) – Stores files containing data that is needed across all file systems (for
example, data import and export files, report output files, and log files).
• Inst (INST_TOP) - Oracle E-Business Suite Release 12 Instance Home, contains all the config files, log files, SSL
certificates etc.
All three file systems serve a single database. The file system that is currently being used by the running application is
never patched: all patches are applied to the file system that is not currently in use.
Tablespace Size
Tablespace Name Before Upgrade Size (MB) After Upgrade Size Difference % Growth
SYSTEM 16489 (MB)
16819 (MB)
330 2%
CTXSYS 475 475 0 00%
OWAPUB 0 0 0 0.06%
SYNCSERVER 25 25 0 0%
DCM 178 178 0 0%
CWMLITE 0 0 0 0%
SYSAUX 1594 1662 68 4.26%
HTMLDB 311 311 0 0%
B2B_IDX 14 14 0 0%
MTR 2 2 0 0%
DSGATEWAY_TAB 5 5 0 0%
DISCO_PTM5_META 2 2 0 0%
B2B_LOB 11 11 0 0%
OLTS_DEFAULT 2 2 0 0%
OPMOR 5 5 0 0%
PORTAL 1 1 0 0%
PORTAL_DOC 0 0 0 0%
B2B_DT 61 61 0 0%
OLTS_SVRMGSTORE 2 2 0 0%
RE 7 7 0 0%
IAS_META 201 201 0 0%
WCRSYS_TS 2 2 0 0%
OCATS 2 2 0 0%
UDDISYS_TS 19 19 0 0%
PORTAL_LOG 0 0 0 0%
OLTS_ATTRSTORE 0 0 0 0%
ODM_DATA 30 30 0 0%
APPS_TS_DISCO_OLAP 10 10 0 0%
APPS_TS_QUEUES 7201 7201 0 0%
APPS_TS_TOOLS 14 14 0 0%
APPS_TS_INTERFACE 17456 17303 -153 -0.89%
APPS_TS_SEED 34184 34317 133 0.39%
XDB 151 151 0 0%
APPS_TS_TX_IDX 98809 99286 477 0.48%
GEOR_TBS 2021 2021 0 0%
NOETIX 0 0 0 0%
APPS_TS_DISCO 766 766 0 0%
TEMP2 9192 9192 0 0%
APPS_TS_MEDIA 2536 2536 0 0%
DISCO_PTM5_CACHE 97 97 0 0%
B2B_RT 38 38 0 0.00%
APPS_TS_SUMMARY 11694 10580 -1114 -0.97%
APPS_TS_ARCHIVE 938 937 1 0.10%
APPS_TS_TX_DATA 94631 94462 -169 -0.18%
APPS_CALCLIP 4676 4676 0 0%
PORTAL_IDX 0 0 0 0%
ORABPEL 11 11 0 0%
OLTS_CT_STORE 7 7 0 0%
APPS_OMO 638 638 0 0%
TEMP1 10740 10740 0 0.00%
BAM 6 6 0 0.00%
OLTS_BATTRSTORE 0 0 0 0%
APPS_TS_NOLOGGING 94 267 173 185%
NON_APPS_TS_DATA 66 66 0 0%
Total 315414 315159 -254
Schema Size
Only a few of the schemas are listed below show significant change in the size after the upgrade.
Schema Name 12.1.3 Size (MB) 12.2 Size (MB) Difference % Difference
AP 4360.63 4379.5 18.88 0.43
APPLSYS 38724.44 39377.81 653.37 1.69
APPS 2395.63 1765.38 -630.3 -26.31
APPS_NE Not applicable 95.25 95.25 Not applicable
AR 90709.44 90567.63 -141.8 -0.16
BSC 457.44 285.69 -171.8 -37.55
CSC 232.75 183.5 -49.25 -21.16
CSI 5964.44 6036.94 72.5 1.22
EGO 2655.94 2690.44 34.5 1.3
INV 11482.56 11658.13 175.57 1.53
JTF 30272.75 30340.38 67.63 0.22
MSC 5120.44 5153.94 33.5 0.65
OKC 2969.19 3037.69 68.5 2.31
PJI 936.25 969.38 33.13 3.54
SYS 19893.52 20819.65 926.13 4.66
XDO 1477.13 1626.38 149.26 10.1
XLA 3059.06 3134 74.94 2.45
• It is recommended to follow AWR pool advisories for optimizing the SGA and PGA size in the Release 12.2
upgrade.
• You should ensure that SGA and PGA are allocated appropriately within the available memory of the
system. If set higher it may cause excessive paging, or even swapping.
• Setting parallel_max_servers to 2 x no. of CPUs will help with large index creation, statistics gathering, and
some large upg+ phase jobs.
• In order to maximize multiblock I/O sizes, you should remove "db_file_multiblock_read_count" (if
specified).
• Ensure you reset the following init.ora parameters after completion of the Release 12.2 upgrade.
o recyclebin
o parallel_max_servers
o job_queue_processes
The downtime portion of the upgrade involves the automatic submission of 95 distinct concurrent programs. For a list of
the programs, refer to the "Required Post-Upgrade Jobs" section of this document.
In several cases, these programs will run in multiple threads, so the total number of concurrent requests that form part
of the post-upgrade step is much higher. These programs will be picked up and executed by the concurrent manager
once the system is up, and as such their execution will be mixed with the execution of ongoing concurrent jobs in the
system.
To improve manageability of this situation, you can define a separate concurrent manager queue to process only these
programs. This can be achieved by using inclusion and exclusion rules to prevent other manager queues (such as the
standard manager) from picking up these requests, and cause this new manager queue to only process these requests.
Doing this allows you to control the number of target processes allocated to these post-upgrade concurrent programs,
including dynamically with the use of work shifts. For additional details about configuring new manager queues, target
processes, inclusion/exclusion rules, and work shifts, refer to Oracle E-Business Suite Setup Guide from the Onine
Documentation Library.
Before you shut down all services as part of the “Perform the Upgrade“ tasks mentioned in the Upgrade Guide, you
need to deactivate all Request Processing managers. This is needed so that when the services are brought up at the end
of the upgrade, the existing Request Processing Managers do not start picking up and executing requests. After the
upgrade is complete, you need to perform the following steps to create new program type and managers to run the
post-upgrade requests.
To create a new program type, and include a program in that program type:
1. Log in to Oracle E-Business Suite as SYSADMIN, and navigate to System Administrator > Concurrent : Program >
Type
Name: R12PUPT
Application: System Administration
Description: Program Type for Post Upgrade Request
2. Include programs from the above list into this new program type.
3. Navigate to System Administrator >Concurrent: Program >Define
4. Search for Program "Refresh Materialized Views"Type (choose):R12PUPT
5. Do the same for other programs in the list.
After completing the above steps, activate all "Request Processing Managers" that you previously deactivated.
Note that after all these post-upgrade requests run, you should revert the exclusion/inclusion of managers and
programs to the original state, removing the new program type and new manager. This is necessary as some of the
programs in the list may need to run in the future, as part of the regular system batch processing requirements rather
than part of the upgrade.
While monitoring CPU usage and I/O response times, you should test a range of values between 1 x No. of CPUs to 1.5 x
No. of CPUs, . The goal is to maximize the number of workers, while keeping CPU usage below 100% (ignoring occasional
spikes) and I/O response times below 10-15 milliseconds (again, ignoring occasional spikes).
Below is a list of of the concurrent programs that form part of the required post-upgrade steps. These concurrent
programs are automatically submitted during the regular downtime upgrade, so no manual submission is required.
These jobs took 7 hours for the 456 GB database upgrade, using 30 target processes in the concurrent manager.
Application Concurrent Program Name User Concurrent Program Name Elapsed Total
Name Time Requests
(min.)
Before applying the main 12.2 upgrade driver (u10124646.drv), AD patch 10117518 must be applied on both file systems
(fs1 and fs2). As a result of applying this patch, two new schemas (APPS_NE and GHG) will be created for use in Release
12.2.
The overall time taken to apply the patch was about two hours.
1. Time taken for creating the users and granting privileges to them was 20 minutes.
2. Compiling JSPs (using perl) took 1 hour 30 minutes.
3. The following database activity timing information is for the Release 12.2 AD patch (10117518), which took 5.5
minutes.
The following timing information is for the Release 12.2 main upgrade driver (u10124646.drv) only
The upgrade is a very I/O intensive process, moving, updating, and indexing large amounts of data. As such, I/O
subsystem performance and bandwidth are critical to minimizing the amount of downtime. During many Release 11i to
Release 12 customer upgrades, poor I/O sub-system performance was found to be one of the major sources of upgrade
performance service requests.
Therefore, during the upgrade testing process you should monitor I/O performance and correct any issues found. As a
reference, shown below are the IOPS rates and bandwidth measurements that were obtained while testing the upgrade
with the 456 GB database. The numbers were calculated based on data from AWR and OS monitoring utilities.
IOPS:
• Maximum IOPS value is 478.9.
• During upgrade, IOPS range is from 142 to 478.9. Max value is reported during large indexes creation phase.
• High IOPS value (140 to 478) is seen during UPG phases.
Timing information for Release 12.2 Edition-Based Redefinition (EBR) enablement (Patch 13543062)
Timing reported here is only for application of the EBR enablement patch. Apart from patch application, many other
steps are performed in enabling EBR. The time these take will depend upon the customizations you have.
Refer the the following document for the steps needed to enable EBR:
• Oracle E-Business Suite Upgrade Guide Release 12.0 and 12.1 to 12.2, Part No. E48839 (Section 4, Oracle E-
Business Suite Online Patching)
You need to register all your custom schemas, following the procedures in the above document.
References:
• Oracle E-Business Suite Release 12.2 Information Center (My Oracle Support Knowledge Document 1581299.1)
• Database Initialization Parameters for Oracle E-Business Suite Release 12 (My Oracle Support Knowledge Document
396009.1)
• Oracle E-Business Suite Recommended Performance Patches (My Oracle Support Knowledge Document 244040.1)
Change Log
Date Description
04-Nov-2013 • Initial publication.