Interoperability Notes: Oracle E-Business Suite Release To

12.1 with Oracle Database 19c (Doc ID 2580629.1) Bottom

This knowledge document is the primary document that describes how to set up Oracle E-
Business Suite Release 12 (12.1) with Oracle Database 19c (19.x).

The most current version of this document can be obtained in My Oracle Support Knowledge
Document 2580629.1.

There is a change log at the end of this document.

In This Document

This document is divided into the following sections:

 Section 1: Overview
o 1.1 Important Information Regarding the Upgrade to Oracle Database 19c
 Section 2: Upgrading an Oracle E-Business Suite Release 12 Database to Oracle
Database 19c
o 2.1 Before the Database Installation
o 2.2 Database Installation
o 2.3 Database Upgrade
o 2.4 After the Database Upgrade
o 2.5 Convert Database to Multitenant Architecture
 Section 3: Unsupported Products
 Section 4: Known Issues
 Appendix A: Database Patch Lists

Section 1: Overview
Before performing any of the instructions in this document, check My Oracle Support to
confirm that your platform and environment configuration are certified to work with Oracle
Database 19c. If you are on the HP-UX PA-RISC platform or Windows 32-bit platform,
migrate the database tier to HP-UX Itanium or Windows x64 respectively. Consult My
Oracle Support Knowledge Document 456347.1, Oracle E-Business Suite Release 12.0 or
12.1 with a Database Tier Only Platform on Oracle 11g Release 2.

Note: This document describes the Oracle E-Business Suite database upgrade procedure for
on-premises and Oracle Cloud Infrastructure (OCI) Compute environments only. If your
database is running on any other Oracle Database cloud service, see My Oracle Support
Knowledge Document 2517025.1, Getting Started with Oracle E-Business Suite on Oracle
Cloud Infrastructure.

These notes apply to UNIX, Linux, and Windows platforms. However, you may need to
modify some instructions depending on your platform. For example, these notes typically use
UNIX/Linux syntax when specifying a directory, so Windows users will need to substitute
the appropriate syntax when specifying a directory.

You can download Oracle Database 19c from Oracle Technology Network.

When upgrading or making other significant changes to your Oracle E-Business Suite
system, ensure sufficient performance and scalability pre-production testing has been
performed for essential and/or time-critical activities. The testing should include activities
such as maintenance, life-cycle management, batch and online operations. Refer to My
Oracle Support Knowledge Document 2528000.1, Oracle E-Business Suite Performance
Best Practices. This document offers strategic guidance on performance best practices for all
Oracle E-Business Suite environments and is updated as new features and options become
available.

Note: If you are using or planning to use any of the unsupported products, do not upgrade the
database to Oracle Database 19c until the Oracle E-Business Suite 12.1 products you require
are supported for use with Oracle Database 19c.

1.1 Important Information Regarding the Upgrade to 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:
o Oracle Database Release Update 19.3 as well as Release Update 19.5 and later
are certified.
o 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 My Oracle Support Knowledge Document
2285040.1, Release Update Introduction and FAQ, for more details.
o 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.
o 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.

Note: We strongly recommend upgrading to Oracle Database 19c using the latest
Oracle E-Business Suite certified Release Update (RU).
  When upgrading your Oracle E-Business Suite database, it is essential to measure
your performance to make certain operations will continue to meet your requirements.
The most reliable strategy is to upgrade the database in a test environment, and then
conduct a benchmark test with a configuration, product mix, and user load that
simulates your own current and expected workloads. These conditions can help verify
performance before you upgrade your production-ready environment.
 Oracle E-Business Suite requires Oracle homes to be writable, not read-only.

Note: If you are going to use Oracle 19c Real Application Clusters (RAC) or Automatic
Storage Management (ASM), see My Oracle Support Knowledge Document 2530680.1,
Using Oracle Database 19c RAC (Single PDB) with Oracle E-Business Suite Release 12.1.3.

Section 2: Upgrading an Oracle E-Business Suite Release

12 Database to Oracle Database 19c
Follow the instructions in this section to upgrade the database and instance to the latest
version of Oracle Database 19c.

2.1 Before the Database Installation

1. Run hcheck.sql

Follow My Oracle Support Knowledge Document 136697.1 hcheck.sql - Script to

Check Data Dictionary for Known Problems, to run hcheck.sql, which looks for
some known common Data Dictionary problems.

Note: One critical check the script performs is to see if there is no SYSTEM datafile
that has a relative file number with the value of 1. If you encounter this error, do not
proceed with any further steps in this document. You will need to perform a migration
of your data that recreates the SYSTEM tablespace using steps documented in My
Oracle Support Knowledge Document 2615617.1, Export/Import Process for Oracle
E-Business Suite Release 12.1 Database Instances Using Oracle Database 19c or My
Oracle Support Knowledge Document 2707504.1, Using Transportable Tablespaces
to Migrate Oracle E-Business Suite Release 12.1 Using Oracle Database 19c
Enterprise Edition on a Multitenant Environment.

 Verify software versions

The following software component versions must exist in your environment.

Software Minimum Version Tier Details

Read the "Oracle Database Releases That
Support Direct Upgrade" subsection of the
Oracle
"Overview of Oracle Database Upgrade
Database
N/A Database Tools and Processes" section in Chapter 1
Enterprise
of the Oracle Database Upgrade Guide
Edition
19c. Make sure that direct upgrade is
supported from your current release.
 Patches to apply, comments on them, and
relevant Oracle E-Business Suite releases.

 Patch 8796558
 Patch 9239090 - Release 12.1.3
 Patch 23569686 -
R12.AD.B.delta.8
 Patch 27135427 -
R12.TXK.B.delta.4
 Patch 30033914 - 19c
interoperability patch for Release
12.1.3
 Patch 27102203 - Prerequisite
patch for 28613638 and 30824278
 Patch 28613638
 Patch 28685719
Oracle E- 12.1.3 with listed  Patch 29178111
Application
Business Suite patches  Patch 29414243
 Patch 29583055
 Patch 29905536
 Patch 30370150
 Patch 30601878
 Patch 31209544
 Patch 31406810
 Patch 31470349
 Patch 30824278 - Apply only for
Windows.

Apply the patches appropriate for your

environment listed in Section 4 of My
Oracle Support Knowledge Document
2500511.1, Implementing Database
Network Access Control Lists in Oracle E-
Business Suite Release 12.2 or 12.1.
If you are using Oracle Value Chain
Planning (VCP), upgrade VCP to at least
12.1.3.9.2. See My Oracle Support
Oracle Value Knowledge Document 746824.1, 12.1.x -
Chain Planning 12.1.3.9.2 Application Latest Patches and Installation
(Conditional) Requirements for Value Chain Planning
(aka APS Advanced Planning &
Scheduling) for information on which
patch to apply.
Oracle 11.2.0.1 with Warehouse If you are using Oracle Warehouse Builder
Warehouse 9403153 Builder (OWB) 11g Release 2, apply OWB 11g
Builder Database Release 2 (11.2.0.1) and Patch 9403153.
(Conditional) The following Oracle E-Business Suite
Release 12 products use OWB 11g Release
2:
  Oracle Manufacturing Operations
