12.2.11 RUP Patch 31856789

1.       The EBS Release 12.2.11 RUP (Patch 31856789) was released on November 9 2021, in MOS Doc. ID: 2758997.1, Oracle E-Business Suite Release 12.2.11 Readme New Features in R12.AD.C.Delta.7 and R12.TXK.C.Delta.7. It includes suite-wide and family-level granularity (unlike Release 12.2.3 and Release 12.2.2). You should apply the Release 12.2.11 RUP using Downtime Mode: 

$ adop phase=apply patches=31856789  apply_mode=downtime

$ . <INSTALL_BASE>/EBSapps.env run
$ adop phase=cleanup

$ adop phase=fs_clone

  • Apply the Oracle E-Business Suite Online Help for 12.2.11 Release Update Pack using adop Hotpatch Mode on the Run File System. Oracle strongly recommends installing this patch.

$ adop phase=apply patches=31856799 hotpatch=yes

  • Grant Flexfield Value Set Access to specific users (required). Release12.2 includes a new security feature, Flexfield Value Set Security. It controls who can create or modify flexfield values in the Flexfield Values Setup window (FNDFFMSV). These are mandatory setup steps before any users can create or update values in the Values window.

However, if you choose not to implement Flexfield Value Set Security upon upgrading to or installing Release 12.2, you have two options to give users access to all Value Sets for backwards compatibility:

  1. Assign the seeded unlimited-access role (“Flexfield and Report Values: All privileges”) directly to users, responsibilities, or roles. With this option, users who have function security access to the Segment Values form and have this role either directly or indirectly can see, insert, and update values for any value set.
  2. Create an “all-value-sets, all-privileges, all-users”. With this option, any users who have function security access to the Segment Values form can view, insert, and update values for any value set.
  • Register new/custom products (conditional).

After completing the steps to update all database tier nodes with the latest code level, perform the post-update steps for HR Legislative only if you have licensed that module. Refer to the Human Resources tasks step from MOS Doc. ID: 2230783.1, Oracle E-Business Suite Release 12.2.7 Readme. Follow MOS Doc. ID: 2393232.1, Applying the R12.HR_PF.C.Delta.12 Release Update Pack.

  • If you are an E-Business Suite Information Discovery customer, see MOS Doc. ID: 2214431.1, Installing Oracle E-Business Suite Information Discovery, Release 12.2 V8.
  • If you support languages other than American English, perform NLS-related Step (conditional) from MOS Doc. ID: 2495027.1, Oracle E-Business Suite Release 12.2.11 Readme.
  • Run Patch Wizard for current recommended and high priority product patches. See MOS Doc. ID: 1400757.1, How to Find E-Business Suite Recommended Patches.

Patch Wizard is a tool included with Oracle Application Manager. Patch Wizard reviews recommended and high priority patches against those that have been applied on your system. Patches can be downloaded and merged using the tool. You can review patch impact to determine how a specific patch or several patches will affect your system. Review MOS Doc. ID: 976188.1, Patch Wizard Utility.

If your environment does not allow the Patch Wizard utility, review MOS Doc. ID: 1400757.1, How to Find Oracle E-Business Suite Recommended Patches.

  • Perform the following three checks to verify the directory service assignments:
  • Log in to Oracle E-Business Suite as the SYSADMIN user and check whether the Application Diagnostics responsibility appears for this user in the navigator. If not, then run the Workflow Directory Services User/Role Validation Concurrent Program with the parameters listed below.
  • Run the following SQL query:
  • SQL> SELECT ASSIGNING_ROLE, LAST_UPDATE_DATE, USER_ORIG_SYSTEM, USER_ORIG_SYSTEM_ID, ROLE_ORIG_SYSTEM, ROLE_ORIG_SYSTEM_ID FROM WF_USER_ROLE_ASSIGNMENTS WHERE USER_NAME = ‘SYSADMIN’ AND ROLE_NAME = ‘FND_RESP|FND|APPLICATION_DIAGNOSTICS|STANDARD’;
  • If the originating system or originating system ID is null for either the user or the role in any of the records returned by this query, then run the Workflow Directory Services User/Role Validation Concurrent Program with the parameters listed below.
  • Run the following SQL query to obtain the originating system ID of the Application Diagnostics responsibility in your Oracle E-Business Suite instance:

