This is the latest edition of Mike Swing’s book on upgrading to Oracle E-Business Suite R12.2.11. The book covers the nuances and lessons learned from many upgrades performed since Release 12 was first released.
Putting together the right team to tackle the Oracle E-Business Suite R12.2.11 upgrade, and understanding the issues that the team needs to consider to be successful, can be quite a challenge. “the little r12.2.11 upgrade essentials for managers and team members” describes the big picture of what you need to consider before tackling the Release 12.2.11 upgrade. Based on TruTek’s popular R11i to R12 Technical Upgrade training classes, this book describes what managers, functional, and technical team members need to know to prepare to upgrade from Release 11i to Release 12.2.11 of Oracle’s E-Business Suite of Applications. Enhanced topics with this edition include: Online Patching, the ADOP Patching Cycle, Materialized Views, Customizations, Development Standards for Edition Based Redefinition, How Cross-Edition Triggers Work, and Understanding the Release 12.2 Architecture.
See MOS Doc. ID: 1583092.1, E-Business Suite RUP, AD and TXK RUP Information and MOS Doc. ID: 1617461.1, Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2.
This AD-TXK codelevel has a dependency on Oracle Fusion Middleware:
For FMW 126.96.36.199, see Patch 20642039
For FMW 188.8.131.52, see Patch 20756887
However, if you are using startCD51, the version of FMW should be 184.108.40.206, and there should be no need to apply these patches. See MOS Doc. ID: 2073977.1, How To Find The Version Of Oracle Fusion Middleware Used By E-Business Suite Release 12.2.
Ensure all the required ETCC database objects will be found by the Delta 10 RUP installation process. This means that you must still run the latest version of ETCC on your database, even if you already have all the required database patches installed.
Use the checkMTpatch.sh script supplied in Patch 17537119 to check your Fusion Middleware version and identify the patches required by ETCC. For the database use checkDBpatch.sh.
You should check to see if there is a new version of the ETCC patch about every 30 days. The xml file that contains the list of recent patches is released about every 30 days. The ETCC scripts check to see if the xml file is older than 30 days, if so, they terminate. In the upgrade environment, you can query the contents of the TXK_TCC_RESULTS table to make sure the dates are current.
[WARNING] DB-ETCC: Bugfix XML file (./db/onprem/txk_R1220_DB_base_bugs.xml) is more than 30 days old. Check if a newer version is available in Patch 17537119.
In our case, on February 5th, the base_bugs.xml is more than 30 days old:
30465 Nov 1 09:47 txk_R1220_DB_base_bugs.xml, but the patch says it was updated 29 days ago:
There may be an error depending on the case of your servers listed in the TXK_TCC_RESULTS table. Check the case of the servers in the TXK_TCC_RESULTS table to make sure they are valid if you get an error on the TXK_TCC_RESULTS table.
select count(table_name) from all_tables where table_name=’TXK_TCC_RESULTS’;
select DATABASE_NAME, COMPONENT_NAME, CHECK_DATE, CHECK_RESULT, CHECK_MESSAGE from TXK_TCC_RESULTS;
Applying the latest AD/TXK Delta patches is highly recommended. AD/TXK Delta 11 was released in June 2019. One of the major changes in AD-TXK Delta 10 was the addition of a new context variable s_srvctl_thread_count. You can now tune the thread count with this new context variable, s_srvctl_thread_count to optimize startup and shutdown.
AD/TXK Delta 9 was released in March 2017. AD/TXK Delta 9 introduced full support for the Oracle Grid Listener used by ASM. The Grid Listener requires all registered service names to be unique. In AD/TXK Delta 8 and earlier, the service name for connections to the Patch Edition of the database was ebs_patch. In AD/TXK Delta.9, the service name to connect to the Patch Edition has been changed to <instance_name>_ebs_patch.
Apply the latest application tier technology patches to the run file system. Refer to MOS Doc.ID: 1355068.1, Oracle E-Business Suite 12.2 Patching Technology Components Guide for instructions on how to do this.
Start only the WebLogic Admin Server on the application tier.
$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start
Download and unzip the AD/TXK Delta 13 patches and run adgrants:
Execute adgrants.sql (currently version 89, by following the instructions in the readme of Patch 32394134, R12.AD.C.Delta.13.
The Release 12.2 database architecture has been modernized by adoption of the Oracle E-Business Suite System Schema, EBS_SYSTEM. Prior to the introduction of the EBS_SYSTEM schema, Oracle E-Business Suite installed application objects in the Oracle Database SYS and SYSTEM schemas. Migration to the EBS SYSTEM Schema obviates the need for any EBS-owned objects to reside in the SYS or SYSTEM schemas.
Key characteristics of the EBS_SYSTEM Schema include:
Creation of the EBS_SYSTEM schema and associated grant management is performed as follows:
Creation of the EBS_SYSTEM schema and is performed by SYS running the adgrants.sql script (supplying the APPS account as the parameter) before applying the AD-TXK Delta 13 RUPs.
Grants required by the APPS account are given by the apps_adgrants.sql script being run automatically by the AD-TXK Delta 13 RUP installation process. This script does not need to be run manually as part of normal patching operations.
All EBS database objects that currently reside in the SYS or SYSTEM schemas are migrated to appropriate Oracle E-Business Suite schemas. Depending upon the EBS object type and function, the object is migrated to EBS_SYSTEM, APPS, or APPS_NE.
All Oracle E-Business Suite administration actions (such as running adop, adadmin and other utilities) are now performed by EBS_SYSTEM.
Access to the Oracle database SYS and SYSTEM and the Oracle database server operating system is no longer required for Oracle E-Business Suite system administrative functions.
Oracle E-Business Suite is focused on revoking unnecessary privileges from the core EBS accounts as part of the implementation of the Defense in Depth and Least Privileges Model. This may impact custom code that runs in the EBS schemas and relies on these privileges. In these cases, you should consider separating the custom code into a separate schema, or, if that is not possible, adding the minimal required privileges back to the necessary account. For more information on interacting with EBS objects and code from a separate schema, refer to MOS Doc. ID: 2327836.1, Guidance for Providing Access to the Oracle E-Business Suite Database for Extensions and Third-Party Products.
To use the EBS System Schema, you need to be on Oracle E-Business Suite Release 12.2.3 or later.
Mandatory Patches and Steps
You must have available the following release update packs (RUPs) and other patches, ready to apply below in Section 3, in the order shown here.
AD Delta 13 (or later) and TXK Delta 13 (or later) — Support for EBS System Schema Migration was introduced in the Oracle Applications DBA (AD) and Oracle E-Business Suite Technology Stack (TXK) Delta 13 release update packs. Previous releases of AD and TXK included database objects owned by AD or TXK that resided in the Oracle Database SYS or SYSTEM schemas, and also included references to private Oracle database SYS or SYSTEM objects.
With AD Delta 13 and TXK Delta 13, EBS database objects are migrated from SYS and SYSTEM into the EBS_SYSTEM, APPS, or APPS_NE schemas. All relevant object references are updated to point to the migrated objects in the APPS or APPS_NE schemas.
AD Delta 13 and TXK Delta 13 also update all code that previously referenced private Oracle Database SYS and SYSTEM objects, to reference Oracle Database approved public objects or public APIs instead.
EBS 12.2.11 RUP, or EBS Release 12.2.3—12.2.10 and EBS System Schema Migration Consolidated Patch — Oracle E-Business Suite Releases 12.2.3—12.2.10 include EBS-owned database objects that reside in the database SYS or SYSTEM schemas, or reference database SYS or SYSTEM objects. The EBS System Schema Migration Consolidated Patch (also referred to as the Consolidated Patch) migrates these objects to the appropriate EBS schemas. The EBS 12.2.11 RUP includes the Consolidated Patch.
Note: Oracle E-Business Suite Release 12.2.11 and later do not install EBS objects in the SYS or SYSTEM schemas, and so do not require the EBS System Schema Migration Consolidated Patch.
Before proceeding with application of the final patch in Step 4, you must update any customizations that have been identified with mandatory compliance requirements. For guidance, refer to MOS Doc. ID: 1577661.1, Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2.
EBS System Schema Migration Completion Patch — Although it is possible to apply AD-TXK Delta 13 and the EBS System Schema Migration Consolidated Patch without applying the EBS System Schema Migration Completion Patch immediately afterwards, the migration is not finished until the Completion Patch has been applied. This patch drops AD, TXK, and EBS product code in the database SYS or SYSTEM schemas, and removes any final restricted references to database SYS or SYSTEM objects.
Prior to applying the Completion Patch, you must apply the following prerequisite patches:AD-TXK Delta 13
Either the EBS 12.2.11 RUP or the EBS System Schema Migration Consolidated Patch
The Completion Patch will fail to apply if you do not apply these patches first.
You should also download and unzip any applicable patches from Section 4. Apply Additional Critical Patches of MOS Doc ID: 1617461.1, Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2, which introduces R12.AD.C.Delta.12 and R12.TXK.C.Delta.12. The following are the critical patches as of February 6, 2020. Run adgrants.sql, from Patch 32394134, which delivers a newer version of adgrants (adgrants.sql.65). This is the proper version of adgrants.sql. Then, apply this critical AD patch:
From MOS Doc. ID: 1617461.1, Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2: On the Run Edition, apply Patch 32394134 (R12.AD.C.Delta.13) and Patch 32392507:R12.AD.C in Hotpatch Mode. Do not merge any other patches in this step.
It is mandatory that you have already installed Oracle E-Business Suite Release 12.2 using the latest startCD (220.127.116.11 – Patch 22066363) along with Patch 32947483 (Rapid Install consolidated one-off bundle on top of startCD51).
Run the Online Patching Enablement Reports. From MOS Doc. ID: 1531121.1, Using the Online Patching Readiness Report in Oracle E-Business Suite Release 12.2:
ADZDPSUM.sql Lists schemas containing objects that reference EBS objects that are not editioned. If the schemas are registered with the application, the Online Patching Enablement patch will enable editioning on those schemas avoiding many EBR rule violations (Non-Editioned objects referencing Editioned objects).
sqlplus system @$AD_TOP/sql/ADZDPSUM.sql
mv adzdpsum.txt adzdpsum_pre_dbprep.txt
From ADZDPSUM.sql, see the full report in the attachments:
DOC> DOC> Schemas that will be editioned upon Online Patching Enablement.
ETL_USER EBS Product — registered before the 12.2 upgrade
HYPERION_USER Custom — not registered before the upgrade
ADZDPMAN.sql Lists objects that violate EBR standards and that require manual intervention in order to address the violations. It groups the objects per violation type and provides instructions on how to address those violations.
sqlplus system @$AD_TOP/sql/ADZDPMAN.sql
mv adzdpman.txt adzdpman_pre_dbprep.txt
ADZDPAUT.sql Lists objects that violate Online Patching Enablement standards. The objects in this report will be adjusted automatically by the Online Patching Enablement patch. This report is provided for information purposes only, no action is required on the output of this report.
sqlplus system @$AD_TOP/sql/ADZDPAUT.sql
mv adzdpaut.txt adzdpaut_pre_dbprep.txt Fix any violations -Oracle recommends that you perform the chosen fix by customizing the template file
Go to edelivery.oracle.com, navigate to the Oracle E-Business Suite 12.2.0 Current
Choose Oracle E-Business Suite 12.2.0 Current
Agree to the Terms and Conditions
Agree to the license agreement and Continue, then download these files.
Unzip and build the rapidwiz stage directory
Use startCD51 for the upgrade, This is the latest startCD. (R12.AD.C.Delta.10 startcd51 – Patch 22066363).
Unzip the following patch using the following command:
Change to the 32947483 directory.
Patch the Rapid Install stage area using the following command:
For Oracle Solaris on SPARC (64-bit) and IBM AIX on Power Systems (64-bit): after executing patchRIStage.sh to patch the existing Rapid Install stage area, you must re-run buildStage.sh with the option “Copy patches to existing stage area”. This is to incorporate additional platform-specific fixes into the Rapid Install Stage area for these platforms. The script should be run with the same user that was used to create the stage area.
Premier Support for Oracle E-Business Suite Release 12.2 through at least Dec 2032.
Premier Support is available for Oracle E-Business Suite Release 12.1 through Dec 2021. After Dec 2021, Market Driven Support (MDS) will be available for 2022 and 2023. Additional details regarding MDS for Oracle E-Business Suite 12.1.3 will be published soon.
Follow the process documented in the following to determine eligibility for the waiver to database Extended Support fees: MOS Doc. ID: 2522948.1, Extended Support Fee Waiver for Oracle Database 12.1 and 11.2 for Oracle E-Business Suite.
Due to the certification timing of Oracle E-Business Suite with Oracle Database versions beyond 12.1, Oracle has waived Extended Support license uplift fees for
Oracle Database 12.1 through 31 July 2022 licenses used for Oracle E-Business Suite and Oracle Database 11.2 Extended Support ended December 2020
Extended Support license uplift fees ended Extended Support December 31, 2020, for 18.104.22.168 databases used for Oracle E-Business Suite
ACS Market Driven Support (MDS) available for 22.214.171.124 databases after December 2020
This Extended Support license uplift fee waiver will be specific to the Oracle Database licenses, within your company’s footprint, that you use for running Oracle E-Business Suite software.
If you have already paid your Oracle Database Extended Support license uplift fees, you may be eligible to receive a credit that we will apply against your Oracle account.
Per MOS Doc. ID: 2580629.1, Interoperability Notes: Oracle E-Business Suite Release 12.1 with Oracle Database 19c:
When upgrading your Oracle E-Business Suite to Oracle Database 19c, your database will be converted to the multitenant architecture, with a Container Database (CDB) and a single Pluggable Database. Only multitenant architecture databases are certified for Oracle E-Business Suite with Oracle Database 19c.
During the upgrade, you will also perform steps to migrate directories defined for PL/SQL File I/O to database directory objects. This requirement is due to the desupport in Oracle Database 19c of the UTL_FILE_DIR database initialization parameter.
Oracle 19c Database Release Update Information for Oracle E-Business Suite:
Oracle Database Release Update 19.3 as well as Release Update 19.5 and later are certified.
Oracle recommends that you upgrade to the latest Oracle Database Release Update that is certified with Oracle E-Business Suite. Applying the latest Release Update will ensure that you have the security-related fixes and high-priority non-security fixes. See MOS Doc. ID: 2285040.1, Release Update Introduction and FAQ, for more details.
You can upgrade directly from an earlier Oracle Database version to either:
Oracle Database 19c Release Update 19.3
Oracle Database 19c Release Update 19.6 or a later Oracle E-Business Suite certified RU.
You can upgrade to Oracle Database 19c Release Update 19.5 indirectly:
Upgrade from your earlier Oracle Database version to Oracle Database 19c Release Update 19.3
EBS Technology Patch Automation Tool for Application Tier (ETPAT-AT)
The EBS Technology Patch Automation Tool for Application Tier automates patching of technology one-offs for the following components of the Oracle E-Business Suite Release (EBS) Release 12.2.0 application tier.
– FMW WebTier 126.96.36.199
– Oracle WebLogic Server 10.3.6 Smart Update Patch
– Oracle WebLogic Server 10.3.6.0
– FMW oracle_common 188.8.131.52
– Forms and Reports 10.1.2.3
ETPAT-AT can be run on an EBS Release 12.2.0 application tier (run file system) for new installations or upgrades. This tool cannot be used on EBS systems that are already at Release 12.2.3 or later.
Run the following command to start ETPAT-AT:
$ perl etpat_at.pl
EBS Technology Patch Automation Tool for Application Tier (ETPAT-AT) (Doc ID 2749774.1)
Different logs are created for Run Edition and Patch Edition Cloning. The log files are created in the following directories in the Run Edition File System:
Per the instructions in MOS Doc. ID: 1383621.1, Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone:
If the database version is 12c Release 1, you must add the following line in your sqlnet_ifile.ora after adcfgclone.pl execution completes:
SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8 (if the initialization parameter SEC_CASE_SENSITIVE_LOGON is set to FALSE)
SQLNET.ALLOWED_LOGON_VERSION_SERVER = 10 (if SEC_CASE_SENSITIVE_LOGON is set to TRUE)
Don’t use a HOSTNAME in UPPER CASE.
Bug 23343062 – Incorrect Patch File System context file with dualfs option when hostname is in uppercase
On a host with uppercase name, the dualfs option of Cloning may result in the context name and context file name being out of sync between the Run and Patch File System. This can happen if the context name or other context variables containing hostname are specified in the pairsfile with the host value in upper case. For example, on host TEST_HOST with database SID prod, if the pairsfile contains the entry s_contextname=prod_TEST_HOST, the Run File System context name and context file name will be set to prod_TEST_HOST and prod_TEST_HOST.xml respectively while the Patch File System context name and context file name will be set to prod_test_host and prod_test_host.xml respectively. This will lead to validation errors during adop execution. To avoid this issue, in case the s_contextname or other context variables containing the hostname are specified in the pairsfile, the specified value should always have the host in lower case.
One recent change that came from either a CPU patch or AD-TXK patch affects cloning. You now need to create an etcc directory under the database Oracle Home, $ORACLE_HOME/appsutil/etcc.
From MOS Doc. ID: 1383621.1, Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone:
“Run EBS Technology Codelevel Checker (ETCC) on the database tier.
On the database tier, run the EBS Technology Codelevel Checker (ETCC) described in MOS Doc. ID: 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes to confirm that all required database patches have been applied. EBS Technology Codelevel Checker (ETCC) is available via Patch 17537119 and analyzes an Oracle Database Oracle Home, and warns of any missing database bug fixes required for Oracle E-Business Suite Release 12.2. It is run with the command checkDBpatch.sh (on UNIX) or checkDBpatch.cmd (on Windows). Further instructions are available in the patch readme. Ensure to install the latest version of ETCC into the directory:
Before cloning a system with Rapid Clone, be sure to allow any active online patching cycles to run all the way through the final (cleanup) phase. In case patches are applied in Hotpatch or Downtime Mode, then you must run the cleanup phase of adop. Review Oracle E-Business Suite Maintenance Guide.
Then run fs_clone to synchronize with the other file system, to avoid the need for synchronization to be performed in the next patching cycle. For more information, review Oracle E-Business Suite Maintenance Guide.
A global (central) inventory is generally recommended for all Oracle E-Business Suite Release 12.2 application tier nodes and database tier nodes.