Center (MOC)
 Oracle Balance Scorecard (BSC)

Apply all the Oracle E-Business Suite

prerequisite patches listed above.

Afterwards, see My Oracle Support

AutoConfig R12.TXK.B.delta.4 Application Knowledge Document 387859.1, Using
AutoConfig to Manage System
Configurations with Oracle E-Business
Suite Release 12 for instructions on
running AutoConfig.
 Apply Patch 6400501 (Conditional)

If you are on a UNIX/Linux platform, apply the 10.1.0.5 version of Patch 6400501 to the iAS
10.1.2 Applications tier Oracle home.

Note: For Linux x86-64 environments, download the Linux 32-bit version of the patch as the
Applications tier Oracle home is 32-bit.
 Allow case sensitive passwords (Optional)

If you choose to enable case sensitive passwords, and the database has the
SEC_CASE_SENSITIVE_LOGON initialization parameter set to FALSE, enable case
sensitive passwords by following My Oracle Support Knowledge Document 1581584.1
Patch 12964564:R12.FND.B - Enabling the Oracle Database 11g Case-Sensitive Password
Feature for Oracle E-Business Suite Release 12.1.1+,

 Create the initialization parameter setup files

Run the following commands to create the

$ORACLE_HOME/dbs/<ORACLE_SID>_initparam.sql and
$ORACLE_HOME/dbs/<ORACLE_SID>_datatop.txt files.

On UNIX/Linux:

$ cd $ORACLE_HOME/appsutil
$ . ./txkSetCfgCDB.env dboraclehome=<full path of ORACLE_HOME>
$ export ORACLE_SID=<ORACLE_SID>
$ cd $ORACLE_HOME/appsutil/bin
$ perl txkOnPremPrePDBCreationTasks.pl -dboraclehome=<ORACLE_HOME> \
-outdir=<ORACLE_HOME>/appsutil/log -appsuser=<apps user> \
-dbsid=<ORACLE_SID> -skipdbshutdown=yes

On Windows:

C:\> cd %ORACLE_HOME%\appsutil
C:\> txkSetCfgCDB.cmd dboraclehome=<full path of ORACLE_HOME>
C:\> set ORACLE_SID=<ORACLE_SID>
C:\> cd %ORACLE_HOME%\appsutil\bin
C:\> perl txkOnPremPrePDBCreationTasks.pl -dboraclehome=<ORACLE_HOME> \
-outdir=<ORACLE_HOME>\appsutil\log -appsuser=<apps user> \
-dbsid=<ORACLE_SID> -skipdbshutdown=yes

When the txkOnPremPrePDBCreationTasks.pl script is run on Oracle Database 11.2.0.4,

ignore any errors related to DBMS_PDB.DESCRIBE.

2.2 Database Installation

1. Prepare to create the 19c Oracle home

The 19c Oracle home must be installed on the database server node in a different
directory from the current Oracle home.

Read the chapters prior to the "Installing Oracle Database" chapter of the Oracle
Database Installation Guide 19c for your platform. Pay attention to Chapter 1 as it
contains checklists of requirements. It is possible that an operating system upgrade is
needed prior to upgrading to Oracle Database 19c. Also read the "Major Steps in the
Upgrade Process for Oracle Database" section of Chapter 1 of the Oracle Database
Upgrade Guide 19c. Make sure you thoroughly understand the installation and
upgrade processes. Perform any steps that are relevant for your environment.

2. Install Oracle Database 19c

Log in to the database server node as the owner of the Oracle RDBMS file system and
database instance. Ensure that environment settings, such as ORACLE_HOME, are
set for the new Oracle home you are about to create, and not for any existing Oracle
homes on the database server node. Perform the steps in the "Installing Oracle
Database" chapter of the Oracle Database Installation Guide 19c for your platform.

In the Database installation windows, select the option to install the database software
only (do not select the option to create and configure a single instance database). In
addition to American English, select any languages used by your Oracle E-Business
Suite database instance. Choose the Enterprise Edition installation type. For Windows
users, in the "Specify Oracle Home User" window, select the "Use Windows Built-in
Account" option.

Note: If you encounter the error "[INS-32921] The specified Oracle base location is
invalid since it contains one or more Oracle bases associated with other Oracle homes
installed on this server.", then choose a different location as the Oracle base.

After the installation, make sure that:

a. The ORACLE_BASE environment variable is set accordingly.

b. The ORACLE_HOME environment variable points to the new 19c Oracle
home.
c. The PATH environment variable includes $ORACLE_HOME/bin and the
directory where the new perl executable is located (usually
$ORACLE_HOME/perl/bin).
d. The LD_LIBRARY_PATH environment variable includes
$ORACLE_HOME/lib.
 e. The PERL5LIB environment variable points to the directories where the new
perl libraries are located: $ORACLE_HOME/perl/lib/<perl version> and
$ORACLE_HOME/perl/lib/site_perl/<perl version> for UNIX/Linux, or
$ORACLE_HOME/perl/lib and $ORACLE_HOME/perl/site/lib for Windows.

Note: The Oracle Database 19c installation on UNIX/Linux includes database Release
Update 19.3.0.0.190416, and OCW Release Update 19.3.0.0.190416. The Oracle
Database 19c installation on Windows includes database Release Update 19.3.0.0.0
(The release is not listed in the inventory).

3. Apply additional 19c Oracle Database patches

For Linux/UNIX platforms, apply the required 19.20.0.0.0 patches listed in Appendix
A. For Windows platforms, apply the required 19.19.0.0.0 patches.

Download the required Oracle Database patches from Patch 35374280, the
consolidated zip file. The consolidated zip file does not include any database bundle
patches or PSUs. These patches need to be downloaded and applied first.

Note: For Oracle Database 19.0.0.0.0, additional bugfixes are listed in My Oracle
Support Knowledge Document 555.1, Oracle Database 19c Important Recommended
One-off Patches. You should review these in the context of the quarterly Release
Updates (RUs) recommended in this Document 2580629.1. Do not apply an RU from
Document 555.1 unless it is recommended in this document, and do not apply any
Release Update Revisions (RURs). For any bugfixes listed in Document 555.1 that
you decide to apply but that are reported as conflicting with the requirements in this
document, contact Oracle Support.

For more information about patches to apply on Oracle Exadata systems, see My
Oracle Support Knowledge Document 1392527.1, Database Patches Required by
Oracle E-Business Suite on Oracle Engineered Systems: Exadata Database Machines
and SuperClusters.

It is possible that $ORACLE_HOME/perl is patched. After patching, verify that the

PERL5LIB environment variable set earlier is still valid. Reset PERL5LIB if needed.
Do not perform any of the post install instructions, as these will be performed after the
upgrade.

4. Create nls/data/9idata directory

On the database server node, as the owner of the Oracle RDBMS file system and
database instance, run the following command to create the
$ORACLE_HOME/nls/data/9idata directory.

$ perl $ORACLE_HOME/nls/data/old/cr9idata.pl

