1597531 A

Oracle E-Business Suite Release 12.2: Upgrade Sizing and Best Practices This document contains database schema sizing information, application tier sizing information, upgrade timing, and other best practices, all designed to make your upgrade to Oracle E-Business Suite Release 12.2 as smooth as possible. The sizing data is based on the upgrade of a 456 GB Release 12.1.3 database to Release 12.2. There is a change log at the end of this document. In This Document

• Application Tier Size • Tablespace Size • Schema Size • R12.2 Best Practices • Required Post upgrade Jobs • Sample Upgrade Timings

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

Operating system: Oracle Linux Enterprise Edition Server Release 5.8 Server Memory: 34 GB Number of CPUs: 32 Database Release: 11.2.0.3 Oracle E-Business Suite: 12.1.3 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. Application Tier Size 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.

Component Before Upgrade Size After Upgrade Size

ORACLE_HOME 3.6 GB 3.6 GB APPL_TOP 28 GB Not applicable INST_TOP 20 MB Not applicable fs1 (APPL_TOP+ INST_TOP) Not applicable 30 GB fs2 (APPL_TOP+ INST_TOP) Not applicable 29 GB fs_ne Not applicable 660 KB

Tablespace Size Tablespace size was calculated as “Total TableSpace Size – Free Space”. Tablespace Name Before Upgrade Size (MB) After Upgrade Size

(MB) Difference

(MB) % Growth

SYSTEM 16489 16819 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 Two new schemas have been created for Release 12.2:

1. APPS_NE: For the Non-Editioned file system 2. GHG: For the Oracle Environmental Accounting and Reporting.

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

Release 12.2 Upgrade Best Practices Recommended initialization (init.ora) parameter settings for the upgrade. • It is recommended to follow AWR pool advisories for optimizing the SGA and PGA size in the Release 12.2

upgrade.

• An upgrade involves tens of concurrent sessions. Suitable starting values are: 1. log buffer = 30 to 100 Mb 2. shared pool = 1 to 4 GB 3. pga target = 3 to 20 GB 4. buffer cache = 5-50 GB (multi-GB)

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

• Set “job_queue_processes = No. of CPUs” – adobjcmp.sql (Phases: plb+90 and last+63) This parameter is set at the beginning of the upgrade; it will be most useful in the phases mentioned above.

• 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

Isolate post-upgrade concurrent programs to a separate manager queue.

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.

To exclude a program type from the Standard Manager:

1. Log in to Oracle E-Business Suite as SYSADMIN and navigate to System Administrator > Concurrent : Manager >Def ine

2. Search for Standard Manager. 3. Click on Specialization Rules. 4. Go at the bottom of the list to add a new record. 5. Include/Exclude (choose): Exclude

Type(choose): Request Type Application(choose): System Administration Name(choose): R12PUPT

6. Do the same for all other Request Processing managers. To create a new concurrent manager and include a program type:

1. Log in to Oracle E-Business Suite as SYSADMIN and navigate to System Administrator > Concurrent: Manager > Define

2. Check the Enabled box. 3. Enter the following to create the new concurrent manager:

Manager: R12_Post_Upgrade Short Name: R12PU Application(choose): Application Object Library Description: New manager queue for R12 post upgrade requests Type(choose): Concurrent Manager Cache Size: 1 Program Library Name(choose): FNDLIBR Specialization Rules: Include/Exclude(choose): Include Type(choose): Request Type

Application(choose): System Administration Name(choose): R12PUPT Work Shifts: Work Shift (choose): Standard Processes: Enter a Value, for example 4 Sleep Second: 30

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. Determine optimal number of workers for 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). Required Post-Upgrade Jobs

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 Name

Concurrent Program Name User Concurrent Program Name Elapsed Time (min.)

Total Requests

Advanced Benefits (BEN)

BENCWBMU Compensation Workbench Model Upgrade Process

0.10 1

Advanced Product Catalog (EGO)

EGOCPAGV User-Defined Attribute Group Views (AGV) Compilation Program

0.57 1

Advanced Supply Chain Planning (MSC)

MSCREFMV Refresh Materialized Views 0.70 2

Application Implementation (AZ)

AZR12UPGRADE iSetup R12 Upgrade Selection Sets Column

0.47 3

Application Object Library (FND)

FNDFIXRN Fix FND role names 0.10 1


DIAGPATCHINGCP Diagnostics patching CP 12.60 9


FDFVGN Flexfield View Generator 135.10 985


AFLOBBLD Rebuild Help Search Index 16.72 1


FNDIRLPP iRep Loading Post Processor 20.72 5


FNDRSSTG Request Set Stage 0.87 3


FNDSCMPI Compile Security 0.40 1


FNDLOAD Generic Loader 13.05 5


FNDIRLOAD FNDIRLOAD 24.70 5


FNDRSSUB Report Set 1.00 2


FNDWFAASTATCC Workflow Agent Activity Statistics Concurrent Program

