Installation Guide: Oracle Apps R12.2.12 on Oracle Linux OEL 7.9 using Oracle VirtualBox

 

Introduction:

Welcome to our comprehensive Installation guide for Oracle Apps R12.2.12, the latest release by Oracle, on the Oracle Linux OEL 7.9 platform, utilizing Oracle VirtualBox. This post, along with the subsequent ones, will provide step-by-step instructions to ensure a successful installation.

Hardware Requirements:

To proceed with the installation, please ensure that your hardware meets the following prerequisites. For reference, we will be using a laptop with the following configuration:

1. 250 GB Hard Disk: This allocation is for the operating system and the staging area. If desired, you can allocate 110 GB instead (50 GB for the operating system and 60 GB for the staging area).
2. An additional 300 GB Hard Disk: This disk will be dedicated to the Application File System and the Database.
3. 16 GB of RAM: We recommend assigning this amount to the virtual machine. However, 12 GB can be allocated if necessary.
4. Minimum of 16 GB Swap Space: In our setup, we will configure it with 20 GB.

Software Requirements:

Before proceeding with the installation, ensure that you have the following software components available:

1. – Oracle VirtualBox:  We will Explore this in Detail in the Action Plan of this Blog 
2. – Oracle Linux 7.9: We will be using version OEL 7.9 in this scenario, you may choose another recommended version based on your preferences. Even OEL 8.2 and Above is Certified with Oracle E-Business Suite.
3. – Oracle E-Business Suite (EBS) R12.2: We will Explore this in Detail in the Action Plan of this Blog .

Action Plan for The Installation:

The installation process will be divided into the following parts, as illustrated below. Each part will be thoroughly explored and discussed in detail as presented below.

 

Part 1. Oracle VirtualBox Installation

This involves setting up the virtualization software and configuring the required network adapters and storage settings.

Virtual Box Installation Link

 

Part 2. Oracle Linux Installation and Configuration

 Here, we will guide you through the installation of Oracle Linux 7.9 and the configuration of essential RPM packages. Furthermore, we will cover the necessary pre-installation setups specific to Oracle Linux.

Oracle Linux Installation Link

Oracle Linux Configuration Link

 

Part 3. Downloading and Creating a Staging Area of Oracle E-Business Suite

In this Part, we will provide a comprehensive walkthrough of the process for downloading and creating a dedicated staging area specifically designed for Oracle Apps R12.2. By following these steps, you will be able to establish a well-organized staging area, guaranteeing a seamless installation process.

Oracle Media Download Procedure Link

Creating Staging Area for EBS Link

 

Part 4. Installing Oracle Apps R12.2.0

This Part covers the installation of Oracle Apps R12.2.0, followed by a verification process to ensure successful deployment.

Oracle Apps R12.2.0 Installation Link

 

Part 5. Oracle Apps Upgrade from 12.2.0 to 12.2.12

This Part covers the upgrade process of  Oracle Apps R12.2.0 to 12.2.12, followed by a verification process to ensure a successful upgrade.

Oracle EBS Apps Upgrade from 12.2.0 to 12.2.12

 

Part 6. Oracle EBS APPS 12.2.12 Database Upgrade from 12.1.0.2 to 19.19

This Part covers the upgrade process of Oracle Apps R12.2.12 Database from 12c to 19c, followed by a verification process to ensure a successful upgrade.

Oracle EBS Database Upgrade from 12c to 19c Part-1

Oracle EBS Database Upgrade from 12c to 19c Part-2

 

 

 

Oracle EBS Database Upgrade from 12c to 19c Part-2

 

This post is a continuation of the previous article on Oracle EBS Database Upgrade from 12c to 19c Part-1. Here, we will delve into the remaining part of the database upgrade process from 12c to 19c. Let’s begin with Section 6, building upon Section 5 discussed in the last post.

 

Section 6 – Create the CDB through DBCA

Step 1. Create the CDB

On the database server node Source 19c environment and run below from GUI Terminal/VNC Run the Database Configuration Assistant (DBCA) to create the container database (CDB). When prompted, click on the “Create Database”, “Advanced Configuration”, and “General Purpose or Transaction Processing” options. In the Specify Database Identification screen, check to create an empty container database (CDB) without a PDB. Set the Global Database Name, the SID to the new CDB SID (maximum of 8 characters)(prodcdb), 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. 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. Click on the Character Sets tab and choose the Character Set and National Character Set to be the same as in the source database. 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.

 

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$  cd $ORACLE_HOME/bin

[oracle@test1 bin]$ ./dbca

Select “Create a Database” Click Next
Select “Advance Configuration” Click Next
Select “General Purpose or Transaction Processing” Click Next
Enter the Following Highlighted Select “Create as Container Database”  Select “Use Local Undo tablespace for PDBs” Click Next
Select The Following as Shown in the Picture Click Next
Click Next
Click Next
Click Next
Enter the Following as Shown in the Picture  Click “Character Sets” TAB
Select The Following as Shown in the Picture Click Next
De Select the Following EM Configuration Click Next
Enter Password Click Next
Select “Create Database”  Click Next
Click Finish
Database Creation Process Starts
Click Close

 

Step 2. Run DataPatch on the CDB

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

Source 19 environment File

[oracle@test1 ~]$ . ./19c.env [oracle@test1 ~]$ export ORACLE_SID=prodcdb [oracle@test1 ~]$ $ORACLE_HOME/OPatch/datapatch SQL Patching tool version 19.19.0.0.0 Production on Mon Jul 17 03:01:50 2023 Copyright (c) 2012, 2023, Oracle.  All rights reserved. Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_29132_2023_07_17_03_01_50/ sqlpatch_invocation.log Connecting to database…OK Gathering database info…done   Note:  Datapatch will only apply or rollback SQL fixes for PDBs        that are in an open state, no patches will be applied to closed PDBs.        Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation        (Doc ID 1585822.1) Bootstrapping registry and package to current versions…done Determining current state…done Current state of interim SQL patches: Interim patch 35050341 (OJVM RELEASE UPDATE: 19.19.0.0.230418 (35050341)):   Binary registry: Installed   PDB CDB$ROOT: Applied successfully on 17-JUL-23 02.35.23.436147 AM   PDB PDB$SEED: Applied successfully on 17-JUL-23 02.47.06.787785 AM Interim patch 35406065 (RESTORE DATABASE PREVIEW FAILING WITH RMAN-00600 [7004] [0] [KRMR_GET_ARCHIVED_NEXT_SCN_ALSCN] AFTER):   Binary registry: Installed   PDB CDB$ROOT: Applied successfully on 17-JUL-23 02.35.23.546590 AM   PDB PDB$SEED: Applied successfully on 17-JUL-23 02.47.06.898928 AM Current state of release update SQL patches:   Binary registry:     19.19.0.0.0 Release_Update 230322020406: Installed   PDB CDB$ROOT:     Applied 19.19.0.0.0 Release_Update 230322020406 successfully on 17-JUL-23 02.35.23.428107 AM   PDB PDB$SEED:     Applied 19.19.0.0.0 Release_Update 230322020406 successfully on 17-JUL-23 02.47.06.781113 AM Adding patches to installation queue and performing prereq checks…done Installation queue:   For the following PDBs: CDB$ROOT PDB$SEED     No interim patches need to be rolled back     No release update patches need to be installed     No interim patches need to be applied SQL Patching tool complete on Mon Jul 17 03:02:14 2023

 

 

Step 3. 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

Source 19c Environment

[oracle@test1 ~]$ . ./19c.env [oracle@test1 ~]$ sqlplus ‘/as sysdba’ SQL*Plus: Release 19.0.0.0.0 – Production on Mon Jul 17 03:04:08 2023 Version 19.19.0.0.0 Copyright (c) 1982, 2022, Oracle.  All rights reserved. Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production Version 19.19.0.0.0 SQL> @$ORACLE_HOME/rdbms/admin/catmgd.sql This creates the new MGDSYS schema on the CDB.

 

 

Step 4. 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. $ 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

 