After creating the directory, make sure that the ORA_NLS10 environment variable is
set to the full path of the 9idata directory whenever you enable the 19c Oracle home.
5. Create appsutil.zip and copy it to the database tier

See Section 3.1b of My Oracle Support Knowledge Document 387859.1, Using

AutoConfig to Manage System Configurations with Oracle E-Business Suite Release
12, for instructions on how to create appsutil.zip and copy it to the database tier.

6. Copy the orai18n.jar file

Run the following command to copy the orai18n.jar file to the

$ORACLE_HOME/jdk/jre/lib/ext directory.

$ cp $ORACLE_HOME/jlib/orai18n.jar $ORACLE_HOME/jdk/jre/lib/ext

7. Create the CDB

On the database server node:

a. Run the Database Configuration Assistant (DBCA) to create the container

database (CDB).
b. When prompted, click on the "Create Database", "Advanced Configuration",
and "General Purpose or Transaction Processing" options.
c. In the Specify Database Identification screen, check to create an empty
container database (CDB) without a PDB.
d. Set the Global Database Name, the SID to the new CDB SID (maximum of 8
characters), and check the "Use Local Undo tablespace for PDBs" checkbox.
The CDB SID has to be different from the current ORACLE_SID, which will
be the PDB SID.
e. In the "Network Configuration" section, do not create a listener. In the
"Specify Configuration Options" section, set the SGA and PGA sizes to 2G
and 1G respectively.
f. Click on the Character Sets tab and choose the Character Set and National
Character Set to be the same as in the source database. If the appropriate
Character Set does not show up, uncheck the "Show recommended character
sets only" box.
g. In the "Select Database Creation Option" section, click on the "Customize
Storage Locations" button. Set the size of the redo log files to be the same as
in the source database. Other options can be configured as appropriate.
h. During the CDB creation, ignore ORA-00313 and ORA-27037 error messages
about redo logs in the alert.log file. These messages are informational.

Note: As a result of creating and instantiating the new CDB instance in parallel with a
running production instance, you must also take into consideration the expected
increase in the total shared memory and "huge" pages requirements on the system.
Accordingly, before attempting to create the CDB, you must consider making needed
adjustments to appropriate kernel parameters that control the total number of "huge"
pages available on the system, and maximum amount of shared memory that can be
allocated on the system.
8. Run datapatch on CDB

Use the following commands to load any necessary patches on the CDB.

On UNIX/Linux:

$ export ORACLE_SID=<CDB SID>

$ $ORACLE_HOME/OPatch/datapatch

On Windows:

C:\> set ORACLE_SID=<CDB SID>

C:\> %ORACLE_HOME%\OPatch\datapatch

9. Create the CDB MGDSYS schema

Use SQL*Plus to connect to the CDB as SYSDBA and run the

$ORACLE_HOME/rdbms/admin/catmgd.sql script. This creates the new MGDSYS
schema on the CDB.

$ sqlplus "/ as sysdba" @?/rdbms/admin/catmgd.sql

10. Create the CDB TNS files

On the database server node, run the following perl script to generate the required
TNS files. Note that this script does not create a listener.

On UNIX/Linux:

$ cd $ORACLE_HOME/appsutil
$ . ./txkSetCfgCDB.env dboraclehome=<full path of ORACLE_HOME>
$ cd $ORACLE_HOME/appsutil/bin
$ perl txkGenCDBTnsAdmin.pl -dboraclehome=<ORACLE_HOME> \
-cdbname=<CDB SID> -cdbsid=<CDB SID> -dbport=<Database port> \
-outdir=<ORACLE_HOME>/appsutil/log

On Windows:

C:\> cd %ORACLE_HOME%\appsutil
C:\> txkSetCfgCDB.cmd dboraclehome=<full path of ORACLE_HOME>
C:\> cd %ORACLE_HOME%\appsutil\bin
C:\> perl txkGenCDBTnsAdmin.pl -dboraclehome=<ORACLE_HOME> \
-cdbname=<CDB SID> -cdbsid=<CDB SID> -dbport=<Database port> \
-outdir=<ORACLE_HOME>\appsutil\log

11. Configure Transparent Data Encryption for CDB (Conditional)

If you have Transparent Data Encryption (TDE) enabled in the source database or if
you choose to use TDE, perform the following steps to create a software keystore for
the CDB and to set the TDE master encryption key:
 a. Set the keystore location and type

Create the <WALLET_ROOT>/tde directory which is where the keystore will be

stored. Next, modify the following CDB initialization parameters and then
restart the database to set the parameters:

WALLET_ROOT='<WALLET_ROOT directory given above (without

"tde")>'
TDE_CONFIGURATION="KEYSTORE_CONFIGURATION=FILE"

b. Create a software keystore

Use SQL*Plus to connect to the database as a user who has the

ADMINISTER KEY MANAGEMENT or SYSKM privilege. Perform the
following steps to create the software keystore under <WALLET_ROOT>/tde.

$ export ORACLE_SID=<CDB_SID>
$ sqlplus sec_admin as syskm
SQL> administer key management create keystore identified by
"<keystore password>";
SQL> administer key management create local auto_login keystore
from keystore
'<WALLET_ROOT>/tde' identified by "<keystore password>";

c. Open the keystore and set the TDE Master Encryption Key

Perform the following steps to open the keystore and set the TDE Master
Encryption Key in the software keystore.

SQL> administer key management set keystore open force keystore

identified by "<keystore password>";
SQL> administer key management set key force keystore
identified by "<keystore password>" with backup;

12. Shut down the CDB

Use SQL*Plus to connect to the CDB as SYSDBA and use the following command to
shut down the database:

$ sqlplus "/ as sysdba"

SQL> shutdown;

2.3 Database Upgrade

1. Store the UTL_FILE_DIR parameter values

Perform the instructions in Section 3.1.1, Migrating UTL_FILE_DIR Settings when

Upgrading to Oracle Database 19c, in 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, to set the UTL_FILE_DIR paramter
 values.

2. Shut down the application tier server processes

On each application tier server node, shut down all server processes or services. The
applications will be unavailable to users until all remaining tasks in this section are
completed.

3. Drop SYS.ENABLED$INDEXES (Conditional)

If the SYS.ENABLED$INDEXES table exists, connect to the database as SYSDBA

and run the following command to drop the table:

$ sqlplus "/ as sysdba"

SQL> drop table sys.enabled$indexes;

4. Disable Database Vault (Conditional)

If you have previously enabled Database Vault, follow the steps below that apply to
your database version.

o For Release 11.2.0.4, follow the steps in Appendix B of Oracle Database Vault
Administrator's Guide 11g Release 2 (11.2).
o For Release 12.1.0.2, follow the steps in Appendix B of Oracle Database Vault
Administrator's Guide 12c Release 1 (12.1).
5. Export OLAP analytical workspaces (Conditional)

If your database server node is on a 32-bit platform, perform detailed steps 1 to 4 of

My Oracle Support Knowledge Document 352306.1, Steps for Migrating OLAP
Across Databases/Platforms.

6. Remove the MGDSYS schema (Conditional)