SQL> SELECT ORIG_SYSTEM_ID FROM WF_LOCAL_ROLES WHERE NAME = ‘FND_RESP|FND|APPLICATION_DIAGNOSTICS|STANDARD’;

Next, run the following SQL query, replacing <RESP_ID> with the originating system ID returned by the previous query:

SQL> SELECT * FROM FND_USER_RESP_GROUPS WHERE RESPONSIBILITY_ID = <RESP_ID> AND USER_ID = 0;

If this query does not return any rows, then run the Workflow Directory Services User/Role Validation concurrent program with the parameters listed below.

To update the assignment records for the SYSADMIN user, run the Workflow Directory Services User/Role Validation concurrent program with the following parameters:

  • Batch size: 10000 (the default value)
  • User name: SYSADMIN
  • Role name:  FND_RESP|FND|APPLICATION_DIAGNOSTICS|STANDARD
  • Fix dangling users: No
  • Add missing user/role assignments: Yes
  • Update WHO columns in WF tables: Yes
  • Number of Parallel Processes: Optionally specify the number of parallel processes you want to use when running the program.

Apply the Latest AD/TXK RUP11 Patches

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 11.1.1.6, see Patch 20642039
  • For FMW 11.1.1.7, see Patch 20756887

However, if you are using startCD51, the version of FMW should be 11.1.1.9, 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:

grep Header <ETCC_LOC>/db/onprem/txk_R1220_DB_base_bugs.xml

grep Header <ETCC_LOC>/db/onprem/txk_R1220_DB_mappings.xml

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.

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

Requirements for Using the EBS System Schema

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.

Prerequisites

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.

  1. 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_SYSTEMAPPS, 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.
  2. 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:

Patch 29591102:R12.AD.C

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

$ adop phase=apply patches=32394134  merge=yes hotpatch=yes

It is mandatory that you have already installed Oracle E-Business Suite Release 12.2 using the latest startCD (12.2.0.51 – Patch 22066363) along with Patch 32947483 (Rapid Install consolidated one-off bundle on top of startCD51).

Apply AD Critical Patches

$adop phase=apply patches=33862025 merge=yes hotpatch=yes

$ adop phase=apply patches=32392507, 33535778 merge=yes hotpatch=yes

  • Apply Patch 27911576:R12.OWF.C

adop phase=apply patches= 27911576 hotpatch=yes

  • Run admkappsutil.pl on the apps tier and copy the appsutil.zip to the database tier, $ORACLE_HOME directory.

Synchronize values of APPLPTMP with UTL_FILE_DIR in 12.2 and 19c

  • Synchronize values of APPLPTMP with UTL_FILE_DIR for PL/SQL-based Concurrent Requests.

For Oracle Database 19c, you can retrieve the value of UTL_FILE_DIR by using the following command as the APPS user:

SQL> select value from v$parameter where name=’utl_file_dir’;

See My Oracle Support Knowledge Document 2525754.1, Using UTL_FILE_DIR or Database Directories for PL/SQL File I/O in Oracle E-Business Suite Releases 12.1 and 12.2 for more information

3.       Set the target UTL_FILE_DIR values in the Oracle Database

Starting with Oracle Database 19c, UTL_FILE_DIR is not a supported database initialization parameter.

Set the target UTL_FILE_DIR values in the database.

Source the environment file.

cd <ORACLE_HOME>
source <CONTEXT_NAME>.env

10.  Obtain the existing value for the UTL_FILE_DIR using the following commands:

perl <ORACLE_HOME>/appsutil/bin/txkCfgUtlfileDir.pl -contextfile=<DB Context File> \
-oraclehome=<ORACLE_HOME> -outdir=<ORACLE_HOME>/appsutil/log -mode=getUtlFileDir

This will create a text file  <DB_NAME>_utlfiledir.txt under the <ORACLE_HOME>/dbs directory with references to the target Oracle home.

  1. Review the <DB_NAME>_utlfiledir.txt file and edit the values, if required.

Note: Before proceeding to the next step, ensure to create the physical directories for all directory paths being specified in the <DB_NAME>_utlfiledir.txt file.

  1. Run the following command to store the updated values for UTL_FILE_DIR in the database:

cd <ORACLE_HOME>/appsutil/bin
perl <ORACLE_HOME>/appsutil/bin/txkCfgUtlfileDir.pl -contextfile=<DB Context File> \
-oraclehome=<ORACLE_HOME> -outdir=<ORACLE_HOME>/appsutil/log \
-mode=setUtlFileDir

This command will validate the directory paths provided in the <DB_NAME>_utlfiledir.txt for existence and will also create directory objects for all the physical directory paths.

  1. Run the following command to create the directory object for the outbound directory (pointed to by the s_outbound_dir context variable in the database tier context file).

perl <ORACLE_HOME>/appsutil/bin/txkCfgUtlfileDir.pl -contextfile=<DB Context File> \
-oraclehome=<ORACLE_HOME> -outdir=<ORACLE_HOME>/appsutil/log -mode=createDirObject

When prompted for the OS path for the directory object to be created, enter the value of the s_outbound_dir context variable in the database tier context file.

  1. Sync up the value of UTL_FILE_DIR in the database tier context file by running the following command:

perl <ORACLE_HOME>/appsutil/bin/txkCfgUtlfileDir.pl -contextfile=<DB Context File> \ -oraclehome=<ORACLE_HOME> -outdir=<ORACLE_HOME>/appsutil/log -mode=syncUtlFileDir \ -skipautoconfig=yes

  1. Run AutoConfig on the database tier nodes:

adconfig.sh contextfile=/u01/app/oracle/product/db12102/etest/appsutil/etest_etestdb.xml

Download 12.2.0 files from edelivery.oracle.com

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.

V100052-01_1of3.zip

V100052-01_2of3.zip

V100052-01_3of3.zip

V100053-01_1of2.zip

V100053-01_2of2.zip

V100054-01.zip

V100055-01.zip

V100056-01.zip

V100057-01.zip

V100058-01.zip

V100059-01_1of2.zip

V100059-01_2of2.zip

V100060-01_1of3.zip

V100060-01_2of3.zip

V100060-01_3of3.zip

V100061-01.zip

V100102-01.zip

V1002910-01

V1002910-01.zip

V1006971-01.zip

V1006972-01_1of2.zip

V1006972-01_2of2.zip

V1006973-01.zip

V29856-01.zip

V35802-01.zip

V35803-01_1of3.zip

V35803-01_2of3.zip

V35803-01_3of3.zip

V35804-01_1of2.zip

V35804-01_2of2.zip

V46095-01_1of2.zip

V46095-01_2of2.zip

V75792-01.zip

V861706-01_1of4.zip

V861706-01_2of4.zip

V861706-01_3of4.zip

V861706-01_4of4.zip

V886647-01.zip

V995061-01_1of5.zip

V995061-01_2of5.zip

V995061-01_3of5.zip

V995061-01_4of5.zip

V995061-01_5of5.zip

V998894-01

V998894-01.zip

V998895-01_1of2.zip

V998895-01_2of2.zip

V999625-01_10of11.zip

V999625-01_11of11.zip

V999625-01_1of11.zip

V999625-01_2of11.zip

V999625-01_3of11.zip

V999625-01_4of11.zip

V999625-01_5of11.zip