[oracle@test1 ~]$ . ./19c.env [oracle@test1 ~]$ cd $ORACLE_HOME/appsutil [oracle@test1 appsutil]$ . ./txkSetCfgCDB.env dboraclehome=$ORACLE_HOME  Oracle Home being passed: /u01/oracle/PROD/19.0.0 [oracle@test1 appsutil]$ cd $ORACLE_HOME/appsutil/bin  [oracle@test1 bin]$ perl txkGenCDBTnsAdmin.pl -dboraclehome=$ORACLE_HOME -cdbname=prodcdb -cdbsid=prodcdb -dbport=1522 -outdir=$ORACLE_HOME/appsutil/log Script Name    : txkGenCDBTnsAdmin.pl Script Version : 120.0.12020000.11 Started        : Mon Jul 17 03:10:02 PKT 2023 Log File       : /u01/oracle/PROD/19.0.0/appsutil/log/ TXK_CDB_TNS_ADMIN_Mon_Jul_17_03_10_02_2023/txkGenCDBTnsAdmin.log ———– Values used ———– Database Oracle Home    : /u01/oracle/PROD/19.0.0 CDB NAME                : prodcdb CDB SID                 : prodcdb Database port           : 1522 OUT Directory           : /u01/oracle/PROD/19.0.0/appsutil/log Is RAC?                 : No Virtual Hostname        : Logical Hostname        : Script execution mode   : generate ========================= Validating oracle home… ========================= Oracle Home: /u01/oracle/PROD/19.0.0 exists. =========================== Validating out directory… =========================== Out directory: /u01/oracle/PROD/19.0.0/appsutil/log exists. =================================== Validating script execution mode… =================================== Script execution mode: generate Script execution mode is valid. ============================ Inside getDBHostDetails()… ============================ DB Hostname : test1 DB Domain   : example.com Logical hostname is not passed, hence using physical hostname details. Logical Hostname : test1 Logical Domain   : example.com ===================== Inside getDBPort()… ===================== DB Port passed as an argument, using the same. DB Port: 1522 ====================================== Inside generateCDBTNSAdminContent()… ====================================== Creating the directory: /u01/oracle/PROD/19.0.0/appsutil/log/ TXK_CDB_TNS_ADMIN_Mon_Jul_17_03_10_02_2023/tns_admin_cdb_bkp Creating the directory: /u01/oracle/PROD/19.0.0/appsutil/log/ TXK_CDB_TNS_ADMIN_Mon_Jul_17_03_10_02_2023/tns_admin_cdb_temp listener_template: listener_ora_cdb_db19.tmp sqlnet_template: sqlnet_ora_cdb_db19.tmp Copying the file —————- SOURCE : /u01/oracle/PROD/19.0.0/appsutil/template/listener_ora_cdb_db19.tmp TARGET : /u01/oracle/PROD/19.0.0/appsutil/log/TXK_CDB_TNS_ADMIN_Mon_Jul_17_03_10_02_2023 /tns_admin_cdb_temp/listener.ora =================================== Inside replaceContextVariables()… =================================== File /u01/oracle/PROD/19.0.0/network/admin/listener.ora does not exist. Copying the file —————- SOURCE : /u01/oracle/PROD/19.0.0/appsutil/log/TXK_CDB_TNS_ADMIN_Mon_Jul_17_03_10_02_2023 /tns_admin_cdb_temp/listener.ora TARGET : /u01/oracle/PROD/19.0.0/network/admin/listener.ora Copying the file —————- SOURCE : /u01/oracle/PROD/19.0.0/appsutil/template/tnsnames_ora_cdb_db121.tmp TARGET : /u01/oracle/PROD/19.0.0/appsutil/log/TXK_CDB_TNS_ADMIN_Mon_Jul_17_03_10_02_2023 /tns_admin_cdb_temp/tnsnames.ora =================================== Inside replaceContextVariables()… =================================== File /u01/oracle/PROD/19.0.0/network/admin/tnsnames.ora does not exist. Copying the file —————- SOURCE : /u01/oracle/PROD/19.0.0/appsutil/log/TXK_CDB_TNS_ADMIN_Mon_Jul_17_03_10_02_2023 /tns_admin_cdb_temp/tnsnames.ora TARGET : /u01/oracle/PROD/19.0.0/network/admin/tnsnames.ora Copying the file —————- SOURCE : /u01/oracle/PROD/19.0.0/appsutil/template/sqlnet_ora_cdb_db19.tmp TARGET : /u01/oracle/PROD/19.0.0/appsutil/log/TXK_CDB_TNS_ADMIN_Mon_Jul_17_03_10_02_2023 /tns_admin_cdb_temp/sqlnet.ora =================================== Inside replaceContextVariables()… =================================== File /u01/oracle/PROD/19.0.0/network/admin/sqlnet.ora does not exist. Copying the file —————- SOURCE : /u01/oracle/PROD/19.0.0/appsutil/log/TXK_CDB_TNS_ADMIN_Mon_Jul_17_03_10_02_2023 /tns_admin_cdb_temp/sqlnet.ora TARGET : /u01/oracle/PROD/19.0.0/network/admin/sqlnet.ora ============================== Inside updateCDBSqlNetOra()… ============================== Updating the IFILE entry… Exiting from the script. Ended: Mon Jul 17 03:10:02 PKT 2023

 

Step 5. Shut down the CDB

Source 19c environment file and Use SQL*Plus to connect to the CDB as SYSDBA and use the following command to shut down the database:

[oracle@test1 bin]$ sqlplus / as sysdba SQL*Plus: Release 19.0.0.0.0 – Production on Mon Jul 17 03:12:11 2023 Version 19.19.0.0.0 Copyright (c) 1982, 2022, Oracle.  All rights reserved. Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production Version 19.19.0.0.0 SQL> shutdown immediate; Database closed. Database dismounted. ORACLE instance shut down.

 

 

---

 

Section 7 – Preparing DB Upgrade

Step 1. Complete the patching cycle and remove ADOP-created editions

As the owner of the source administration server, execute any of the following commands that have not been executed before. This action will remove any editions that were created during previous adop patching cycles, thereby cleaning up the environment. Additionally, these commands will finalize any pending patching cycles that are still open.

On Application Tier source run file system environment 

[oracle@test1 ~]$ . ./EBSapps.env run   E-Business Suite Environment Information   —————————————-   RUN File System           : /u01/oracle/PROD/fs2/EBSapps/appl   PATCH File System         : /u01/oracle/PROD/fs1/EBSapps/appl   Non-Editioned File System : /u01/oracle/PROD/fs_ne   DB Host: test1.example.com  Service/SID: PROD   Sourcing the RUN File System …

$ adop phase=prepare 

$ adop phase=actualize_all   

$ adop phase=finalize finalize_mode=full 

$ adop phase=cutover mtrestart=no 

Note: The steps mentioned above may require a significant amount of time to complete. Therefore, it is advised to relax and monitor the progress during this period.

 

Source the Environment Again On the new run file system

oracle@test1 ~]$ . ./EBSapps.env run   E-Business Suite Environment Information   —————————————-   RUN File System           : /u01/oracle/PROD/fs2/EBSapps/appl   PATCH File System         : /u01/oracle/PROD/fs1/EBSapps/appl   Non-Editioned File System : /u01/oracle/PROD/fs_ne   DB Host: test1.example.com  Service/SID: PROD   Sourcing the RUN File System …

 

$ adop phase=cleanup cleanup_mode=full

These maintenance operations will have a significantly longer duration compared to a typical online patching cycle. Therefore, it is recommended to perform them only when there is no urgent requirement to initiate a new online patching cycle.

The applications will be unavailable to users until all remaining tasks are completed.

 

You Can monitor the above process through ADOPMON

[oracle@test1 PROD]$ adopmon Running script. Press Ctrl-C to quit. Enter the APPS password: Validating credentials… Printing the log statements starting from sequence #702651 Timestamp           Node name           Message Type Message Text ————————————————————————————————————————— 2023/07/17 17:30:38 test1               EVENT        Drop covered objects, pass #11 complete, dropped: 122, errors: 0 2023/07/17 17:31:03 test1               EVENT        Drop covered objects, pass #12 complete, dropped: 52, errors: 0 2023/07/17 17:31:19 test1               EVENT        Drop covered objects, pass #13 complete, dropped: 15, errors: 0 2023/07/17 17:31:35 test1               EVENT        Drop covered objects, pass #14 complete, dropped: 1, errors: 0 2023/07/17 17:31:47 test1               EVENT        Drop covered objects, pass #15 complete, dropped: 0, errors: 0 2023/07/17 17:31:47 test1               EVENT        Drop Covered Objects – alternate method 2023/07/17 17:32:10 test1               EVENT        Cleanup crossedition triggers 2023/07/17 17:32:11 test1               EVENT        Cleanup unused columns 2023/07/17 17:33:04                     EVENT        Drop Edition: “ORA$BASE” 2023/07/17 18:25:51                     EVENT        Drop Edition: “V_20230716_1415” 2023/07/17 18:25:55 test1               EVENT        Generating log report. 2023/07/17 18:25:55 test1               EVENT        Output: /u01/oracle/PROD/fs_ne/EBSapps                                                           /log/adop/8/20230717_144033/clea                                                      nup/test1/adzdshowlog.out 2023/07/17 18:25:56 test1               EVENT        The cleanup phase completed successfully.

 

 

 Step 2. Store the UTL_FILE_DIR parameter values

In Oracle EBS, the PLSQL IO files are typically stored in the /usr/tmp directory of the Database Node. This is a common practice across all EBS versions, starting from 11i to R12.2. EBS achieves this by utilizing the UTL_FILE_DIR initialization parameter. However, starting from version 18c, the UTL_FILE_DIR initialization parameter has been deprecated and is no longer supported.

To address this change in Oracle 19c, Oracle for EBS has introduced new views in the APPS schema, namely apps.v$parameter and apps.v$parameter2, which provide a supplemental parameter for UTL_FILE_DIR. In order to configure this parameter, please refer to the instructions provided in Section 3.1.1 of the document titled ‘Using UTL_FILE_DIR or Database Directories for PL/SQL File I/O in Oracle E-Business Suite Releases 12.1 and 12.2′ (Doc ID 2525754.1).”

