The course will help you to upgrade Oracle Database from 12c to 19c, here are the course contents

Upgrading Oracle EBS Database to 19c. 3

About the Upgrade. 3

Environment: 3

Here are support notes that we are going to follow.. 5

Let’s download 19.3 from below links. 5

Highlevel Steps. 6

Before the Database Installation. 6

After the Database Upgrade. 6

Convert Database to Multitenant Architecture. 6

Before the Database Installation. 7

Run hcheck.sql 7

Apply required patches on R12.1.3. 8

Create the initialization parameter setup files: 10

Install Oracle Database 19c. 11

Install vncserver. 11

Disable firewall in Linux 7. 11

Upgrade Oracle Home from 19.3 to 19.12. 23

Create the nls/data/9idata directory. 26

Install JRE 8. 26

Create the container database - DEVCDB. 27

Create the CDB MGDSYS schema. 51

Create the CDB TNS Files: 51

Shutdown the CDB now.. 52

Database upgrade. 53

Store the UTL_FILE_DIR parameter values. 53

Drop SYS.ENABLED$INDEXES. 55

Remove the MGDSYS schema (not applicable for our version) 55

Shut down the database listener. 56

Database Pre-Upgrade Steps: 56

Run the Pre-upgrade Tool: 57

Make changes to initDEV.ora file as follows. 69

Upgrade the database instance. 71

Issues and Solutions. 81

Perform patch post-install instructions. 84

Run adgrants.sql 84

Grant create procedure privilege on CTXSYS. 86

Compile invalid objects. 86

Grant datastore access. 86

Convert Database to Multitenant Architecture: 88

Run the post PDB script 98

Modify initialization parameters: 103

How to Connect as SYSDBA without password into a PDB directly. 112

Verify ETCC patches are applied. 114

From On-Premises to Oracle Cloud Infrastructure

Lift and Shift is a common term in cloud industry nomenclature. While exact definitions vary, we use this term to mean copying (or cloning) an on-premises Oracle E-Business Suite environment into OCI.

The cloud copy can be used for testing or development, and - when you are ready - as part of a permanent migration of your production environment to the cloud.

At present, you can follow the tutorials and use the tools we provide to lift and shift either:

· A copy of your entire on-premises EBS environment to the Oracle Compute Cloud Service (IaaS)

· A copy of your application tier to IaaS and your database tier to the Database Cloud Service (DBCS)

We'll look at what each of these scenarios offers. This article will cover the first scenario, and a subsequent article will cover the second.

When you lift and shift your on-premises EBS environment to the Oracle Compute Cloud Service, you start by creating either one or two Oracle
Compute Cloud Service instances (virtual machines) using the EBS OS-Only Image from the Oracle Cloud Marketplace. These instances will be used to host your environment in the cloud. Whether you create one or two instances will depend on whether you want to co-locate the application tier and database tier in the same cloud instance or keep them separate.

You then create temporary stage areas in the cloud and on-premises to hold backups of your on-premises database and your on-premises application tier respectively. These can be removed after the lift and shift process is complete.

In this second lift and shift scenario, you copy one or more application tiers to the Oracle Compute Cloud Service, and install your database into the Database Cloud Service. The database can be either single-node or Oracle RAC.

You start by creating a provisioning instance in the Oracle Compute Cloud using the EBS Provisioning Image from the Oracle Cloud Marketplace. This provisioning instance will act as a launchpad for the cloud provisioning process.

You then create a stage area in the Oracle Compute Cloud and attach it to the provisioning instance.

Next, you create two on-premises stage areas, the first to hold a copy of your application tier files and the second to hold a database backup.

You are now ready to start the lift and shift operation, which (in
contrast to the method used in EBS Lift and Shift Part 1: From On-Premises to Oracle Compute Cloud) uses two utilities, a cloning utility and a provisioning utility.

First, you invoke the cloning utility, which will:

1. Copy your application tier files to the corresponding local stage area

2. Create an RMAN backup of your database tier in the corresponding local stage area

3. Copy the contents of the on-premises stage areas to the cloud stage area

Second, you run the provisioning utility, which will:

1. Restore your RMAN database backup into the Database Cloud Service instance (or instances in the case of an Oracle RAC database)

2. Create your desired application tier topology, with one or more
application tiers and (if more than one) either a shared or non-shared
file system

Whichever application tier topology you deploy, be aware that:

· The Oracle Traffic Director load
balancer will always be installed in readiness to balance the load between multiple application tiers

· You can scale out by running the provisioning utility to add nodes at any time

We are continually working to refine and further automate our processes, so stay tuned to this blog for further announcements.