If you are upgrading from a database version prior to Oracle 12c, log on to the old
database server node, use SQL*Plus to connect to the database as SYSDBA, and run
the $ORACLE_HOME/md/admin/catnomgdidcode.sql script. This drops the MGDSYS
schema.

$ sqlplus "/ as sysdba" @?/md/admin/catnomgdidcode.sql

7. Shut down the database listener

On the database tier server node, shut down the Oracle Net or Net8 database listener
in the old Oracle home.

Note: To ensure that the database does not inadvertently point to a non-existent
listener during the upgrade, verify that you do not have the LOCAL_LISTENER
initialization parameter set.
8. Prepare to upgrade

Read Chapter 2 of the Oracle Database Upgrade Guide 19c. If you are on a 32-bit
platform, take note of the sections pertaining to the manual/command line method for
upgrading the database. Otherwise, take note of the "The Graphical User Interface
Method for Upgrading Oracle Database" section pertaining to the Database Upgrade
Assistant (DBUA). Also read the section about the Pre-Upgrade Information Tool.

If you are using Transparent Data Encryption (TDE), perform the steps listed in the
"Copying Transparent Encryption Oracle Wallets" subsection of the "Database
Preparation Tasks to Complete Before Starting Oracle Database Upgrades" section of
Chapter 2. This wallet copy is the non-CDB wallet, which is different from the CDB
wallet created previously.

Ensure that the oratab file contains an entry for the database to be upgraded.

Modify the following initialization parameters before the upgrade:

o Comment out all the deprecated initalization parameters. Any necessary

parameter will be added back in after the upgrade.
o Unset the olap_page_pool_size initialization parameter.
o If you have an 11g source database, set the PGA_AGGREGATE_TARGET
initialization parameter to at least 10G.
o Set the SGA_TARGET initialization parameter to at least 2G.
o Add the event EVENT='10946 trace name context forever, level 8454144'

Shut down and restart the database to enable the parameters.

If you are using a Windows environment, ensure that the Services applet window is
closed on the database server node. You cannot remove the current database instance
service during the upgrade if this window is open.

Note: The preupgrade.jar log file provides instructions to remove the OLAP catalog
(amd_exists). It does not actually remove the OLAP catalog. Run the
$ORACLE_HOME/olap/admin/catnoamd.sql script manually to remove the OLAP
catalog.

9. Upgrade the database instance

The instructions for the database upgrade are outlined in Chapters 4, 6, and Appendix
B of the Oracle Database Upgrade Guide 19c.

If you are upgrading from a 32-bit platform, Perform the "Upgrading Manually with
Parallel Upgrade Utility" section of chapter 4. Otherwise, perform the steps in
Appendix B and any step in chapter 6 that is relevant to your environment.

Invoke DBUA using the following command. The keepEvents parameter allows
events in the preupgraded database to be enabled during the upgrade.
 $ dbua -keepEvents

In Oracle Database 19c, the DMSYS schema is no longer used. The Data Mining
option is installed in the SYS schema. The Oracle 19c pre-upgrade tool has been
extended to include a warning that the DMSYS schema should be dropped. If this
warning is reported, it is recommended to drop the schema. Removing the DMSYS
schema has no effect on the functioning of Data Mining.

When upgrading all statistics tables, note that Oracle E-Business Suite has only one
statistics table (APPLSYS.FND_STATTAB) that needs to be upgraded.

Take note of the following after the upgrade:

o The OLAP Catalog Component (AMD) may have "OPTION OFF" or

"REMOVED" status in the dba_registry table. Oracle E-Business Suite has no
dependencies on AMD and so this is acceptable.
o Modify the following initialization parameters after the upgrade:
 If you previously had the SEC_CASE_SENSITIVE_LOGON
initialization parameter set to FALSE, re-enable the parameter.
 Set COMPATIBLE to 19.0.0.
 If you modified the PGA_AGGREGATE_TARGET initialization
parameter in the previous step, revert it back to the original value.
10. Perform patch post-install instructions

Run all the patch post install instructions.

Note: Several patches may require datapatch to be run. This only needs to be run
once after the last patch has been applied.

11. Natively compile PL/SQL code (Optional)

You can choose to run Oracle E-Business Suite Release 12 PL/SQL database objects
in natively compiled mode with Oracle Database 19c. See the "Compiling PL/SQL
Program Units for Native Execution" section of Chapter 12 of Oracle Database
PL/SQL Language Reference 19c.

2.4 After the Database Upgrade

1. Import OLAP analytical workspaces (Conditional)

If your database server node was upgraded from a 32-bit platform, perform detailed
steps 6 and 7 of My Oracle Support Knowledge Document 352306.1, Upgrading
OLAP from 32 to 64 bits.

2. Run adgrants.sql

Copy $APPL_TOP/admin/adgrants.sql (adgrants_nt.sql for Windows) from the

administration server node to the database server node. Use SQL*Plus to connect to
 the database as SYSDBA and run the script using the following command:

$ export ORACLE_SID=<source SID>

$ sqlplus "/ as sysdba" @adgrants.sql (or adgrants_nt.sql) <apps
user>

Note: When running adgrants.sql, you may get ORA-00942 errors. These are
caused by adgrants.sql trying to create grants on non-existent objects. The errors
can be ignored.

3. Grant create procedure privilege on CTXSYS

Copy $AD_TOP/patch/115/sql/adctxprv.sql from the administration server node

to the database server node. Use SQL*Plus to connect to the database as apps and run
the script using the following command:

$ export ORACLE_SID=<source SID>

$ sqlplus apps/<apps password> @adctxprv.sql <SYSTEM password> CTXSYS

4. Compile invalid objects

Use SQL*Plus to connect to the database as SYSDBA and run the

$ORACLE_HOME/rdbms/admin/utlrp.sql script to compile invalid objects.

$ export ORACLE_SID=<source SID>

$ sqlplus "/ as sysdba" @$ORACLE_HOME/rdbms/admin/utlrp.sql

5. Grant datastore access

Use SQL*Plus to connect to the database as SYSDBA and run the following
command:

$ export ORACLE_SID=<source SID>

$ sqlplus "/ as sysdba"
SQL> grant text datastore access to public;

6. Validate Workflow ruleset

Copy $FND_TOP/patch/115/sql/wfaqupfix.sql from the administration server

node to the database server node. Use SQL*Plus to connect to the database as apps
and run the script using the following command:

$ export ORACLE_SID=<source SID>

$ sqlplus apps/<apps password> @wfaqupfix.sql <applsys user> <apps
user>

7. Gather statistics for SYS schema

Copy $APPL_TOP/admin/adstats.sql from the administration server node to the

database server node. Note that adstats.sql has to be run in restricted mode. Use
SQL*Plus to connect to the database as SYSDBA and use the following commands to
 run adstats.sql in restricted mode:

$ export ORACLE_SID=<source SID>

$ sqlplus "/ as sysdba"
SQL> alter system enable restricted session;
SQL> @adstats.sql
$ sqlplus "/ as sysdba"
SQL> alter system disable restricted session;
SQL> exit;