Now, we need to execute the txkCfgUtlfileDir.pl script twice in different modes to complete this task. First, run the script in the ‘getUtlFileDir‘ mode to retrieve the directory paths previously specified in the UTL_FILE_DIR database initialization parameter and prepare them for the upgrade. Subsequently, execute the script in the ‘setUtlFileDir’ mode to store the directory paths in the new Oracle E-Business Suite tables that underlie the apps.v$parameter and apps.v$parameter2 views, and to create the corresponding directory objects.

 

To retrieve the directory path values from the source UTL_FILE_DIR database initialization parameter, follow these steps:

a) Source the Oracle E-Business Suite database environment of your 11g or 12c Oracle home.

[oracle@test1 ~]$ . ./PROD_test1.env [oracle@test1 ~]$ echo $CONTEXT_FILE /u01/oracle/PROD/12.1.0/appsutil/PROD_test1.xml [oracle@test1 ~]$ echo $ORACLE_HOME /u01/oracle/PROD/12.1.0

 

b) Run txkCfgUtlfileDir.pl script in getUtlFileDir mode using the following command:

$ perl $ORACLE_HOME/appsutil/bin/txkCfgUtlfileDir.pl -contextfile=<DB Context File> -oraclehome=<11g/12c ORACLE_HOME> -outdir=<Output/Log location> -upgradedhome=<19c ORACLE_HOME> -mode=getUtlFileDir -servicetype=onpremise|opc [oracle@test1 ~]$ perl $ORACLE_HOME/appsutil/bin/txkCfgUtlfileDir.pl -contextfile=/u01/oracle/PROD/12.1.0/appsutil/PROD_test1.xml -oraclehome=/u01/oracle/PROD/12.1.0 -outdir=/tmp -upgradedhome=/u01/oracle/PROD/19.0.0  -mode=getUtlFileDir -servicetype=onpremise Enter the APPS Password: Script Name    : txkCfgUtlfileDir.pl Script Version : 120.0.12020000.29 Started        : Mon Jul 17 18:47:47 PKT 2023 Log File       : /tmp/TXK_UTIL_DIR_Mon_Jul_17_18_47_46_2023/txkCfgUtlfileDir.log   Context file: /u01/oracle/PROD/12.1.0/appsutil/PROD_test1.xml exists.   ==============================================================================   Successfully generated the below file with UTL_FILE_DIR content: /u01/oracle/PROD/12.1.0/dbs/PROD_utlfiledir.txt   ==============================================================================   Completed        : Mon Jul 17 18:47:48 PKT 2023 Successfully Completed the script ERRORCODE = 0 ERRORCODE_END Using this command, the script retrieves the directory paths stored in the UTL_FILE_DIR database initialization parameter. It then modifies these paths to prepare them for usage in Oracle Database 19c. As a result, a text file named <DB_NAME>_utlfiledir.txt is created in the <ORACLE_HOME>/dbs directory. This file contains the list of modified directory paths. Additionally, the script saves the original values from the 11g or 12c UTL_FILE_DIR database initialization parameter, along with the corresponding 19c replacement values, in a text file located in the log directory. To review the modifications made by the script, you can compare this log file with the <DB_NAME>_utlfiledir.txt file present in the <ORACLE_HOME>/dbs directory.

 

c) Creating the directory paths of the directories for UTL in the end of the file created /u01/oracle/PROD/12.1.0/dbs/PROD_utlfiledir.txt

[oracle@test1 ~]$ cat /u01/oracle/PROD/12.1.0/dbs/PROD_utlfiledir.txt /u01/oracle/PROD/temp/PROD /u01/oracle/PROD/temp/PROD /u01/oracle/PROD/19.0.0/appsutil/outbound/PROD_test1 /u01/oracle/PROD/temp/PROD [oracle@test1 ~]$ mkdir -p /u01/oracle/PROD/temp/PROD [oracle@test1 ~]$ mkdir -p /u01/oracle/PROD/temp/PROD [oracle@test1 ~]$ mkdir -p /u01/oracle/PROD/19.0.0/appsutil/outbound/PROD_test1 [oracle@test1 ~]$ mkdir -p /u01/oracle/PROD/temp/PROD

Source the Oracle E-Business Suite database environment of your 11g or 12c Oracle home.

[oracle@test1 ~]$ . ./PROD_test1.env Run the txkCfgUtlfileDir.pl script in setUtlFileDir mode using the following command: $ perl $ORACLE_HOME/appsutil/bin/txkCfgUtlfileDir.pl -contextfile=<DB Context File> -oraclehome=<11g/12c ORACLE_HOME> -outdir=<Output/Log location> -upgradedhome=<19c ORACLE_HOME> -mode=setUtlFileDir -servicetype=onpremise|opc [ -skipdirvalidation=Yes ] [oracle@test1 ~]$ perl $ORACLE_HOME/appsutil/bin/txkCfgUtlfileDir.pl -contextfile=/u01/oracle/PROD/12.1.0/appsutil/PROD_test1.xml -oraclehome=/u01/oracle/PROD/12.1.0 -outdir=/tmp -upgradedhome=/u01/oracle/PROD/19.0.0  -mode=setUtlFileDir -servicetype=onpremise Enter the APPS Password: Script Name    : txkCfgUtlfileDir.pl Script Version : 120.0.12020000.29 Started        : Mon Jul 17 19:03:46 PKT 2023 Log File       : /tmp/TXK_UTIL_DIR_Mon_Jul_17_19_03_45_2023/txkCfgUtlfileDir.log Context file: /u01/oracle/PROD/12.1.0/appsutil/PROD_test1.xml exists. Enter the ebs_system Password: Completed        : Mon Jul 17 19:03:52 PKT 2023 Successfully Completed the script ERRORCODE = 0 ERRORCODE_END

 

Step 3. 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.

This should be already down based on pervious adop cycle steps.

 

Step 4. Drop SYS.ENABLED$INDEXES

Source 12c Database environment file

If the SYS.ENABLED$INDEXES table exists, connect to the database as SYSDBA, and run the following command to drop the table:

[oracle@test1 ~]$ sqlplus / as sysdba SQL> drop table sys.enabled$indexes; drop table sys.enabled$indexes                * ERROR at line 1: ORA-00942: table or view does not exist Proceed Further if table doesn’t exists.

 

Step 5. Shut down the database listener

Source 12c Environment file

[oracle@test1 ~]$ . ./PROD_test1.env

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

[oracle@test1 ~]$ lsnrctl stop $ORACLE_SID

LSNRCTL for Linux: Version 12.1.0.2.0 – Production on 17-JUL-2023 19:09:23

Copyright (c) 1991, 2014, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=test1.example.com)(PORT=1521)))

The command was completed successfully

 

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.

 

[oracle@test1 ~]$ sqlplus / as sysdba

SQL> show parameter LOCAL_LISTENER

NAME                                                      TYPE VALUE

———————————— ———– ——————————

local_listener                                         string               PROD_LOCAL

SQL> alter system set local_listener=”;

System altered.

SQL> show parameter LOCAL_LISTENER

NAME                                                      TYPE VALUE

———————————— ———– —- ————————–

local_listener                                         string

 

Step 6. Database Pre Upgrade Steps

Modify the following initialization parameters before the upgrade:

• Comment out all the deprecated initialization parameters. Any necessary parameter will be added back in after the upgrade.
• Unset the olap_page_pool_size initialization parameter.

SQL> alter system set olap_page_pool_size=0 scope=spfile;

• If you have an 11g source database, set the PGA_AGGREGATE_TARGET initialization parameter to at least 10G.
• Set the SGA_TARGET initialization parameter to at least 2G.
• Add the event EVENT=’10946 trace name context forever, level 8454144‘

SQL>  alter system set event=’10946 trace name context forever, level 8454144′ scope=spfile;

Shut down and restart the database to enable the parameters.

 

Step 7. Run the Pre-upgrade Tool

Connect to the 12c Database and run the command as below:

[oracle@test1 ~]$ /u01/oracle/PROD/12.1.0/jdk/bin/java -jar /u01/oracle/PROD/19.0.0/rdbms/admin/preupgrade.jar

==================

PREUPGRADE SUMMARY

==================

  /u01/oracle/PROD/12.1.0/cfgtoollogs/PROD/preupgrade/preupgrade.log

  /u01/oracle/PROD/12.1.0/cfgtoollogs/PROD/preupgrade/preupgrade_fixups.sql

  /u01/oracle/PROD/12.1.0/cfgtoollogs/PROD/preupgrade/postupgrade_fixups.sql

Execute fixup scripts as indicated below:

Before upgrade:

Log into the database and execute the preupgrade fixups

@/u01/oracle/PROD/12.1.0/cfgtoollogs/PROD/preupgrade/preupgrade_fixups.sql

After the upgrade:

Log into the database and execute the postupgrade fixups

@/u01/oracle/PROD/12.1.0/cfgtoollogs/PROD/preupgrade/postupgrade_fixups.sql

 

As per the recommendation above by the Pre Upgrade tool we will execute preupgrade_fixups.sql