1.98 10


FNDWFWITSTATCC Workflow Work Items Statistics Concurrent Program

2.75 10


FNDWFDSURV Workflow Directory Services User/Role Validation

0.88 2


FNDWFMLRSTATCC Workflow Mailer Statistics Concurrent Program

0.70 10


FNDWFNTFCU Workflow Update Notification Action Comments

1.50 6


FNDWFDSRHP Workflow Role Hierarchy Propagation

0.27 3


FDFCMPN Compile Non-Compiled Flexfields 56.33 7


FNDWFBES_CONTROL_QUEUE_CLEANUP

Workflow Control Queue Cleanup 0.02 2

Applications DBA (AD)

ADDRPOBS Drop obsolete products schema 51.62 204

Asia/Pacific Localizations (JA)

JAINDFOBS India - Remove India Localization contexts from DFFs

0.07 3

Collections IEX_COLLECTORS_TO_RESOURCE IEX: AR Collectors To Resource 0.88 1

(IEX) Collectors Contracts Core (OKC)

OKCARTCRTCTX Create Clause Text Index 0.18 1

Contracts Core (OKC)

OKCCHRCRCTX Create Contract Header Text Index 0.27 1

Human Resources (PER)

PAY_GEN_UPG Generic Upgrade Mechanism 2.03 1


PER_FND_SESSIONS_CLEANUP Remove obsolete sessions from fnd_sessions

0.53 12


HRTCAUNMP Unmerge contacts from TCA (TCA purge only)

3.62 1


IRC_CREATE_NOTIFICATION iRecruitment Create Notification Preferences

0.07 8

Incentive Compensation (CN)

CN_R1212_CNCMAUPD CN_R1212_CNCMAUPD 1.35 48


CN_R1212_CNCMHUPD CN_R1212_CNCMHUPD 0.30 48


CN_R1212_CNSRPTXN CN_R1212_CNSRPTXN 0.35 48


CN_FORMULA_GEN Generate Formula Packages 7.55 3


CN_COLLECT_GEN Generate Collection Packages 1.90 3


CNUPGPMTRXWRKER Upgrade payment transactions - Worker

0.05 10


CNUPGPMTCLWRKER Upgrade payment commission lines - Worker

0.05 10


CNUPGPMTRXMGR Upgrade transactions for AutoUpgrade or AutoPatch

0.08 1


CNUPGPMTCOMMTRXMGR Upgrade commissions and transactions for AutoUpgrade or AutoPatch - Manager

0.12 1

Inventory (INV)

INVIDSEP Items Data Scripts Execution 4.45 6

Labor Distribution (PSP)

PSPERUPB PSP: Migrate to OAFramework Effort Reporting

0.03 1

Labor Distribution

PSPUPREP PSP: Post Upgrade Bad Data Report 0.82 1

(PSP) Learning Management (OTA)

OTARPUPG Upgrade Log Report 1.30 1

Learning Management (OTA)

OTATZUPG Update Time Zone 0.23 1

Lease and Finance Management (OKL)

OKLSVPTH Service Passthrough Report 0.80 1

Marketing (AMS)

AMSUPGHISTORYRECSWKR Upgrade metrics history records process - Worker

1.05 64

Marketing (AMS)

AMSUPGHISTORYRECSMGR Upgrade metrics history records process - Manager

1.33 8

Oracle iProcurement (ICX)

ICXCUCDER Catalog Child Data Exceptions Report 3.93 1

Payables (SQLAP)

APWUPDST Update Expense Status Code in Expense Report Headers

0.07 1

Payables (SQLAP)

APWUPRD Upgrade Report Distribution 0.07 8

Payments (IBY)

IBYUPGCP iPayment FP.G Upgrade Program 0.00 2

Payroll (PAY) PYUSLV Payroll Worker Process 1.47 4 Purchasing (PO)

POXUPMGR Purchasing Post-Upgrade Process 0.05 1

Purchasing (PO)

POXUPWKR Purchasing Post-Upgrade Sub Process

0.00 3

Receivables (AR)

HZ_THIRD_PARTY_UPDATE Third Party Data Integration Update 0.47 2

Receivables (AR)

ARHGNRW Geography Name Referencing Worker

1.75 20

Receivables (AR)

HZ_GNR_DYNMK_PKG_GEN GNR Dynamic packages Generation 0.75 6

Receivables (AR)

ARHDCH DQM Sync Import Child Program 0.23 4

Receivables (AR)

ARHSUFXS Data Fix for Party Site Use 0.07 1

Receivables (AR)

ARHDQSYN DQM Synchronization Program 0.32 1

Receivables (AR)

ARHMAILS Mailstop Migration Program 0.03 1

Receivables (AR)

ARHDQCMAL DQM Compile All Rules 17.60 3

Receivables (AR)

ARHDNBCH Create DNB Hierarchy 0.07 1

Receivables (AR)

