What is the difference between a Full, Differential and Incremental backup?

 A Full Backup is a complete backup of all files on the designated hard drive.

An Incremental Backup is a backup of all changed files since the last Full or Incremental backup. For example:

• Sunday - Full Backup
• Monday - All changed files since Sunday
• Tuesday - All changed files since Monday

A Differential Backup is a backup of all changed files since the last Full Backup. For example:

• Sunday- Full Backup
• Monday - All changed files since Sunday
• Tuesday - All changed files since Sunday, including Monday's changed files

Linux/Unix Basic Commands

 

RC-50004: Fatal: Error occurred in ApplyAppsTechStack:Cannot proceed with ApplyAppsTechStack - the paths/ports in the context file are not valid.,RC-20403: The following port numbers are busy - please make sure the ports are available and try again.

ERROR INFO:

Log file located at /Mount/oracle/nadhans/inst/apps/nadhans.com/admin/log/ApplyAppsTier_11252253.log

RC-50004: Fatal: Error occurred in ApplyAppsTechStack:

Cannot proceed with ApplyAppsTechStack - the paths/ports in the context file are not valid.

ERROR while running Apply...

Thu Nov 25 22:53:33 2021

 ERROR: Failed to execute /Mount/oracle/nadhans/inst/apps/nadhans.com/apps/apps_st/comn/clone/bin/adclone.pl

 Please check logfile.

Cannot proceed with ApplyApplTop - the paths/ports in the context file are not valid.

RC-20403: The following port numbers are busy - please make sure the ports are available and try again.

Raised by oracle.apps.ad.clone.ApplyAppsTechStack

        s_metdataport : 9100

--------------------------------------

FIX:

Check and kill if any process are running with port 9100

 If you don’t find any process ..update s_metdataport value in context file to 9101 and run Adcfgclone.

Later change it to original value and run autoconfig or else you can run adcfgclone again.

adop fails with "invalid username/password; logon denied" for custom schema

 adop fails with "invalid username/password; logon denied" for custom schema XX*

Below error encountered in the txk delta level 10 patching . Please go through this post to fix this issue.

Error:

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

Done running adaaddlb.pls for YMS