SQL> alter system set processes=300 scope=spfile; SQL>set head off SQL>zet lines 200 pages 200 SQL>set echo off SQL>set feedback off; SQL>spool hidden_parameter.sql SQL>SELECT ‘alter system reset ‘||'”‘||name||'”‘||’ scope =spfile;’ FROM SYS.V$PARAMETER WHERE name LIKE ‘_%’ ESCAPE ”; SQL>spool off SQL>@hidden_parameter.sql   SQL> @/u01/oracle/PROD/12.1.0/cfgtoollogs/PROD/preupgrade/preupgrade_fixups.sql Executing Oracle PRE-Upgrade Fixup Script Auto-Generated by:       Oracle Preupgrade Script                          Version: 19.0.0.0.0 Build: 13 Generated on:            2023-07-17 21:56:05 For Source Database:     PROD Source Database Version: 12.1.0.2.0 For Upgrade to Version:  19.0.0.0.0 Preup                             Preupgrade Action                            Issue Is Number  Preupgrade Check Name     Remedied    Further DBA Action ——  ————————  ———-  ——————————– parameter_min_val         NO          Manual fixup recommended. parameter_obsolete        NO          Manual fixup recommended. invalid_objects_exist     NO          Manual fixup recommended. amd_exists                NO          Manual fixup recommended. duplic_sys_system_objs    NO          Manual fixup recommended. exclusive_mode_auth       NO          Manual fixup recommended. case_insensitive_auth     NO          Manual fixup recommended. mv_refresh                NO          Manual fixup recommended. hidden_params             NO          Informational only.                                               Further action is optional. underscore_events         NO          Informational only.                                               Further action is optional. dictionary_stats          YES         None. trgowner_no_admndbtrg     YES         None. component_info            NO          Informational only.                                               Further action is optional. parameter_deprecated      NO          Informational only.                                               Further action is optional. rman_recovery_version     NO          Informational only.                                               Further action is optional. invalid_ora_obj_info      NO          Informational only.                                               Further action is optional. invalid_app_obj_info      NO          Informational only.                                               Further action is optional. The fixup scripts have been run and resolved what they can. However, there are still issues originally identified by the preupgrade that have not been remedied and are still present in the database. Depending on the severity of the specific issue, and the nature of the issue itself, that could mean that your database is not ready for upgrade.  To resolve the outstanding issues, start by reviewing the preupgrade_fixups.sql and searching it for the name of the failed CHECK NAME or Preupgrade Action Number listed above. There you will find the original corresponding diagnostic message from the preupgrade which explains in more detail what still needs to be done.   PL/SQL procedure successfully completed.

 

 

---

 

Section 8 – Upgrade the database instance

Step 1. Running Database Upgrade using DBUA 

Invoke DBUA using the following command. The keep events parameter allows events in the pre-upgraded database to be enabled during the upgrade.

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.

Disregard warnings related to Network ACLs. AutoConfig manages all the Oracle E-Business Suite Network ACLs.

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

Make sure 12c db entry is present in /etc/oratab. Open GUI and run the below command

Source 19c Environment file

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$ $ORACLE_HOME/bin/dbua -keepEvents

Select “PROD” Enter User SYS and Password Click Next
Wait for Performing Pre-Upgrade Checks
Click Next
Click Yes
Select the following as shown in the Picture Click Next
Select “I have my own Backup and restore strategy” Click Next
Click Next
Deselect the following in the Picture Click Next
Click Finish
Database Upgrade Started
Click Close

The database upgrade has been completed successfully, and the database is ready to use.

SQL> select banner from v$version;

BANNER

——————————————————————————–

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production

Step 2. Run the Post Upgrade Script generated during the Pre-Upgrade Steps

Source 19c Environment

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$ export ORACLE_SID=PROD

SQL> @/u01/oracle/PROD/12.1.0/cfgtoollogs/PROD/preupgrade/postupgrade_fixups.sql

 

Step 3. Post-Upgrade Tasks

Source 19c Environment

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$ export ORACLE_SID=PROD

There are few important post-upgrade miscellaneous tasks that need to be performed.

If you previously had the SEC_CASE_SENSITIVE_LOGON initialization parameter set to FALSE, re-enable the parameter.

In case spfile is not there then create spfile and restart database.

SQL> alter system set SEC_CASE_SENSITIVE_LOGON=false;

System altered.

SQL> alter trigger SYSTEM.EBS_LOGON compile;

Trigger altered.

SQL> alter system set compatible=’19.0.0′ scope=spfile;

System altered.

Restart DB

SQL> shu immediate;

Database closed.

Databas edismounted.

ORACLE instance shut down.

SQL> startup

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

ORACLE instance started.

Total System Global Area 4294963248 bytes

Fixed Size            8933424 bytes

Variable Size           2583691264 bytes

Database Buffers  1677721600 bytes

Redo Buffers               24616960 bytes

Database mounted.

Database opened.

SQL> show parameter compatible

NAME                         TYPE   VALUE

———————————— ———– ——————————

compatible                   string 19.0.0

noncdb_compatible            boolean      FALSE

 

Step 4. Run DataPatch

Source 19c Environment

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$ export ORACLE_SID=PROD

[oracle@test1 OPatch]$ $ORACLE_HOME/OPatch/datapatch

 

Step 5. Connect to sysdba and run below

Source 19c Environment

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$ export ORACLE_SID=PROD

SQL> @?/rdbms/admin/dbmsxdbschmig.sql

SQL> @?/rdbms/admin/prvtxdbschmig.plb

 

Step 6. Run ADgrants

Source 19c Environment

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$ export ORACLE_SID=PROD

Copy adgrants.sql from $APPL_TOP/admin to DB tier and run it

[oracle@test1 ~]$ cp /u01/oracle/PROD/fs1/EBSapps/appl/admin/adgrants.sql /u01/oracle/PROD/19.0.0/appsutil

SQL> @/u01/oracle/PROD/19.0.0/appsutil/adgrants.sql apps

 

Step 7. Grant create procedure privilege on CTXSYS

Source 19c Environment

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$ export ORACLE_SID=PROD

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:

[oracle@test1 admin]$ cp $AD_TOP/patch/115/sql/adctxprv.sql /u01/oracle/PROD/19.0.0/

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

[oracle@test1 ~]$ cd /u01/oracle/PROD/19.0.0/

[oracle@test1 19.0.0]$ sqlplus apps/apps @adctxprv.sql oracle CTXSYS

SQL*Plus: Release 19.0.0.0.0 – Production on Tue Jul 18 01:16:40 2023

Version 19.19.0.0.0

Copyright (c) 1982, 2022, Oracle.  All rights reserved.

Last Successful login time: Mon Jul 17 2023 19:03:52 +05:00

Connected to:

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production

Version 19.19.0.0.0

Commit complete.

Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production

Version 19.19.0.0.0

 

Step 8. Compile invalid objects

Source 19c Environment

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$ export ORACLE_SID=PROD

Use SQL*Plus to connect to the database as SYSDBA and run the $ORACLE_HOME/rdbms/admin/utlrp.sql script to compile invalid objects.

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

Run the following Query to check the INVALID Objects

SQL> select count(*) from dba_objects where status=’INVALID’;

 

Step 9. Grant datastore access

Source 19c Environment

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$ export ORACLE_SID=PROD

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

[oracle@test1 ~]$ sqlplus “/ as sysdba”

SQL> grant text datastore access to public;

Grant succeeded.

 

Step 10. Gather statistics for the SYS schema

Source 19c Environment

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$ export ORACLE_SID=PROD

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:

[oracle@test1 19.0.0]$  cp /u01/oracle/PROD/fs1/EBSapps/appl/admin/adstats.sql /u01/oracle/PROD/19.0.0/

[oracle@test1 ~]$ sqlplus / as sysdba

SQL> alter system enable restricted session;

System altered.

SQL> @adstats.sql

Connected.

————————————————–

— adstats.sql started at 2023-07-18 11:48:37 —

Checking for the DB version and collecting statistics …

PL/SQL procedure successfully completed.

————————————————

— adstats.sql ended at 2023-07-18 11:55:38 —

Commit complete.

Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production

Version 19.19.0.0.0

[oracle@test1 19.0.0]$ sqlplus / as sysdba

SQL> alter system disable restricted session;

System altered.

SQL> exit

 

Step 11. Convert Database to Multitenant Architecture or PDB

Source 19c Environment

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$ export ORACLE_SID=PROD

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

 

a) Create the PDB descriptor

• $ cd $ORACLE_HOME/appsutil
• $ . ./txkSetCfgCDB.env dboraclehome=<full path of 19c 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>

[oracle@test1 ~]$  cd $ORACLE_HOME/appsutil[oracle@test1 appsutil]$ . ./txkSetCfgCDB.env dboraclehome=/u01/oracle/PROD/19.0.0 Oracle Home being passed: /u01/oracle/PROD/19.0.0

oracle@test1 appsutil]$ export ORACLE_SID=PROD

oracle@test1 appsutil]$ cd $ORACLE_HOME/appsutil/bin