ARHDQM DQM Staging Program 0.42 3

Receivables ARHDQMPP DQM Parallel Sync Index Parent 0.10 1

(AR) Program Receivables (AR)

ARHDQMPC DQM Parallel Sync Index Child Program

0.02 4

Regional Localizations (JG)

JGZZVATTRXUPG EMEA VAT: Transaction Upgrade 0.95 6

Service Contracts (OKS)

OKSUHAFMGR Service Contracts Update History Annualized Factor Manager

0.28 1


OKS_TAX_MIGRATION Service Contracts eBTax Migration 0.05 1


OKSAQUMG Service Contracts ASO Queue Migration

0.58 1


OKSUHAFWKR Service Contracts Update History Annualized Factor Worker

0.02 4


OKSUBAFMGR Service Contracts Update Base Annualized Factor Manager

0.20 1


OKS_REPROCESS_SUBREQUEST Service Contracts Subrequest for Reprocessing Rule Data

0.02 1


OKSUBAFWKR Service Contracts Update Base Annualized Factor Worker

0.02 4


OKSLAUNCHKWF Launch Process Workflow for existing Service Contracts

0.10 1


OKSTAXHMGR Service Contracts Update History Tax Columns Manager

0.23 1


OKSTAXHWKR Service Contracts Update History Tax Columns Worker

0.00 4


REPROCESS_SYNC_RULE_DATA Service Contracts Reprocess/Synchronize Rule Data

0.23 1


OKSTAXBMGR Service Contracts Update Base Tax Columns Manager

0.20 1


OKSTAXBWKR Service Contracts Update Base Tax Columns Worker

0.00 4

Service (CS) CSSRAUDCMAN Service: Upgrade for Audit Creation Record - Manager

0.03 1

Service (CS) CSSRAWGEN Service: General Upgrade for Audit Records - Worker

0.00 3

Service (CS) CSSRAUDCWKR Service: Upgrade for Audit Creation Record - Worker

0.02 3

Service (CS) CS_KB_SYNC_SOLUTIONS_INDEX Knowledge Management Solution Index Synchronization

0.73 2

Service (CS) CS_KB_SYNC_STATEMENTS_INDEX Knowledge Management Statement Index Synchronization

0.12 1

Service (CS) CSSRAMGEN Service: General Upgrade for Audit Records - Manager

0.03 1

Service (CS) CSCHGLINENOMGR Charges: Upgrade for Line Number - Manager

0.03 1

Service (CS) CSCHGLINENOWKR Charges: Upgrade for Line Number - Worker

0.02 3

Service (CS) CS_SR_SYNC_TEXT_INDEX Service Request: Synchronize Text Index Program

1.08 2

Service (CS) CS_KB_SYNC_CATEGORIES_INDEX Knowledge Management Category Index Synchronization

0.05 1

Trade Management (OZF)

OZFEARNMV Refresh Materialized View 0.95 3

Trade Management (OZF)

OZFMIGUTLREC Migrate Accruals for Multi Currency Changes

0.55 9

Warehouse Management (WMS)

WMSGRULE Generate All Rules 1.05 2

XML Publisher (XDO)

XDOTMGEN XML Publisher Template Re-Generator

23.53 1

Total 431.05 1692

Sample Upgrade Timings

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.

Phase Time (sec.) first 24 con 55 seq 2 tab 22 tbm 18 pls 5 plb 19 dat 11 dfr 1 en 0

last 89 Invoker 90

Total 336 (5.5 min.)

The following timing information is for the Release 12.2 main upgrade driver (u10124646.drv) only

Phase-wise breakdown of time for upgrade:

Phase Time (in min.) first 0.31 con 2.75 seq 1.15 tab 4.83 tbm 16.98 os 0.03 pls 7.11 vw 3.14 plb 28.04 pda 2.75 daa 21.96 upa 0.08 pdt 2.57 dat 34.4 upg 102.2 dfr 1.06 en 8.00 last 98.04 Total 335.4 min. (5.59 hours)

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.

I/O Read bandwidth:

• Maximum I/O Read bandwidth (in MB): 10.23 • During upgrade I/O Reads ( in MB) per second range is from 1.44 to 10.23 • Max value is reported during dat and upg phase.

I/O Write bandwidth:

• Maximum I/O Write bandwidth (in MB): 3.09

• During upgrade I/O Writes per second range is from 0.9 to 3.09 MB. • Max value is reported during dat phase.

I/O Response Times ( in milliseconds):

• Below 20ms for the vast majority of AWR snapshot periods. Higher values were present with spikes above 50ms during the Large indexes create phase and some upgrade 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. Phase-wise breakdown of time needed for the upgrade:

Phase Time (min.) first 57.13 con 0.46 seq 0.8 tab 0.25 tbm 35.13 pls 2.65 last 3.53 Total 100 min. (1.6 hours)

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.

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1581299.1




Documents

1597531 A