V999625-01_6of11.zip

V999625-01_7of11.zip

V999625-01_8of11.zip

V999625-01_9of11.zip

Unzip and build the rapidwiz stage directory

  1. Use startCD51 for the upgrade, This is the latest startCD. (R12.AD.C.Delta.10 startcd51 – Patch 22066363).
  2. Unzip the following patch using the following command:

              unzip p32947483_R12_GENERIC.zip

  • Change to the 32947483 directory.
  • Patch the Rapid Install stage area using the following command:

              sh patchRIStage.sh

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

Support for Database and E-Business Suite releases in 2022

According to MOS Doc. ID: 2655839.2, Information Center: Oracle Database 19c with Oracle E-Business Suite 12.2 and 12.1:

  1. Lifetime Support Stages and Benefits of Lifetime Support (https://www.oracle.com/support/lifetime-support/)
  2. The Applications Unlimited Lifetime Support Policy is available here:
    1. https://www.oracle.com/support/lifetime-support/resources.html
    1. https://www.oracle.com/support/lifetime-support/applications-unlimited.html
    1. Premier Support for Oracle E-Business Suite Release 12.2 through at least Dec 2032.
    1. 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.
  3. According to MOS Doc. ID: 742060.1, Database: Release Schedule of Current Database Releases
    1. 19c Long Term Release
      1. Premier Support (PS) ends April 30, 2024, Extended Support (ES) fees will be required beginning May 01, 2024, through April 30, 2027
      1. Error Correction / Patching is available through April 30, 2027, with paid ES. Without paid ES, patching is only available until April 30, 2024
    1. Extended Support for Database 12.1.0.2 through July 31, 2022. Oracle E-Business Suite customers may be eligible for a waiver to Extended Support Fees through July 31, 2022.
    1. Database 11.2.0.4 is in sustaining support. As of December 31, 2020, Market Driven Support (MDS) is available for Database 11.2.0.4. For more information see: Oracle Market Drive Support for Oracle Database 11g Release 2

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 11.2.0.4 databases used for Oracle E-Business Suite
    • ACS Market Driven Support (MDS) available for 11.2.0.4 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.

The Lifetime Support section of the Oracle Software Technical Support Policies documents the Extended Support license uplift fee waiver. 


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
      • Apply Oracle Database Release Update 19.5.

EBS Technology Patch Automation Tool for Application Tier (ETPAT-AT)

The following middle tier tech stacks are part of the middle tier and all patches in the recommendations should be applied to these components of the middle tier:

  • Oracle Forms and Reports 10.1.2.3.0
  • Oracle Fusion Middleware (FMW) – Web Tier 11.1.1.9.0
  • RSF within FMW Web tier 11.1.0.7.0
  • Oracle Fusion Middleware (FMW) – oracle_common 11.1.1.9.0
  • Oracle WebLogic Server (WLS) 10.3.6.0.7

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 11.1.1.9

 – Oracle WebLogic Server 10.3.6 Smart Update Patch

 – Oracle WebLogic Server 10.3.6.0

 – FMW oracle_common 11.1.1.9

 – 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)

Steps to Complete a Clone in Release 12.2 – Part 9

Part 7: Finishing Tasks

Finishing tasks consists of applying any customizations that may be needed in your environment.

In our case, we do the following “Branding” change for the <TARGET_DB_SID> environment:

Default Branding Change

  • Login page Message (on the page)

cd $OA_MEDIA
mv oracle_white_logo_CUSTOM.png oracle_white_logo.png

Start the application tier processes.

  • Site Name Profile Change

Login > System Administrator > Profile System

Search for the Site Name profile.

Update the site level profile option to: <TARGET_DB_SID> – Clone of <SOURCE DB SID> as of XX/XX/XX

Close the forms session, then connect again to validate the changes took effect.

Steps to Complete a Clone in Release 12.2 – Part 8

Log File Locations

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:

<INST_TOP>/admin/log/clone/run

<INST_TOP>/admin/log/clone/patch

Potential Issues

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

 <RDBMS_ORACLE_HOME>/appsutil/etcc

Cloning/Patching Nuances

  1. 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.
  2. 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.
  3. A global (central) inventory is generally recommended for all Oracle E-Business Suite Release 12.2 application tier nodes and database tier nodes.

Steps to Complete a Clone in Release 12.2 – Part 7

6.2 RUN ADPRECLONE ON RUN EDITION 

Run adpreclone.pl on the run edition file system in the Target System.

$ cd $ADMIN_SCRIPTS_HOME

$ adpreclone.pl appsTier

**require Apps User password and Weblogic AdminServer password

6.3 SHUTDOWN THE APPLICATION TIER PROCESSES

cd $ADMIN_SCRIPTS_HOME

./adstpall.sh apps/<apps_password>
**require Apps User password and Weblogic AdminServer password

6.4 Copy Target Run Edition Over Target Patch Edition

Now we need to copy the EBSapps directory from the run edition file system to the patch edition file system on the target application server.

Create the TARGET PATCH EDITION file system (in our case $ORACLE_HOME/<TARGET_DB_SID>/fs2), if it does not already exist:

cd $ORACLE_BASE
mkdir fs2
cd ./fs1
tar –cvf EBSapps.tar EBSapps
mv EBSapps.tar ../fs2
cd ../fs2
tar –xvf EBSapps.tar

Once this is complete, remove the TAR file:
rm –fr EBSapps.tar

IMPORTANT! – Unset the application environment if it set. This is done by logging out of the OS and logging back in making sure not to set the EBS environment.

$ cd $ORACLE_HOME/<TARGET_DB_SID>/fs2

6.5 Run ADCFGCLONE on Target Application Node on Patch Edition

The patch edition file system uses the RUN edition context XML file. At the prompt “Location of Run System Context File”, enter the absolute path to the context file for the run edition file system that was created in the previous step:

In our environment, the path is:
$ORACLE_HOME/<TARGET_DB_SID>/fs1/inst/apps/<TARGET_DB_SID>_apps1/appl/admin/<TARGET_DB_SID>_apps1.xml

Also the PATCH file system port pool MUST be different than RUN file system port pool (0).

Log on to the patch edition file system in the Target System as the applmgr user and enter the following commands:

$ cd $ORACLE_HOME/<TARGET_DB_SID>/fs2/EBSapps/

comn/clone/bin

$ perl adcfgclone.pl appsTier

                   Copyright (c) 2002, 2015 Oracle Corporation

             Redwood Shores, California, USA

          Oracle E-Business Suite Rapid Clone

                   Version 12.2

          adcfgclone Version 120.63.12020000.56

                ***********************************************************

In AD-TXK Delta 7, we recommend you clone the run and patch file systems in a single operation using the ‘dualfs’ option.

Separate cloning of the run and patch file systems will be deprecated

                ************************************************************

Enter the APPS password :

Enter the Weblogic AdminServer password :

Do you want to add a node (yes/no) [no] :

Running: Context clone…

Log file located at $ORACLE_HOME/<TARGET_DB_SID>/fs2/EBSapps/comn/clone/bin/CloneContext_1230145305.log

Target System File Edition type [run] : patch

Enter the full path of Run File System Context file : $ORACLE_HOME/<TARGET_DB_SID>/fs1/inst/apps/<TARGET_DB_SID>_apps1/appl/admin/<TARGET_DB_SID>_apps1.xml

Provide the values required for creation of the new APPL_TOP Context file.

Target System Fusion Middleware Home set to $ORACLE_HOME/<TARGET_DB_SID>/fs2/FMW_Home

Target System Web Oracle Home set to $ORACLE_HOME/<TARGET_DB_SID>/fs2/FMW_Home/webtier