8. Create the new MGDSYS schema (Conditional)

If you upgraded from an RDBMS version prior to Oracle 12c, use SQL*Plus to
connect to the database as SYSDBA and run the
$ORACLE_HOME/rdbms/admin/catmgd.sql script. This creates the new MGDSYS
schema.

$ export ORACLE_SID=<source SID>

$ sqlplus "/ as sysdba" @?/rdbms/admin/catmgd.sql

9. Export Master Encryption Key (Conditional)

If the database is encrypted, perform the following steps to export the non-CDB
wallet Master Encryption Key.

a. Disable Auto-Login wallet if enabled

Use SQL*Plus to connect to the database as SYSDBA and run the following
query to determine if the wallet is opened in Auto-Login mode.

SQL> select wallet_type from v$encryption_wallet;

WALLET_TYPE
--------------------
AUTOLOGIN

If the result is AUTOLOGIN, disable Auto-Login by running the following

commands:

SQL> administer key management set keystore close;

SQL> !mv <new 19c wallet location>/cwallet.sso <new 19c wallet
location>/cwallet.sso_old
SQL> !cp <new 19c wallet location>/ewallet.p12 <new 19c wallet
location>/ewallet.p12_old
SQL> administer key management set keystore open identified by
<wallet password>;
SQL> administer key management set key identified by <wallet
password> with backup;

b. Export wallet keys

Run the following command to export the current wallet

 SQL> administer key management export encryption keys with
secret
"<secret password>" to '<export file name>' identified by
<wallet password>;

c. Change the wallet to Auto-Login mode

Run the following command to change the wallet to Auto-Login mode.

SQL> administer key management create auto_login keystore from

keystore
'<new 19c wallet location>' identified by <wallet password>;

2.5 Convert Database to Multitenant Architecture

In this subsection, there are two databases that are associated with the 19c Oracle home, the
CDB and the non-CDB database. Moreover, the non-CDB database will be migrated to the
PDB database. Set the appropriate environment variables to connect to the appropriate
database.

Only the txkSetCfgCDB.env/cmd file in the $ORACLE_HOME/appsutil directory is necessary.

It sets certain environment variables. However, it does not distinguish between the different
databases in the 19c Oracle home. It is used mainly to complete the steps in this subsection.
The following steps assume that a new window is brought up every time. However, there is
no need to run txkSetCfgCDB.env/cmd twice in the same window. So, you may skip running
the txkSetCfgCDB.env/cmd script if it has already been run on the particular terminal you are
using.

After running the txkPostPDBCreationTasks.pl, additional environment files are created

so that connecting to the database is more convenient. Load the proper environment variables
and connect to the database by performing the following steps:

 For the non-CDB database, source the $ORACLE_HOME/<non-CDB

SID>_<HOST>.env/cmd file. Then, run sqlplus <user>/<password>@<non-CDB
SID>. (The environment file was created during the earlier upgrade steps)
 For the CDB database, source the $ORACLE_HOME/<CDB SID>_<HOST>.env/cmd file.
Then, run sqlplus <user>/<password> or connect as SYSDBA.
 For the PDB database on UNIX/Linux platforms, to connect as SYSDBA, source the
$ORACLE_HOME/<CDB SID>_<HOST>.env file. Set the ORACLE_PDB_SID
environment variable to <PDB SID>. Then, connect as SYSDBA.
 For the PDB database on Windows platforms, to connect as SYSDBA, source the
$ORACLE_HOME/<PDB SID>_<HOST>.cmd file. Then, connect as SYSDBA.
 For the PDB database, to connect to other users, source the $ORACLE_HOME/<PDB
SID>_<HOST>.env/cmd file. Then, run sqlplus <user>/<password>@<PDB SID>.

1. Create the PDB descriptor

Perform the following commands to create the PDB descriptor file in the
$ORACLE_HOME/dbs directory.
 On UNIX/Linux:

$ cd $ORACLE_HOME/appsutil
$ . ./txkSetCfgCDB.env dboraclehome=<full path of ORACLE_HOME>
$ export ORACLE_SID=<source SID>
$ cd $ORACLE_HOME/appsutil/bin
$ perl txkOnPremPrePDBCreationTasks.pl -dboraclehome=<ORACLE_HOME> \
-outdir=<ORACLE_HOME>/appsutil/log -appsuser=<apps user> -
dbsid=<source SID>

On Windows:

C:\> cd %ORACLE_HOME%\appsutil
C:\> txkSetCfgCDB.cmd dboraclehome=<full path of ORACLE_HOME>
C:\> set ORACLE_SID=<source SID>
C:\> cd %ORACLE_HOME%\appsutil\bin
C:\> perl txkOnPremPrePDBCreationTasks.pl -dboraclehome=<ORACLE_HOME>
\
-outdir=<ORACLE_HOME>\appsutil\log -appsuser=<apps user> -
dbsid=<source SID>

Note: The txkOnPremPrePDBCreationTasks.pl script shuts down the non-CDB

database. Do not manually bring up the non-CDB database. There will be no access to
the non-CDB database until after the migration of the non-CDB database to the PDB.

2. Disable the ENCRYPTION_WALLET_LOCATION sqlnet.ora entry

(Conditional)

If the database is encrypted, remove or comment out the

ENCRYPTION_WALLET_LOCATION entry in both the Oracle Database 19c
sqlnet.ora and sqlnet_ifile.ora files.

3. Update the CDB initialization parameters

On the database server node, copy the <source SID>_initparam.sql and <source
SID>_datatop.txt files from the source $ORACLE_HOME/dbs directory to the new
$ORACLE_HOME/dbs directory. Then use SQL*Plus to connect to the CDB as
SYSDBA, and run the following commands to update the CDB initialization
parameters:

On UNIX/Linux:

$ cd $ORACLE_HOME/appsutil
$ . ./txkSetCfgCDB.env dboraclehome=<full path of ORACLE_HOME>
$ export ORACLE_SID=<CDB SID>
$ sqlplus "/ as sysdba"
SQL> startup nomount;
SQL> @$ORACLE_HOME/dbs/<source SID>_initparam.sql
SQL> alter system set LOCAL_LISTENER="<hostname>:<port number>"
scope=both;
SQL> shutdown;
SQL> startup;
 On Windows:

C:\> cd %ORACLE_HOME%\appsutil
C:\> txkSetCfgCDB.cmd dboraclehome=<full path of ORACLE_HOME>
C:\> set ORACLE_SID=<CDB SID>
C:\> sqlplus "/ as sysdba"
SQL> startup nomount;
SQL> @%ORACLE_HOME%/dbs/<source SID>_initparam.sql
SQL> alter system set LOCAL_LISTENER="<hostname>:<port number>"
scope=both;
SQL> shutdown;
SQL> startup;

If using a pfile initialization parameter file, add the LOCAL_LISTENER setting to

the file. Ignore any ORA-25138 errors that occur when there are initialization
parameters in the source database that are obsolete in Oracle Database 19c.

Note: During this process, setting some parameters using ALTER SYSTEM SET may
fail as they can only be set when the database is open. For example:

ORA-07452: specified resource manager plan does not exist in the data
dictionary

For any such parameters, identify the appropriate ALTER SYSTEM SET commands
from the <source SID>_initparam.sql script and run them manually after starting
or opening the database. You will need to restart the database again for those
parameters to take effect.

4. Check for PDB violations

Use the following commands to run the txkChkPDBCompatability.pl script. This

checks the PDB for any violations.

On UNIX/Linux:

$ cd $ORACLE_HOME/appsutil
$ . ./txkSetCfgCDB.env dboraclehome=<full path of ORACLE_HOME>
$ export ORACLE_SID=<CDB SID>
$ cd $ORACLE_HOME/appsutil/bin
$ perl txkChkPDBCompatability.pl -dboraclehome=<ORACLE_HOME> \
-outdir=<ORACLE_HOME>/appsutil/log -cdbsid=<CDB SID> \
-pdbsid=<source SID> -servicetype=onpremise

On Windows:

C:\> cd %ORACLE_HOME%\appsutil
C:\> txkSetCfgCDB.cmd dboraclehome=<full path of ORACLE_HOME>
C:\> set ORACLE_SID=<CDB SID>
C:\> cd %ORACLE_HOME%\appsutil\bin
C:\> perl txkChkPDBCompatability.pl -dboraclehome=<ORACLE_HOME> \
-outdir=<ORACLE_HOME>\appsutil\log -cdbsid=<CDB SID> \
-pdbsid=<source SID> -servicetype=onpremise
 Note: Use the same command options for Oracle Cloud Infrastructure Compute
environments.

Review all warnings and resolve all errors. Re-run the script to verify all errors have
been resolved. Do not run noncdb_to_pdb.sql as that will be run by
txkCreatePDB.pl in the next step.

5. Create the PDB

Load the environment variables by running the following commands:

On UNIX/Linux:

$ cd $ORACLE_HOME/appsutil
$ . ./txkSetCfgCDB.env dboraclehome=<full path of ORACLE_HOME>
$ cd $ORACLE_HOME/appsutil/bin

On Windows:

C:\> cd %ORACLE_HOME%/appsutil
C:\> txkSetCfgCDB.cmd dboraclehome=<full path of ORACLE_HOME>
C:\> cd %ORACLE_HOME%\appsutil\bin

If the database is encrypted, use the following command to run the txkCreatePDB.pl
script to create the PDB.

$ perl txkCreatePDB.pl -dboraclehome=<ORACLE_HOME> -

outdir=<ORACLE_HOME>/appsutil/log \
-cdbsid=<CDB SID> -pdbsid=<source SID> -dbuniquename=<CDB SID> -
istdeenabled=yes \
-secretkeyfile=<full path of non-CDB wallet keys file created in step
2.4.9.b> \
-keystoreloc=<WALLET_ROOT specified in step 2.2.11/tde> -
servicetype=onpremise

Otherwise, use the following command:

$ perl txkCreatePDB.pl -dboraclehome=<ORACLE_HOME> -

outdir=<ORACLE_HOME>/appsutil/log \
-cdbsid=<CDB SID> -pdbsid=<source SID> -dbuniquename=<CDB SID> -
servicetype=onpremise

Note: Use the same command options for Oracle Cloud Infrastructure Compute
environments.

The PDB datafile location can be the same as the source datafile location. When
prompted with "Enter the wallet credentials" and "Enter the secret key", enter the
previously specified CDB wallet password and non-CDB secret password
respectively.

6. Run the post PDB script

 Use the following commands to run the txkPostPDBCreationTasks.pl script. This
updates the PDB configuration.

On UNIX/Linux:

$ cd $ORACLE_HOME/appsutil
$ . ./txkSetCfgCDB.env dboraclehome=<full path of ORACLE_HOME>
$ perl $ORACLE_HOME/appsutil/bin/txkPostPDBCreationTasks.pl -
dboraclehome=<ORACLE_HOME> \
-outdir=<ORACLE_HOME>/appsutil/log -cdbsid=<CDB SID> -pdbsid=<PDB
SID> \
-appsuser=apps -dbport=<TNS port number> -servicetype=onpremise

On Windows:

C:\> cd %ORACLE_HOME%\appsutil
C:\> txkSetCfgCDB.cmd dboraclehome=<full path of ORACLE_HOME>
C:\> perl %ORACLE_HOME%\appsutil\bin\txkPostPDBCreationTasks.pl -
dboraclehome=<ORACLE_HOME> \
-outdir=<ORACLE_HOME>\appsutil\log -cdbsid=<CDB SID> -pdbsid=<PDB
SID> \
-appsuser=apps -dbport=<TNS port number> -servicetype=onpremise

Note: Use the same command options for Oracle Cloud Infrastructure Compute
environments.

7. Modify initialization parameters

Use the following sections in My Oracle Support Knowledge Document 396009.1,

Database Initialization Parameter Settings for Oracle E-Business Suite Release 12, as
a guideline in modifying your initalization parameters.

a. Common Database Initialization Parameters For All Releases

b. Release-Specific Database Initialization Parameters For Oracle 19c
c. Temporary Tablespace Setup
d. Database Initialization Parameter Sizing
8. Run AutoConfig on applications tier

As the user of the applications server node, modify the $TNS_ADMIN/tnsnames.ora

file to specify the CDB instance name. The following shows the format of the new
TNS entry.

<TWO_TASK> =
(DESCRIPTION =
(ADDRESS = (PROTOCOL=tcp)(HOST=<hostname>.<domain>)(PORT=<port
number>))
(CONNECT_DATA = (SERVICE_NAME=ebs_<PDB SID>)(INSTANCE_NAME=<CDB
SID>))
)

Update the following values in the context file of every Applications tier server node.
 Variable Name Value
s_dbport New database port
s_apps_jdbc_connect_descriptor NULL (blank entry)
Directory (not /usr/tmp) defined in
s_applptmp
UTL_FILE_DIR
To identify the allowable directories for s_applptmp use, connect to the Oracle E-
Business Suite database instance as the apps user and run the following query:

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

Run AutoConfig on the APPL_TOP using the following command.

On UNIX/Linux:

$ $INST_TOP/admin/scripts/adautocfg.sh

On Windows:

C:\> %INST_TOP%\admin\scripts\adautocfg.cmd

After running AutoConfig, run the correct Oracle E-Business Suite file system
environment file again, in a new window to ensure the correct environment variables
are loaded. (Existing windows logged into the application tier may have the old
environment variables loaded.)

9. Apply post-upgrade WMS patch (Conditional)

If you upgraded from a database version prior to 12c, apply Patch 18039691.

10. Re-create custom database links (Conditional)

If the Oracle Net listener in the 19c Oracle home is defined differently to the one used
by the old Oracle home, you must recreate any custom self-referential database links
that exist in the Oracle E-Business Suite database instance. To check for the existence
of database links, use SQL*Plus on the database server node to connect to the
database instance as apps and run the following query:

$ sqlplus apps/<apps password>

SQL> select db_link from all_db_links;

The EDW_APPS_TO_WH and APPS_TO_APPS database links, if they exist, should