oracle@test1 bin]$ perl txkOnPremPrePDBCreationTasks.pl -dboraclehome=/u01/oracle/PROD/19.0.0 -outdir=/u01/oracle/PROD/19.0.0/appsutil/log -appsuser=apps -dbsid=PROD

Enter the APPS Password:

 

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

*                                                                                      *

*         IMPORTANT NOTE: DO NOT START THE DB TILL THE DATA FILES ARE MIGRATED         *

*                                                                                      *

*         IF DB IS STARTED, THEN PDB DESCRIPTOR XML GENERATED BECOMES INVALID          *

*                                                                                      *

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

Exiting from the script.

Ended: Tue Jul 18 12:01:42 PKT 2023

 

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

• $ 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>:<cdb port number>” scope=both;
• SQL> shutdown;
• SQL> startup;

[oracle@test1 bin]$ cd /u01/oracle/PROD/12.1.0/dbs

[oracle@test1 dbs]$ cp PROD_initparam.sql PROD_datatop.txt /u01/oracle/PROD/19.0.0/dbs/

[oracle@test1 dbs]$ cd $ORACLE_HOME/appsutil

[oracle@test1 appsutil]$ . ./txkSetCfgCDB.env dboraclehome=$ORACLE_HOME

Oracle Home being passed: /u01/oracle/PROD/19.0.0

[oracle@test1 appsutil]$ export ORACLE_SID=prodcdb

[oracle@test1 appsutil]$ sqlplus “/ as sysdba”

SQL*Plus: Release 19.0.0.0.0 – Production on Tue Jul 18 12:07:23 2023

Version 19.19.0.0.0

Copyright (c) 1982, 2022, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup nomount;

ORACLE instance started.

Total System Global Area 2147482336 bytes

Fixed Size                 9136864 bytes

Variable Size            570425344 bytes

Database Buffers       1560281088 bytes

Redo Buffers               7639040 bytes

SQL> @$ORACLE_HOME/dbs/PROD_initparam.sql

SQL> alter system set LOCAL_LISTENER=”test1.example.com:1522″ scope=both;

System altered.

SQL> shutdown

ORA-01507: database not mounted

ORACLE instance shut down.

SQL> startup

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

ORACLE instance started.

Total System Global Area 4294963736 bytes

Fixed Size                         9171480 bytes

Variable Size                2583691264 bytes

Database Buffers          1677721600 bytes

Redo Buffers                   24379392 bytes

Database mounted.

Database opened.

SQL> select name,open_mode from v$database;

NAME    OPEN_MODE

——— ——————–

PRODCDB   READ WRITE

 

c) Check for PDB violations

Use the following commands to run the txkChkPDBCompatability.pl script. This checks the PDB for any violations.

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

[oracle@test1 appsutil]$ cd $ORACLE_HOME/appsutil

[oracle@test1 appsutil]$ . ./txkSetCfgCDB.env dboraclehome=$ORACLE_HOME

Oracle Home being passed: /u01/oracle/PROD/19.0.0

[oracle@test1 appsutil]$ export ORACLE_SID=prodcdb

[oracle@test1 appsutil]$ cd $ORACLE_HOME/appsutil/bin

[oracle@test1 bin]$ perl txkChkPDBCompatability.pl -dboraclehome=$ORACLE_HOME -outdir=$ORACLE_HOME/appsutil/log -cdbsid=prodcdb -pdbsid=PROD -servicetype=onpremise

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

*                                                                                      *

*       IMPORTANT NOTE: RESOLVE ALL VIOLATIONS BEFORE PROCEEDING TO CREATE PDB         *

*                                                                                      *

*         – All the errors except SQL PATCH ERRORS should be resolved                  *

*                                                                                      *

*         – All the warnings except CHARACTER SET WARNINGS can be ignored              *

*                                                                                      *

*         – Review and set the INIT PARAMETERs to match the EBS requirements           *

*                                                                                      *

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

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.

 

d) Create the PDB

Load the environment variables by running the following commands.

Make sure to extend tablespaces on CDB to have sufficient space.

$ cd $ORACLE_HOME/appsutil

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

$ cd $ORACLE_HOME/appsutil/bin

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

[oracle@test1 bin]$ cd $ORACLE_HOME/appsutil

[oracle@test1 appsutil]$ . ./txkSetCfgCDB.env dboraclehome=$ORACLE_HOME

Oracle Home being passed: /u01/oracle/PROD/19.0.0

[oracle@test1 appsutil]$ cd $ORACLE_HOME/appsutil/bin

[oracle@test1 bin]$ perl txkCreatePDB.pl -dboraclehome=$ORACLE_HOME -outdir=$ORACLE_HOME/appsutil/log -cdbsid=prodcdb -pdbsid=PROD -dbuniquename=prodcdb -servicetype=onpremise

============================

Inside promptDataTopDir()…

============================

Number of DATA_TOPs: 1

DATA_TOP_1

===========

Enter the non-CDB data top [/u01/oracle/PROD/data]:

Enter the corresponding PDB data top [/u01/oracle/PROD/data]:

The PDB datafile location can be the same as the source datafile location.

 

e) Run the post-PDB script

Source 19c Environment

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$ export ORACLE_SID=PROD

change CDB system password

[oracle@test1 ~]$ sqlplus / as sysdba

SQL> alter user system identified by oracle#123;

User altered.

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

$ 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=<CDB TNS port number> -servicetype=onpremise

[oracle@test1 bin]$ cd $ORACLE_HOME/appsutil

[oracle@test1 appsutil]$ . ./txkSetCfgCDB.env dboraclehome=$ORACLE_HOME

Oracle Home being passed: /u01/oracle/PROD/19.0.0

[oracle@test1 appsutil]$ cd $ORACLE_HOME/appsutil/bin

[oracle@test1 appsutil perl $ORACLE_HOME/appsutil/bin/txkPostPDBCreationTasks.pl -dboraclehome=$ORACLE_HOME -outdir=$ORACLE_HOME/appsutil/log -cdbsid=prodcdb -pdbsid=PROD -appsuser=apps -dbport=1522 -servicetype=onpremise

Enter the APPS Password:

Enter the CDB SYSTEM Password:

#####################################################################

#                    I M P O R T A N T    N O T E                   #

#                                                                   #

#   EBS_SYSTEM credentials are set to same value as that of SYSTEM  #

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

This step also runs the autoconfig at DB level.

SQL> show pdbs

 

    CON_ID CON_NAME                           OPEN MODE  RESTRICTED

———- —————————— ———- ———-

           2 PDB$SEED                         READ ONLY  NO

           3 PROD                             READ WRITE NO

 

f) Change 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 initialization parameters.

           

[oracle@test1 appsutil]$ export ORACLE_SID=prodcdb

[oracle@test1 appsutil]$ sqlplus / as sysdba

SQL> alter system set event=’10946 trace name context forever, level 8454144′ scope=spfile;

System altered.

SQL> alter system set sec_case_sensitive_logon=FALSE scope=spfile;

System altered.

 

Step 12. Run Autoconfig on the Application tier

Add the CDB entry in tnsnames.ora of Application

<TWO_TASK> =

 (DESCRIPTION =

  (ADDRESS = (PROTOCOL=tcp)(HOST=<hostname>.<domain>)(PORT=<port number>))

  (CONNECT_DATA = (SERVICE_NAME=ebs_<PDB SID>)(INSTANCE_NAME=<CDB SID>))

 )

As the user of the applications server node, on both the Patch and Run APPL_TOP, modify the $TNS_ADMIN/tnsnames.ora file to specify the CDB instance name. The following shows the format of the new TNS entry.

[oracle@test1 ~]$ . ./EBSapps.env run

 E-Business Suite Environment Information

  —————————————-

  RUN File System           : /u01/oracle/PROD/fs1/EBSapps/appl

  PATCH File System         : /u01/oracle/PROD/fs2/EBSapps/appl

  Non-Editioned File System : /u01/oracle/PROD/fs_ne

  DB Host: test1.example.com  Service/SID: PROD

  Sourcing the RUN File System …

[oracle@test1 ~]$ cd $TNS_ADMIN

[oracle@test1 admin]$ pwd

/u01/oracle/PROD/fs1/inst/apps/PROD_test1/ora/10.1.2/network/admin

[oracle@test1 admin]$ vi tnsnames.ora

prodcdb =

 (DESCRIPTION =

  (ADDRESS = (PROTOCOL=tcp)(HOST= test1.example.com)(PORT=1522))

  (CONNECT_DATA = (SERVICE_NAME=ebs_PROD)(INSTANCE_NAME=prodcdb))

 )

 

• Edit the same in Patch File System

[oracle@test1 ~]$ . ./EBSapps.env patch

 E-Business Suite Environment Information

  —————————————-

  RUN File System           : /u01/oracle/PROD/fs1/EBSapps/appl

  PATCH File System         : /u01/oracle/PROD/fs2/EBSapps/appl

  Non-Editioned File System : /u01/oracle/PROD/fs_ne

  DB Host: test1.example.com  Service/SID: PROD

  Sourcing the PATCH File System …