Target System Appl TOP set to $ORACLE_HOME/<TARGET_DB_SID>/fs2/EBSapps/appl

Target System COMMON TOP set to $ORACLE_HOME/<TARGET_DB_SID>/fs2/EBSapps/comn

Target System Instance Top set to $ORACLE_HOME/<TARGET_DB_SID>/fs2/inst/apps/<TARGET_DB_SID>_apps1

Target System Port Pool [0-99] : 1

Checking the port pool 1

done: Port Pool 1 is free

UTL_FILE_DIR on database tier consists of the following directories.

1. /usr/tmp

2. /usr/tmp

3. $ORACLE_HOME/<TARGET_DB_SID>/12.1.0/appsutil/

outbound/<TARGET_DB_SID>_data1

4. /usr/tmp

Choose a value which will be set as APPLPTMP value on the target node [1] : 1

6.6 Start Application from Run File System and Review

Set RUN file system environment:

. ~/EBSapps.env

Make sure to select the RUN file system when prompted.

Start Application:

$ cd $ADMIN_SCRIPTS_HOME

$ ./ adstrtal.sh

**require Apps User password and Weblogic AdminServer password

From EBS side you can do these checks:

  1. Login to the application. Check that Apache, forms sessions are coming up.
  2. Run Synchronize views for Oracle Workflow

Request Name = Workflow Directory Services User/Role Validation

p_BatchSize = 10000

p_Check_Dangling = Yes

Add missing user/role assignments = Yes

Update WHO columns in WF tables = No

  • Check Concurrent Manager processes.
  • Run a simple Concurrent Program (like the Active Users report). Check if output and log files can be opened.
  • If required, purge old log/out files from $APPLCSF/$APPLLOG and $APPLCSF/$APPLOUT directories as you may find that the output/log files have old dates.

Steps to Complete a Clone in Release 12.2 – Part 7

Part 4: Copy Database Tier Node

For copying the database tier node from source to target database you can always follow the easiest approach of copying the database files from source to target database by first shutting down the source database system. But not all DBAs have the luxury of taking down their Production database at will to refresh a non-production database.

4.1 Stop Target Database – If Required

Login to the target Database node as the oracle software user.

$ sqlplus / as sysdba

SQL> shutdown immediate

4.2 Cleanup Target Database File

Delete all target data files.

Use a simple rm –rf command to delete these database files

4.3 Restore Your Production Database to the Target Database Server Using the Method of Your Choice

Part 5: Configure Target Database System

Log on to the Target System as the oracle user and enter the following commands to configure the adcfgclone dbTechStack

$ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin

$ perl adcfgclone.pl dbTechStack

The log file is created in the <RDBMS_ORACLE_HOME>/appsutil/log/<CONTEXT_NAME> directory.

Answer the adcfgclone script questions and allow the script to run to completion.

5.1 De-Register the Production Nodes from the Configuration

As the APPS user, run the following command to de-register the current configuration:

Login from the target database node as the APPS user:

$ sqlplus apps/<PASSWORD>

SQL> exec fnd_conc_clone.setup_clean;

PL/SQL procedure successfully completed.

SQL> commit;

Commit complete.

5.2 Execute Autoconfig on Target Database Node

On the target database node from the $ORACLE_HOME/appsutil/bin directory, execute AutoConfig on the database tier by running the adconfig.pl script.

$ cd $ORACLE_HOME/appsutil/bin
$ perl adconfig.pl dbTier

Check the AutoConfig log for any errors.

Also check the CONTEXT_FILE that was generated under $ORACLE_HOME/appsutil

Part 6: Configure Target Application System

Configuring the target system changes instance settings from the source settings to the target settings that match the target hostname, target instance name, SID, paths and ports.