sqlplus -s XXCUST/***** @/ut9001/nadhans/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql '/ut900/nadhans/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adaddls.pls ***** XXCUST *****'

ERROR:

ORA-01017: invalid username/password; logon denied

An error occurred while running a SQL*Plus script.

***

Continue as if it were successful :

***

AutoPatch could not find a response to the above prompt

in the defaults file.

The patch has FAILED,

Please check the adpatch logs for more details.

Solution:

1. Validate and change the XXCUST password by using FNDCPASS.

FNDCPASS apps/apps 0 Y system/manager ORACLE  XXCUST   XXCUSTT

Above Solution will fix the issue .

 If still its failing you can perform the below.

2. Validate and  Correct the password in xxdprod.tx. (cd $APPL_TOP/admin).

Script location : $AD_TOP/patch/115/sql

Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> @adaddls.pls
Enter value for 1: *********** (System Password)
Connected.
Enter value for 2: XXCUST (Custom username)
old   1: grant create procedure to &&2
new   1: grant create procedure to XXCUST

Grant succeeded.

old   1: ALTER SESSION SET CURRENT_SCHEMA = &2
new   1: ALTER SESSION SET CURRENT_SCHEMA = XXCUST

Session altered.

old   2:   execute immediate 'drop synonym &2..APPS_DDL';
new   2:   execute immediate 'drop synonym XXAHQ.APPS_DDL';

PL/SQL procedure successfully completed.


Package created.


Commit complete.

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
bash-3.2$ sqlplus system

SQL*Plus: Release 10.1.0.5.0 - Production on Wed Sep 26 15:32:07 2018

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

Enter password:

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> @adaddlb.pls
Enter value for 1: ********* (System password)
Connected.
Enter value for 2: XXCUST
old   8:        where grantee='&2'
new   8:        where grantee='XXCUST'
Enter value for 2: XXCUST
old  14:     execute immediate 'grant execute on sys.dbms_sql to &&2';
new  14:     execute immediate 'grant execute on sys.dbms_sql to XXCUST';

PL/SQL procedure successfully completed.

old   1: ALTER SESSION SET CURRENT_SCHEMA = &2
new   1: ALTER SESSION SET CURRENT_SCHEMA = XXCUST

Session altered.


Package body created.


Commit complete.

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

Manually connect to the schema and confirm whether its working.

Retry the adop once again. you can use the below :

adop phase=apply patches=patch_number abandon=no restart=yes

If its failing you can perform the below.

As you can see the error above it was failing at the step below. So i ran the step below manually.


sqlplus -s XXCUST/XXCUST @/a01/appsclone/CLONE/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql '/a01/appsclone/CLONE/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adaddls.pls opensys_33 XXCUST XXCUST'


I was able to run adop without any issue with autoskip flag option.

adop phase=apply patches=25828573 abandon=no restart=yes flags=autoskip 

we can use the below to skip the failed adop session or if you manually performed the failed step. 

abandon=no restart=yes flags=autoskip 

This command will restart the patch once again from starting onwards and will skip all the failures if any comes. But make sure to review the log file at the end of the patch application that you have skipped the failures that you want to.

OPSS: PKI-02002: Unable to open the wallet. Check password. Caused By: java.io.IOException

ERROR INFO:

When attempting to start ADMIN server the following error occurs.

.Default (self-tuning)'> <<WLS Kernel>> <> <> <1635571086361> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password. >
####<Oct 30, 2021 12:18:06 AM CDT> <Critical> <WebLogicServer> <nadhans.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1635571086362> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:888)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
                                                                                                                                           60,1-8        12%
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:888)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
                                                                                           at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: oracle.security.jps.service.credstore.CredStoreException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
        at oracle.security.jps.internal.credstore.ssp.CsfWalletManager.openWallet(CsfWalletManager.java:189)
        at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.doInit(SspCredentialStore.java:378)
        at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:193)
        at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:177)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: java.lang.SecurityException: The jurisdiction policy files are not signed by the expected signer! (Policy files are specific per major JDK release.Ensure the correct version is installed.)
        at javax.crypto.JarVerifier.verifyPolicySigned(JarVerifier.java:336)
        at javax.crypto.JceSecurity.loadPolicies(JceSecurity.java:378)
        at javax.crypto.JceSecurity.setupJurisdictionPolicies(JceSecurity.java:323)
        at javax.crypto.JceSecurity.access$000(JceSecurity.java:50)
        at javax.crypto.JceSecurity$1.run(JceSecurity.java:82)


Solution:

Issue with the JDK.
JDK in $FMW_HOME/webtier and $ORACLE_HOME locations should be compatible
with the JDK exists in $COMMON_TOP/util/.

Verify and copy JDK directory from $COMMON_TOP/util/ to $FMW_HOME/webtier and $ORACLE_HOME locations.

If JDK is compatible in all the locations .
Then 

1.Removed the cwallet.sso in the /<MW_HOME>/user_projects/domains/<DOMAIN_NAME>/config/fmwconfig/ directory.

2.left the one in /<MW_HOME>/user_projects/domains/<DOMAIN_NAME>/config/fmwconfig/bootstrap and then the server started
​
Once server started copy the same files to the other host Where managed servers are running  and start the Managedserver on other hosts.

Now start Admin server .

WFLOAD – Oracle Workflow Loader utility

We use the Workflow Definitions Loader to save or load process definitions from a database or flat file. We can also define as it is a utility that moves workflow data between a file and a database and it is also used to upgrade, upload and download the workflow data.

How can one download,
                      upload,
                      upgrade,
                      force upload a workflow to the database?
Download :

To download a wft file of a specific item type, please use the following command:

 WFLOAD apps/pwd 0 Y DOWNLOAD file.wft ITEMTYPE1  
e.g.
WFLOAD apps/apps 0 Y DOWNLOAD POAPPRV.wft POAPPRV 
Note:
Please make sure to replace file with a more descriptive name, and ITEMTYPE1 with the item type for which you are download the workflow definition.

​Upload:

The upload option is used to load a process definition from a flat file into the database. The upload mode is useful to someone who is developing a workflow process. It allows the developer to save definitions to the database without concern that accidental customizations to existing objects might prevent the upload of some process definition elements. The Workflow Definitions Loader uses the access level defined by the input file to upload the process definitions from the file and therefore will overwrite objects in the database that are protected at a level equal to or higher than that file's access level.

There are two options for the upload process:

1. Upload the workflow definition file wft using the Workflow Definitions Loader               concurrent request:

     A. Login in to the System Administrator responsibility.
     B. Choose requests/run
     C. Choose 'Workflow Definitions Loader'
     D. The report has three parameters: item type, file location, and mode:
     E. Leave item type blank
     F. For the second put in the full path (no Aliases) for the workflow file
       
     NT Server Example:
         d:/oracle/appltop/po/11.5.0/patch/11.5/import/US/poxwfrqa.wft
     Linuz Server Example:
        $oracle/appltop/po/11.5.0/patch/11.5.0/import/US/poxwfrqa.wft
​
     G. For the third parameter, Mode, choose Force.

IMPORTANT: This will overwrite the existing workflow in the database, including any customizations. Proceed only after making sure the customized workflow backup is saved in its own flat file.

2. To upload a wft file to the database, By using WFLOAD command:

WFLOAD apps/pwd 0 Y UPLOAD file.wft
e.g.
WFLOAD apps/apps 0 Y UPLOAD POAPPRV.wft

Note:

Please make sure to replace file.wft with the name of the wft file containing the workflow definition to be uploaded to the database.

​Upgrade:

The upgrade option is used to apply a seed data upgrade to a database from an input file. The Workflow Definitions Loader assumes the access level of the file's creator (seed data provider) and overwrites any objects protected at a level equal to or above the upgrade file's access level. The Loader program preserves any customizations made to customizable seed data in the database.

To upgrade a wft file on the database, please use the following command:

WFLOAD apps/pwd 0 Y UPGRADE file.wft
e.g.
WFLOAD apps/apps 0 Y UPGRADE POAPPRV.wft

Note:
Please make sure to replace file.wft with the name of the wft file containing the workflow definition to be upgraded on the database.

​Force Upload:

You can use the "Force" to force an upload of the process definitions from an input file to a database regardless of an object's protection level. You should be certain that the process definition in the file is correct as it overwrites the entire process stored in the database. The Force mode is useful for fixing data integrity problems in a database with a known, reliable file backup.

If you would like to force the load of specific wft files, please use the following command, while replacing pwd with the apps password, and file.wft with the name of the wft file that you want to force upload to the database:

To force upload a wft file to the database, please use the following command:

WFLOAD apps/pwd 0 Y FORCE file.wft
e.g.
WFLOAD apps/apps 0 Y FORCE POAPPRV.wft

Note:
Please make sure to replace file.wft with the name of the wft file containing the workflow definition to be force uploaded to the database.

​Note:

In case of working on a translated workflow process definition, before using the above commands, make sure to set the environmen variable NLS_LANG properly, using a
syntax like the following:

export NLS_LANG=LANGUAGE_TERRITORY.CHARACTERSETe.g.
export NLS_LANG=FRENCH_FRANCE.UTF8

Oracle Database Extended Support Dates

 Deadline Dates for Current Oracle Database Versions

Oracle publishes a Lifetime Support Policy to describe each aspect of the support that it provides. In summary, each new release of Oracle Database receives five years of Premier Support from its release date. If purchased, Extended Support provides an additional three years for a total of eight. In limited situations, the fee-based Market-Driven Support is also offered. At the end of those types of support, each release enters an indefinite Sustaining Support status.

Here are the support end dates that should be on your radar:

Version 11.2 (11g)

Premier Support ended in January 2015

Extended Support ended December 31, 2020

Market-Driven Support is a paid service that ends December 31, 2022

Version 12.1.0.1

Support for this release has ended, and it isn’t eligible for Extended Support

Version 12.1.0.2

Premier Support ended July 31, 2019

Without Extended Support or an Unlimited License Agreement, Error Correction/Patching ended July 31, 2019

With Extended Support or an Unlimited License Agreement, Error Correction/Patching ends July 31, 2022

Version 12.2.0.1

Error Correction/Patching ended November 30, 2020

Limited Error Correction is available from December 1, 2020, through March 31, 2022

Extended Support is not available

Version 12.2.0.2 (18c)

Error Correction/Patching ends June 30, 2021

Extended Support isn’t available

Version 12.2.0.3 (19c)

Premier Support ends April 30, 2024

Extended Support runs from May 1, 2024, through April 30, 2027

With paid Extended Support, Error Correction/Patching is available through April 30, 2027

Without paid Extended Support, Error Correction/Patching is available through April 30, 2024

Version 21c

Error Correction/Patching ends June 30, 2023

Extended Support is not available

 

What's New : Release Schedule of Current Database Releases

What's New

The most recent changes will be highlighted with a "New" or "Updated" icon to help you quickly identify the modifications.  (For a history of modifications, see the Change Record Table at the bottom of the document.)

New 

·   August 2021: Oracle Database 21c (21.3) released on Linux.

·       June 2021: Oracle will use best effort to support the Oracle 12.1.0.2 Database on Microsoft Windows until July 2022. See Table 1

·    May 2021: Oracle Instant Client 19.10 released on Linux on ARM

May 2021: Oracle is not planning to release 21c on IBM AIX Power Systems and IBM Linux on System Z

Oracle is mindful of the unprecedented economic and business disruption our customers faced in 2020. We decided to not promote our Database 20c Preview version to General Availability. Instead, we incorporated all of the 20c functionality into the 21c release and made 21c available initially in our Autonomous Database Free Tier so that all can test drive the new features and enhancements for free.

Oracle recommends the following upgrade options:

• For product longevity and patching, Oracle strongly recommends upgrading to 19c which is the Long Term Release with a support end date of April 30, 2027 (or April 30, 2024 if you choose not to pay Extended Support fees or purchase a ULA).
• If you are currently running 11.2.x/12.1.x you will need to upgrade to the terminal release (i.e. 11.2.0.4/12.1.0.2) for the DB Release you are running and then continue the upgrade process by upgrading to the 19c.
• If you are currently running 12.2.0.1 or 18c, you should upgrade to 19c without delay.  18c is in Sustaining Support.

For questions related to certification combinations and Lifetime Support agreements with other Oracle products like Oracle E-Business Suite, Oracle JD Edwards, Oracle PeopleSoft, and Oracle Siebel, please contact your Oracle Account Representative.

Patching End Dates for Roadmap

Release	Patching End Date	Notes and Exceptions
21cInnovation Release	April 30, 2024	Error Correction / Patching is available until April 30, 2024 21c is not eligible for Extended Support (ES) Only quarterly Release Updates (RUs) are provided for 21c. Release Update Revisions (RURs) are limited to Long Term Releases.
19c Long Term Release	April 30, 2024 with no ES/ULA April 30, 2027 with ES/ULA	Premier Support (PS) ends April 30, 2024, Extended Support (ES) fees will be required beginning May 01, 2024 through April 30, 2027 Error Correction / Patching is available through April 30, 2027 with paid ES. Without paid ES, patching is only available until April 30, 2024
18c Innovation Release	Jun 30, 2021	Error Correction / Patching was available until Jun 30, 2021. 18c is now in Sustaining Support. 18c is not eligible for Extended Support (ES)
12.2.0.1	March 31, 2022 (Limited Error Correction from Dec 1, 2020 through March 31, 2022)	Error Correction / Patching is available until Nov 30, 2020 Limited Error Correction (Sev 1 and Security Updates only)    See Note 161818.1 for details. 12.2.0.1 is not eligible for Extended Support (ES)
12.1.0.2 Terminal Release	Jul 31, 2022 with paid ES, ULA, or EBS waiver	Premier Support (PS) ended Jul 31, 2018 and one year of free Extended Support (ES) was in effect until July 31, 2019. ES fees or a ULA was required beginning 01-Aug-2019 through 31-Jul-2022. Without paid ES or ULA, patching ends 31-Jul-2019.   We have a global ES uplift fee waiver in place for E-Business customers, see details and dates of expiration see: Extended Support Fee Waiver for Oracle Database 12.1 and 11.2 for Oracle E-Business Suite (Doc ID 2522948.1) or Technical Support Policy Document. * One additional year (01-Aug-2021 through 31-July-2022) has been added to the 12.1.0.2 DB Extended Support time frame with the following exceptions: Apple Macintosh platform patching end date (Error Correction end date) is July 31, 2021.  Microsoft Windows platform exception has changed.  Regardless of the version used to run the 12.1.0.2 Database, Oracle built the 12.1.0.2 Database on Microsoft Windows 2008  This platform reached end-of-life support on January 14, 2020. However, we will make reasonable efforts to deliver patches for the Database 12.1.0.2 on Windows until July 2022, as long as our tooling continues to function.
12.1.0.1	Aug 31, 2016	Error Correction / Patching has ended for this release 12.1.0.1 is not eligible for Extended Support (ES) 12.1.0.1 was the last release of Standard Edition (SE) and Standard Edition One (SE1)
11.2.0.4 Terminal Release for 11.2	Dec 31, 2020 (with paid Extended Support or ULA Extended Support or EBS Waiver) Dec 31, 2022 (with Market Driven Support) Dec 31, 2021 for the OpenVMS platform	Premier Support (PS) ended 31-Jan-2015 and one year of free Extended Support (ES) was in effect until Dec 31, 2018. ES fees or a ULA was required beginning Jan 1, 2019 through Dec 31, 2020. At the end of ES, Market Driven Support (MDS) will be available for two additional years. See https://www.oracle.com/a/ocom/docs/ds-mds-database-11g-r2.pdf Oracle has a global Extended Support Uplift Fee waiver in place for E-Business customers, see details and dates of expiration see: Extended Support Fee Waiver for Oracle Database 12.1 and 11.2 for Oracle E-Business Suite (Doc ID 2522948.1) or Technical Support Policy Document. Gen 1 and Gen 2 ExaCC, OCC DBCS, OCI DBCS,OCI ExaCS and ODA had 3 additional months of Extended Support. The end of Extended Support for 11.2.0.4 databases on these platforms was: 31-March 2021. New instances could be created up until the end of extended support; however, Oracle makes no commitment that any 11.2.0.4 DBCS instances will continue to run after the end of Support. Market Driven Support is only available for the following Database Cloud Services: Gen 1 and Gen 2 ExaCC, OCC DBCS, OCI DBCS (non-PSM), OCI ExaCS.  New instances can be created up until the end of Market Driven Support.  Oracle makes no commitment that any 11.2.0.4 DBCS instances will continue to run after the end of MDS support. Market Driven Support is not available for PSM-based OCI DBCS, OCI-C DBCS and OCI-C ExaCS. 11.2.0.4 is the terminal release on OpenVMS. During calendar year 2021, customer will receive Severity 1 Fixes and Security Updates for no additional fees beyond standard Premier Support costs. Coverage does not extend to new certifications, third-party products, or any Java/JDK functionality including Java components embedded in the database. Coverage also excludes any updates related to cryptography and network encryption. This offering does not include standard Security Patch Updates (SPUs).

Change History (2020 -2021)

Date	What Changed?
13-Aug-2021	Oracle Database 21.3 released on Linux with a patching end date of April 30, 2024
08-Jun-2021	Oracle will use best effort to support the Oracle 12.1.0.2 Database on Microsoft Windows until July 2022.  See Table 1 above.
03-Jun-2021	Added Market Driven Support is not available for PSM-based OCI DBCS, in 11.2.0.4
05-May-2021	Oracle Instant Client 19.10 released on Linux on ARM
04-May-2021	Oracle is not planning to release 21c on IBM AIX Power Systems and IBM Linux on System Z (Added link to Doc ID 2766930.1 05/06/2021)
16-Dec-2020	Updated Table 1 11.2.0.4 Market Driven Support bullet for Database Cloud Services
08-Dec-2020	Updated Roadmap, Added 21c information
23-Nov-2020	Changed end date for 18c from June 08, 2021 to June 30, 2021 to match contract date requirements.
12-Oct-2020	Added OpenVMS Itanium Support dates that will extend their support until Dec 31, 2021.  See Table 1 - 11.2.0.4 section above.
02-Sep-2020	Added additional information around 11.2.0.4 DBCS and Market Driven Support. See Table 1- 11.2.0.4 section above.
03-Aug-2020	Because 12.2.0.1 LEC applies to all on-prem and DB cloud services, removed the following from 12.2.0.1 bullet points: 'Limited Error Correction applies to Gen 1 ExaCC, OCC DBCS, and ODA (UPDATED)'.  Added a comment that MDS does not apply to DBCS (This comment was removed 02-Sep-2020) Amended 12.1.0.2 EXS extension to specifically call out the Windows exception end date is the 'Patching/Error Correction end date'.  In certify, the EXS date for Windows platforms will still show as July 31, 2022 due to a tool limitation but patching (including bundles) will stop July 31, 2021.
10-Jun-2020	Added Long Term and Innovation release definitions, added updated Premier and Extended Support dates for 19c, added terminal release for the Solaris x86-64 bit platform, clarified the 12.2.0.1 additional 3 months of support for Gen 1 ExaCC, OCC DBCS, and ODA has been absorbed into Limited Error Correction window.
15-Apr-2020	Added Limited Error Correction for 12.2.0.1 from Dec 1, 2020- until March 31, 2022
23-Mar-2020	Gen 1 ExaCC, OCC DBCS, and ODA will have 3 additional months of support life. The end of life dates for databases on these platforms is: 11.2.0.4: 31-March 2021 12.2.0.1: 28-Feb-2021
Jan 28, 2020	Restructured original document, removed older releases that are no longer covered under Premier or Extended Support, removed unnecessary information contained in other documents, Added estimated release dates for annual release 20c.