[oracle@test1 ~]$ cd $TNS_ADMIN

[oracle@test1 admin]$ vi tnsnames.ora

 

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

s_applptmp    Directory (not /usr/tmp) defined in UTL_FILE_DIR

[oracle@test1 admin]$ grep s_dbport $CONTEXT_FILE

      <dbport oa_var=”s_dbport” oa_type=”EXT_PORT” base=”1521″ step=”1″ range=”-1″ label=”Database Port”>1521</dbport>

[oracle@test1 admin]$ grep s_apps_jdbc_connect_descriptor $CONTEXT_FILE

         <jdbc_url oa_var=”s_apps_jdbc_connect_descriptor”>jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=test1.example.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=PROD)))</jdbc_url>

[oracle@test1 admin]$ grep s_applptmp $CONTEXT_FILE

         <APPLPTMP oa_var=”s_applptmp” osd=”UNIX”>/usr/tmp</APPLPTMP>

To identify the allowable directories for s_applptmp use, connect to the Oracle E-Business Suite database instance as the app’s user (on PDB)and run the following query:

[oracle@test1 appsutil]$ sqlplus apps/apps@PROD

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

VALUE

——————————————————————————–

/u01/oracle/PROD/temp/PROD,/u01/oracle/PROD/temp/PROD,/u01/oracle/PROD/19.0.0/ap

psutil/outbound/PROD_test1,/u01/oracle/PROD/temp/PROD

/u01/oracle/PROD/temp/PROD

/u01/oracle/PROD/temp/PROD

/u01/oracle/PROD/19.0.0/appsutil/outbound/PROD_test1

[oracle@test1 admin]$ vi $CONTEXT_FILE

Enter the values of s_applptmp and save

[oracle@test1 admin]$ grep s_applptmp $CONTEXT_FILE

         <APPLPTMP oa_var=”s_applptmp” osd=”UNIX”>/u01/oracle/PROD/19.0.0/appsutil/outbound/PROD_test1</APPLPTMP>

Edit the same in Patch file System

[oracle@test1 admin]$ vi $CONTEXT_FILE

Enter the values of s_applptmp and save

[oracle@test1 admin]$ grep s_applptmp $CONTEXT_FILE

         <APPLPTMP oa_var=”s_applptmp” osd=”UNIX”>/u01/oracle/PROD/19.0.0/appsutil/outbound/PROD_test1</APPLPTMP>

 

Now, Run AutoConfig on both ‘PATCH’ and ‘RUN’ APPL_TOPs using the following command.

• Running On Run File System

[oracle@test1 admin]$ $INST_TOP/admin/scripts/adautocfg.sh

• Running On Patch File System

[oracle@test1 admin]$ $INST_TOP/admin/scripts/adautocfg.sh

Note: When running AutoConfig on the patch file system APPL_TOP, ignore all errors.

 

Step 13. Start Application Services and Validate the Database Version

[oracle@test1 ~]$. ./EBSapps.env run

 E-Business Suite Environment Information

  —————————————-

  RUN File System           : /u01/oracle/PROD/fs1/EBSapps/appl

  PATCH File System         : /u01/oracle/PROD/fs2/EBSapps/appl

  Non-Editioned File System : /u01/oracle/PROD/fs_ne

  DB Host: test1.example.com  Service/SID: PROD

  Sourcing the RUN File System …

[oracle@test1 ~]$ cd $ADMIN_SCRIPTS_HOME

[oracle@test1 scripts]$ ./adstrtal.sh apps/apps

 

Thank you all for accompanying us on this journey of upgrading the EBS Apps Database from version12.1.0.2 to 19.19. I sincerely appreciate your time and interest. Please stay tuned for more informative content and updates. We look forward to welcoming you back soon. 

If you have not yet explored the blog on Oracle Apps R12.2.12 Installation Steps, we kindly encourage you to follow the provided link.

Oracle Apps R12.2.12 on Oracle Linux OEL 7.9 using Oracle VirtualBox

 

 

Oracle EBS Database Upgrade from 12c to 19c Part-1

 

In this article, I will be discussing the process of upgrading Oracle Database 12.1.0.2 to the latest version, 19.19 (Latest PSU APR-23), while using Oracle EBS Apps R12.2.12. This post follows the previous article on upgrading Oracle EBS Apps from version 12.2.0 to 12.2.12.

If you are new here and interested in installing and upgrading Oracle E-Business Suite R12.2.x, you can refer to the following link for a step-by-step installation guide for Oracle APPS R12.2.12 

Throughout this Upgrade Process, I will be following Oracle Standard DOC ID  “Oracle E-Business Suite Release 12.2 with Oracle Database 19c (Doc ID 2552181.1)”

• As part of upgrading your Oracle E-Business Suite to Oracle Database 19c, your database will undergo a conversion to a multitenant architecture. This means it will consist of a Container Database (CDB) with a single Pluggable Database. Please note that only multitenant architecture databases are supported for Oracle E-Business Suite when using Oracle Database 19c.
• During the upgrade process, you will also need to migrate directories that are defined for PL/SQL File I/O to database directory objects. This requirement arises from the de support of the UTL_FILE_DIR database initialization parameter in Oracle Database 19c.
• Oracle Database Release Update 19.3, as well as Release Updates 19.5 and later, have been certified for compatibility.
• If the products you have implemented do not support 19c, it is advised not to proceed with the database upgrade.

Section 1 – Running Health Check

Section 2 – Applying Interoperability Patches

Step 1. Checking AD and TXK Current Versions

Apply the necessary patches to EBS as per the requirements, considering the version and the AD/TXK delta versions.

The current AD and TXK versions in my environment are already at Delta 14 as shown below

SQL> col ABBREVIATION for a10 set lines 1000 col NAME for a50 col CODELEVEL for a20 SELECT ABBREVIATION,NAME,codelevel FROM apps.AD_TRACKABLE_ENTITIES WHERE abbreviation in (‘txk’,’ad’); ABBREVIATION NAME                                             CODELEVEL ———- ————————————————– ——————– ad Applications DBA                                           C.14 txk Oracle Applications Technology Stack                      C.14

Step 2. Checking Patches that are Already Applied

As per our Application Version, The following software component versions must exist in our environment.

Patch 25452805

• Patch 26052406
• Patch 26521736 – 19c interoperability patch for Release 12.2
• Patch 30433124
• Patch 31349591
• Patch 31800803
• Patch 33346385
• Patch 33119203 – Apply on AD/TXK Delta 13 or later versions.
• Patch 30611319 – Apply only if using Integrated SOA Gateway (ISG).
• Patch 28732161 – Apply on Release 12.2.6 or later versions.
• Patch 31088182 – Apply on Release 12.2.4 or later versions.

For my specific environment, the patches mentioned in the above list have already been applied. If these patches have not been applied in your environment, it is necessary to apply them.

 

sql> SELECT bug_number, creation_date FROM ad_bugs WHERE bug_number IN (25452805, 26052406, 26521736, 30433124, 31349591, 31800803, 33346385, 33119203, 30611319, 28732161, 31088182); BUG_NUMBER CREATION_ —————————— ——— 31800803 13-JUL-23 33119203 13-JUL-23 33346385 13-JUL-23 31349591 14-JUL-23 25452805 14-JUL-23 31088182 14-JUL-23 30433124 14-JUL-23 26052406 14-JUL-23 30611319 14-JUL-23 9 rows selected.

Note: Since we have applied all the patches except (26521736, 28732161) for the ones listed below, we will proceed to download these two patches from Oracle Support Metalink and transfer them to the Linux environment.

Step 3. Applying the Interoperability Patches

[oracle@test1 ~]$ cd /u01/oracle/PROD/19.0.0/media/interoperability [oracle@test1 interoperability]$ ll total 4700 -rwxrwxr-x. 1 oracle oinstall 3298300 Jul 16 00:09 p26521736_12.2.0_R12_LINUX.zip -rwxrwxr-x. 1 oracle oinstall 1500624 Jul 16 00:09 p28732161_R12.FRM.C_R12_GENERIC.zip [oracle@test1 interoperability]$ unzip p26521736_12.2.0_R12_LINUX.zip [oracle@test1 interoperability]$ unzip p28732161_R12.FRM.C_R12_GENERIC.zip [oracle@test1 interoperability]$ cp -pr 26521736/ $PATCH_TOP [oracle@test1 interoperability]$ cp -pr 28732161/ $PATCH_TOP Now Applying the patches through ADOP in one command after sourcing the application run environment [oracle@test1 ~]$ . ./EBSapps.env E-Business Suite Environment Information —————————————- RUN File System : /u01/oracle/PROD/fs1/EBSapps/appl PATCH File System : /u01/oracle/PROD/fs2/EBSapps/appl Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: test1.example.com Service/SID: PROD E-Business Suite Environment Setting ———————————— – Enter [R/r] for sourcing Run File System Environment file, or – Enter [P/p] for sourcing Patch File System Environment file, or – Enter anything else to exit Please choose the environment file you wish to source [R/P]:R Sourcing the RUN File System … [oracle@test1 ~]$ cd /u01/oracle/PROD/19.0.0/media/interoperability [oracle@test1 ~]$ adop phase=prepare,apply,finalize,cutover,cleanup mtrestart=no patches= 26521736,28732161 Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Initializing. Run Edition context : /u01/oracle/PROD/fs1/inst/apps/PROD_test1/appl/admin/PROD_test1.xml Patch edition context: /u01/oracle/PROD/fs2/inst/apps/PROD_test1/appl/admin/PROD_test1.xml Patch file system free space: 95.41 GB Validating system setup. ADOP (C.Delta.14) Session ID: 6 Node: test1 Phase: prepare,apply,finalize,cutover,cleanup Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/6/20230716_124157/adop.log

 

 