NOTES:

  • At the prompt Do you want to add a node (yes/no), enter the value no.
  • At the prompt: Target System Base Directory, enter the location of the base directory. For example: /u01/oracle/VIS.
  • Provide the new port pools for the Run Edition File System and the Patch Edition File System.
  • When asked the question Do you want to startup the Application Services for <TWO_TASK>? (y/n) you should answer y if you do not need to perform any further actions and n if there are other pending actions that need the Application services to be down.

6.1 Run ADCFGCLONE on Target Application Node Run Edition

Login to the Application node as the OS Apps user.

$ cd $COMMON_TOP/clone/bin

Example :

$ cd $ORACLE_HOME/<TARGET_DB_SID>/fs1/EBSapps/comn/

clone/bin

$ perl adcfgclone.pl appsTier

**This step requires the Apps User password AND the Weblogic Server Admin password

perl adcfgclone.pl appsTier

      Copyright (c) 2002, 2015 Oracle Corporation

             Redwood Shores, California, USA

            Oracle E-Business Suite Rapid Clone

                      Version 12.2

         adcfgclone Version 120.63.12020000.56

               ****************************************************

In AD-TXK Delta 7, we recommend you clone the run and patch file systems in a single operation using the ‘dualfs’ option.

Separate cloning of the run and patch file systems will be deprecated

                ***************************************************

Enter the APPS password :

Enter the Weblogic AdminServer password :

Do you want to add a node (yes/no) [no] :

Running: Context clone…

Log file located at $ORACLE_HOME/<TARGET_DB_SID>/fs1/EBSapps/comn/clone/bin/CloneContext_1230123711.log

Target System File Edition type [run] :

Provide the values required for creation of the new APPL_TOP Context file.

Target System Hostname (virtual or normal) [apps1] :

Target System Database SID : <TARGET_DB_SID>

Target System Database Server Node [apps1] : data1

Target System Database Domain Name [dg.local] :

Target System Base Directory : $ORACLE_HOME/<TARGET_DB_SID>

Target System Base Directory set to $ORACLE_HOME/<TARGET_DB_SID>

Target System Current File System Base set to $ORACLE_HOME/<TARGET_DB_SID>/fs1

Target System Other File System Base set to $ORACLE_HOME/<TARGET_DB_SID>/fs2

Target System Fusion Middleware Home set to $ORACLE_HOME/<TARGET_DB_SID>/fs1/FMW_Home

Target System Web Oracle Home set to $ORACLE_HOME/<TARGET_DB_SID>/fs1/FMW_Home/webtier

Target System Appl TOP set to $ORACLE_HOME/<TARGET_DB_SID>/fs1/EBSapps/appl

Target System COMMON TOP set to $ORACLE_HOME/<TARGET_DB_SID>/fs1/EBSapps/comn

Target System Instance Home Directory [$ORACLE_HOME/<TARGET_DB_SID>] :

Target System Instance Top set to $ORACLE_HOME/<TARGET_DB_SID>/fs1/inst/apps/<TARGET_DB_SID>_apps1

Do you want to preserve the Display [<Target_App_Server>:0.0] (y/n)  : n

Target System Display [apps1:0.0] : :1

Target System Root Service [enabled] :

Target System Web Entry Point Services [enabled] :

Target System Web Application Services [enabled] :

Target System Batch Processing Services [enabled] :

Target System Other Services [disabled] :

Do you want the target system to have the same port values as the source system (y/n) [y] ? : n

Target System Port Pool [0-99] : 0

Checking the port pool 0

done: Port Pool 0 is free

Report file located at $ORACLE_HOME/<TARGET_DB_SID>/fs1/inst/apps/<TARGET_DB_SID>_apps1/admin/out/portpool.lst

UTL_FILE_DIR on database tier consists of the following directories.

1. /usr/tmp

2. /usr/tmp

3. $ORACLE_HOME/<TARGET_DB_SID>/12.1.0/appsutil/outbound/<TARGET_DB_SID>_data1

4. /usr/tmp

Choose a value which will be set as APPLPTMP value on the target node [1] : 1