have been updated with the new port number by AutoConfig.

If you have custom self-referential database links in the database instance, use the
following commands to drop and re-create them:

$ sqlplus apps/<apps password>

SQL> drop database link <custom database link>;
SQL> create database link <custom database link> connect to <user>
identified by
<password> using '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)
 (HOST=<hostname>)
(PORT=<port number>))(CONNECT_DATA=(SID=<ORACLE_SID>)))';

where <custom database link>, <user>, <password>, <hostname>, <port number>,

and <ORACLE_SID> reflect the new Oracle Net listener for the database instance.

11. Implement the Network Access Control Lists

Perform the steps in Sections 2-3 of My Oracle Support Knowledge Document

2500511.1, Implementing Database Network Access Control Lists in Oracle E-
Business Suite Release 12.2 or 12.1, to implement the Network Access Control Lists
(ACL) for Oracle E-Business Suite.

12. Enable Database Vault (Optional)

If you choose to enable Database Vault, follow the instructions in My Oracle

Knowledge Document 2648854.1.

13. Recreate the Concurrent Manager services (Conditional)

If you are on Windows, perform the following commands on the APPL_TOP to

recreate the Concurrent Manager services.

C:\> %APPL_TOP%\APPS<PDB SID>_<hostname>.cmd

C:\> %INST_TOP%\admin\install\adsvcm.cmd -deinstall
C:\> %INST_TOP%\admin\install\adsvcm.cmd

14. Reconfigure external node integrations (Conditional)

If you have implemented any integrations that connect an external node to Oracle E-
Business Suite, then you should reconfigure those integrations with the updated DBC
file. For example, if you have integrated Oracle E-Business Suite with Oracle Access
Manager using Oracle E-Business Suite AccessGate, then you should reconfigure
Oracle E-Business Suite AccessGate and the associated datasource with the updated
DBC file as indicated in My Oracle Support Knowledge Document 1388152.1,
Overview of Single Sign-On Integration Options for Oracle E-Business Suite.

15. Restart applications tier server processes

Restart all the application tier server processes you shut down previously. Remember
that the Oracle Net listener for the database instance, as well as the database instance
itself, need to be started in the 19c Oracle home. Users may return to the system.

Section 3: Unsupported Products

The following Oracle E-Business Suite products are currently not supported with Oracle E-
Business Suite Release 12 on Oracle Database 19c:

 Oracle Enterprise Data Warehouse (EDW)

  Oracle Enterprise Planning and Budgeting (EPB)
 Oracle Demand Signal Repository (DSR)
 Oracle Demand Planning (ODP)
 Demantra Demand Management

Section 4: Known Issues

The following are known issues with Oracle E-Business Suite 12.1 on Database 19c:

 AutoConfig may fail in RDBMS 19c because adgentns.pl times out. As outlined in
bug 16525885, the workaround is to use SQL*Plus to connect to the database as
SYSDBA and run DBMS_STATS.GATHER_DATABASE_STATS.
 If your Oracle E-Business Suite environment is configured for Integrated SOA
Gateway (ISG):
o As outlined in bug 30547875, you may experience slower response for certain
ISG design time operations after upgrade to Oracle Database 19c. The
following ISG design time operations may take additional time to complete as
compared to time taken on Oracle Database 12c or earlier versions:
 Deploy an API as REST Service
 Generate an API as SOAP Service
o As outlined in bug 30217081, ISG design time operations may fail for certain
public APIs on Oracle Database 19c.
o If you are performing the above operations from the Integration Repository
UI, you may see a time out exception. However, the web service generation or
deployment activities will continue to execute in the background. After a few
minutes, when the service generation or deployment is complete, you will be
able to view the web service artifacts from the Interface Detail page. Please
avoid redoing the design-time operations on the same API until web service
artifacts are available.
o If you are performing any of the above operations using backend scripts, you
may see the script taking more time to complete.

Appendix A: Database Patch Lists

Patches required for 19.20.0.0.0:

Release Version
Platform Patches
(Footnote 3)
Patch 35320081 (Footnote 1) 19.0.0.0.0
UNIX/Linux
Patch 35354406 (Footnote 2) 19.0.0.0.0
Footnote 1- This is the Database Release Update Patch 19.20.0.0.230718 (Jul2023). Refer to
the patch readme for content and installation instructions. For additional information on
Oracle Database patch delivery refer to Oracle Database Patch Maintenance.

Footnote 2- This is the OJVM Release Update Patch 19.20.0.0.230718 (Jul2023) which
requires additional post-patch installation steps as detailed in its readme.

Footnote 3- This column reflects the exact patch version that must be downloaded from My
Oracle Support:

 Individual patches may be available for multiple releases but only the specific version
listed can co-exist with the other recommended patches in the table. Ensure the patch
release version for your chosen platform is installed.
 Individual patches on top of an earlier Release Update must be explicitly rolled back
prior to installing Patch 35320081 Database Release Update 19.20.0.0.230718
(Jul2023), these are not automatically handled by the OPatch utility.
 Earlier Release Updates do not need to be explicitly rolled back as the OPatch utility
automatically supersedes them when later versions are applied, this applies to the
Database Release Update, OJVM Release Update Patch and OCW Release Update.
 Patches listed with version 19.20.0.0.0 DBRU must be installed after Patch 35320081
Database Release Update 19.20.0.0.230718 (Jul2023) has been installed.

Patches required for 19.19.0.0.0:

Release Version
Platform Patches
(Footnote 3)
Patch 35042068 (Footnote 1) 19.0.0.0.0
Patch 35050341 (Footnote 2) 19.0.0.0.0
UNIX/Linux Patch 35037877 19.19.0.0.0
Patch 35119957 19.19.0.0.0
Patch 35406065 19.19.0.0.0
Footnote 1- This is the Database Release Update Patch 19.19.0.0.230418 (Apr2023). Refer
to the patch readme for content and installation instructions. For additional information on
Oracle Database patch delivery refer to Oracle Database Patch Maintenance.

Footnote 2- This is the OJVM Release Update Patch 19.19.0.0.230418 (Apr2023) which
requires additional post-patch installation steps as detailed in its readme.

Footnote 3- This column reflects the exact patch version that must be downloaded from My
Oracle Support:

 Individual patches may be available for multiple releases but only the specific version
listed can co-exist with the other recommended patches in the table. Ensure the patch
release version for your chosen platform is installed.
 Individual patches on top of an earlier Release Update must be explicitly rolled back
before installing Patch 35042068 Database Release Update 19.19.0.0.230418
(Apr2023), these are not automatically handled by the OPatch utility.
 Earlier Release Updates do not need to be explicitly rolled back as the OPatch utility
automatically supersedes them when later versions are applied, this applies to the
Database Release Update, OJVM Release Update Patch and OCW Release Update.
 Patches listed with version 19.19.0.0.0 DBRU must be installed after Patch 35042068
Database Release Update 19.19.0.0.230418 (Apr2023) has been installed.

Patches required for 19.19.0.0.0:

Platform Patches Release

 Version