---

Section 3– Creating the Initialization Parameter Files

 

Step 1. Make sure the below parameter is false in DB.

SQL> show parameter SEC_CASE_SENSITIVE_LOGON

NAME TYPE VALUE
———————————— ———– ——————————
sec_case_sensitive_logon boolean FALSE

Step 2. Creating the initialization parameter files

Run the following commands to create the $ORACLE_HOME/dbs/<ORACLE_SID>_initparam.sql and $ORACLE_HOME/dbs/<ORACLE_SID>_datatop.txt files. $ 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 perl txkOnPremPrePDBCreationTasks.pl -dboraclehome=$ORACLE_HOME -outdir=$ORACLE_HOME/appsutil/log -appsuser=apps -dbsid=PROD -skipdbshutdown=yes [oracle@test1 ~]$ cd $ORACLE_HOME/appsutil [oracle@test1 appsutil]$ echo $ORACLE_HOME /u01/oracle/PROD/12.1.0 [oracle@test1 appsutil]$ . ./txkSetCfgCDB.env dboraclehome=/u01/oracle/PROD/12.1.0 Oracle Home being passed: /u01/oracle/PROD/12.1.0 [oracle@test1 appsutil]$ echo $ORACLE_SID PROD [oracle@test1 appsutil]$ cd bin [oracle@test1 bin]$ perl txkOnPremPrePDBCreationTasks.pl -dboraclehome=$ORACLE_HOME -outdir=$ORACLE_HOME/appsutil/log -appsuser=apps -dbsid=PROD -skipdbshutdown=yes Enter the APPS Password: Once completed you can check the below highlighted are created in cd $ORACLE_HOME/dbs [oracle@test1 bin]$ cd $ORACLE_HOME/dbs [oracle@test1 dbs]$ ls -ltrh total 38M -rw-r–r–. 1 oracle oinstall 0 Jul 11 22:17 PROD_ifile.ora -rw-r—–. 1 oracle oinstall 24 Jul 11 22:18 lkPROD -rw-r—–. 1 oracle oinstall 4.0M Jul 11 22:26 arch1_32_899606885.dbf -rwxr-xr-x. 1 oracle oinstall 433 Jul 11 22:28 RMANinit.ora -rw-r–r–. 1 oracle oinstall 22K Jul 11 22:31 initPROD.ora -rw-r–r–. 1 oracle oinstall 0 Jul 14 17:03 PROD_test1_ifile.ora -rw-r–r–. 1 oracle oinstall 22K Jul 14 17:03 initPROD_noaq.ora -rw-r—–. 1 oracle oinstall 34M Jul 15 17:24 snapcf_PROD.f -rw-rw—-. 1 oracle oinstall 1.6K Jul 16 12:27 hc_PROD.dat -rw-r—–. 1 oracle oinstall 6.5K Jul 16 14:24 spfilePROD.ora -rw-r–r–. 1 oracle oinstall 3.4K Jul 16 14:46 PROD_initparam.sql -rw-r–r–. 1 oracle oinstall 419 Jul 16 14:46 PROD_datatop.txt -rw-r–r–. 1 oracle oinstall 40K Jul 16 14:46 PROD_PDBDesc.xml

 

 

 

---

Section 4– Install 19c Database Oracle Home

I have downloaded the Software of 19.3 From Download Link 19c and moved it to /u01/oracle/PROD/19.0.0 directory.

[oracle@test1 ~]$ cd /u01/oracle/PROD/19.0.0
[oracle@test1 19.0.0]$ unzip -oq LINUX.X64_193000_db_home.zip

Now after unzipping the 19c software files we will launch the installer to install the 19c software

[oracle@test1 19.0.0]$ ./runInstaller

Select “Set Up Software Only” Click Next
Select “Single instance database installation” Click Next
Select “Enterprise Edition” Click Next
Click Next
Select “oinstall” for all Group Click Next
Select “Automatically run configuration scripts” Enter OS root User Credential Click Next
Click Install
Installation Process Starts
Click Yes
Click Close

 

 

---

 

Section 5 – Applying Latest Database Patchset 19.19

Step 1. Creating 19c ENV File

After successfully installing the 19c Oracle Home, you can create a straightforward environment by configuring the following parameters. In this case, “prod” represents the CDB that will be created. The ORACLE_BASE environment variable is appropriately set. The ORACLE_HOME environment variable is directed to the newly installed 19c Oracle home. The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new Perl executable is located (typically $ORACLE_HOME/perl/bin). The LD_LIBRARY_PATH environment variable contains $ORACLE_HOME/lib. The PERL5LIB environment variable points to the directories where the new Perl libraries are stored: $ORACLE_HOME/perl/lib/<perl version> and $ORACLE_HOME/perl/lib/site_perl/<perl version>. Additionally, the ORA_NLS10 environment variable is set to /u01/oracle/PROD/19.0.0/nls/data/9idata. Ensure to export these environment variables for easy configuration and access in the environment.

Open New Terminal and Create 19c.env file with the following parameters given below and save the file as shown in the Picture below

[oracle@test1 ~]$ vi 19c.env

export ORACLE_HOME=/u01/oracle/PROD/19.0.0

export ORACLE_SID=PROD

export PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$ORACLE_HOME/perl/bin

export ORACLE_BASE=/u01/oracle/PROD

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib

export PERL5LIB=$ORACLE_HOME/perl/lib/5.28.1:$ORACLE_HOME/perl/lib/site_perl/5.28.1

 

Step 2. Applying the Latest DB PSU 19.19

Here we are going to apply the Latest Database 19c Patch Set (Release Update 19.19.0.0.230418) Certified with Oracle E-Business Suite As per Oracle (Doc ID 1594274.1) (Oracle E-Business Suite Release 12.2: Consolidated List of Oracle Database Patches and Bug Fixes)

I have downloaded the patches mentioned in Pictures below and moved them to the Linux Machine on /u01/oracle/PROD/19.0.0/media directory

 

 

[oracle@test1 ~]$ cd /u01/oracle/PROD/19.0.0/media

[oracle@test1 media]$ ls -ltrh p3504*

-rwxrwxr-x. 1 oracle oinstall 4.7M Jul 16 15:40 p35047599_1919000DBRU_Linux-x86-64.zip

-rwxrwxr-x. 1 oracle oinstall 1.7G Jul 16 15:41 p35042068_190000_Linux-x86-64.zip

Unzip the Patches

[oracle@test1 media]$ unzip p35047599_1919000DBRU_Linux-x86-64.zip

[oracle@test1 media]$ unzip p35042068_190000_Linux-x86-64.zip

 

Also, download the latest Opatch from the link given in README.html of p35042068_190000_Linux-x86-64.zip patch files when unzipped

[oracle@test1 media]$ ls -ltrh p6880880_122010_Linux-x86-64.zip

-rwxrwxr-x. 1 oracle oinstall 120M Jul 16 15:53 p6880880_122010_Linux-x86-64.zip

[oracle@test1 media]$ unzip p6880880_122010_Linux-x86-64.zip

 

Create a Backup of the OLD Opatch Directory

[oracle@test1 ~]$ cd /u01/oracle/PROD/19.0.0

[oracle@test1 19.0.0]$ mv OPatch/ OPatch_BKP/

 

Now copy the new Opatch Directory

[oracle@test1 19.0.0]$ mv /u01/oracle/PROD/19.0.0/media/OPatch .

 

Now Start Applying the Database Patches Download and Unzipped

Patch 1:  Patch 35042068:  Database Release Update Patch 19.19.0.0.230418 (Apr 2023).

[oracle@test1 ~]$ . ./19c.env [oracle@test1 ~]$ cd /u01/oracle/PROD/19.0.0/media/35042068 [oracle@test1 35042068]$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./ Oracle Interim Patch Installer version 12.2.0.1.37 Copyright (c) 2023, Oracle Corporation.  All rights reserved. PREREQ session Oracle Home       : /u01/oracle/PROD/19.0.0 Central Inventory : /u01/oracle/oraInventory    from           : /u01/oracle/PROD/19.0.0/oraInst.loc OPatch version    : 12.2.0.1.37 OUI version       : 12.2.0.7.0 Log file location : /u01/oracle/PROD/19.0.0/cfgtoollogs/opatch/opatch2023-07-16_16-20-19PM_1.log Invoking prereq “checkconflictagainstohwithdetail” Prereq “checkConflictAgainstOHWithDetail” passed. OPatch succeeded.   [oracle@test1 35042068]$ opatch apply Oracle Interim Patch Installer version 12.2.0.1.37 Copyright (c) 2023, Oracle Corporation.  All rights reserved. Oracle Home       : /u01/oracle/PROD/19.0.0 Central Inventory : /u01/oracle/oraInventory    from           : /u01/oracle/PROD/19.0.0/oraInst.loc OPatch version    : 12.2.0.1.37 OUI version       : 12.2.0.7.0 Log file location : /u01/oracle/PROD/19.0.0/cfgtoollogs/opatch/opatch2023-07-16_16-21-39PM_1.log Verifying environment and performing prerequisite checks…

 

Patch 2:  Patch 35050341: OJVM RELEASE UPDATE 19.19.0.0.0

[oracle@test1 media]$ cd 35050341 [oracle@test1 35050341]$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./ Oracle Interim Patch Installer version 12.2.0.1.37 Copyright (c) 2023, Oracle Corporation.  All rights reserved. PREREQ session Oracle Home       : /u01/oracle/PROD/19.0.0 Central Inventory : /u01/oracle/oraInventory    from           : /u01/oracle/PROD/19.0.0/oraInst.loc OPatch version    : 12.2.0.1.37 OUI version       : 12.2.0.7.0 Log file location : /u01/oracle/PROD/19.0.0/cfgtoollogs/opatch/opatch2023-07-16_17-09-58PM_1.log Invoking prereq “checkconflictagainstohwithdetail” Prereq “checkConflictAgainstOHWithDetail” passed. OPatch succeeded.   [oracle@test1 35050341]$ opatch apply Oracle Interim Patch Installer version 12.2.0.1.37 Copyright (c) 2023, Oracle Corporation.  All rights reserved. Oracle Home       : /u01/oracle/PROD/19.0.0 Central Inventory : /u01/oracle/oraInventory    from           : /u01/oracle/PROD/19.0.0/oraInst.loc OPatch version    : 12.2.0.1.37 OUI version       : 12.2.0.7.0 Log file location : /u01/oracle/PROD/19.0.0/cfgtoollogs/opatch/opatch2023-07-16_17-10-45PM_1.log Verifying environment and performing prerequisite checks…

 

 

Patch 1:  Patch 35406065: RESTORE DATABASE PREVIEW FAILING WITH RMAN-00600

[oracle@test1 ~]$ cd /u01/oracle/PROD/19.0.0/media/ [oracle@test1 media]$ cd 35406065 [oracle@test1 35406065]$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./ Oracle Interim Patch Installer version 12.2.0.1.37 Copyright (c) 2023, Oracle Corporation.  All rights reserved. PREREQ session Oracle Home       : /u01/oracle/PROD/19.0.0 Central Inventory : /u01/oracle/oraInventory    from           : /u01/oracle/PROD/19.0.0/oraInst.loc OPatch version    : 12.2.0.1.37 OUI version       : 12.2.0.7.0 Log file location : /u01/oracle/PROD/19.0.0/cfgtoollogs/opatch/opatch2023-07-16_18-44-53PM_1.log Invoking prereq “checkconflictagainstohwithdetail” Prereq “checkConflictAgainstOHWithDetail” passed. OPatch succeeded.   [oracle@test1 35406065]$ opatch apply Oracle Interim Patch Installer version 12.2.0.1.37 Copyright (c) 2023, Oracle Corporation.  All rights reserved. Oracle Home       : /u01/oracle/PROD/19.0.0 Central Inventory : /u01/oracle/oraInventory    from           : /u01/oracle/PROD/19.0.0/oraInst.loc OPatch version    : 12.2.0.1.37 OUI version       : 12.2.0.7.0 Log file location : /u01/oracle/PROD/19.0.0/cfgtoollogs/opatch/opatch2023-07-16_18-45-17PM_1.log Verifying environment and performing prerequisite checks… OPatch continues with these patches:   35406065

 

 

Step 3.  Create the 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.

[oracle@test1 ~]$ . ./19c.env

[oracle@test1 ~]$ unset PERL5LIB

[oracle@test1 ~]$  perl $ORACLE_HOME/nls/data/old/cr9idata.pl

Creating directory /u01/oracle/PROD/19.0.0/nls/data/9idata …

Copying files to /u01/oracle/PROD/19.0.0/nls/data/9idata…

Copy finished.

Please reset environment variable ORA_NLS10 to /u01/oracle/PROD/19.0.0/nls/data/9idata!

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. Add export ORA_NLS10=/u01/oracle/PROD/19.0.0/nls/data/9idata in 19c environment file 

[oracle@test1 ~]$ vi 19c.env

[oracle@test1 ~]$ cat 19c.env  

export ORACLE_HOME=/u01/oracle/PROD/19.0.0export ORACLE_SID=PROD

export PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$ORACLE_HOME/perl/bin

export ORACLE_BASE=/u01/oracle/PROD

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib

export PERL5LIB=$ORACLE_HOME/perl/lib/5.28.1:$ORACLE_HOME/perl/lib/site_perl/5.28.1

export ORA_NLS10=/u01/oracle/PROD/19.0.0/nls/data/9idata

 

Step 4.  Create appsutil.zip and copy it to the database tier

 

On Application Tier source run file system environment 

[oracle@test1 ~]$ . ./EBSapps.env run

  E-Business Suite Environment Information

  —————————————-

  RUN File System           : /u01/oracle/PROD/fs2/EBSapps/appl

  PATCH File System         : /u01/oracle/PROD/fs1/EBSapps/appl

  Non-Editioned File System : /u01/oracle/PROD/fs_ne

  DB Host: test1.example.com  Service/SID: PROD

  Sourcing the RUN File System …

 

Run the below-given command to create appsutil.zip

[oracle@test1 ~]$ perl $AD_TOP/bin/admkappsutil.pl

Starting the generation of appsutil.zip

Log file located at /u01/oracle/PROD/fs2/inst/apps/PROD_test1/admin/log/MakeAppsUtil_07161853.log

output located at /u01/oracle/PROD/fs2/inst/apps/PROD_test1/admin/out/appsutil.zip

MakeAppsUtil completed successfully.

 

Copy appsutil.zip file to 19c Oracle Home and unzip

[oracle@test1 ~]$ cp /u01/oracle/PROD/fs2/inst/apps/PROD_test1/admin/out/appsutil.zip /u01/oracle/PROD/19.0.0/

[oracle@test1 ~]$ cd $ORACLE_HOME

[oracle@test1 19.0.0]$ unzip -o appsutil.zip

 

Step 5. Install JRE 8

 

To install JRE 8 on the appsutil directory, copy the $ORACLE_HOME/jdk/jre directory to $ORACLE_HOME/appsutil/jre. Run the following commands:

[oracle@test1 19.0.0]$ cd $ORACLE_HOME/appsutil

[oracle@test1 appsutil]$ cp -r $ORACLE_HOME/jdk/jre .

[oracle@test1 appsutil]$ cp $ORACLE_HOME/jlib/orai18n.jar $ORACLE_HOME/appsutil/jre/lib/ext

---

 

 

 

 

 

 

Installation of Oracle APPS 12.2.0 on OEL 7.9

Once all  the prereqs steps are completed as discussed in an earlier post we are ready to do the installation of Apps12.2.0

In Case You are here for the first time, Kindly go through the Following Link given below before Proceeding with the Installation Of Oracle Apps 12.2.0

• Oracle Linux 7.9 Installation On Virtual Box
• OEL Configuration for Oracle Apps R12.2

 

[oracle@test1 rapidwiz]$ cd /home/apps/stage/startCD/Disk1/rapidwiz [oracle@test1 rapidwiz]$ export DISPLAY=192.168.1.147:0.0

Note: Before Running rapidwiz, Make sure display is set properly by running below command.

Note: The IP provided above is of your local machine from where the Rapidwiz is being executed not Virtual Machine

 

[oracle@test1 rapidwiz]$ cd /home/apps/stage/startCD/Disk1/rapidwiz [oracle@test1 rapidwiz]$ export DISPLAY=192.168.1.147:0.0 Note: the ip is of your local machine not Virtual Machine [oracle@test1 rapidwiz]$ ./rapidwiz Click Next
Click Next
Click Next
Click Next
Click Next
Enter the Following Details Highlighted as per the environment and then Click Next
Click Next
Click Next
Click Next
Click Next
Enter the Following Details Highlighted as per the environment and then Click Next
Enter the Following Details Highlighted as per the environment and then Click Next
Click Next
It will Perform all the Pre-RequisiteTests for the Smooth Installation of Oracle APPS
Make Sure all The Pre-Requisite Test Pass Successfully with Green Tick as Shown in the Picture. Now Click Next
Click Next
Click Yes to Start the Installation Process
The installer will initiate and will be closely monitored for any potential issues throughout the installation process. It is important to note that the installation is expected to take approximately 10 hours to complete. Upon completion of the installation, a post-verification procedure will be performed to ensure the successful execution of all post-installation tasks. This verification step is essential in confirming that all necessary tasks have been completed without any errors or issues.
Click Next
Click Finish