Patch 35046439 (Microsoft Windows Bundle 19.19.0.0.230418) 19.0.0.0.0
Windows
Patch 35050341 (OJVM Bundle 19.19.0.0.0) 19.0.0.0.0
For the patch list of older Database Release Updates, see My Oracle Knowledge Document
2683670.1.

Change Log
Date Description
 Updated consolidated zip file to Patch 35374280.
 Added Oracle Database 19.19.0.0.0 Patch 35406065.
2023-
 Replaced 19.18.0.0.0 UNIX/Linux information with 19.20.0.0.0.
08-17
 Replaced 19.17.0.0.0 Windows information with 19.19.0.0.0.

2023-  Added the setting of PERL5LIB after database patching.

05-31
 Modified title of 136697.1.
 Updated consolidated zip file to Patch 35047681.
 Added Oracle Database 19.18.0.0.0 Patch 35037877 and Patch 35119957.
2023-
 Took out Known Issues related to patches 35037877 and 35119957.
05-23
 Replaced 19.17.0.0.0 UNIX/Linux information with 19.19.0.0.0.
 Replaced 19.14.0.0.0 Windows information with 19.17.0.0.0.

 Added Oracle Database 19.18.0.0.0 35037877 known issue.

2023-
 Added instructions for Network ACLs.
03-29
2023-  Added Oracle Database 19.18.0.0.0 FRM-99999 known issue.
03-03
 Replaced 19.16.0.0.0 UNIX/Linux information with 19.18.0.0.0.
2023-
 Updated consolidated zip file to Patch 34779179.
02-13
 Replaced 19.15.0.0.0 UNIX/Linux information with 19.17.0.0.0.
2022-  Updated consolidated zip file to Patch 34452810.
11-01  Modified Oracle Database 19.16.0.0.0 Patch 31424070 to Patch 33525014.

2022-  Added Oracle E-Business Suite Patch 31470349.

09-29
 Replaced 19.14.0.0.0 UNIX/Linux information with 19.16.0.0.0.
2022-
 Updated consolidated zip file to Patch 34136577.
08-16
2022-  Added Oracle E-Business Suite Patch 29414243.
05-19
 Added line to ignore ORA-00313 and ORA-27037 errors during CDB
creation.
2022-  Updated consolidated zip file from Patch 33570853 to Patch 33812345.
05-17  Replaced 19.13.0.0.0 UNIX/Linux information with 19.15.0.0.0.
 Replaced 19.9.0.0.0 Windows information with 19.14.0.0.0.
  Replaced 19.12.0.0.0 UNIX/Linux information with 19.14.0.0.0.
2022-
 Updated consolidated zip file from Patch 33186812 to Patch 33570853.
02-14
 Removed 19.13.0.0.0 warning.
2021-
 Added Oracle Database 19.13.0.0.0 Patch 33632051.
12-22
2021-  Added 19.13.0.0.0 warning.
12-13
 Added reference to Document 555.1.
2021-
 Updated consolidated zip file to Patch 33186812.
12-09
 Updated consolidated zip file to Patch 33186784.
2021-
 Replaced 19.11.0.0.0 UNIX/Linux information with 19.13.0.0.0.
11-16
 Updated consolidated zip file to Patch 32898871.
2021-
 Replaced 19.10.0.0.0 UNIX/Linux information with 19.12.0.0.0.
08-24
 Updated Oracle Database Upgrade Guide DBUA references.
 Added reference to Document 2528000.1.
2021-  Replaced 19.9.0.0.0 UNIX/Linux information with 19.11.0.0.0.
05-18  Added Oracle Database 19.10.0.0.0 Patch 31431771.
 Updated consolidated zip file to Patch 32670824.

 Added reference to Document 2517025.1.

 Removed the fixed known issue when selecting a configurator item under
Order management.
 Modified required TNS service name to be ebs_<PDB SID> instead of <PDB
SID>.
 Added that only writable Oracle homes are supported.
2021-
 Replaced 19.8.0.0.0 UNIX/Linux information with 19.10.0.0.0.
02-16
 Replaced 19.7.0.0.0 Windows information with 19.9.0.0.0.
 Updated consolidated zip file to Patch 32288957.
 Added Oracle Database 19.9.0.0.0 Patch 31334961, Patch 31405300, Patch
31424070, and Patch 31903523.
 Added note on possible errors when running <source SID>_initparam.sql.

2021-  Updated consolidated zip file to Patch 31770871.

01-08
 Removed 19.7.0.0.0 UNIX/Linux information.
 Added 19.9.0.0.0 UNIX/Linux information.
 Added information to measure performance.
2020-
 Replaced Oracle Database 19.8.0.0.0 Patch 29867728 and Patch 31178103
11-17
with Patch 28698087, Patch 30336383, Patch 30518349, Patch 31142749,
Patch 31404014, Patch 31802118, and Patch 31820859.

 Added consolidated zip file Patch 31381618 information.

2020-
 Added step to reconfigure external nodes.
11-06
2020-  Added Oracle Database Release Update information.
08-27
 Replaced Oracle Database 19.7.0.0.0 Patch 30125765 with Patch 30621255,
2020-
Patch 30758943, Patch 31113249, Patch 31413115, and Patch 31178103.
08-13
 Created Appendix A containing the patch list of the latest Database Release
Update.
 Replaced the list of 19.3.0.0.0 Database patches to a link to Appendix A.
2020-
 Removed step to apply the latest Database Release Update.
08-11
 Removed step to create Demantra privileges.
 Added 19.8.0.0.0 Database patch list.

2020-  Added Oracle Database Patch 31178103.

08-04
 Replaced 19.6.0.0.0 Windows information with 19.7.0.0.0.
 Added Oracle E-Business Suite Patch 31406810.
 Modified TDE related steps to make it clearer.
2020-
 Added Oracle Value Chain Planning prerequisite.
06-30
 Added Demantra Demand Management and Oracle Demand Planning to list
of unsupported products.

 Added Oracle Database Patch 31113249.

2020-
 Replaced 19.5.0.0.0 UNIX/Linux information with 19.7.0.0.0.
05-14
 Removed setting event 10995 trace name context forever, level 16.
 Modified document format.
2020-  Added Windows instructions.
04-23  Added Oracle E-Business Suite Patch 31209544, and Patch 30824278.
 Added Oracle Database Patch 30431274.

 Added Database Release Update 19.6.0.0.0 information.

2020-
 Removed 19.5.0.0.0 Oracle Database Patch 28318139.
02-06
2019-  Added Oracle E-Business Suite Patch 30601878.
12-03
 Added Oracle E-Business Suite Patch 30370150.
 Added ISG-related steps and removed ISG from unsupported product list.
2019-  Added Oracle Database Patch 30193505.
11-27  Supplied event initialization parameters to be added pre-upgrade.
 Added step to copy the orai18n.jar file.

2019-  Added bug 30139564 for the Order management known issue.
11-13
2019-  Added step to apply the latest release update.
11-05
2019-  Initial publication.
09-13
My Oracle Support Knowledge Document 2580629.1 by Oracle E-Business Suite
Development.